The occupant of one of the bedrooms with a ventbot sometimes wants to ventbot to operate and sometimes not. When they don't want it, on my advice they simply unplug the ventbot power from the wall. That worked fine when each ventbot operated independently. Under ecobee control, though, it triggered a problem. It took me a while to notice this. I was randomly perusing my Home Assistant dashboards and saw that ventbot disabled, which was not surprising. But two of the other ventbots were on and two were off. Hmmm.

You saw my script for activating the ventbot in my previous project log. It calls a service for each ventbot. The problem is that it calls them in sequence, and the script stops with an error when it tries to call the ventbot that is offline. The fix is pretty simple. Instead of calling the services in sequence, I now call them in parallel. An error is logged for the offline ventbot, but it doesn't stop the calls to the others.

Here's is the revised activation script:

alias: Ventbots activate!
sequence:
  - parallel:
      - service: esphome.ventbot_red_set_inout_neutral_zone_and_hold
        data:
          in_neutral_zone: false
          duration_seconds: 500000
      - service: esphome.ventbot_orange_set_inout_neutral_zone_and_hold
        data:
          in_neutral_zone: false
          duration_seconds: 500000
      - service: esphome.ventbot_yellow_set_inout_neutral_zone_and_hold
        data:
          in_neutral_zone: false
          duration_seconds: 500000
      - service: esphome.ventbot_green_set_inout_neutral_zone_and_hold
        data:
          in_neutral_zone: false
          duration_seconds: 500000
      - service: esphome.ventbot_blue_set_inout_neutral_zone_and_hold
        data:
          in_neutral_zone: false
          duration_seconds: 500000
mode: restart
icon: mdi:fan