Domoticz

Hi Pipiche,

I successfully paired two Aqara 2 button remote switches, but I don't get any events when I press one of the buttons. I had them on zigate before and then they worked without any problems. But now with the latest beta they don't do anything.

Can you please help?

Regards Ronald

I do notice an error during binding and a create group message which I don't understand.
Maybe this helps.

2020-05-02 21:57:42.810 Status: (Zigate2) Device Announcement Addr: 9bd1, IEEE: 00158d00031360ed Join Flag: 0x99 - Unknown value received. RSSI: 0
2020-05-02 21:57:43.827 Error: (Zigate2) ReadCluster - 0000 - 9bd1/01 Attribut ff01 received while device not inDB
2020-05-02 21:57:47.547 Status: (Zigate2) [0] NEW OBJECT: 9bd1 Model Name: lumi.remote.b286acn01
2020-05-02 21:57:52.510 Status: (Zigate2) [1] NEW OBJECT: 9bd1 Model Name: lumi.remote.b286acn01
2020-05-02 21:57:57.554 Status: (Zigate2) [2] NEW OBJECT: 9bd1 Model Name: lumi.remote.b286acn01
2020-05-02 21:58:02.540 Status: (Zigate2) [3] NEW OBJECT: 9bd1 Model Name: lumi.remote.b286acn01
2020-05-02 21:58:07.575 (Zigate2) Creation Group
2020-05-02 21:58:07.556 Status: (Zigate2) [4] NEW OBJECT: 9bd1 Model Name: lumi.remote.b286acn01

Not an issue

Ok, but not receiving the events anymore is
The switches are useless now

So if I summarize, you have been able to pair those 2 Aqara buttons, corresponding widgets have been created, but what ever you do on the button you don't see on Domoticz nor on the logs ?

Did you check the battery ?

Yep, that is correct.

I replaced the battery of one of them and rebind, but it didn't make a difference. I used them before on zigate and yesterday they also worked fine on the Xiaomi hub.

When I delete the widget and press a button I do get something is the log:

Spoiler: show

2020-05-03 13:09:09.930 (Zigate2) lookupForIEEE - looking for b250 in Neighbourgs table
2020-05-03 13:09:09.931 (Zigate2) Decode8102 - Receiving a message from unknown device : b250 with Data : 12b2500200120055002100020001
2020-05-03 13:09:09.931 (Zigate2) - [b250:02] ClusterID: 0012 AttributeID: 0055 Status: 00 Type: 21 Size: 0002 ClusterData: >0001<
2020-05-03 13:09:09.931 (Zigate2) Request for IEEE for short address: b250
2020-05-03 13:09:13.728 (Zigate2) lookupForIEEE - looking for b250 in Neighbourgs table
2020-05-03 13:09:13.728 (Zigate2) Decode8102 - Receiving a message from unknown device : b250 with Data : 13b2500100120055002100020001
2020-05-03 13:09:13.729 (Zigate2) - [b250:01] ClusterID: 0012 AttributeID: 0055 Status: 00 Type: 21 Size: 0002 ClusterData: >0001<
2020-05-03 13:09:13.729 (Zigate2) Request for IEEE for short address: b250

So I guess the device sends the state but the plugin doesn't pass it to the widget.

See also my raw device list attached. I tested with "Test switch".

Thanks for your help.

Indeed the Device you name 'Test switch' is communicating.

(1) It looks like it changes its Network Address, and the plugin reconnect it.

Could you get the latest beta branch

and redo the test with enabling debugWidget debugCluster

And share the logs when actioning the device

Sure, here is the result. Short adress is 61f6

Spoiler: show

2020-05-03 14:30:13.391 (Zigate2) Too early for a new update of LastSeen dccb
2020-05-03 14:30:13.392 (Zigate2) Too early for a new update of LastSeen dccb
2020-05-03 14:30:13.392 (Zigate2) ReadCluster - 0000 - dccb/01 AttrId: 0000 AttrType: 20 Attsize: 0001 Status: 00 AttrValue: 03
2020-05-03 14:30:13.393 (Zigate2) decodeAttribute( 20, 03)
2020-05-03 14:30:13.393 (Zigate2) ReadCluster - 0x0000 - ZCL Version: 3
2020-05-03 14:30:13.393 (Zigate2) decodeAttribute( 20, 03)
2020-05-03 14:30:13.393 (Zigate2) decodeAttribute( 20, 03)
2020-05-03 14:30:13.394 (Zigate2) Too early for a new update of LastSeen 94f3
2020-05-03 14:30:13.395 (Zigate2) Too early for a new update of LastSeen 94f3
2020-05-03 14:30:13.395 (Zigate2) ReadCluster - 0000 - 94f3/01 AttrId: 0000 AttrType: 20 Attsize: 0001 Status: 00 AttrValue: 03
2020-05-03 14:30:13.395 (Zigate2) decodeAttribute( 20, 03)
2020-05-03 14:30:13.395 (Zigate2) ReadCluster - 0x0000 - ZCL Version: 3
2020-05-03 14:30:13.395 (Zigate2) decodeAttribute( 20, 03)
2020-05-03 14:30:13.395 (Zigate2) decodeAttribute( 20, 03)
2020-05-03 14:30:13.648 (Zigate2) Too early for a new update of LastSeen 61f6
2020-05-03 14:30:13.649 (Zigate2) Too early for a new update of LastSeen 61f6
2020-05-03 14:30:13.649 (Zigate2) ReadCluster - 0012 - 61f6/01 AttrId: 0055 AttrType: 21 Attsize: 0002 Status: 00 AttrValue: 0001
2020-05-03 14:30:13.649 (Zigate2) readCluster - 0012 - 61f6/01 - MsgAttrID: 0055 MsgAttType: 21 MsgAttSize: 0002 MsgClusterData: 0001 Model: lumi.remote.b286acn01
2020-05-03 14:30:13.649 (Zigate2) decodeAttribute( 21, 0001)
2020-05-03 14:30:13.649 (Zigate2) ReadCluster - ClusterId=0012 - Switch Aqara: EP: 01 Value: 1
2020-05-03 14:30:13.650 (Zigate2) MajDomoDevice - Device ID : 00158d00031360ed - Device EP : 01 - Type : 0006 - Value : 1 - Hue : - Attribute_ :
2020-05-03 14:30:13.650 (Zigate2) ClusterSearch - Cluster: 0006, ProfileID: , ZDeviceID: , create: False
2020-05-03 14:30:13.650 (Zigate2) MajDomoDevice - Type = Switch
2020-05-03 14:30:13.650 (Zigate2) MajDomoDevice - NWKID = 61f6 IEEE = 00158d00031360ed Unit = 989
2020-05-03 14:30:13.650 (Zigate2) MajDomoDevice - {'0006': {'0000': 1}, 'ClusterType': {'989': 'DButton_3'}, '0012': {'0055': 1}}
2020-05-03 14:30:13.650 (Zigate2) MajDomoDevice - We have 1 EPs with ClusterType
2020-05-03 14:30:13.651 (Zigate2) MajDomoDevice - NWKID: 61f6 SwitchType: 18, DeviceType: DButton_3, ClusterType: Switch, old_nVal: 0 , old_sVal:

seems that I own you a beer .
Try with the new version on beta

haha, its beta so it's ok

I updated to latest beta, restarted domoticz, delteted the widget and rebind. And the result is the same, no evets.

Spoiler: show

2020-05-03 16:25:42.476 (Zigate2) Too early for a new update of LastSeen fa3a
2020-05-03 16:25:42.477 (Zigate2) Too early for a new update of LastSeen fa3a
2020-05-03 16:25:42.477 (Zigate2) ReadCluster - 0012 - fa3a/01 AttrId: 0055 AttrType: 21 Attsize: 0002 Status: 00 AttrValue: 0001
2020-05-03 16:25:42.478 (Zigate2) readCluster - 0012 - fa3a/01 - MsgAttrID: 0055 MsgAttType: 21 MsgAttSize: 0002 MsgClusterData: 0001 Model: lumi.remote.b286acn01
2020-05-03 16:25:42.478 (Zigate2) decodeAttribute( 21, 0001)
2020-05-03 16:25:42.478 (Zigate2) ReadCluster - ClusterId=0012 - Switch Aqara: EP: 01 Value: 1
2020-05-03 16:25:42.478 (Zigate2) MajDomoDevice - Device ID : 00158d00031360ed - Device EP : 01 - Type : 0006 - Value : 1 - Hue : - Attribute_ :
2020-05-03 16:25:42.478 (Zigate2) ClusterSearch - Cluster: 0006, ProfileID: , ZDeviceID: , create: False
2020-05-03 16:25:42.478 (Zigate2) MajDomoDevice - Type = Switch
2020-05-03 16:25:42.479 (Zigate2) MajDomoDevice - NWKID = fa3a IEEE = 00158d00031360ed Unit = 989
2020-05-03 16:25:42.479 (Zigate2) MajDomoDevice - {'0006': {'0000': 1}, 'ClusterType': {'989': 'DButton_3'}, '0012': {'0055': 1}}
2020-05-03 16:25:42.479 (Zigate2) MajDomoDevice - We have 1 EPs with ClusterType
2020-05-03 16:25:42.479 (Zigate2) MajDomoDevice - NWKID: fa3a SwitchType: 18, DeviceType: DButton_3, ClusterType: Switch, old_nVal: 0 , old_sVal:

Will look tonight


Envoyé de mon iPhone en utilisant Tapatalk

Ok, thanks

if you can try once more ?
just update beta branch, no need to remove the device and redo the pairing

Yes, it works again

I did found a typo, "Left double clink" should be "Left double click".

Thanks Pipiche

I was too early. I have likewise problem with my single button Aqara battery wall switch. It seems connected, but no reaction to switching, nothing in logs.
I had an hard time to re-include my switch after I removed it yesterday. Did git pull (now on 4.8.22) an re-including only was successfull after 8 times or so. But I read that is more often a problem with Aqara. Now I succesfully included it, it is still not reporting switches.

It is this switch:

Spoiler: show

Aqara-Wireless-Switch-Single-Double-Key-Button-Smart-Light-Control-ZigBee-Version-for-Mi-Home-APP.jpg_960x960.jpg (61.75 KiB) Viewed 870 times

Yep, that’s it. I never have problems binding Aqara devices. Only a few THB devices last week with low battery.
Maybe your battery is low also

OK, I changed the battery. Unpaired the switch, and re-paired it. Paring went OK first try. However still no reaction to pushing the switch.
EDIT: saw there was again an update of the plugin. After new git pull it works... Thanks Pipiche!