ColorReport z-wave event ignored

🛎️ Get Help
, ,
1

Hello there! Is there any reason that the following would get ignored?

def createEvent(hubitat.zwave.commands.switchcolorv2.SwitchColorReport cmd) {
    log.debug "color report $cmd"
}

I have a catchall method afterwards that routinely shows this event

def createEvent(hubitat.zwave.Command cmd,	Map map) {
	 // Handles any Z-Wave commands we aren't interested in
	 log.debug "UNHANDLED COMMAND $cmd $map"
}

Logs are as such:

2020-11-09 04:38:05.567 pm debugUNHANDLED COMMAND SwitchColorReport(colorComponent:warmWhite, colorComponentId:0, value:0) [canBeCurrentState:false, linkText:Cabinet lights, isStateChange:false, displayed:false, descriptionText:zw device: 4D, command: 3304, payload: 00 00 , isMulticast: false, value:zw device: 4D, command: 3304, payload: 00 00 , isMulticast: false]
2

Change "createEvent" to "zwaveEvent"?

3

Tried both, no dice :frowning:

4

In the hubitat docs for switchcolorv2 it actually lists that specific item as "v3"... I wonder if that typo persists in the actual back end definition?

Note the "v3" in the documented v2 function:

Switch Color Get
Command 0x03

 class hubitat.zwave.commands.switchcolorv3.SwitchColorReport {
     String colorComponent
     short colorComponentId
 
     List<Short> getPayload()
     String format()
 }

From this page:
https://docs.hubitat.com/index.php?title=ZWave_Classes

5

Strangely enough, I attempted switchcolorv3 in a first pass since the triggering method is zwave.switchColorV3.switchColorGet.

Yet for some reason neither gets picked up on the response...

6

Sorry I couldn't be of more help. I don't have any zwave color supporting devices to test against.

1 Like
8

If anyone from the Hubitat team has any ideas, it does seem like a bug. @bravenel just pinging you as you recommended taking this approach as opposed to emailing support.

The summary is, I’m able to log the z-wave event as seen above with the methods provided, but can’t seem to catch the event in a dedicated method to parse the data coming back.

9

I guess in truth I can always just build our a switch case to handle the payload as a workaround. But it seems like best practices would have us use these zwaveEvent hooks. Not sure why this one doesn’t work.

10

Can you post the whole driver.. More specifically I'm interested in your parse method..

are you specifying the command class versions when invoking zwave.parse ?

11

I have corrected the docs.. thanks for pointing that out..

12

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.