Not all devices responding to web core piston

The other thing to check (mentioned in the article I posted) is if you have really old zwave devices (that don't report status like new ones), you may need to use zwavePoller

  • If you are using older zwave devices (and some zwave plus devices), these devices may not report physical switch state changes in a timely manner, so you may need to add a refresh in your pistons before checking state for conditions.
    • For triggers or conditions, Zwave Poller should be enabled for these older devices. This is due to ST vs. HE differences in handling of older zwave devices. If you choose Zwave poller, you won't need the refresh commands in you pistons: