A couple of bugs to be aware of
These are 2 bugs I've reported to Zipato that people might want to be aware of.
1) A conditional wait causes subsequent commands not to be executed.
This is quite subtle. If you place a wait inside an "if" block, the commands that come *after* the "if" block are not executed, but this only happens the first time after rules are synchronised. And not even all the time - perhaps in 90% of cases.
So if you have:
if (x) blah blah; wait 20; blah blah
xyz
After you create the rule and synchronise, the first time the rule runs, "xyz" will not get executed. This has been reproduced by Zipato.
This can obviously cause mysterious, apparently inexplicable failures.
(It may also occur the first time the rule is run after rebooting. I haven't tested that).
2) The weather values tempMaxC and tempMinC are always 0.
This has not been confirmed by Zipato yet - they're still investigating. So maybe it only happens to me. Or maybe it depends on where you're living. But it looks like a bug because those values are definitely correct if you look at the weather with the Zipabox API.
I'd be interested to know if anyone else has this problem.
The same problem 
Another bug I forgot to mention:
3) Comparison of today's date with date of (now) fails after midday
This has also been reproduced by Zipato, I believe. I'm not sure whether it's been fixed or not in recent firmwares.
The effect is that, if you ask whether today is, say, the 1st of March, on the 1st of March the condition will evaluate to "true" until midday, whereupon it starts returning "false".
Another bug I forgot to mention:
3) Comparison of today's date with date of (now) fails after midday
This has also been reproduced by Zipato, I believe. I'm not sure whether it's been fixed or not in recent firmwares.
The effect is that, if you ask whether today is, say, the 1st of March, on the 1st of March the condition will evaluate to "true" until midday, whereupon it starts returning "false".
Yes, I just wanted to tell everyone else in case it explains why something doesn't work in their rules.
Yes, I just wanted to tell everyone else in case it explains why something doesn't work in their rules.
I would add the fact that if you use a JOIN and a REPEAT block in the same rule the repeat does not work. This is a known issue too.
I would add the fact that if you use a JOIN and a REPEAT block in the same rule the repeat does not work. This is a known issue too.
Alberto, for me the repeat does not work regardless if there is a join or not. This rule basically should flash the outside lights 4 times when I (or my partner) get home and the presence detector changes state to on. It only flashes once.
Alberto, for me the repeat does not work regardless if there is a join or not. This rule basically should flash the outside lights 4 times when I (or my partner) get home and the presence detector changes state to on. It only flashes once.
Also another known issues for the record;
1. Sensor grouping or "Groups" don't work.
2. Scenes dont work well with Fibaro RGBW controllers. They act randomly and don't go to preset state on scenes.
Also another known issues for the record;
1. Sensor grouping or "Groups" don't work.
2. Scenes dont work well with Fibaro RGBW controllers. They act randomly and don't go to preset state on scenes.
Thanks David
I had issues in a rule and tried to solve it by adding a wait in it. Bad idea it seems...
Thanks David
I had issues in a rule and tried to solve it by adding a wait in it. Bad idea it seems...
Yes, if the "wait" is inside an "if". Hopefully this will be fixed soon. It explained a few mysterious rule failures of mine.
Yes, if the "wait" is inside an "if". Hopefully this will be fixed soon. It explained a few mysterious rule failures of mine.
Just to let everyone know: bugs 1) (conditional wait) and 3) (date comparison after midday) are now fixed.
Just to let everyone know: bugs 1) (conditional wait) and 3) (date comparison after midday) are now fixed.
Also, the repeat now works for a while.
Also, the repeat now works for a while.
thanks guys for the updates. You comments are well appreciated.
thanks guys for the updates. You comments are well appreciated.
Replies have been locked on this page!