Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lupusec does not report when Alarm has been triggered #81397

Closed
NCO3 opened this issue Nov 2, 2022 · 11 comments
Closed

Lupusec does not report when Alarm has been triggered #81397

NCO3 opened this issue Nov 2, 2022 · 11 comments

Comments

@NCO3
Copy link

NCO3 commented Nov 2, 2022

The problem

If the Lupus XT1's (lupusec integration) Alarm is triggered by a window / door contact it's not reported to homeassistant.
Even though the source code mentiones to following:
state = STATE_ALARM_TRIGGERED

The Lupusec Alarm System has a state which is called "triggered" (as it can be selected via dropdown in the automations)
However, if the alarm is on armed_away and I trigger the alarm by opening the door it is not reflected in the Lupusec Entity’s state.

What version of Home Assistant Core has the issue?

Home Assistant 2022.10.5

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

Lupusec

Link to integration documentation on our website

https://github.com/home-assistant/core/tree/dev/homeassistant/components/lupusec

Diagnostics information

No response

Example YAML snippet

- platform: state
    entity_id:
      - alarm_control_panel.lupusec_alarm
    to: triggered

Anything in the logs that might be useful for us?

No response

Additional information

No response

@home-assistant
Copy link

home-assistant bot commented Nov 4, 2022

Hey there @majuss, 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 Change the title of 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.

(message by CodeOwnersMention)


lupusec documentation
lupusec source
(message by IssueLinks)

@github-actions github-actions bot added the stale label Dec 4, 2022
@majuss
Copy link
Contributor

majuss commented Dec 11, 2022

@NCO3 unfortunately I have no way with my XT1 to trigger an alarm, because I have no sensors at all.

@github-actions github-actions bot removed the stale label Dec 11, 2022
@NCO3
Copy link
Author

NCO3 commented Dec 12, 2022

@majuss Don't worry, I will play around with the webhook on HA and the action http command on the XT1 to see if I can get achieve the alarm trigger this way.
Thanks for your response

@majuss
Copy link
Contributor

majuss commented Dec 18, 2022

@NCO3 please test HA 12.6 and report back :)

@majuss
Copy link
Contributor

majuss commented Dec 19, 2022

#84252

Implements alarm detection for XT2

@NCO3
Copy link
Author

NCO3 commented Dec 19, 2022

Thank you @majuss
Will do! :-)

@NCO3
Copy link
Author

NCO3 commented Dec 21, 2022

@majuss:
I tried on HA 2022.12.7, but Lupusec still does not report "Triggered"
Unfortunately I need to admit, that I haven't been precise enough (sorry for that).
I actually have a Lupus XT1 Plus
So I assume that there is a difference.
(I have seen issues with XT1 I did not observe with the XT1 Plus)
Would you mind checking if there is a difference.
As mentioned earlier - I have a workaround using a webhook.
So it's not urgent.
I really appreciate the effort you put into this integration!
Thank you!

@majuss
Copy link
Contributor

majuss commented Dec 28, 2022

Is the webinterface of the XT1 Plus in the same style as the XT1? Or is it modern like the XT2 and upwards?

@NCO3
Copy link
Author

NCO3 commented Dec 28, 2022

I am not sure because I just know the XT1 Plus. As the XT1 is discontinued AFAIK I assume the XT1 Plus is modern (see below).
1E763AAF-4979-40EC-BA21-258B3A790ABA

@majuss
Copy link
Contributor

majuss commented Dec 29, 2022

This is the old interface:
image

Please check it on a pc and report back.
Only way to fix this is probably when we meet virtually and you provide me a temporary VPN access.

@issue-triage-workflows
Copy link

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.

@issue-triage-workflows issue-triage-workflows bot closed this as not planned Won't fix, can't repro, duplicate, stale Apr 5, 2023
@github-actions github-actions bot locked and limited conversation to collaborators May 5, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants