Basi

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:...

When only the perimetral alarm is activated the request/answer is like this: ``` { "operationName":"CheckAlarmStatus", "variables":{ "numinst":"XXXXX", "panel":"SDVFAST", "referenceId":"XXXX", "idService":"11", "counter":3 }, "query":"query CheckAlarmStatus($numinst: String!, $idService: String!, $panel: String!, $referenceId:...

Other statuses are: ``` { "operationName":"CheckAlarmStatus", "variables":{ "numinst":"XXXXX", "panel":"SDVFAST", "referenceId":"YYYYY", "idService":"11", "counter":3 }, "query":"query CheckAlarmStatus($numinst: String!, $idService: String!, $panel: String!, $referenceId: String!) {\n xSCheckAlarmStatus(numinst: $numinst, idService: $idService, panel: $panel, referenceId:...

I’ll do it asap, tonight when I’m at home

When I pressed the CUSTOM BYPASS it has activated the "PERI" alarm! Nice! But it's incorrectly seen in the panel:  In fact the current status is this one: ...

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...

After this update now it's reported like this: 

This is how it's seen:  AFAIK it should be in the state `armed_custom_bypass`, as I see in the possible status list: https://developers.home-assistant.io/docs/core/entity/alarm-control-panel/#states

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...

Related to this I've created this PR: https://github.com/guerrerotook/securitas-direct-new-api/pull/16