Simple Piston help

[T-rav]

I have used webcore for a few years in Smartthings and now have migrated to Hubitat.... the simple piston below will not turn off all of the mentioned lights. It worked flawlessly in ST. Not sure what I'm missing.
Basement lights 1&2 are both dimmers while #3 is just a standard zwave switch. I can control them thru the dashboard so I know they all are allowed or connected. I've approved them all in the Webcore App... It seems that it will turn off #1 & #2 but not 3.

any ideas?

[Eric.C.Miller]

I think the posting limitation is because you are new to the forum.
I believe the solution is for you to join the Hubitat Owners group . . . Hub owners - Hubitat

@bobbyD

[nh.schottfam]

Couple of things (once sorted out to post images):

[Wiki] webCoRE Documentation Digest

Reporting issues if you want piston help, the webCoRE forum is also a resource with folks that can help on writing pistons if you believe there is a webCoRE bug or feature request see below: You can use a private message, start a new topic, or add to the main webCoRE on HE thread (PLEASE DO NOT POST IN THIS THREAD BUG REPORTS) Desired information: 1) Give a description of the problem I got a new motion sensor and thought I’d try to have my bedroom lights turn on as I’m heading to be…

How to use stays* in webCoRE

In webCoRE there are several trigger comparison types around stays: stays stays equal to ... Stays means we want to check in the future if things stay the way they are now So what is going on: [staysopen] Let's assume the starting state is we have not run since saving and the contact is open In this example the piston is subscribed to the vctl1:contact events If I hit the 'test' piston in the IDE, the piston runs: First execution the test event wakeup occurred, and we began exe…

[T-rav]

I've now attached the image to the original post... 10 seconds is just for testing purposes. The 2 dimmers(#1 and #2) execute fine but #3(switch) does not turn off. It does work if manually toggled on a dashboard.

[nh.schottfam]

Can you show Minimal or Medium logs for the piston execution?

One of my links above shows what to do for that

[T-rav]

I read through the link and I have been out of the game/loop for some time because alot of that stuff I didn't grasp the progression of running through the piston multiple times. Must be some newer features that I haven't used since first using WebCore when it was first developed.

This run #1 didn't turn off as well as #3 and both indicated they were skipped because it would cause no change.... its like the status isn't being reported correctly. They were both on and remained on when the piston ran. I removed and re-added the devices but that didn't make any difference either.

[T-rav]

I just hit refresh a few times and now the piston ran properly. I've narrowed it down to the device status isn't be updated properly in Hubitat when the switches are manually pressed. Any idea what would cause this? If I manually turn the switch on and check the status in the hub it still says off. If it toggle it on through the hub interface it changes the status appropriately.

[eibyer]

Might be related to this if you have older zwave devices.

Device status not updated when switch is physically toggled

I have GE Z-Wave switches and dimmer switches in my house. I have noticed that if I turn them on or off at the physical switch, the device status is not updated in HE. Is there a way to get this to work properly? Device type for the switches is Generic Z-Wave Switch and for the dimmer switch is Generic Z-Wave Dimmer.

[T-rav]

Thanks for that, I'll check it out. The devices are quite old... like 7 or 8 years old already.

Edit: Fixed with the built-in poller app... I had to replace one of the dimmers in the last 3 yrs so that one wasn't having the issue but the other 2 are the original GE switches that I purchased. Thanks again. Odd that I never had an issue on SmartThings.

[thebearmay]

@T-rav

never had an issue on SmartThings.

Smartthings polled everything whether it needed it or not, Hubitat takes the opposite approach and defaults to not polling as the ZW+ devices do not require it.

[jens]

You need something to trigger the event.

If any of the Light 1-3 change to on.. The keyword is that it needs a trigger, and that will be change

[T-rav]

Gotcha. I was not aware of that. Good to know.

[michicago]

For pistons with... stubborn devices like that, you can also disable command optimization for your piston. With that disabled, webcore will send an Off command even if webcore believes it's already off.

You can access it by editing your piston, clicking the piston name at the top, and disabling command optimization in the settings.