Automation to update tablet sensors runs with step by step, but fails if using this automation

Configuration
1

I have Google voice integration through Nabu Casa. In the morning, I say “Hey Google, good morning”, and Google:

  • Toggles OFF a Home Assistant binary sensor “Day-Nite Mode”
  • Turns off DND on phone
  • Adjusts media volume on Google Nest Hub
  • Tells me about the weather
  • Tells me about the calendar

All that is done through the Google Home app.

Meanwhile, there is a Home Assistant automation below that when the binary toggle Day-Nite Mode turns off, it opens the blinds and turns the Lenovo tablet screen and screen saver and motion detector back on. The automation runs, as it opens the blinds, but the Lenovo stays in its evening state.

When I click each action manually in the automation editor to “Run”, it properly changes the tablet settings without delay.

So why is it not completing the automation and turning the tablet sensors back on properly?

alias: Toggle Day-Night Mode Off to Daytime
description: Toggle Day-Night Mode Off to Morning Actions, blinds
trigger:
  - platform: state
    entity_id:
      - input_boolean.day_night_mode
    from: "on"
    to: "off"
    for:
      hours: 0
      minutes: 0
      seconds: 3
condition: []
action:
  - service: cover.open_cover
    metadata: {}
    data: {}
    target:
      entity_id: cover.blinds_master_bedroom
  - delay:
      seconds: 30
  - service: cover.open_cover
    metadata: {}
    data: {}
    target:
      entity_id: cover.blinds_living_room
  - service: input_boolean.turn_off
    target:
      entity_id:
        - input_boolean.toggle_night_light_mode
        - input_boolean.toggle_morning_music_played
    data: {}
  - delay:
      hours: 0
      minutes: 0
      seconds: 30
      milliseconds: 0
  - type: turn_on
    device_id: a964faf40b29d5ed0f52dd8421f42719
    entity_id: 60d6f4b9fb435ad7a876c41732b99eff
    domain: switch
  - delay:
      hours: 0
      minutes: 0
      seconds: 5
      milliseconds: 0
  - type: turn_on
    device_id: a964faf40b29d5ed0f52dd8421f42719
    entity_id: dc99326da75ed9cdfa1f880f8e9c20ae
    domain: switch
  - delay:
      hours: 0
      minutes: 0
      seconds: 5
      milliseconds: 0
  - type: turn_on
    device_id: a964faf40b29d5ed0f52dd8421f42719
    entity_id: 8ede690fe88bc6b075fb6b15658875b2
    domain: switch
  - delay:
      hours: 0
      minutes: 0
      seconds: 5
      milliseconds: 0
  - device_id: a964faf40b29d5ed0f52dd8421f42719
    domain: number
    entity_id: de4fcc54de29df95ebaefa04e747e5ec
    type: set_value
    value: 175
  - delay:
      hours: 0
      minutes: 0
      seconds: 5
      milliseconds: 0
  - device_id: a964faf40b29d5ed0f52dd8421f42719
    domain: number
    entity_id: b95f20badac5431fc8f7f155898b22de
    type: set_value
    value: 175
mode: single
2

Is the Lenovo the bit with device ids? You might get more insight into what’s going on if you use entity ids. It’s certainly hard for anyone else to comment at the moment.

3

Changed them to entity ID’s, works great. Thank you. That was sloppy of me.

1 Like