Closed alfonsolsl closed 5 years ago
I experienced the same issue using Docker for versions 0.90.2 and 0.91.
From the code history it looks like maybe @wonderslug or @teharris1 would be the best ones to take a look at this.
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.
This is still a issue to be resolved.
I also have this. I bought a hub, put in the correct config (as best as I can see, but checked and re-checked it several times). 100% of the time it bricks my Home Assistant interface to the point I have to restart.
I’ll start with a fresh install, and the moment I add the Insteon config, it’s gone until I wipe the card and replace it with another fresh install.
Can you confirm you are using the Hub password, not the APP password? They are different.
Good to know! I’m definitely using my App password, as I didn’t know there was a Hub password. How do I find the Hub password?
Thanks! -Chris On Aug 23, 2019, 8:11 AM -0700, Tom Harris notifications@github.com, wrote:
Can you confirm you are using the Hub password, not the APP password? They are different. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.
Home Assistant release with the issue: 0.90.2
Last working Home Assistant release (if known):
Operating environment (Hass.io/Docker/Windows/etc.): HASS.IO
Component/platform: INSTEON
Description of problem: When the configuration doesn't match and the HUB refuse the connection the front end don't load.
When the hub is unreacheble the same happens
The other components appear to load correctly.
Problem-relevant
configuration.yaml
entries :Traceback (if applicable):
Additional information:
Log: