Centralite 3400 - lots of catchall logs

[christian.busch]

Hi, picked up a Centralite 3400 4210c V2.

Im getting a lot of catch all messages. Is that normal?

dev:42392022-10-13 17:11:05.923debugdescMap: [raw:catchall: 0104 0501 01 01 0040 00 2392 01 00 0000 07 00 , profileId:0104, clusterId:0501, clusterInt:1281, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:2392, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:07, direction:00, data:[]]
dev:42392022-10-13 17:11:04.875infoskipped: [raw:catchall: 0000 0013 00 00 0040 00 2392 00 00 0000 00 00 909223C72C3105006F0D0080, profileId:0000, clusterId:0013, clusterInt:19, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:2392, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[90, 92, 23, C7, 2C, 31, 05, 00, 6F, 0D, 00, 80]], description:catchall: 0000 0013 00 00 0040 00 2392 00 00 0000 00 00 909223C72C3105006F0D0080
dev:42392022-10-13 17:11:04.868debugdescMap: [raw:catchall: 0000 0013 00 00 0040 00 2392 00 00 0000 00 00 909223C72C3105006F0D0080, profileId:0000, clusterId:0013, clusterInt:19, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:2392, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[90, 92, 23, C7, 2C, 31, 05, 00, 6F, 0D, 00, 80]]
dev:42392022-10-13 17:11:03.230infoKP MBR Keypad was disarmed [physical]
dev:42392022-10-13 17:11:01.607tracesendArmResponse- sucess, bin:-1, armMode:01 -> armRequest:00, exitDelay:0, isInitiator:true, lcData:[isValid:true, isInitiator:true, code:6767, name:TV, codeNumber:3]
dev:42392022-10-13 17:11:01.592debugdescMap: [raw:catchall: 0104 0501 01 01 0040 00 2392 01 00 0000 00 00 00043637363700, profileId:0104, clusterId:0501, clusterInt:1281, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:2392, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[00, 04, 36, 37, 36, 37, 00]]
dev:42392022-10-13 17:10:48.427debuggetMotionResult: active
dev:42392022-10-13 17:10:48.422debugdescMap: [raw:catchall: 0104 0501 01 01 0040 00 2392 01 00 0000 07 00 , profileId:0104, clusterId:0501, clusterInt:1281, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:2392, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:07, direction:00, data:[]]
dev:42392022-10-13 17:10:47.529infoKP MBR Keypad is active
dev:42392022-10-13 17:10:47.439infoKP MBR Keypad is active
dev:42392022-10-13 17:10:47.418debuggetMotionResult: active
dev:42392022-10-13 17:10:47.413debugdescMap: [raw:catchall: 0104 0501 01 01 0040 00 2392 01 00 0000 07 00 , profileId:0104, clusterId:0501, clusterInt:1281, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:2392, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:07, direction:00, data:[]]
dev:42392022-10-13 17:10:47.399debuggetMotionResult: active
dev:42392022-10-13 17:10:47.393debugdescMap: [raw:catchall: 0104 0501 01 01 0040 00 2392 01 00 0000 07 00 , profileId:0104, clusterId:0501, clusterInt:1281, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:2392, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:07, direction:00, data:[]]
dev:42392022-10-13 17:10:43.315infoskipped: [raw:catchall: 0000 0013 00 00 0040 00 2392 00 00 0000 00 00 8F9223C72C3105006F0D0080, profileId:0000, clusterId:0013, clusterInt:19, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:2392, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[8F, 92, 23, C7, 2C, 31, 05, 00, 6F, 0D, 00, 80]], description:catchall: 0000 0013 00 00 0040 00 2392 00 00 0000 00 00 8F9223C72C3105006F0D0080
dev:42392022-10-13 17:10:43.308debugdescMap: [raw:catchall: 0000 0013 00 00 0040 00 2392 00 00 0000 00 00 8F9223C72C3105006F0D0080, profileId:0000, clusterId:0013, clusterInt:19, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:2392, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[8F, 92, 23, C7, 2C, 31, 05, 00, 6F, 0D, 00, 80]]
dev:42392022-10-13 17:10:41.655infoKP MBR Keypad was armed home [physical]
dev:42392022-10-13 17:10:40.013tracesendArmResponse- sucess, bin:-1, armMode:00 -> armRequest:01, exitDelay:0, isInitiator:true, lcData:[isValid:true, isInitiator:true, code:0000, name:not required, codeNumber:-1]
dev:42392022-10-13 17:10:40.006debugdescMap: [raw:catchall: 0104 0501 01 01 0040 00 2392 01 00 0000 00 00 01043637363700, profileId:0104, clusterId:0501, clusterInt:1281, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:2392, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[01, 04, 36, 37, 36, 37, 00]]

[bertabcd1234]

Are you expecting traffic from the device at that time (e.g., because you just armed/disarmed it or it detected motion)? If so, that looks pretty normal to me. Debug logging is enabled by default for 30 minutes after you add a device (or manually enable it), then self-disables after that time. The "info" logs are descriptionText logging and are enabled by default and indefinitely, though you can turn them off at any time. Neither will help a device that is spamming your hub with reports unexpectedly, but this all looks normal to me, assuming it's not unexpected to you.

Eventually, it will settle on just showing the "info" logs, which generally represent what events the information from the device translated into, which you may care to have for troubleshooting (but can disable if you really don't, and it's also available from the "Events" tab on the device detail page).

[christian.busch]

Cool, thank you. wasn’t sure. Thought with a proper driver there wouldn’t be any catch alls.