Ikea Shortcut Button (E1812) Stops Working After Pairing #7150
Comments
|
For me exactly the same problem, with
Zigbee2MQTT version: 1.18.2 Log at joining (with error): |
|
In this thread @ebaauw said on 22.12.2020: "It's one of those devices that goes to sleep pretty quickly after pairing, and won't wake up, unless you created a binding within that time." This might be what we're seeing here.... Not sure how to continue from here though, or even validate that that's indeed the matter |
|
@idofr Did you also noticed this error in the log, when adding the device? Zigbee2MQTT:error 2021-04-25 21:59:28: Failed to configure '0x588e81fffe2b8222', attempt 1 (Error: Bind 0x588e81fffe2b8222/1 genPowerCfg from '901' failed (AREQ - ZDO - bindRsp after 10000ms) |
|
Pairing looks fine: Problem is - this is the last communication from/to the device I get. It doesn't respond and doesn't send anything regardless of what I try. |
|
Have same issue here. Running latest version of zigbee2mqtt + zzh! stick 20210120 firmware zStack3x0. Pairing seems to be successful, no errors. Buttons are working fine, sending mqtt output in debug log is visible, integration with Node-Red or HA works fine. And next day none of them works. It is paired, visible in devices list but action (toggle or up/down) does not make any action, nothing in debug log. I have E1524/E1810 remote and E1812 button, new batteries. Very strange behaviour. |
|
Hello I paired two E1810 recently. Both of then are seen as unsupported. The first one that I paired was recognized as E1810 after 2-3 days. For the second one I am still waiting. My conf: Antoine |
|
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 |
|
Solved by switching to https://slae.sh/projects/cc2652/ |
|
I'm having this same problem with:
Just bought the 2 Ikea devices to play around with. They paired fine, didn't notice any issues pairing. Looks like zigbee2mqtt is seeing battery levels from the devices. But I'm seeing zero activity in MQTT when using the buttons. |
|
I have the same situation with Ikea Shortcut Button E1812. This device worked perfectly but after OTA update and restart zigbee2mqtt device don't publish his state/battery/link on button press. |
|
@wiuwiu You have using IKEA test feed for OTA and the latest controller firmware is very "test" its not zigbee citified and have problems. Its not possible doing firmware downgrading then its blocked in IKEA controllers firmware so its only waiting until IKEA is relenting one working firmware in the production feed. |
|
Same problem here |
|
I don't have that problem, but I have obviously an older firmware version and the OTA check fails which is weird - but the button works: Button E1812 Zigbee2MQTT Version Coordinator
OTA Check Result Maybe this helps for a cross-check. |
Weird, my second button with the same firmware version just was logged as no update available: And that's with version 2.3.0.15 and you have 2.3.075 so there should be an update available. |
|
One of the issues with this button is that it does not switch it's parent once paired (just like the Xiaomi devices). At least that is my feeling. So you should not move the button to a new location after pairing (do that before pairing). |
|
Hello, I have same issue. I am able to pair the E1812 shortcut button but I see only action N/A and no messages in log when I am pushing the button (also nothing happens in Home Assistant). Button E1812 zigbee2mqtt_version I have Rapsberry PI with Sonoff CC2351. |
I'm amending my prior comment to let you know I got the SYMFONISK dial button working fine. But the Tradfri E1812 is still useless to me. I've tried re-interviewing it close to a zigbee smart plug closest to where the button is intended to be used, but I can't get it to re-interview, or if it does, it still doesn't seem to cause any events to fire when pressed. |
|
I just upgraded my ConBee II firmware to Link Quality Indicator and Battery are sampled just once during setup as far as I can tell. |
Thanks for info. You have right. I have another Ikea button which I don't upgraded with Ikea test firmware and it works perfect. |
|
The IKEA test feed is for the moment the same as the production then they have taking the "bad updates" away but its new in the pipe for blinds, signal repeater, 5 button remote, on/off and open/close buttons. Shortcut and SYMFONISK have not showing up on Zigbee certificate site but very likely is coming 2 and both need one refresh then they is spamming the network as also Styrbar is doing. |
|
I now have the weird problem that the button seems to drop out of the network (though I cannot find any error message about that in the log) and then rejoins: The symptom is that the button does not work until after has joined again. |
|
I'm having a similar issue. After the button failed to send messages, I upgraded zigbee2mqtt, force removed it (regular remove was unresponsive) and paired it again successfully. I also had to manually reconfigure since the first configuration failed. Now it is paired, but all it does is regularly announce itself. No Zigbee messages whatsoever when the button is actually pressed. |
|
Hi, I had the same issues with my ikea dimmer switches and buttons. Also using z2m 1.21.1 and cc2652rb. For me persistence was the key to success. I paired every button several Times (4x click to reset). Before it finally worked I also removed the buttons once. Also continously clicking on the button (not the reset switch) seems to have helped. (to prevent it falling asleep) After a few tries I could see the action messages coming in. Final configuration failed however and I paired again, clicking and clicking.... After 10-15 tries it finally worked. But I admit that pita process is not as it should be 😁 |
|
Having this issue with a Symfonisk, although I see the following How can I help debug this? |
|
I've got this issue on E1812 - firmware 2.3.075 and CC2652 - pairing is not a problem but then I cannot get anything out of this shortcut. Is it a matter of waiting for new firmware? |
I had the same experience as @McMornan described. I bought four E1812 (fw 2.3.015) Shortcut buttons and two E1744 (fw 2.1.024) Sympfonisk dimmers. Initially I tried pairing them with a CC2531 coordinator. 1-2 paired right away but after that didn't got much success. I then swapped the coordinator to a CC2652R (zzh!) I had already purchased in anticipation of potential issues and upgraded Z2M. This didn't seem to help. I got the devices paired several times but within hours each stopped working. I tried pairing them both to a Trådfree extender/router and to "any device". After persistently trying to pair them several times during 2-3 days, suddenly I got all but one Shortcut button paired and they've now worked reliably for 3-4 days in a row, even two which I moved to another room. I remember pairing them multiple times to a BlitzWolf BW-SHP13 socket at that time. Another noteworthy thing was that 4 of the 6 devices reported 30-70% battery state right out the package and I had to replace them. The actual voltages of the replaced IKEA branded batteries were between 2.5-3.05V. I'm currently running Zigbee2MQTT v1.21.1 with zStack3x0 rev. 20210708. |
|
@MaciejR89 After doing this it wreaks havoc for me (I have a toggle action onClick) as it fires three times now: |
|
I guess I will throw that thing in the bin and stick a wonderful Aqara button on the wall. Luckily I still have one unused left. |
|
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. |
|
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. |
|
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 . . . |
|
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? |
|
I have unpacking the last good working firmware for all updated controller that have loosing group binding or is locked in bad firmware. If you like keep it on the last good or updating it later if its coming on good working version. |
|
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. |
|
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. |
|
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. |
|
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. |
|
Same problem with the E1812. Binding is OK, but configuring does not work. I work with a conbee2 |
|
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. |
|
@chasebolt |
|
the problem has already a workaround which is already mentioned in this issue some comments above.. you should try to bind the device during the interview to the coordinator Hope that helps |
|
@eloo Thanks a lot eloo, you saved my day :-) |
|
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. |
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. |
|
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
<#7150 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJKSSGVUBOEHNNCXDO4BU3UPM23TANCNFSM43I4POGA>
.
|
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. |
|
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) |
|
I had these problems with a Raspbee (deconz) under zigbee2mqtt |
|
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: |
|
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. 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 Then I issued your mqtt bind again: and saw 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 |
|
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 |
|
I returned to try and debug this and it's now working for me. I upgraded HEAD to 1a0a9a6 Pushes on the button get: Holding gets: The Rotary produces |
|
It would be very useful for other users if you would add a link to the workaround (#9439 (comment)) to the initial post. I read all of this long issue just to see there is an easy workaround available. 😄 |
and others
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.
The text was updated successfully, but these errors were encountered: