No, that means the rule is probably working. You said you wanted the switch to turn off after 2 seconds. Try pausing the rule and controlling the plug manually from the edit device page.
mmmm.... I am not sure... I'll do some more experimenting.
I no that when I push ON or OFF on ANY of my Peanut plug devices (via the hubitat page).... the Status does not update. That seems odd to me... and maybe bad?
I know the rule is definitely not turning off the plug in 2 seconds.... I've tested that with a lamp....
Yes, your rules won't run correctly if the device state doesn't update correctly.
Rule - has conditions. Changes to any of the conditions will cause the rule to be evaluated. Actions will only be executed if the rule changes from True to False or vice versa. If rule changes from True to False, False actions are executed. If rule changes from False to True, True actions are executed.
Trigger - can have multiple triggering events. Actions are executed any time one of the triggering events occurs.
Triggered Rule - can have multiple triggering events. At the time a triggering event occurs, the rule is evaluated. If the rule is True, True actions are executed. If the rule is False, False actions are executed.
In your case, I would use a trigger for simplicity. You don't care about True/False state, you want the plug to turn off every time it's turned on. However, your normal rule that you have set up should also function the same way in this case, so it shouldn't matter if you have a Rule or Trigger for this particular thing. You do not need a Triggered Rule though.
Have you clicked CONFIGURE on the Peanut Plug's Device page? This tells the plug how to report status changes.
1 Like
Have you paired the plugs to HE or created devices manually in HE?
HI @Ryan780 - I paired the Peanut's with HE
Hi @ogiewon, yeah- I've pushed CONFIGURE but nothing happens.... I was wondering about that... should something pop up?
Wow- what a community. Thanks!
Did you disable your auto off rule? Did you try turning on and off after hitting configure?
Oh my goodness.... it works now....
Once I hit the configure button on the peanut plug -- even though nothing seems to happen visually... then the device page "status" updates properly when I push on or off.,, AND my auto off rule works. Sweet!!!
So this is a little weird to me then still... Whenever I pair in a new device I need to push "configure" I guess? What does that actually do and why doesn't it happen when the device is paired and more importantly... does it ever need to be done again?
So many questions... thanks so much.
1 Like
You have to do it once after the device is paired.
It initiates the configuration between HE and the device.
You shouldn't have to do it again but it's the first thing I try if a device isn't responding.
2 Likes
In addition to what Ryan mentioned above... When you press CONFIGURE on a device, it usually sliently sends either Zigbee or Z-Wave configuration parameters to the device. These parameters tell the device how they should behave, including how to report status updates.
Normally, when you pair a device, if the correct driver is automatically assigned, the configuration parameters will be sent without need for user interaction. If you manually change the driver that a device uses, you'll want to click CONFIGURE after you save the device with the new driver.
3 Likes
Hi all! New to the Hubitat Community, and excited to be once again working with a SERIOUS HA Hub after playing with all of the other web-based "toys" out there. I really like what I see so far!! I'm trying to do the exact same thing with a towel warmer, turning it "OFF" 4hrs after it has been turned ON (with Leviton Z-Wave Switch. This trigger logic seemed simple enough, but for some reason, will only work when the switch is turned on with Hubitat (which will never happen), When it's turned on locally with the switch though, the OFF never happens. Any thoughts on what I'm doing wrong? I also tried setting the trigger to "Physical Switch Turned On" but that had no impact on the outcome. Appreciate your thoughts. Thanks!
I believe some of the Leviton Z-wave switches need a firmware upgrade to properly report physical switch status changes. Search the community and Iām sure youāll find some threads.
Thanks! I was actually thinking the switch may not be reporting back, but it seems to be. When I look at the switch within devices, it always shows the proper status, whether it was turned on / off from the physical switch or dashboard switch. So, I don't think the switch reporting is the issue. Then I thought I may need to poll the switch every 10mins or so, but that seems to be counterproductive.
Please share a screenshot of your rule that is supposed to turn it off automatically. Perhaps the clue lies within?
Ok. I just created a very similar Trigger in RM, after updating my hub to the latest firmware (I am assuming youāre running the latest as well.). It worked perfectly. (Note: I am using Lutron Caseta switches and dimmers, not Leviton Z-Wave. )
Here is what the RM Trigger looks like
Here are the logs
[dev:2027](http://192.168.1.144/logs/past#dev2027)2019-05-04 04:00:15.496 pm [info](http://192.168.1.144/device/edit/2027)Kitchen Table was turned off
[app:2183](http://192.168.1.144/logs/past#app2183)2019-05-04 03:59:58.332 pm [info](http://192.168.1.144/installedapp/configure/2183)Screened Porch Light: Screen Porch Environment Sensor illuminance 7482
[app:2469](http://192.168.1.144/logs/past#app2469)2019-05-04 03:59:45.400 pm [info](http://192.168.1.144/installedapp/configure/2469)Test Auto Off Triggered
[app:2469](http://192.168.1.144/logs/past#app2469)2019-05-04 03:59:45.214 pm [info](http://192.168.1.144/installedapp/configure/2469)Test Auto Off: Kitchen Table switch on
[dev:2027](http://192.168.1.144/logs/past#dev2027)2019-05-04 03:59:45.121 pm [info](http://192.168.1.144/device/edit/2027)Kitchen Table was set to 100.0%
[dev:965](http://192.168.1.144/logs/past#dev965)2019-05-04 03:59:44.915 pm [info](http://192.168.1.144/device/edit/965)rcvd: OUTPUT,9,1,100.00Well, I REALLY appreciate you doing that to test my logic! Really appreciate the confirmation, but now I need to figure out what's going wrong in my setup. Obviously not in a position to change out the Leviton switches (15+ throughout our home). Never had a problem with this auto shut-offf routine when using Wink and while that wasn't nearly as powerful of a hub as HE, I've got to believe it got it's switch status the same way.
So, if anyone else has an idea of what else I could try as a workaround, I'd appreciate hearing about it!
1 Like
I wanted to follow up on this issue, and advise what was causing the problem. First, thank you for your feedback, and actually taking the time to try to emulate the issue on your home system! That went above and beyond! So... it seems the problem is that my Leviton switch is not Z-Wave plus, so it isnāt reporting back status when the switch is activated locally. Therefore, the action that I was expecting to trigger the turn-off 4hrs later was never reported to the HE hub. After further research within the community, I learned that there is a Z-Wave polling app, and that it can be used to selectively poll certain devices. Since this is really the only device where I absolutely need to know status, Iām only polling this one, hopefully minimizing network traffic. Now, RM is working like a champ, and behaving exactly as exactly as expected.
Thanks again to the community for the help provided!
2 Likes
Glad to hear you have found a solution! I would say that Z-Wave (non Plus models) switches and dimmers not reporting physical status updates has to be one of the most reported issues on Hubitat. I am glad the Z-Wave Poller App is addressing the issue for now.
