Gathering real world feedback on how well (or not) Zwave Switch to ZWave-JS is going

My Range Extenders have been in place for years. I assumed there was only the 1 driver available. I checked and realized I'm using a user written driver. I don't remember if a native driver was available at the time. There is no author in the source.

  • Ring Alarm Range Extender Gen 1 / Gen 2
  • version: 2.0

So @LearningHubitat it looks like you can try the JS update. Let me know if it works. I may change to the native driver.
Everyone else, I apologize for the confusion.

No, this is how we all learn. You are helping me. Thank you and I will report back when I can make the change.

what about the go control garage openers screaming bloody murder .... has that been resolved.

And for me the Zen55 goes back offline at the first refresh. If I roll back to the last 2.5.1 hub version it works as normal. I've been on JS on the 8 Pro almost since the introduction without issues. If you hit configure it goes online. Click refresh and it quickly returns to offline. Something in a recent 2.5.2 update has caused the Zen55 issue. I'm hoping my post in a different thread will get some staff or developer attention soon.

Back in June I had to roll back to legacy Z-wave - I had 3 main issues:

  1. My Yale Assure SL Locks (Z-Wave module) would only respond 60% of the time (using Generic HE Z-wave lock driver).
  2. My half dozen Aeotec Smart Switch 6 Outlets won’t report Switch state changes (using official HE driver)
  3. Occasional unresponsive periods, most frequently straight after my door locks have been commanded to unlock in the morning, but also in a couple of random scenarios

Overall, I think Z-WaveJS is better (when a device works correctly, its faster and more reliable), so I'll give it another crack this weekend.

It only happens once during the interview.. I have no idea what is triggering it from a bunch of get requests.. A quick power cycle and it should never do that again..

thanks but that means I need to have a step ladder ready and I have 2 of them lol

flip the breaker for that circuit(s)?

I just switched over just now ..
Because of all the updates they've been doing.
Thought I'd give it a try. I was kind of scared to do it.
Took a little while, but it finished. ( Freaked me out a bit )
I did have to reboot two Z-Wave devices.
Sensor AEON Labs Power meter. and Door Lock Kwikset
But everything else seemed to go just fine. ( Wipes brow )

Glad your migration was mostly uneventful. FWIW, those locks work well with ZWaveJS. I have an Aeotec heavy duty smart switch (40A) that I use to monitor my dryer. It used to pair only with S0 security with Z/IP, but I could re-pair it with no security under ZWaveJS.

Using the : AEON Labs Power meter for my mains .. covers hole house.
AI and me, created an energy monitor tracker system. This is what it looks like:
I'd like to know what the whole house is using per day during the summer and winter.

Spoke to soon I guess .. getting Multiple entries for opening and closing of the lock in the logs.
Pretty sure it didn't do that before I changed over the Z-Wave.

What model lock is that, and which driver is it using? My locks are "Kwikset Homeconnect 620", and I don't see that.

Also tagging @bcopeland.

Nothing that I know of, other than device spam, that would cause that many reports..

@WarlockWeary is it still happening?

If it is I will need some logs.. Z-Wave logging...

Well, it's not quite as bad all of a sudden, but I'm still getting it.


This is still broken in Zwave-JS - the outlet turns on and off as commanded, but status doesn't update. It doesn't matter if you manually turn them on/off or send the commands from HE.



dev:14242026-10-03 9:21:55.349 am

debug

BasicReport(value:99)

dev:14242026-10-03 9:21:55.347 am

debug

BasicReport(value:99)

dev:14242026-10-03 9:21:55.004 am

warn

Range Hood command "on()" failed after 5 retries.

dev:14242026-10-03 9:21:54.804 am

debug

ignore: SwitchBinaryReport(value:255)

dev:14242026-10-03 9:21:54.751 am

debug

on()

dev:14242026-10-03 9:21:47.806 am

debug

BasicReport(value:99)

dev:14242026-10-03 9:21:47.805 am

debug

BasicReport(value:99)

dev:14242026-10-03 9:21:47.260 am

debug

ignore: SwitchBinaryReport(value:255)

dev:14242026-10-03 9:21:47.201 am

debug

on()

dev:14242026-10-03 9:21:41.763 am

debug

BasicReport(value:99)

dev:14242026-10-03 9:21:41.761 am

debug

BasicReport(value:99)

dev:14242026-10-03 9:21:41.217 am

debug

ignore: SwitchBinaryReport(value:255)

dev:14242026-10-03 9:21:41.161 am

debug

on()

dev:14242026-10-03 9:21:37.231 am

debug

BasicReport(value:99)

dev:14242026-10-03 9:21:37.230 am

debug

BasicReport(value:99)

dev:14242026-10-03 9:21:36.685 am

debug

ignore: SwitchBinaryReport(value:255)

dev:14242026-10-03 9:21:36.628 am

debug

on()

dev:14242026-10-03 9:21:34.217 am

debug

BasicReport(value:99)

dev:14242026-10-03 9:21:34.215 am

debug

BasicReport(value:99)

dev:14242026-10-03 9:21:33.670 am

debug

ignore: SwitchBinaryReport(value:255)

dev:14242026-10-03 9:21:33.614 am

debug

on()

dev:14242026-10-03 9:21:32.702 am

debug

BasicReport(value:99)

dev:14242026-10-03 9:21:32.700 am

debug

BasicReport(value:99)

dev:14242026-10-03 9:21:32.159 am

debug

ignore: SwitchBinaryReport(value:255)

dev:14242026-10-03 9:21:32.104 am

debug

on()

dev:14242026-10-03 9:21:31.192 am

debug

BasicReport(value:99)

dev:14242026-10-03 9:21:31.191 am

debug

BasicReport(value:99)

dev:14242026-10-03 9:21:30.613 am

debug

ignore: SwitchBinaryReport(value:255)

dev:14242026-10-03 9:21:30.519 am

debug

on()

dev:14242026-10-03 9:21:30.111 am

debug

BasicReport(value:0)

dev:14242026-10-03 9:21:30.110 am

debug

BasicReport(value:0)

dev:14242026-10-03 9:21:29.563 am

debug

ignore: SwitchBinaryReport(value:0)

dev:14242026-10-03 9:21:29.486 am

debug

off()

dev:14242026-10-03 9:21:27.420 am

debug

BasicReport(value:99)

dev:14242026-10-03 9:21:27.419 am

debug

BasicReport(value:99)

dev:14242026-10-03 9:21:26.874 am

debug

ignore: SwitchBinaryReport(value:255)

dev:14242026-10-03 9:21:26.820 am

debug

on()

dev:14242026-10-03 9:21:24.397 am

debug

BasicReport(value:99)

dev:14242026-10-03 9:21:24.396 am

debug

BasicReport(value:99)

dev:14242026-10-03 9:21:23.845 am

debug

ignore: SwitchBinaryReport(value:255)

dev:14242026-10-03 9:21:23.790 am

debug

on()

dev:14242026-10-03 9:21:22.870 am

debug

BasicReport(value:99)

dev:14242026-10-03 9:21:22.870 am

debug

BasicReport(value:99)

dev:14242026-10-03 9:21:22.319 am

debug

ignore: SwitchBinaryReport(value:255)

dev:14242026-10-03 9:21:22.264 am

debug

on()

dev:14242026-10-03 9:21:21.344 am

debug

BasicReport(value:99)

dev:14242026-10-03 9:21:21.344 am

debug

BasicReport(value:99)

dev:14242026-10-03 9:21:20.768 am

debug

ignore: SwitchBinaryReport(value:255)

dev:14242026-10-03 9:21:20.684 am

debug

on()

dev:14242026-10-03 9:21:14.635 am

info

Range Hood current is 0 A

dev:14242026-10-03 9:21:13.631 am

info

Range Hood voltage is 239.873 V

dev:14242026-10-03 9:21:12.637 am

info

Range Hood power is 0 W

dev:14242026-10-03 9:21:11.634 am

info

Range Hood energy is 820.888 kWh

dev:14242026-10-03 9:21:11.631 am

info

Range Hood energyDuration is 1619.85 Days

dev:14242026-10-03 9:21:10.570 am

debug

BasicReport(value:99)

dev:14242026-10-03 9:21:10.570 am

debug

BasicReport(value:99)

dev:14242026-10-03 9:21:10.446 am

debug

refresh()

dev:14242026-10-03 9:21:02.871 am

debug

ignore: SwitchBinaryReport(value:255)

dev:14242026-10-03 9:20:58.869 am

debug

ignore: SwitchBinaryReport(value:0)

dev:14242026-10-03 9:20:57.206 am

debug

BasicReport(value:99)

dev:14242026-10-03 9:20:57.205 am

debug

BasicReport(value:99)

dev:14242026-10-03 9:20:56.854 am

warn

Range Hood command "on()" failed after 5 retries.

dev:14242026-10-03 9:20:56.659 am

debug

ignore: SwitchBinaryReport(value:255)

dev:14242026-10-03 9:20:56.600 am

debug

on()

dev:14242026-10-03 9:20:49.707 am

debug

BasicReport(value:99)

dev:14242026-10-03 9:20:49.706 am

debug

BasicReport(value:99)

dev:14242026-10-03 9:20:49.159 am

debug

ignore: SwitchBinaryReport(value:255)

dev:14242026-10-03 9:20:49.062 am

debug

on()

dev:14242026-10-03 9:20:48.760 am

debug

ignore: SwitchBinaryReport(value:0)

dev:14242026-10-03 9:20:43.580 am

debug

BasicReport(value:99)

dev:14242026-10-03 9:20:43.580 am

debug

BasicReport(value:99)

dev:14242026-10-03 9:20:43.036 am

debug

ignore: SwitchBinaryReport(value:255)

dev:14242026-10-03 9:20:42.975 am

debug

on()

dev:14242026-10-03 9:20:39.021 am

debug

BasicReport(value:99)

dev:14242026-10-03 9:20:39.021 am

debug

BasicReport(value:99)

dev:14242026-10-03 9:20:38.474 am

debug

ignore: SwitchBinaryReport(value:255)

dev:14242026-10-03 9:20:38.420 am

debug

on()

dev:14242026-10-03 9:20:36.002 am

debug

BasicReport(value:99)

dev:14242026-10-03 9:20:36.001 am

debug

BasicReport(value:99)

dev:14242026-10-03 9:20:35.459 am

debug

ignore: SwitchBinaryReport(value:255)

dev:14242026-10-03 9:20:35.400 am

debug

on()

dev:14242026-10-03 9:20:34.528 am

debug

BasicReport(value:99)

dev:14242026-10-03 9:20:34.525 am

debug

BasicReport(value:99)

dev:14242026-10-03 9:20:33.941 am

debug

ignore: SwitchBinaryReport(value:255)

dev:14242026-10-03 9:20:33.888 am

debug

on()

dev:14242026-10-03 9:20:33.002 am

debug

BasicReport(value:99)

dev:14242026-10-03 9:20:33.002 am

debug

BasicReport(value:99)

dev:14242026-10-03 9:20:32.423 am

debug

ignore: SwitchBinaryReport(value:255)

dev:14242026-10-03 9:20:32.365 am

debug

on()

dev:14242026-10-03 9:20:31.581 am

debug

BasicReport(value:0)

dev:14242026-10-03 9:20:31.581 am

debug

BasicReport(value:0)

dev:14242026-10-03 9:20:31.029 am

debug

ignore: SwitchBinaryReport(value:0)

dev:14242026-10-03 9:20:30.959 am

debug

off()

dev:14242026-10-03 9:20:16.463 am

warn

description logging is: true

dev:14242026-10-03 9:20:16.462 am

warn

debug logging is: true

EDIT: ZWave logs (Node 079):

https://raw.githubusercontent.com/dJOS1475/HubitatRules/refs/heads/main/SmartSwitch%206%20Zwave%20JS.log

Z-Wave logs that Bryan asked for are accessed from the Z-Wave Details page...

Open the Z-Wave logs page and then trigger the event, and copy/paste the Z-Wave logs to Bryan. :slight_smile:

Sent a message to him .. thanks

I'm having trouble with a ZEN21 VER2.0. I don't know if this is related to the upgrade. I have 2 newly created test rules.

Test

Test clone

Physically toggling the switch only produces logs for the second rule.

The switches event log shows: