Z-Wave JS migration C8 Hub - success and issues

Get Help
1

Running a C8 hub (non-pro) and my z-wave JS migration by in large went smoothly. I made the uncharacteristcly wise choice to kick off the migration around 1am when my wife was asleep and by morining most mains devices and a few battery devices had interviewed fine and by in large things were working.

For all of the mains devices hitting "refresh" resolved it. I was able to get the battery devices going as well by waking them.

I do have a few that seem to be sort of stuck "almost" finishing. Any ideas here?

image
image1446×260 49.9 KB

Note these are both battery devices so I can tell that it's not getting the full picture yet. I've woke them up multiple times and refreshed them as well.

I also noted a few devices with no names, etc. that it couldn't get any info on at all. My current running theory are these are some old failed devices that I'd attempted to force remove under the old z-wave stack that were ghosted. Is force-removing a failed device more effective in z-wave JS?

Overall I have to say the migration for me went impressively smoothly. All of my automations are largely controlled by home assistant through the makerapi so there really aren't any hubitat automations to fail and I'm running 70 devices.

Thanks in advance for any clarity/help provided.

2

When I switched to Z-Wave JS (on a C8 Pro) 3 weeks ago, I had several battery sensors that got stuck like this. Two in particular were old Fibaro Flood Sensors. After 2 days I just removed them and then re-included them.

I also had about 6 of these, even though I had no ghosts (according to Simplicity City and a Zooz stick) last time I checked. I just removed them.

3

I feel like a simple grasshopper next to you. :wink:

You can try restarting the device interview, that might help. I believe this is the correct endpoint, wake up the devices:

http://<YOUR_HUB_IP>/hub/zwave2/reinterview?node=<NODE_NUMBER>

You can also try restarting your radios...do this by:

  1. Shut down hub
  2. At red LED pull power
  3. Wait 30s
  4. Restore power

This restarts the radios (simple reboot doesn't) and might help get the interview to complete. Make sure to wake up the devices again.

4

Pretty sure you can reboot the radio from Settings-> Z-wave-> Reboot radio, derp nevermind, that's Zigbee I'm thinking of. Would be nice if we had the same option in Z-wave ! @gopher.ny

5

There's no "hard reboot the chip" GPIO pin for the Z-Wave radio, unfortunately.

6

Excuses, excuses... :wink: :rofl:

7

I seem to have a ghost:

image
image1449×154 14.2 KB

Only device left. No idea what it is so I can't go hunt for something to wake up. Removing it doesn't seem to want to take either.

8

So no joy from below? Restarting interview or shutting down hub didn't help at all?

Also, you should be able to use your mystery device's DNI (Device Network ID) to look for it in your Devices list.

DNI for one of my devices below is 0b.

26-10-11-6891
26-10-11-68911741×150 27 KB

Its Device page, on Device Info tab:

image
image1223×286 22.5 KB

Your device's DNI is 67.

image
image1035×109 14.3 KB

You can search in your Device list...first click on the DNI header to sort based on DNI, then type your DNI (67) into the search field and scroll to your device w/DNI = 67.

26-10-11-6892
26-10-11-68921215×393 48 KB

If you find it in your Device list via DNI I believe that should mean it's a valid device, just needs to finish the interview. Let us know what you find.

9

Update here - I got it to remove. I have had a few ghost devices in the past that failed and I suspect this was one of them. I just waited, still haven't bothered to pull power, etc.

10

Happy day, glad to hear of your patient success. Surprising how often waiting a bit can do some magic w/this stuff. :slight_smile: