This object is in archive!
Events clock 2 hours behind
Not a Problem
Hi
My time zone is set to the right one - but my events are logged two hours behind. Meaning alarm OFF at 7 is logged as alarm OFF at 5.
Anybody knows how I can adjust this?
Thomas
The same problem 
No connection
Real-time notifications may not work
I have the same. In addition to lots of events missing on most devices
I have the same. In addition to lots of events missing on most devices
Same for me.
Same for me.
Same for me. Events displayed delayed.
Same for me. Events displayed delayed.
Hello everyone,
Events are logged in logs with time stamp -2 hours (two hours behind). We are aware of this issue and we are working on resolving it as soon as possible.
Hello everyone,
Events are logged in logs with time stamp -2 hours (two hours behind). We are aware of this issue and we are working on resolving it as soon as possible.
Hello,
any update about the status of the wrong timing in the events?
Hello,
any update about the status of the wrong timing in the events?
Any progress on this issue? Still two hours off...
Any progress on this issue? Still two hours off...
Still 2 hours off. Am I the only one with this annoying problem?
Still 2 hours off. Am I the only one with this annoying problem?
Seems to work for me now! But for a long time it have bin a problem.
Seems to work for me now! But for a long time it have bin a problem.
Same here... just noticed because i was investigating something weird with my alarm.
Same here... just noticed because i was investigating something weird with my alarm.
Here still 2 hours behind. In the app and web. iOS, android, IE and chrome.
Running 1.1.23 beta
Here still 2 hours behind. In the app and web. iOS, android, IE and chrome.
Running 1.1.23 beta
Same for me, still two hours behind.
Same for me, still two hours behind.
Hi everyone,
This issue is currently present on the 1.1.23 firmware, so anyone who isn't testing the cluster feature - please revert your firmware back to 1.0.17 and reboot the box.
However, if you have the 1.0.17 firmware and you are still experiencing that delay, you need to open a ticket for us to check your box and manually fix this.
Since I see that still a lot of you are using the firmware 1.1.23 I need stress out that 1.1.23 fw was developed purely for cluster testing purposes, so please do not use that firmware if you haven't been instructed by Zipato Support to do so.
Have a nice day!
Vedran
Hi everyone,
This issue is currently present on the 1.1.23 firmware, so anyone who isn't testing the cluster feature - please revert your firmware back to 1.0.17 and reboot the box.
However, if you have the 1.0.17 firmware and you are still experiencing that delay, you need to open a ticket for us to check your box and manually fix this.
Since I see that still a lot of you are using the firmware 1.1.23 I need stress out that 1.1.23 fw was developed purely for cluster testing purposes, so please do not use that firmware if you haven't been instructed by Zipato Support to do so.
Have a nice day!
Vedran
ticket made. still nog working on 1.0.17
ticket made. still nog working on 1.0.17
it has always been the case even on 1.0.17.
it has always been the case even on 1.0.17.
Gert and Tobias opened a ticket and got the response. If there is anyone else with the similar problem, please follow their example and open a ticket so we can inspect the issue and resolve it.
Best regards,
Vedran
Gert and Tobias opened a ticket and got the response. If there is anyone else with the similar problem, please follow their example and open a ticket so we can inspect the issue and resolve it.
Best regards,
Vedran
worked fine for me, I like to use beta versions, but didn't know 1.1.23 is specially for cluster testing.
fixed the problem within half an hour!
thanks again Vedran!
worked fine for me, I like to use beta versions, but didn't know 1.1.23 is specially for cluster testing.
fixed the problem within half an hour!
thanks again Vedran!
Issue fixed!
Thanx Vedran for quick respons on ticket! Issue solved within 30 min. Good job!
/Tobias
Issue fixed!
Thanx Vedran for quick respons on ticket! Issue solved within 30 min. Good job!
/Tobias
After rolling back to latest official, the issue seems to be solved. Thanks.
Rolling back also seems to fix the problem that I had with battery operated z-wave devices status change not always being received by the controller.
After rolling back to latest official, the issue seems to be solved. Thanks.
Rolling back also seems to fix the problem that I had with battery operated z-wave devices status change not always being received by the controller.
Replies have been locked on this page!