Kwikset 916 Zigbee Lock Error in log :CommandResponse skipped clusterId:8032

I have a Kwikset 916 Zigbee lock that when anything addresses it, it posts an error in the log. I have hit "configure", doesn't correct. I am using the generic zigbee lock driver. Does anybody have any Idea what is causing this?

warnCommandResponse skipped clusterId:8032, descMap:[raw:catchall: 0000 8032 00 00 0040 00 99FB 00 00 0000 00 00 00000A0109000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000, profileId:0000, clusterId:8032, clusterInt:32818, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:99FB, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[00, 00, 0A, 01, 09, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00]]

Attached is a screen shot of the log:

I would turn off debug logging. If that cluster isn't available and the driver uses it for something you may get that error. Turn off debugging and then on the device page click configure and wait a minute and see if it goes away. (I'm going to assume when you click on the orange/yellow warn that it does indeed take you to the lock and not something else?

Thats a warn not an error, in any event these messages are used for debugging and can be ignored. They are only exposed when debug logging is enabled.

1 Like

Great! Thanks that was easy.....

1 Like

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