Stuck on "Loading data" since update to 0.61

Dullage · January 16, 2018, 8:47pm

I have my front end back !

Albeit without Broadlink and Snapcast. The latest step of disabling Snapcast seemed to do it.

I still have that same error in the log though.

rendili · January 16, 2018, 8:47pm

I am not sure I fully understand that, but if the updated .py files were the only platforms / components with the issue with the Domain, I don’t use any of those, so at least my issue is probably not that

rendili · January 16, 2018, 8:47pm

@anderson110, do you get a new error in the log as above, each time your close your browser?
sorry, meant for @Dullage

Dullage · January 16, 2018, 8:51pm

Yup. I’ve just tested this and it does seem to be logged upon browser closure.

rendili · January 16, 2018, 8:53pm

ok great (I think ) at least we are pretty consistent with each other in our installations and time or new error in log

where now?

rendili · January 16, 2018, 8:55pm

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

Dullage · January 16, 2018, 8:57pm

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 .

rendili · January 16, 2018, 9:05pm

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…

rendili · January 16, 2018, 9:35pm

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

7even · January 16, 2018, 9:50pm

same issue here… i removed custom ui for now.

Mister_Slowhand · January 17, 2018, 9:03am

I had the same issue, using broadlink components and custom-ui, and plex. All 3 caused some troubles.

broadlink.py in the switch directory has to be upgraded. If you don’t want to wait, you can copy it as a custom component and change the 3 lines needed : https://github.com/home-assistant/home-assistant/pull/11677
the custom-ui needs to be upgraded to 20180117 in order to work with 0.61 : https://github.com/andrey-git/home-assistant-custom-ui/issues/84
and I also found out that the Plex media player doesn’t start if the “include_non_clients” option is set to “True”.

Works fine now !

Dullage · January 17, 2018, 1:36pm

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

Tolaxor · January 17, 2018, 2:29pm

nvm i jsut need to reload everything

rendili · January 17, 2018, 9:13pm

I just upgraded to 0.61.1 and I still get the error
what else could be causing it?

Dullage · January 17, 2018, 9:21pm

I’ve just updated. Broadlink and Snapcast now working again , still get the error message when closing the browser .

rendili · January 17, 2018, 9:23pm

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

rendili · January 17, 2018, 9:39pm

looks like there is still an open issue for this:

Dullage · January 17, 2018, 9:43pm

Ah good spot! Looks like we just need to keep an eye on that then.

davedan · January 17, 2018, 9:46pm

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 …

rendili · January 17, 2018, 9:46pm

I just subscribed to it and added a few comments