This is exactly the behavior I was experiencing before I applied Hub 698 update. Now, it’s been connected and still working 17 hours later.
I assume you’re running on the new .698 update, so the other thing I did that may have help was to remove all of my Xiaomi devices and Reset the ZigBee Stick (in Settings > Zigbee Information). If you do the same just be aware that all Zigbee devices will lose their connection, and need to be rejoined (though they will still be in the Devices list, so that should just involve using the “Discover Devices” mode and putting the devices in pairing mode).
That is the “status report” and your button’s voltage data is present. I’ve boldfaced it. It’s big-endian so the value is
0BEC, which is equal to 3052, divided by 1000 to give us 3.052 Volts.
That message is another kind of announcement message. ZigBee Cluster
0000 is for “Basic” information about the device, and Attribute ID
0005 of cluster
0000 is for the Model Identifier.
If you take the value
126C756D692E73656E736F725F737769746368 and convert it to ASCII text, it’s
Don’t worry about sending more of the
read attr - raw: messages for the button, as I’ve already got all of that from mine. Really what I’d like to help get working for you is the connection, seeing as my button is staying connect while your is not for some reason.
By they way, I’ve posted all of my findings on the button over here, and would love any input on what you think would be a good way to set up the device drivers’ output of the messages received from the button.
Thanks again for sharing feedback!