Ikea Shortcut Button (E1812) Stops Working After Pairing

[idofr]

What happened

I've got two Ikea Shortcut Buttons and a Hue Dimmer Switch, all brand new. All three devices were easily added to Zigbee2MQTT without any problems. The pairing was quick and they're all recognised as the devices they really are, link quality and battery status is also showing. Yet, I can't seem to get any response from the Ikea buttons after pairing. Using Mqtt Explorer and a very simple NodeRed scheme to show all communications in the network, I only see events coming from the Hue Switch, both Ikea Buttons don't seem to be generating any sort of messages. Sometimes, when I restart Zigbee2MQTT (used as the HomeAssistant plugin), it then show the last message in the queue, but that's it, it doesn't show anything afterwards. As I said, the Hue Switch works perfectly fine and I see all messages it's generating.

Would very much appreciate some assistance here.

Cheers

What did you expect to happen

I'd expect to see the messages from both Ikea buttons just the way I see the messages from the Hue switch, i.e. both in MQTT Explorer and in NodeRed.

How to reproduce it (minimal and precise)

I did nothing really but pairing all three devices. No other devices are connected/paired.

Debug info

Zigbee2MQTT version: 1.18.1-1 Adapter hardware: CC2531 Adapter firmware version: now sure where to find this info.

[FlatulentCow]

Having exactly the same issue. I have two brand new E1812 buttons (delivered yesterday) that were working without issue then I saw there was an update in the OTA section. I updated them both to 2.3.080 and now I cannot get any actions to register. Battery is being reported but even with fresh batteries they still show low power. I've tried all the workarounds suggested that I can find and nothing so far has worked.

I should probably add that I'm using a CC2652R (zzh!) with the latest firmware and HA/Z2M are all the latest versions as I've only just rebuilt it all.

[jonas740]

I don't really know if I have succeeded in fixing this issue, don't want to celebrate just yet.

But what I have done so far.

Took my CC2652RB apart and inspected it with microscope and found a solder point to look a bit odd, so I resoldered that one. (can't really say if it was a problem but it just did not look "neat")

Reflashed it with latest firmware.

I bought a new USB 2.0 extension cable(Amazon Basic 3 meter) and I placed my CC2652RB as far away from any electronics I could.

After this it has magically worked.

I had a USB 2.0 extension cable prior to buying a new one but I wanted to take every step I could to make sure that I have removed all the variables that might cause the issue.

Regarding battery status for each device, I believe that to be very inaccurate and not to be trusted.

[MattWestb]

Sounds great Jonas !!

Sleeping end device is using max 1/10 of the chip max power and most of the time they is using less then 1/100 of the chop max power so if its noisy around they is getting problem sending commands and getting replay back then its parent can here them.

One good thing its having routers around the sleeping end device so they is not needing using "high power" and still can communicating OK.

IKEA implementation of battery status is . . . Its reporting OK but always the same until you is using one button then its updating the is sending the "new" battery status and is reporting it until . . . And its very "jumpy" !!!

[unsounddabbit]

I just bought 6 of these guys and upgraded the firmware to all of them. All worked before the FW update. Is there a way to roll back firmware?

[MattWestb]

I have unpacking the last good working firmware for all updated controller that have loosing group binding or is locked in bad firmware. You need one SWD probe for flashing. https://github.com/zigpy/zigpy/discussions/660#discussioncomment-1565541 And for the E1812 you can do it without distorting the device https://github.com/zigpy/zigpy/discussions/660#discussioncomment-1563280.

If you like keep it on the last good or updating it later if its coming on good working version.

[FlatulentCow]

Group bindings is indeed what caused my issues. They were binding to a default group 901 (after the OTA update to 2.3.080) which didn't actually exist. I struggled for 3 days trying to bind them to the coordinator. Must have deleted them and re-added them 30 times. With a combination of clicking the button when binding whilst simultaneously kicking off an OTA check and pushing the bind to coordinator command, I finally got them bound to the coordinator. They work now but in hindsight I would return them, get replacements and prevent the auto OTA updates.

[unsounddabbit]

Matt, Thanks for that, but I'm not skilled enough to pull off your fix. I tried to work with the bindings and nothing worked. I'm going to return them. it's such a shame. I see this thread was created in April. I'm guessing there won't be a firmware update that fixes this any time soon.

[MattWestb]

IKEA was having one test feed for firmware (they have closing it and using one that we dont knowing now) and it was some bad beta firmware there that is not possible updating or roiling back therefor i was making the flashing as one last resort for user with real broken not upgrading devices.

If enough users is returning then is IKEA getting one large red light in there system and perhaps somthing is happening but all controllers is very tricky for them redoing then its making all magic in there system.

And in the pipe is blinds and signal repeater and the old CWS 1.0 was certified yesterday (the last ZLL that is getting Zigbee 3) and i think they is rolling update on all lights for fixing some stack bugs but its only speculations from my side.

I think update fixing group binding i think is possible but it was taking very long time for this release after the bad one so i thing its not weeks but mounts before it can being released if they is doing it.

[unsounddabbit]

Matt,

That's what I was thinking. They will need to fix this and me doing their job won't make that happen. I've heard that IKEA firmware can be hit or miss and I've been slow to use their stuff. Phillips is expensive, but it works. I'm going to order more IKEA switches and wait for the firmware fixes.

[eljanoc]

Same problem with the E1812. Binding is OK, but configuring does not work. After a lot of tries, I succeeded once in configuring the module, but I did not know exactly how ... So, it answered correctly with short and long click response ! I then deleted the item, to see, and start the association again ..., never managed to correctly configure the module.

I work with a conbee2 Version Zigbee2MQTT 1.22.0 commit: a51626e3 E1812 version is 20190715 2.3.015 Unable to OTA : "Failed to check if update available for 'Bouton1' (Device didn't respond to OTA request)"

[chasebolt]

I updated from 2.3.015 to 2.3.080 and the button has stopped responding when pressed. zigbee2mqtt sees it come online when i pull the battery and reinsert it.

[Lars383]

@chasebolt Same problem here. Alle buttons worked fine till the update. Tried different setup, HA instead of OH and a different coordinator. The 2.3.080 firmware just doesn´t seem to work correctly with z2m. Pairing was smooth like allways. The shortcut button exposes the battery lvl and the link quality just fine. Only the actions aren´t recognized by z2m.

[eloo]

@chasebolt @Lars383

the problem has already a workaround which is already mentioned in this issue some comments above.. https://github.com/Koenkk/zigbee2mqtt/issues/9439#issuecomment-956456214

you should try to bind the device during the interview to the coordinator at least this is working for all of my 4 E1812

Hope that helps

[Lars383]

@eloo Thanks a lot eloo, you saved my day :-) Danke Joseph :-)

[GrumpyMeow]

I regret i updated the firrmware of one my E1524/E1810 remotes to v2.3.080. This as i'm now unable to bind this remote to a group of lights. In contrary to others in this thread, everything else seems to be working alright with the remote. I do see actions being triggered. The reason i want this remote to be bound to a group, is because i want two remotes to control the lights. 1.22.0, zStack3x0, 20210120, 0.6.30, SonfOff Zigbee Dongle Plus

[reneklootwijk]

I regret i updated the firrmware of one my E1524/E1810 remotes to v2.3.080. This as i'm now unable to bind this remote to a group of lights. In contrary to others in this thread, everything else seems to be working alright with the remote. I do see actions being triggered. The reason i want this remote to be bound to a group, is because i want two remotes to control the lights. 1.22.0, zStack3x0, 20210120, 0.6.30, SonfOff Zigbee Dongle Plus

I think firmware 2.3.080 does not support binding to a group anymore, you have to bind to the individual devices. At least this worked for my E1524 after upgrading.

[chasebolt]

the steps outlined above aren't straight forward and not a great user experience. it will be nice when someone sorts out how to make this "just work" for users.

On Sun, Dec 5, 2021 at 04:08 Rene Klootwijk @.***> wrote:

I regret i updated the firrmware of one my E1524/E1810 remotes to v2.3.080. This as i'm now unable to bind this remote to a group of lights. In contrary to others in this thread, everything else seems to be working alright with the remote. I do see actions being triggered. The reason i want this remote to be bound to a group, is because i want two remotes to control the lights. 1.22.0, zStack3x0, 20210120, 0.6.30, SonfOff Zigbee Dongle Plus

I think firmware 2.3.080 does support binding to a group anymore, you have to bind to the individual devices. At least this worked for my E1524 after upgrading.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Koenkk/zigbee2mqtt/issues/7150#issuecomment-986201312, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJKSSGVUBOEHNNCXDO4BU3UPM23TANCNFSM43I4POGA .

[reneklootwijk]

Group bindings is indeed what caused my issues. They were binding to a default group 901 (after the OTA update to 2.3.080) which didn't actually exist. I struggled for 3 days trying to bind them to the coordinator. Must have deleted them and re-added them 30 times. With a combination of clicking the button when binding whilst simultaneously kicking off an OTA check and pushing the bind to coordinator command, I finally got them bound to the coordinator. They work now but in hindsight I would return them, get replacements and prevent the auto OTA updates.

For me this also worked, I removed the device, rejoined and during the interview process send the mqtt message to bind to the coordinator. I also updated the zigbee-herdsman-converters version to support the off command by double clicking the switch.

[Koenkk]

Pushed a fix to correctly configure these remotes after the latest OTA update.

Changes will be available in the dev branch in a few hours from now. (https://www.zigbee2mqtt.io/advanced/more/switch-to-dev-branch.html)

[lbt]

I had these problems with a Raspbee (deconz) under zigbee2mqtt I switched to the dev branch (HEAD is 42569d6c39295b6bcbde788a2db94e0262b434e8) and still don't get events from the E1812

[McMornan]

The fix will not affect devices which already have the non functional firmware, only ones which are upgraded by zigbee2mqtt with the lates dev branch. You need to manually bind the button to the coordinator after successful pairing. It works. I paired two shortcut buttons just yesterday and they work as intended (only send an "on" message though, which is enough to toggle)

example command on linux command line: mosquitto_pub -h 192.168.2.5 -p 1883 -t zigbee2mqtt/bridge/request/device/bind -m '{"from":"IKEAButton5","to":"coordinator"}'

[lbt]

I'm afraid I'm having problems with this:

Here you see the mqtt traffic including my initial request. I tried "coordinator" with lowercase as you said but noted it was in uppercase in the UI so I tried that too.

zigbee2mqtt/bridge/request/device/bind = b'{"from":"PushButton","to":"Coordinator"}'        2 {'dup': 0, 'retain': 0}
zigbee2mqtt/bridge/logging = b'{"level":"error","message":"Failed to bind cluster \'genLevelCtrl\' from \'PushButton\' to \'Coordinator\' (Error: Bind 0x0c4314fffe4c09fe/1 genLevelCtrl from \'0x00212effff022d34/1\' failed (waiting for response TIMEOUT))"}'        0 {'dup': 0, 'retain': 0}
zigbee2mqtt/bridge/logging = b'{"level":"info","message":"MQTT publish: topic \'zigbee2mqtt/bridge/log\', payload \'{\\"message\\":{\\"cluster\\":\\"genLevelCtrl\\",\\"from\\":\\"PushButton\\",\\"to\\":\\"Coordinator\\"},\\"type\\":\\"device_bind_failed\\"}\'"}'        0 {'dup': 0, 'retain': 0}
zigbee2mqtt/bridge/log = b'{"message":{"cluster":"genLevelCtrl","from":"PushButton","to":"Coordinator"},"type":"device_bind_failed"}'        0 {'dup': 0, 'retain': 0}

The UI already shows a binding:

(I think I set the onOff)

Clearly the timeout suggests the lack of an RF connection so I tried clicking the button before doing this to get it awake but that didn't help.

I then force removed the device (remove failed) via the UI and reset the button and it re-paired. Here are the logs

Dec 20 21:25:52 plum npm[26755]: Zigbee2MQTT:info  2021-12-20 21:25:52: Device '0x0c4314fffe4c09fe' joined
Dec 20 21:25:52 plum npm[26755]: Zigbee2MQTT:info  2021-12-20 21:25:52: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x0c4314fffe4c09fe","ieee_address":"0x0c4314fffe4c09fe"},"type":"device_joined"}'
Dec 20 21:25:52 plum npm[26755]: Zigbee2MQTT:info  2021-12-20 21:25:52: Configuring '0x0c4314fffe4c09fe'
Dec 20 21:25:52 plum npm[26755]: Zigbee2MQTT:info  2021-12-20 21:25:52: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":{"friendly_name":"0x0c4314fffe4c09fe"},"type":"device_connected"}'
Dec 20 21:25:52 plum npm[26755]: Zigbee2MQTT:info  2021-12-20 21:25:52: Starting interview of '0x0c4314fffe4c09fe'
Dec 20 21:25:52 plum npm[26755]: Zigbee2MQTT:info  2021-12-20 21:25:52: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x0c4314fffe4c09fe","ieee_address":"0x0c4314fffe4c09fe","status":"started"},"type":"device_interview"}'
Dec 20 21:25:52 plum npm[26755]: Zigbee2MQTT:info  2021-12-20 21:25:52: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"interview_started","meta":{"friendly_name":"0x0c4314fffe4c09fe"},"type":"pairing"}'
Dec 20 21:25:53 plum npm[26755]: Zigbee2MQTT:info  2021-12-20 21:25:53: Successfully interviewed '0x0c4314fffe4c09fe', device has successfully been paired
Dec 20 21:25:53 plum npm[26755]: Zigbee2MQTT:info  2021-12-20 21:25:53: Device '0x0c4314fffe4c09fe' is supported, identified as: IKEA TRADFRI shortcut button (E1812)
Dec 20 21:25:53 plum npm[26755]: Zigbee2MQTT:info  2021-12-20 21:25:53: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"definition":{"description":"TRADFRI shortcut button","exposes":[{"access":1,"description":"Remaining battery in %","name":"battery","property":"battery","type":"numeric","unit":"%","value_max":100,"value_min":0},{"access":1,"description":"Triggered action (e.g. a button click)","name":"action","property":"action","type":"enum","values":["on","off","brightness_move_up","brightness_stop"]},{"access":1,"description":"Link quality (signal strength)","name":"linkquality","property":"linkquality","type":"numeric","unit":"lqi","value_max":255,"value_min":0}],"model":"E1812","options":[{"description":"Simulate a brightness value. If this device provides a brightness_move_up or brightness_move_down action it is possible to specify the update interval and delta.","features":[{"access":2,"description":"Delta per interval, 20 by default","name":"delta","property":"delta","type":"numeric","value_min":0},{"access":2,"description":"Interval duration","name":"interval","property":"interval","type":"numeric","unit":"ms","value_min":0}],"name":"simulated_brightness","property":"simulated_brightness","type":"composite"}],"supports_ota":true,"vendor":"IKEA"},"friendly_name":"0x0c4314fffe4c09fe","ieee_address":"0x0c4314fffe4c09fe","status":"successful","supported":true},"type":"device_interview"}'
Dec 20 21:25:53 plum npm[26755]: Zigbee2MQTT:info  2021-12-20 21:25:53: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"interview_successful","meta":{"description":"TRADFRI shortcut button","friendly_name":"0x0c4314fffe4c09fe","model":"E1812","supported":true,"vendor":"IKEA"},"type":"pairing"}'
Dec 20 21:26:15 plum npm[26755]: Zigbee2MQTT:info  2021-12-20 21:26:15: MQTT publish: topic 'zigbee2mqtt/0x0c4314fffe4c09fe', payload ''
Dec 20 21:26:15 plum npm[26755]: Zigbee2MQTT:info  2021-12-20 21:26:15: MQTT publish: topic 'zigbee2mqtt/PushButton/availability', payload 'online'
Dec 20 21:26:15 plum npm[26755]: Zigbee2MQTT:info  2021-12-20 21:26:15: MQTT publish: topic 'zigbee2mqtt/PushButton', payload '{"linkquality":255}'
Dec 20 21:26:15 plum npm[26755]: Zigbee2MQTT:info  2021-12-20 21:26:15: MQTT publish: topic 'zigbee2mqtt/bridge/response/device/rename', payload '{"data":{"from":"0x0c4314fffe4c09fe","homeassistant_rename":false,"to":"PushButton"},"status":"ok","transaction":"00bj4-9"}'
Dec 20 21:26:53 plum npm[26755]: Zigbee2MQTT:error 2021-12-20 21:26:53: Failed to configure 'PushButton', attempt 1 (Error: Bind 0x0c4314fffe4c09fe/1 genOnOff from '901' failed (waiting for response TIMEOUT)
Dec 20 21:27:46 plum npm[26755]: Zigbee2MQTT:error 2021-12-20 21:27:46: Failed to bind cluster 'genOnOff' from 'PushButton' to 'Coordinator' (Error: Bind 0x0c4314fffe4c09fe/1 genOnOff from '0x00212effff022d34/1' failed (waiting for response TIMEOUT))
Dec 20 21:27:46 plum npm[26755]: Zigbee2MQTT:info  2021-12-20 21:27:46: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":{"cluster":"genOnOff","from":"PushButton","to":"Coordinator"},"type":"device_bind_failed"}'
Dec 20 21:28:47 plum npm[26755]: Zigbee2MQTT:error 2021-12-20 21:28:47: Failed to bind cluster 'genLevelCtrl' from 'PushButton' to 'Coordinator' (Error: Bind 0x0c4314fffe4c09fe/1 genLevelCtrl from '0x00212effff022d34/1' failed (waiting for response TIMEOUT))
Dec 20 21:28:47 plum npm[26755]: Zigbee2MQTT:info  2021-12-20 21:28:47: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":{"cluster":"genLevelCtrl","from":"PushButton","to":"Coordinator"},"type":"device_bind_failed"}'
Dec 20 21:29:09 plum npm[26755]: Zigbee2MQTT:info  2021-12-20 21:29:09: Configuring 'PushButton'
Dec 20 21:29:11 plum npm[26755]: Zigbee2MQTT:info  2021-12-20 21:29:11: Successfully bound cluster 'closuresWindowCovering' from 'PushButton' to 'Coordinator'
Dec 20 21:29:11 plum npm[26755]: Zigbee2MQTT:info  2021-12-20 21:29:11: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":{"cluster":"closuresWindowCovering","from":"PushButton","to":"Coordinator"},"type":"device_bind"}'
Dec 20 21:29:11 plum npm[26755]: Zigbee2MQTT:info  2021-12-20 21:29:11: MQTT publish: topic 'zigbee2mqtt/bridge/response/device/bind', payload '{"data":{"clusters":["closuresWindowCovering"],"failed":["genOnOff","genLevelCtrl"],"from":"PushButton","to":"coordinator"},"status":"ok"}'
Dec 20 21:29:24 plum npm[26755]: Zigbee2MQTT:info  2021-12-20 21:29:24: MQTT publish: topic 'zigbee2mqtt/PushButton', payload '{"battery":60,"linkquality":255}'
Dec 20 21:29:24 plum npm[26755]: Zigbee2MQTT:info  2021-12-20 21:29:24: Successfully configured 'PushButton'

Then I issued your mqtt bind again:

$ python mqtt_publish.py zigbee2mqtt/bridge/request/device/bind '{"from":"PushButton","to":"coordinator"}'

and saw

zigbee2mqtt/bridge/request/device/bind = b'{"from":"PushButton","to":"coordinator"}'        2 {'dup': 0, 'retain': 0}
zigbee2mqtt/bridge/logging = b'{"level":"info","message":"Successfully bound cluster \'genOnOff\' from \'PushButton\' to \'Coordinator\'"}'        0 {'dup': 0, 'retain': 0}
zigbee2mqtt/bridge/logging = b'{"level":"info","message":"MQTT publish: topic \'zigbee2mqtt/bridge/log\', payload \'{\\"message\\":{\\"cluster\\":\\"genOnOff\\",\\"from\\":\\"PushButton\\",\\"to\\":\\"Coordinator\\"},\\"type\\":\\"device_bind\\"}\'"}'        0 {'dup': 0, 'retain': 0}
zigbee2mqtt/bridge/log = b'{"message":{"cluster":"genOnOff","from":"PushButton","to":"Coordinator"},"type":"device_bind"}'        0 {'dup': 0, 'retain': 0}
zigbee2mqtt/bridge/logging = b'{"level":"info","message":"Successfully bound cluster \'genLevelCtrl\' from \'PushButton\' to \'Coordinator\'"}'        0 {'dup': 0, 'retain': 0}
zigbee2mqtt/bridge/logging = b'{"level":"info","message":"MQTT publish: topic \'zigbee2mqtt/bridge/log\', payload \'{\\"message\\":{\\"cluster\\":\\"genLevelCtrl\\",\\"from\\":\\"PushButton\\",\\"to\\":\\"Coordinator\\"},\\"type\\":\\"device_bind\\"}\'"}'        0 {'dup': 0, 'retain': 0}
zigbee2mqtt/bridge/log = b'{"message":{"cluster":"genLevelCtrl","from":"PushButton","to":"Coordinator"},"type":"device_bind"}'        0 {'dup': 0, 'retain': 0}
zigbee2mqtt/bridge/logging = b'{"level":"info","message":"Successfully bound cluster \'closuresWindowCovering\' from \'PushButton\' to \'Coordinator\'"}'        0 {'dup': 0, 'retain': 0}
zigbee2mqtt/bridge/logging = b'{"level":"info","message":"MQTT publish: topic \'zigbee2mqtt/bridge/log\', payload \'{\\"message\\":{\\"cluster\\":\\"closuresWindowCovering\\",\\"from\\":\\"PushButton\\",\\"to\\":\\"Coordinator\\"},\\"type\\":\\"device_bind\\"}\'"}'        0 {'dup': 0, 'retain': 0}
zigbee2mqtt/bridge/log = b'{"message":{"cluster":"closuresWindowCovering","from":"PushButton","to":"Coordinator"},"type":"device_bind"}'        0 {'dup': 0, 'retain': 0}

Which resulted in this:

But I still get no events

Let me know if there are any other tests/debug settings etc that I could do

[github-actions[bot]]

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

[lbt]

I returned to try and debug this and it's now working for me. I upgraded HEAD to 1a0a9a6e

Pushes on the button get:

info MQTT publish: topic 'zigbee2mqtt/PushButton', payload '{"action":"on","battery":16,"linkquality":255,"update":{"state":"idle"},"update_available":false}'

Holding gets:

info MQTT publish: topic 'zigbee2mqtt/PushButton', payload '{"action":"on","battery":16,"linkquality":255,"update":{"state":"idle"},"update_available":false}'
info MQTT publish: topic 'zigbee2mqtt/PushButton', payload '{"action":"brightness_move_up","action_rate":83,"battery":16,"linkquality":255,"update":{"state":"idle"},"update_available":false}'
info MQTT publish: topic 'zigbee2mqtt/PushButton', payload '{"action":"brightness_move_up","action_rate":83,"battery":16,"linkquality":255,"update":{"state":"idle"},"update_available":false}'
info MQTT publish: topic 'zigbee2mqtt/PushButton', payload '{"action":"brightness_move_up","action_rate":83,"battery":16,"linkquality":255,"update":{"state":"idle"},"update_available":false}'
info MQTT publish: topic 'zigbee2mqtt/PushButton', payload '{"action":"brightness_move_up","action_rate":83,"battery":16,"linkquality":255,"update":{"state":"idle"},"update_available":false}'
info MQTT publish: topic 'zigbee2mqtt/PushButton', payload '{"action":"brightness_stop","battery":16,"linkquality":255,"update":{"state":"idle"},"update_available":false}'
info MQTT publish: topic 'zigbee2mqtt/PushButton', payload '{"action":"brightness_stop","battery":16,"linkquality":255,"update":{"state":"idle"},"update_available":false}'
info MQTT publish: topic 'zigbee2mqtt/PushButton', payload '{"action":"on","battery":16,"linkquality":255,"update":{"state":"idle"},"update_available":false}'
info

The Rotary produces

info MQTT publish: topic 'zigbee2mqtt/Rotary', payload '{"action":"play_pause","battery":60,"brightness":97,"linkquality":255,"rate":195,"update":{"state":"available"},"update_available":true}'

info MQTT publish: topic 'zigbee2mqtt/Rotary', payload '{"action":"rotate_left","battery":60,"brightness":1,"linkquality":239,"rate":195,"update":{"state":"available"},"update_available":true}'
info MQTT publish: topic 'zigbee2mqtt/Rotary', payload '{"action":"rotate_left","battery":60,"brightness":1,"linkquality":239,"rate":195,"update":{"state":"available"},"update_available":true}'
info MQTT publish: topic 'zigbee2mqtt/Rotary', payload '{"action":"rotate_stop","battery":60,"brightness":1,"linkquality":239,"rate":195,"update":{"state":"available"},"update_available":true}'

info MQTT publish: topic 'zigbee2mqtt/Rotary', payload '{"action":"rotate_right","battery":60,"brightness":1,"linkquality":199,"rate":195,"update":{"state":"available"},"update_available":true}'
info MQTT publish: topic 'zigbee2mqtt/Rotary', payload '{"action":"rotate_right","battery":60,"brightness":21,"linkquality":199,"rate":195,"update":{"state":"available"},"update_available":true}'
info MQTT publish: topic 'zigbee2mqtt/Rotary', payload '{"action":"rotate_stop","battery":60,"brightness":1,"linkquality":239,"rate":195,"update":{"state":"available"},"update_available":true}'

[CWempe]

@idofr

It would be very useful for other users if you would add a link to the workaround (https://github.com/Koenkk/zigbee2mqtt/issues/9439#issuecomment-956456214) to the initial post.

I read all of this long issue just to see there is an easy workaround available. 😄