0.113: Automations & Scripts, and even more performance!

[dedi]

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)

[heyepic (Matt)]

Figured it out - did a bunch of replacements. Thanks!

[jerobins (James Robinson)]

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.

[Mutt (Muttley)]

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

[marciogranzotto (Marcio Granzotto Rodrigues)]

It actually supports lights, the documentation wasn’t merged accidentally:

Update Bond documentation to include all applicable categories

[danmed (Dan Medhurst)]

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!

[eugene.prystupa]

Yes, it does poll the hub for state.

[marciogranzotto (Marcio Granzotto Rodrigues)]

Hey Eugene, engineer at Bond here, great work!
BTW, insted of pooling the state, you can use BPUP (Bond Push UDP Protocol). After establishing an connection, the Bond will push state updates. You can check the docs here: http://docs-local.appbond.com/#section/Bond-Push-UDP-Protocol-(BPUP)

Also I’m curious how your integration handles multiple Bonds and Smart By Bond devices, will be testing that shortly!

[taste (Marc)]

Big shout-out the full team. Great to see you make your release on time and with so good content. Every time my HA installations run more smoothly even the depreciated PI zero W in my motorhome
Keep up the good work!

[heartkingz]

Another brilliant release. Thanks to the entire team!

[chrismdann]

I do like the consolidated breaking changes. All these choices for automations now. Might be able to move a few node red automations back to HA.

[eugene.prystupa]

Hi Marcio and thanks. I am looking into BPUP.

The integration supports multiple hubs - you just need to run UI wizard once for each hub. I don’t own any SBB devices, so can’t tell - but it should work just fine if SBB devices are like an integrated Bond bridge and talk the same API.

[fintmu]

Awesome! I’ve really waited for some of these great improvements. Thanks to the whole dev team, you rock!

[synekvl (Vladimír Synek)]

May I ask for help or suggestion how to update HA. Since last update to 0.112.1 I get:

20-07-22 19:30:16 ERROR (SyncWorker_2) [supervisor.docker.interface] Can’t install homeassistant/raspberrypi3-homeassistant:0.113.0 -> 404 Client Error: Not Found (“no such image: homeassistant/raspberrypi3-homeassistant:0.113.0: No such image: homeassistant/raspberrypi3-homeassistant:0.113.0”).
20-07-22 19:30:16 WARNING (MainThread) [supervisor.homeassistant] Update Home Assistant image fails

Thanks
Vladimir

[Molodax (Alex)]

Tried to use repeat in scripts but get this:

Invalid config for [script]: [repeat] is an invalid option for [script]. Check: script->script->nextbus->repeat. (See /config/configuration.yaml, line 1614)

script.yaml

nextbus:
  alias: Bus To Work
  repeat:
    while:
      - condition: state
        entity_id: script.workroutine
        state: 'on'
      - condition: template
        value_template: '{{ (states.sensor.next_bus_work.state|int - states.sensor.next_bus_f.state|int) >= 15 }}'
      - condition: template
        value_template: '{{ (states.sensor.next_bus_work.state|int - states.sensor.next_bus_f.state|int) <= 35 }}'
      - condition: numeric_state
        entity_id: sensor.next_bus_f
        above: 5
    sequence:
      - service: script.turn_on
        entity_id: script.say
        data_template:
          variables:
            where: 'al_s_2nd_sonos_one'
            what: 'Next bus is departing...'
      - delay:
          minutes: 3

What could be wrong? It doesn’t work with script: !include scripts.yaml?

[cogneato]

Whenever you see 404 Client Error: Not Found (“no such image:... check for free space.

[123 (Taras)]

@danmed

20-07-22 18:20:28 WARNING (MainThread) [supervisor.homeassistant] Don’t wait anymore of Home Assistant startup!

Aside from the funky grammar, it sounds like the Supervisor is upset …

20-07-22 18:20:28 WARNING (MainThread) [supervisor.homeassistant] Too slow, not waiting anymore, I’m outta here!

[schoenof (Tony)]

I have the same issue as danmed…same exact logs…tried multiple times to upgrade…first time I have had a failure to upgrade…

[123 (Taras)]

@Molodax

Tried to use repeat in scripts but get this:

Invalid config for [script]: [repeat] is an invalid option for [script]. Check: script->script->nextbus->repeat. (See /config/configuration.yaml, line 1614)

Me too and probably because we both tried to follow the supplied examples … which aren’t complete scripts.

Insert a sequence: below alias: and then indent all remaining lines (starting with the line containing repeat).

nextbus:
  alias: Bus To Work
  sequence:
    repeat:
      while:
        - condition: state
          entity_id: script.workroutine
          state: 'on'
        - condition: template
          ... etc ...

That will pass Configuration Check.

FWIW, I posted a simple example here:

Add easier solution for loops in automations/scripts

Here is a simple example of how to use the new repeat feature in a script (introduced in 0.113). It repeats (loops) a sequence 5 times. The sequence simply increments counter.test then waits 2 seconds. #script: increment_by_5: sequence: repeat: count: 5 sequence: - service: counter.increment entity_id: counter.test - delay: '00:00:02' In an automation, you can call the script like this: action: service: script.increment_by_5 F…

[janssenjones]

Though I don’t see it mentioned anywhere in the release notes, the big fix for me is that the Honeywell Lyric T5 thermostat finally works through the Homekit integration. Setting the temp had been broken forever (I believe was it due to partial degree changes or something, but I can’t find that discussion now), but I can confirm it finally works. Woo hoo! All my components are now finally working!!

Thanks!
Janssen