-
-
Notifications
You must be signed in to change notification settings - Fork 288
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
Daylight saving time change is not reflected in Gladys #1917
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Node-schedule is unmaintained, one option would be to migrate to this library: https://www.npmjs.com/package/croner If anyone wants to help us here! |
Gladys keep the old hour in scene after a daylight saving time change.
Restarting Gladys fixes the issue.
The issue comes from the
node-schedule
NPM library.node-schedule/node-schedule#435
node-schedule/node-schedule#267
node-schedule/node-schedule#34
We can either find a new library or try to fix this one
https://community.gladysassistant.com/t/gladys-nest-pas-passe-a-lheure-dhiver/8428
The text was updated successfully, but these errors were encountered: