Can sequential messages be received in < 1ms?

2.3.1.142 on a C7

@bobbyD @gopher.ny

I'm troubleshooting an issue with a custom Zigbee device. It should be sending 6 bytes every 5 minutes. The data is a measurement so it is likely a number of messages will be identical.
periodically the hub reports split messages often within a ms or less.

Can you tell from the below log data if the issue is likely from the source or from the decoding by the Hub? I suspect it is from the source but any supporting (or not) opinion would be helpful.

Thanks
John

metadata{

    definition(name: "Zigbee Log Message", namespace: "johnrob", author: "johnr"){
        capability "Actuator"
        capability "Sensor"

        fingerprint profileId: "0104", outClusters: "0000", inClusters: "0000, 0B05, 0014"
    }
    preferences{
    }
}  //  --- metadata ---

def parse(String description){
     pauseExecution(2000) 
     log.info  " Raw Description  ${description}"
     pauseExecution(2000)
}

below is same data as screenshot. Might be more readable.

2022-04-30 05:38:39.994 pm info Raw Description  read attr - raw: F376010014140E004106010619160104, dni: F376, endpoint: 01, cluster: 0014, size: 14, attrId: 000E, encoding: 41, command: 0A, value: 06010619160104
2022-04-30 05:43:50.403 pm info Raw Description  read attr - raw: F376010014140E004106010619160104, dni: F376, endpoint: 01, cluster: 0014, size: 14, attrId: 000E, encoding: 41, command: 0A, value: 06010619160104
2022-04-30 05:49:00.792 pm info Raw Description  read attr - raw: F376010014140E004106010619160104, dni: F376, endpoint: 01, cluster: 0014, size: 14, attrId: 000E, encoding: 41, command: 0A, value: 06010619160104
2022-04-30 05:54:11.190 pm info Raw Description  read attr - raw: F376010014140E004106010619160104, dni: F376, endpoint: 01, cluster: 0014, size: 14, attrId: 000E, encoding: 41, command: 0A, value: 06010619160104
2022-04-30 05:59:21.593 pm info Raw Description  read attr - raw: F376010014140E004106010618160104, dni: F376, endpoint: 01, cluster: 0014, size: 14, attrId: 000E, encoding: 41, command: 0A, value: 06010618160104
2022-04-30 06:04:32.015 pm info Raw Description  read attr - raw: F376010014140E00410601061A150404, dni: F376, endpoint: 01, cluster: 0014, size: 14, attrId: 000E, encoding: 41, command: 0A, value: 0601061A150404
2022-04-30 06:09:42.485 pm info Raw Description  read attr - raw: F376010014140E004106010619160504, dni: F376, endpoint: 01, cluster: 0014, size: 14, attrId: 000E, encoding: 41, command: 0A, value: 06010619160504
2022-04-30 06:14:52.951 pm info Raw Description  read attr - raw: F3760100140A0E00410104, dni: F376, endpoint: 01, cluster: 0014, size: 0A, attrId: 000E, encoding: 41, command: 0A, value: 0104
2022-04-30 06:14:52.956 pm info Raw Description  read attr - raw: F376010014100E00410401061915, dni: F376, endpoint: 01, cluster: 0014, size: 10, attrId: 000E, encoding: 41, command: 0A, value: 0401061915
2022-04-30 06:20:03.346 pm info Raw Description  read attr - raw: F376010014140E00410601061A150004, dni: F376, endpoint: 01, cluster: 0014, size: 14, attrId: 000E, encoding: 41, command: 0A, value: 0601061A150004
2022-04-30 06:25:13.601 pm info Raw Description  read attr - raw: F376010014140E00410601061A150904, dni: F376, endpoint: 01, cluster: 0014, size: 14, attrId: 000E, encoding: 41, command: 0A, value: 0601061A150904
2022-04-30 06:30:24.018 pm info Raw Description  read attr - raw: F376010014140E00410601061A150804, dni: F376, endpoint: 01, cluster: 0014, size: 14, attrId: 000E, encoding: 41, command: 0A, value: 0601061A150804
2022-04-30 06:35:34.413 pm info Raw Description  read attr - raw: F376010014140E00410601061A150804, dni: F376, endpoint: 01, cluster: 0014, size: 14, attrId: 000E, encoding: 41, command: 0A, value: 0601061A150804
2022-04-30 06:40:44.817 pm info Raw Description  read attr - raw: F376010014140E00410601061A150804, dni: F376, endpoint: 01, cluster: 0014, size: 14, attrId: 000E, encoding: 41, command: 0A, value: 0601061A150804
2022-04-30 07:37:39.261 pm info Raw Description  read attr - raw: F376010014140E00410601061D150004, dni: F376, endpoint: 01, cluster: 0014, size: 14, attrId: 000E, encoding: 41, command: 0A, value: 0601061D150004

i only see one read attribute set that's a few ms after another one and the second of them appears to contain invalid data.
It's not likely this is being generated by the hub, but the only way to find out for sure is by sniffing the traffic for this device.

1 Like