probot-home-assistant[bot]
commented
4 years ago esphome documentation esphome source (message by IssueLinks)
Closed picto3000 closed 4 years ago
probot-home-assistant[bot]
commented
4 years ago esphome documentation esphome source (message by IssueLinks)
probot-home-assistant[bot]
commented
4 years ago Hey there @OttoWinter, mind taking a look at this issue as its been labeled with a integration (esphome) you are listed as a codeowner for? Thanks!
(message by CodeOwnersMention)
picto3000
commented
4 years ago An update that 0.110.2 has helped the situation. Logs are still showing failed pings and disconnects, Logbook are showing devices going unavailable and disconnecting/reconnecting, but the devices uptime counters are no longer resetting and switches are no longer momentarily switching off/on.
ronytomen
commented
4 years ago I had a similar issues in the past:
What do the logs on the ESPHome device tell you?
picto3000
commented
4 years ago As of 0.110.4 the unavailable/available Logbook entries have stopped. HA logs are not showing any failed pings or disconnects.
I had a similar issues in the past:
- 2.4 GHz network needed to be isolated because of congestion and overlap with neighbors. This one just started happening on day, luckily it did not correspond with an upgrade or other change to the system.
- On ESP32 devices where I was doing Bluetooth Low Energy (BLE) scanning there were major issues with timing of WiFi and Bluetooth which resulted in those devices dropping off the network. There has been a lot of discussions around this issue. I resolved it for my main BLE scanner by moving to the ESP32 module with Ethernet to remove WiFi from the equation.
What do the logs on the ESPHome device tell you?
I've been managing 2.4Ghz WiFi congestion by making sure an unused band is being used. Overall I don't have much 2.4Ghz congestion.
None of my ESP devices have Bluetooth. I do use mitemp_bt BLE sensors, which are polled by HA using my NUC's BT, but as part of my testing I disable this integration and the issue still remained.
ryanjohnsontv
commented
4 years ago In several of my devices I've had to add this to the logger component, and doing so stopped the exact same issues that you seem to be experiencing:
logger:
baud_rate: 0
laca75tn
commented
4 years ago Thanks for posting your solution. How is that fixing the problem?
picto3000
commented
4 years ago This has now come back without upgrading HA, and I now suspect the issue is devices rebooting. I'll open a ticket with ESPHome but won't close this just yet.
In several of my devices I've had to add this to the logger component, and doing so stopped the exact same issues that you seem to be experiencing:
logger: baud_rate: 0
This has no affect.
stale[bot]
commented
4 years ago There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
Lepelot
commented
2 years ago I don't know if this issue has been resolved, but I am experiencing it right no with mini switches and I relay board I purchased recently (ATHOM with ESPHome installed). Isolating the 2.4GHz wifi network seem to improve the situation, but they are still disconnecting randomely.
The problem
For a couple of weeks all ESPHome devices are randomly disconnecting, causing:
Looking into the logs, device pings appear to be failing and HA disconnects the device, only to rediscover the device almost instantaneously.
Occurring on a range of ESPhome devices:
Historically I've seen similar behaviour caused by custom_components, but none are installed and have reduced my setup complexity to remove possible component interference. All with no change.
Environment
Problem-relevant
configuration.yamlN/A
Traceback/Error logs
Example Kogan Smart Plug ESPHome YAML - all yamls are very similar:
Additional information
I see #35540 but this appears to be unrelated. Different log issues.