home-assistant[bot]
commented
1 week ago 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 close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign lupusec` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove 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)
The problem
I have a Lupus XT2 Plus with many door/window sensors. Sometimes one of these sensors is not accessible. This could be a radio problem or a weak battery. In this case, the Lupus central unit reports this.
The problem is that the Lupus integration in Home Assistant switches from "armed" to "alarm triggered" for 1 second when such a message is received and then back to "armed". This leads to massive problems because automations are triggered as if there really was a burglar alarm, even though absolutely nothing is happening and only one sensor was briefly unavailable. The central unit itself does not trigger an alarm when a sensor triggers an error, but only informs about this sensor.
It is OK if the integration also receives such messages and makes them available separately. But what must never happen is that the integration interprets something like this as an alarm and triggers an alarm.
Can you please fix this as soon as possible, as the integration is currently unusable if there is a risk that it will trigger an alarm several times a day that is completely incorrect?
What version of Home Assistant Core has the issue?
2024.10.2
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Lupus Electronics LUPUSEC
Link to integration documentation on our website
https://www.home-assistant.io/integrations/lupusec/
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response