This object is in archive!
Strange delay in app
Need Answer
Hi,
I encounter a strange behavior in the feedback of switch- and slider status in the android app.
When i opperate a slider to e.g. 100%, the associated lamp will go immediately to 100%, but... within a second, the slider walks back to 0%, and after 20 to 60 seconds the slider walks to 100%. And sometimes it doesn't go to the right value at all.
A switch does the same thing; by tapping it, the lamp turns on, but the switch-button turns gray for about 20 to 60 seconds and then eventually turns to on/orange.
(Operating these sliders/switches in the webinterface gives no problems at all. The respons is just perfect.)
Connecting remote or locally doesn't make a difference.
Where is this delay in response coming from? What can i do about it?
The same question
No connection
Real-time notifications may not work
Hello,
same behaveiour in the IOS App.
Andreas
Hello,
same behaveiour in the IOS App.
Andreas
Locks like we are seeing the same things:-)
https://community.zipato.com/topic/how-fast-is-z-wave-zipabox-fibaro-together
Locks like we are seeing the same things:-)
https://community.zipato.com/topic/how-fast-is-z-wave-zipabox-fibaro-together
I am having the same problem on website (switches switching on and off instead of just on or off) and in old and new iOS app (delay and strange movement to on and off positions).
I am having the same problem on website (switches switching on and off instead of just on or off) and in old and new iOS app (delay and strange movement to on and off positions).
Thanks for the reply's.
To Milan: I am pretty sure that the problem is in the communication between the app and the server. Sometimes the app shows the message 'the device can not communicate with the server or zipabox'. It looks like the app is not receiving the feedback (downstream) from te server right. The upstream is ok because the devices react within a second. Also in the live-view on the webinterface i see no delay at all. It is just in the app.
To Jacob: exactly, your movies (in particular the first one) are showing the problem.
Thanks for the reply's.
To Milan: I am pretty sure that the problem is in the communication between the app and the server. Sometimes the app shows the message 'the device can not communicate with the server or zipabox'. It looks like the app is not receiving the feedback (downstream) from te server right. The upstream is ok because the devices react within a second. Also in the live-view on the webinterface i see no delay at all. It is just in the app.
To Jacob: exactly, your movies (in particular the first one) are showing the problem.
Same random issue for me since many months.
Same random issue for me since many months.
More over the box seems often very slow to react on z-wave and ip modules.
More over the box seems often very slow to react on z-wave and ip modules.
Hi Laurent,
In which direction do they react slow? I have serveral devices: zwave (fibaro and aeon), coco and virtual switches. They react all fine to a command, only the status-feedback is heavily delayed in the app. In fact the old web-gui responds best.
What i was thinking: could the amount of devices be a part in this problem? The more devices, the more delay? I hope not......
Hi Laurent,
In which direction do they react slow? I have serveral devices: zwave (fibaro and aeon), coco and virtual switches. They react all fine to a command, only the status-feedback is heavily delayed in the app. In fact the old web-gui responds best.
What i was thinking: could the amount of devices be a part in this problem? The more devices, the more delay? I hope not......
This morning i was testing it again and now the respons is way better than yesterday.... Now i have a maximum of 5 sec. delay in the feedback. That's acceptable for me....
This morning i was testing it again and now the respons is way better than yesterday.... Now i have a maximum of 5 sec. delay in the feedback. That's acceptable for me....
I think this is still a problem/bug. Currently have this on one of our
customers boxes. Everything you do is immediantly done at the
controller, but you don't get a response to the server quickly.
Sometimes it takes several minutes.
- removed backup battery
- restart doen't work
- firmware update doen't work
I think this is still a problem/bug. Currently have this on one of our
customers boxes. Everything you do is immediantly done at the
controller, but you don't get a response to the server quickly.
Sometimes it takes several minutes.
- removed backup battery
- restart doen't work
- firmware update doen't work
Here also ... No Connection
Here also ... No Connection
Replies have been locked on this page!