I (on owfs) set the time like this:
echo "$(date +%s)" > "clock/udate" I then make sure it is running and correct.If I then load it up in OneWireViewer on Windows, it reads exactly 1 month behind. So if I set the clock to today, 20180822, the windows machine sees it as 20180722.
We are having an issue the other way around. Windows user syncs the clock to their system time, which is correct. I read the probe: cat clock/dateAnd it comes back exactly 1 month ahead. So a windows machine that synced the DS1921 to 20180822 would come back as 20180922 using owfs.
I am not familiar with how Windows works, is there a reason why this could be happening? Could it just be a bug in the 1wire viewer, or is it an issue with owfs?
Just trying to determine the root cause of this.
signature.asc
Description: PGP signature
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers