-
-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Model Certification] - Aotec Zigbee Button #12
Comments
Thanks. I'll see what I can do with that. Do you want to keep the Voltage widget (as I believe the Battery level is provided ) ? Would you mind providing the same log when "holding" the button ? |
Yes, Voltage widget looks fine and lets keep it; there is currently "2.6V". Lets see what happens when battery is depleted. Here is what happens with long press of button: Button was again in the state where we don't get the attribute messages after clicking, hence only this short one above. 2023-10-17 00:42:29,631 INFO :b'ZigateRead - MsgType: 8002, Data: 00010405000101025cda020000097100030000000000, LQI: 48' |
And to avoid confusion; these lines are some additional debug info I added to "Modules/input.py": 2023-10-17 00:39:35,158 INFO :b'button = 03' I'm running: No problems to move 7.1.004 |
After upgrade and restart and redoing the pairing, I do get the three widgets. Temperature and voltage widgets are fine. Now I get after double click But Domoticz widget doesn't change to "Double Click". It will stay at "Click". If I manually change Domoticz switch selector to "Double Click", there is message Then, after single click and Domoticz widged changes to "Click". |
did you enable the ZclCluster debug parameter ? |
Yes I did, there are some bunch of stuff coming when I enable it 2023-10-18 10:02:17,939 INFO :b' _majdomo_formater: None' However, nothing seems to come directly related to button click. Maybe it is related what I reported earlier, sometimes I got more logging events when button is pressed, sometimes it just stopped and only the short ones with IAS Zone information appeared. The IAS Zone information seems to be the only reliable one that happens after button click. After upgrade and re-pairing I don't seem to get the "more logging events" after click anymore, only the IAS message thing I reported. |
can you simply redo the same test as you did in introduction: Logs for 1 click |
All three clicking functions do pretty much same:
1 click: 2 clicks: hold: |
Can you check the Domoticz log to see if there is no errors ? this is weird as you get less logs than before, so i suspect a mistake on my end |
I can't see any errors, neither in Domoticz log nor plugin log with debug settings you provided. Something seems to have changed, either with upgrade from 7.1.001 to 7.1.004 or with aotec-button. Button does not have any "0006" listed in EP1 raw devices, does it have any consequences? |
Hold on, now I found some errors which happened during pairing process! Oct 17 23:37:29 curder domoticz[2896260]: 2023-10-17 23:37:29.642 Status: ZiggiS: [None] NEW OBJECT: 4efc None |
that is what I'm looking for. I think I understood. let me come back to you later. |
Aotec Button is small button, which have three clicking operations for button
single click
double click
long press
It has also temperature sensor for ambient temperature
https://aeotec.com/products/aeotec-button/
Document as much what works, what doesn't work, what do you miss, what do you need
Aotech Button pairs with z4d. Three widgets are created
Button Voltage
Button Temperature
Button Switch, type Door switch
Button Temperature widget operates as expected and shows device ambient temperature.
Button switch widget doesn't work satisfactorily:
Only single click is detected and widget changes to "Door Open".
After a while (30-60 seconds), widget changes back to "Door Closed" autonomously.
Widget doesn't respond to double clicks and long presses.
Sometimes also single click is not detected by widget.
Following snips for Debug log indicate that pressing button create 0500 cluster messages, where alarm1 and alarm2 are activated depending on click type. For single click, alarm1 is activated. For double click, alarm2 is activated. For long press, both alarm1 and alarm2 are activated.
After widget stops responding to single click, I could still see 0500 cluster messages after clicking button, even though widget didn't respond. Seems some attribute reports are missing from log in that case.
Debug Logs from single click, button short id 5cda:
2023-10-16 23:53:57,495 INFO :b'ZigateRead - MsgType: 8002, Data: 00010405000101025cda020000090d00010000000000, LQI: 45'
2023-10-16 23:53:57,496 INFO :b'zcl_decoders sending a default response for command 00'
2023-10-16 23:53:57,497 INFO :b'zcl_decoders Zcl.ddr: 0 GlobalCommand: False Sqn: 0d ManufCode: None Command: 00 Data: 010000000000 Payload: 090d00010000000000'
2023-10-16 23:53:57,503 INFO :b'buildframe_8401_cmd - 5cda 01 0500 Data: 010000000000'
2023-10-16 23:53:57,507 INFO :b'Decode8401 - Reception Zone status change notification: 0d010500025cda000100000000'
2023-10-16 23:53:57,509 INFO :b'Decode8401 - MsgSQN: 0d MsgSrcAddr: 5cda MsgEp:01 MsgClusterId: 0500 MsgZoneStatus: 0001 MsgExtStatus: 00 MsgZoneID: 00 MsgDelay: 0000'
2023-10-16 23:53:57,509 INFO :b'IAS Zone for device:5cda - alarm1: 1, alarm2: 0, tamper: 0, battery: 0, Support Reporting: 0, restore Reporting: 0, trouble: 0, acmain: 0, test: 0, battdef: 0'
2023-10-16 23:53:57,510 INFO :b'Decode8401 MsgZoneStatus: 01 '
2023-10-16 23:53:57,511 INFO :b'get_device_config_param: 5cda Config: MotionViaIASAlarm1'
2023-10-16 23:53:57,512 INFO :b'MotionViaIASAlarm1 = None'
2023-10-16 23:53:57,514 INFO :b'button = 01'
2023-10-16 23:53:57,516 INFO :b'ZigateRead - MsgType: 8002, Data: 00010405000101025cda020000080e0a0200190100, LQI: 45'
2023-10-16 23:53:57,536 INFO :b'zcl_decoders sending a default response for command 0a'
2023-10-16 23:53:57,543 INFO :b'zcl_decoders Zcl.ddr: 0 GlobalCommand: True Sqn: 0e ManufCode: None Command: 0a Data: 0200190100 Payload: 080e0a0200190100'
2023-10-16 23:53:57,544 INFO :b'zcl_decoders Sqn: 14/0e ManufCode: None Command: 0a Data: 0200190100 '
2023-10-16 23:53:57,546 INFO :b'buildframe_report_attribute_response - 5cda 01 0500 Data: 0200190100'
2023-10-16 23:53:57,547 INFO :b'Decode8102 - Attribute Reports: [5cda:01] MsgSQN: 0e ClusterID: 0500 AttributeID: 0002 Status: 00 Type: 19 Size: 0002 ClusterData: >0001<'
2023-10-16 23:53:57,548 INFO :b'scan_attribute_reponse - Sqn: 0e i_sqn: 0e Nwkid: 5cda Ep: 01 Cluster: 0500 MsgData: 0e5cda0105000002001900020001 Type: 8102'
2023-10-16 23:53:57,549 INFO :b'scan_attribute_reponse - 8102 idx: 28 Read Attribute Response: [5cda:01] ClusterID: 0500 MsgSQN: 0e, i_sqn: 0e, AttributeID: 0002 Status: 00 Type: 19 Size: 0002 ClusterData: >0001<'
2023-10-16 23:53:57,550 INFO :b'Decode8102 - LQI: 45 Received Cluster:0500 Attribute: 0002 Value: 0001 from (5cda/01)'
2023-10-16 23:53:58,127 INFO :b'ZigateRead - MsgType: 8011, Data: 005cda, LQI: 45'
after a while, autonomous messages in log and widget responds "Door Closed"
2023-10-16 23:54:58,070 INFO :b'ZigateRead - MsgType: 8002, Data: 00010405000101025cda020000080f0a0200190000, LQI: 45'
2023-10-16 23:54:58,071 INFO :b'zcl_decoders sending a default response for command 0a'
2023-10-16 23:54:58,072 INFO :b'zcl_decoders Zcl.ddr: 0 GlobalCommand: True Sqn: 0f ManufCode: None Command: 0a Data: 0200190000 Payload: 080f0a0200190000'
2023-10-16 23:54:58,074 INFO :b'zcl_decoders Sqn: 15/0f ManufCode: None Command: 0a Data: 0200190000 '
2023-10-16 23:54:58,075 INFO :b'buildframe_report_attribute_response - 5cda 01 0500 Data: 0200190000'
2023-10-16 23:54:58,076 INFO :b'Decode8102 - Attribute Reports: [5cda:01] MsgSQN: 0f ClusterID: 0500 AttributeID: 0002 Status: 00 Type: 19 Size: 0002 ClusterData: >0000<'
2023-10-16 23:54:58,079 INFO :b'scan_attribute_reponse - Sqn: 0f i_sqn: 0f Nwkid: 5cda Ep: 01 Cluster: 0500 MsgData: 0f5cda0105000002001900020000 Type: 8102'
2023-10-16 23:54:58,080 INFO :b'scan_attribute_reponse - 8102 idx: 28 Read Attribute Response: [5cda:01] ClusterID: 0500 MsgSQN: 0f, i_sqn: 0f, AttributeID: 0002 Status: 00 Type: 19 Size: 0002 ClusterData: >0000<'
2023-10-16 23:54:58,080 INFO :b'Decode8102 - LQI: 45 Received Cluster:0500 Attribute: 0002 Value: 0000 from (5cda/01)'
2023-10-16 23:54:58,581 INFO :b'ZigateRead - MsgType: 8011, Data: 005cda, LQI: 45'
double click, button short id still 5cda:
2023-10-16 23:58:36,503 INFO :b'ZigateRead - MsgType: 8002, Data: 00010405000101025cda020000091300020000000000, LQI: 48'
2023-10-16 23:58:36,504 INFO :b'zcl_decoders sending a default response for command 00'
2023-10-16 23:58:36,506 INFO :b'zcl_decoders Zcl.ddr: 0 GlobalCommand: False Sqn: 13 ManufCode: None Command: 00 Data: 020000000000 Payload: 091300020000000000'
2023-10-16 23:58:36,509 INFO :b'buildframe_8401_cmd - 5cda 01 0500 Data: 020000000000'
2023-10-16 23:58:36,512 INFO :b'Decode8401 - Reception Zone status change notification: 13010500025cda000200000000'
2023-10-16 23:58:36,513 INFO :b'Decode8401 - MsgSQN: 13 MsgSrcAddr: 5cda MsgEp:01 MsgClusterId: 0500 MsgZoneStatus: 0002 MsgExtStatus: 00 MsgZoneID: 00 MsgDelay: 0000'
2023-10-16 23:58:36,514 INFO :b'IAS Zone for device:5cda - alarm1: 0, alarm2: 1, tamper: 0, battery: 0, Support Reporting: 0, restore Reporting: 0, trouble: 0, acmain: 0, test: 0, battdef: 0'
2023-10-16 23:58:36,515 INFO :b'Decode8401 MsgZoneStatus: 02 '
2023-10-16 23:58:36,516 INFO :b'get_device_config_param: 5cda Config: MotionViaIASAlarm1'
2023-10-16 23:58:36,516 INFO :b'MotionViaIASAlarm1 = None'
2023-10-16 23:58:36,518 INFO :b'button = 02'
2023-10-16 23:58:36,520 INFO :b'ZigateRead - MsgType: 8002, Data: 00010405000101025cda02000008140a0200190200, LQI: 45'
2023-10-16 23:58:36,521 INFO :b'zcl_decoders sending a default response for command 0a'
2023-10-16 23:58:36,523 INFO :b'zcl_decoders Zcl.ddr: 0 GlobalCommand: True Sqn: 14 ManufCode: None Command: 0a Data: 0200190200 Payload: 08140a0200190200'
2023-10-16 23:58:36,524 INFO :b'zcl_decoders Sqn: 20/14 ManufCode: None Command: 0a Data: 0200190200 '
2023-10-16 23:58:36,526 INFO :b'buildframe_report_attribute_response - 5cda 01 0500 Data: 0200190200'
2023-10-16 23:58:36,526 INFO :b'Decode8102 - Attribute Reports: [5cda:01] MsgSQN: 14 ClusterID: 0500 AttributeID: 0002 Status: 00 Type: 19 Size: 0002 ClusterData: >0002<'
2023-10-16 23:58:36,527 INFO :b'scan_attribute_reponse - Sqn: 14 i_sqn: 14 Nwkid: 5cda Ep: 01 Cluster: 0500 MsgData: 145cda0105000002001900020002 Type: 8102'
2023-10-16 23:58:36,529 INFO :b'scan_attribute_reponse - 8102 idx: 28 Read Attribute Response: [5cda:01] ClusterID: 0500 MsgSQN: 14, i_sqn: 14, AttributeID: 0002 Status: 00 Type: 19 Size: 0002 ClusterData: >0002<'
2023-10-16 23:58:36,537 INFO :b'Decode8102 - LQI: 45 Received Cluster:0500 Attribute: 0002 Value: 0002 from (5cda/01)'
2023-10-16 23:58:37,141 INFO :b'ZigateRead - MsgType: 8011, Data: 005cda, LQI: 45'
The "Received Cluster:0500 Attribute:...." message doesn't seem to always follow the single click, double click, long press value, sometimes there is "Value: 0000" even though this message follows "IAS Zone for device" message. Only reliable message seems to bee "IAS Zone" and alarm1 and alarm2 corresponding to button click.
2023-10-17 00:13:59,651 INFO :b'ZigateRead - MsgType: 8002, Data: 00010405000101025cda020000093600010000000000, LQI: 48'
2023-10-17 00:13:59,652 INFO :b'zcl_decoders sending a default response for command 00'
2023-10-17 00:13:59,653 INFO :b'zcl_decoders Zcl.ddr: 0 GlobalCommand: False Sqn: 36 ManufCode: None Command: 00 Data: 010000000000 Paylo
ad: 093600010000000000'
2023-10-17 00:13:59,655 INFO :b'buildframe_8401_cmd - 5cda 01 0500 Data: 010000000000'
2023-10-17 00:13:59,655 INFO :b'Decode8401 - Reception Zone status change notification: 36010500025cda000100000000'
2023-10-17 00:13:59,655 INFO :b'Decode8401 - MsgSQN: 36 MsgSrcAddr: 5cda MsgEp:01 MsgClusterId: 0500 MsgZoneStatus: 0001 MsgExtStatus: 00
MsgZoneID: 00 MsgDelay: 0000'
2023-10-17 00:13:59,656 INFO :b'IAS Zone for device:5cda - alarm1: 1, alarm2: 0, tamper: 0, battery: 0, Support Reporting: 0, restore Re
porting: 0, trouble: 0, acmain: 0, test: 0, battdef: 0'
2023-10-17 00:13:59,656 INFO :b'Decode8401 MsgZoneStatus: 01 '
2023-10-17 00:13:59,656 INFO :b'get_device_config_param: 5cda Config: MotionViaIASAlarm1'
2023-10-17 00:13:59,656 INFO :b'MotionViaIASAlarm1 = None'
2023-10-17 00:13:59,656 INFO :b'button = 01'
2023-10-17 00:14:00,165 INFO :b'ZigateRead - MsgType: 8011, Data: 005cda, LQI: 48'
2023-10-17 00:14:07,729 INFO :b'ZigateRead - MsgType: 8002, Data: 0001040402010102d58202000018f10a00002939f8, LQI: 48'
2023-10-17 00:14:07,730 INFO :b'zcl_decoders Zcl.ddr: 1 GlobalCommand: True Sqn: f1 ManufCode: None Command: 0a Data: 00002939f8 Payload:
18f10a00002939f8'
2023-10-17 00:14:07,731 INFO :b'zcl_decoders Sqn: 241/f1 ManufCode: None Command: 0a Data: 00002939f8 '
2023-10-17 00:14:07,731 INFO :b'buildframe_report_attribute_response - d582 01 0402 Data: 00002939f8'
2023-10-17 00:14:07,732 INFO :b'Decode8102 - Attribute Reports: [d582:01] MsgSQN: f1 ClusterID: 0402 AttributeID: 0000 Status: 00 Type: 2
9 Size: 0002 ClusterData: >f839<'
2023-10-17 00:14:07,733 INFO :b'scan_attribute_reponse - Sqn: f1 i_sqn: f1 Nwkid: d582 Ep: 01 Cluster: 0402 MsgData: f1d58201040200000029
0002f839 Type: 8102'
2023-10-17 00:14:07,733 INFO :b'scan_attribute_reponse - 8102 idx: 28 Read Attribute Response: [d582:01] ClusterID: 0402 MsgSQN: f1, i_sq
n: f1, AttributeID: 0000 Status: 00 Type: 29 Size: 0002 ClusterData: >f839<'
2023-10-1
Button device is "AstiaButton" in following export.
export.json
The text was updated successfully, but these errors were encountered: