Time offset questions
We have an eco unit and found that when connected to a computer that was set as GMT+7 and deployed.
After retrieved the eco and sync the dataset, all data shown was showing correct date/time BUT the timezone was set at GMT-7 instead of GMT+7
Could it be some mistake in our configurations?
-
Official comment
Hello Wisarute
Check out the below FAQ from the app:
Note that the Eco's clock is synchronized to the device upon connection with the Eco, so if the clock was changed after the initial connection, then it would not have been set correctly. Either that, or perhaps the computer was not really set to the desired time zone (or maybe another device was used?). In any case, as you can see, this is done automatically. So if the time zone is not as you wished, you can change this after the deployment. Note that this requires the device to be online, as the data will be re-processed with the new time zone.
Comment actions -
Thanks. We tried again today.
- The computer used to config was set to GMT+7 and update to the time server (NTP)
- deploy the eco using same computer.
- collect the data & process online on same computer.
- the collected data displayed with correct date & time. but if we click at the "change timezone" it reported as GMT-7.
- If we changed to GMT+7, it will report wrong date&time.
- should we leave the system with GMT-7 ? as it is giving the correct time.
-
Hi Wisarute
If the correct time is shown, then I would suggest you keep it as is. If it was a true configuration error, a 14-hour lapse (-7 to +7) would be easy to spot and easily impact the date as well). We'll look into this, but I'm suspecting that it could be a conflicting configuration with the device being used, so yes, lead it as is.
Please sign in to leave a comment.
Comments
3 comments