I went here to check if anybody tried it yet.
Just installed 61.1
No apparent issues so far
1 Like
Good for me, too.
No more 10 second warnings either!
3 Likes
I’ve successfully updated to 0.61.0 yesterday on my pi zero, however today after a reboot the same (not ui loading problem) occurred. Next I updated to 0.61.1 and it worked again! But after a restart the same problem…
The hassio ha logs say something like
2018-01-17 21:31:39 ERROR (MainThread) [homeassistant.core] Error doing job: Fatal error on transport TCPTransport (error status in uv_stream_t.shutdown callback)
OSError: [Errno 107] Socket not connected
2018-01-17 21:31:39 INFO (MainThread) [transitions.core] Exited state connected
2018-01-17 21:31:39 INFO (MainThread) [transitions.core] Entered state disconnected
2018-01-17 21:31:39 INFO (MainThread) [hbmqtt.broker] Listener ‘default’: 0 connections acquired
2018-01-17 21:31:39 ERROR (MainThread) [homeassistant.core] Error doing job: Fatal error on transport TCPTransport (error status in uv_stream_t.shutdown callback)
OSError: [Errno 107] Socket not connected
core-ssh:~#
And the supervisor logs complain about a watchdog api and says that it’s restarting home assistant…
seemed that way indeed, but now my hassio has gone…
rebooted 3 times, same result:
2018-01-17 23:23:13 WARNING (MainThread) [homeassistant.setup] Setup of hassio is taking over 10 seconds.
2018-01-17 23:23:14 ERROR (MainThread) [homeassistant.components.hassio] Timeout on /supervisor/ping request
2018-01-17 23:23:14 ERROR (MainThread) [homeassistant.components.hassio] Not connected with HassIO!
2018-01-17 23:23:14 INFO (MainThread) [homeassistant.setup] Setup of domain hassio took 34.1 seconds.
2018-01-17 23:23:14 ERROR (MainThread) [homeassistant.setup] Setup failed for hassio: Component failed to initialize.
now what.
try host reboot? Hard reset? wait for a new update…?
Cheers,
Marius
Not sure what that could be sorry.
I’d be sure supervisor is 0.82 and then I’d try an host reboot
BIngo:
2018-01-18 00:00:07 INFO (MainThread) [homeassistant.setup] Setting up hassio
2018-01-18 00:00:11 INFO (MainThread) [homeassistant.setup] Setup of domain hassio took 3.4 seconds.
pfff, lets give it a good rest now…
Got same experience as you (sporadic UI not loading) on 61.0 as well.
Been wanting to migrate from Hassbian to Hassio, given your experience I might now wait for 61.2 till I give hassio a go.
From another thread I found out the errors I got were due to my system not booting fast enough… I tried to disable some components and it boots! I’ve now set up mariadb as to make it a bit faster and I ordered a pi3 xD
No luck trying to update… 60.1 works ok, 61.1 is “loading data” forever!
Supervisor is 0.83 on a PI3.
Back to 60.1!
Hi guys, maybe you can help… I am unable to update Hassio after 0.59.2. I am running most up to date version of the supervisor (0.83), but I cant manage to update HA. I’ve tried to update it both on the front-end and via the command line (using hassio homeassistant update and curl -d methods). All the errors and log notes are not really descriptive in it’s nature, especially since I’m 100% sure these versions and images DO exist.
On the command line the error I’m getting is:
{"result": "error", "message": null}
supervisor logs:
Updated to 0.61.1 and no problems. Also running supervisor 0.83…
Everything is working well…
I found the problem, it was the chuangmi custom component… all good now!
how do i downgrade. new and dont know. i updated to 61 and none of my switchs let me control them
After few days of headaches with the new version, i found that the main issue with all errors in my Supervisor are because home assistant could not connect with curl to other hostnames.
Same errors all the time
curl: (6) Could not resolve host:
Duckdns addon is not working and says:
ERROR: Problem connecting to server (get for https://acme-v01.api.letsencrypt.org/directory; curl returned with 6)
Wheather stopped, nmap is stopped, cloud component is not working mtqq is not working and all others that need a connection from HA to the outside world.
At the same time, my panel is accessible from outside to my xxx.duckdns.org:8123 without any issues.
I found a threat that says that the docker needs to have a falback Google DNS. So i went to /etc/ and nano the resolv.conf with the following:
nameserver 8.8.8.8
options ndots:0
After that via SSH i can curl hostnames but still cannot connect via HA.
Please help me… to solve that huge issue
btw. I found this issue report
But i am with RPi3 and everything was working just perfect before the upgrade.
I ran into something similarly recently, Im running on ubuntu, but following the advice in the bottom this linked thread to update the host’s resolv.comf fixed the issues for me.
I fix it with deleting the home-assistant_v2.db file 
Question @Peter_Iliev - What gets lost if you kill that DB file? im running into this issue now on my system.
Killing your DB will have influence on your history and logbook
1 Like