This object is in archive!
Non Routing node don't work anymore
In Progress
My zipabox worked fine for many years until now, but...
Since I added a new device qubino, all door opening sensors don't update when doors lock or open. Same with motion detector, switchs works normally.
- - I deleted doors sensors and added again. They don't react. It seems that some service is dead.
- - I deleted the new Cubino device, same problem.
- - Try to shutdown and start the box, same problem
- - Try to Heal the network, same problem
My version is 0.999.8.a
Does anyone encounter this problem? What can I do ?
Thanks.
The same problem 
No connection
Real-time notifications may not work
I think this problem is related to the Server Lag Problem....
I think this problem is related to the Server Lag Problem....
thanks for your update
any fix available ?
thanks for your update
any fix available ?
Hello,
I have the same issue. Did anyone solve this issue?
Hello,
I have the same issue. Did anyone solve this issue?
If this is related to the server problems, no fix is available until Zipato adresses this. You can find more information here: https://community.zipato.com/topic/server-problems-again
If this is related to the server problems, no fix is available until Zipato adresses this. You can find more information here: https://community.zipato.com/topic/server-problems-again
I thought the Zipabox itself worked independantly from Zipato servers and that online access was only needed for rule setup etc? Quite disurbing if you are depending on Zipato servers for e.g. a doorsensor to activate, firealarm to trigger or any other event. or am I misunderstanding something here?
I thought the Zipabox itself worked independantly from Zipato servers and that online access was only needed for rule setup etc? Quite disurbing if you are depending on Zipato servers for e.g. a doorsensor to activate, firealarm to trigger or any other event. or am I misunderstanding something here?
Yes could someone explain the same question as Troels?
Yes could someone explain the same question as Troels?
Hallo!
I am also interested how the server problems effect local rules on the box or function of devices.
regards,
bernhard
@ZIPATO: is it not possible to release an anouncement when there are problems with the serverss. So we do not have to search for problems with our devices and do a lot of postings in the forum when there is a known ongoing problem.
Hallo!
I am also interested how the server problems effect local rules on the box or function of devices.
regards,
bernhard
@ZIPATO: is it not possible to release an anouncement when there are problems with the serverss. So we do not have to search for problems with our devices and do a lot of postings in the forum when there is a known ongoing problem.
Sensor/devices should still activate lights etc normally, it is just the update status on your app or in control center. This is because the signal goes to the cloud then back to your app. The basic signal from your device to your zipabox will work as normal and thus trigger the rule you have created. Unless your rule uses a trigger from the internet like a weather option, then you will have a delay.
Sensor/devices should still activate lights etc normally, it is just the update status on your app or in control center. This is because the signal goes to the cloud then back to your app. The basic signal from your device to your zipabox will work as normal and thus trigger the rule you have created. Unless your rule uses a trigger from the internet like a weather option, then you will have a delay.
Hi,
I confirm what Adrian just wrote.
It's just a very hard now to work on the configuration...
Things seems to get a bit better since I wrote the 1st post, I have around 20s between notification...
Thanks to Ivan for telling the situation. I know how hard it is to admit a situation. Some times corporation have a hard time to admit a difficult situation. But down the road, customers are more comprehensive than you may think, it build up a great reputation. (talking from experience... I run a telecom company, outages happen some times ;o))
So, good luck fixing this issue, I'll be patient...
Hi,
I confirm what Adrian just wrote.
It's just a very hard now to work on the configuration...
Things seems to get a bit better since I wrote the 1st post, I have around 20s between notification...
Thanks to Ivan for telling the situation. I know how hard it is to admit a situation. Some times corporation have a hard time to admit a difficult situation. But down the road, customers are more comprehensive than you may think, it build up a great reputation. (talking from experience... I run a telecom company, outages happen some times ;o))
So, good luck fixing this issue, I'll be patient...
What about http requests in rules. Are they relayed though the cloud, or do the requests go directly from the controller to the requested server? My pushover messages have frequently been delayed the last weeks, up to 30 seconds late. I don't know if it is the Pushover service or Zipato that is the problem.
What about http requests in rules. Are they relayed though the cloud, or do the requests go directly from the controller to the requested server? My pushover messages have frequently been delayed the last weeks, up to 30 seconds late. I don't know if it is the Pushover service or Zipato that is the problem.
Hi,
Any news on this issue ?
Hi,
Any news on this issue ?
Replies have been locked on this page!