ThirdReality Buttons Intermittent Double Tap

🛎️ Get Help Devices
1

I bought a handful of ThirdReality buttons but they are intermittently failing to send double taps. I'm able to reproduce this by watching the raw data coming in while having them set to the "Device" driver. Here's a log output from one where I double tapped three times in a row. I used the same timing for the double tap each time, but only the last instance actually registered as a double (value:0002 is a double, value:0001 is a single; from what I can tell).

Has anyone else had this issue? I messaged them via Facebook and was told they'd get back to me on Monday, but I'm really ready to just send them back.

Logs 
dev:20692022-12-16 04:39:21.490 PMinfoZigbee parsed:[raw:CF0F0100120A5500210200, dni:CF0F, endpoint:01, cluster:0012, size:0A, attrId:0055, encoding:21, command:0A, value:0002, clusterInt:18, attrInt:85]
dev:20692022-12-16 04:39:21.473 PMinfoZigbee parsed:[raw:catchall: 0104 0006 01 01 0040 00 CF0F 01 00 0000 00 00 , profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:CF0F, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[]]
dev:20692022-12-16 04:39:20.193 PMinfoZigbee parsed:[raw:CF0F0100120A5500210100, dni:CF0F, endpoint:01, cluster:0012, size:0A, attrId:0055, encoding:21, command:0A, value:0001, clusterInt:18, attrInt:85]
dev:20692022-12-16 04:39:20.174 PMinfoZigbee parsed:[raw:catchall: 0104 0006 01 01 0040 00 CF0F 01 00 0000 01 00 , profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:CF0F, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:01, direction:00, data:[]]
dev:20692022-12-16 04:39:18.099 PMinfoZigbee parsed:[raw:CF0F0100120A5500210100, dni:CF0F, endpoint:01, cluster:0012, size:0A, attrId:0055, encoding:21, command:0A, value:0001, clusterInt:18, attrInt:85]
dev:20692022-12-16 04:39:18.095 PMinfoZigbee parsed:[raw:catchall: 0104 0006 01 01 0040 00 CF0F 01 00 0000 01 00 , profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:CF0F, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:01, direction:00, data:[]]
dev:20692022-12-16 04:39:08.562 PMinfoZigbee parsed:[raw:CF0F0100120A5500210100, dni:CF0F, endpoint:01, cluster:0012, size:0A, attrId:0055, encoding:21, command:0A, value:0001, clusterInt:18, attrInt:85]
dev:20692022-12-16 04:39:08.557 PMinfoZigbee parsed:[raw:catchall: 0104 0006 01 01 0040 00 CF0F 01 00 0000 01 00 , profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:CF0F, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:01, direction:00, data:[]]
2

Give them a chance, I have some other buttons that screw up double click sometimes.

3

I have a ZEN34 that works without a hitch, but are a bit pricier.

I'll give them a chance but if it turns into a prolonged endeavor, I'll send them back. I should add, it's not intermittent....its more like an 80% fail rate.

4

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