I don’t know enough on the topic, but could this be related?
HTTP-01
was used in the command line I used to install LetsEncrypt
I don’t know enough on the topic, but could this be related?
HTTP-01
was used in the command line I used to install LetsEncrypt
It looks as though the pull request will be published in an interim 0.61.1 build which will hoepfully be released pretty quickly. I can do without Broadlink and Snapcast for a few days so I might wait and re-test after applying this.
Yeh, there’s a lot I don’t understand in that question so not sure either .
I guess for now that is the only that can be done.
I also saw this which could be in the same release:
https://github.com/home-assistant/home-assistant/pull/11660
maybe this will help also? it has an upgrade to the aiohttp version, this is component…
so a I little more testing and I have found that loading home assistant in Microsoft Edge does not add any new errors, but loading home assistant in Chrome adds a new error when closing the browser
no idea what this means, but I just thought I would mention it
same issue here… i removed custom ui for now.
I had the same issue, using broadlink components and custom-ui, and plex. All 3 caused some troubles.
Works fine now !
0.61.1 is now out and has the pull request mentioned above: https://home-assistant.io/blog/2018/01/14/release-61/#release-0611---january-16
nvm i jsut need to reload everything
I just upgraded to 0.61.1 and I still get the error
what else could be causing it?
I’ve just updated. Broadlink and Snapcast now working again , still get the error message when closing the browser .
good news you are fully up and running again
I am sort of comforted to know it is not just me that still has the issue still with the error on browser close. would be nice to find a fix for it
looks like there is still an open issue for this:
Ah good spot! Looks like we just need to keep an eye on that then.
I was having the same issue driving me crazy.
I tested each and every config file one by one by removing everything and adding step by step …
got resolved when I upgraded to Hassio 0.61.1 …
I just subscribed to it and added a few comments
Hi @davedan
Did you have the error with Hassio on a previous version, or did you get the error on a Hassbian type build
I found the error when I was doing some updates/configs. I was in 0.60.
ok, thanks
I have done the removing bits from the config for a few, but I guess I need to try a load more.