Chatty zen72- better rule in RM?

[MD617]

hi

on C8 Pro version 2.4.3.164. I have 1 rule associated with this Zooz Zen72 dimmer (using Jeff Page's advanced dimmer driver). Seems pretty basic but noticed a lot of msg on the zwave details page. Rule works perfect since inception awhile go.

1.) does the higher message on zwave details page matter? about 4x the next "chatty device"

2.) If it does matter, should the rule be updated to reduce noise? private boolean?

All other zwave devices work great, more curious why this one device had more noise.

[hydro311]

Your rule is firing every time the sensor reports active, which (depending on the sensor) could be a lot...

Using a Private Boolean (or similar approach) to prevent the rule from firing with every activation would very likely help.

[MD617]

Not familiar with the PBs, but did some research on prior posts. does this look to be the right way to use it and eliminate noise? Do i need a set PB back to true at the end of the first IF and ELSE IF? or is it all set given its there under the ELSE section?

[hydro311]

Yep, the last action in the rule needs to be "Set PB = True" -- that's clutch to all this.

Although leveraging the PB via Req'd Expression should work totally fine, RM's original architect (Bruce R) suggested that using it instead as a condition for the Trigger (i.e. as a Trigger Conditional) was a more sure-fire method to ensure the PB's effectiveness. That change isn't necessary here for you, but food for thought.

But otherwise, I think that overall setup there should work better!

[MD617]

since you suggested best practices, updated it to below and works perfect- thank you!

[pseudonym]

Since your Waits and Offs are the same you can simplify your rule like this:

IF (Time between 6:15 and 8:00 AND...) THEN
   Dim: Kitchen Lights  99...
ELSE-IF(time between 8:00 and 11:00 AND...) THEN
    Dim: Kitchen Light:  30...
END-IF
Wait for Event: Kitchen Motion sensor motion is inactive and stays that way for: 0:03:00
Off: Kitchen Lights
Set PB True

I'm suggesting Wait for Event instead of Expression since you're waiting for the same sensor that triggered the rule. If it was a different sensor than the triggering sensor, I would suggest using Wait for Expression, but this is a personal preference as both will work in your case.

[hydro311]

Sage inputs from pseudonym above, as always!

I should've been more specific about the Trigger Conditional thing (although what you have now should also work fine).

If you click down into the Trigger, you'll see this option... Selecting it allows you to use "PB = True" as a Conditional for each trigger event.

I'll be honest - I myself am not sold on this approach being broadly preferable to (instead) using "PB = True" as a Req'd Expression (RE)... There's no way I'd question Bruce R's expertise, and it is possible that under certain circumstances, the condition's evaluation is more effective/timely at the trigger-level vs RE, but I'd contend such circumstances just aren't terribly common.

To me, using the PB = True in the RE makes better overall sense, since then I'm not still evaluating the Trigger every time (seems kinda inefficient), but in reality at the end of the day, both approaches are effectively a wash (in most circumstances, anyway).

[MD617]

thank you both- updated to the below, works perfect! Thought I had a good grasp of RM, have a lot to learn.

[hydro311]

Love it -- there's always more to learn (for all of us), and rarely ever one way to skin the cat.