0.90: Remote UI, Streams, User Groups

Still no luck on updating from 0.89.2 to 0.90

this is the System log I get

19-03-21 15:39:03 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 
19-03-21 15:39:08 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 
19-03-21 15:39:08 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_appdaemon3 
19-03-21 15:39:08 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 
19-03-21 15:39:13 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 
19-03-21 15:39:13 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_appdaemon3 
19-03-21 15:39:13 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 
19-03-21 15:39:14 WARNING (MainThread) [hassio.homeassistant] Don't wait anymore of Home Assistant startup!
19-03-21 15:39:14 CRITICAL (MainThread) [hassio.homeassistant] HomeAssistant update fails -> rollback! 
19-03-21 15:39:14 INFO (MainThread) [hassio.homeassistant] Update Home Assistant to version 0.89.2 
19-03-21 15:39:14 INFO (SyncWorker_9) [hassio.docker.interface] Update Docker homeassistant/qemux86-64-homeassistant:0.90.0 to homeassistant/qemux86-64-homeassistant:0.89.2 
19-03-21 15:39:14 INFO (SyncWorker_9) [hassio.docker.interface] Pull image homeassistant/qemux86-64-homeassistant tag 0.89.2. 
19-03-21 15:39:18 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 
19-03-21 15:39:18 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_appdaemon3 
19-03-21 15:39:18 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 
19-03-21 15:39:23 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 
19-03-21 15:39:23 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_appdaemon3 
19-03-21 15:39:23 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 
19-03-21 15:39:28 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 
19-03-21 15:39:28 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_appdaemon3 
19-03-21 15:39:28 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 
19-03-21 15:39:33 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 
19-03-21 15:39:33 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_appdaemon3 
19-03-21 15:39:33 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 
19-03-21 15:39:38 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 
19-03-21 15:39:38 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_appdaemon3 
19-03-21 15:39:38 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 
19-03-21 15:39:43 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 
19-03-21 15:39:43 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_appdaemon3 
19-03-21 15:39:43 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 
19-03-21 15:39:46 INFO (SyncWorker_9) [hassio.docker.interface] Tag image homeassistant/qemux86-64-homeassistant with version 0.89.2 as latest 
19-03-21 15:39:46 INFO (SyncWorker_9) [hassio.docker.interface] Stop homeassistant/qemux86-64-homeassistant Docker application 
19-03-21 15:39:48 INFO (SyncWorker_9) [hassio.docker.interface] Clean homeassistant/qemux86-64-homeassistant Docker application 
19-03-21 15:39:48 INFO (SyncWorker_9) [hassio.docker.interface] Cleanup Docker images: ['homeassistant/qemux86-64-homeassistant:0.90.0'] 
19-03-21 15:39:48 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 
19-03-21 15:39:48 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_appdaemon3 
19-03-21 15:39:48 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 
19-03-21 15:39:49 INFO (SyncWorker_7) [hassio.docker.homeassistant] Start homeassistant homeassistant/qemux86-64-homeassistant with version 0.89.2 
19-03-21 15:39:53 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 
19-03-21 15:39:53 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_appdaemon3 
19-03-21 15:39:53 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 
19-03-21 15:39:58 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 
19-03-21 15:39:58 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_appdaemon3 
19-03-21 15:39:58 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 
19-03-21 15:40:03 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 
19-03-21 15:40:03 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_appdaemon3 
19-03-21 15:40:03 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 
19-03-21 15:40:08 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 
19-03-21 15:40:08 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_appdaemon3 
19-03-21 15:40:08 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 
19-03-21 15:40:13 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 
19-03-21 15:40:13 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_appdaemon3 
19-03-21 15:40:13 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 
19-03-21 15:40:18 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 
19-03-21 15:40:18 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_appdaemon3 
19-03-21 15:40:18 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 
19-03-21 15:40:23 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 
19-03-21 15:40:23 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_appdaemon3 
19-03-21 15:40:23 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 
19-03-21 15:40:28 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 
19-03-21 15:40:28 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_appdaemon3 
19-03-21 15:40:28 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 
19-03-21 15:40:33 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 
19-03-21 15:40:33 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_appdaemon3 
19-03-21 15:40:33 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 
19-03-21 15:40:38 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 
19-03-21 15:40:38 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_appdaemon3 
19-03-21 15:40:38 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 
19-03-21 15:40:43 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 
19-03-21 15:40:43 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_appdaemon3 
19-03-21 15:40:43 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 
19-03-21 15:40:48 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 
19-03-21 15:40:48 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_appdaemon3 
19-03-21 15:40:48 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 
19-03-21 15:40:53 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 
19-03-21 15:40:53 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_appdaemon3 
19-03-21 15:40:53 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 
19-03-21 15:40:58 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 
19-03-21 15:40:58 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_appdaemon3 
19-03-21 15:40:58 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 
19-03-21 15:41:03 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 
19-03-21 15:41:03 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_appdaemon3 
19-03-21 15:41:03 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 
19-03-21 15:41:08 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 
19-03-21 15:41:08 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_appdaemon3 
19-03-21 15:41:08 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 
19-03-21 15:41:13 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 
19-03-21 15:41:13 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_appdaemon3 
19-03-21 15:41:13 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 
19-03-21 15:41:18 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 
19-03-21 15:41:18 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_appdaemon3 
19-03-21 15:41:18 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 
19-03-21 15:41:23 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 
19-03-21 15:41:23 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_appdaemon3 
19-03-21 15:41:24 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request running 
19-03-21 15:41:24 INFO (MainThread) [hassio.api.proxy] /homeassistant/api/config access from a0d7b954_appdaemon3 
19-03-21 15:41:24 INFO (MainThread) [hassio.api.proxy] /homeassistant/api/states access from a0d7b954_appdaemon3 
19-03-21 15:41:24 INFO (MainThread) [hassio.homeassistant] Detect a running Home Assistant instance 
19-03-21 15:41:24 INFO (MainThread) [hassio.homeassistant] Successful run Home Assistant 0.89.2```

Any suggestion?

I have an Ubuntu server with Docker and Hassio installed in containers.

Earlier today I restarted Home Assistant just before I went out and it wasn’t accessible via the remote endpoint until I manually used https://remote.nabucasa.com to connect (this was at least an hour after I restarted it).

Now it seems to be working like you said and it is accessible soon after restarting without needing that automation, so I don’t know what the problem could have been earlier (unless there was a network issue and the remote connection was dropped).

I’ve tried to restore my yesterday backup from 0.89.2 to a newly fresh install of Hassio in docker on a VirtualBox Ubuntu server and it works, fortunately.

Should I try this to update to 0.90, since I’m getting error and rollback when trying to update “normally” ?

Thanks

Remote access and stream look very promising…

Edit: got this working with my Apple TVs… Amazing stuff!

I think a need to move my Hass.io install to a more powerful machine to improve the speed.

The default was discovery: and hassio would be “discovered”. If you ever disabled discovery: you would specify hassio: in its place in order to have the hassio panel. I think a change involving default_config: removed discovery: for some users and they ended up without a hassio panel.

The new change is that hassio: is now the default so that it doesn’t depend on discovery: You still don’t want to remove hassio: or comment it out.

Tado device tracking not working indeed, hope for fix

I try add hassio and remove discovery and back and both. But always have error

> 2019-03-21 16:04:48 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /supervisor/ping request 2019-03-21 16:04:48 ERROR (MainThread) [homeassistant.components.hassio] Not connected with Hass.io 2019-03-21 16:04:48 ERROR (MainThread) [homeassistant.setup] Setup failed for hassio: Component failed to initialize.

I would try with both entered and a full reboot.

Konnected problems here also.

Not seen it mentioned but also problems with the loop energy monitor too.

Any help appreciated!

WD

1 Like

Temporary fix for tado device tracking:

https://github.com/home-assistant/home-assistant/issues/22208#issuecomment-475071636

I just found out. It doesn’t depend on hassio: or discovery: anymore.

After upgrading to 0.90 it happen:

1 Like

After the update i get this warning

api_password is going to deprecate. You need to use a bearer token to access /api/ from 172.30.32.2

I know this IP address is related to the supervisor anyone else experience this?

Have you cleared browser cache? (I deleted your gif for privacy reasons :male_detective: )

Yes, I did. Same on Chrome and Firefox.

Should not come from hassio itself, maybe some add-on

I understand that supervisor 150 is supposed to address the screen drawing issues, but after clearing cache, cookies, and restarting my browser, I’m still seeing some navigation issues in the Configuration section. I can get into the Configuration section by clicking the link in the left bar, but once I’m there none of the sections will open. When I click on “Home Assistant Cloud”, “Integrations”, “Users”, etc., I see the URL in address bar change, but the screen doesn’t redraw to show the new section. If I then do a normal “reload” in the browser, the new section shows up.

Do I need to do anything other than restarting HA and hitting “reload” in the Hass.io System tab to ensure that I’m using the latest supervisor? This is all in the latest Chrome on MacOS, BTW.

Check log. Maybe you have same issue as me…

Thank you i will investigate my add-ons is that include custom cards?

Hi,

will this give trouble to Happy Bubble Presence Server?

* **MQTT** - Pass Message object to MQTT message callbacks instead of topic, message and qos. Users of custom components please take note, these values are now available on the passed in message object: msg.topic, msg.message, msg.qos . The old method will continue to work for now but will print warnings. ([@emontnemery](https://github.com/emontnemery) - [#21959 ](https://github.com/home-assistant/home-assistant/pull/21959)) ([mqtt docs ](https://www.home-assistant.io/components/mqtt/))