Update to zwavejsui today seems to have broken my BE469ZP lock

[obtuse bramble]

I'm pretty sure that the "fix" in https://github.com/zwave-js/zwave-js-ui/issues/4421 has broken my lock. I just updated zwavejsui to the latest in the addons repo (6.0.0) and it prompted me to "reinterview the device, because some stuff has changed".

I did this, and now my device is "unknown 0xXXXX" and in home assistant it's missing most of it's properties and sensors. The other lock (identical) wants to reinterview according to the UI, but currently is NOT broken, so I'm not going to do that yet.

I suspect that somehow reinterviewing is broken. I have tried doing a refresh and a reinterview in zwaveJS and it hasn't changed anything really.

I have Driver logs from the zwavejsui container available..

Looking at these logs it seems that the controller is timing out almost instantly (less than a second?) after trying to do some interview stages...

The node in question is node 022. I have truncated to just before the upgrade began at 1225 or so. Note two restarts of zwavejsui in the log.

[solid estuary]

Try Z-Wave JS discord. https://discord.com/channels/1111193770935996459/1440004228914614435

[abstract dagger]

Changes to a configuration parameter don't break the communication with a device.