On Sunday, August 14, 2016 at 12:04:01 PM UTC-4, flynndacat: > > Hello: After I upgraded to V3.5, I noticed the time on my weather console > was off by several seconds. I know that the old Ultimeter driver I had used > (11RC3) corrected any drift, so I waited a few days to see if the time > corrected. It did not (the drift had increased by another 2 seconds), so I > rolled back the driver to 11RC3. This took care of the clock problem, and > so far I have not noticed anything else different between this and the new > driver. The code, however is different in a few places. > > Just FYI if anyone else notices this. >
hi steve, take a look at the ultimeter.py v0.16 code that came with weewx 3.5.0. at line 127 you'll see DISABLED_getTime and a bit later DISABLED_setTime. remove the DISABLED_ text so that the functions are simply getTime and setTime, then restart weewx. see if that takes care of the time synchronization the two methods are disabled because off the comments in this thread: https://groups.google.com/forum/#!searchin/weewx-user/ultimeter|sort:relevance/weewx-user/jRDyOpG15V4/qTvMZcG9BgAJ are there other ultimeter users out there who can validate the time synchronization? m -- 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.
