No zha_event for KE TRADFRI open/close remote part 2

thd6n75 commented 4 years ago

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)

I don't see any events when listening for zha_event and pushing buttons.

I've tried removing the device and re-pairing while forcing the E1766 to stay awake by pressing buttons (see logs bellow)

Environment

Linear HUSBZB-1 controller

Home Assistant Core release with the issue: homeassistant/home-assistant:0.114.4 docker image
Last working Home Assistant Core release (if known): unknown
Operating environment (OS/Container/Supervised/Core): Ubuntu 20.04, Docker 19.03.8
Integration causing this issue: zha
Link to integration documentation on our website: https://www.home-assistant.io/integrations/zha

Problem-relevant `configuration.yaml`

zha:
  database_path: /config/zigbee.db

Traceback/Error logs

Pairing the device: https://pastebin.com/rrQbR4Ju

Additional information

This issue is exactly the same as https://github.com/home-assistant/core/issues/36484

It was allegedly fixed in https://github.com/home-assistant/core/pull/36489 but I still don't see any zha_events.

zha-binds

This is what I get when joining the device. I end up with a battery sensor (sensor.xxx) and a binary_sensor. But pushing the buttons doesn't generate any event when listening for zha_event and the binary_sensor never changes state.

probot-home-assistant[bot] commented 4 years ago

Hey there @dmulcahey, @adminiuga, mind taking a look at this issue as its been labeled with an integration (zha) you are listed as a codeowner for? Thanks! _{^{(message by CodeOwnersMention)}}

Adminiuga commented 4 years ago

Log looks good. on_off,level and window covering cluster were bound. I wonder if it sends updates on light link group? And 2nd question: is this a genuine Ikea sensor? Why the manufacturer is juste "KE"

thd6n75 commented 4 years ago

Thanks for your time.

I've been using ZHA for a couple years and never had to do anything with bindings or groups, so forgive me, what would you like for me to do re: light link group?

Here are my options

Clusters menu: ha-clusters

Device binding menu: ha-device-binding

It is a genuine Ikea remote. It came with my Fyrtur zigbee blinds (which are paired directly with HA). The rear of the remote states that it's a E1766. The guy in https://github.com/home-assistant/core/issues/36484 named his issue "KE TRADFRI" too - maybe they all show up like that - I don't know.

thd6n75 commented 4 years ago

Is there anything I can do to provide more info?

AlexMarent commented 4 years ago

I have exactly the same problem! Do you need any information?

Adminiuga commented 4 years ago

What radio? Is coordinator member of the group 0? Did you bind remote to any other group?

AlexMarent commented 4 years ago

I'm using the Conbee II. I didn't changed anything after binding.

Adminiuga commented 4 years ago

Well, ConBee would receive traffic for any group and if you are not getting anything in the logs when pressing buttons, that makes me believe the remote isn't sending anything.

I have a similar remote, but it returns correct manufacturer and works as expected on husbzb and ConBee radios.

I don't know if there's just a bad batch of these remotes in the wild. Do they work as expected when bound directly to the blinds?

thd6n75 commented 4 years ago

Mine worked with the Fyrtur blinds that they came with.

I have 3 of these, I can try them all. I will report back if any of them behave any differently than I originally reported

Adminiuga commented 4 years ago

Add debug logging for the zhaquirks component as well, and remove device before re-pairng, so it would do device discovery again.

Another thing you could try, is binding the remote to an existing group and check if it can control that group

AlexMarent commented 4 years ago

If I press a button I get the following lines:

[0x00f7: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=1>
[0x00f7:1:0x0102] ZCL request 0x0001: []
[0x00f7:1:0x0102] No handler for cluster command 1

And with the other button:

[0x00f7: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=18 command_id=0>
[0x00f7:1:0x0102] ZCL request 0x0000: []
[0x00f7:1:0x0102] No handler for cluster command 0

I tried 5 buttons , every button has exactly the same behaviour. What I also recognized, is that the buttons which did not come with the blinds works fine.

Adminiuga commented 4 years ago

Can you post device signature? Just to confirm it has the quirk applied? I see it sending command on cluster 102, it should be possible to create a zha event for it

Adminiuga commented 3 years ago

enable homeassistant.core: debug logging or listen to zha_event in devloper -> Events. I'm getting

2020-10-21 21:29:55 DEBUG (MainThread) [zigpy.zcl] [0x56d3: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=12 command_id=1>
2020-10-21 21:29:55 DEBUG (MainThread) [zigpy.zcl] [0x56d3:1:0x0102] ZCL request 0x0001: []
2020-10-21 21:29:55 DEBUG (MainThread) [zigpy.zcl] [0x56d3:1:0x0102] No handler for cluster command 1
2020-10-21 21:29:55 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event zha_event[L]: device_ieee=ec:1b:bd:ff:fe:bb:49:f4, unique_id=ec:1b:bd:ff:fe:bb:49:f4:1:0x0102, endpoint_id=1, cluster_id=258, command=down_close, args=[]>
...
2020-10-21 21:30:24 DEBUG (MainThread) [zigpy.zcl] [0x56d3: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=14 command_id=0>
2020-10-21 21:30:24 DEBUG (MainThread) [zigpy.zcl] [0x56d3:1:0x0102] ZCL request 0x0000: []
2020-10-21 21:30:24 DEBUG (MainThread) [zigpy.zcl] [0x56d3:1:0x0102] No handler for cluster command 0
2020-10-21 21:30:24 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event zha_event[L]: device_ieee=ec:1b:bd:ff:fe:bb:49:f4, unique_id=ec:1b:bd:ff:fe:bb:49:f4:1:0x0102, endpoint_id=1, cluster_id=258, command=up_open, args=[]>

Adminiuga commented 3 years ago

0x0102 cluster is already in HA, so if you are getting

[0x00f7: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=18 command_id=0>
[0x00f7:1:0x0102] ZCL request 0x0000: []
[0x00f7:1:0x0102] No handler for cluster command 0

then you also should get the zha events

AlexMarent commented 3 years ago

Sorry for the late response. The ZHA event does not look bad. But I'm only able to trigger automations on the state (open or close - which never will change) but not onto "up pressed" or "down pressed".


{
    "event_type": "zha_event",
    "data": {
        "device_ieee": "00:0d:6f:ff:fe:be:46:29",
        "unique_id": "00:0d:6f:ff:fe:be:46:29:1:0x0102",
        "endpoint_id": 1,
        "cluster_id": 258,
        "command": "down_close",
        "args": []
    },
    "origin": "LOCAL",
    "time_fired": "2020-10-25T10:10:03.969665+00:00",
    "context": {
        "id": "400bc95916aa11eb8c98498f7ac4e672",
        "parent_id": null,
        "user_id": null
    }
}

Adminiuga commented 3 years ago

But there's no state? What do you mean?

Adminiuga commented 3 years ago

Down pressed is you event for down_close command.

AlexMarent commented 3 years ago

I'm not able to select a trigger like "down_close" in an automation, I'm only able to select "opened" or "closed", which is a state but not an event.

thd6n75 commented 3 years ago

I can't speak of HA automations because I don't use them, but I think you can use ZHA events in appdaemon pretty easily (look at https://appdaemon.readthedocs.io/en/latest/AD_API_REFERENCE.html#appdaemon.adapi.ADAPI.listen_event ). You can also use https://github.com/xaviml/controllerx which is an appdaemon app that's already tailored to use these Ikea remotes.

What version of HA are you using, Alex? I still don't see zha_events when I listen for them in the HA UI.

thd6n75 commented 3 years ago

Ha! I tried a different E1766 and it works. Adminiuga, sorry for wasting your time.

{
    "event_type": "zha_event",
    "data": {
        "device_ieee": "68:0a:e2:ff:fe:f7:4c:be",
        "unique_id": "68:0a:e2:ff:fe:f7:4c:be:1:0x0102",
        "endpoint_id": 1,
        "cluster_id": 258,
        "command": "up_open",
        "args": []
    },
    "origin": "LOCAL",
    "time_fired": "2020-10-26T23:36:04.032050+00:00",
    "context": {
        "id": "034d705e17e411eb9bbc71521e79a785",
        "parent_id": null,
        "user_id": null
    }
}

{
    "event_type": "zha_event",
    "data": {
        "device_ieee": "68:0a:e2:ff:fe:f7:4c:be",
        "unique_id": "68:0a:e2:ff:fe:f7:4c:be:1:0x0102",
        "endpoint_id": 1,
        "cluster_id": 258,
        "command": "down_close",
        "args": []
    },
    "origin": "LOCAL",
    "time_fired": "2020-10-26T23:36:03.247757+00:00",
    "context": {
        "id": "02d5c44717e411eba89bbdd0fef8092b",
        "parent_id": null,
        "user_id": null
    }
}

This issue can be resolved.

thd6n75 commented 3 years ago

BTW, I'll mention that the remote that doesn't work was one that came with Fyrtur blinds purchased maybe in early 2019. The one that works was purchased with blinds in Oct 2020.

MattWestb commented 3 years ago

I think the "KE TRADFRI" problems is coming form from one bad data setting in the factory that is manufacturing the devices for IKEA. And the large problems with the latest OTA files can being that IKEA is trying patching the "user data" in the flash with new data for correcting the bad data settings (possible with GBL OTA files but not with the old format EBL). Wold being interesting downgrading one of those devices and letting the IKEA GW updating it and see if the data setting is corrected with dumping the internal flash userdata memory.

yfaber commented 3 years ago

Ha! I tried a different E1766 and it works. Adminiuga, sorry for wasting your time.

{
    "event_type": "zha_event",
    "data": {
        "device_ieee": "68:0a:e2:ff:fe:f7:4c:be",
        "unique_id": "68:0a:e2:ff:fe:f7:4c:be:1:0x0102",
        "endpoint_id": 1,
        "cluster_id": 258,
        "command": "up_open",
        "args": []
    },
    "origin": "LOCAL",
    "time_fired": "2020-10-26T23:36:04.032050+00:00",
    "context": {
        "id": "034d705e17e411eb9bbc71521e79a785",
        "parent_id": null,
        "user_id": null
    }
}

{
    "event_type": "zha_event",
    "data": {
        "device_ieee": "68:0a:e2:ff:fe:f7:4c:be",
        "unique_id": "68:0a:e2:ff:fe:f7:4c:be:1:0x0102",
        "endpoint_id": 1,
        "cluster_id": 258,
        "command": "down_close",
        "args": []
    },
    "origin": "LOCAL",
    "time_fired": "2020-10-26T23:36:03.247757+00:00",
    "context": {
        "id": "02d5c44717e411eba89bbdd0fef8092b",
        "parent_id": null,
        "user_id": null
    }
}

This issue can be resolved.

I have the same problem as you, tried pairing and using 4 different remotes and none seem to work... what else did you do?

thd6n75 commented 3 years ago

I didn't do anything. One of my E1766 worked without issue, and one didn't. I haven't tested one other that I have.

The only (unsubstantiated) idea I have about the cause is related to date of manufacture, see my comment: https://github.com/home-assistant/core/issues/40036#issuecomment-718261562

I'm not sure what can be done for the scenario where the remote doesn't produce zha_event. One of my remotes is effectively useless, as far as I know.

yfaber commented 3 years ago

I updated all 4 remotes and none of them are working, any ideas guys?

sebbe1985 commented 3 years ago

I believe I'm having similar issues. I can't see any zha_events in the log, I have tried with the only 2 TRÅDFRI remotes that I have (E1810).

fudunco commented 3 years ago

I have the same issue, no ZHA_event for my IKEA remote (E1810), I've tried with z2m and that didn't work neither.

MattWestb commented 3 years ago

Please post the information from "Zigbee device signature" from the device card.

sebbe1985 commented 3 years ago

I have the same issue, no ZHA_event for my IKEA remote (E1810), I've tried with z2m and that didn't work neither.

I got it working by updating the firmware of my Conbee-stick :)

fudunco commented 3 years ago

I have the same issue, no ZHA_event for my IKEA remote (E1810), I've tried with z2m and that didn't work neither.

I got it working by updating the firmware of my Conbee-stick :)

Thanks for the solution I've tried to flash my cc2531 dongle with the last firmware and that works better

thd6n75 commented 3 years ago

I've migrated from zha to zigbee2mqtt and the E1766 that wouldn't produce zha_events paired without issue.

home-assistant / core