Product Review: GE Hinge Pin Smart Door Sensor

Hardware
21

Yes, please let me know too. I really like the hinge sensor and its good to know its an HA thing instead of a sensor thing as that can be fixed in an update at some point.

I thought of working the access control but did not want to mess with it too much in case it was a sensor issue. I did not want to set up several customizations to deal with a broken sensor. If that is not the case, it would make it more worthwhile. However, I would be even more interested in what is missing in HA that prevents these from working out of the box and seeing if that could be fixed easily enough.

22

Got it, pretty easy:

sensor:    
  - platform: template
      sensors:
        main_door_hindge:
          value_template: "{%if states.sensor.main_door_t_access_control_9_9.state == '23' %}closed{% elif states.sensor.main_door_t_access_control_9_9.state == '22' %}open{% endif %}"
          friendly_name: 'Main Door Status'
        entry_door_hindge:
          value_template: "{%if states.sensor.entry_door_t_access_control_18_9.state == '23' %}closed{% elif states.sensor.entry_door_t_access_control_18_9.state == '22' %}open{% endif %}"
          friendly_name: 'Garage Entry Door Status'

This changes the state of the template object I believe. As this stands, it changes the word on the sensor which I believe is the state of the new template sensor.

3 Likes
23

Well, maybe this will turn into a good thing after all. Thanks for posting the code.

1 Like
24

I’m also experiencing the same issue. The binary sensor always reports off unless i press the button while its in a new state. However, I did manage to get the 22/23 state change working…

A couple things to make note of:

  • The battery was EXTREMELY loose. I had to bend the spring to get a reliable battery connection. It kept cutting out for me.
  • The device is made of two parts - the plastic white part (holds the battery and all the zwave guts), and the metal top part that connects the the hinge. The device WILL NOT report new values in the Notification report unless these two are snugly fit together.

I spent about an hour trying to figure out why the values weren’t changing before I realize there was a sensor inside that knew if the top was securely on or not.

After that, i was able to get the 22/23 status change mentioned above on the sensor.ge_32563_hinge_pin_smart_door_sensor_access_control_37_9 device.

Hope this helps someone!

1 Like
25

Can you go through the steps that you went through again. There was a place there where you went into ozwcp and it seemed kind of like “magic happened”. Can you shed some light on the magic?

26

Are you stuck somewhere? I just went through setup last night, I can probably help while its fresh in my mind :slight_smile:

27

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 :slight_smile: so i’m ready to get back to it.

28

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)

  1. The little button on the side controls the mode of the device.
  2. you have to have the device not talking to a zwave network to configure it.
    1. you can do this by turning off the zwave network momentarily through HA configuring it and turning the zwave network back on.
  3. 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.
  4. Note: I am going to call the modes based on the number of flashes you get after pressing the button 5 times.
  5. Modes:
    1. mode 3: does nothing I can tell
    2. mode 2: does nothing I can tell
    3. mode 1: works (sends messages to HA)
  6. 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.
  7. The state change of these numbers happens immediately when the door is open or closed.
  8. 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
29

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
30

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
31

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.

32

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.

33

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.

34

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.

35

Do you know whether these sensors are available in Europe on the European Z-wave frequencies?

36

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
37

Click the blue link at the top of the page and follow the directions there to properly format your code.

38

Also, that template should be going in the sensor section, not the customize section.

39

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!

40

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.