more than 1000 seconds away
That would explain it, the time was set to some date in May...
Posts by al_f
-
-
NB: It's cheap and simple to add an RTC chip to an RPi board.
Thank you for this suggestion!
That doesn't sound exactly like what you're seeing though?
You're right. It connects to my wifi, but for some reason just doesn't update the time. Interestingly, I tried running Ultramarine Linux on the Pi, getting the exact same problem: connecting just fine to the network, but failing to update the time until I force it to. Looks like it's a hardware problem and not a problem with LibreElec, then. I didn't try cabled network, though.
So I'm going to order an rtc chip and cross my fingers.
-
Don't know if it's possible to unset thread resolved?
It turns out whenever the Raspberry is shut down, the clock will stop. Regardless of the time of shutdown, at boot the time is set to 18:26.
I don't have wired network, it runs on wifi, and on each boot I have to go Settings > LibreELEC > Connections > MyNetwork > Connect to get internet and correct time.
So,
1. Is it possible to set system time manually?
2. How do I get automatic connection to wifi at boot?
In Settings > LibreELEC > Network > Wireless networks is set to active while Wired networks is set inactive.
Thankful for any input!
-
New to LibreELEC, running on Raspberry model 4 B.
Had a problem similar to this: Strange problem with ntp time - it is 6 minutes off!
Time was off by several hours, but in my case the router had the correct time.
Using Settings > LibreELEC > Updates > Firmware updates to update Bootloader EEPROM (now at 2024-04-15) and VIA USB3 firmware (now at 000138c0) fixed the problem after rebooting.
