Yup, just pointing out why Molodax’s example failed Config Check because the examples aren’t standalone scripts (i.e. more statements are needed to flesh them out).
It tripped me up. Fortunately, VS Code (with the Home Assistant extension) kept underlining repeat and then it dawned on me that I was creating a script that didn’t contain a leading sequence: statement and there’s the problem.
I am having similar issues updating to 0.113.0 - My HACS integrations are uptodate per @ danmed suggestion. Here is my log:
20-07-22 21:11:46 INFO (SyncWorker_4) [supervisor.docker.interface] Pull image homeassistant/raspberrypi4-homeassistant tag 0.113.0.
20-07-22 21:11:59 INFO (SyncWorker_4) [supervisor.docker.interface] Stop homeassistant application
20-07-22 21:12:20 INFO (SyncWorker_4) [supervisor.docker.interface] Clean homeassistant application
20-07-22 21:12:20 INFO (MainThread) [supervisor.homeassistant] Update pulse/client.config: /data/tmp/homeassistant_pulse
20-07-22 21:12:27 INFO (SyncWorker_7) [supervisor.docker.homeassistant] Start homeassistant homeassistant/raspberrypi4-homeassistant with version 0.113.0
20-07-22 21:12:43 INFO (MainThread) [supervisor.homeassistant] Home Assistant pip installation in progress
20-07-22 21:13:00 INFO (MainThread) [supervisor.homeassistant] Home Assistant pip installation done
20-07-22 21:13:05 INFO (MainThread) [supervisor.homeassistant] Home Assistant pip installation in progress
20-07-22 21:13:25 INFO (MainThread) [supervisor.updater] Fetch update data from https://version.home-assistant.io/stable.json
20-07-22 21:15:58 INFO (MainThread) [supervisor.homeassistant] Home Assistant pip installation done
20-07-22 21:20:05 INFO (MainThread) [supervisor.host.info] Update local host information
20-07-22 21:20:05 INFO (MainThread) [supervisor.utils.gdbus] Call org.freedesktop.DBus.Properties.GetAll on /org/freedesktop/hostname1
20-07-22 21:20:06 INFO (MainThread) [supervisor.host.services] Update service information
20-07-22 21:20:06 INFO (MainThread) [supervisor.utils.gdbus] Call org.freedesktop.systemd1.Manager.ListUnits on /org/freedesktop/systemd1
20-07-22 21:20:06 INFO (MainThread) [supervisor.host.network] Update local network DNS information
20-07-22 21:20:06 INFO (MainThread) [supervisor.utils.gdbus] Call org.freedesktop.DBus.Properties.GetAll on /org/freedesktop/NetworkManager/DnsManager
20-07-22 21:20:06 INFO (MainThread) [supervisor.host.sound] Update PulseAudio information
20-07-22 21:26:01 WARNING (MainThread) [supervisor.homeassistant] Don’t wait anymore of Home Assistant startup!
20-07-22 21:26:01 CRITICAL (MainThread) [supervisor.homeassistant] HomeAssistant update fails -> rollback!
20-07-22 21:26:01 INFO (MainThread) [supervisor.homeassistant] Update Home Assistant to version 0.112.4
20-07-22 21:26:01 INFO (SyncWorker_4) [supervisor.docker.interface] Update image homeassistant/raspberrypi4-homeassistant:0.113.0 to homeassistant/raspberrypi4-homeassistant:0.112.4
20-07-22 21:26:01 INFO (SyncWorker_4) [supervisor.docker.interface] Pull image homeassistant/raspberrypi4-homeassistant tag 0.112.4.
20-07-22 21:26:02 INFO (SyncWorker_4) [supervisor.docker.interface] Stop homeassistant application
20-07-22 21:26:12 INFO (SyncWorker_4) [supervisor.docker.interface] Clean homeassistant application
20-07-22 21:26:12 INFO (MainThread) [supervisor.homeassistant] Update pulse/client.config: /data/tmp/homeassistant_pulse
20-07-22 21:26:14 INFO (SyncWorker_3) [supervisor.docker.homeassistant] Start homeassistant homeassistant/raspberrypi4-homeassistant with version 0.112.4
Upgraded to 113.0 but my logitech harmony is broken?
my current activity is ALWAYS powerOff , doesnt detect the correct state anymore
turning on activities still working …
edit: seems after restart HA again, it works again
awesome update, and welcome to new automating and scripting by @pnbruckner. Phil, amazing. got a short list of modes to re-edit (after the test run) and all went buttery smooth! Magic all over. And quick! again, @bdraco worked wonders.
Only thing for now I can see is a newly discovered Plugwise integration, while it already is configured. Is this a bug? or do we need to delete the formerly discovered integration first…
Upgraded to 113.0 popup cards in lovelace (browser_mod) stopped working.
Hi,
I lost my cover just after update my HA. My dashboard show me entity unavailable. You can see below my config code? Thx for support.
rfxtrx:
device: /dev/serial/by-id/usb-RFXCOM_RFXtrx433XL_DO332IY6-if00-port0
cover:
platform: rfxtrx
automatic_add: true
devices:
“071a0000010A0202”: # RFY
name: Séjour
“071a0000020A0404”: # RFY
name: SàM
“071a00030A0909”: # RFY
name: Cuisine
Smooth update and no problems to report so far, well done 
This looks like such an awesome release. I’ve spent a inordinate amount of time coding around some of the nuances in scripts and automation to handle multiple recurring trigger, I can’t wait to try so some of the improved features.
Many thanks guys, you just keep going from strength to strength.
An issue has been raised on the browser_mod github page.
@lisegra same problem here. Yeelight auto discovery is broken for me too.
I added them manually as a workaround to the config.
Updated from the Android app 300 Miles from home. Well done team
Same here. I had the Bond custom component installed through HACS, so I uninstalled it from there and restarted Home Assistant. I was then able to utilize the new built-in integrations setup method.
That’s a typo in the release announcement, probably because originally it was going to be queue but was changed to queued before being released. I believe the docs are correct.
@frenck, sorry about that!
@frenck image size considerably reduced to ~330mb in 0.113 from ~420mb in 0.112. wondering what changed. thanks.
This build breaks all my Hue integrations; the log is filled with something like “light does not exists” and if i click it on it in HA, it asks if i want to remove the node.
So far i had to roll-back to 0.112.4.
I disabled the tensorflow stuff and the upgrade to 0.113 finished now…re-enabling tensorflow after 113.0 upgrade results in some errors and hangs the HA startup again…seems there is some issue with 113 and tensorflow
What will happen when we overreach max? Latest one will be ignored or newest one will be finished?
Hmmm, I am not using Tensorflow but Amazon Rekognition. Will try disabling.
