No inclusions will occur on C7

Platform version

2.3.7.145

I can't seem to include anything. I tried a lock and tried a motion sensor. Both devices seem to think they are included, but the C7 does not recognize them as included.

I have many zwave/zigbee devices already loaded (maybe 40?). How can I reset the device and reload everything to see if I can get the c7 to start including devices?

Or is there an obvious manner to resolve the issue?
Step by step would be great.
Appreciate it.


We will need considerably more information in order to be of any assistance to you.

Extract from How to Collect Information for Support | Hubitat Documentation --

"Please include the following in support requests

  1. Your hub platform version and hub hardware version (from Settings > Hub Details).
  2. A detailed description of the problem: what is happening and the expected result.
  3. Driver debug logs and application log, isolated to the specific device or application that is suspected (see above).
  4. Screenshots of associated Rule Machineยฎ rule details, or other app configuration; plus Device Detail and App Status."
2 Likes

We can't see your hub, so we don't quite know what to do. Maybe start by telling us the brand/model of these devices that aren't working, and like Eric pointed out above, screenshots of what you are seeing. Logs, error messages, Z-wave details (if applicable) or anything else that may help us.

2 Likes

I didn't know if this was a thing. I thought it was (and may still be) because of the lock. I have a Kwikset zwave plus 620. It seemed to stop functioning. I attempted to remove and include it. I keep seeing the message that says "found zwave device ... initializing" but then Hubitat inclusion times out. There are no logs that I'm aware of, but if there are, I'd like to know about them. It just times out.

I then attempted to include an Aeotec multisensor 6. The inclusion process did the same thing where it was "initializing the device" but then timed out. I did, however, see the "green" light show up on the Multisensor. The instructions indicate that it is included if it turns green. I didn't see the device in hubitat and it timed out.

I then downloaded a backup of the hubitat and did a "soft reboot" and uploaded the backup I just made.

After this process (not sure if this was the reason), I then saw the Aeotec device listed as one of the devices. It seems to work and logs show proper information.

I went back to the lock and went through the "exclude" process and reset the Kwikset 620 lock. I then attempted to include it and saw the "zwave device found .. .initializing" but it timedout. I did the same process of creating a backup, soft reset, upload backup, but to no avail. No Kwikset Lock (or any other unusual device) found.

thoughts? I could have a bad Kwikset lock, but seemed like the Aeotec multisensor inclusion exhibited the same results (but ultimately was successful)

thank you.

Some Z-Wave locks are designed to be paired very close to the Z-Wave controller. This is to prevent someone else nearby from 'grabbing' your lock device during the pairing process. Try moving the lock and hub close together, then perform a Hubitat Z-Wave EXCLUSION on the lock, and then try the INCLUSION process again. Also, make sure you have fresh batteries in the lock.

2 Likes

Thanks for that info. I always wondered why I needed to drag my hubitat to be close to the lock. I did as you stated though. I but the hubitat within inches of the lock with no luck.
First exclusion and then full reset of lock. Then inclusion. And what I stated above is what the results were. Obviously this worked a while back. Of course this was many many version of hubitat ago and it could be the lock as well.

1 Like

Can you post a copy of your z-wave details page in its entirety?

1 Like

@rlithgow1 I took a look at the zwave Details and I saw a ton of "lock" entries. The full list is quite large. Perhaps this allows for some insight?

How do I remove all these, what appears to be, orphaned locks? perhaps causing all my problems?

The only insight we have from that screenshot is that you have created a large number of zwave ghosts that must be removed.

Can you post a screenshot of the **entire ** zwave details page?

2 Likes

Is there a way to export? Or put in some non graphical format?

A screenshot is ideal.



Every one of those without anything in the route column are ghosts and will prevent you from adding more devices and prevent your existing devices from working properly. Start by clicking refresh on a ghost line, then when it appears click remove. If this does not work for any of them, shut down power to the device that created the ghost and power cycle the hub (not just reboot) and then attempt to remove again. If this also doesn't work you will have to either use a z-wave stick to remove them or nuke the whole radio and start over. Your entire mesh is trashed.

1 Like

ugh. So, I've been attempting to remove them, but seems like it doesn't always work. I'm guessing it is because the device is already active using a different ID and the ID that is incomplete is just causing problems?

If I do "nuke" the whole system, I take it all my apps will need to be recreated as the IDs won't match?

If I remove the batteries for all my locks, I "should" be able to remove all these ghosts tied to locks?

Right but power cycle (shutdown, remove power for 2 mins and power back up) and attempt to remove again

@Caboose Any time you have a failed pairing, STOP. Check for ghosts and remove them. It's far easier to do at that point then later...

1 Like

thanks. will attempt this.

another option is to connect up remotely (not close to all my stuff) and remove all ghosts? Only 12 more to go (that won't remove ...)