Onion has correct timezone, and NTP has set to correct date/time, but LED display still shows wrong time
Quote from jnaujok on July 17, 2018, 1:17 amI got the updated firmware, loaded the correct timezone into the config, and manually ran ntpd peered to my local NTP server to make sure the time was set correctly.
Running "date" on the command line shows the correct time and date, but the clock face still stubbornly shows an odd time about 2 hours and 50 minutes earlier, which isn't even a valid GMT time.
Is there a command that updates the real time clock on the display?
I got the updated firmware, loaded the correct timezone into the config, and manually ran ntpd peered to my local NTP server to make sure the time was set correctly.
Running "date" on the command line shows the correct time and date, but the clock face still stubbornly shows an odd time about 2 hours and 50 minutes earlier, which isn't even a valid GMT time.
Is there a command that updates the real time clock on the display?
Quote from ihermit2 on July 17, 2018, 9:18 amI'm pretty sure a reboot should fix it.
I haven't been able to quickly find how Onion updates the display.
I'm pretty sure a reboot should fix it.
I haven't been able to quickly find how Onion updates the display.
Quote from Red on July 17, 2018, 11:15 amI had the same issue. It eventually "took", but I can't tell you the rhyme or reason why.
I had the same issue. It eventually "took", but I can't tell you the rhyme or reason why.
Quote from franko553 on July 17, 2018, 10:35 pmMy display only updates the time when the card changes. To see the accurate time, I have to wave at the motion sensor.
My display only updates the time when the card changes. To see the accurate time, I have to wave at the motion sensor.
Quote from ihermit2 on July 17, 2018, 10:38 pmhave you tried from the new set your timezone and time thread:/usr/bin/mcu/setMcuTime.sh
have you tried from the new set your timezone and time thread:
/usr/bin/mcu/setMcuTime.sh
Quote from ihermit2 on July 17, 2018, 11:22 pmWell now that I've done all that I'm seeing the same behavior and some time deltas despite the system time being synched
Well now that I've done all that I'm seeing the same behavior and some time deltas despite the system time being synched
Quote from jnaujok on July 17, 2018, 11:44 pmI did finally accidentally wave my hand in front of the sensor, and the clock reset. Oddly it only seems to keep time if it is on the "weather" card, but not on the "You need to update your Oboo Clock" card.
I did finally accidentally wave my hand in front of the sensor, and the clock reset. Oddly it only seems to keep time if it is on the "weather" card, but not on the "You need to update your Oboo Clock" card.
Quote from ihermit2 on July 18, 2018, 8:21 amdropping the extra information after the timezone and using uci set + commit and reboot has my time tracking normally.
so far the setMcuTime.sh has allowed the time to stay stable. I will update if it drifts.
dropping the extra information after the timezone and using uci set + commit and reboot has my time tracking normally.
so far the setMcuTime.sh has allowed the time to stay stable. I will update if it drifts.
Quote from Zheng Han on July 20, 2018, 5:55 pmHere is the official way to setup time on the Oboo
https://getoboo.com/community/topic/setting-your-oboos-time-and-date/
Here is the official way to setup time on the Oboo
https://getoboo.com/community/topic/setting-your-oboos-time-and-date/
Quote from ihermit2 on July 20, 2018, 6:52 pmSetting it that way messes up my time. Is there some data I can provide to help you debug why?
Setting it that way messes up my time. Is there some data I can provide to help you debug why?