Garage Door Automation Causing Closed Status Issues

Configuration
,
1

I don’t know when(date-wise) this issue started happening, but I have been having issues with a garage door automation and just now figured out a correlation.

I am using a z-wave relay and z-wave tilt sensor to handle the control and status of our garage door(configured as template cover).

I have an automation set up that sends us notifications of when the garage door is opened and or closed, I also have it send a notification if the door was left open for 15 minutes.

Whenever we open and close the door using the garage wall button(which is wired to the relay as an input), we have no issues of the door shutting and updating its status.

I have a couple of automations that rely on either an NFC tag, or ESP8266s that will automatically close the door. If we scan the NFC tag with our phones, it’ll close, or open depending on the state.
The ESP8266s live in our cars, if the signal strength on those falls below a threshold, the door closes(or opens if it reconnects).

For whatever reason, the automations with the NFC tag and ESP8266s are stopping the tilt sensor from reporting its status correctly, every time.

What in my automations would be causing this?

Info: Latest HA-OS on raspberry Pi 4 - core-2021.12.9, supervisor-2021.12.2, Zooz ZST10 - Z-Wave JS Addon: 0.1.52
Automations:

NFC:

alias: Tag Garage Door is scanned
description: ''
trigger:
  - platform: tag
    tag_id: secret
    id: Tag Scanned
condition: []
action:
  - choose:
      - conditions:
          - condition: trigger
            id: Tag Scanned
          - condition: state
            entity_id: cover.garage_door
            state: closed
        sequence:
          - service: cover.open_cover
            target:
              entity_id: cover.garage_door
          - service: lock.unlock
            target:
              entity_id: lock.house_garage_door_lock
          - wait_for_trigger:
              - platform: state
                entity_id: binary_sensor.house_garage_door
                to: 'on'
          - service: cover.close_cover
            target:
              entity_id: cover.garage_door
      - conditions:
          - condition: trigger
            id: Tag Scanned
          - condition: state
            entity_id: cover.garage_door
            state: open
        sequence:
          - service: cover.close_cover
            target:
              entity_id: cover.garage_door
          - service: lock.lock
            target:
              entity_id:
                - lock.front_door_lock
                - lock.house_garage_door_lock
    default: []
mode: single

ESP8266:

alias: Garage Door - Ceru
description: Operating Garage Door Based on Cerus State
trigger:
  - type: connected
    platform: device
    device_id: d9b41032a86c66990a5c15c6fad6aa4e
    entity_id: binary_sensor.ceru_status
    domain: binary_sensor
    id: ceru_connected
condition: []
action:
  - choose:
      - conditions:
          - condition: and
            conditions:
              - condition: trigger
                id: ceru_connected
              - condition: state
                entity_id: cover.garage_door
                state: open
        sequence:
          - wait_for_trigger:
              - type: signal_strength
                platform: device
                device_id: d9b41032a86c66990a5c15c6fad6aa4e
                entity_id: sensor.ceru_signal_sensor
                domain: sensor
                below: -68
            continue_on_timeout: false
          - service: cover.close_cover
            target:
              entity_id: cover.garage_door
          - service: lock.lock
            target:
              entity_id: lock.house_garage_door_lock
      - conditions:
          - condition: and
            conditions:
              - condition: trigger
                id: ceru_connected
              - condition: state
                entity_id: cover.garage_door
                state: closed
        sequence:
          - service: cover.open_cover
            target:
              entity_id: cover.garage_door
          - service: lock.unlock
            target:
              entity_id: lock.house_garage_door_lock
            data:
              code: 'secret'
          - wait_for_trigger:
              - platform: state
                entity_id: binary_sensor.house_garage_door
                to: 'on'
            continue_on_timeout: false
          - service: cover.close_cover
            target:
              entity_id: cover.garage_door
    default: []
mode: single
max: 3
2

I’m curious to know why you included this option (whose default value is true):

continue_on_timeout: false

but did not specify a timeout value (which has no default value; if unspecified the wait_for_trigger doesn’t time out).

3

I did this all via the GUI, so since I didn’t give it a value and seeing that switch enabled is what caused me to shut it off(might genuinely be OCD).

For me, I don’t know why having it set to false isn’t default and let the user decide they want a time out and enable that then show the timeout value field.

Would that be causing my problem?

4

I don’t think it’s the cause of the problem. I just it found it curious that it explicitly indicates it should not continue after timing out … except it won’t ever time out.

5

I think I’ve sorted it out.

I removed the service call to lock the door, as soon as I tested the automation after that, the state of the garage door started reporting properly!

So, I removed the service call to lock the door, but added in a wait_for_trigger to unlock the house door once the garage door had been open for 10 seconds.

I guess I was overwhelming the z-wave network or something…