This object is in archive!
Synchronisation failing constantly
Known
Ever since the firmware change, it's been hard to synchronise rules. It typically takes 2-3 attempts before you succeed. But today is even worse. I'm averaging 10-20 attempts before I can manage to synchronise. Is it just me?
The same problem 
No connection
Real-time notifications may not work
Same problem here. From the web app both synchronization types fail randomly, from API rule synchronization seems to work but not controller synchronization. This have been happening since the server overload problems Zipato have been having, I already opened a ticket which is still open... you should do the same so Zipato is aware more and more users keep having this issues. Alegedly they are fixing the server overload soon.
Same problem here. From the web app both synchronization types fail randomly, from API rule synchronization seems to work but not controller synchronization. This have been happening since the server overload problems Zipato have been having, I already opened a ticket which is still open... you should do the same so Zipato is aware more and more users keep having this issues. Alegedly they are fixing the server overload soon.
I've had a ticket open for weeks.
I've had a ticket open for weeks.
Right now I'm now past 20 attempts, I think. It's impossible to synchronise changes. This is TOTALLY unacceptable.
Right now I'm now past 20 attempts, I think. It's impossible to synchronise changes. This is TOTALLY unacceptable.
Dear David and Alberto,
We are working to resolve the synchronize issue as quickly as possible and apologize for any inconvenience.
Best regards,
Pero Zovkic
Dear David and Alberto,
We are working to resolve the synchronize issue as quickly as possible and apologize for any inconvenience.
Best regards,
Pero Zovkic
Here the same, for a week.
Have two Zipatile and a Zipabox in the cluster.
As it looks, it's the box that causes the problems.
The devices on the box also have a large delay (10-15 sec) and the box often reboots.
Here the same, for a week.
Have two Zipatile and a Zipabox in the cluster.
As it looks, it's the box that causes the problems.
The devices on the box also have a large delay (10-15 sec) and the box often reboots.
Dear David and Alberto,
Our team has resolved this issue and system is now working properly.
Feel free to test it out for yourselves and leave us some feedback here.
@David
About your case, my colleague doing his best to resolve your issue.
He will keep you informed about the progress through the support ticket.
Best regards,
Pero Zovkic
Dear David and Alberto,
Our team has resolved this issue and system is now working properly.
Feel free to test it out for yourselves and leave us some feedback here.
@David
About your case, my colleague doing his best to resolve your issue.
He will keep you informed about the progress through the support ticket.
Best regards,
Pero Zovkic
For weeks i have been looking at this several times every day.
A reboot of the box might fix it once, then its back to more of the same.
My Astro related schedules have all died. Cant fix them, cause i cant sync.
Why do i have these issues? What do you want from me Zipato, Stefan, Pero and all you other guys?
Name your price, i might pay it!
For weeks i have been looking at this several times every day.
A reboot of the box might fix it once, then its back to more of the same.
My Astro related schedules have all died. Cant fix them, cause i cant sync.
Why do i have these issues? What do you want from me Zipato, Stefan, Pero and all you other guys?
Name your price, i might pay it!
I have the same problem since weeks. Support told me, that even with a failure message box is syncing in the backgroud. I have this problem just now, so there is no solved issue.
My workaround:
- box sync fails: if yes got to api "box" "box:sync", change wait flag to true, take some longer time (i.e. 300 s) and try. you will get perhaps a true (everything went fine) or a false (box was not ready with sync but works on in the background)
- rule sync fails: First sync with api like I wrote above, after that use box.syncrules. Change wait to true and a longer time (300 sec). There has to be a result like "true". Then your rules are synced. Works fine.
For me it is normal, that I get "Sync failed". I am astonished if the box syncs without error first time. Perhaps my workaround helps until the team has solved it. I think this an timing problem. I have more than 100 devices, so that perhaps sync of the box needs much more time than expected.
I have the same problem since weeks. Support told me, that even with a failure message box is syncing in the backgroud. I have this problem just now, so there is no solved issue.
My workaround:
- box sync fails: if yes got to api "box" "box:sync", change wait flag to true, take some longer time (i.e. 300 s) and try. you will get perhaps a true (everything went fine) or a false (box was not ready with sync but works on in the background)
- rule sync fails: First sync with api like I wrote above, after that use box.syncrules. Change wait to true and a longer time (300 sec). There has to be a result like "true". Then your rules are synced. Works fine.
For me it is normal, that I get "Sync failed". I am astonished if the box syncs without error first time. Perhaps my workaround helps until the team has solved it. I think this an timing problem. I have more than 100 devices, so that perhaps sync of the box needs much more time than expected.
It's definitely got better now. I might still have to try a couple of times, but not 20(!)
It's definitely got better now. I might still have to try a couple of times, but not 20(!)
Now i managed to sync on the first try also, and my Astro scheduler rules seems to be working to Don't know what has happened?
This has not been working for a couple of weeks now. Started working today.
Synced my rules now as well, seemed to work fine. Great! Hope it stays this way.
Now i managed to sync on the first try also, and my Astro scheduler rules seems to be working to Don't know what has happened?
This has not been working for a couple of weeks now. Started working today.
Synced my rules now as well, seemed to work fine. Great! Hope it stays this way.
It's got worse again today.
It's got worse again today.
I'm sorry to say that my sync happiness lasted for a couple off hours. Tried to sync now, didnt work. :(
I'm sorry to say that my sync happiness lasted for a couple off hours. Tried to sync now, didnt work. :(
Most of my problems with synchronization were related to timeouts. Zipato developers poorly estimated how much time the process should take and it with many devices in network it generally never succeded. They made sync for me 1-2 times through a helpdesk ticket but later they generally my next request for sync - since that time (Jan 27th) my ticket is open and ignored.
And I've found my own resolution to that problem - I don't use web ui anymore but API function box / synchronize or box / synchronizeRules. It allows you to set any timeout you want (like 100-300 sec) and even make sync asynchronously :) what makes sense, as it occurs between cloud and box so your browser has no part in this process. So as Zipato developers have no idea how to adapt timeout to number of devices you have in your subscription and permanently get rid of problem that makes many users frustrated, instead of waiting for reasonable solution in web UI, you can sync via API call.
Recently there were problems with sync probably from other reasons as in my test subscription with few devices I had to sync several times to succeed and this couldn't have been timeout, but generally workaround with API call works every time.
Most of my problems with synchronization were related to timeouts. Zipato developers poorly estimated how much time the process should take and it with many devices in network it generally never succeded. They made sync for me 1-2 times through a helpdesk ticket but later they generally my next request for sync - since that time (Jan 27th) my ticket is open and ignored.
And I've found my own resolution to that problem - I don't use web ui anymore but API function box / synchronize or box / synchronizeRules. It allows you to set any timeout you want (like 100-300 sec) and even make sync asynchronously :) what makes sense, as it occurs between cloud and box so your browser has no part in this process. So as Zipato developers have no idea how to adapt timeout to number of devices you have in your subscription and permanently get rid of problem that makes many users frustrated, instead of waiting for reasonable solution in web UI, you can sync via API call.
Recently there were problems with sync probably from other reasons as in my test subscription with few devices I had to sync several times to succeed and this couldn't have been timeout, but generally workaround with API call works every time.
Tomasz, that sounds like a good suggestion. I'll try it.
I have a lot of devices, so that may be the cause of my woes.
Tomasz, that sounds like a good suggestion. I'll try it.
I have a lot of devices, so that may be the cause of my woes.
I just tried /box/synchronizeRules and it appeared to work first time with a 60-second timeout.
I just tried /box/synchronizeRules and it appeared to work first time with a 60-second timeout.
So, does synchronize synch both rules and devices?
So, does synchronize synch both rules and devices?
I do that as well, but my recent attempts have all been a failure. I used to change to 120sec but that is no longer enough. I changed now to 300sec and that succeded.
Interesting is the fact that despite the failure dialog it seems to work anyway. I can change a scene and press sync and the scene is actually changed and it works.
In my firewall I can trace all traffic going in and out from the box and the first 20-25sec alot of things happen but after that nothing happends so it just waits. And the gives a failure notice.
I do that as well, but my recent attempts have all been a failure. I used to change to 120sec but that is no longer enough. I changed now to 300sec and that succeded.
Interesting is the fact that despite the failure dialog it seems to work anyway. I can change a scene and press sync and the scene is actually changed and it works.
In my firewall I can trace all traffic going in and out from the box and the first 20-25sec alot of things happen but after that nothing happends so it just waits. And the gives a failure notice.
To sync rules with the API is perfect, for me it works every time and is very fast.
Huge improvement.
To sync rules with the API is perfect, for me it works every time and is very fast.
Huge improvement.
Cant Sink my rules also, from yesterday
Cant Sink my rules also, from yesterday
I've tried SynchronizeRules twice and it's worked both times. Synchronize has timed out once and given me "storage is busy" several times. But the nice thing is that it tells you if you need to synch or not (it seems that when you modify devices the changes get synched right away, but I was never sure about that).
I've tried SynchronizeRules twice and it's worked both times. Synchronize has timed out once and given me "storage is busy" several times. But the nice thing is that it tells you if you need to synch or not (it seems that when you modify devices the changes get synched right away, but I was never sure about that).
When you change rules only it's enough to run synchronizeRules without syncing box. It's very fast comparing to syncing devices. I'm glad it worked for you as well :)
When you change rules only it's enough to run synchronizeRules without syncing box. It's very fast comparing to syncing devices. I'm glad it worked for you as well :)
And "storage busy" is probably error message from box telling you that writing new data to storage hasn't finished, so you can't start new synchronization. As it's very little communicative it actually makes sense.
And "storage busy" is probably error message from box telling you that writing new data to storage hasn't finished, so you can't start new synchronization. As it's very little communicative it actually makes sense.
So "synchronize" does everything, including rules. Yes, synchronizeRules is much, much faster.
So "synchronize" does everything, including rules. Yes, synchronizeRules is much, much faster.
I have done measurements on a succesful sync.
It only took 41 seconds to transfer the data and then it waits.
Perhaps default settings is 30seconds when using GUI so in my case it is not enough.
I used the API in the test and had the timeout set to 300sec
I have done measurements on a succesful sync.
It only took 41 seconds to transfer the data and then it waits.
Perhaps default settings is 30seconds when using GUI so in my case it is not enough.
I used the API in the test and had the timeout set to 300sec
Here is another packet capture when I sync from the GUI and get a "failed sync.."
Exact 41sec also, and the sync times out after about 120sec as failed.
Here is another packet capture when I sync from the GUI and get a "failed sync.."
Exact 41sec also, and the sync times out after about 120sec as failed.
Hmm strange.
Hmm strange.
I sooo wish someone from zipato would/could explain how this works, or is suppose to work. The answer I got on my support ticket wasn't either correct or easy to understand. I got: "it syncs in the background so don't worry." it didn't sync in the background, and it didn't work!
I sooo wish someone from zipato would/could explain how this works, or is suppose to work. The answer I got on my support ticket wasn't either correct or easy to understand. I got: "it syncs in the background so don't worry." it didn't sync in the background, and it didn't work!
Synchronisation process on Zipabox can take more than a minute or two, if there are many devices connected to it. User interface is currently having the time limit and after not receiving "Synchronisation successful" message from the server within a certain time, it will show you the "Synchronisation failed" message". Anyway, synchronisation will still continue between the server and a box, and it will probably end successfully after some period of time.
We have now extended the time limit for synchronisation process on the web UI, and you should not get "Synchronisation failed" message so often.
Synchronisation process on Zipabox can take more than a minute or two, if there are many devices connected to it. User interface is currently having the time limit and after not receiving "Synchronisation successful" message from the server within a certain time, it will show you the "Synchronisation failed" message". Anyway, synchronisation will still continue between the server and a box, and it will probably end successfully after some period of time.
We have now extended the time limit for synchronisation process on the web UI, and you should not get "Synchronisation failed" message so often.
I dont really care if it takes a long time to sync (even though it should of course be optimized, and IS a big part of the zipabox/zipatile user experience). My problem is that syncing rules have been impossible also. (Now using the API it looks like its really fast to sync rules. Why is that?
I dont really care if it takes a long time to sync (even though it should of course be optimized, and IS a big part of the zipabox/zipatile user experience). My problem is that syncing rules have been impossible also. (Now using the API it looks like its really fast to sync rules. Why is that?
Looks like the sync issues are back and also now I have some bigger problems. Support upgraded my zipabox to the latest beta per my request to fix an issue with Zipato Keyfob and now all my alarm zones show "no sensor" in their configuration, if i try to configure a sensor or make any changes to the Alarm partition and try to sync from the web app it fails, if I try to do a "Save and Sync" from the API my box reboots and reverts all my changes back, so my alarm system is useless right now. Anyone else with the same issue?
Looks like the sync issues are back and also now I have some bigger problems. Support upgraded my zipabox to the latest beta per my request to fix an issue with Zipato Keyfob and now all my alarm zones show "no sensor" in their configuration, if i try to configure a sensor or make any changes to the Alarm partition and try to sync from the web app it fails, if I try to do a "Save and Sync" from the API my box reboots and reverts all my changes back, so my alarm system is useless right now. Anyone else with the same issue?
Hi, again!
I still seem to get this after only 30s of sync time approx.
Didn't you say that it was extended this time Sebastian?
It doesnt seem to be valid on my box anyhow.
Hi, again!
I still seem to get this after only 30s of sync time approx.
Didn't you say that it was extended this time Sebastian?
It doesnt seem to be valid on my box anyhow.
Replies have been locked on this page!