Upstream/esphome-docs
1
0
Fork 0
mirror of https://github.com/esphome/esphome-docs.git synced 2024-12-26 17:27:47 +01:00
Code Issues Projects Releases Wiki Activity

FAQ: unavailable entities during deep sleep (#3648)

Browse Source 
* FAQ: unavailable entities during deep sleep

* Deep sleep: added note about unavailable entity states

---------

Co-authored-by: Kevin Reilly <kevin.reilly@epicgames.com>
This commit is contained in:
Kevin Reilly 2024-02-27 22:51:46 -08:00 committed by GitHub
parent a49bc0140e
commit eb3cfff760
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 13 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
components/deep_sleep.rst
View File

@ -21,7 +21,9 @@ to wake up on any RTC pin (``GPIO0``, ``GPIO2``, ``GPIO4``, ``GPIO12``, ``GPIO13
``GPIO15``, ``GPIO25``, ``GPIO26``, ``GPIO27``, ``GPIO32``, ``GPIO39``).
While in deep sleep mode, the node will not do any work and not respond to any network traffic,
even Over The Air updates.
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.
.. code-block:: yaml
@ -32,8 +34,8 @@ even Over The Air updates.
.. note::
Some ESP8266s have an onboard USB chip (e.g. D1 mini) on the chips' control line that is connected to the RST pin. This enables the flasher to reboot the ESP when required. This may interfere with deep sleep on some devices and prevent the ESP from waking when it's powered through its USB connector. Powering the ESP from a separate 3.3V source connected to the 3.3V pin and GND will solve this issue. In these cases, using a USB to TTL adapter will allow you to log ESP activity.
Some ESP8266s have an onboard USB chip (e.g. D1 mini) on the chips' control line that is connected to the RST pin. This enables the flasher to reboot the ESP when required. This may interfere with deep sleep on some devices and prevent the ESP from waking when it's powered through its USB connector. Powering the ESP from a separate 3.3V source connected to the 3.3V pin and GND will solve this issue. In these cases, using a USB to TTL adapter will allow you to log ESP activity.
Configuration variables:
------------------------

9
guides/faq.rst
View File

@ -361,7 +361,7 @@ And a docker compose file looks like this:
.. _docker-reference-notes:
.. note::
By default ESPHome uses mDNS to show online/offline state in the dashboard view. So for that feature to work you need to enable host networking mode.
By default ESPHome uses mDNS to show online/offline state in the dashboard view. So for that feature to work you need to enable host networking mode.
On MacOS the networking mode ("-net=host" option) doesn't work as expected. You have to use
another way to launch the dashboard with a port mapping option and use alternative to mDNS
@ -451,6 +451,13 @@ Note that this only works for Pull Requests that only change files within compon
``esphome/components/`` are added or changed, this method unfortunately doesn't work. Those Pull Requests are labeled
with the "core" label on GitHub.
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.
See Also
--------