Any idea when this will be fixed?
1 Like
As per @patrick, this should only be an issue with the UI. If it's affecting your apps then it may be a bigger issue than he is aware of. Please post a code snippet so we can see how you are gathering your time data and comparing them.
We have identified the cause and are working on deploying a hotfix that will fix this issue.
3 Likes
This has been fixed in 2.1.1.116 now available.
2 Likes
Simple test, create a new virtual switch, turn on switch, check event details for that switch, are they correct in local time?
Also, verify your timezone is set and hub time in settings, hub info match up.
Yes creating a virtual switch works and hub time is correct. Attached are the screen shots of everything including the virtual switch created AND a device in the same time of the logs and the event time for that device.
Check again tomorrow. It appears your screen shots show current time with the exception of the device that had an event stores in utx prior to the update. Give it 7 hours and more events will then be generated in local time.
Ok, Yes I just updated to 119 about 2 hours ago, will check tomorrow
So, it's tomorrow and I checked and yes the event timestamp is corrected, however it created another issue as it "coincidentally" started occurring at the same time that the time stamp error caught back up with "correct" time. This has occurred on all 3 of my hubs. The Zigbee and Zwave hubs are with errors as below and continue to run.
Coordinator One of the 3 hubs locked up completely at the same specific time and I will be trying to ip reboot,
When I rebooted the locked up coordinator hub, everything was gone all apps/rules/dashboards, everything.....So I'm installing the backup now.
Tagging @bobbyD as this installing my previous backup is still going after 30 minutes and still hasn't completed, how long should I wait and what should I do if it doesn't complete?
Going on 1 hour and 40 minutes now with this.
