-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Authentication tokens expired after time change (CEST to CET) #147
Comments
I have the same problem here and It seems that I can’t reactivate the developper mode ... :’( |
Same here |
I've found a solution, If ypu have home assistant i just rebooted m'y home assistant instance ans it works again |
Ok, after hassling around for some hours I can confirm, that this can be fixed by restarting HA. This seems to be induced by the automatic change of the clock to summer time. Since I might have forgotten the solution in next spring when the clock changes back, can somebody fix that? Or can I do something to prevent that? |
I found that I needed to go to my countrys somfy site (ie https://www.somfy.dk/) and login here. If I tried the default one I would get an error with wrong password. |
At least for me the developer mode isn't available any more. Can't find that anymore in the Tahoma / Somfy pages. |
As @KimSchultz said, i found it on the somfy page.
|
I have the same problem 😕 |
Hi everyone, The developerMode cannot be deactivated once it has been activated once. Tokens generated following the documentation do not have an expirationTime. |
Description:
This morning, all my authentication credentials for Somfy expired unexpectedly. This issue occurred on the same day as the time change in Spain, where we transitioned from Central European Summer Time (CEST, UTC+2) to Central European Time (CET, UTC+1).
I suspect the problem might be related to the time change and how token issuance and validation are handled. It seems likely that the server issuing the tokens and the server validating them might not be using the same time zone. The difference in time zones could be causing the tokens to be considered invalid due to a mismatch in the expected times.
Proposed Solution:
A possible fix would be to use UTC consistently across all systems involved in token issuance and validation, ensuring that time zone changes do not affect the authentication process.
Steps to Reproduce:
Expected Result:
Tokens should remain valid regardless of time zone changes.
Actual Result:
Tokens expired after the time change.
The text was updated successfully, but these errors were encountered: