I tried a 4th time to update from .104.3 to .105.2.
Steps
New snapshot
Ran check config no errors.
Read breaking changes. No conflicts, static IP, no ipv6.
Ran update.
SSH and Samba load correctly but can’t get to Lovelace through browser. Cannot connect to host, refused like others above. I tried the chat support and all I’m seeing is reinstall on a fresh sd card. Someone must understand the errors that people are posting here and many other threads and GitHub sites and have a better solution for people to try. Very frustrating when the configuration check says all is good and it still fails.
try disable netatmo – did it for me
2 Likes
Check this website as well: https://github.com/home-assistant/home-assistant/issues/31584
Here also place where people post similar errors and similar solutions… None did the trick for me so far.
I run Hassio on Proxmox VM
1 Like
Update:
Seeing many threads about the issues with 0.105.2, I decided to do a full rollback…
- Fresh SD flash
- hassio rollback to 3.8
- ha rollback to 0.104.3
And there must still be something weird going on, because the moment I restore my (previously working and config checked) backup, it stops responding… even SSH…
I’m starting to be out of ideas here…
R
1 Like
wait for 0.105.3 
I updated, and then, of course, HA will not restart! I mean, why would it? Life would be too boring otherwise. That has become a feature of life now. If you have home assistant, you need to spend all your free time troubleshooting it. So, you’d better enjoy that or you should use something else, because I don’t see this problem going away ever.
Every time there is an update, I know everything will break down after I press that button but I cannot resist. So I press it… And then, I spend the rest of my weekend troubleshooting. So much for home ‘automation’ that makes your life easier. hahahaha
3 Likes
I’m like you, I cannot resist, but the limit for me is the night, I have to rollback, because the only way I have to activate my bedroom roller shutters is using my z-wave remote 
2 Likes
Too long to have my home without HA now 
I´ve been a user since 3 months now… Control my lights, blinds, thermostats, humidifiers and -most importantly- my coffee machine with HA. All the systems (by design) can work without HA, but… I miss my automations and scenes 
New update:
- Fresh SD flash (3.9 and 0.105.2)
- Manual install and configuration of add-ons (just copy and paste config from my backup)
- Manual configuration of HA (copy and paste from backup)
- Config check (passes as expected)
- Happy me…
Not a solution, but at least a workaround until the issue is solved… And didn´t take much longer than a normal restore from backup.
Lessons learnt…
- I´m very happy I always backup before an upgrade (or any config changes)
- Next time, before upgrade… full SD dump… to be able to recover in case the ´restore´ option doesn´t work (like yesterday/today)
R
Ok, I’ve got it!!
Let me explain:
I have Proxmox VM, I do have 2 VM’s running. I was working on one of the VM’s while I had the other one still running…
Read several logs after the reboots, never saw this one, until just now: There was an unique other one running, so I stopped the other VM, upgrade again and viola! It came up.
Just to clarify, both VM’s had unique IP addresses, so no errors there. Apparently the one VM also looked at the other VM …??
I wish I would have left well enough alone… I am a new user to home assistant and raspberry pi. I have been working on my HA for a couple of weeks none stop, and I DID NOT make a backup… I got carried away building it and I have intergrated my whole house to it.
So today when I hit the update button on the home assistant it didnt seem to do anything, and so I decided to update the operating system to 3.9 and that was a huge mistake. when it restarted itself it will not boot. I cant get back into my home assistant and I am really freaking out. I just downloaded some of my files on the sd card using a linux file reader program so I have what I think is most of the yaml files that I spent so much time on. What is the best way to get my instance back up and running. Should I reinstall on a new card and then try to copy over via samba when I have it up and running again? what files do I need other than the yaml files? there seems to be alot of different partions in the linux files. Can I just reinstall and then copy my files back over? Any help would greatly be appreciated.
The problem is if you don’t keep up to date, when you actually want to update there will be so many breaking changes that you will run into so many issues that it may be easier to start fresh if you have missed several releases
SD cards are known for failure many people have switched to storing their config’s on USB’s or away from Raspberry Pi’s all together the best way to reinstall home assistant would be to just move over your config files/folder via SAMBA as the other files on the usb could be corrupt. I highly recommend setting up automatic backups of your config so this doesn’t happen in the future
ok, I may have raised my help flag too soon, I plugged it all back in… and it is up and running again. Now I am trying to make a snapshot, but it also seems just to be having problems, when I click it is just sits there, but I dont want to hijack this thread… thanks
I got the same error, it was because of netatmo device.
Just comment your netamo configuration in configuration file, update yout hassio and after you have to redifine your netatmo config with new options.
1 Like
After a few tries, it finally worked for me as well. Removing netatmo did not work at first, but changing the configuration to the new standard did the trick and I managed to upgrade to 105.2
netatmo:
client_id: YOUR_CLIENT_ID
client_secret: YOUR_CLIENT_SECRET
6 Likes
Hi,
I have also big trouble with updating to 105.1 and Hassos to 3.9.
My deCONZ integration is now empty (all lights are gone) but the rooms still exist.
Also zwave isn’t working anymore. It’s impossible to start network again… so all my lights are out of order. This is really the hell.
Went back to 104.3 but nothing happened. It seems like I never had a zwave system at all. Could it be that the update of HassOs to 3.9 destroyed the zwave stick?
I have no idea how to rebuild this system again using my backups.
Has anybody made some progress with this issue?
Hoping to hear some good news!
Lars
try “wipe and restore” from your snapshot, and stay with 104.3, it worked for me.
what is the difference between “wipe and restore” and just “restore”?
unfortunately same result… no change after “wipe and restore”
Can’t start zwave network anymore.
OZW log:
2020-02-10 13:12:27.399 Always, OpenZwave Version 1.4.3452 Starting Up
2020-02-10 13:12:44.627 Info, Setting Up Provided Network Key for Secure Communications
2020-02-10 13:12:44.628 Info, mgr, Added driver for controller //dev/ttyACM0
2020-02-10 13:12:44.628 Info, Opening controller //dev/ttyACM0
2020-02-10 13:12:44.628 Info, Trying to open serial port //dev/ttyACM0 (attempt 1)
2020-02-10 13:12:44.629 Info, Serial port //dev/ttyACM0 opened (attempt 1)
2020-02-10 13:12:44.630 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2020-02-10 13:12:44.630 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2020-02-10 13:12:44.630 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2020-02-10 13:12:44.630 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2020-02-10 13:12:44.630 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2020-02-10 13:12:44.630 Detail,
2020-02-10 13:12:44.630 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x15) - FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2020-02-10 13:12:45.630 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2020-02-10 13:12:45.630 Detail, contrlr, Removing current message
2020-02-10 13:12:45.630 Detail, contrlr, Notification: Notification - TimeOut
2020-02-10 13:12:45.631 Detail,
2020-02-10 13:12:45.631 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x20) - FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2020-02-10 13:12:46.631 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2020-02-10 13:12:46.631 Detail, contrlr, Removing current message
2020-02-10 13:12:46.631 Detail, contrlr, Notification: Notification - TimeOut
2020-02-10 13:12:46.632 Detail,
2020-02-10 13:12:46.632 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x05) - FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2020-02-10 13:12:47.632 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2020-02-10 13:12:47.633 Detail, contrlr, Removing current message
2020-02-10 13:12:47.633 Detail, contrlr, Notification: Notification - TimeOut
2020-02-10 13:12:47.634 Detail,
2020-02-10 13:12:47.634 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x07) - FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2020-02-10 13:12:48.634 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2020-02-10 13:12:48.634 Detail, contrlr, Removing current message
2020-02-10 13:12:48.635 Detail, contrlr, Notification: Notification - TimeOut
2020-02-10 13:12:48.636 Detail,
2020-02-10 13:12:48.636 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x56) - FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2020-02-10 13:12:49.637 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2020-02-10 13:12:49.637 Detail, contrlr, Removing current message
2020-02-10 13:12:49.637 Detail, contrlr, Notification: Notification - TimeOut