Long Range pairing issue ghost nodes


I got this app [APP] SmartStart Manager for Z-Wave (Long Range support) adding tons of ghost entries for the zwave LR device. How do I stop this? I followed all the instructions.

  • How many LR devices have you actually tried to set up using SmartStart in the mobile app?
  • Do you have any entries in your Z-Wave Details page for your LR device(s) that aren't ghost entries?

You can try shutting down your hub, pull power, and then restore power.

  1. 1
  2. no
  3. excluded and power cycled both the hub and device.

@hypnosis4u2nv Also power down the device you are trying to add, so it will stop trying to pair, it is not working obviously. You could also disable it in the Smart Start List view so the hub will not try to pair it again until you enable it. Once that is done shut down and unplug for 30 seconds then boot back up, that may clear all of those nodes out of there.

You might be encountering an issue that two of us in Beta had a thread about but it was not solved yet.

I am going to split this into a new thread.

1 Like

Was your current hub (presumably a C8) migrated from a C7 hub or earlier in the past?

Please check your logs for something like this to see if this might be the same issue:

Here is the beta post about the bootstrapping error (this will only work if you are in the beta group)
https://community.hubitat.com/t/2-3-9-112-117-smartstart-s2-bootstrapping-error-c8-pro/136682/78?u=jtp10181

Rebooting the hub isn't the same as shutting it down and pulling power from the hub...the Z-Wave and Zigbee radios only clear if you shut down and pull the USB power connection for a bit as noted above. I think you understood that, but just wanted to make sure.

Came from C7 to C8 to C8 Pro.

Didn't see anything in the logs. I just saw an update available that had a fix for zwave exclusion issue. Once the hub booted up on that firmware, the unknown device were cleared.

Here's the logs for the device in question

dev:7022024-05-30 12:45:19.294 PMdebugOutlet LR Dual: Update Params List

dev:7022024-05-30 12:19:59.721 PMdebugOutlet LR Dual: Need to reset lifeline association...

dev:7022024-05-30 12:19:57.731 PMdebugOutlet LR Dual: manualControl - Physical Button On/Off Control (#8) = 1

dev:7022024-05-30 12:19:57.646 PMdebugOutlet LR Dual: powerFailure - Behavior After Power Failure (#6) = 2

dev:7022024-05-30 12:19:55.138 PMdebugOutlet LR Dual: Need to reset lifeline association...

dev:7022024-05-30 12:19:53.138 PMdebugOutlet LR Dual: onTimer2 - Auto Turn-On Timer (Outlet 2) (#5) = 0

dev:7022024-05-30 12:19:50.408 PMdebugOutlet LR Dual: Need to reset lifeline association...

dev:7022024-05-30 12:19:48.412 PMdebugOutlet LR Dual: onTimer - Auto Turn-On Timer (#4) = 0

dev:7022024-05-30 12:19:47.386 PMdebugOutlet LR Dual: offTimer2 - Auto Turn-Off Timer (Outlet 2) (#3) = 0

dev:7022024-05-30 12:19:46.651 PMdebugOutlet LR Dual: offTimer - Auto Turn-Off Timer (#2) = 0

dev:7022024-05-30 12:19:45.800 PMdebugOutlet LR Dual: ledIndicator - LED Indicator (#1) = 0

dev:7022024-05-30 12:19:45.756 PMdebugOutlet LR Dual: Lifeline Association: [1] | MC:

dev:7022024-05-30 12:19:45.510 PMdebugOutlet LR Dual: (Outlet 2) switch is turned off (physical) [NOT CHANGED]

dev:7022024-05-30 12:19:45.340 PMdebugOutlet LR Dual: switch is turned off (physical) [NOT CHANGED]

dev:7022024-05-30 12:19:43.445 PMdebugOutlet LR Dual: Set Device Info - Model: ZEN14 | Firmware: 2.00

dev:7022024-05-30 12:19:43.443 PMdebugOutlet LR Dual: Received Version Report - Firmware: 2.00

dev:7022024-05-30 12:19:42.420 PMdebugOutlet LR Dual: Changing manualControl - Physical Button On/Off Control (#8) from null to 1

dev:7022024-05-30 12:19:42.417 PMdebugOutlet LR Dual: Changing powerFailure - Behavior After Power Failure (#6) from null to 2

dev:7022024-05-30 12:19:42.414 PMdebugOutlet LR Dual: Changing onTimer2 - Auto Turn-On Timer (Outlet 2) (#5) from null to 0

dev:7022024-05-30 12:19:42.411 PMdebugOutlet LR Dual: Changing onTimer - Auto Turn-On Timer (#4) from null to 0

dev:7022024-05-30 12:19:42.408 PMdebugOutlet LR Dual: Changing offTimer2 - Auto Turn-Off Timer (Outlet 2) (#3) from null to 0

dev:7022024-05-30 12:19:42.405 PMdebugOutlet LR Dual: Changing offTimer - Auto Turn-Off Timer (#2) from null to 0

dev:7022024-05-30 12:19:42.399 PMdebugOutlet LR Dual: Changing ledBrightness - LED Brightness (#7) from null to 2

dev:7022024-05-30 12:19:42.378 PMdebugOutlet LR Dual: Changing ledIndicator - LED Indicator (#1) from null to 0

dev:7022024-05-30 12:19:42.317 PMinfoOutlet LR Dual: Logging Level is: Debug (3) for 30 Minutes

dev:7022024-05-30 12:19:42.286 PMdebugOutlet LR Dual: executeConfigureCmds...

dev:7022024-05-30 12:19:39.595 PMdebugOutlet LR Dual: componentRefresh from Zooz ZEN Plugs Advanced - Outlet 2 (702-2)

dev:7022024-05-30 12:19:39.568 PMdebugOutlet LR Dual: Creating 'Outlet 2' Child Device

dev:7022024-05-30 12:19:39.567 PMdebugOutlet LR Dual: Creating new child device for endPoint 2, did not find existing

dev:7022024-05-30 12:19:39.555 PMdebugOutlet LR Dual: componentRefresh from Zooz ZEN Plugs Advanced - Outlet 1 (702-1)

dev:7022024-05-30 12:19:39.487 PMdebugOutlet LR Dual: Creating 'Outlet 1' Child Device

dev:7022024-05-30 12:19:39.483 PMdebugOutlet LR Dual: Creating new child device for endPoint 1, did not find existing

dev:7022024-05-30 12:19:38.446 PMdebugOutlet LR Dual: Endpoints (2) Detected and Enabled

dev:7022024-05-30 12:19:38.326 PMinfoOutlet LR Dual: switch is turned off (physical)

dev:7022024-05-30 12:19:38.282 PMdebugOutlet LR Dual: Update Params List

dev:7022024-05-30 12:19:38.279 PMdebugOutlet LR Dual: Set Device Info - Model: ZEN14 | Firmware: 2.00

dev:7022024-05-30 12:19:38.274 PMdebugOutlet LR Dual: Received Version Report - Firmware: 2.00

dev:7022024-05-30 12:19:38.232 PMdebugOutlet LR Dual: Probing for Power Metering Support

dev:7022024-05-30 12:19:38.202 PMdebugOutlet LR Dual: Probing for Multiple End Points

dev:7022024-05-30 12:19:37.429 PMdebugZooz ZEN Plugs Advanced: Update Params List

dev:7022024-05-30 12:19:37.427 PMdebugZooz ZEN Plugs Advanced: Set Device Info - Model: ZEN14 | Firmware: 0.0

dev:7022024-05-30 12:19:37.410 PMdebugZooz ZEN Plugs Advanced: Unhandled zwaveEvent: ZipNamingNameReport(name: Outlet LR Dual) (ep 0)

dev:7022024-05-30 12:19:37.346 PMdebugZooz ZEN Plugs Advanced: fingerprint mfr:"027A", prod:"7000", deviceId:"B003", inClusters:"0x5E,0x9F,0x55,0x6C", secureInClusters:"0x25,0x7A,0x5A,0x70,0x8E,0x59,0x85,0x86,0x73,0x60,0x72,0x87"

dev:7022024-05-30 12:19:37.165 PMwarnZooz ZEN Plugs Advanced: Clearing state variables and data...

dev:7022024-05-30 12:19:37.164 PMdebugZooz ZEN Plugs Advanced: Enabling Full Re-Sync

dev:7022024-05-30 12:19:37.115 PMwarnZooz ZEN Plugs Advanced: configure...

dev:7022024-05-30 12:19:37.059 PMdebugZooz ZEN Plugs Advanced: refresh...

dev:7022024-05-30 12:19:37.058 PMwarnZooz ZEN Plugs Advanced: initialize...

dev:7022024-05-30 12:19:37.057 PMwarnZooz ZEN Plugs Advanced: installed...

1 Like

So it looks like you got the device working now, possibly on Long Range?

What does it look like in Z-Wave details now?

I must be losing it. I can't find it on the Z-Wave device details. But it's in my devices.



Would be much better if you could get screenshots from a wider screen, tablet or PC/Laptop.

Looks like though you have two LR devices paired but only one is showing on the details page? I would shut down, unplug and reboot again see if that clears it up.

I see 0x0101 is matching up. But the other one my app is showing 0x014F, but that's not in your details. Also the security is blank in my app, which I would guess means that node was not in the z-wave details endpoint I am querying.

Clearly some lingering bugs in the Z-Wave details screen with this LR update.

This is not the normal experience, I did not have issues like this during the beta.

014f is the one that's giving me a tough time and not showing up.

I'll try a hub power down and see if that changes anything.



This device still won't show up in the zwave details.

But it is working? What does the DNI show on the device page?

You may have to exclude it and then let it include itself again in a new node.

Also, why do you have both of them set to Mesh boot mode now? And also the patio outlet you have set to no security? Unless you plan to take it out of LR mode and add it to the mesh...? I mean it wont hurt anything unless you exclude and pair again, but why.

1 Like

Does it show up on your Devices tab? Or only in the SmartStart app?

image

DNI shows 014F

I can see the device in both Device tab and SmartStart but not in the Zwave Details page.

Smart Mesh is the only way they got included initially. The Patio Outlet is the only one that got the LR tag in the Zwave devices page. Been trying to get the Outlet LR to do the same. It's been a royal PITA.

1 Like

From Jeff's comments and questions from above:

Is it working? If it is working, I'd hold off for more advice from Jeff about the lack of an entry on the Z-Wave Details page, but it seems like unless a shut-down/pull power/restart populated the Z-Wave Details page you'll end up having to exclude it and see if it re-joins normally.

If it currently isn't working...

I don't think you've answered Jeff's questions above. Key to him helping is getting the info he asks for. :slight_smile: Good luck!

No, actually they got included as Long Range so thats what the boot mode was set to when they were included. Since then you have changed it to Mesh and probably force removed the LR node for 0x014F

You are making this much more complicated than it needs to be by changing random things you do not understand, and not answering questions being asked.

I will await the answers to the rest of the questions, and also one more. Do you want these devices as LR or in Mesh mode?

1 Like

I want these two device as LR since they're plugs and I can test there radios on LR before moving some of my switches over to LR as well.

This one device is being a pain joining as LR which is why I'm playing with the settings to begin with and why I'm here asking for help.

Still waiting to know if the device on node 0x014F is actually working? Can you control it from the hub or does the status update on the hub if you turn the device on/off physically?