-
Notifications
You must be signed in to change notification settings - Fork 160
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
Time not working in military time #257
Comments
What version of the firmware are you running? |
3.01 |
Going to need more as I can't replicate it and most of the European users use the 24 hour clock. |
i had the same problem too.I change to AM/PM and it was working.Now after rebooting it still shows January 1 12:00 even with AM/PM ... |
Yea |
Check that your time db api key is active and valid. I can't replicate this. https://timezonedb.com/register |
Make sure the timezonedb.com endpoint is accessible and not being blocked on your network. You can also connect to the Serial Monitor in the Arduino IDE and view the log as it attempts to get the time and find out what is going on there. I am not able to replicate the issue. |
-edit- weather data returns just fine. tried another API key for time, same result: time is retrieved correct from timeserver, but clock starts at 12.00 1/1. Same sort of issue over here (Netherlands). running v 3.01. after reboot clock starts at 12.00 date: thursday 1st of january. 17:49:39.079 -> |
Also Netherlands here |
Is the service endpoint really getting a valid response for time there? EU has blocked news services and other things as well. This is an open source project -- if someone that has the issue can literally debug or test some changes, that would be helpful. |
Not sure why but a lot of European cities do not work, i am using cityID 2759879 (Almere Netherlands), what i do is take the cityID from Paris to configure the time because that does work and set it back to my own city after time is updated. |
There is a call that uses the latitude / longitude values to get the time zone. I am wondering if those values have changed in the response. |
I can confirm that 24H works for me, I live in Sweden. CityID=2698733 Kungsängen, SE, CityID=2698733 Almere Stad, NL, CityID=2759879 But from what I can see there is some parameters missing from your serial log, :
And then you get an |
I noticed something, when i reset the clock will be 00:00 and can take from 5 minutes to an hour till it updates the time at this moment. |
@RetroCare: i can confirm that after a while the time is displayed correct (took up to 30 minutes). |
I can say now that after a reset (somehow my unit is freezing now and then :) ) it updates immediately now, maybe there was something on the API side of the service not related to the scroller because there was no change in that area of the code. |
Any update? |
I'm getting what I think is the same issue. The clock doesn't seem to be getting set:
Is the output from serial monitor. |
I want to update my experience with this (EU-The Netherlands), i still get 00:00 at startup of the clock, only when i wait a minute or 3-5 i refresh data from Web and it will fetch current time. |
I am having the exact same issue |
I am from the netherlands and we use 24 hour clock, but its not working, as soon as i set the time to 24 hours the time is going to 12:00 midnight and not updating to the correct time, as soon as i set it to am pm time it displays the correct time
The text was updated successfully, but these errors were encountered: