version 1.2.3 still disconnects after some time (12h?)

[mazi1987]

It seems that the newest version token refresh doesn't not work, I need to re-add the device every day to HA

[piolec66]

In my case, device is every day unavailable between ~15:00 and ~02:00. Every day... Also refresh token?

[modo1302]

same here!

on the Electrolux dev page, you can see this info:

thats 12h.
does it mean you ahve to generate new access token every 12h? that sucks!

[HonkStonk]

Hmm - not sure how the token refresh/expiration is supposed to work but now that I found this issue it seems I'm experiencing exactly the same except my history shows its unavailable more or less 7h out of 24h every day.

What I also notice in this repeating pattern is that after 7h of unavailability - it gets roughly 12+4h of availability divided in two "blocks" of "Idle"... so for sure there seems to be a 12h timer somewhere but I don't get what gives only 4h of availability after the 12...

Suggestions?

This is with 1.3.1 but has been so since the addition of Pure i9.2 in this integration. I am using 2x Pure i9.2 robots. Both are behaving the same and it seems very related to the token expiration...

[PsychoV3]

Defo experiencing the same issue here, it appears the refresh token timer is off, as in the evening - No access, but by the morning it is running again.

[HonkStonk]

Yeah… but how to fix? Would it help to create new tokens and set some settings upon creation that didn’t exist before?

…

On Sat, 2 Nov 2024 at 09:58, PsychoV3 ***@***.***> wrote: Defo experiencing the same issue here, it appears the refresh token timer is off, as in the evening - No access, but by the morning it is running again. — Reply to this email directly, view it on GitHub <#126 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AADNN75TBVT2UR43SFK4G2LZ6SH4RAVCNFSM6AAAAABM2SB3GCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJSHEZDMNJRHE> . You are receiving this because you commented.Message ID: ***@***.***>