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
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:
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: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)
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)
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: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)
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 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: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: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: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)
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.