Closed roelleke closed 2 years ago
I have the same problem as of today, if I look at the debug output the time looks ok but on the scroller the time is 1st Jan 1970 same on all three of my scrollers, even tried a new timedb api key, no joy, may be a problem with timedb? I tried your modification and it does resolve the issue, many thanks
Sent from my iPad Pro
On 9 Oct 2021, at 18:04, roelleke @.***> wrote:
The Clock get no time at reboot. All API keys are present an valid but the clock starts at midnight 1st January.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.
would it be possible to create bin firmware files if the code lines above really are the solution. Generally, what is the problem, did the 3rd party from time server change and therefore is not reachable anymore?
Kind Regards
Thanks for sharing the solution. I will have a look at it later today if I get time. If it all works out there will be an official update and firmware builds. Thanks.
Thanks, please keep in mind 2.17 with ° symbol. Cheers. love your project!
Thanks for the help. I have tested and confirmed the change. It is now merged to master and is part of 2.18 release with binary files.
https://github.com/Qrome/marquee-scroller/releases/tag/Scroller_V2.18
Let me know how it goes.
The Clock get no time at reboot. All API keys are present an valid but the clock starts at midnight 1st January.
I fixed the Problem in the TimeDB.cpp with this three lines after line 77: