Closed Javvaz closed 1 year ago
hello, the same issue here.
https://github.com/guerrerotook/securitas-direct-new-api/issues/90
Best Regards
I have no idea why. Can you share the logs a little bit before to see what was the status of the alarm?
I'm interested in the request when disarming the alarm.
The below messages appear in home-assistant.log when I request to disarm the alarm from armed_custom_bypass (just perimetral armed), indeed it doesn't get it.
I forgot, I try to disarm the alarm in the control panel to simplify the log. In the scripts neither works. From the any other status (armed_away, armed_home) it works disarming those status, but if the perimetral is armed at the same time, then the final status is armed_custom_bypass (perimetral armed), it is never able to disarm armed_custom_bypass.
Solved in this release https://github.com/guerrerotook/securitas-direct-new-api/releases/tag/v2.1.0.0
Since yesterday Nov 8 the securitas-direct-new-api intergration version 2.1.0.0. is not able to disarm from any arm state. When I try to disarm the alarm the below messages can be found in home-assitant.log with debug mode: