GE enbrighten Jasco Z-Wave Motion Switch - motion : inactive

[guy]

I just bought a new GE enbrighten Jasco Z-Wave Motion Switch, it work great until I added it to my Hubitat. I can't get Hubitat to recognized the motion, it keeps telling me that the motion is inactive. I changed all sort of the setting and can't seam to get it to work. I google and it seams that that are others out there in the same boat. Apparently GE Jasco Z-Wave Motion Switch has change the firmware from 5.38 to 5.39 and now does not work. Can anyone help me out and get this to work, please and thank you in advance.

• motion : inactive

[JasonJoel]

1st thing I would recommend is to hit CONFIGURE on the device detail page.

2nd thing I would recommend is to turn on debug logging and see if you get anything in the log file.

I remember @NoWon having issues at one point with these devices w/firmware 5.39, but don't remember what the resolution was.

[NoWon]

I just checked all my GE Jasco motion switches (I have a lot of them) I do not remember which one had the latest firmware but they all appear to working correctly. I am at work and checking remotely. There are 2 I can only confirm were working 2 days ago since nobody has been in those 2 rooms today.

Here is the thread on the issue but it was fixed with a DH update last year.

Jasco Zwave motion switch DH

The new Jasco Zwave motion switches zw4006 - 26931-2 have new firmware I used the zwave stick to scan my Jasco ZW4006 switches and firmware version 5.39 are the ones not reporting motion in Hubitat. I can get them to report motion with SmartThings using custom DH. I modded the custom DH for Hubitat but it still will not report motion. To be clear older ZW4006 firmware version 5.38 reports motion correctly in Hubitat. Not sure why motion reporting would work with SmartThings but not Hubitat …

[NoWon]

Also all my hubs are on the latest Hubitat firmware.
and using the stock Hubitat "Jasco Zwave motion switch" DH

[NoWon]

Check all my GE Jasco motion switches when I got home and all are working correctly.
so even the 1-2 with firmware 5.39 on them are working.

[guy]

I have mine working except for the motion sensor, it keeps saying inactive. But everything else works.
Guy

[guy]

When I disconnect the switch from Hubitat the motion detector works properly.

When I reconnect to the hub, everything work except for the motion sensor.

When I called GE Jasco support, they did say there were others who have been calling in with the same problem. They told me I would have to contact Hubitat as the problem is with the hub drivers for that switch.

[JasonJoel]

Did you turn on debug logging and try to trigger motion to see if anything is logged?

The user drivers, or in-box drivers, won't be updated unless someone posts info that shows the problem.

None of us have one of those new firmware versions, and there is no reliable way to order one (as mentioned, the last one I ordered just 2 weeks ago still had old firmware). The one before that I ordered straight from Jasco and still didn't get a new firmware version.

[guy]

I did turn on the Debug Log,

Did you want me to send it/post it?

[JasonJoel]

Post it if there is something that shows up, and we'll see what it says.

[JasonJoel]

Well, that's disappointing. Nothing to go off of there.

I think if you change to "device" driver it logs all zwave messages. I'll double check. If it does, that may be worth a try.

EDIT 1: Yes, it does. So try changing the driver to "Device", hit Save Device, and generate a few motion events on the device. Then we'll hopefully see what's what in the logs...

EDIT 2: Also click get info button while you are on that driver.

EDIT 3: When I use the "Device" driver on my dev hub with a GE Motion Dimmer I get entries like this in the log when there is motion:

dev:552020-09-19 09:27:27.082 am infoZ-Wave command:NotificationReport(v1AlarmType:0, v1AlarmLevel:0, reserved:0, notificationStatus:255, notificationType:7, event:0, sequence:false, eventParametersLength:0, eventParameter:[])
dev:552020-09-19 09:26:53.139 am infoZ-Wave command:NotificationReport(v1AlarmType:0, v1AlarmLevel:0, reserved:0, notificationStatus:255, notificationType:7, event:8, sequence:false, eventParametersLength:0, eventParameter:[])

[guy]

dev:1632020-09-19 10:46:38.611 am infofingerprint mfr:"0063", prod:"494D", deviceId:"3032", inClusters:"0x5E,0x72,0x5A,0x73,0x27,0x25,0x2B,0x2C,0x70,0x86,0x71,0x60,0x8E,0x85,0x59,0x7A,0x56"

dev:1632020-09-19 10:46:38.608 am debugbuilding fingerprint for unknown Z-Wave device...

dev:1632020-09-19 10:46:36.486 am debugconfigure() called...

dev:1632020-09-19 10:46:32.926 am infofingerprint mfr:"0063", prod:"494D", deviceId:"3032", inClusters:"0x5E,0x72,0x5A,0x73,0x27,0x25,0x2B,0x2C,0x70,0x86,0x71,0x60,0x8E,0x85,0x59,0x7A,0x56"

dev:1632020-09-19 10:46:32.923 am debugbuilding fingerprint for unknown Z-Wave device...

dev:1632020-09-19 10:46:30.818 am infofingerprint mfr:"0063", prod:"494D", deviceId:"3032", inClusters:"0x5E,0x72,0x5A,0x73,0x27,0x25,0x2B,0x2C,0x70,0x86,0x71,0x60,0x8E,0x85,0x59,0x7A,0x56"

dev:1632020-09-19 10:46:30.813 am debugbuilding fingerprint for unknown Z-Wave device...

dev:1632020-09-19 10:45:34.070 am infofingerprint mfr:"0063", prod:"494D", deviceId:"3032", inClusters:"0x5E,0x72,0x5A,0x73,0x27,0x25,0x2B,0x2C,0x70,0x86,0x71,0x60,0x8E,0x85,0x59,0x7A,0x56"

dev:1632020-09-19 10:45:34.067 am debugbuilding fingerprint for unknown Z-Wave device...

dev:1632020-09-19 10:45:31.249 am infofingerprint mfr:"0063", prod:"494D", deviceId:"3032", inClusters:"0x5E,0x72,0x5A,0x73,0x27,0x25,0x2B,0x2C,0x70,0x86,0x71,0x60,0x8E,0x85,0x59,0x7A,0x56"

dev:1632020-09-19 10:45:31.225 am debugbuilding fingerprint for unknown Z-Wave device...

[JasonJoel]

Thanks. Were you able to get any motion events though? I don't see anything that looks like a motion event - just the get info lines.

If the device isn't sending any events when there is motion, then you are going to be out of luck - can't make a driver do something if the device doesn't send anything.

[guy]

Here is what I got, not sure if I did this right?

[JasonJoel]

Those just look like the Get Info data.

Need to walk around in front of the device and see if it logs something when there is motion/no motion. If it isn't logging anything when that happens, then you will never get it to work in Hubitat.

And if it isn't sending any events when there is motion, the last thing I could think of trying is to use my custom driver for this device, and make sure that when you configure the preferences ensure that the motion sensor is actually turned on in preferences.

[RELEASE] GE/Jasco Z-Wave Plus Motion Switch Driver

GE/Jasco Z-Wave Plus Motion Switch Driver I got tired of the generic built-in driver missing features that are on the GE/Jasco switches. This was loosely derived from the ST device handler, but mostly re-written. NOTE 1: This is for the motion GE/Jasco Z-Wave Plus Switches only . It will not work with the non Z-Wave Plus models (12xxx), it will not work with any dimmer model, and it will not work with the non-motion Switch (14291). It has been tested with a GE 26931 switch. It should also …

[guy]

Thanks I am new to this,

Doing it now. Cheers Guy

[guy]

[JasonJoel]

Really? That is definitely odd. It isn't reporting anything for motion then - SwitchBinaryReport on all previous firmware is when the light part turns on/off.

Ok. well, that is a new one. I would suggest trying my user driver posted above, make sure the motion sensor is ON when you set/save preferences. After saving preferences hit confgiure once, wait a minute, hit refresh once.

[guy]

Janson How do you install new drivers to Hubitat

[JasonJoel]

On hub:

• click Drivers Code

• click New Driver

• click Import
  paste this url into the input dialog:
  https://raw.githubusercontent.com/Botched1/Hubitat/master/Drivers/GE-Jasco%20Z-Wave%20Plus%20Motion%20Switch/GE-Jasco%20Z-Wave%20Plus%20Motion%20Switch.groovy

• click Import

• click Save