C7 GE Hinge Pin Door Sensor — can’t add / stuck at “initializing”

[eric17]

Hi there. I recently bought a C7 and am migrating ZWave devices over from my C5.

I have 2 GE Hinge Pin Door Sensor devices, which I’m unable to add to the C7’s network. They were working fine on the C5 (and previously SmartThings).

I’ve gone through multiple rounds of debugging, but no matter what I do, I get stuck at “initializing” on the Device Discovery screen.

Here are things I’ve attempted:

• Excluding before including
• Device factory reset before including
• Bringing the device closer to the C7 hub
• Hitting “Discover” button on C7’s Z-Wave Details screen
• Removing the device on C7’s Z-Wave Details screen
• Sending activity (contact open/closed) from the sensor while initializing

Here are the Z-Wave logs for when I attempt to add the device, and after getting stuck on the “initialization” screen me pressing the “Discover” button

>     [42](http://192.168.7.91/hub/zwaveLogs#zwaveRx42)2020-12-12 14:38:13.184 seqNo: 201, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: Unknown
> 
>     [42](http://192.168.7.91/hub/zwaveLogs#zwaveRx42)2020-12-12 14:38:13.084 seqNo: 182, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: Unknown, rssi: [N/A, N/A, N/A, N/A, N/A], Ack channel: 0, Transmit channel: 0
> 
>     [42](http://192.168.7.91/hub/zwaveLogs#zwaveRx42)2020-12-12 14:37:48.567 seqNo: 182, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: Unknown
> 
>     [42](http://192.168.7.91/hub/zwaveLogs#zwaveRx42)2020-12-12 14:37:48.466 seqNo: 178, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: Unknown, rssi: [N/A, N/A, N/A, N/A, N/A], Ack channel: 1, Transmit channel: 1
> 
>     [42](http://192.168.7.91/hub/zwaveLogs#zwaveRx42)2020-12-12 14:37:42.127 seqNo: 178, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: Unknown
> 
>     [42](http://192.168.7.91/hub/zwaveLogs#zwaveRx42)2020-12-12 14:37:41.926 seqNo: 162, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: Unknown, rssi: [N/A, N/A, N/A, N/A, N/A], Ack channel: 1, Transmit channel: 1
> 
>     [42](http://192.168.7.91/hub/zwaveLogs#zwaveRx42)2020-12-12 14:37:14.905 seqNo: 162, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: Unknown
> 
>     [42](http://192.168.7.91/hub/zwaveLogs#zwaveRx42)2020-12-12 14:37:14.805 seqNo: 161, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: Unknown, rssi: [N/A, N/A, N/A, N/A, N/A], Ack channel: 0, Transmit channel: 1
> 
>     [42](http://192.168.7.91/hub/zwaveLogs#zwaveRx42)2020-12-12 14:36:49.852 seqNo: 161, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: Unknown
> 
>     [42](http://192.168.7.91/hub/zwaveLogs#zwaveRx42)2020-12-12 14:36:49.651 seqNo: 160, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: Unknown, rssi: [N/A, N/A, N/A, N/A, N/A], Ack channel: 1, Transmit channel: 1
> 
>     [42](http://192.168.7.91/hub/zwaveLogs#zwaveRx42)2020-12-12 14:36:19.199 seqNo: 160, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: Unknown

Here’s what the device looks like on the Z-Wave Details screen:

Any advice would be appreciated!

[rlithgow1]

ok, take the battery out. Go into settings, then z-wave settings and look for ghosts. I'd bet it's one of them. Remove it (it make take a few times. If it won't remove, cleanly shut down the hub, unplug power for 5 mins then bring it back up. Unplugging the power is key). Re add but do it next to the hub. I have a few of these units and they're really good.

[eric17]

Thanks for the advice. Tried this a dozen times, still no luck.

[rlithgow1]

did you remove power from the sensor as well? You can't get rid of the ghost if there is still power to the device as the hub will be able to ping it.

[eric17]

I eventually got this working by leaving the battery out of the device for >24h, and then re-adding. Weird. Thanks for your help.

[coreyclerico]

Same issue. Have not successfully added my 2 units. Painful.

[rlithgow1]

Do you have any ghosts?

[coreyclerico]

Yes, all the time. Deleted most of them that could be removed and re-tried to no avail with hub reboots. I'm giving them 24 hrs and will try both again. Each of these where new hinge pins. Also to note the stop Z-Wave inclusion never comes back and freezes. The hinge pin devices light up and never seem to unlight once the device is initializing. never once do these get to the security window or a edit box.

[rlithgow1]

That's the thing with removing ghosts. You have to cut power to the device otherwise it's still pingable and the ghost won't remove. Usually the best course is to remove power to the device, shut down hub via menu and then pull the power (from outlet side not hub side) for 5 or 10 mins. Power back up Hubitat and then remove ghost (may take a few times). After removal, shut down hub again, pull power (at the outlet side, not the hub side) for 5 or 10 mins and then power backup. Reset device to factory defaults and try to pair again. in the case of the hing sensors (I have a few of these) pair them next to the hub.

[domingy]

What driver are youy guys using? My sensor seems to be on the z wave network just fine the problem is that it only is reporting the battery level. On the device page it says closed but when open/closed it never sends open/close ? I am using generic z-wave contact sensor driver. I contacted support for help to see if they plan on making a specific driver for this device.

[eric17]

I have two of the exact same product (GE Hinge Pin Door Sensor).

One works perfectly fine with the Generic Z-Wave Contact Sensor driver.

A second doesn't (only reports battery level).

From another thread, someone recommended the Ring Alarm Contact Sensor driver, which works well enough for this second sensor. It doesn't correctly report battery level, however.