@bcopeland I just ran the test again, but I also turned on trace logging for the ZEN30. I am using the driver from @jtp10181.
In a nutshell, I am seeing a 553MS delay between when the hub receives the z-wave message and the driver is notified. The 2 key log entries from this test cycle that drive that conclusion are:
Z-wave log: 2025-12-04 02:38:36.218 PMCNTRLR [Node 041] [!] [Central Scene] scene[001]: 0
Driver log: dev:1898 2025-12-04 02:38:36.771 PM info Garage Exterior Lights: button 1 pushed [up 1x]
I suspect this is the source of the additional delay I am seeing when I use the ZwaveJS stack vs. the legacy z-wave stack.
Marc
@support-agent @bobbyD, I would like to get help from Hubitat Support in resolving this issue. I am summering the issue in this post so you do not have to digest the entire thread.
Let me start by acknowledging that the focus of this thread has shifted from the z-wave crash, which has not happened in several days, to the noticeably increased lag I am experiencing when using the ZwaveJS stack vs. the legacy stack.
It's been over 36 hours since I moved to ZwaveJS stack, so I assume the interview process is over. I am still experiencing perceptible lag.
I am going to net-out a lot of the log info.
From the z-wave logs: 2025-12-06 07:17:14.410 AMCNTRLR « [Node 041] received CentralScene notification { - "nodeId": 41, - "ccId": "Central Scene", - "ccCommand": "0x03" - }
From the hub logs: app:1696 2025-12-06 07:17:14.964 AM info Event: Garage Exterior Lights pushed 1
Based on those time stamps, there is a 554ms delay between receipt of the event by the hub and the event being delivered to the rule.
This means that the lag is not caused by z-wave problems -- it is caused by delays in delivering the event to the rule. While I do not have the same measurement for the legacy stack, the user experience is that there is virtually no perceivable delay when using the legacy stack. It is quite noticeable with the ZwaveJS stack.
My conclusion is that there is a material performance degradation on delivery of events to rule machine when using ZwaveJS vs. the legacy stack.
My hub is a C8-pro running platform version 2.4.3.158.
Thanks!
Marc
The rule is:
The z-wave crash has been resolved by replacing the power supply.
I have created a separate thread about the lag issue I am experiencing with ZwaveJS: Is anyone else experiencing a ~500MS delay when running ZwaveJS? - 
Get Help / Devices - Hubitat
Marc
