This object is in archive! 
How to use "repeat" control in the rules creator?
Answered
Hi
I'd like to set up a rule to create a "luminosity wake-up function".
If I need to wakeup on 7am, I'd like to set my bedroom's light to 10% (intensity) at 6.30am, then increase it by 2% every minute so it would be at 70% at 7am when my wakeup alarm will ring.
I tried to use the "repeat" control (not the one in scheduler) this way (see attached file) but it doesn't work...the rule sets my light on 10%, waits 60 seconds, then increase it by 2% and then everything stops.
Could anybody explain me how to use the "repeat" control correctly please?
Files:
screen-capture-...
No connection
Real-time notifications may not work
We have a bug with repeat puzzle which we are trying to resolve ASAP. For desired effect please try following ( use example in attached picture for starting point).
We have a bug with repeat puzzle which we are trying to resolve ASAP. For desired effect please try following ( use example in attached picture for starting point).
Thanks!
I supposed it was a bug because I was pretty sure about how I was using the "repeat control".
I was thinking about your way to do it, but I would need to set 30 actions and 30 pauses as I want to increase light by 2% each minute ^^
Do you think it will be ok before a new firmware or can't you fix it without modifying the fw of the zipabox?
Thanks for support!
Best regards
Thanks!
I supposed it was a bug because I was pretty sure about how I was using the "repeat control".
I was thinking about your way to do it, but I would need to set 30 actions and 30 pauses as I want to increase light by 2% each minute ^^
Do you think it will be ok before a new firmware or can't you fix it without modifying the fw of the zipabox?
Thanks for support!
Best regards
During the time needed to fix it, you could use a Google Drive script, based on a Google Calendar event to generate multiple HTTP requests to a virtual meter of your Zipabox, that you would use to set the value of your light diming module.
Check out the UrlFetchApp class of Google Drive scripts
During the time needed to fix it, you could use a Google Drive script, based on a Google Calendar event to generate multiple HTTP requests to a virtual meter of your Zipabox, that you would use to set the value of your light diming module.
Check out the UrlFetchApp class of Google Drive scripts
I will, even if I can wait a few days/weeks for this fix...I wakeup normally everyday with my classic wakeup alarm even if the lights are off ^^
thanks ardillon!
I will, even if I can wait a few days/weeks for this fix...I wakeup normally everyday with my classic wakeup alarm even if the lights are off ^^
thanks ardillon!
Do you have any news about the "repeat bug"? ;)
Do you have any news about the "repeat bug"? ;)
The repeat control still isn't working 2 years later...
The repeat control still isn't working 2 years later...
I'm also trying to use repeat to create a flashing light for n times. The repeat block worked one time over 20.
I'm also trying to use repeat to create a flashing light for n times. The repeat block worked one time over 20.
How is the "repeat" rule comming? I cannot see this working?
How can i get a rule to run once every X min without it?
How is the "repeat" rule comming? I cannot see this working?
How can i get a rule to run once every X min without it?
Jørgen, you should be able to do that with the scheduler (run something every x minutes).
I only use repeat in one rule, and it works. The rule sounds a short notification sound every 2 seconds, for 20 seconds when I ARM my security. I use it for a countdown to get outside before the alarm is activated.
Long waits in repeat loops does not "sound right" to me (although it should work)
Jørgen, you should be able to do that with the scheduler (run something every x minutes).
I only use repeat in one rule, and it works. The rule sounds a short notification sound every 2 seconds, for 20 seconds when I ARM my security. I use it for a countdown to get outside before the alarm is activated.
Long waits in repeat loops does not "sound right" to me (although it should work)
Well, you could use the repeat function in the scheduler... if it worked correctly. In my case, it certainly doesn't. I have one rule set to repeat every 30 minutes, and it runs once per day instead. Another set to run every minute clearly isn't working either. It's a little alarming that such basic features don't work correctly, and even more alarming that they are taking so long to fix them.
Well, you could use the repeat function in the scheduler... if it worked correctly. In my case, it certainly doesn't. I have one rule set to repeat every 30 minutes, and it runs once per day instead. Another set to run every minute clearly isn't working either. It's a little alarming that such basic features don't work correctly, and even more alarming that they are taking so long to fix them.
Hello everybody,
May I suggest a solution ? Maybe you can add a block "linked" to your rule.
I had the same problem with this repeat function. My need was to receive a push message each 10 minutes when the battery of my security module was charging (it means that I have a power failure at home).
It seems that although the limit of number of repetition, the rule is executed each time the condition is verified within the 600 seconds. This afternoon I received 50 push messages i/o the 5 requested with this own rule without refreshing any status...
The rule attached is working fine
Hello everybody,
May I suggest a solution ? Maybe you can add a block "linked" to your rule.
I had the same problem with this repeat function. My need was to receive a push message each 10 minutes when the battery of my security module was charging (it means that I have a power failure at home).
It seems that although the limit of number of repetition, the rule is executed each time the condition is verified within the 600 seconds. This afternoon I received 50 push messages i/o the 5 requested with this own rule without refreshing any status...
The rule attached is working fine
Replies have been locked on this page!