Hassio upgrade from 0.104.3 to 0.105 fail

Installation Home Assistant OS
22

I have no netatmo devices, but I had to add this bloc to configuration.yaml to enable startup :slight_smile:

netatmo:
  client_id: dummy
  client_secret: dummy

So it’s solved for me

23

Are you saying that you had no netatmo devices and added this to the configuration yaml file fixed your not issue?

24

i have much trouble with this relese
because is impossible for me make thi upgrade , i make a new installation directly with 105, but. in this case i have much trouble to configure remote access because take over one hour for go online, and if i make any change in yaml al restart non riesce a partire piu.

25

Are there any updates? I’m still having these exact same issues… Don’t have netatmo running or anything, recently did a fresh install of 104.3, so not looking to do it again for 105.5…

26

Holy shit, this actually worked. I have no netatmo devices, but adding this code to my configuration.yaml, rebooting, and then performing the update actually got me to 105.5!

27

Worked for me too.
I have a netatmo weather station. I had to change the configuration.yaml as described, restarted HA and then the upgrade worked! Re-enable netatmo via integrations and everything seems to run fine.

28

I have been playing around for several weeks and finally got .104.3 updated to .105.5. I’ll list my steps to hopefully help others.

  1. Cloned SD card. This way it is very easy to go back.
  2. Updated to .105.5
  3. Lovelace fails to load but Samba and SSH work.
  4. Removed all my custom setting except my duck dns from configuration.yaml. Basically just the default plus the http address.
  5. Deleted the lovelace file.
  6. Restarted
  7. Lovelace loaded.
  8. Added sections of my configuration.yaml file one at a time, saved and restarted.
    When all configuration restored started on the lovelace
  9. Added all the community integrations Rebooted.
  10. Slowly added cards back in. Backing up lovelace and rebooting after each. This was a lesson learned as I added something wrong and after the reboot, Lovelace failed loading again.

I believe my error is improper formatting somewhere in Lovelace. I have a logger setting for hacs and all my custom cards and no errors are showing.

I didn’t change anything and it didn’t cause an issue in the past, but something does now. Maybe time to go to yaml for lovelace. To me the visual in the raw editor, the card editor and Json is inconsistent and confusing and leads to errors.

Hope this can help others.