Securitas fails sometime after HASS restart because of expired token or credentials

[pedropaislopes]

Securitas fails sometime after HASS restart because of expired token or credentials

[lukelalo]

Yep, I have it fixed by removing the securitas part on my configuration.yaml file and letting only the web configuration

[pedropaislopes]

Something happened on Securitas side, as the integration is normal now. No changes was made on my installation. Weird…

[pedropaislopes]

Two updates:

• arming and disarming works fine some minutes after hass restart (less then 5 minutes). This is why I suspect that something is related to token or credentials obtained on securitas initialization
• change check alarm period from 40 (config flow default value) to 20 minutes (minimum) didn’t helped neither. The “expired” message appears on log.

Cheers!

[lukelalo]

Same issue for me, since 2013.10.3 HASS update

[KoolLSL]

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.

[guerrerotook]

Thanks for the update