Download the snapshot (.tar) file to your computer…
Unpack the file (search online for an app to deal with .tar files depending on your computer OS).
Inside the tar (it’s kind of like a zip file) you’ll find other .tar.gz files … with the name of each add-on…
If you unpack those, you’ll find the configuration in .json format, which is readable enough for you to configure again your add-ons as you reinstall them fresh…
R
I can confirm too.
I commented # the netatmo lines in configuration.yaml, I updated again, wrote down netatmo with the new configuration method and add it from integration, and all is now ok.
You were right. I made the upgrade yesterday and it broke a lot of stuff. Took me 3 hours to get everything working again. So yeah, better not skip too many releases, the issues are adding up.
Did it for me. Tnx!
WOW tried for so many days now and this worked!!
Have same problem. Now successfully upgrade to 0.105.3 by changing configure.yaml to just
netatmo:
client_id: <<your_client_id>>
client_secret: <<your_client_secret>>
Excellent! I can confirm this is the issue. Upgraded from old 0.100.3. Thank you for the info!
See you on the bitstream ! Alain
OK, so has anyone (without modifying anything) tried upgrading to the new 105.3 that arrived on the 10th (https://www.home-assistant.io/blog/2020/02/05/release-105/#release-01053---february-10), or OS3.10 (https://github.com/home-assistant/operating-system/releases/tag/3.10) ?
It also worked for me.
I deleted the lines concerning NETATMO, relaunched and the update worked.
Thank you for sharing.
I see that Valentine’s Day brought in 0.105.4, so can anyone confirm that all is well?
I don’t really want to have to deal with more bugs 
It workd for me too. Thx!
I still have the problem, but could update the system to 3.10, but not luck with ha aka core. However, I got a nice rollback back to 0.104.3. I disabled netatmo and most adding except ssh and samba beforehand and restart the Raspberry pi. It seems that core is completely restarted by looking at the logs but the supervisor thinks it’s not and therefore rolling back:
Thanks
~ $ ha su logs
20-02-17 19:47:03 INFO (MainThread) [hassio.homeassistant] Update Home Assistant to version 0.105.4
20-02-17 19:47:03 INFO (SyncWorker_12) [hassio.docker.interface] Update image homeassistant/raspberrypi4-homeassistant:0.104.3 to homeassistant/raspberrypi4-homeassistant:0.105.4
20-02-17 19:47:03 INFO (SyncWorker_12) [hassio.docker.interface] Pull image homeassistant/raspberrypi4-homeassistant tag 0.105.4.
20-02-17 19:49:20 INFO (SyncWorker_12) [hassio.docker.interface] Stop homeassistant application
20-02-17 19:49:32 INFO (SyncWorker_12) [hassio.docker.interface] Clean homeassistant application
20-02-17 19:49:33 INFO (SyncWorker_9) [hassio.docker.homeassistant] Start homeassistant homeassistant/raspberrypi4-homeassistant with version 0.105.4
20-02-17 19:49:48 INFO (MainThread) [hassio.homeassistant] Home Assistant pip installation in progress
20-02-17 19:50:28 INFO (MainThread) [hassio.homeassistant] Home Assistant pip installation done
20-02-17 19:50:33 INFO (MainThread) [hassio.homeassistant] Home Assistant pip installation in progress
20-02-17 19:50:56 INFO (MainThread) [hassio.host.info] Update local host information
20-02-17 19:50:56 INFO (MainThread) [hassio.utils.gdbus] Call org.freedesktop.DBus.Properties.GetAll on /org/freedesktop/hostname1
20-02-17 19:50:56 INFO (MainThread) [hassio.host.services] Update service information
20-02-17 19:50:56 INFO (MainThread) [hassio.utils.gdbus] Call org.freedesktop.systemd1.Manager.ListUnits on /org/freedesktop/systemd1
20-02-17 19:50:56 INFO (MainThread) [hassio.host.network] Update local network DNS information
20-02-17 19:50:56 INFO (MainThread) [hassio.utils.gdbus] Call org.freedesktop.DBus.Properties.GetAll on /org/freedesktop/NetworkManager/DnsManager
20-02-17 19:52:13 INFO (MainThread) [hassio.homeassistant] Home Assistant pip installation done
20-02-17 20:02:15 WARNING (MainThread) [hassio.homeassistant] Don't wait anymore of Home Assistant startup!
20-02-17 20:02:15 CRITICAL (MainThread) [hassio.homeassistant] HomeAssistant update fails -> rollback!
20-02-17 20:02:15 INFO (MainThread) [hassio.homeassistant] Update Home Assistant to version 0.104.3
20-02-17 20:02:15 INFO (SyncWorker_9) [hassio.docker.interface] Update image homeassistant/raspberrypi4-homeassistant:0.105.4 to homeassistant/raspberrypi4-homeassistant:0.104.3
20-02-17 20:02:15 INFO (SyncWorker_9) [hassio.docker.interface] Pull image homeassistant/raspberrypi4-homeassistant tag 0.104.3.
20-02-17 20:02:17 INFO (SyncWorker_9) [hassio.docker.interface] Stop homeassistant application
20-02-17 20:02:18 INFO (SyncWorker_9) [hassio.docker.interface] Clean homeassistant application
20-02-17 20:02:18 INFO (SyncWorker_15) [hassio.docker.homeassistant] Start homeassistant homeassistant/raspberrypi4-homeassistant with version 0.104.3
20-02-17 20:02:28 INFO (MainThread) [hassio.homeassistant] Home Assistant pip installation in progress
20-02-17 20:03:09 INFO (MainThread) [hassio.homeassistant] Home Assistant pip installation done
20-02-17 20:03:19 INFO (MainThread) [hassio.homeassistant] Home Assistant pip installation in progress
20-02-17 20:05:29 INFO (MainThread) [hassio.homeassistant] Home Assistant pip installation done
20-02-17 20:05:39 INFO (MainThread) [hassio.homeassistant] Detect a running Home Assistant instance
20-02-17 20:05:39 INFO (MainThread) [hassio.homeassistant] Successful run Home Assistant 0.104.3
20-02-17 20:05:39 INFO (SyncWorker_5) [hassio.docker.interface] Cleanup images: ['homeassistant/raspberrypi4-homeassistant:0.105.4']
I stopped the ESPHome add-on. Then I updated to 0.105.5 with success.
After the update I could run the ESPHome again
For all those interested! I was not using netatmo, but still had these issues. Surprisingly, adding the below code to my configuration.yaml and rebooting resolved my issues and I was able to update to 105.5! I’m completely confused why this was necessary, but hey, it worked!
netatmo:
client_id: dummy
client_secret: dummy
wow, you’re absolutely right. I commented out the Netatmo section before which wasn’t working, but adding the new config worked so I could finally upgade to 0.105.5 
However, I activated the Netatmo integration via Nabu Casa and have the cameras back, but they don’t work anymore 
and there is only 1 motion sensor per camera left and not the AI based ones detecting persons, cars etc
Had the same issue not being able to upgrade from 105.2 to 106.2
Commented out this line from my config and that did the trick for me.
#group: !include groups.yaml
Hope this helps.
Thanks,
I was able to upgrade 0.106.2 to 0.106.6 by commenting this line about groups.yaml. I’ll have to modify my automation to make sure I don’t have any reference to group.
Hi,
adding the “dummy” Netatmo config did the trick for me as well to update from 0.104.3 to 0.106.x. (Before adding it, updates failed all of the time…)
Now I am running 0.107.1.
I tried to remove my dummy Netatmo configuration, but without it Home Assistant is not starting up anymore. The logs do not provide any helpful information or errors and startup is stuck at
[homeassistant.setup] Setup of domain hassio took xx seconds.
When I add the dummy Netatmo configuration again, Home Assistant starts fine and logs continue to stream after “domain hassio”…
[homeassistant.setup] Setup of domain hassio took xx seconds.
homeassistant.bootstrap] Home Assistant initialized in xxs.
I am running on a RPI3b with Hassos 3.8 and Supervisor 209.
This is just kind of a cosmetic issue for me, but still I am wondering why this is the case.
Anybody able to help here?
Thanks!
Hi All,
I’m running Hass.io 98.5 on a 3B+. I want to update to the latest version 107.6 and after a lot of reading about updating, I haven’t found one about using the update capabilities from the browser interface. So I want to try doing it this way but the very first step has me confused.
When I go to the Hass.io tab Dashboard page, there are two choices to update 1) Home Assistant Core 0.107.6 AND 2) Operating System 3.12. I have no idea which one to do first and I’m afraid doing one without the other will get me into all kinds of trouble.
Can someone tell me if I only need to update Home Assistant core? I’m not running linux/docker installation, just the hass.io image.
Thanks for any insights before I wreck something.
Stay well, stay safe,
Hi, I have exactly the some issue, simply by a clean new installation of home assistant v.0.108.9. Without any installed add-ons or backup’s. Simply a new clean installation. I have tried this several times on different Raspberry’s (3, 3B+, 4) with different mSD-cards. Always with the some result. Every restart of home assistant (no Host restart!) takes more than 16 minutes. On top I get this error message:
2020-04-26 11:30:54 ERROR (MainThread) [aiohttp.server] Unhandled exception
Traceback (most recent call last):
File “/usr/local/lib/python3.7/site-packages/aiohttp/web_protocol.py”, line 461, in start
await prepare_meth(request)
File “/usr/local/lib/python3.7/site-packages/aiohttp/web_fileresponse.py”, line 224, in prepare
st = await loop.run_in_executor(None, filepath.stat)
File “/usr/local/lib/python3.7/concurrent/futures/thread.py”, line 57, in run
result = self.fn(*self.args, **self.kwargs)
File “/usr/local/lib/python3.7/pathlib.py”, line 1178, in stat
return self._accessor.stat(self)
FileNotFoundError: [Errno 2] No such file or directory: ‘/config/home-assistant.log’