Closed mcnutter1 closed 3 years ago
Still happening, no indication as to why and it happens on a completely clean build.
Have you tried to disconnect your Sonos speakers and check if HA becomes more stable ? I have a similar issue that dissappears if I disconnect all my sonos (HA was stable more than 1 week vs 2-3 days max with Sonos). I suspect this issue might be related to a network loop with Sonos speakers and the network access points. As Sonos speakets might be connected both WiFi and Ethernet, it might end-up with an infinite network loop that might saturate hass.io docker connection pool (see https://github.com/home-assistant/home-assistant/issues/24853#issuecomment-509330221). Unfortunatelly, so far, I don't have solved this issue. I plan to connect all my Sonos thorugh Ethernet with WiFi disabled. @zacs any news from your side with your Sonos issue ?
Thanks.
My guess is network loop (specifically STP settings) was responsible for this. I enabled STP on my switches following the guidance Sonos gives here, after seeing it linked at this very good article describing the issue. I recently (accidentally) reverted the STP change and my entire home network became a disaster, so I'm guessing this may help. I'd note that all (well, most) my Sonos are connected via ethernet and that actually made the problem worse until I fixed STP.
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.
I've narrowed this down to the iaqualink plugin, the issue started happening again now that I turned my pool equipment on for the year... havent had this issue the entire winter.
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.
Home Assistant release with the issue: 99.2, 99.3, 100.1, 100.2
Last working Home Assistant release (if known): 89.X
Operating environment (Hass.io/Docker/Windows/etc.): Ubuntu 19.0.4
Integration: ISY, Aqualink, Tesla, Ring, Nest, Alexa, Sonos, Unifi
Description of problem: Homeassistant's Web UI and all automations top working randomly after a period of time... Ranging between an hour and 8 hours... Logs are set to Warn but no events are reported. Was happening to me after an upgrade to 99.2... Built a new VM with Ubuntu 19.0.4, clean install of HASS using Python 3.7.3 in a VENV, just copied the config file and it still crashes. I've disabled countless integrations trying to nail it down but no luck.
Problem-relevant
configuration.yaml
entries and (fill out even if it seems unimportant):Entire configuration.yaml...
Traceback (if applicable):
Additional information: