Some ideas for the rules creator.
I am using zipabox for
several weeks now and learning more along the way.
I like the way of
programming via the puzzle and although I can do everything I want with it (at
the moment) I still have a few remarks:
1) Please make it possible
to use the "When" puzzle the same way as the others so that I can use
multiple "When"s in one rule. This reduces the number of rule in
the list so we have a better overview. This is something like
"grouping" of rules.
2) I would like to see in
the rule list if a rule is running (via a green dot (led) or so).
3) I would like to see when
a rule was last started and also the time it ran.
4) No when I disable a rule
I have to synchronize my rules. I would like to see it instantaneously, without
synchronizing. I think it can be done by assigning a boolean to every rule at
sync time. By changing the rule-n boolean to false stops that rule from firing.
Just a few thoughts.
Thanks,
Frank.
I like this idea 
1. what do you mean multiple when puzzles, do you mean using a "and" block in the sensor block of the first when block? this creates multiple whens, and there is the option of an "or" block to you can use too.
2 & 3. not a bad idea, good for debugging also.
4. I guess being a cloud service you have to decide when to sync everything back to the box. Otherwise every change you make will require resyncing and this could be a continuous event, meaning if the box is still syncing from your last change, you wouldn't know if it got your current change.
1. what do you mean multiple when puzzles, do you mean using a "and" block in the sensor block of the first when block? this creates multiple whens, and there is the option of an "or" block to you can use too.
2 & 3. not a bad idea, good for debugging also.
4. I guess being a cloud service you have to decide when to sync everything back to the box. Otherwise every change you make will require resyncing and this could be a continuous event, meaning if the box is still syncing from your last change, you wouldn't know if it got your current change.
Dear Frank,
thank you for your thoughts.
Regarding 2 and 3: You can set up your rule to send push messages on your mobile phone or e-mail when rule execute and also when rule finish. From there you can check how long the rule was running.
Regarding 4: Synchronize is necessary because you have to tell (exchange information) your Zipabox what rules to execute and what rules not to execute.
Dear Frank,
thank you for your thoughts.
Regarding 2 and 3: You can set up your rule to send push messages on your mobile phone or e-mail when rule execute and also when rule finish. From there you can check how long the rule was running.
Regarding 4: Synchronize is necessary because you have to tell (exchange information) your Zipabox what rules to execute and what rules not to execute.
Hi Mato,
Regarding 2 and 3: That's what I did now for debugging purposes but when I do that for all rules, my mailbox gets swamped with messages.
Regarding 4: I understand but by doing it "real time" so without the sync. At the moment I have an issue with a few rules after the sync. There are two rules that doesn't execute the commands after an IF puzzle. This is only at the first trigger (known problem). An other rule has an issue with not knowing that status of the virtual switch state. (State is on but the rule thinks it is off) After a few switch changing the rule works ok.
Hi Mato,
Regarding 2 and 3: That's what I did now for debugging purposes but when I do that for all rules, my mailbox gets swamped with messages.
Regarding 4: I understand but by doing it "real time" so without the sync. At the moment I have an issue with a few rules after the sync. There are two rules that doesn't execute the commands after an IF puzzle. This is only at the first trigger (known problem). An other rule has an issue with not knowing that status of the virtual switch state. (State is on but the rule thinks it is off) After a few switch changing the rule works ok.
Replies have been locked on this page!