I updated to .157 last night when the required expressions were false. Following this statement I didn't update or Done
With the required expression true for all of the rules, the curtain closed and the lux value outside dropped below 50 but neither triggered the Hub Variable to false - the rule didn't trigger at all. The rule:
The logs show the required expression going false around 8PM and nothing else.
I have 4 rules for 4 rooms (Dining, Kitchen, Study, Dressing Room) and none of them triggered. I'll have to turn on the logs for all of those rules and the respective curtains/shades.
I ignored that and I did get a screenshot of the rules event subscriptions this morning while the RE was true. I updated last night to .157 and screenshot the event subscriptions this morning:
They are at 8AM this morning. It worked and set the hub variable diningDark to true. The issue is that this evening it didn't trigger when the curtain was closed or when the illuminance fell below 50 (20:04:29 - the required expression went to false for the rule but thats it, no other actions). It seems to have worked in one direction but not the other.
The illuminance values are shown in the logs only after the required expression that references illuminance goes to false. It should've triggered at 20:04 and set the diningDark boolean to true but it didn't. As the required expression went false, the closing of the curtain at 20:13 couldn't trigger it.
Here are the events for the curtain that show that it closed at 20:13 (irrelevant as the RE is false at that point):
The rule is set up so that whatever happens first - illuminance below 50 or curtain closing will set the diningDark to true. Likewise in the morning when the illuminance rises it will set diningDark back to false if the curtain is open, otherwise it will wait until the curtain opens before setting it to false.
But 20:13 is after RE is false, so of course no events for the triggers then.
I have a rule similar to yours. It logs every event for the RE state changes. And it works for shade closing. Leaves me at a loss for what to say about your rule and those logs. If it were my rule that didn't work as expected, I'd troubleshoot by creating a new simpler rule that isolates just the parts that seem wonky. The fact that you are missing obvious logs is concerning. Can you track down the illuminance event that must have happened at 20:04:29?
Nothing has changed with the illuminance sensor (Fibaro Motion with HE driver). I know that as I have the lux value from it overlaid on my camera feed and can see it throughout the day updating every minute or two)
Something's seems wonky, but you can't show what it is. Without something to go on, I can't help. I'm open to looking at evidence of something not working, but so far that's not the case here.
Understood. What is baffling to me when I look at the events page for that 'external multi sensor rear' is that it is working normally but the earliest illuminance event is today - 10 lux, then it reports 9,8,7 etc down to zero. There are no earlier events for today or the previous day for illuminance though there are for battery and temperature.
I've just had a look at another identical sensor (Fibaro motion using Hubitat driver) that is in the Study and it's the same there. You can see I've been getting illuminance reports only from 19:26 this evening - nothing before that and nothing yesterday:
Have there been any changes to the Fibaro motion sensor driver over the last few builds. It would be strange for multiple sensors to start playing up on the same day...
I'd say you have other problems and other explanations to be had for things not working as you expect.
I have no idea about drivers and updates to them.
Please follow my advice and do some troubleshooting. Create a small rule that isolates whatever you think isn't working, to determine whether it is working or not. This takes less time than writing one of these posts. Possibly use a virtual device instead of a Fibaro, so you can force it take any value you want. If that all works as expected, that might point a finger at the Fibaro.
Will do, I've little choice as lights aren't working without manual intervention. I've just checked and the reason those values are missing from the device events is that the events page only holds 11 events of each type as per the preferences.
The illuminance passes 50 and the only thing that happens is that the required expression goes false - nothing else is actioned. The illuminance reaching 50 or below should both make the required expression false AND trigger the rule. It does not trigger the rule as can be seen in the logs.
I'll delete and re write the one rule in case it's some corruption that's occurred over the last couple of releases/fixes.
The only difference is I have two triggers, though I can't see why that would make a difference. I've deleted and rewritten 1 of the 4 rules so will know in about 20 hours whether it's just something went screwy somehow. I probably should've just tried that a couple of days ago as it takes minutes.
