fwmarcel / home-assistant-divera

This is a custom component that allows to address the Divera 24/7 alarm software from Home Assistant.
49 stars 11 forks source link

[Bug]: Different Alarm, same title -> No automation triggered #210

Closed JbbDE closed 2 days ago

JbbDE commented 5 days ago

Requirements

Current Behavior

First Alarm fired title "F2" (Feuer 2), the automation is triggered. 7 Days later, a alarm, also an "F2" is called, even description changes, date changes, but the automation isn't triggered.

Expected Behavior

Automation should be triggered with every new alarm, even with the same title

Steps To Reproduce

No response

Context

YAML state

Environment

- HA Version: 2024.11
- Divera Version: 1.2.1
- Blueprint Version: Unknown

Anything else?

No response

fwmarcel commented 4 days ago

the behavior is correct. Ideally, the automation should always be triggered when the ID of the alarm changes. I think that should work...

fwmarcel commented 4 days ago

I've had a look. the blueprint is currently designed to only trigger when the alarm ids change. Is your alarm combined? And are you using the current blueprint version?

JbbDE commented 4 days ago

When was the last change?

fwmarcel commented 4 days ago

@N1c093 modified the blueprint 6 months ago... You can take control of your automation / blueprint as follows: https://www.home-assistant.io/docs/automation/using_blueprints/ Have a look if the trigger attribute is set.

JbbDE commented 2 days ago

okay, that was the problem xD