Lupusec integration trigger alarm without an alarm
The problem
I created an automation on:
- Lupusec Alarm Trigger -> Flash Hue lights
Interesting is that this plugin triggers also not if an alarm is done.
See
What version of Home Assistant Core has the issue?
core-2024.8.3
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant Container
Integration causing the issue
lupusec
Link to integration documentation on our website
No response
Diagnostics information
trigger: id: '0' idx: '0' alias: null platform: device entity_id: alarm_control_panel.lupusec_alarm from_state: entity_id: alarm_control_panel.lupusec_alarm state: disarmed attributes: code_format: null changed_by: null code_arm_required: false friendly_name: Lupusec Alarm supported_features: 3 last_changed: '2024-09-28T05:00:10.896651+00:00' last_reported: '2024-09-28T05:00:30.904799+00:00' last_updated: '2024-09-28T05:00:10.896651+00:00' context: id: 01J8VG08P0CHFK8Z49HZ88D019 parent_id: 01J8VG08P0G7HM1HQB8PH7B0BQ user_id: null to_state: entity_id: alarm_control_panel.lupusec_alarm state: triggered attributes: code_format: null changed_by: null code_arm_required: false friendly_name: Lupusec Alarm supported_features: 3 last_changed: '2024-09-28T05:00:32.912934+00:00' last_reported: '2024-09-28T05:00:32.912934+00:00' last_updated: '2024-09-28T05:00:32.912934+00:00' context: id: 01J8VG108GGACM0MN43DCXE98K parent_id: null user_id: null for: null attribute: null description: state of alarm_control_panel.lupusec_alarm
Example YAML snippet
No response
Anything in the logs that might be useful for us?
I would expect only the trigger if the lupusec was "armed" and then there is an alarm trigger.
Additional information
No response
Hey there @majuss, @suaveolent, mind taking a look at this issue as it has been labeled with an integration (lupusec) you are listed as a code owner for? Thanks!
Code owner commands
Code owners of lupusec can trigger bot actions by commenting:
-
@home-assistant closeCloses the issue. -
@home-assistant rename Awesome new titleRenames the issue. -
@home-assistant reopenReopen the issue. -
@home-assistant unassign lupusecRemoves the current integration label and assignees on the issue, add the integration domain after the command. -
@home-assistant add-label needs-more-informationAdd a label (needs-more-information, problem in dependency, problem in custom component) to the issue. -
@home-assistant remove-label needs-more-informationRemove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.
(message by CodeOwnersMention)
lupusec documentation lupusec source (message by IssueLinks)
I am missing if this issue is about the integration not behaving correctly or the automation not doing what you expect
Hi joostlek,
I think the lupus integration has a big, from mY perspective. I would assume an alarm trigger only if there is a real alarm or?
or do i need to filter on some trigger detailes?
Best regards Sebastian
I have no clue, I don't own an alarm system so I'm not sure what is normal here
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
I’ll have a look.