#Reboot device if unavailable, trigger does not work

5 messages · Page 1 of 1 (latest)

magic fulcrum
#

Hello, my yale bridge disconnect sometime and don't reconnect until a manual reboot (plu off plug on)
To fix my issue I ve added a smart socket behind the Yale bridge to perform the plug off plug on task.

But for some reason this automation doesn't trigger, if I trigger it manually it perform the task successfully
Any idea why is wrong with the trigger ?

Thanks or your help

description: The bridge turn off after few days and an hard reboot is necessary
trigger:
  - platform: state
    entity_id:
      - lock.porte_dentree
    to: unavailable
    for:
      hours: 0
      minutes: 20
      seconds: 0
action:
  - type: turn_off
    device_id: a27def5723af9e987c3aa196fcf284e4
    entity_id: 9794735edc919180390c8b9ff1b5a5d5
    domain: switch
  - delay:
      seconds: 15
  - type: turn_on
    device_id: a27def5723af9e987c3aa196fcf284e4
    entity_id: 9794735edc919180390c8b9ff1b5a5d5
    domain: switch```
#

PS on the capture it's written capslok as "Unavailable" but tin the developer tools "state " it is "unavailable"

#

PS2 do not buy Yale product and if you do, create a SSID using only 2.4ghz it will fix half of your issue, but yeah don't buy their product ..

magic fulcrum
#

Up

lone trail
#

I’ve never been able to get a state trigger to detect unavailable state reliably. I use a template trigger for things like that: {{ is_state(‘lock.porte_dentree’, ‘unavailable’) }}. I don’t know why, but that has always been more reliable for me.