search

dresden-elektronik / deconz-rest-plugin

deCONZ REST-API plugin to control ZigBee devices
BSD 3-Clause "New" or "Revised" License
1.89k stars 498 forks source link

Can't connect to IKEA Shortcut button - No button handler for: TRADFRI SHORTCUT Button endpoint #4306

Closed brujoand closed 3 years ago

brujoand commented 3 years ago

Describe the bug

Trying to add the IKEA Shortcut button doesn't work, and the logs show

[INFO] - No button handler for: TRADFRI SHORTCUT Button endpoint: 0x01 cluster: 0x0003 command: 0x01 payload[0]: 000

Steps to reproduce the behavior

  1. Start the pairing process by either adding as IKEA Remote/Dimmer or Other
  2. Press the pair button 4 times in 5 seconds
  3. Wait
  4. Logs say there is no handler for the button endpoint

Expected behavior

The button should be paired as support was added in 2.9.0

Environment

deconz: 2.09.01 / 12/23/2020 fw; 26660700

deCONZ Logs

10:27:31:623 sync() in 24 ms
10:27:31:638 Current channel 15
10:27:31:642 CTRL got nwk update id 0
10:27:31:649 Device TTL 3475 s flags: 0x7
10:27:32:658 ZCL attribute report 0xBC33ACFFFE5F0088 for cluster: 0x0008, ep: 0x01, frame control: 0x08, mfcode: 0x0000
10:27:35:597 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
10:27:36:622 GW firmware version: 0x26660700
10:27:36:623 GW firmware version is up to date: 0x26660700
10:27:40:598 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
10:27:45:598 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
10:27:46:616 send permit join, duration: 59
10:27:46:617 send GP proxy commissioning mode
10:27:50:598 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
10:27:54:697 ZCL attribute report 0xBC33ACFFFE9B33D9 for cluster: 0x0300, ep: 0x01, frame control: 0x08, mfcode: 0x0000
10:27:54:702 ZCL attribute report 0xBC33ACFFFE9B33D9 for cluster: 0x0300, ep: 0x01, frame control: 0x08, mfcode: 0x0000
10:27:55:598 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
10:28:00:362 0xEA33 nwk changed to 0x5B00
10:28:00:363 DeviceAnnce of SensorNode: 0x680AE2FFFE25E078 [1]
10:28:00:364    nwk address changed 0xEA33 -> 0x5B00 [2]
10:28:00:365 device announce 0x680AE2FFFE25E078 (0x5B00) mac capabilities 0x80
10:28:00:365 set fast probe address to 0x680AE2FFFE25E078 (0x5B00)
10:28:00:366 FP indication 0x0000 / 0x0013 (0x680AE2FFFE25E078 / 0x5B00)
10:28:00:366                       ...     (0x680AE2FFFE25E078 / 0x5B00)
10:28:00:367 device announce 0x680AE2FFFE25E078 (0x5B00) mac capabilities 0x80
10:28:00:376 discard double entry in binding queue (size: 2) for for 0x680AE2FFFE25E078, cluster 0x0006
10:28:01:297 [1] get node descriptor for 0x680ae2fffe25e078
10:28:01:492 Bind response success for 0x680ae2fffe25e078 ep: 0x01 cluster: 0x0006
10:28:01:520 FP indication 0x0000 / 0x8002 (0x680AE2FFFE25E078 / 0x5B00)
10:28:01:521                       ...     (0x680AE2FFFE25E078 / 0x5B00)
10:28:01:521 ZDP indication search sensors 0x680AE2FFFE25E078 (0x5B00) cluster 0x8002
10:28:01:522 ZDP indication search sensors 0x680AE2FFFE25E078 (0x5B00) clear timeout on cluster 0x8002
10:28:01:529 [2] get active endpoints for 0x680ae2fffe25e078
10:28:02:590 Bind response success for 0x680ae2fffe25e078 ep: 0x01 cluster: 0x0001
10:28:02:608 FP indication 0x0000 / 0x8005 (0x680AE2FFFE25E078 / 0x5B00)
10:28:02:609                       ...     (0x680AE2FFFE25E078 / 0x5B00)
10:28:02:609 ZDP indication search sensors 0x680AE2FFFE25E078 (0x5B00) cluster 0x8005
10:28:02:610 ZDP indication search sensors 0x680AE2FFFE25E078 (0x5B00) clear timeout on cluster 0x8005
10:28:02:697 FP indication 0x0000 / 0x8005 (0x680AE2FFFE25E078 / 0x5B00)
10:28:02:698                       ...     (0x680AE2FFFE25E078 / 0x5B00)
10:28:02:699 ZDP indication search sensors 0x680AE2FFFE25E078 (0x5B00) cluster 0x8005
10:28:02:703 Bind response success for 0x680ae2fffe25e078 ep: 0x01 cluster: 0x0001
10:28:03:690 FP indication 0x0000 / 0x8005 (0x680AE2FFFE25E078 / 0x5B00)
10:28:03:691                       ...     (0x680AE2FFFE25E078 / 0x5B00)
10:28:03:691 ZDP indication search sensors 0x680AE2FFFE25E078 (0x5B00) cluster 0x8005
10:28:03:696 FP indication 0x0104 / 0x0001 (0x680AE2FFFE25E078 / 0x5B00)
10:28:03:697                       ...     (0x680AE2FFFE25E078 / 0x5B00)
10:28:03:698 ZCL configure reporting rsp seq: 46 0x680AE2FFFE25E078 for ep: 0x01 cluster: 0x0001 attr: 0x0021 status: 0x00
10:28:03:702 FP indication 0x0104 / 0x0001 (0x680AE2FFFE25E078 / 0x5B00)
10:28:03:702                       ...     (0x680AE2FFFE25E078 / 0x5B00)
10:28:04:630 Bind response success for 0x680ae2fffe25e078 ep: 0x01 cluster: 0x0006
10:28:07:238 FP indication 0x0104 / 0x0003 (0x680AE2FFFE25E078 / 0x5B00)
10:28:07:239                       ...     (0x680AE2FFFE25E078 / 0x5B00)
10:28:07:240 [INFO] - No button handler for: TRADFRI SHORTCUT Button endpoint: 0x01 cluster: 0x0003 command: 0x01 payload[0]: 000
10:28:21:398 ZCL attribute report 0xBC33ACFFFE9B33D9 for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000
10:28:26:594 ZCL attribute report 0xBC33ACFFFE9B33D9 for cluster: 0x0008, ep: 0x01, frame control: 0x08, mfcode: 0x0000
10:28:31:611 Current channel 15
10:28:31:615 CTRL got nwk update id 0
10:28:31:619 Device TTL 3415 s flags: 0x7
10:28:39:714 ZCL attribute report 0xBC33ACFFFE9B33D9 for cluster: 0x0300, ep: 0x01, frame control: 0x08, mfcode: 0x0000
10:28:42:687 ZCL attribute report 0xBC33ACFFFEA516BD for cluster: 0x0008, ep: 0x01, frame control: 0x08, mfcode: 0x0000
10:28:45:597 send permit join, duration: 59
10:28:45:598 send GP proxy commissioning mode
10:28:45:802 FP indication 0x0104 / 0x0019 (0x680AE2FFFE25E078 / 0x5B00)
10:28:45:802                       ...     (0x680AE2FFFE25E078 / 0x5B00)
close-issue-app[bot] commented 3 years ago

Hi there.

Thank you for filing this issue. Unfortunately, we cannot help you, as you haven't sticked to the provided template and/or have not provided all information requested. Consequently, this issue has been closed.
We're more than happy to help out where we can once you raise a new issue containing all requested information in the requested format.

In this regard, please take note that:
- read the template thoroughly
- all given header lines (starting with ###) must not be deleted
- everything enclosed by <!-- --> is intended to give you guidance and should be replaced by your input specific to the issue
- Listings regarding your environment must be filled out completely where applicable (bug reports and user questions).
- Not following the template or providing insufficient information can still implicate manual closure.

So please, first help us a bit to help you!