Uh, now none a bunch of my Zooz switches seem to be reporting physical events only digital ones.. even the V3's & 4's? My enbrighten fan switches are working as expected..
Something is afoot at the Circle K apparently - should I do a soft-reset?
Note: a Zooz bathroom light switch seems to be reporting physical events (System Zooz Central Scene Switch) but my kitchen dimmer is not - using community advanced zooz drivers.
So for my kitchen dimmer I switched to the System Central Scene dimmer.. did the configure/debug thing and physical is now reporting... note: this is a V4 dimmer not the V2 switch I have upstairs.
You can try my advanced driver on the older switches, you will just possibly get the "Pending Changes" message because it cannot sync up all the parameters. Otherwise it should work. I do have a parameter test which is supposed to hide any not working parameters as well to get rid of the pending message but I don't have any old devices to thoroughly test it.
@bcopeland, I will have to go in and see what of your old community drivers don't have other good options and should be revived. I will take you up on that offer to continue them when I get some time to do so.
Add this driver and run the command and give me the log output:
metadata {
definition(name: "Association Group Validator", namespace: "hubitat", author: "Bryan Copeland") {
command "checkAssociations"
}
}
import groovy.transform.Field
@Field static CMD_CLASS_VERSIONS = [0x6C:1, 0x85:2]
void checkAssociations() {
sendToDevice(new hubitat.zwave.commands.associationv2.AssociationGroupingsGet().format())
}
void zwaveEvent(hubitat.zwave.commands.associationv2.AssociationGroupingsReport cmd) {
List<String> cmds = []
for (int grp in 1..cmd.supportedGroupings.toInteger()) {
cmds.add(new hubitat.zwave.commands.associationv2.AssociationGet(groupingIdentifier: grp.shortValue()).format())
}
sendToDevice(cmds)
}
void zwaveEvent(hubitat.zwave.commands.associationv2.AssociationReport cmd) {
log.debug "Association Group ${cmd.groupingIdentifier} nodes: ${cmd.nodeId}"
}
void zwaveEvent(hubitat.zwave.Command cmd) {
log.debug "skip:${cmd}"
}
void zwaveEvent(hubitat.zwave.commands.securityv1.SecurityMessageEncapsulation cmd) {
hubitat.zwave.Command encapsulatedCommand = cmd.encapsulatedCommand(CMD_CLASS_VERS)
if (encapsulatedCommand) {
zwaveEvent(encapsulatedCommand)
}
}
void zwaveEvent(hubitat.zwave.commands.supervisionv1.SupervisionGet cmd) {
hubitat.zwave.Command encapsulatedCommand = cmd.encapsulatedCommand(CMD_CLASS_VERS)
if (encapsulatedCommand) {
zwaveEvent(encapsulatedCommand)
}
sendToDevice(zwave.supervisionV1.supervisionReport(sessionID: cmd.sessionID, reserved: 0, moreStatusUpdates: false, status: 0xFF, duration: 0).format())
}
void parse(String description) {
if (logEnable) log.debug "parse:${description}"
hubitat.zwave.Command cmd = zwave.parse(description, CMD_CLASS_VERS)
if (cmd) {
zwaveEvent(cmd)
}
}
void sendToDevice(List<String> cmds, Long delay=300) {
sendHubCommand(new hubitat.device.HubMultiAction(commands(cmds, delay), hubitat.device.Protocol.ZWAVE))
}
void sendToDevice(String cmd, Long delay=300) {
sendHubCommand(new hubitat.device.HubAction(zwaveSecureEncap(cmd), hubitat.device.Protocol.ZWAVE))
}
List<String> commands(List<String> cmds, Long delay=300) {
return delayBetween(cmds.collect{ zwaveSecureEncap(it) }, delay)
}
Great..
Well that was uneventful .. Ha.. But at least the hub is in group 1.. So I'm at a loss as to why it's not reporting physical..
Not really sure what to make of that.
Is that Great... (please dont) -or- Great! (thanks) ?
I am totally confuzzled.... I switched to the "generic z-wave" and it only is showing the physical "off" events and as "digital" no less... .
I am going to powerdown then maybe do a soft-reset for fun. Going to set the V2's to Zooz central and try again...
So after rebooting (no SR) the guest room light switch set to the system "Zooz Central Scene driver" is ignoring physical events for some reason... It does appear to be responsive from the device page, something that I was having trouble with earlier..
Note: it appears ALL my Zooz V2 switches are behaving this way under Zooz Central Scene driver.. just tested on my laundry room light...
So my kitchen dimmer a Zen24v4 Zen74 dimmer with firmware v1.2 is not working with the system "Zooz Central Scene" driver now.. I mean it's not showing up in the logs or events when I toggle either via the device page or physically....
However... it IS working with maker api - in Node-RED my kitchen lights respond as they should..
The V2 guest room lights do not report..
EDIT: I confused Zen24 with the new Zen74 I just put in for my kitchen recessed lights, sorry!!!
For the V2 - I tried the:
and am still getting the behavior where it will not report until I hit refresh. The "Generic Z-wave Switch" works but does not report "physical" or "digital"..
edit: The Zen23/24 V2s are supposed to be Z-Wave+ I thought... but this behavior would make more sense if they were just standard Z-Wave devices.
... And that would truly suck as at the time I put them in I was purposefully replacing all my regular Z-Wave devices... sigh.
They are Z-Wave+ devices!
- deviceType: 45329
- inClusters: 0x5E,0x86,0x72,0x5A,0x73,0x85,0x59,0x25,0x27,0x20,0x70
- zwNodeInfo: D3 9C 00 04 10 01 5E 86 72 5A 73 85 5C 59 25 27 20 70 68 23
- firmwareVersion: 20.15
- deviceId: 9500
- manufacturer: 634
So I have a V2 switch in my closet that is activated by a motion sensor... The V2 switch is set to "Generic Z-Wave Smart Switch"... it works fine but does not show up in the Events or Logs when it fires.. it will also not respond on the device page when I click "on" or "off" unless I hit refresh first.
Still testing this - why in the world does the "Generic Z-Wave Switch" work fine without refresh and yet the others do not..
I would try Bryans driver from above and press the physical buttons to see what event gets logged. Or you could also try my Zooz switch driver and go to the very bottom and uncomment the tracing which will show tons of details. You should be getting a "BasicReport" on physical button presses, that is how my driver determines the difference between a physical tap and a digital on/off event.
Seeing what reports are being sent by the device is the first step to solving it.
Yep tried Bryans and no luck - was not reporting anything physical at all or digital without a refresh being sent. I'm banging my head against the wall trying to figure out why...
Your drivers work wonderfully well with the newer switches.. (thank you so much for those!!!!) I may give that a shot with the V2's to see if I can't figure something out and let you guys know..
Unfortunately for me swapping out the V2s is kind of painful - looking at 10 switches or so.. My goal is on/off events with "type". With the generic basic z-wave switch driver I get the first bit not the second.
Was also thinking maybe some unknown/advanced parameters are getting set where they shouldnt be with the V2s - alas the basic Z-Wave report shows nothing.
I meant try this driver he posted code for above, not his actual switch driver. When you then press the buttons on the device I would be curious to see what that driver logs. It should be logging a "BasicReport". Or using the super generic "Device" driver I think would accomplish the same thing. Just a very simple driver that logs everything coming in.
EDIT: You could also try switching to the custom "Basic ZWAVE Tool" driver or my ZWave Tweaker that I posted and do a parameter scan so we can see what all the parameters are set to. I think those old switches only had a couple parameters, they were pretty basic.
I did and posted the results... see the above pic. Weird right?
I tried the Basic Z-Wave tool because I had installed - parameters 0-255 were all '0'
Download the Hubitat app
