First attempt, did some searching but this seems so basic it should work (but it doesn't seem to).
Attempted rule: IF hue motion sensor detections motion THEN turn on group KitchenHobLights (IF luminance <10); IF hue motion senor inactive for 5 min THEN turn off. (basically the rule explained on youtube by hubitat staff, but with one single variation of luminance value).
I attempted to add the necessary screenshots for the below but I get this brilliant "can't embed media items in a post".
The rule as shown on screen:
When Hue1 activates ...
Turn on KitchenHobLights
Wait until Hue1 motion stops and stays inactive for 1 minute, then ...
Turn off KitchenHobLights
Present luminance
Luminance rule, if =>10
Optional restriction on the rule builder screen
Known to all, you hit this one to add a restriction
The optional restriction
The restriction screen where I first input >50 and on a second attempt >10
Optional restriction after clicking done
When you click "done" after adding the value in step 4. , you get stuck in the optional restriction dialog with only a cancel button (bottom right hand corner) - no way out.
The problems I have are:
The lights turn on, but never off. After a while, I see the following in the logs evt: "Hue1 motion stayed inactive, wait over", but nothing happens, next event is act: Wait Until, after that I only see events like Hue1 illuminance is 13 Lux
Even with a luminance that is significantly above treshold, the lights still turn on on detection of movement
After adding this value for luminance and clicking done, you get stuck on a screen where the only button is "cancel" . There is no way out, and if I get out by going to the apps dialog, the rule on the screen never shows the condition related to luminance being added.
I tried another browser (first firefox then safari), makes no difference.
Welcome aboard. You can overcome this restriction by joining the "Owners" group (Hub owners - Hubitat).
Do you mind sharing the app name, the browser used and the hub model?
I am pretty sure this was probably a typo, but you've mentioned that your condition was "IF luminance <10" but in your details you mentioned if =>10, >50... Did you use greater or lower? Sharing screenshot of the rule may help, so when you have a chance, please join the owners group.
Required Expression: luminance equal to or less than 10
Triggers: Motion sensor active, Motion sensor inactive and stays for 5 minutes
Action:
If motion, turn on kitchen lights
else, turn off kitchen lights.
Thanks for your reply, I added myself to the group.
Rule only runs when luminance is equal to or lower than 10 (I first tried with 50). (in other words, if dark enough, the rule runs)
Running firefox on MacOS13.5.2 Hub version 2.3.5.152;
Using basic rule app
It seems clear that the luminance condition is never taken into account because it doesn't appear in the condition at the top.
even if the luminance condition is "hidden" in there, the light still doesn't turn off for this very stupid/simple rule; I don't think the luminance condition can cause this to happen
I appreciate being able to use other rule sets - but nevertheless something as basic as this should work no?
I was also going to suggest Motion Lighting. I probably have 20 ML rules, some using illuminance. It works perfectly, but I use 2 of my Hue outdoor motion sensors (that aren't under an outside light source) for lux measurement and average them into an "average outdoor lux" device for using in the ML rules.
Having a spot of bother with the edits. Anyway, I would like this basic rule problem resolved. Telling me to go somewhere driving backwards is fine, but I would like to fix driving forwards first ...
Thank you, that resolves it. Guess this is as intuitive as SAP ... Will have to get used to the idiosyncracies. Also resolves the issue of not getting out of the dialog. Kind regards, G.
Can you try Chrome? Firefox may be the problem, as it doesn't look like clicking "Done" actually saves the luminance restriction. Here is how the rule should look if the restriction was active (I tried with Chrome and didn't experience the same issue):
I guess i need to step out of this discussion as I didn't even know Basic Rule app even exists...
Most of my Rules are still In Rules 4.0 format. These guys created to many ways to do the same thing, and all three ways are a solution to the same issue
