Just added a couple of Zooz ZEN76 switches in the past day. Something weird about the device name gets overwritten when I do a refresh.
I named the Device as Garage Coach New, saved it, went over to the ZWave details, new name was there, then did a device refresh and name was changed to ZEN76 some sort of generic name. Happened twice with two different devices.
Never seen this before and I have paired dozens of Zooz devices, This device is a new one though, Hardware Rev 4 and Firmware rev 4.0.
Don't know if it is Hubitat or the device misbehaving? Is device name even sent to the switch? I would guess not so I lean to Hubitat...
This new device is being named the same name as a prior device since deleted. If I name the new device Garage Coach Lights2 then this problem doesn't occur. Something about using a recent name on a new device the system doesn't like...
Must be something persistent about the old device hanging around in the system. I could do a reboot but I'm on to other things. Just noting for developers in case other see same thing.
I notice in logs header device and apps names persist even after they are deleted. I think that is because old log entries still refer to them so might be unrelated.
Yes, that's correct. Old log entries w/device names from when they were created stay in the logs until they roll off.
When you have time I'd try a shut down/pull power/30s/restore to see if clearing the radio helps. I have a vague memory of running into this issue once myself, but unfortunately I can't remember much in the way of details. Looks like you're on Z-WaveJS, right?
It just happened for a third time with yet another ZEN76. This time I wasn;t setting to the old name so that seemed a false conclusion. It seems any name gets written over....
Fix coming.. The bug was causing discovery to run again on the device when the updated state came in.. It could also swap the driver to the initially discovered driver, if you are using a community driver that doesn't have the correct fingerprint..
... I do believe you found a bug... Will investigate..