@csteele Please read this: I have found the issue and verified it is an issue with ZWaveJS for my Utilitech Z-Wave Water Sensor Issue
So that is something new I was unaware of.
" Since release 2.4.5.151 in April of 2025 Hubitat has made ZWaveJS (an open-source Z-Wave library) available as an optional Z-Wave library. One of the benefits of ZWaveJS is more effective removal of Z-Wave ghosts via the hub's built-in Z-Wave removal tools.
On the C8-Pro you can switch from ZipGateway (the original/default Z-Wave library on HE hubs) to ZWaveJS via a button on the Z-Wave Details page. On C8 and earlier hubs running ZWaveJS on an ongoing basis isn't recommended (ZWaveJS has memory requirements that those hubs don't reliably support), but temporarily switching to ZWaveJS to remove a stubborn ghost and then switching back to ZipGateway is supported."
Looks like using ZWaveJS breaks my Utilitech Z-Wave Water Sensors, As I switched back to legacy to also try removal from there also and figured I would test the Utilitech Z-Wave Water Sensor again, and it just works now.
And relized it must have switched over to ZQaveJS after I did the update as I had migrated from a C* earlier this month and not on the Pro and the platform update must have triggered it on. And would explain why it work a few days before the Upgrade.
I have verified that switching back to ZWaveJS breakes the z-wave device again and going back to legacy it works again.
So something in the new ZWaveJS (open-source Z-Wave library) breaks them. (Others seem to be ok.
