-
Notifications
You must be signed in to change notification settings - Fork 7
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
Timezone not working? Also some other things I noticed #13
Comments
6bdbe6b 8629731 test(1).zip |
Hi Thank you, the Holow typo is also in the firmware.ino too. I've updated the latest version and it does print the time now, I can confirm that it is getting the correct time. Its currently 10:16am and its reporting the correct time, however its still not properly moving the hour hand. If I reset it now, it'll move the minute to 16 and the time is set to 12:16. I've tried setting it to GMT0 and the serial print correctly states 9:16 (using the above example) and the minute hand moves to 16 but doesnt move the hour hand so stays at 12:16 still. Obviously I know the hands are not independent so I assume the normal action would be to keep going around clockwise until it hits the correct time I tried <+01>-1, it reports the correct time (10:16) in serial, interestingly it sets 1:16 on the clock itself. So I tried <+02>-2 and that reported 11:16am, which would be correct if I lived in that timezone. It set the clock to 2:16. I'm no coder so not really sure whats going!! If its working fine for others, then only thing I can think of is that I need to flip the rotation so maybe something is happening with that code? Quick info, I'm in the UK. We have daylight savings so winter = GMT0 and summer = BST with is GMT+1. We're still in BST. Thanks |
Hi @HennieLP , i'm having the same issue. finished my clock yesterday, uploaded the .ino code (latest) and checked on the SErial monitor, (this is my timezone <-05>5 Bogota, Colombia, Latin America). However, the clock is kind of not showing the right time. |
The same problem. |
Asking if i understand the problem corectly the Clock Prints The Corect time via Serial But the clock shows The Wrong Time? |
Yeah for me, serial was reporting the correct time but the clock was moving to the correct minute but incorrect hour. It seems like its not calculating the time correctly and taking the time zone too literal. From the 2 examples above: I was also encountering the same issue, when I first set it, it was 3pm and I had to set GMT+3 to get the correct time, which obviously moved the hour hand 3 hours but setting my correct timezone (GMT0BST,M3.5.0/1,M10.5.0) only moved 1 hour as BST is plus 1 hour. |
Added Check If NTP Server Responds With Vaild Response |
I created a development branch in which I rewrote the time calculation. If it dosent work as Expected Please Let me Know |
Hi @HennieLP , my case it stays in an infinite loop on line 626 |
Added That The Clock automatically Retrys After 60 seconds pleas Try Again |
didn't work so i commented couple lines and added 1 according to time.h documentation. all of this inside updateTime() function |
if this
dosent work than the clock cant conect to the NTP server does your clock have an Active Internet conection ? or is your Own Ntp Server runing corectly ? |
the clock is cheking if its past the Year 2000 to verify its result from the NTP Libary |
It gets ip address normally. As i mentioned, i replaced the time function and curiously now it works. Perhaps in my case there is something not working with the way you structured the sentences in updateTime. |
is your clock in an difernet network than your phone/pc ? |
It is on the same network. I'm also able to set it up over a pc browser now in case i need to modify anything. |
what NTP server are you using ? |
co.ntp.pool.org |
please try co.pool.ntp.org |
co.ntp.pool.org is not a NTP server |
My mistake, it was a typo on my response. I used co.ntp.pool.org. As i mentioned, after changing the two lines in UpdateTime function, it worked. |
curently Trying With getLocalTime(&tm); you can actualy Remove The NTP Client Libary beacuse it isnt used |
changed it in The Dev Branche Thanks for the Help! |
if you whant i can even undo your code Change and you can make A Pull Request so that you are Listet As Contributor |
I updated my clock today to the dev branch version of yesterday and it worked fine. Thanks Hennie for all the improvements in the last weeks :). If the dev branch is working correctly, should we push a new release version or at least commit it to the main. |
@HennieLP @nikzin96 Hey both! Coming back to ask you a question, is there any way i can see the html setup after initial configuration? Reason is that i would like to be able to edit my clock wifi data and even factory reset it without having to reflash. Hope it's feasible. I'm really not good at coding so haven't tried. Additionally something I've seen is that no matter if i reflash it, it keeps the memory of previous wifi info, reason why I would like to create a sort of factory reset. Thanks in advance for any help !!!! |
If you open the ip of the clock a page Shud appear where you can change the WiFi and other Settings |
Tried but doesn't work. I had to change the code to dinamically delete the server object on the initwifi function when you're already connected to wifi so that it launches the server normally. |
hi |
Did you already try the dev branche if not please do so and let me know if it fixed your problem |
Hi |
|
Hi
Thanks for the code. I loved the design of the clock but the wifi and NTP really brought it together.
I've built the clock and everything is working, however initially I was struggling to get the correct time, obviously I was manually setting to 12:00 and plugging in, but the correct time was never set. After some troubleshooting, I determined it was setting the correct minutes but not the correct hour.
I played around last weekend, it was just after 3pm but when I set my timezone (I'm in the UK so set GMT0BST,M3.5.0/1,M10.5.0) it would set 1pm plus whatever minute it was. I started to play around with other timezones like 2 hours on but the only one I could get working was <+03>-3. I left the clock running all last week, it did drift about 7 mins over the week so need to play with the steps a little. Thats a task for another day.
I saw you released an update, so just flashed that, unfortunately it doesnt fix the NTP issue but funnily enough the timezone <+03>-3 doesnt work as I am playing around at 4pm this weekend so I needed to use <+04>-4 to get the correct hour. The serial monitor doesnt print out what it thinks the current time is so I am not sure exactly what time the clock thinks it is, it is possible to print the time each minute when it updates? could help others diagnose similar issues.
A few other things I noticed, in the HTML code for the main page, settings and wifi settings its called Holow, not Hollow. Just a typo obviously.
Also on my clock, I originally noticed when it was finding the correct time on initial boot it was fairly quiet but the minute updates were very loud, almost sounded like old 3D printers before the silent stepper drivers. I noticed there was a 'fast rotate' for when it starts and a slow/normal for the minute updates. Only difference seemed to be int dt = 1 & 20 with 1 being fast. I changed both to 1 and the noise was massively reduced on minute updates.
Thanks
The text was updated successfully, but these errors were encountered: