No problem. I'll remember that for future. I hope this is what you need?
Yup, perfect
I spoke too soon. I guess I hadn't waited long enough because the one I reported as working just exhibited the same issue as before. So other than providing a new fingerprint for the driver, I did not help anything.
@lelynch I have posted my driver to help with this issue until a fix is found. Please see below.
Thank you! I'll will load up your driver and see how it does. Also, now that I've had about a day with the new firmware installed on the buttons, the issue seems to be more random whereas before I could pretty much count on the issue after a certain period of time.
in case this helps:
2018-12-31 12:55:01.390 pm [debug] zigbee.parseDescriptionAsMap-read attr: [raw:DE530104020A000029F707, dni:DE53, endpoint:01, cluster:0402, size:0A, attrId:0000, encoding:29, value:07F7, clusterInt:1026, attrInt:0]
2018-12-31 12:55:01.388 pm [debug] parse: read attr - raw: DE530104020A000029F707, dni: DE53, endpoint: 01, cluster: 0402, size: 0A, attrId: 0000, encoding: 29, value: 07F7
I just noticed a “double” event on my new Samsung button. Will there be a fix for this?
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.