-
-
Notifications
You must be signed in to change notification settings - Fork 33.8k
No zha_event for KE TRADFRI open/close remote #36484
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
Comments
zha documentation |
Hey there @dmulcahey, @Adminiuga, mind taking a look at this issue as its been labeled with a integration ( |
Nah, just need to add |
nah, not that. Need to take a look at the sources. HA is getting commands from the remote,
The default ZHA Event channel should have handled that. |
There is nothing from core getting logged: 2020-06-05 17:00:01 DEBUG (bellows.thread_0) [bellows.uart] Data frame: b'6697b1ed562e14b05895b529ab55929a35e3de231231648aedc6a1297e'
2020-06-05 17:00:01 DEBUG (bellows.thread_0) [bellows.uart] Sending: b'87009f7e'
2020-06-05 17:00:01 DEBUG (MainThread) [bellows.ezsp] Application frame 69 (incomingMessageHandler) received: b'020401020101ff0c010000d3a9adf988ffff03011000'
2020-06-05 17:00:01 DEBUG (MainThread) [bellows.zigbee.application] Received incomingMessageHandler frame with [<EmberIncomingMessageType.INCOMING_MULTICAST: 2>, <EmberApsFrame profileId=260 clusterId=258 sourceEndpoint=1 destinationEndpoint=255 options=268 groupId=0 sequence=211>, 169, -83, 0x88f9, 255, 255, b'\x01\x10\x00']
2020-06-05 17:00:01 DEBUG (MainThread) [zigpy.zcl] [0x88f9:1:0x0102] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=CLUSTER_COMMAND manufacturer_specific=False is_reply=False disable_default_response=False> manufacturer=None tsn=16 command_id=0>
2020-06-05 17:00:01 DEBUG (MainThread) [zigpy.zcl] [0x88f9:1:0x0102] ZCL request 0x0000: []
2020-06-05 17:00:01 DEBUG (MainThread) [zigpy.zcl] [0x88f9:1:0x0102] No handler for cluster command 0 For my other 5btn IKEA remote I see "Bus:Handling" tho. 2020-06-05 17:00:42 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event zha_event[L]: device_ieee=00:0b:57:ff:fe:14:41:46, unique_id=00:0b:57:ff:fe:14:41:46:1:0x0006, endpoint_id=1, cluster_id=6, command=toggle, args=[]> |
wanna give #36489 a try? |
Awesome @Adminiuga, works like a charm! {
"event_type": "zha_event",
"data": {
"device_ieee": "ec:1b:bd:ff:fe:e8:86:f9",
103CE
"unique_id": "ec:1b:bd:ff:fe:e8:86:f9:1:0x0102",
"endpoint_id": 1,
"cluster_id": 258,
"command": "up_open",
"args": []
},
"origin": "LOCAL",
"time_fired": "2020-06-05T19:36:45.425826+00:00",
"context": {
"id": "1f68ae87b1054639bf53d098aab14a37",
"parent_id": null,
"user_id": null
}
} |
excellent. Once it gets merged into rc branch (hopefuly 0.111.0b2), don't forget to remove the |
@Adminiuga was this ever merged? I'm using the |
Hm, ok. Am I supposed to see anything in WindowCovering binding? This is what I get when joining the device. I end up with a battery sensor (
|
it didn't finish the configuration
if it failed to configure this cluster, means it probably failed to configure other clusters as well. Remove the device, w B589 ait 45s. Try-rejoining and keep device awake during the process by pressing the buttons. |
Thanks for the response. I tried to do that, and I got the same result: my device shows up with 2 entities, and I don't see any events when listening for Log: https://pastebin.com/rrQbR4Ju I think the log is long because I kept pushing each button every few seconds to keep it awake |
Please open a new issue. This issue has been resolved. |
The problem
Remote doesn't send any events even after re-pair, reset re-add. This is the remote https://zigbee.blakadder.com/Ikea_E1766.html (not confirmed there to work with zha)
Other type of remote works (https://zigbee.blakadder.com/Ikea_E1810.html)
Environment
Docker
Home Assistant 0.111.0b0 using Silicon Labs EZSP
Problem-relevant
configuration.yaml
Traceback/Error logs
Event button press #1 and #2:
Additional information
Seems similar to this issue #31734
The text was updated successfully, but these errors were encountered: