search

Koenkk / zigbee2mqtt

Zigbee 🐝 to MQTT bridge 🌉, get rid of your proprietary Zigbee bridges 🔨
https://www.zigbee2mqtt.io
GNU General Public License v3.0
11.31k stars 1.62k forks source link

After OTA update Ikea E1524/E1810 can't be bound to group - how to downgrade? #7716

Closed andreypolyak closed 2 years ago

andreypolyak commented 3 years ago

What happened

  1. I upgraded Ikea E1524/E1810 remote to the latest version using Zigbee2mqtt — 2.3.075
  2. Deleted remote and readded it back (this was not related to OTA update so not sure how important is it to reproduce the issue)
  3. Tried to setup the binding between the remote and light group as I previously had. It doesn't work

I read about the same issue in ZHA related issue: https://github.com/home-assistant/core/issues/43969#issuecomment-854951280. So looks like the problem is reproducable.

What did you expect to happen

Is there any way to downgrade the firmware? I have bunch of E1524/E1810 remotes that are on 2.3.014 firmware and they are working great.

How to reproduce it (minimal and precise)

Debug info

Zigbee2MQTT version: 1.19.1 Adapter hardware: CC2652 Adapter firmware version:

MattWestb commented 2 years ago

Some new is that IKEA was taking the "bad firmware" from the test feed for some week ago so they is knowing its not working OK.

And they have certified the new version 2.3.079 of the 5 button remote, On/Off, Open/Close and the blinds. Its still not in the test feed but very likely is coming there in one week or 2.

Shortcut and Symphonosik was also getting "bad ones" but still no new OTA files have showing up in the feed or certificate documents.

Have little patios with testing them then they is showing up for not braking your devices and i is trying them out then i can getting the new OTA files for the remotes but i dont have any blinds but they was working OK after the last update for 2 month ago.

I keep posting the status of the new remotes OTA files here for user that have getting in trouble.

PS: to updating one certificated product is only 1500$ in fee to CSA plus the fee to the company that is doing the work / cert / product.

github-actions[bot] commented 2 years ago

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

MattWestb commented 2 years ago

All "bad" firmware have getting updates certified but they is not released in the test feed but is likely being made very soon. https://zigbeealliance.org/zigbee_products/?product_type=certified_product&se=ikea

github-actions[bot] commented 2 years ago

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

MattWestb commented 2 years ago

IKEA have not released the new firmware in the test feed (as of today 11:00 CET) but they have certified one new firmware for there GW for one week ago. Its normal they need doing some new settings of the controlling devices and therefor need updating the GW for doing that in the controllers and the controllers can then joining other devices like lights and blinds. Also they need doing very mush testing for not braking there GW system and also if you is pairing one controller direct with one light without the GW and the last is the "normal" working mode with coordinator that we are using also must working OK before they is relenting all the now controller firmware.

This is start being one long story but i hope in the end they hopefully is getting it right and its better to do it right then not doing it at all (as some other manufacture is doing: not fixing there buggy firmware).

andreypolyak commented 2 years ago

The new firmware is now available for IKEA E1524/E1810 as well as some other Ikea remotes. Did anyone test it?

MattWestb commented 2 years ago

with version 2.3.075 (old test feed that was deleted) is rolling back after restating. I have 2 that have rolling back and downloading new all the night so must moving them to my test system.

TRÅDFRI on/off switch (E1743) with version 2.2.010 is applying the the new OTA OK and is not looping the update. (I was only having one with "old production firmware").

MattWestb commented 2 years ago

One more tested:

Looks like the bad firmware have problem with the security setting and is not liking upgrading to new firmware.

I have not testing the group binding on the E1743 and E1744 then i trying saving some battery then i have 15 controller looping updating there firmware and have disabling OTA on my production system and only making test in one test system.

Ultraboss77 commented 2 years ago

Same here with 5.1-TRADFRI-remote-control, upgrade from 075 is looping... dam it !

LivArt01 commented 2 years ago

Hi, I have E1743 with fw 2.3.079. And it stopped working after update. How to make it work again?

//after numerous tries of pairing I can pair it with bulbs and see action in HA, but no battery.

havardthom commented 2 years ago

My E1524 IKEA trådfri remote stopped working a few days ago, it does not communicate with my light group anymore. I have a light group with 2 trådfri drivers (kitchen) bind with the IKEA trådfri remote. The firmware on my devices seem to be quite old: image As you can see I do not have the new firmware, but still the E1524 cannot communicate with the drivers (I can control the drivers directly/manually).

I've tried binding the E1524 remote both to the device group and directly to the two driver devices, nothing seem to work anymore.

I've tried to check the devices for newest firmware, so I can update and connect directly to devices as reported in this issue, but it does not find any update (my configuration has ikea_ota_use_test_url: true)

Info MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"No update available for 'Kjøkken Lyskontroll'","meta":{"device":"Kjøkken Lyskontroll","status":"not_available"},"type":"ota_update"}'
Info MQTT publish: topic 'zigbee2mqtt/bridge/response/device/ota_update/check', payload '{"data":{"id":"Kjøkken Lyskontroll","updateAvailable":false},"status":"ok","transaction":"ljx33-1"}'

Anyone have suggestions what I can do? Can I upgrade device firmware manually somehow?

MattWestb commented 2 years ago

I have not testing all new controllers but the E1743 (on/off) have loosing group binding (and likely all other new device firmware) and can only being bonded too one device, that is very bad the its not possible having more lights/derives that is working then the host system is down / remote.

Also user that have upgraded to the bad test firmware cant upgrading to the new version then its rolling the bad back on reboot and downgrading is blocked in the firmware.

I have flashing 5 E1743 with one old dumped firmware and and then its updating to the last production one OK (but still loosing the group binding) but shall being OK then new firmware is released.

I trying extracting the last good firmware and repacking it to S37 files so user can manual flashing there device with Simplicity commander with one SWD probe without braking them, but i need more testing for getting it working OK. I keep posting then i finding more interesting things.

cpuks commented 2 years ago

So if my E1743 are on .75 firmware which is considered bad - what can I do to upgrade those to .79 ? All I have in mind now is to try with IKEA gateway see if that helps...

muddy79 commented 2 years ago

Just for the record: I've updated some of my E1524 to "stable" 2.3.080 and I lost group binding capability. What a shame... It seems "test" feed still supplies 2.3.014. Is there any way to force downgrade to the older version via z2m? I've updated z2m configuration to use test feed for IKEA OTA but OTA is not possible due to the error message: firmware version is newer than OTA version.

havardthom commented 2 years ago

I am currently upgrading my E1524 remote to v2.3.080 through deconz, it's taking forever though, currently at 8% after 15 minutes. Hopefully I'll get it working again after the update. It seems that the ikea test feed (http://fw.test.ota.homesmart.ikea.net/feed/version_info.json) only had v2.3.014 which is probably why Zigbee2mqtt couldn't find the newest firmware. The stable feed (http://fw.ota.homesmart.ikea.net/feed/version_info.json) has v.2.3.080 though and luckily deconz had that version downloaded in it's /data/ota folder

havardthom commented 2 years ago

Just for the record: I've updated some of my E1524 to "stable" 2.3.080 and I lost group binding capability. What a shame... It seems "test" feed still supplies 2.3.014. Is there any way to force downgrade to the older version via z2m? I've updated z2m configuration to use test feed for IKEA OTA but OTA is not possible due to the error message: firmware version is newer than OTA version.

I had v2.3.014 on my E1524 and could not communicate with my light group anymore, so I don't think downgrading helps. It seems you can bind directly with the devices on the newest firmware though.

muddy79 commented 2 years ago

All remotes on v2.3.014 are able to be bound to the group. Yes, I'm able to bind to the single light, but it seems I can only bind to only one light at the same time, while most of my setup are multiple bulbs. Moreover, it seems arrows buttons (left/right) are no more recognized by z2m. Nothing in the debug log :(

asmigala commented 2 years ago

Just as an extra datapoint, I have two remotes with two different versions:

havardthom commented 2 years ago

All remotes on v2.3.014 are able to be bound to the group. Yes, I'm able to bind to the single light, but it seems I can only bind to only one light at the same time, while most of my setup are multiple bulbs. Moreover, it seems arrows buttons (left/right) are no more recognized by z2m. Nothing in the debug log :(

Been dealing with my remote on v2.3.014 all day, it stopped working earlier this week, doubt it is a coincidence. Binding to the group was successful, but nothing happened on button actions. Reconnected and rebinded the remote probably 3-4 times and nothing seemed to solve the problem. I'm taking my chances on the new firmware instead atleast.

muddy79 commented 2 years ago

I've tried to upgrade 4 remotes. 1 of them is reporting firmware v2.3.080, other 3 still report v2.3.014. All have the same issue: not able to control group. All others reporting v2.3.014 (but without upgrade attempt) still work properly. Strange, indeed.

havardthom commented 2 years ago

My E1524 remote is now updated to v2.3.080, can confirm that bind to a group does not work, but binding to my two devices (ICPSHC24-30EU-IL-1 Ikea drivers) directly works.

muddy79 commented 2 years ago

Tried again and it is possible to bind two devices, so it might be a workaround. What about arrow buttons (scene change)? It's not reported by z2m anymore... EDIT: it seems it is reported, unless the remote is bound to the device. After that, no MQTT messages are generated after clicking the button. So, arrow keys rely only on the ikea build-in scenes, which are available for some, but not all bulbs I have. Before, I was able to rely on group binding to perform basic operations like: on/off and brightness, but arrow keys (click, hold, release) was handled by HA to either control scenes or perform other actions (like: controlling brightness of additional ambient light). Now, it's not possible to mix it: either bind to the device and the remote actions are no more accessible in HA, or do not bind and handle everything from HA.

tubededentifrice commented 2 years ago

I've 6 remotes (E1810) and because I've an automation to update them whenever an update is available... they all stopped working after that upgrade (October 26-27). When force removed and re-paired, they seems to be interviewed fine, but they seem to bind to "default_bind_group" (cluster OnOff only though), but none of the button reports anything in Zigbee2MQTT (I assume because of the new behavior you're describing above).

However, I've been unable to unbind the remotes from that endpoint, no matter what button I press during the process to keep the remote alive. The 6 remotes are essentially bricked now 😭

How have you been able to unbind and received commands in Zigbee2MQTT? Thanks,

tubededentifrice commented 2 years ago

Examples of logs I'm getting on join ; I assume other people will be getting the same issues when they update...

info  2021-10-31 10:56:52: Device '0x84fd27fffe2476d6' joined
info  2021-10-31 10:56:52: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x84fd27fffe2476d6","ieee_address":"0x84fd27fffe2476d6"},"type":"device_joined"}'
info  2021-10-31 10:56:52: MQTT publish: topic 'homeassistant/sensor/0x84fd27fffe2476d6/battery/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state"},{"topic":"zigbee2mqtt/0x84fd27fffe2476d6/availability"}],"device":{"identifiers":["zigbee2mqtt_0x84fd27fffe2476d6"],"manufacturer":"IKEA","model":"TRADFRI remote control (E1524/E1810)","name":"0x84fd27fffe2476d6","sw_version":"Zigbee2MQTT 1.21.2"},"device_class":"battery","enabled_by_default":true,"json_attributes_topic":"zigbee2mqtt/0x84fd27fffe2476d6","name":"0x84fd27fffe2476d6 battery","state_class":"measurement","state_topic":"zigbee2mqtt/0x84fd27fffe2476d6","unique_id":"0x84fd27fffe2476d6_battery_zigbee2mqtt","unit_of_measurement":"%","value_template":"{{ value_json.battery }}"}'
info  2021-10-31 10:56:52: MQTT publish: topic 'homeassistant/sensor/0x84fd27fffe2476d6/action/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state"},{"topic":"zigbee2mqtt/0x84fd27fffe2476d6/availability"}],"device":{"identifiers":["zigbee2mqtt_0x84fd27fffe2476d6"],"manufacturer":"IKEA","model":"TRADFRI remote control (E1524/E1810)","name":"0x84fd27fffe2476d6","sw_version":"Zigbee2MQTT 1.21.2"},"enabled_by_default":true,"icon":"mdi:gesture-double-tap","json_attributes_topic":"zigbee2mqtt/0x84fd27fffe2476d6","name":"0x84fd27fffe2476d6 action","state_topic":"zigbee2mqtt/0x84fd27fffe2476d6","unique_id":"0x84fd27fffe2476d6_action_zigbee2mqtt","value_template":"{{ value_json.action }}"}'
info  2021-10-31 10:56:52: MQTT publish: topic 'homeassistant/sensor/0x84fd27fffe2476d6/linkquality/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state"},{"topic":"zigbee2mqtt/0x84fd27fffe2476d6/availability"}],"device":{"identifiers":["zigbee2mqtt_0x84fd27fffe2476d6"],"manufacturer":"IKEA","model":"TRADFRI remote control (E1524/E1810)","name":"0x84fd27fffe2476d6","sw_version":"Zigbee2MQTT 1.21.2"},"enabled_by_default":false,"icon":"mdi:signal","json_attributes_topic":"zigbee2mqtt/0x84fd27fffe2476d6","name":"0x84fd27fffe2476d6 linkquality","state_class":"measurement","state_topic":"zigbee2mqtt/0x84fd27fffe2476d6","unique_id":"0x84fd27fffe2476d6_linkquality_zigbee2mqtt","unit_of_measurement":"lqi","value_template":"{{ value_json.linkquality }}"}'
info  2021-10-31 10:56:52: MQTT publish: topic 'homeassistant/sensor/0x84fd27fffe2476d6/update_state/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state"},{"topic":"zigbee2mqtt/0x84fd27fffe2476d6/availability"}],"device":{"identifiers":["zigbee2mqtt_0x84fd27fffe2476d6"],"manufacturer":"IKEA","model":"TRADFRI remote control (E1524/E1810)","name":"0x84fd27fffe2476d6","sw_version":"Zigbee2MQTT 1.21.2"},"enabled_by_default":false,"icon":"mdi:update","json_attributes_topic":"zigbee2mqtt/0x84fd27fffe2476d6","name":"0x84fd27fffe2476d6 update state","state_topic":"zigbee2mqtt/0x84fd27fffe2476d6","unique_id":"0x84fd27fffe2476d6_update_state_zigbee2mqtt","value_template":"{{ value_json['update']['state'] }}"}'
info  2021-10-31 10:56:52: MQTT publish: topic 'homeassistant/binary_sensor/0x84fd27fffe2476d6/update_available/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state"},{"topic":"zigbee2mqtt/0x84fd27fffe2476d6/availability"}],"device":{"identifiers":["zigbee2mqtt_0x84fd27fffe2476d6"],"manufacturer":"IKEA","model":"TRADFRI remote control (E1524/E1810)","name":"0x84fd27fffe2476d6","sw_version":"Zigbee2MQTT 1.21.2"},"enabled_by_default":false,"json_attributes_topic":"zigbee2mqtt/0x84fd27fffe2476d6","name":"0x84fd27fffe2476d6 update available","payload_off":false,"payload_on":true,"state_topic":"zigbee2mqtt/0x84fd27fffe2476d6","unique_id":"0x84fd27fffe2476d6_update_available_zigbee2mqtt","value_template":"{{ value_json.update_available}}"}'
info  2021-10-31 10:56:52: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":{"friendly_name":"0x84fd27fffe2476d6"},"type":"device_connected"}'
info  2021-10-31 10:56:52: MQTT publish: topic 'zigbee2mqtt/0x84fd27fffe2476d6/availability', payload 'online'
error 2021-10-31 10:56:52: Failed to unbind cluster 'genOnOff' from '0x84fd27fffe2476d6' to 'default_bind_group' (Error: Unbind 0x84fd27fffe2476d6/1 genOnOff from '901' failed (waiting for response TIMEOUT))
info  2021-10-31 10:56:52: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":{"cluster":"genOnOff","from":"0x84fd27fffe2476d6","to":"default_bind_group"},"type":"device_unbind_failed"}'
error 2021-10-31 10:56:53: Failed to unbind cluster 'genLevelCtrl' from '0x84fd27fffe2476d6' to 'default_bind_group' (Error: Unbind 0x84fd27fffe2476d6/1 genLevelCtrl from '901' failed (Error: status: 136))
info  2021-10-31 10:56:53: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":{"cluster":"genLevelCtrl","from":"0x84fd27fffe2476d6","to":"default_bind_group"},"type":"device_unbind_failed"}'
info  2021-10-31 10:56:53: MQTT publish: topic 'zigbee2mqtt/bridge/response/device/unbind', payload '{"data":{"clusters":[],"failed":["genOnOff","genLevelCtrl"],"from":"0x84fd27fffe2476d6","to":"default_bind_group"},"error":"Failed to unbind","status":"error"}'
error 2021-10-31 10:56:53: Failed to unbind
tubededentifrice commented 2 years ago

So, here are the things I noted:

'901':
  friendly_name: default_bind_group
MattWestb commented 2 years ago

For users that have upgraded there controllers to the bad test firmware i have doing one set of firmware that can being flashed on the device but is need one J-Link or SWD probe and connecting it to the device PCB.

I have testing it on E1743, E1744 and E1812 but not on the 5 button remote then i cant open it without destroying it.

The firmware is the X-latest good production ones with working group binding and can being OTA upgraded to the latest with not working group binding and shall working with new OTS upgrades (if IKEA is doing it right).

Flashing working firmware on IKEA controller

Edit: I have open the 5 button remote without destroying it completely (the glue is not easy getting losing its grip) and using the battery connection and 2 DuPont cables for the SWD and have flashed it with the "old good" firmware and its now doing its update to new production version.

So in the end its looks its possible reflashing all bad controllers if having one SWD / J-Link probe and the "extracted" firmware form the old OTA files and getting then on production standard or leaving then with group binding working :-)))

groenmarsmannetje commented 2 years ago

I am able to bind the 5 button remote after update to multiple devices by long pressing the connect button near the light bulb that you want to bind. This seems to be a workaround. Probably the remote is creating it’s own group and adds the device to that group after binding.

After doing this I had to remove and add each light bulb again in their original groups. Now it is working again as it was, only lost the default scene selection with the left and right button.

frank-f commented 2 years ago

Does anyone have any insights or contacts at IKEA to find out why the behavior of all (?) remotes was changed so fundamentally?

sjorge commented 2 years ago

Does anyone have any insights or contacts at IKEA to find out why the behavior of all (?) remotes was changed so fundamentally?

The best one can do is probably reach out to u/TRADFRI on the tradfri subreddit, but IKEA has not been very communicative overall on there changes at all.

sjorge commented 2 years ago

@Koenkk can we maybe also pin this issues? As a few new ones seem to be opened everyday for this.

heisenberg2980 commented 2 years ago

Does anyone know how the firmware upgrade works in z2m (kind of a black box for me at the moment) and if downgrade to a previous version is somehow possible?

I guess there are two challenges here:

Ideally the downgrade process would have a "revert to previous version" option (I don´t have a clue of how that would work as it would need to store the previous version of the firmware somewhere, just thinking out loud here)

MattWestb commented 2 years ago

@Heisenberg2980

You can downgrading devices by flashing the with SWD probe as i have described in one link and also provided last good working version for doing it for all problem devices.

heisenberg2980 commented 2 years ago

@Koenkk it looks like this issue affects many (maybe even all) Ikea devices, could z2m block the firmware upgrade for Ikea devices showing some message like "Ikea latest firmware makes devices unusable in z2m so upgrade is blocked".

Unfortunately it is too late for anyone who has already upgraded the firmware (like me) but at least we can avoid more people having this issue.

havardthom commented 2 years ago

The latest firmware does not make E1524/E1810 unusable. You loose binding to group, but you gain binding to device. E.g. you can bind the E1524/E1810 directly to devices instead of binding to a group. For me the remote is working fine on the newest firmware. Some warning/docs could be justifiable though, since the new firmware introduces a breaking change.

heisenberg2980 commented 2 years ago

In that case we might be talking about two different issues, is E1524/E1810 sending commands to z2m after the firmware upgrade?

In my case the device (E1766) has stopped sending commands to z2m after the firmware upgrade, so it is totally unusable. I opened a different issue (#9439) but @sjorge mentioned it was a duplicate so I closed it, should I open it again to track the two different issues ("no binding to group" vs "no sending open/close commands").

frank-f commented 2 years ago

In that case we might be talking about two different issues, is E1524/E1810 sending commands to z2m after the firmware upgrade?

In my case the device (E1766) has stopped sending commands to z2m after the firmware upgrade, so it is totally unusable. I opened a different issue (#9439) but @sjorge mentioned it was a duplicate so I closed it, should I open it again to track the two different issues ("no binding to group" vs "no sending open/close commands").

The two things are kind of related. As soon as a remote is bound to a device, it stops sending button presses to the coordinator. The latter is what you're observing.

MattWestb commented 2 years ago

@havardthom The update is one large braking thing if you is using the controller as one light controller as is constructed to being in one Zigbee system then all with searing lights is done with groups.

If you like doing host automatons with click clicks its working but you have baying wrong controller then and shall going for HA remotes like Aqara and not ZLO controllers.

asmigala commented 2 years ago

The two things are kind of related. As soon as a remote is bound to a device, it stops sending button presses to the coordinator. The latter is what you're observing.

@frank-f that is not true. My 2.3.079 E1743 is bound to a single LED1732G11 (not through a group) and I still see mqtt messages when I press the buttons on it.

heisenberg2980 commented 2 years ago

In that case we might be talking about two different issues, is E1524/E1810 sending commands to z2m after the firmware upgrade? In my case the device (E1766) has stopped sending commands to z2m after the firmware upgrade, so it is totally unusable. I opened a different issue (#9439) but @sjorge mentioned it was a duplicate so I closed it, should I open it again to track the two different issues ("no binding to group" vs "no sending open/close commands").

The two things are kind of related. As soon as a remote is bound to a device, it stops sending button presses to the coordinator. The latter is what you're observing.

That is interesting, in that case if I pair my E1766 with z2m while my other Ikea device is disconnected from the network I should see the messages from E1766, right? I only have another Ikea device (roller blind - E1757) and I have tried removing its battery and then pairing the E1766 with no luck (I still can´t see any messages from E1766 in z2m after pairing)

frank-f commented 2 years ago

That is interesting, in that case if I pair my E1766 with z2m while my other Ikea device is disconnected from the network I should see the messages from E1766, right? I only have another Ikea device (roller blind - E1757) and I have tried removing its battery and then pairing the E1766 with no luck (I still can´t see any messages from E1766 in z2m after pairing)

At least for me it was not that complicated. I just had to unbind the remote from the device and the messages started appearing in my MQTT Client again. But looking at @asmigala s Post, that seems to not be the case for everybody. I had tried several things including completely resetting the remote, repairing it and after that I got the above behavior.

MattWestb commented 2 years ago

@asmigala How many devices can the E1743 being bounded to before its not adding more bindings ?

The E1766 i think can having more problems then IKEA have certified the signal repeater and blinds but have not releasing them (dont like having more problems then they have making) but i think and hope you can resetting the E1766 and letting it making its own network and then paring the signal repeater and then the blinds but then you is loosing Z2M connection but its working 24/7 but i think its better then have it not working at all .

frank-f commented 2 years ago

I have testing it on E1743, E1744 and E1812 but not on the 5 button remote then i cant open it without destroying it.

...

Edit: I have open the 5 button remote without destroying it completely (the glue is not easy getting losing its grip) and using the battery connection and 2 DuPont cables for the SWD and have flashed it with the "old good" firmware and its now doing its update to new production version.

I didn't try it myself yet, but I found a video on it and it looks rather simple to open up the 5-button remotes as well.

https://youtu.be/NMupi1FeAB8

Edit: Sorry, this video seems to be about an ancient version from years ago. I presume almost all models in the wild are the newer version with glued top. Those look much harder to open.

MattWestb commented 2 years ago

I have doing one 5 button yesterday its little trickery and getting little scratches but working without distorting it :-))

muddy79 commented 2 years ago

The two things are kind of related. As soon as a remote is bound to a device, it stops sending button presses to the coordinator. The latter is what you're observing.

@frank-f that is not true. My 2.3.079 E1743 is bound to a single LED1732G11 (not through a group) and I still see mqtt messages when I press the buttons on it. So that's not true for 2.3.079 and E1743, while it is true for 2.3.080 and E1524. More over, after the device joins network. z2m automatically binds it to default group #901, so the device is useless after joining, until it is manually unbound from this group. I agree that not binding to any group/device brings back the actions reporting via MQTT, so this is kind of a workaround, but direct binding is much more reliable. The original behavior (group binding + actions) was very powerful and handy: in case z2m/ha is not working, it's still possible to perform basic operations like on/off and brightness, while additional automation can be performed for arrow buttons (scene / color / temperature change is usually not working after binding), or triggering additional action after the button is pressed. It's all gone after the firmware upgrade.

asmigala commented 2 years ago

How many devices can the E1743 being bounded to before its not adding more bindings ?

@MattWestb I can try that later today, though I only have a total 5 devices + coordinator I can bind to.

By the way, looking at my shell history, it appears I unbound from the coordinator first, bound to the light (specifically the genOnOff and genLevelCtrl clusters), then rebound to the coordinator.

@muddy79 @frank-f can you try that as well?

No particular reason I did that, I'm new to z2m and was just migrating from the IKEA gate this weekend, ran into this issue and just tried various combinations until it worked.

frank-f commented 2 years ago

@asmigala How do you bind the remote to the controller? I've never done that before.. Oh and also, how do you bind just specific clusters? I have been wondering if that's possible, but didn't find anything about it.

asmigala commented 2 years ago

@frank-f 

{"from": "<device friendly name>", "to": "coordinator"}
muddy79 commented 2 years ago

By the way, looking at my shell history, it appears I unbound from the coordinator first, bound to the light (specifically the genOnOff and genLevelCtrl clusters), then rebound to the coordinator.

@muddy79 @frank-f can you try that as well?

No particular reason I did that, I'm new to z2m and was just migrating from the IKEA gate this weekend, ran into this issue and just tried various combinations until it worked.

Wow, that did the trick: after binding the remote to the coordinator on genOnOff and genLevelCtrl indeed the mqtt messages are sent via z2m!

So, this might be another workaround, solving the issue completely. The question is: from the zigbee network perspective: is it save to bind the remotes to the coordinator in that way?

heisenberg2980 commented 2 years ago

@frank-f

{"from": "<device friendly name>", "to": "coordinator"}

YESSSSSSSSS, you just saved my day!! After binding the device to the coordinator it is finally sending messages to z2m!!

MattWestb commented 2 years ago

Binding and reporting to coordinator is standard in Zigbee with exception lights is using groups for being redundant if the coordinator is going off line = OK