You guys are making it very difficult to resist .0 releases while I am 5000km away from home.
10 Likes
Another awesome looking release, looking forward to getting it installed! Iām glad to see automations getting a lot more āpower tools.ā Previously, you had to go to AppDaemon and Node-Red to use some of the more advanced logical constructs, and while those are fantastic tools, they arenāt for everyone. Having more of these options built right in by default is going to open up a lot of possibilities for newer users and those who might not consider themselves programmers.
Yeah, this a nice one for me too. Iāve had a longstanding to-do item to create a convoluted process in AppDaemon to manually update the sensor at the time the harmony service call was made. Glad I procrastinated and donāt have to do it now. 
1 Like
I am curious how the bond intergration works. I have so many scripts controlling my bond right now. I notice it doesnāt include lights in description which are attached to the fans. I also wonder if it polls for state as right now I am doing that with booleans.
I get that some automations may be easier to implement in HA than in Node-RED, but the latter is much more powerful and once it seems that every new update to automations in HA is just playing catch-up with NodeRED. I canāt think of one thing that HA can do that Node-RED canāt, but canāt say the same the other way around.
My point was about spending the effort developing something when thereās a complementary platform that can already handle all automations. But anyway, Iām glad automations are getting some love.
Not if you have a handle on jinja.
3 Likes
Well it cannot do device automations for starters 
4 Likes
sure, but the same end-result can be achieved in other ways. You strike me as a Node-RED fan too so thereās no point in arguing about it. If you guys think spending cycles developing and enhancing automations is worth it then you must be right.
I love both platforms and I want to thank you for the work you do. 
2 Likes
Thanks for this release, it really is fantastic. 112 was as well. Lots of really great work that leads to real improvements.
The new automation/script issues have significantly allowed me to cut down on lines of yaml which helps maintenance, fragility, and the all important WAC. I may get a nice steak and XX on Saturday night thanks to the dev team 
Hi, Just upgraded. Cool features introduced with this release, but please help me to find the repeat function. I cannot see it under āactionā. Thanks
Edit: from the release notes
Before we start with this all, please note, that the
actionpart of an automation is a scriptsequence.
1 Like
Great update devs! Only thing I noticed is I had the custom theme Google Dark Theme for the backend and now everything is appearing as white. Anyone else running this theme and know how to fix?
Ah ok, thanks! 
Read the breaking changes.
The theme variable
paper-card-background-coloris removed. You can useha-card-backgroundorcard-background-coloras a replacement.In general, all variables that start with
paperwill be removed at some point.
4 Likes
Thanks for this update. All went well.
Will it be possible to use repeat or choose in the frontend soon?
I also noticed that you canāt use subseconds in the frontend yet. (Edit: the scripts tab does not even load anymore if there is a script using the new milliseconds delay)
Figured it out - did a bunch of replacements. Thanks!
I donāt understand #36609 and the breaking change.
MQTT expires_after would normally expire the state_topic or sensor value.
New behavior is marking the sensor unavailable even when the availability_topic is clearly set. I would suggest that ignoring the availability topic is not the correct or expected behavior.
That is a good point and a salient reminder, do you know if there is a resource listing the deprecated (or soon to be) and their replacements ?
(a link in this blog thread would help many, including me 
or did I miss it in the OP ? Iāll just check ā¦)
Nope, it must be hiding
1 Like
It actually supports lights, the documentation wasnāt merged accidentally:
1 Like
Iām getting an update fail in HASSOS
20-07-22 18:07:57 INFO (MainThread) [supervisor.homeassistant] Update Home Assistant to version 0.113.0
20-07-22 18:07:57 INFO (SyncWorker_1) [supervisor.docker.interface] Update image homeassistant/qemux86-64-homeassistant:0.112.4 to homeassistant/qemux86-64-homeassistant:0.113.0
20-07-22 18:07:57 INFO (SyncWorker_1) [supervisor.docker.interface] Pull image homeassistant/qemux86-64-homeassistant tag 0.113.0.
20-07-22 18:08:46 INFO (SyncWorker_1) [supervisor.docker.interface] Stop homeassistant application
20-07-22 18:09:36 INFO (SyncWorker_1) [supervisor.docker.interface] Clean homeassistant application
20-07-22 18:09:36 INFO (MainThread) [supervisor.homeassistant] Update pulse/client.config: /data/tmp/homeassistant_pulse
20-07-22 18:09:36 INFO (SyncWorker_4) [supervisor.docker.homeassistant] Start homeassistant homeassistant/qemux86-64-homeassistant with version 0.113.0
20-07-22 18:09:46 INFO (MainThread) [supervisor.homeassistant] Home Assistant pip installation in progress
20-07-22 18:10:26 INFO (MainThread) [supervisor.homeassistant] Home Assistant pip installation done
20-07-22 18:20:28 WARNING (MainThread) [supervisor.homeassistant] Don't wait anymore of Home Assistant startup!
20-07-22 18:20:28 CRITICAL (MainThread) [supervisor.homeassistant] HomeAssistant update fails -> rollback!
2 Likes
Yes, it does poll the hub for state.
1 Like