I have this problem. HomeAssistant update fails -> rollback! can anyone help?From 0.109.3 to 0.110.3.
1 Like
What errors do you get in your supervisor log ?
20-05-27 13:44:17 CRITICAL (MainThread) [supervisor.homeassistant] HomeAssistant update fails -> rollback!
Nothing before in the log ?
No other error.only info. and this warning 20-05-27 15:17:05 WARNING (MainThread) [supervisor.homeassistant] Don’t wait anymore of Home Assistant startup!
Can you post the whole supervisor log ? The reason is normally somewhere there.
EDIT
Failed to load cookie file from cookie: No such file or directory
20-05-27 14:26:10 INFO (MainThread) [supervisor.homeassistant] Update Home Assistant to version 0.110.3
20-05-27 14:26:10 INFO (SyncWorker_1) [supervisor.docker.interface] Update image homeassistant/intel-nuc-homeassistant:0.109.3 to homeassistant/intel-nuc-homeassistant:0.110.3
20-05-27 14:26:10 INFO (SyncWorker_1) [supervisor.docker.interface] Pull image homeassistant/intel-nuc-homeassistant tag 0.110.3.
20-05-27 14:26:38 INFO (SyncWorker_1) [supervisor.docker.interface] Stop homeassistant application
20-05-27 14:27:39 INFO (SyncWorker_1) [supervisor.docker.interface] Clean homeassistant application
20-05-27 14:27:39 INFO (MainThread) [supervisor.homeassistant] Update pulse/client.config: /data/tmp/homeassistant_pulse
20-05-27 14:27:39 INFO (SyncWorker_11) [supervisor.docker.homeassistant] Start homeassistant homeassistant/intel-nuc-homeassistant with version 0.110.3
20-05-27 14:27:49 INFO (MainThread) [supervisor.homeassistant] Home Assistant pip installation in progress
20-05-27 14:28:59 INFO (MainThread) [supervisor.homeassistant] Home Assistant pip installation done
20-05-27 14:39:01 WARNING (MainThread) [supervisor.homeassistant] Don't wait anymore of Home Assistant startup!
20-05-27 14:39:01 CRITICAL (MainThread) [supervisor.homeassistant] HomeAssistant update fails -> rollback!
20-05-27 14:39:01 INFO (MainThread) [supervisor.homeassistant] Update Home Assistant to version 0.109.3
20-05-27 14:39:01 INFO (SyncWorker_16) [supervisor.docker.interface] Update image homeassistant/intel-nuc-homeassistant:0.110.3 to homeassistant/intel-nuc-homeassistant:0.109.3
20-05-27 14:39:01 INFO (SyncWorker_16) [supervisor.docker.interface] Pull image homeassistant/intel-nuc-homeassistant tag 0.109.3.
20-05-27 14:39:02 INFO (SyncWorker_16) [supervisor.docker.interface] Stop homeassistant application
20-05-27 14:39:06 INFO (SyncWorker_16) [supervisor.docker.interface] Clean homeassistant application
20-05-27 14:39:06 INFO (MainThread) [supervisor.homeassistant] Update pulse/client.config: /data/tmp/homeassistant_pulse
20-05-27 14:39:06 INFO (SyncWorker_10) [supervisor.docker.homeassistant] Start homeassistant homeassistant/intel-nuc-homeassistant with version 0.109.3
20-05-27 14:39:21 INFO (MainThread) [supervisor.homeassistant] Home Assistant pip installation in progress
20-05-27 14:40:22 INFO (MainThread) [supervisor.homeassistant] Home Assistant pip installation done
20-05-27 14:40:42 INFO (MainThread) [supervisor.homeassistant] Detect a running Home Assistant instance
20-05-27 14:40:42 INFO (MainThread) [supervisor.homeassistant] Successful run Home Assistant 0.109.3
20-05-27 14:40:42 INFO (SyncWorker_17) [supervisor.docker.interface] Cleanup images: ['homeassistant/intel-nuc-homeassistant:0.110.3']
20-05-27 14:42:07 INFO (MainThread) [supervisor.homeassistant] Updated Home Assistant API token ```Ok, I don’t see a reason immediately. Do you have a SSH server installed ? If so, SSH in, and issue these commands :
ha core stop
ha core update --version 0.110.3
ha core start
1 Like
Just a little ‘meta’ about markdown syntax.
If you mark text as a code-block using triple backquotes but don’t want the forum’s default formatting, you can append the desired format at the end of the triple backquotes.
For example, this:
produces this:
ha core stop
ha core update --version 0.110.3
Notice that no part of the result is displayed as a comment (and no key-words are emphasized).
5 Likes
Can
someone share how to set these options in config.yaml?
Are they put in place of base_url?
What you see is what you are supposed to do in configuration.yaml 
1 Like
Hi, I use both “(Xiaomi) Vacuum Card” and “Lovelace Xiaomi Vacuum Map Card” from HACS and are both broken (both with 110.0 and 110.3). Has anybody else the same problem?
From the JS log it appears that the object “this.stateObj” no longer exists, how is it possible to fix it?
Apart from this, the increase in speed is terrific!
Thank you
Edit2: sorry guys, it turned out that I actually had a network issue in my LAN, could not ping the vacuum and I wasn’t suspecting it because the Xiaomi app which works through the internet was working. After a reboot of the router everything went back to normal, I thought it had to do with the update because it happened right after the upgrade. So nothing is wrong with xiaomi vacuum, great update for the UI speedup!
Thank you!
1 Like
Neither has had a commit to their repositories since January and February respectively. There have been significant changes to some gui element handling in 0.110 (particularly icons). I suggest you post in their respective github repo issue trackers.
as a paying customer I shared the details and my findings already in March with the support and I waited patiently since then. The netatmo cameras worked fine before the new integration.
I have no idea what you are talking about.
you don’t pay for support for HA
3 Likes
anyone seeking to use custom-ui under HA 110+, please see this dedicated repo I made.
Be gentle, it is rudimentary. Functional though 
2 Likes
I’m talking about Nabu Casa aka Home Assistant Cloud and their support: https://www.nabucasa.com/support/
With the new Netatmo integration under /config/integrations you have two ways to authenticate via Configuration.yaml or Home Assistant Cloud. Both are not working for me
But you are aware that one has nothing to do with the other, right?
