Closed pedropaislopes closed 10 months ago
Two updates:
Cheers!
Same issue for me, since 2013.10.3 HASS update
I had a similar issue after updating HA to 2023.10.3, getting an "Unauthorized" message. But it seems to have self-solved after doing "Reconfigure" on the Securitas integration (asking on which phone number to send the SMS code to enter). It is now working correcting since 24 h. By the way, I see now only one Securitas Direct integration on the Integration page, before was always 2.
Yep, I have it fixed by removing the securitas
part on my configuration.yaml
file and letting only the web configuration
Something happened on Securitas side, as the integration is normal now. No changes was made on my installation. Weird…
Thanks for the update
Hi! Unfortunately I'm facing an issue that seems to be related to expired login session.
On my understanding, on HASS startup Securitas components makes a "login", obtaining a token (sorry if I misuse the "token" word here!). This token is reused on subsequent commands to Securitas servers (I guess). But, after a while (I don't have any idea how long this while is), this token is expired, causing every subsequent communication to Securitas to fail.
I'm using a slightly modified
alarm_control_panel.py
and__init__.py
files. I've changed all occurrences ofasyncio.sleep(1)
toasyncio.sleep(3)
, because if servers have a status update (after arm/disarm event) every second it returns with a "false positive", causing an arm or disarm operation without changing HASS entity state.And, to produce such a more complete log, I'm using @guerrerotook https://github.com/guerrerotook/securitas-direct-new-api/blob/146-error-arming-but-dissarming/custom_components/securitas/alarm_control_panel.py file (with my modifications as described).
Below is HASS log.
Can you take a look?
Cheers!