Hi There,
i have a interesting Problem were an automation is triggered; but non of the conditions are true
Even if i delete it, the ghost will pick another.
the can be annoying if the radion start in the night.
I am running the highest version on a PI.
Any hint how i can troubleshoot who triggers this… or how to stop this behaviour?
Wiping and reinstall should be the last option …
stay healthy
Ralph
Start by sharing your automation, and why you think it’s this automation that’s doing whatever it is.
i observe this for some different automation which sometimes triggered unique actions.
All in common is that the trigger are ‘switches’
1 was observerd some days back (i removed this in the meantime)
2 and 3 only differ condition… but only 3 fires frequently… i can also see it in the "last triggered time’.
2 was affected some days back … looks like that only one automation is affected at a time.
It’s a lot easier to help if you can share the (correctly formatted) YAML for that automation, not the pretty images. Decoding images is nothing like as easy 
I already noticed that the infected entry is the last in the list.
I put another entry to the last postion and the problem is gone actually.
Also the new ‘last entry’ behaves at expected.
Anyhow i feel that there is a bug somewere in the automation.
The behavoiur was predictable every 15 mins.
will try to sent a file as PN; am only allowed to attached pictures.
my automation.yaml
- id: '1577541192231'
alias: ZZ Tuer loescht Anwesenheit
description: ''
trigger:
- device_id: 44bc804036f74331b2c13327fdd35aa5
domain: binary_sensor
entity_id: binary_sensor.kontakt_haustur
platform: device
type: not_opened
condition: []
action:
- alias: ''
data: {}
entity_id: input_boolean.anwesend
service: input_boolean.turn_off
- data:
message: Intruder alert at apartment!!
title: Intruder alert
service: notify.smtp2go
- id: '1577549385533'
alias: Anwesend wenn bewegung erkannt
description: ''
trigger:
- entity_id: binary_sensor.flur_melder
from: 'off'
platform: state
to: 'on'
condition: []
action:
- alias: ''
data: {}
entity_id: input_boolean.anwesend
service: input_boolean.turn_on
- id: '1578759398372'
alias: bewegung schaltet Flur ein
description: ''
trigger:
- entity_id: binary_sensor.flur_melder
from: 'off'
platform: state
to: 'on'
condition:
- condition: or
conditions:
- before: sunrise
condition: sun
- after: sunset
condition: sun
action:
- device_id: 8f6148e9b88346e79ead0cd52ec1791c
domain: light
entity_id: light.lampe_flur
type: turn_on
- delay: '35'
- condition: state
entity_id: light.lampe_esszimmer_bottom_notification
state: 'off'
- device_id: 8f6148e9b88346e79ead0cd52ec1791c
domain: light
entity_id: light.lampe_flur
type: turn_off
- id: '1578817099107'
alias: WZ Schalter startet Hue im WZ aus
description: aus
trigger:
- device_id: 186140f6dc8748f5bf1067ae919a2bd1
domain: light
entity_id: light.brand_switch_notification_light
platform: device
type: turned_off
condition: []
action:
- scene: scene.wohnzimmer_kueche_alles_aus
- id: '1578822895867'
alias: Manuel Schalter Flur
description: ''
trigger:
- device_id: 7baac63de31b42a7950063ef847e8bbc
domain: light
entity_id: light.lampe_esszimmer_bottom_notification
platform: device
type: turned_on
condition: []
action:
- alias: ''
data: {}
entity_id: input_boolean.flurschalter
service: input_boolean.turn_on
- id: '1578824833250'
alias: Manual Schalter Flur aus
description: ''
trigger:
- device_id: 7baac63de31b42a7950063ef847e8bbc
domain: light
entity_id: light.lampe_esszimmer_bottom_notification
platform: device
type: turned_off
condition: []
action:
- entity_id: input_boolean.flurschalter
service: input_boolean.turn_off
- id: '1578942589302'
alias: Rollanden auf 6:30
description: ''
trigger:
- at: 06:30
platform: time
condition:
- condition: and
conditions:
- condition: state
entity_id: binary_sensor.workday_sensor
state: 'on'
- condition: state
entity_id: input_boolean.urlaub
state: 'off'
action:
- alias: ''
data: {}
entity_id: cover.jeq0105763
service: cover.open_cover
- entity_id: cover.jeq0105781
service: cover.open_cover
- entity_id: cover.jeq0105947
service: cover.open_cover
- entity_id: cover.jeq0106936
service: cover.open_cover
- entity_id: cover.rollladen_esszimmer
service: cover.open_cover
- id: '1579342380103'
alias: Rolladen auf 8:00
description: ''
trigger:
- at: 08:00
platform: time
condition:
- condition: or
conditions:
- condition: state
entity_id: binary_sensor.workday_sensor
state: 'off'
- condition: state
entity_id: input_boolean.urlaub
state: 'on'
action:
- entity_id: cover.jeq0105763
service: cover.open_cover
- entity_id: cover.jeq0105781
service: cover.open_cover
- entity_id: cover.jeq0105947
service: cover.open_cover
- entity_id: cover.jeq0106936
service: cover.open_cover
- entity_id: cover.rollladen_esszimmer
service: cover.open_cover
- id: '1579453273432'
alias: Taeglich verdunkeln
description: ''
trigger:
- event: sunset
offset: 00:30:00
platform: sun
condition: []
action:
- data:
entity_id: cover.rollladen_esszimmer
position: 68
entity_id: cover.rollladen_esszimmer
service: cover.set_cover_position
- entity_id: cover.jeq0106936
service: cover.close_cover
- entity_id: cover.jeq0105781
service: cover.close_cover
- data:
entity_id: cover.jeq0105947
position: 60
entity_id: cover.jeq0105947
service: cover.set_cover_position
- data:
entity_id: cover.jeq0105763
position: 60
entity_id: cover.jeq0105763
service: cover.set_cover_position
- id: '1580161151689'
alias: heimkommend licht an
description: ''
trigger:
- entity_id: input_boolean.anwesend
for: 00:00:05
from: 'off'
platform: state
to: 'on'
condition:
- condition: or
conditions:
- before: sunrise
condition: sun
- after: sunset
condition: sun
action:
- scene: scene.alpha
- id: '1581249119914'
alias: test button
description: ''
trigger:
- entity_id: remote.hue_smart_button_1
platform: state
condition:
- condition: state
entity_id: remote.hue_smart_button_1
state: 1_click_up
action:
- device_id: 8f6148e9b88346e79ead0cd52ec1791c
domain: light
entity_id: light.lampe_flur
type: turn_on
- id: '1586602561838'
alias: Musik HR1 an
description: ''
trigger:
- entity_id: remote.hue_dimmer_switch_1_2
platform: state
condition:
- condition: state
entity_id: remote.hue_dimmer_switch_1_2
state: 2_click_up
action:
- data: {}
entity_id: media_player.yamaha_receiver
service: media_player.turn_on
- data:
source: NET RADIO
entity_id: media_player.yamaha_receiver
service: media_player.select_source
- data:
entity_id: media_player.yamaha_receiver
media_content_id: Radio>Favoriten>hr1
media_content_type: NET RADIO
entity_id: media_player.yamaha_receiver
service: media_player.play_media
- id: '1586604842640'
alias: Musik Yahama aus
description: ''
trigger:
- entity_id: remote.hue_dimmer_switch_1_2
platform: state
condition:
- condition: state
entity_id: remote.hue_dimmer_switch_1_2
state: 3_click_up
action:
- data: {}
entity_id: media_player.yamaha_receiver
service: media_player.turn_off
If you want to post code, select </> and put your code between the 2 times three tickmarks
So… which of that mass is the problem one? That’s the only one we needed
As wrote ealier … the last entry.
As i now put another entry as last, the problem diappeared. The problematic entry is now the sencond to last.
This sounds weird; but i dont feel that the entry itself has a problem.
- id: '1586604842640'
alias: Musik Yahama aus
description: ''
trigger:
- entity_id: remote.hue_dimmer_switch_1_2
platform: state
condition:
- condition: state
entity_id: remote.hue_dimmer_switch_1_2
state: 3_click_up
action:
- data: {}
entity_id: media_player.yamaha_receiver
service: media_player.turn_off
This automation looks fine, however you don’t need the condition, you can just change your trigger like this:
trigger:
- entity_id: remote.hue_dimmer_switch_1_2
platform: state
to: "3_click_up"
and remove the condition.
I also tried the reduced setting; but i see there more delays (or it is even not working)
After some observation i can say, the problem is still there.
It is not related to the position within the automation file; currently i see it only with the HUEremotes.
Any ide how to find the guy who triggers this automations?
Are you seeing the automation run in the Logbook?
Or, are you just seeing the receiver turn off?
i just see the result … Logbook is empty.
The Logbook shouldn’t be empty, unless you’ve excluded things from it or recorder
If you haven’t, then it’s not the automation doing it.
You are correct… Looks like the ’ hue remote ’ is doing the magic.
Interestingly it has a timer… actually 30 mins
Earlier today on my HUE dimmer is was 15 mins
22:02:58
Hue Smart button 1 changed to short_release
22:02:56
Hue Smart button 1 changed to unavailable
21:32:45
Hue Smart button 1 changed to short_release
21:32:43
Hue Smart button 1 changed to unavailable
I’d say the issue is that you
So if the button drops off the network it goes to ‘unavailable’ and triggers the automation, it then comes online again i.e. it goes to short_release and triggers the automation, it then goes to ‘unavailable’ again and triggers the automation - and so on.
Maybe you can rectify this at least partly by defining the from and to states that should trigger the automation as @Burningstone partly suggested.
And that’s the best example of why I don’t think it’s a good idea to implement wireless remotes as state entities. It’s better and more logical to use events in my opinion.
Agreed - and that’s what, at least in my philosophy, the inclusion of the from-to parameters in the state triggers do: it triggers an automation based on the event when the state of an entity/device goes from on defined state to another defined state.