Are you stuck somewhere? I just went through setup last night, I can probably help while its fresh in my mind 
I’ve been rebuilding my install for the past 3 days. But the last I had, was, the hinge was recognized by HA but no matter what I did with the switch, nothing changed in HA. The light on the switch would turn on and off as the door opened. I could hear the click as it passed by the trigger point, but nothing changed in the HA screens. I figured at that point, I probably needed to go into ozwcp and do whatever magic was done, but couldn’t get ozwcp to install. So that’s when I started rebuilding my environment. Now I have an environment where I can get into ozwcp so i’m ready to get back to it.
SUCCESS!!! I did it through AppDaemon instead of through YAML, just because that’s where all of my automations are. But, it works!!!
Here is what I found out (some of this is a re-hash)
- The little button on the side controls the mode of the device.
- you have to have the device not talking to a zwave network to configure it.
- you can do this by turning off the zwave network momentarily through HA configuring it and turning the zwave network back on.
- you change nodes by pressing the button 5 times, relatively fast. if your zwave network is still connnected to the device, the lights won't flash.
- Note: I am going to call the modes based on the number of flashes you get after pressing the button 5 times.
- Modes:
- mode 3: does nothing I can tell
- mode 2: does nothing I can tell
- mode 1: works (sends messages to HA)
- As everyone has figured out, when the sensor.ge_32563_hinge_pin_smart_door_sensor_access_control_3_9 returns 22 the door is closed, 23 means the door is open.
- The state change of these numbers happens immediately when the door is open or closed.
- if the button is pressed once, it will return a message that has more information and switches the GE 32563 Hinge Pin Smart Door Sensor Sensor state.
Next:
- I am going to reach out to GE/Jasco and see if I can get a better description of what the modes do and what the different values returned by the device actually mean. (wish me luck).
- Wink is supposed to have support for this sometime in the next month or so. (Keep your fingers crossed)
- It would be nice if someone that knows the HA sensor code would put address this and make it a standard part of HA. (hint hint)
2 Likes
I just setup a second one of these. It helped me immediately that I did a device reset on it by pressing the button 10x in rapid succession. I then added the device in OZWCP and started up HA. Got the 22/23 state change going just fine!
1 Like
You guys are amazing. I was working with this sensor for a few hours running into all of the same issues. I had eventually worked out the button pushing to reset and that got me paired, but then the issue of open/closed not working. I was trying to figure out how to deal with mapping the access control values when Google lead me here. I am grateful for this forum!
I took the example above one step further and took advantage of a binary sensor and its class called “opening.”
binary_sensor:
- platform: template
sensors:
kitchen_to_garage_door:
value_template: "{{ states.sensor.kitchen_to_garage_door_sensor_access_control_12_9.state == '22' }}"
friendly_name: 'Kitchen to Garage Door'
device_class: "opening"
entity_id: sensor.kitchen_to_garage_door_sensor_access_control_12_9
entity_id: isn’t required but the documentation seems to indicate it helps out with Home Assistant performance.
2 Likes
Picked one of these up as my first foray into zwave. Got it paired, created the template sensor and have open/close reporting on the front end.
However, after a short period it stops reporting changes, any idea why? Any config options to change?
The sensor still lights up each time the door is opened.
Make sure your Zwave config didn’t rename the sensor. Open your Zwave config and make sure it has a name associated with the zwave index.
This ended up being an issue with the USB pass through on my ESXi host. Not sure what the issue was but I moved back to a Pi and everything works fine.
Man, I just had issues with this device and I had to reset to factory defaults… I forgot how I set it up and your post refreshed my memory. The little graphic in the corner of the manual is terrible.
Do you know whether these sensors are available in Europe on the European Z-wave frequencies?
I’m currenty trying to do this for my Door hinge sensor in my customize.yaml file, but I keep getting the error:
Configuration invalid
Error loading /config/configuration.yaml: while parsing a block collection in “/config/customize.yaml”, line 46, column 3 expected <block end>, but found ‘?’ in “/config/customize.yaml”, line 53, column 3
I apologize, I’m fairly new t all this, but here is the code section:
binary_sensor.ge_32563_hinge_pin_smart_door_sensor_sensor:
- platform: template
sensors:
master_bedroom_door:
value_template: “{{ states.sensor.master_bedroom_door.state == ‘22’ }}”
friendly_name: ‘Main Door Status’
device_class: “opening”
entity_id: sensor.master_bedroom_door
Click the blue link at the top of the page and follow the directions there to properly format your code.
Also, that template should be going in the sensor section, not the customize section.
I apologize, I tried to use the formatting, but when I pasted, the lines were all at the same depth.
I do not have a sensor.yaml file, I will try to find information on generating one.
Thanks, and sorry again!
Don’t copy from a post, it preserves the formatting.
Copy from your yaml then post it using the appropriate formatting techniques described in the blue ribbon at the top of the page.
Anyone tried to replace the batteries in one of these yet? My hinge stopped reporting the other day so I replaced the batteries. It’s been working fine for about a year so I assumed it was the battery. Now I’m beginning to wonder if something else happened. I can see it broadcasting as node 4 to OZW logs, but HA doesn’t recognize it and it’s got a strange entry in the ozwcfg file. Any thoughts? I’m about to unpair and re-pair the device and see if that works.
Battery replacement was fine. No action required afterwards.
I had one of 3 go on the fritz a while back. Had to exclude it reset to factory then include it again. Had to change the reporting again too. had to come back to this thread because I forgot the settings.
same here. Stinks that it didn’t apparently didn’t retain it’s settings after the battery went dead for a while. But it’s back in operation now. Only took about an hour to find everywhere it was referenced in groups and automations. LOL
If you know how to delete old entity_ids from the .storage entity registry, you don’t have to do any searching. Just delete the old entity after excusion. Include the new one, and rename it to the old entity_id. I can show you how to safely edit the entity_registry. Hopefully in the future we will have a way to remove old entity_id’s from that via the UI.