This object is in archive!
Rules not triggering
In Progress
On numerous occasions my rules have failed, i.e. they have not triggered. I cannot find any obvious reason for this. I have opened a few support tickets regarding this and every time Zipato have responded something like "we have done some changes to you system and it shall now be ok" but I still have some issues.
Does anyone else have the same problem?
/Henrik
The same problem 
No connection
Real-time notifications may not work
Same experience, rules not triggering, controller hangs(1-4 times/day).
Seriously getting tired of "beta testing". Considering moving on.
/Jonsson
Same experience, rules not triggering, controller hangs(1-4 times/day).
Seriously getting tired of "beta testing". Considering moving on.
/Jonsson
Hello people!
@Henrik Andersson
Do all rules fail, or just some of them? Are those rules linked to schedulers, ASTRO, or any other functionalities?
Are your rules properly synced? Do these rules contain some devices which may have failed? Do these rules include scenes, or groups? Are you using a cluster? Which firmware are you on? Please be as specific as possible, because debugging the problem with "Sometimes it doesn't work" is a living hell.
@Anders Jonsson
It's not beta anymore, and your controller shouldn't "hang" at all.
We are working on your open issues and we will keep you updated trough ticketing.
Anyone else having similar problems, please, open up a ticket for us so we can inspect each individual issue.
Best regards,
V
Hello people!
@Henrik Andersson
Do all rules fail, or just some of them? Are those rules linked to schedulers, ASTRO, or any other functionalities?
Are your rules properly synced? Do these rules contain some devices which may have failed? Do these rules include scenes, or groups? Are you using a cluster? Which firmware are you on? Please be as specific as possible, because debugging the problem with "Sometimes it doesn't work" is a living hell.
@Anders Jonsson
It's not beta anymore, and your controller shouldn't "hang" at all.
We are working on your open issues and we will keep you updated trough ticketing.
Anyone else having similar problems, please, open up a ticket for us so we can inspect each individual issue.
Best regards,
V
@Vedran:
As I said, I see no obvious reason or pattern when rules fail. It seems to happen arbitrarily. A rule that failed last week is now running fine and I',m quite sure that the rule that failed this morning will trigger tomorrow and then, maybe next week, some other rule will fail. That is what makes it frustrating! It also lowers the WAF dramatically!!! ;)
Yes, some rules have Astro-scheduler, other have only time scheduler (that was what was failing this morning) and yet others are triggered by virtual switches. I have synched the rules and got a "Success" message. I'm not using a cluster. I'm on the latest firmware (not beta). I have a Zipabox Duo. The rules contain scenes, conditions and a few http-calls. All devices are ok, no failed devices.
I am aware that is is hard to debug errors that you cannot reproduce at will and that was not the point of my post. I just want to know if other user have the same issues or if I am alone in this. It would also be nice to know if Zipato as this as a known error that they're working on...?
br
Henrik
@Vedran:
As I said, I see no obvious reason or pattern when rules fail. It seems to happen arbitrarily. A rule that failed last week is now running fine and I',m quite sure that the rule that failed this morning will trigger tomorrow and then, maybe next week, some other rule will fail. That is what makes it frustrating! It also lowers the WAF dramatically!!! ;)
Yes, some rules have Astro-scheduler, other have only time scheduler (that was what was failing this morning) and yet others are triggered by virtual switches. I have synched the rules and got a "Success" message. I'm not using a cluster. I'm on the latest firmware (not beta). I have a Zipabox Duo. The rules contain scenes, conditions and a few http-calls. All devices are ok, no failed devices.
I am aware that is is hard to debug errors that you cannot reproduce at will and that was not the point of my post. I just want to know if other user have the same issues or if I am alone in this. It would also be nice to know if Zipato as this as a known error that they're working on...?
br
Henrik
This morning the Wake-up rule, which is time based, triggered as it should. My Daylight rule, however, did NOT trigger! :(
This morning the Wake-up rule, which is time based, triggered as it should. My Daylight rule, however, did NOT trigger! :(
I had problems with rules not syncing even though the interface said they where synced correctly, and the box triggering them even though i deleted them, synced. Downgraded FW, synced, upgraded FW, synced. Nothing worked. But Zipato peeps helped me out today.
Besides that i must say that i find the box quite stable nowadays. Keep up the work Zipato! You should focus on Zipabox 2 instead of Zipatile. I think thats a business strategy failure.
Soon Samsung will dominate the market with Smartthings if these smaller firms dont pull they´re shit togather.
I had problems with rules not syncing even though the interface said they where synced correctly, and the box triggering them even though i deleted them, synced. Downgraded FW, synced, upgraded FW, synced. Nothing worked. But Zipato peeps helped me out today.
Besides that i must say that i find the box quite stable nowadays. Keep up the work Zipato! You should focus on Zipabox 2 instead of Zipatile. I think thats a business strategy failure.
Soon Samsung will dominate the market with Smartthings if these smaller firms dont pull they´re shit togather.
Zipabox 2 and more of your own sensors, cams, switches. And make it look damn good to. You guys have a much better platform and original strategy with protocol addons to the box. You could own the market.
Zipabox 2 and more of your own sensors, cams, switches. And make it look damn good to. You guys have a much better platform and original strategy with protocol addons to the box. You could own the market.
Replies have been locked on this page!