Im seeing this every few mins.
The internal driver has a bug and only looks for clusterid 6 and doesnt require profileId = "0104"
My driver doesn't trigger a button press because I require the 104. But the internal driver creates false button presses when it sees this.
Something in the hub causes the device to send this. Its not a driver problem.
It did this before and was fixed but now its back.
It happened after one of the updates made changes to ZigBee.
profileId:0000 clusterId:0006 clusterInt:6 sourceEndpoint00 destinationEndpoint00 options:0040 command:00 data:[59, FD, FF, 04, 01, 01, 19, 00, 00]
Map [raw:catchall: 0000 0006 00 00 0040 00 F7F6 00 00 0000 00 00 65FDFF040101190000, profileId:0000, clusterId:0006, clusterInt:6, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:F7F6, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[65, FD, FF, 04, 01, 01, 19, 00, 00]]
This will run down the battery and causing lots of traffic....
