Note: I am splitting this post off from my original post about a Z-wave crash, as the Z-wave crash was resolved by replacing the power supply and this really is a different issue.
My hub is a C8-pro running platform version 2.4.3.158. I migrated to ZwaveJS and I am experiencing a ~500MS lag between pushing a button and lights going on. I do not experience this lag when running on the legacy Z-wave stack. I suspect the issue is somewhere in the ZwaveJS stack.
Is anyone else experiencing this type of problem and does anyone have any suggestions of what I can do to resolve the issue?
Thanks for any help or insight you can provide -- details below.
Marc
- Device information
- The "button" I am pushing is "up" on the paddle of a Zooz Zen30 double switch.
- The lights are wired to the relay of the same Zen30.
- The screenshot of the rule that turns the lights on is below. The rule consists of 2 actions and the first action turns the lights on.
- The environment
- Background noise is under -100, which is very good.
- The hub and switch are line-of-sight, about 23 feet.
- The migration was done ~48 hours before this test was run, so plenty of time for the "interview" process to complete.
- I am using @jtp10181's driver for the Zen30.
- I turned on z-wave logging, logging of the trigger for the rule, trace logging for the ZEN30 and added a log statement at the top of zwaveParse in the ZEN30's driver.
The result is that I am seeing a 510MS delay between hub receiving the "button 1 pressed" z-wave message and the log message I added to zwaveParse in the device driver:
2025-12-06 08:55:16.175 PM|DRIVER « [Node 041] [REQ] [BridgeApplicationCommand] - │ RSSI: -83 dBm - └─[CentralSceneCCNotification] - sequence number: 91 - key attribute: KeyPressed - scene number: 1
2025-12-06 08:55:16.685 PM trace Garage Exterior Lights: Marc add this msg at the top of zwaveParse
Delta: 685-175=510
The rule that is being executed:
