I have a Homeseer Dimmer that does not report physical presses.
If I digitally refresh from the devices page it picks up the changed status.
I can't use the Z-Wave Poller app because it's not offered as a device choice.
And I can't do a refresh within RM before running my Conditional actions? At least if I try adding the Refresh after I'd already crafted my "If Then" statements. Is this a software bug?
I'm going to start from scratch with my Rule and see if that changes things.
EDIT: Ok, that did not change things. Why are only some devices shown under the "Refresh" action?
If the Dimmer and Outlet are both on via digital and the button is pressed... both go off
If the Dimmer is on via Physical and the Outlet is on via digital and the button is pressed... then only the Outlet goes off, a second press of the button will turn the Dimmer off.
I don't see anywhere in your rule where you are testing physical vs digital events. I also am not sure why this matters for your use case, so some explanation might be helpful. Along those lines, where does the HomeSeer device that doesn't report physical vs digital fit into this, and how does a refresh help with that? I can't think of any reason it should, and on a HomeSeer, you shouldn't need to worry about triggering off a physical event since you could just do it off the button events instead that they generate from physical taps, assuming you never generate those "digitally" (technically possible now with most drivers but probably not widely used).
That being said, your rule doesn't seem logically flawed (though I do still have the concern above). However, it might be easier to read and edit if you used ELSE-IF instead of a bunch of nested ELSEs and IFs.
The "testing" is me going up to the room and physically turning the switch on, which is the most common use case for this light. There are two lights in this room, a ceiling light controlled by the dimmer switch, and a table lamp controlled by a Zigbee outlet plug. My wife will come into her room, turn on the physical light, then turn on the table lamp, and then fall asleep. She's one of those annoying people that can fall asleep in less than 2 minutes. I'm hoping a simple button right next to her head might be close enough that she'll turn both the lights off before she herself turns off.
I don't know why changes done at the physical switch are not reflected in HE, not on the dashboard and not in this rule, but the Custom Action has at least made it workable for the rule. I've actually got newer Z-wave devices that respond this way in HE as well, and it drives me nuts.
The Aqara Button works for about 15 minutes and then falls off the Zigbee mesh. Zero excuse for it as I have 5 Sinope Zigbee T-Stats within 10-15ft of the button, but that's another issue entirely I'll tackle next.
I'm hoping a simple button right next to her head might be close enough that she'll turn both the lights off before she herself turns off.
