Timeout kills Homeassistant #13
Comments
More people are experiencing this; please check https://community.home-assistant.io/t/unable-to-reach-home-assistant-ui-ssh/131204?u=emphyrio |
Server is down (locked in a stopping state), not sure when it will be fixed. |
An idea how it can be that a timeout can affect home-assistant I'm such a way? I am thinking if this should be investigated and safeguards put into place inside home-assistant itself so a (custom)component can't bring down the whole system. |
Not really, I have never seen that behavior before. |
How fun.... |
Pushed a release that maybe will fix it, but since I did not have the issue I can not confirm that. |
I manually applied the changes (and restarting HA) allowed me to access the Home Assistant UI. I'm running HA in a Debian python virtual env ver 0.93.2. This morning I was no longer able to access the HA UI and things were running very slowly. Thanks for your fix. |
Version of the custom_component
0.3.2
Describe the bug
hachanges.halfdecent.io is down.
This seems to impact this component which kills my whole homeassistant. Startup when this component is added is about 20 minutes and after that homeassistant only reacts every 2 minutes to any input from the outside.
Somehow the failed update interacts with the async loop in ways it shouldn't.
custom_updater
configuration# Add configuration here
Debug log
The text was updated successfully, but these errors were encountered: