Hi. lately i started to use RPI with Raspbian Stretch(last version) to send data from Davis console with data logger online. Equipment is at my place at the moment, im testing it and it will go in remote location soon. Everything is working nice, I have adjusted to send archives from Davis every 5 minutes, and ftp, wunderground, cwop...Everything working great, no errors. I have just one problem. I simulated power outages(which will happen, location is solar powered) and when powering rpi wewx starts BEFORE ntp has finished checking and updating time! So soon after boot, weewx adjusts time on Davis to his time(which is wrong, its last time RPI was online). I have removed fake clock, and it seems that its still working? Because after boot, i always get this time when RPI was shut off. So, that leads to wrong archive time, and that could be a big problem because many power outages. I was searching, and seems that weewx should wait for ntp to adjust time, and start after that, but that is not working correctly. I made a workaround by adjusting max_drift to big value, like 864000 so time will never update by itself(i can do it mannualy over team viewer with wee_device commands. Is there any way to delay console time update, so rpi has few minutes of time to update ntp? Or even, not to start weewx until ntp has finished updating(I checked weewx filein ini.d folder, ntp is listed as start requirment. Is this some type of bug, and is there any way to prolong davis time synchronization, or to start weewx after time has been upgraded?
Regards Ċ½eljko from Croatia -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
