AlCalzone

> Or did you mean you still will need to re-interview the devices once upgrading to the fixed version (I restored a backup and downgraded so notifications are gone)? This....

For reference, here's the explanation why it was done: https://github.com/zwave-js/zwave-js/pull/7984 The urgency is one of `BatteryReplacementStatus.Soon | BatteryReplacementStatus.Now` I would actually not create a value ID for it. The whole...

> BTW I already show battery levels on UI, I don't know if this Is really necessary The point of these notifications is that each battery type is different. 20%...

I'll have to check the specs how this is supposed to work. I **think** there is some kind of network update procedure that needs to be triggered while the secondary...

What I meant is: if node 53 was not part of the network at the time ZUI joined as secondary controller, it should not have been reported to ZUI as...

Like I said, I'll have to look at the specifications to see which options we have and what can be done using a secondary controller. Including/excluding nodes is definitely possible,...

I can imagine what's going on there. The device probably has a simple linear function to estimate the battery level from voltage and happens to have worked below the level...

I double-checked. Formatting the messages happens outside of the transport format, in https://github.com/zwave-js/zwave-js/blob/266f47f49f804609d633313fe128a81c987732ff/packages/zwave-js/src/lib/log/Driver.ts#L113 We'd need to add an option `raw` to the log config in the driver options and evaluate...

None of the problematic nodes report any battery level but "battery low" in that log. Any chance you have older ones? FWIW, this is just for curiosity - the issue...

I've added the driver option in https://github.com/zwave-js/zwave-js/pull/8204