Problem: After upgrading to Platform v2.5.0.143 the EVA LOGIK ZW97 2 Outlet Zwave Switch becomes intermittently unresponsive. Typically the parent switch gets shutoff and you need to make several attempts to get it back on again. You can't then get the child switches to work until you turn off a child switch and its turns off the parent again causing you to repeat the process to get either of the child switches to work again. Prior to the platform update, Ive never needed to fiddle with the parent switch.
Solution: Roll back to Platform v2.5.0.136. After roll back both child switches functions reliably again and no interaction with parent switch is needed.
I assume im running legacy since I see a button on the Zwave details page that's called "Switch to ZwaveJS". I was running a C7 hub but upgraded it to a C8 Pro several months ago.
FWIW, I'm also running an Eva Logic plug (EVA LOGIK ZW36). I'm on C8-Pro/J-WaveJS, no issues w/any 2.5.0 platform releases, including productions and betas. It's one controlled and one always on plug, so no child devices.
If you wanted to you can update to Z-WaveJS and see if that resolves your problems w/out creating any new ones...I held off on Z-WaveJS for quite a while but switched over to JS a few months ago and things have been very good, not having issues.
You can easily switch between the Legacy and Z-WaveS stacks, so it's not like it's a one-way change.
Ok. Thx for the info. I had no idea that config setting has been hiding down there. I havent purchased a Zwave device in ages as most these days are Zigbee
Thx. I removed the 2 devices that didnt have names, updated the platform version and I've successfully used the switches several times. I'll set this thread to resolved once I see a couple days of reliability. It is odd, a down rev of the platform version solved the problem. Its also still not clear if I should update my zwave protocol to JS?
Easy to try Z-WaveJS and easy to revert if you run into issues. Z-WaveJS is where Hubitat is going long-term, so unless it causes you problems makes sense to go with it, it's where HE will be focusing their efforts on Z-Wave development.
Agree, that is a little odd that they worked on the previous version but not .143 (until you removed the ghosts). Sometimes a reboot can surface underlying issues that have been quiet, but I don't remember hearing about ghost issues resolved by a platform version change.