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
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 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 
)
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/))
No errors in the log, and I just rebooted the host to see if that would help. Configuration area still requires a manual refresh when navigating between pages. Same behavior over my OpenVPN connection, from a local machine, and on both Chrome and Safari. Interesting data point is that when I click on one of the configuration sections, all of the UI elements on the page shift left by a few pixels as the URL changes in the address bar, but it still takes a reload to get the new screen to show up.
Another possibility, are you using HA cloud remote? Or cloud web hook?
No i use the old manual method for my google home connection and duckdns for remote connection.
Ok it was appdeamon fixed using token
I’ve just upgraded to 0.90 (from 0.89.2) without any problems.
Thank you very much for giving rest of us a modern and flexible home automation system, without costing us much more than running an upgrade from time to time.
A special thanks to @endor-force for fixing the Tellstick component before it was totally outdated.
