-
Notifications
You must be signed in to change notification settings - Fork 30
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
[FEATURE REQUEST] Allow management and report status of "PERI" alarm #3
Comments
Thanks for this. I am a total noob to HA, Python etc. so I have a lot to learn. I DID get it working, so am really thrilled. +1 for any feature requests - Annex (secondary) alarm would be great, and I can't see how to set Partial Day/Night... I will keep exploring. |
Thanks @bvis for the feature request. How I write the api was by opening the https://customers.securitasdirect.es/owa-static/login web application and logging calls to the /owa-api/graphql with the json payload. If you need help let me know and we can work on getting those logs. |
Hi, now I have had some time for doing this. It was so easy because all the calls are as you said between the browser and the backend: First request:
First response:
Polling request:
Polling first response:
Final response:
|
When only the perimetral alarm is activated the request/answer is like this:
After some WAITS, the final answer:
|
Other statuses are:
|
Awesome! Let me work on that tomorrow! |
I added the support for the PERI1 type of alarm in this commit, can you download and test it and tell me if it works? |
I’ll do it asap, tonight when I’m at home |
On other hand it would be very useful, I don't know if it's possible, to have a "button" or activator to do a call to the remote system and update the status of the sensor. This way I could check the current status of the alarm in case I want to program an scenario or script, as it's very usual to change the status via the control panel we have in home. |
Thanks for the update on the perimeter alarm. I see what you mean when you said that is reporting the incorrect status. Home Assistant define a set of possible status for the alarm, defined here. The original code for the integration of the alarm used that custom state STATE_ALARM_ARMED_CUSTOM_BYPASS for the perimeter alarm. I don't know how to set a custom state for the panel. |
This is happening in the background automatically. I push a new changed in the alarm_control_panel.py file, please update and tell me if it fix the issue. |
This is how it's seen: AFAIK it should be in the state |
Now I realized that there are three new states for when the perimeter is active, So I pushed new changes to group all those changes into the CUSOM_BYPASS. Here is the commit Tell me how it looks like right now. |
Hi and thanks again for this, you are so responsive! As you may see it right now show the "correct", based in the current limitations the alarm control panel card has. Thanks a lot for this! One improvement which I think shouldn't be hard to do is to add an attribute to the current sensor with the obtained message, it contains the exact sentence like in my example: `"msg":"Tu Alarma está conectada en modo Parcial Noche y en el exterior". It could be something like this, it would be very helpful because I could show the message below the alarm card to give me more information.
On other hand I suspect there's another This is answer I obtain when it's in this status:
|
Related to this I've created this PR: #16 |
Yeah, I'm looking forward in how to add custom attributes to an entity so I can add more information. I'm going to investigate this. |
Hi, |
#71 It is the same that this issue. |
I think this is solved with latest releases. |
First of all thanks for this great job!
One thing I miss in the Securitas Direct integration in HA is that I cannot check the status of the perimeter alarm or activate/deactivate it.
I know it was exposed by the earlier API because the component Cebeerre developed by supported it.
Is it anything you could do for adding this feature?
The text was updated successfully, but these errors were encountered: