wrong date/time with LAN
couldnt scrape in kodi, so i found out that switching to Wifi leads to correct date/time and makes scraping possible again.
any help on this, because i prefer LAN in general
@neo207 I don't use kodi, but I believe it is possible to change the date and time internally in kodi, or am I wrong?
Furthermore, being on Wifi or LAN should not change the date and time, definitely being on LAN is more stable. The configuration I know about date and time is in
## Select your timezone from : ls /usr/share/zoneinfo/ (string) ;system.timezone=Europe/Paris
@Zing thanks, will try that out but it is really strange... when i boot, the date and the time is wrong... restart doesn't help.
Enabling Wi-Fi and a restart leads to the correct date and time, hence scraping and updating kodi is possible again.
but as i said, i will try to set the region in recalbox.conf and see what happens
Am. I really the only one whose recalbox starts with 2:00 all the time? Changing time and zone in kodi doesn't help. Multiple enabling and disabling wifi incl restarts help sometimes...
I have the same. Issue with rpi3 and rpi4 at home
@Zing this is set correctly in my recalbox.conf file, so it must be something different.
@neo207 I don't really understand what's going on, so I recommend that you do some tests:
Have you tested it on another Internet / another Wifi network?
Are you getting the "Connected" Status?
Does the Scrape work normally?
What is the default IP address for your Recalbox? 192.168.0.XXX or 192.168.1.XXX, 192.168.2.XXX? (I don't know if it influences, but as I don't know exactly why this is happening, we have to evaluate the possibilities)
@Zing when I restart several times and turn wifi on/off several times, i get lucky and the time and is correct again until i shut down. WHEN the date is set correct, scraping works perfectly.
as long as the date is wrong, neither works the internal scraper nor the scraping via KODI for new videos.
and yes, i have the CONNECTED status all the time. no error is shown.
i am pretty sure that i have to enable something in my router because the EXACT same problem is with recalbox rpi3 and rpi4 (i have both at home).
i tried "automatically open ports / upnp" for the two recalboxes but no change so far
my recalboxes have the IPs 192.168.178.xxx (just like all my devices in my network)
@neo207 Do you have a Fixed IP in reclabox.conf?
Can you test whether fixing or not fixing interferes with the result?
i am not sure where to look for, but i got this in the config file:
;kodi.network.waithost=192.168.0.XX (i don't know if i should but i replaced the last two numbers)
Set system hostname
Activate wifi (0,1)
Set wifi region
Wifi SSID (string)
Wifi KEY (string)
after rebooting the recalbox, the "new key" is replace by a hidden value "enc:xxxxx"
you can edit the "enc:xxxxx" value to replace by a clear value, it will be updated again at the following reboot
Escape your special chars (# ; $) with a backslash : $ => $
wifi.key=XXXXXXXXX (replaced with Xs)
Wifi - static IP
if you want a static IP address, you must set all 3 values (ip, gateway, and netmask)
if any value is missing or all lines are commented out, it will fall back to the
default of DHCP
;wifi.ip=manual ip address
secondary wifi (not configurable via the user interface)
third wifi (not configurable via the user interface)
;wifi.ip=manual ip address
The semicolon at the beginning of the line indicates that this command is not being used, to set the Ip manually you need to configure these 3 fields and remove the semicolon from the beginning of the lines.
If you don't want to test it, that's fine, it's just a test suggestion, as I said, I don't know what it can be and I'm proposing things that might be related, it's "trial and error".