Updater runs once per day.
Just upgraded from .109.4 -> .110.4 with zero issues.
Updated the internal_url and external_url before upgrading, fwiw - also ran the ‘Check Home Assistant configuration’ add-on first and showed no errors.
Nice to have multiple Rokus combined into a single integration.and love the speed improvements.
Thanks for another great release!
2 Likes
Even with this, a rollback is been done…someone has any other ideas?
20-05-31 12:26:27 INFO (MainThread) [supervisor.api.security] /core/stop access from core_ssh
20-05-31 12:26:27 INFO (SyncWorker_13) [supervisor.docker.interface] Stop homeassistant application
20-05-31 12:27:42 WARNING (MainThread) [supervisor.misc.tasks] Watchdog found a problem with Home Assistant Docker!
20-05-31 12:27:42 INFO (SyncWorker_3) [supervisor.docker.interface] Start homeassistant/raspberrypi3-64-homeassistant
20-05-31 12:29:23 INFO (MainThread) [supervisor.homeassistant] Detect a running Home Assistant instance
20-05-31 12:31:13 INFO (MainThread) [supervisor.api.security] /core/update access from core_ssh
20-05-31 12:31:13 INFO (MainThread) [supervisor.homeassistant] Update Home Assistant to version 0.110.3
20-05-31 12:31:13 INFO (SyncWorker_11) [supervisor.docker.interface] Update image homeassistant/raspberrypi3-64-homeassistant:0.109.6 to homeassistant/raspberrypi3-64-homeassistant:0.110.3
20-05-31 12:31:13 INFO (SyncWorker_11) [supervisor.docker.interface] Pull image homeassistant/raspberrypi3-64-homeassistant tag 0.110.3.
20-05-31 12:36:03 INFO (SyncWorker_11) [supervisor.docker.interface] Stop homeassistant application
20-05-31 12:37:06 INFO (SyncWorker_11) [supervisor.docker.interface] Clean homeassistant application
20-05-31 12:37:06 INFO (MainThread) [supervisor.homeassistant] Update pulse/client.config: /data/tmp/homeassistant_pulse
20-05-31 12:37:08 INFO (SyncWorker_14) [supervisor.docker.homeassistant] Start homeassistant homeassistant/raspberrypi3-64-homeassistant with version 0.110.3
20-05-31 12:37:43 INFO (MainThread) [supervisor.homeassistant] Home Assistant pip installation in progress
20-05-31 12:38:38 INFO (MainThread) [supervisor.homeassistant] Home Assistant pip installation done
20-05-31 12:47:00 INFO (MainThread) [supervisor.updater] Fetch update data from https://version.home-assistant.io/stable.json
20-05-31 12:48:41 WARNING (MainThread) [supervisor.homeassistant] Don't wait anymore of Home Assistant startup!
20-05-31 12:48:41 CRITICAL (MainThread) [supervisor.homeassistant] HomeAssistant update fails -> rollback!
20-05-31 12:48:41 INFO (MainThread) [supervisor.homeassistant] Update Home Assistant to version 0.109.6
20-05-31 12:48:41 INFO (SyncWorker_15) [supervisor.docker.interface] Update image homeassistant/raspberrypi3-64-homeassistant:0.110.3 to homeassistant/raspberrypi3-64-homeassistant:0.109.6
20-05-31 12:48:41 INFO (SyncWorker_15) [supervisor.docker.interface] Pull image homeassistant/raspberrypi3-64-homeassistant tag 0.109.6.
20-05-31 12:48:43 INFO (SyncWorker_15) [supervisor.docker.interface] Stop homeassistant application
20-05-31 12:48:48 INFO (SyncWorker_15) [supervisor.docker.interface] Clean homeassistant application
20-05-31 12:48:48 INFO (MainThread) [supervisor.homeassistant] Update pulse/client.config: /data/tmp/homeassistant_pulse
20-05-31 12:48:49 INFO (SyncWorker_8) [supervisor.docker.homeassistant] Start homeassistant homeassistant/raspberrypi3-64-homeassistant with version 0.109.6
20-05-31 12:49:19 INFO (MainThread) [supervisor.homeassistant] Home Assistant pip installation in progress
20-05-31 12:50:20 INFO (MainThread) [supervisor.homeassistant] Home Assistant pip installation done
20-05-31 12:51:30 INFO (MainThread) [supervisor.homeassistant] Detect a running Home Assistant instance
20-05-31 12:51:30 INFO (MainThread) [supervisor.homeassistant] Successful run Home Assistant 0.109.6
20-05-31 12:51:30 INFO (SyncWorker_4) [supervisor.docker.interface] Cleanup images: ['homeassistant/raspberrypi3-64-homeassistant:0.110.3']
And, WOW, the OS even resizes the filesystems automatically, now?
I think I had to do this manually, the last time around.
What’s in HA log when 0.110.3 starts?
Has anyone managed to successfully integrate Agent DVR yet?
I’m not having any luck!
Where can i find this?
That’s the question of the day! 
As a venv user with --log-rotate-days option i would simply look at the home-assistant.log file.
I tried to replicate this on my VBox HassOS.
Install the SSH & Web Terminal Addon, disable protection mode.
Open up two SSH Sessions, don’t use the Web Terminal, use another ssh client like putty.
In the first terminal start
docker logs -f hassio_supervisor
this will show the log of the supervisor
In the second one only type (don’t press Enter at the moment)
docker logs -f homeassistant
Now start the HA Update.
Watch the supervisor log in the first terminal and when it comes to
20-05-31 12:37:08 INFO (SyncWorker_14) [supervisor.docker.homeassistant] Start homeassistant homeassistant/raspberrypi3-64-homeassistant with version 0.110.3
Press Enter in the second terminal to see the startup log of 0.110.x
Hope that helps and good luck! 
I have manage to resolve my issue by providing base_url in the tts config.
Hello Everybody,
I have a new multimode xiaomi gateway and it is working fine with the homekit integration but the Aqara motion sensor does not report the illuminance. Do you know somebody what is the solution?
Thank you!
think I checked the full thread here, so forgive me if I missed it…
Very happy with the ‘not’ condition in automations, was a very much anticipated feature we now have. thanks Frenck.
condition:
condition: not
conditions:
entity_id: alarm_control_panel.home_alarm
state: disarmed
still this is a somewhat convoluted way of writing this, and I would hope we could have a state_not, or not_state variant of that?
condition:
condition: state
entity_id: alarm_control_panel.home_alarm
not_state: disarmed
Would this be on the horizon yet, or would a FR be necessary for this … 
1 Like
Over the last two weeks I’ve tried 0.110.0 to 0.110.5 and all of them appear to start Core (on Docker) but fail to open port 8123 for GUI. Finally I put some time into it today and determined that removing my ONVIF camera definition from my configuration.yaml allows the new instance to start up properly. Just FYI in case someone is struggling with the same issue of this new version of HomeAssistant not starting. Good luck.
1 Like
I’m having this same issue. Was it ever resolved by the devs? did you find a way to get the other onvif cameras set up?
Thanks!
Doing it with the not condition like this probably makes it more flexible, as you could do things like:
condition:
condition: not
conditions:
- condition: or
conditions:
- condition: state
entity_id: sensor.my_sensor
state: 'state1'
- condition: state
entity_id: sensor.my_sensor
state: 'state2'
Which would pass if that sensor had any other state than ‘state1’ or ‘state2’. With not_state you could probably do something like:
condition:
condition: and
conditions:
- condition: state
entity_id: sensor.my_sensor
not_state: 'state1'
- condition: state
entity_id: sensor.my_sensor
not_state: 'state2'
but, at least for me, I find the first one easier to follow the logic.
Your last example could be written like:
condition:
- condition: state
entity_id: sensor.my_sensor
not_state: 'state1'
- condition: state
entity_id: sensor.my_sensor
not_state: 'state2'
Which is way preferable imho… and much easier to read (to me)
I’d like it to replace my current template conditions, to be more efficient.
Dont know, it works, so I just ignored the error that occurred when setting it up.
After the setup all was fine.
Why is 110.6 out with no release notes?
2 Likes
Probably wasn’t worth someone’s time for one fix. https://github.com/home-assistant/core/releases/tag/0.110.6
could be but its great its there now, i feel better
Has anyone successfully set up Onvif with Reolink cameras? I get my Main and Sub streams just fine but don’t see any sensors for motion or anything else.