You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using your library in a light controller that I built based on an Arduino Nano. This runs 24/7 and is responsible to switch on some outdoor lighting based on some time rules and external sensors. Actually this works really well usually.
But today it, again, failed to "survive" the switch from CEST to CET. I took some time to finally find out what is going wrong here. I literally spent hours debugging my own code until I decided to have a look at the DCF library. And the reason, finally, was pretty obvious.
You use "now()" to get a timestamp. If the DST switch happens, then "now()" jumps one hour and now some of your DCF time validation routines are broken until I powercycle the whole controller.
I could fix that, but I'm asking myself if the library actually is still maintained? If you consider the library as being "unmaintained", I would continue maintaining it under the same name. I would continue with a different name otherwise.
The text was updated successfully, but these errors were encountered:
I'm using your library in a light controller that I built based on an Arduino Nano. This runs 24/7 and is responsible to switch on some outdoor lighting based on some time rules and external sensors. Actually this works really well usually.
But today it, again, failed to "survive" the switch from CEST to CET. I took some time to finally find out what is going wrong here. I literally spent hours debugging my own code until I decided to have a look at the DCF library. And the reason, finally, was pretty obvious.
You use "now()" to get a timestamp. If the DST switch happens, then "now()" jumps one hour and now some of your DCF time validation routines are broken until I powercycle the whole controller.
I could fix that, but I'm asking myself if the library actually is still maintained? If you consider the library as being "unmaintained", I would continue maintaining it under the same name. I would continue with a different name otherwise.
The text was updated successfully, but these errors were encountered: