Invalid session

[knutmarius]

This plug-in worked for a little while, but recently stopped working. I checked the log, and it seemed like the app was flooding the server with login attempts. My polling interval was set to 60 sec. Account was then blocked, and I unblocked it again. Changed the polling frequency to 1200 sec, but did not affect anything. Reinstalled the app and was able to add the devices back, but they don't seem to be controllable anymore. Log is saying "SectorAlarmError: Invalid session, please re-login".

I am located in Norway, by the way.

Snippet from the log:
+14:20:59.922: onCapabilityChanged, set locked to: true
+14:21:0.204: SectorAlarmError: Invalid session, please re-login
+14:30:19.528: onCapabilityChanged, set locked to: false
+14:30:25.817: onCapabilityChanged, set locked to: true
+14:30:26.087: SectorAlarmError: Invalid session, please re-login
+14:30:28.686: {"status":"success"}
+14:30:28.798: onCapabilityChanged, set locked to: false
+14:30:29.409: onCapabilityChanged, set locked to: true
+14:30:29.756: SectorAlarmError: Invalid session, please re-login
+14:30:32.972: {"status":"success"}

[Gurkgurkan]

I’m located in Sweden and have the exact same problem. My updating frequency is set on 120 seconds.

It always works after an app restart though.

+20:53:3.964: Info: Invalid session, logging back in.
+20:55:4.285: Info: Invalid session, logging back in.
+20:57:3.701: Info: Invalid session, logging back in.
+21:0:3.893: SectorAlarmError: Could not parse the response received from Sector Alarm. See innerError for more details
+21:1:3.726: Info: Invalid session, logging back in.
+21:3:3.754: Info: Invalid session, logging back in.
+21:5:3.944: Info: Invalid session, logging back in.
+21:7:3.863: Info: Invalid session, logging back in.
+21:9:3.943: Info: Invalid session, logging back in.
+21:11:3.962: Info: Invalid session, logging back in.
+21:13:4.822: Info: Invalid session, logging back in.
+21:15:4.077: Info: Invalid session, logging back in.
+21:17:4.089: Info: Invalid session, logging back in.
+21:19:4.030: Info: Invalid session, logging back in.
+21:21:4.206: Info: Invalid session, logging back in.
+21:23:4.290: Info: Invalid session, logging back in.
+21:25:4.477: Info: Invalid session, logging back in.
+21:27:4.282: Info: Invalid session, logging back in.
+21:29:4.473: Info: Invalid session, logging back in.
+21:31:4.567: Info: Invalid session, logging back in.
+21:33:4.569: Info: Invalid session, logging back in.
+21:34:51.346: Capability changed to partially_armed
+21:34:51.363: Error: No alarm code set
+21:34:56.602: Error: SectorAlarmError: Invalid session, please re-login
+21:35:4.696: Info: Invalid session, logging back in.
+21:37:4.707: Info: Invalid session, logging back in.
+21:39:4.612: Info: Invalid session, logging back in

[valleolsen]

Same issue here (in Norway). Running 60s updates. App restart fixes the issue for a short while. @Vaggan any chance to figure out what is causing this?

[valleolsen]

To me it seems the "Fix problem with multiple locks" PR is causing the issue. Haven't been able understand the whole workings yet but when getting the lock-id from the source every-time one need it by calling this.getData().id seems to be an issue since the auth-session seems to die pretty fast. Was able to recreate this by logging in manually to https://mypagesapi.sectoralarm.net/locks/getlocks/?withstatus=true&id={my system id} that returns valid information for a few refreshes before it suddenly returns unauthenticated. I see that the "sector_alarm_central" driver is authenticating on every call.

[Vaggan]

If you have more information or suggestions, please contact me.Sorry for not replying earlier.
Thank you @valleolsen for your research.
When I have time, hopefully soon, I will look in to this and see if I can figure out a solution.
If you have more information or suggestions, please contact me.

[ugumba]

Same issue here. I use 600s updates.
Restarting app helps only occasionally.