Need Hassio reboot in order to reconnect ESPHome device

ESPHome
1

Hi,

i am using the latest Stable Versions of Homeassistant and ESPHome.
It is a fantastic thing and i really love it thanks to all developers involved.

But here is my Problem … after a few days a start to loose connection to the ESPHome devices … one by one with an interval off multiple days.
After having a look into my network i see that they are all connected properly to my network, so i tried to manually reset the lost node … but nothing changes, also restarting the ESPHome Plugin didnt solve the issue …
the only way to reconnect the node is to restart the entire hassio, after that everything is back to normal for some days.

any ideas or solution? i dont really want to restart my homeassistant every time a node looses connection.

br

2

How many wifi devices do you have and what are you using as a wifi access point/router?

3

at the moment ~15 wifi devices distributed to 2 base stations from TP-Link Deco M4 Mesh.
EDIT:
to be exact there are 5 ESPHome devices 2 H801 and 3 wemos d1 mini based, the rest are mobile devices and tv sticks

but i have no problem reaching them over wifi, they are there and i am able to connect to them from my PC … and after a restart of Homeassistant they get added and there entities are active again :confused:

4

Yeah ok, that sounds fine. People trying to connect to 40+ Wifi devices using a home all in one router/modem/wifi AP can see clients drop off the network. That’s not your issue.

Any relevant errors or warnings in your home assistant logs?

6

No errors no Warnings, i will check the logs for anything suspicious in the info logs as soon as i am at home again

Edit: no nothing to find in the logs

7

Now i got the following:

Logger: homeassistant.components.esphome
Source: components/esphome/init.py:197
Integration: ESPHome (documentation, issues)
First occurred: 18:14:49 (2 occurrences)
Last logged: 18:17:19

  • Error getting initial data for 192.168.1.170: Timeout while waiting for API response!
  • Error getting initial data for 192.168.1.170: Disconnected while waiting for API response!

the funny thing is that i now lost connection to another device but not the the device with ip ending with 170

1 Like
8

I have exactly the same problem; only error messages are that the sensors of the device are not readable, even after the device has reconnected to the lan.

I did not have this problem at 2021.3.4, it started after upgrading to 2021.12.3, and persists at current 2021.12.7 .

Upgrading python from 3.8.0 to 3.8.12 did not make any difference.

I found these errors in my log:

Blockquotean 2 22:31:34 backupserver hass[3789]: #033[31m2022-01-02 22:31:34 ERROR (MainThread) [custom_components.dewpoint.sensor] Unable to read relative humidity from sensor sensor.th16_garage_humidity, state: unavailable#033[0m
Jan 2 22:31:42 backupserver hass[3789]: #033[33m2022-01-02 22:31:42 WARNING (MainThread) [aioesphomeapi.reconnect_logic] Can’t connect to ESPHome API for 10.0.0.185 @ 10.0.0.185: Unexpected error while connecting to sonoffth16_garage @ 10.0.0.185: #033[0m
Jan 2 22:31:49 backupserver hass[3789]: #033[33m2022-01-02 22:31:49 WARNING (MainThread) [homeassistant.components.esphome] Error getting initial data for 10.0.0.185: Timeout waiting for response for <class ‘api_pb2.ListEntitiesRequest’>#033[0m
Jan 2 22:31:54 backupserver hass[3789]: #033[31m2022-01-02 22:31:54 ERROR (MainThread) [homeassistant] Error doing job: Future exception was never retrieved
Jan 2 22:31:54 backupserver hass[3789]: AssertionError
Jan 2 22:31:54 backupserver hass[3789]: aioesphomeapi.core.ReadFailedAPIError: Read failed#033[0m
Jan 2 22:32:00 backupserver hass[3789]: #033[31m2022-01-02 22:32:00 ERROR (MainThread) [custom_components.dewpoint.sensor] Unable to parse temperature sensor sensor.th16_garage_temperature with state: unavailable#033[0m
Jan 2 22:32:00 backupserver hass[3789]: #033[31m2022-01-02 22:32:00 ERROR (MainThread) [custom_components.dewpoint.sensor] Unable to read relative humidity from sensor sensor.th16_garage_humidity, state: unavailable#033[0m
Jan 2 22:32:04 backupserver hass[3789]: #033[33m2022-01-02 22:32:04 WARNING (MainThread) [homeassistant.components.esphome] Error getting initial data for 10.0.0.185: Timeout waiting for response for <class ‘api_pb2.ListEntitiesRequest’>#033[0m
Jan 2 22:32:12 backupserver hass[3789]: #033[31m2022-01-02 22:32:12 ERROR (MainThread) [custom_components.dewpoint.sensor] Unable to read relative humidity from sensor sensor.th16_garage_humidity, state: unavailable#033[0m
Jan 2 22:35:13 backupserver hass[3789]: #033[31m2022-01-02 22:35:13 ERROR (MainThread) [custom_components.dewpoint.sensor] Unable to parse temperature sensor sensor.th16_garage_temperature with state: unavailable#033[0m
Jan 2 22:35:13 backupserver hass[3789]: #033[31m2022-01-02 22:35:13 ERROR (MainThread) [custom_components.dewpoint.sensor] Unable to read relative humidity from sensor sensor.th16_garage_humidity, state: unavailable#033[0m
Jan 2 22:35:22 backupserver hass[3789]: #033[33m2022-01-02 22:35:22 WARNING (MainThread) [homeassistant.components.esphome] Error getting initial data for 10.0.0.185: Timeout waiting for response for <class ‘api_pb2.ListEntitiesRequest’>#033[0m
Jan 2 22:35:29 backupserver hass[3789]: #033[31m2022-01-02 22:35:29 ERROR (MainThread) [custom_components.dewpoint.sensor] Unable to read relative humidity from sensor sensor.th16_garage_humidity, state: unavailable#033[0m

Blockquote