This object is in archive!
rule for shutter - i get crazy
Need Answer
Hi there,
since days I want to create a simple rule like "open the shutters at 7:30 a.m.", but I cannot get it work.
Rules are accepted by the system and synchronized with the Zipabox, but nothing happens.
I am quite frustrated. I thought the rule creator is somehow self explaining .......
Is there anyone who can help me out with his rule or give me some tutorial advice?
Many thanks,
Oliver
The same question
No connection
Real-time notifications may not work
why don't you post a screen shoot of your rule here?
why don't you post a screen shoot of your rule here?
Hi again,
these are the last two versions I have tried. These might be too complicated ....
Any help his highly appreciated.
Regards,
Oliver
Hi again,
these are the last two versions I have tried. These might be too complicated ....
Any help his highly appreciated.
Regards,
Oliver
Oliver, your rules seems to be wrong.
What you need is to use scheduler as trigger and not in IF.
so
When (scheduler 1)
roller shutters position to 100
when (scheduler 2)
roller shutters position to 0
two very basic rules, scheduler 1 @7.30 and the repeat cycle you need.. scheduler 2 @20.00 and the repeat cycle you need to close the shutters.
Obviously you can add to these basic rules more conditions inside to avoid opening/closing in certain conditions and so on.
example:
When (scheduler 1)
if rain_sensor=true then ' if it is raining..
roller shutters position to 50 'half opening the shutters..
bedroom_light_dimmers to 50 'and turn on the bedroom lights to 50%
else
roller shutters position to 100 ' else.. full opening!
Hope this helps.
//////////////////////////////
Oliver, your rules seems to be wrong.
What you need is to use scheduler as trigger and not in IF.
so
When (scheduler 1)
roller shutters position to 100
when (scheduler 2)
roller shutters position to 0
two very basic rules, scheduler 1 @7.30 and the repeat cycle you need.. scheduler 2 @20.00 and the repeat cycle you need to close the shutters.
Obviously you can add to these basic rules more conditions inside to avoid opening/closing in certain conditions and so on.
example:
When (scheduler 1)
if rain_sensor=true then ' if it is raining..
roller shutters position to 50 'half opening the shutters..
bedroom_light_dimmers to 50 'and turn on the bedroom lights to 50%
else
roller shutters position to 100 ' else.. full opening!
Hope this helps.
//////////////////////////////
Many thanks! I will try the basic rules first and report if I am sucessfull.
Can I have more than one rule for a sensor / activator or do I need to have only one rule. E.g. can the basic ruls suggested been split in one rule for opening and another rule for closing (just as a simple example)?
Are the rules automatically implemented by the Synchronisation prozess or do I have to change some Settings, etc.?????
Many thanks again,
Oliver
Many thanks! I will try the basic rules first and report if I am sucessfull.
Can I have more than one rule for a sensor / activator or do I need to have only one rule. E.g. can the basic ruls suggested been split in one rule for opening and another rule for closing (just as a simple example)?
Are the rules automatically implemented by the Synchronisation prozess or do I have to change some Settings, etc.?????
Many thanks again,
Oliver
you can create multiple rules involving a single sensor. Obviously you need to understand that change, example, a switch status in more that one rule .. maybe in conflict if rules are executed at the same time.. so unexpected results can be achieved.
you can also build a single rule with multiple triggers, then use if inside.. to change the required action.
example:
When schedule1 OR Schedule2 (rule executed on schedule 1 or schedule 2)
if rollershutter=100 'if rollershutter is opened...
rollershutter set to 0 ' then c lose it.
else
rollershutter set to 100 'else.. full open
After a rule cration/change you only need to sync.
The sync process simply upload on your box the result of rules building process.
you can create multiple rules involving a single sensor. Obviously you need to understand that change, example, a switch status in more that one rule .. maybe in conflict if rules are executed at the same time.. so unexpected results can be achieved.
you can also build a single rule with multiple triggers, then use if inside.. to change the required action.
example:
When schedule1 OR Schedule2 (rule executed on schedule 1 or schedule 2)
if rollershutter=100 'if rollershutter is opened...
rollershutter set to 0 ' then c lose it.
else
rollershutter set to 100 'else.. full open
After a rule cration/change you only need to sync.
The sync process simply upload on your box the result of rules building process.
First success due to your help - many thanks!!!!!
So now I have a base to try some more.
@Zipato-Team: A basic manual for the rule creator will help much to decrease the frust level. I was near by to send my Zipabox back to Amazon ......
Regards,
Oliver
First success due to your help - many thanks!!!!!
So now I have a base to try some more.
@Zipato-Team: A basic manual for the rule creator will help much to decrease the frust level. I was near by to send my Zipabox back to Amazon ......
Regards,
Oliver
Also I can't get even simple time based on/off rule created. Something on at 21:00, and off at 23:00. When Time _____ between 21:00 and 23:00... What it want to first field _____ ? Time is invalid, Now is invalid, date has not every day option...
Also I can't get even simple time based on/off rule created. Something on at 21:00, and off at 23:00. When Time _____ between 21:00 and 23:00... What it want to first field _____ ? Time is invalid, Now is invalid, date has not every day option...
Use the scheduler puzzle for this.
Use the scheduler puzzle for this.
Hi,
try to make two single rules first. These ones work fine.... see attachment.
Hi,
try to make two single rules first. These ones work fine.... see attachment.
Replies have been locked on this page!