Upstream/esphome-docs
1
0
Fork 0
mirror of https://github.com/esphome/esphome-docs.git synced 2025-01-13 20:11:53 +01:00
Code Issues Projects Releases Wiki Activity

FAQ: fixed location of re-add when unavailable (#3650)

Browse Source
This commit is contained in:
Kevin Reilly 2024-02-28 09:23:44 -08:00 committed by GitHub
parent eb3cfff760
commit 89f7224656
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
components/deep_sleep.rst
View File

@ -23,7 +23,7 @@ to wake up on any RTC pin (``GPIO0``, ``GPIO2``, ``GPIO4``, ``GPIO12``, ``GPIO13
While in deep sleep mode, the node will not do any work and not respond to any network traffic,
even Over The Air updates. If the device's entities are appearing as **Unavailable** while your device is actively
sleeping, this component was likely added after the device was added to Home Assistant. To prevent this behavior,
you can remove and re-add the device within ESPHome.
you can remove and re-add the device in Home Assistant.
.. code-block:: yaml

2
guides/faq.rst
View File

@ -456,7 +456,7 @@ Why do entities show as Unavailable during deep sleep?
The :doc:`Deep Sleep </components/deep_sleep>` component needs to be present within the config when the device
is first added to Home Assistant. To prevent entities from appearing as Unavailable, you can remove and re-add the
device within ESPHome.
device in Home Assistant.
See Also
--------