Feature request: jasco/GE hinge pin battery reporting

any chance you would add support for battery on the jasco device.. The device works with the generic zwave contact device driver but doesn't report battery levels.

deviceType: 18771
inClusters: 0x5E,0x86,0x72,0x80,0x84,0x70,0x85,0x59,0x30,0x71,0x73,0x7A,0x5A
deviceId: 12338
manufacturer: 99

I am anxiously awaiting the delivery of my Hubitat. I really liked the look of the hinge pin, but wasn't sure that Hubitat would support it. I just bought one as my first Zwave device. Glad to see that it is supported.

I'm surprised the generic zwave contact driver doesn't report the battery levels.

Looking at the device specs, it would appear that the GE hinge contact is just using the standard zwave powerlevel and battery capabilities.

Maybe it just need a refresh?

Maybe. Never hurts to hit configure, wait a bit, and a refresh... :slight_smile:

Or maybe they forgot to handle the battery notification messages in that particular driver for some reason. Don't know, as I can't see the code for in-box drivers.

just looked at the jasco documentation again and saw this

maybe it is as simple as pressing the button 5 times.. see two flashes and it works..
or maybe 5 more to get basic report. nothing explains this table in the instructions.
I'll see when i get home tonight

I saw that too. Doesn't hurt anything to try.

Notification is the normal mechanism (and supported by hubitat in general), but I have seen some drivers/devices use basic report instead before.

You can also use the basic z-wave tool and change it that way w/o the physical button presses. It is parameter 20, size 1, values are 1,2,3 in the same order as the pic above.

well i tried all three settings of MODE. nothing. I left on MODE 1 as you indicated that was typical/default setting driver used.

would it be worth the time to exclude, factory reset, include?

Probably not. If you haven't already, it would be worth hitting the configure button in the device detail page, though.

oh I have tried the config button... :> When I tried the z-wave tool it didn't do much. It loaded I tried getting 20,1,1 and got nothing. ran the reports nothing. i tried on a android phone a macbook and a windows 10 system.

I wish I had one of these to play with. I'm sure it wouldn't be hard to figure out/make a user driver that supports the battery reports.

The next thing I would suggest is maybe asking @mike.maxwell if he has any thoughts on why the battery reports aren't creating events on this device. He may know of some goofy thing GE did to these that makes it not report right (wouldn't be the first time!).

I have one of these, still in a box from over a year ago, I can look at supporting it.

I guess I would have thought the generic contact driver would have supported powerlevel/battery notifications (thus not needing a special driver).

Was that a bad assumption?

me too, but since it doesn't work, I guess not...
If I can ninja the thing into a generic I will, if not, then I won't...

1 Like


You're the man. :smile:

There are jasco drivers for their dimmer and switch, maybe there is something strange about jasco devices..


Although I looked at the device capabilities and associations and didn't see anything that looked 'special' about it. But you never know for sure until you look at the zwave notifications/reports the device actually sends.

What resources could you point me to to learn about the low level zwave, zigbee communication. I'd love to understand more about it and be able to dig deeper into problems. and maybe write a drive or app some day..

ZWave is easy, as the protocol, capabilities, and format is very defined.

You could read through the zwave spec. It is super boring, though, and only useful if you are going to do a lot of zwave development. I've read it, some sections many times, but it definitely is not necessary.

What I would suggest, and the way I started way back when, is to find a working user zwave driver and look at it. The format isn't that complicated. In general there is a message parser that gets the raw messages and breaks them into zwave commands that then get processed in their respective handler sections in the driver. So the base system/parser do pretty much all of the hard part (intercepting the packet, and putting it into usable commands).

Then to make a driver for a device, typically you can start with the published device capabilities on the zwave alliance website to learn the supported capabilities, parameters, and associations.

Zigbee is a different beast. In my opinion you really need a hardware zigbee sniffer device to make zigbee drivers effectively. While the protocol packet format is pretty straightforward, the capabilities can be very different per devices/supported zigbee class. It is much easier if you can poke and watch the response on zigbee.

@spokra, I know this is an old thread but did you ever get the battery reporting working with the GE Hinge?