From 8cb61ce6c3f98b51c377847573f95952b76aebc6 Mon Sep 17 00:00:00 2001 From: Franck Nijhof Date: Mon, 12 May 2025 23:07:24 +0200 Subject: [PATCH] Clean up old references to dev-docs.home-assistant.io (#2666) --- docs/asyncio_working_with_async.md | 5 +---- docs/dev_101_config.md | 2 +- docs/dev_101_hass.md | 4 ++-- 3 files changed, 4 insertions(+), 7 deletions(-) diff --git a/docs/asyncio_working_with_async.md b/docs/asyncio_working_with_async.md index 5736af1c..58da0255 100644 --- a/docs/asyncio_working_with_async.md +++ b/docs/asyncio_working_with_async.md @@ -6,7 +6,7 @@ Although we have a backwards compatible API, using the async core directly will ## Interacting with the core -[All methods in the Home Assistant core][dev-docs] are implemented in two flavors: an async version and a version to be called from other threads. The versions for other are merely wrappers that call the async version in a threadsafe manner. +All methods in the Home Assistant core are implemented in two flavors: an async version and a version to be called from other threads. The versions for other are merely wrappers that call the async version in a threadsafe manner. So if you are making calls to the core (the hass object) from within a callback or coroutine, use the methods that start with async_. If you need to call an async_ function that is a coroutine, your task must also be a coroutine. @@ -108,6 +108,3 @@ If you want to spawn a task that will not block the current async context, you c ```python hass.async_create_task(async_say_hello(hass, target)) ``` - -[dev-docs]: https://dev-docs.home-assistant.io/en/dev/api/core.html -[dev-docs-async]: https://dev-docs.home-assistant.io/en/dev/api/util.html#module-homeassistant.util.async diff --git a/docs/dev_101_config.md b/docs/dev_101_config.md index 4e924af7..790ff7fa 100644 --- a/docs/dev_101_config.md +++ b/docs/dev_101_config.md @@ -29,4 +29,4 @@ On [the hass object](./dev_101_hass.md) there is an instance of the Config class | safe_mode | bool | If Home Assistant is running in safe mode | | legacy_templates | bool | Use legacy template behavior | -It also provides some helper methods. [See available methods.](https://dev-docs.home-assistant.io/en/dev/api/core.html#homeassistant.core.Config) +It also provides some helper methods. diff --git a/docs/dev_101_hass.md b/docs/dev_101_hass.md index 9c47d4da..e4cc5849 100644 --- a/docs/dev_101_hass.md +++ b/docs/dev_101_hass.md @@ -11,8 +11,8 @@ The Home Assistant instance contains four objects to help you interact with the | Object | Description | | ------ | ----------- | -| `hass` | This is the instance of Home Assistant. Allows starting, stopping and enqueuing new jobs. [See available methods.](https://dev-docs.home-assistant.io/en/dev/api/core.html#homeassistant.core.HomeAssistant) -| `hass.config` | This is the core configuration of Home Assistant exposing location, temperature preferences and config directory path. [See available methods.](https://dev-docs.home-assistant.io/en/dev/api/core.html#homeassistant.core.Config) +| `hass` | This is the instance of Home Assistant. Allows starting, stopping and enqueuing new jobs. | +| `hass.config` | This is the core configuration of Home Assistant exposing location, temperature preferences and config directory path. | | `hass.states` | This is the StateMachine. It allows you to set states and track when they are changed. [See available methods.](https://developers.home-assistant.io/docs/dev_101_states) | | `hass.bus` | This is the EventBus. It allows you to trigger and listen for events. [See available methods.](https://developers.home-assistant.io/docs/dev_101_events) | | `hass.services` | This is the ServiceRegistry. It allows you to register service actions. [See available methods.](https://developers.home-assistant.io/docs/dev_101_services) |