OK, I just put up a fix for that flash, I hope. I haven’t tested this. Please do so. In theory, now when you set lightlevel to 0 it should change the color using the previous lightlevel, and then turn off — I hope! V1.2.1c on Github
Awesome. I’ll give it a try and report back.
That flash light fix is not working. It works the first time the light is activated via the rule but subsequent calls via the rule do not turn the light back on. I tried it about 15 - 20 times with the target lights in various states.
I reloaded the V1.2.1b code and it immediately started working again.
Also, this doesn’t bother me, but most light apps translate the 0 - 255 values to 0% - 100% values. I’m not suggesting you change this, just an observation.
You were correct. The timer did get reset once motion stopped. I was suspicious because the app used different wording for the two types of delay.
Thanks for all your work and quick responses!
1 Like
Not good! I have put it back. The flash shall remain for now. 
But, at least they should work right. V1.2.1d on Github
1 Like
Hey Bruce thx for all your hard work, this is truly amazing. I made some rules a few days ago and saw an option for physical override, now after the update I cant seem to find it. Also when selecting my actions, when I hit done they dont populate on the next screen. I have to go back into actions and hit done again to see them… Not sure if both of these have been discussed already and I just missed it. This is on a note 3 with android 5.0 Thx
I can also confirm that the Physical Override seems to be gone. I checked under ‘simple’ and ‘advanced’ views…
Sorry, I removed that feature because for many people it would not work, and cause confusion as to why it does or doesn’t work.
Instead, coming soon, will be a generalize disable feature, using a switch to disable a rule. With that, if someone wants to disable a rule using a physical switch, that would be easy. Stay tuned.
4 Likes
Hi all, I’m having some trouble getting the delayed ‘off after delay’ feature to work. This is what I have below, it looks pretty straight forward, but I don’t know why the switches won’t turn off after the delay period.
Do you have any other trouble with Rules based on your iPhone’s presence? What about your Goodnight trigger ? Can’t say for certainty, but if you are, the programming might not like the # or * in the name. Just a shot in the dark, but I’ve seen programming choke on operator characters in other platforms. If they work fine in other rules, then the next step would be to test the same rule, but turn off only a couple of things with delayed off and see if it reacts differently. That’s a lot of devices.
Thanks Colin, I actually have my iPhone presence sensor for almost all my other rules without any issue. The goodnight trigger is just an outlet switch that I use to activate the goodnight routine in ST and shortcut in Wink. That is it’s only function. I have a lot of lights on the 1st floor of my house, so I want to make sure they are all off when I go upstairs. Do you think there is a limit to how many ‘things’ that can be triggered in one swoop?
Every SmartApp is limited to 20 seconds of execution time. You could turn on Live Logging and see what’s going on there. 20 seconds is a very long time. Otherwise, there should not be a limit on how many devices can be used. Have you tried breaking this into a smaller set to see if that works?
Great Smart App. I think it has loads of potential. Unfortunately I have to be added to the list of people that had a rule fail at a certain time. Just as a proof of concept I attempted to have my Good Morning routine executed by Rule Machine at 7:30am. No dice. I had it restricted to Home and Night modes and I was definitely in Night mode this morning. This has never happened when the time condition was in the routine instead of rule machine. Any help or insight would be greatly appreciated!
Thanks!
Hi Bruce,
Firstly - its amazing the rate of progress here - i tried to set up a rule 2 days ago - couldnt find the right output but then bam - i come here and see you have already added it! It seems you are some sort of community mind reader!
I did however wonder if it is possible to have a condition comparison read the value of another input?
Eg have a temperature sensor value checked against another temp sensor? Currently you can set a temp sensor to check against a fixed value but id love to be able to say if sensor x is less than sensor y then do action Z.
My scenario being if a multi sensor temp value upstairs is significantly less than the value from my nest in the living room (which will be in line with my current heating need and can therefore change) do Z (notify me / extend or increase my nest temp etc). Im thinking of ways to get upstairs warm before bed and my nest can sometimes cut the house heating as the room it is in is very well insulated / has a room fire etc. I know the ideal solution would be to relocate the nest but for now that isnt an option.
Hope that makes sense and is perhaps possible?
Ant
I checked the log and the delay that should turn off the switches never activates. I tried creating a separate rule that would turn off these switches when mode changes to “Night”, and that worked, but that is in an entirely separate rule. I would like it to work within my “Goodnight” rule above. I’m really stumped at this point.
For debugging this you could do this:
Get the rule to fire, to start the 5 minute timer. Then go into the IDE, My Locations, bottom of page, List SmartApps; find the Rule under Rule Machine, and click on it. On the page that comes up, look for the Scheduled Jobs, and see what’s there. Please report back. You should see the turn-off job scheduled.
As you have no doubt figured out, this is not part of the design of Rule Machine. I’ll have to think about this. I understand what you want and why. Hmmmm…
Hi Bruce, I created the test rule and the scheduled task looks to be there and waiting.
I am waiting for it to execute.
It executed flawlessly…I will use this tonight to troubleshoot this issue I, if it occurs again. Ia appreciate all the help:grin:
If the timer is set in one mode and, as part of the rule, the mode changes and the “Evaluate only when mode is” is set to the mode before the rule changed it, will the rule still be evaluated?
In other words, does the “Evaluate only when mode is” apply to the original mode that triggered the rule?
“Evaluate only when mode is” is a hard condition, looked at before each rule evaluation. However, if you start a delay-on/off timer, it will still do its thing when the time is up irrespective of the mode. In that case, the rule was evaluated in the previous mode and started the timer.