Zooz Zen25 Firmware issues / Rebuild Routes failure?

Configuration Z-Wave
1

I performed the Firmware upgrade for the Zen25’s that showed up about a week ago… And I’m working with Zooz support trying to resolve the firmware issues.
(I suspect that this thread solves those problems - Zooz ZEN25 firmware update bricked plug? - #8 by Tomek985).

But they asked me to Heal the Network, and it appears that got renamed / rebuild as “rebuild routes”?

Well, I did that, but even after rebooting, my Zen25 nodes keep coming up in the log:

2024-04-09 15:07:16.103 INFO Z-WAVE: [Node 077] Value updated: 50-0-value-66049 0 => 0
2024-04-09 15:07:18.846 INFO APP: GET /health/zwave 301 1.505 ms - 191
2024-04-09 15:07:30.484 INFO Z-WAVE: [Node 078] Metadata updated: 50-0-value-66049
2024-04-09 15:07:30.489 INFO Z-WAVE: [Node 078] Value updated: 50-0-value-66049 0 => 0
2024-04-09 15:07:31.414 INFO Z-WAVE: [Node 079] Metadata updated: 50-1-value-66049
2024-04-09 15:07:31.420 INFO Z-WAVE: [Node 079] Value updated: 50-1-value-66049 74.3 => 74.2
2024-04-09 15:07:31.507 INFO Z-WAVE: [Node 079] Metadata updated: 50-2-value-66049
2024-04-09 15:07:31.512 INFO Z-WAVE: [Node 079] Value updated: 50-2-value-66049 0 => 0
2024-04-09 15:07:31.604 INFO Z-WAVE: [Node 079] Metadata updated: 50-0-value-66049
2024-04-09 15:07:31.609 INFO Z-WAVE: [Node 079] Value updated: 50-0-value-66049 74.3 => 74.3
2024-04-09 15:07:33.865 INFO Z-WAVE: [Node 076] Metadata updated: 50-1-value-66049
2024-04-09 15:07:33.869 INFO Z-WAVE: [Node 076] Value updated: 50-1-value-66049 0 => 0
2024-04-09 15:07:33.960 INFO Z-WAVE: [Node 076] Metadata updated: 50-2-value-66049
2024-04-09 15:07:33.965 INFO Z-WAVE: [Node 076] Value updated: 50-2-value-66049 0 => 0
2024-04-09 15:07:34.056 INFO Z-WAVE: [Node 076] Metadata updated: 50-0-value-66049
2024-04-09 15:07:34.061 INFO Z-WAVE: [Node 076] Value updated: 50-0-value-66049 0 => 0
2024-04-09 15:07:39.192 INFO Z-WAVE: [Node 080] Metadata updated: 50-1-value-66049
2024-04-09 15:07:39.197 INFO Z-WAVE: [Node 080] Value updated: 50-1-value-66049 0 => 0
2024-04-09 15:07:39.287 INFO Z-WAVE: [Node 080] Metadata updated: 50-2-value-66049
2024-04-09 15:07:39.291 INFO Z-WAVE: [Node 080] Value updated: 50-2-value-66049 0 => 0
2024-04-09 15:07:39.384 INFO Z-WAVE: [Node 080] Metadata updated: 50-0-value-66049
2024-04-09 15:07:39.389 INFO Z-WAVE: [Node 080] Value updated: 50-0-value-66049 0 => 0
2024-04-09 15:07:45.702 INFO Z-WAVE: [Node 077] Metadata updated: 50-1-value-66049
2024-04-09 15:07:45.707 INFO Z-WAVE: [Node 077] Value updated: 50-1-value-66049 0 => 0
2024-04-09 15:07:45.902 INFO Z-WAVE: [Node 077] Metadata updated: 50-2-value-66049
2024-04-09 15:07:45.909 INFO Z-WAVE: [Node 077] Value updated: 50-2-value-66049 0 => 0
2024-04-09 15:07:46.099 INFO Z-WAVE: [Node 077] Metadata updated: 50-0-value-66049
2024-04-09 15:07:46.105 INFO Z-WAVE: [Node 077] Value updated: 50-0-value-66049 0 => 0

(To be clear, nodes 76-80 are the Zen25’s… )

Now, I’ve rebooted, and even shutdown HA… And this continues to persist?

Am I misreading normal traffic as continuous “Rebuild” attempts? How can I stop this, if it needs to be stopped? The Rebuild Routes “Stop” button doesn’t seem to do anything.

Am I misattributing this?

2

Yes. I believe it’s just reinterviewing the device. I see this all the time during startup and during a reinterview.

3

Those are just meter reports. I would guess 66049 are watt reports, the default for this device is to report power consumption every 30 seconds, which you can see is the case for Node 77.

Not sure what help you’re actually looking for, but I recommend dialing those report intervals to a longer interval, or disable it completely and rely on percentage changes. Continuous meter reports are a big contributor to unstable networks.

https://zwave-js.github.io/node-zwave-js/#/troubleshooting/network-health?id=optimizing-the-reporting-configuration

4

Ah. Only on a few of the units, 76-112-0-3 - Power (W) Report Frequency was set to 30. That appears to be the default, I’ve set it to 300… The Current, Voltage, and Energy reporting was set to 300 by default.

Very interesting.

Thanks for clarifying what I was seeing!

5

Just an FYI – Increasing the reporting to 300, did seemingly help. It’s not perfect, one of them locked up again today, but a popo (Power Off Power On) brought it back online again…