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
Switch on/off reporting works with both firmware and on both Hubs

Try this DH... Not sure on the firmware levels... All of mine are 5.38, so who knows if it will do anything different.

What exactly did you have to change in the ST DTH to make it work?

I just changed physicalgraph in mlebaugh code. Motion works in SmartThings using his code but not Hubitat with the new firmware.
Tried yours as well thanks but same issue no motion reporting with version 5.39 firmware.
Same issue with Hubitat stock DH code
Jasco tech contacted me but still waiting on a response what changes were made in the firmware change or if they will release the old firmware (doubtful).

Very strange that the same code works in SmartThings but not in Hubitat.
I think I was able to get it to stop working in SmartThings last night but it was 2 am. Will see if I can duplicate it now.

Also, just FYI, You have to change a number more things than that from Matt's DTH to get it working 100% in Hubitat.... Buttons, configure/preferences events, etc.

Did you turn on debug logging and see if there is anything in the logs? If it is some new unhandled notification I would think it should show up there.

Also, I wonder if on that firmware Association Group 2 needs to be assigned to the hub? It is not set to the hub ID on most of the DTH I've seen, as it generates duplicate events.

Could try that, too. In my DTH just change the two instances of this:

cmds << zwave.associationV1.associationRemove(groupingIdentifier:2, nodeId:zwaveHubNodeId).format()

to this:

cmds << zwave.associationV1.associationSet(groupingIdentifier:2, nodeId:zwaveHubNodeId).format()

debug logging on

using your "Association Group 2" mod whenever I trigger motion I get the following log errors (one set for active one set for not active)

dev:36802019-01-26 03:31:34.778 pm errorgroovy.lang.MissingMethodException: No signature of method: hubitat.zwave.Zwave.commandClass() is applicable for argument types: (java.lang.Short) values: [113] on line 164 (parse)

dev:36802019-01-26 03:31:34.649 pm debugzwaveEvent(): CRC-16 Encapsulation Command received: Crc16Encap(checksum:65535, command:5, commandClass:113, data:[0, 0, 0, 255, 7, 0, 0])

dev:36802019-01-26 03:31:11.728 pm errorgroovy.lang.MissingMethodException: No signature of method: hubitat.zwave.Zwave.commandClass() is applicable for argument types: (java.lang.Short) values: [113] on line 164 (parse)

dev:36802019-01-26 03:31:11.647 pm debugzwaveEvent(): CRC-16 Encapsulation Command received: Crc16Encap(checksum:65535, command:5, commandClass:113, data:[0, 0, 0, 255, 7, 8, 0])

SmartThings log for working motion sensor switch with firmware 5.39
(also generic zwave motion sensor works in SmartThings with this switch motion only of course again does not work with Hubitat)

zw:L type:1001 mfr:0063 prod:494D model:3032 ver:5.39 zwv:4.54 lib:03 cc:5E,72,5A,73,27,25,2B,2C,70,86,71,60,8E,85,59,7A,56 role:05 ff:8700 ui:8700 ep:['1001 5E,59,25', '0701 5E,59,71']

deb1b1fe-cf57-48e4-8b4b-fd8d3f041155 7:50:03 PM: debug Parse returned [[name:motion, value:active, descriptionText:GE Z-Wave Plus Motion Wall Switch detected motion, isStateChange:true, displayed:true, linkText:GE Z-Wave Plus Motion Wall Switch]]

deb1b1fe-cf57-48e4-8b4b-fd8d3f041155 7:50:03 PM: debug ---NOTIFICATION REPORT V3--- GE Z-Wave Plus Motion Wall Switch sent NotificationReport(eventParametersLength: 0, eventParameter: [], zensorNetSourceNodeId: 0, v1AlarmType: 0, reserved61: 0, notificationStatus: 255, sequence: false, event: 8, notificationType: 7, v1AlarmLevel: 0)

deb1b1fe-cf57-48e4-8b4b-fd8d3f041155 7:50:03 PM: debug parse() >> zwave.parse(zw device: 29, command: 7105, payload: 00 00 00 FF 07 08 00 )

deb1b1fe-cf57-48e4-8b4b-fd8d3f041155 7:48:38 PM: debug Parse returned [[name:motion, value:inactive, descriptionText:GE Z-Wave Plus Motion Wall Switch motion has stopped, isStateChange:true, displayed:true, linkText:GE Z-Wave Plus Motion Wall Switch]]

deb1b1fe-cf57-48e4-8b4b-fd8d3f041155 7:48:38 PM: debug ---NOTIFICATION REPORT V3--- GE Z-Wave Plus Motion Wall Switch sent NotificationReport(eventParametersLength: 0, eventParameter: [], zensorNetSourceNodeId: 0, v1AlarmType: 0, reserved61: 0, notificationStatus: 255, sequence: false, event: 0, notificationType: 7, v1AlarmLevel: 0)

deb1b1fe-cf57-48e4-8b4b-fd8d3f041155 7:48:38 PM: debug parse() >> zwave.parse(zw device: 29, command: 7105, payload: 00 00 00 FF 07 00 00 )

I'm surprised to see CRC-16 messages in there....

It may be time to just email Hubitat support. They are usually pretty quick to get these things straightened out - and it sounds like they will need to sooner or later anyway as more people get the new firmware... @mike.maxwell

I may have modded your code incorrectly
I re-installed your DH and in debug mode

Still no motion reporting but here are the error logs for motion
(side note when I pressed the switch manually the switch state was not updating unless I pressed refresh)

dev:36802019-01-26 03:58:55.580 pm errorgroovy.lang.MissingMethodException: No signature of method: hubitat.zwave.Zwave.commandClass() is applicable for argument types: (java.lang.Short) values: [113] on line 164 (parse)

dev:36802019-01-26 03:58:55.468 pm debugzwaveEvent(): CRC-16 Encapsulation Command received: Crc16Encap(checksum:65535, command:5, commandClass:113, data:[0, 0, 0, 255, 7, 0, 0])

dev:36802019-01-26 03:58:55.466 pm debugparse() >> zwave.parse(zw device: 76, command: 5601, payload: 71 05 00 00 00 FF 07 00 00 61 20 )

dev:36802019-01-26 03:58:33.184 pm errorgroovy.lang.MissingMethodException: No signature of method: hubitat.zwave.Zwave.commandClass() is applicable for argument types: (java.lang.Short) values: [113] on line 164 (parse)

dev:36802019-01-26 03:58:32.994 pm debugzwaveEvent(): CRC-16 Encapsulation Command received: Crc16Encap(checksum:65535, command:5, commandClass:113, data:[0, 0, 0, 255, 7, 8, 0])

dev:36802019-01-26 03:58:32.988 pm debugparse() >> zwave.parse(zw device: 76, command: 5601, payload: 71 05 00 00 00 FF 07 08 00 E8 89 )

I was mistaken debug must have timed out when I had the stock Hubitat Jasco motion sensor switch DH loaded. reran it and here are the logs still no motion reporting but make more sense.

dev:36802019-01-26 04:17:56.432 pm debugskip: AlarmReport(alarmLevel:0, alarmType:0)

dev:36802019-01-26 04:17:56.428 pm debugparse description: zw device: 76, command: 5601, payload: 71 05 00 00 00 FF 07 00 00 61 20

dev:36802019-01-26 04:17:33.527 pm debugskip: AlarmReport(alarmLevel:0, alarmType:0)

dev:36802019-01-26 04:17:33.523 pm debugparse description: zw device: 76, command: 5601, payload: 71 05 00 00 00 FF 07 08 00 E8 89

What version is your Hubitat hub on? CRC16 support was only recently added, which is why I ask.

Hubitat Elevationโ„ข Platform Version

2.0.4.118

Hardware Version

Rev C-3

OK, so which driver were those logs from:

  1. built-in
  2. your custom driver
  3. my custom driver
  1. built in
  1. your (my mod) custom driver

dev:36802019-01-26 03:31:34.778 pm error groovy.lang.MissingMethodException: No signature of method: hubitat.zwave.Zwave.commandClass() is applicable for argument types: (java.lang.Short) values: [113] on line 164 (parse)

dev:36802019-01-26 03:31:34.649 pm debug zwaveEvent(): CRC-16 Encapsulation Command received: Crc16Encap(checksum:65535, command:5, commandClass:113, data:[0, 0, 0, 255, 7, 0, 0])

dev:36802019-01-26 03:31:11.728 pm error groovy.lang.MissingMethodException: No signature of method: hubitat.zwave.Zwave.commandClass() is applicable for argument types: (java.lang.Short) values: [113] on line 164 (parse)

dev:36802019-01-26 03:31:11.647 pm debug zwaveEvent(): CRC-16 Encapsulation Command received: Crc16Encap(checksum:65535, command:5, commandClass:113, data:[0, 0, 0, 255, 7, 8, 0])

  1. my custom driver (JasonJoel's driver)

dev:36802019-01-26 03:58:55.580 pm errorgroovy.lang.MissingMethodException: No signature of method: hubitat.zwave.Zwave.commandClass() is applicable for argument types: (java.lang.Short) values: [113] on line 164 (parse)

dev:36802019-01-26 03:58:55.468 pm debugzwaveEvent(): CRC-16 Encapsulation Command received: Crc16Encap(checksum:65535, command:5, commandClass:113, data:[0, 0, 0, 255, 7, 0, 0])

dev:36802019-01-26 03:58:55.466 pm debugparse() >> zwave.parse(zw device: 76, command: 5601, payload: 71 05 00 00 00 FF 07 00 00 61 20 )

dev:36802019-01-26 03:58:33.184 pm errorgroovy.lang.MissingMethodException: No signature of method: hubitat.zwave.Zwave.commandClass() is applicable for argument types: (java.lang.Short) values: [113] on line 164 (parse)

dev:36802019-01-26 03:58:32.994 pm debugzwaveEvent(): CRC-16 Encapsulation Command received: Crc16Encap(checksum:65535, command:5, commandClass:113, data:[0, 0, 0, 255, 7, 8, 0])

dev:36802019-01-26 03:58:32.988 pm debugparse() >> zwave.parse(zw device: 76, command: 5601, payload: 71 05 00 00 00 FF 07 08 00 E8 89 )

  1. working SmartThings log

zw:L type:1001 mfr:0063 prod:494D model:3032 ver:5.39 zwv:4.54 lib:03 cc:5E,72,5A,73,27,25,2B,2C,70,86,71,60,8E,85,59,7A,56 role:05 ff:8700 ui:8700 ep:['1001 5E,59,25', '0701 5E,59,71']

deb1b1fe-cf57-48e4-8b4b-fd8d3f041155 7:50:03 PM: debug Parse returned [[name:motion, value:active, descriptionText:GE Z-Wave Plus Motion Wall Switch detected motion, isStateChange:true, displayed:true, linkText:GE Z-Wave Plus Motion Wall Switch]]

deb1b1fe-cf57-48e4-8b4b-fd8d3f041155 7:50:03 PM: debug ---NOTIFICATION REPORT V3--- GE Z-Wave Plus Motion Wall Switch sent NotificationReport(eventParametersLength: 0, eventParameter: [], zensorNetSourceNodeId: 0, v1AlarmType: 0, reserved61: 0, notificationStatus: 255, sequence: false, event: 8, notificationType: 7, v1AlarmLevel: 0)

deb1b1fe-cf57-48e4-8b4b-fd8d3f041155 7:50:03 PM: debug parse() >> zwave.parse(zw device: 29, command: 7105, payload: 00 00 00 FF 07 08 00 )

deb1b1fe-cf57-48e4-8b4b-fd8d3f041155 7:48:38 PM: debug Parse returned [[name:motion, value:inactive, descriptionText:GE Z-Wave Plus Motion Wall Switch motion has stopped, isStateChange:true, displayed:true, linkText:GE Z-Wave Plus Motion Wall Switch]]

deb1b1fe-cf57-48e4-8b4b-fd8d3f041155 7:48:38 PM: debug ---NOTIFICATION REPORT V3--- GE Z-Wave Plus Motion Wall Switch sent NotificationReport(eventParametersLength: 0, eventParameter: [], zensorNetSourceNodeId: 0, v1AlarmType: 0, reserved61: 0, notificationStatus: 255, sequence: false, event: 0, notificationType: 7, v1AlarmLevel: 0)

deb1b1fe-cf57-48e4-8b4b-fd8d3f041155 7:48:38 PM: debug parse() >> zwave.parse(zw device: 29, command: 7105, payload: 00 00 00 FF 07 00 00 )

I wish ge would stop screwing around with these devices.
Crc16 support was added to these drivers in 2.0.4, however it seems they are now using a different alarm event than they were before.

Since I don't have one of the "let's Implement crc16, because we can, even though it's depricated..." firmware versions...., and oh yeah, while we're at it, let's change the alarm report for no good reason...

So using the stock driver, if some one can tell me the alarm report commands that are skipped, one each for motion active, and a separate one for motion inactive I should be able to fix the stupid thing..,

Please pm me the results so I don't loose track, thanks.

3 Likes

sent

thanks

and thank you @JasonJoelOld for all the help

Ugh. I really don't understand why they would do EITHER of those things....

I was a fan of the zwave+ versions of this product line until now.

I love how they function, but these firmware shenanigans are BS.

I just installed 2 more of the 26933 dimmers earlier today, actually. Glad they were the same old non-goofy firmware level.

1 Like

Just got a few from Amazon across a week and they have all been 5.32 firmware.