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.54k stars 1.63k forks source link

Ikea Shortcut Button (E1812) Stops Working After Pairing #7150

Closed idofr closed 2 years ago

idofr commented 3 years ago

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.

mpmario commented 3 years ago

For me exactly the same problem, with

Zigbee2MQTT version: 1.18.2 Adapter hardware: CC2652RB Adapter firmware version: revision: 20210120

Log at joining (with error): https://pastebin.com/XFuJ166G

idofr commented 3 years ago

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

mpmario commented 3 years ago

@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) at Timeout._onTimeout (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/dist/utils/waitress.js:67:35) at listOnTimeout (internal/timers.js:554:17) at processTimers (internal/timers.js:497:7))

idofr commented 3 years ago

Pairing looks fine: What you see here is removing the device, enabling pairing mode, resetting the button and paiting again

Warning Device '0x588e81fffe2b4513' left the network
Info MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"ieee_address":"0x588e81fffe2b4513"},"type":"device_leave"}'
Info MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"left_network","meta":{"friendly_name":"0x588e81fffe2b4513"},"type":"device_removed"}'
Info Device '0x588e81fffe2b4513' joined
Info MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x588e81fffe2b4513","ieee_address":"0x588e81fffe2b4513"},"type":"device_joined"}'
Info Starting interview of '0x588e81fffe2b4513'
Info MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x588e81fffe2b4513","ieee_address":"0x588e81fffe2b4513","status":"started"},"type":"device_interview"}'
Info MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":{"friendly_name":"0x588e81fffe2b4513"},"type":"device_connected"}'
Info MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"interview_started","meta":{"friendly_name":"0x588e81fffe2b4513"},"type":"pairing"}'
Info MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x588e81fffe2b4513","ieee_address":"0x588e81fffe2b4513"},"type":"device_announce"}'
Info MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"announce","meta":{"friendly_name":"0x588e81fffe2b4513"},"type":"device_announced"}'
Info Successfully interviewed '0x588e81fffe2b4513', device has successfully been paired
Info Device '0x588e81fffe2b4513' is supported, identified as: IKEA TRADFRI shortcut button (E1812)
Info 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","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","supports_ota":true,"vendor":"IKEA"},"friendly_name":"0x588e81fffe2b4513","ieee_address":"0x588e81fffe2b4513","status":"successful","supported":true},"type":"device_interview"}'
Info MQTT publish: topic 'homeassistant/sensor/0x588e81fffe2b4513/battery/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state"}],"device":{"identifiers":["zigbee2mqtt_0x588e81fffe2b4513"],"manufacturer":"IKEA","model":"TRADFRI shortcut button (E1812)","name":"0x588e81fffe2b4513","sw_version":"Zigbee2MQTT 1.18.1"},"device_class":"battery","json_attributes_topic":"zigbee2mqtt/0x588e81fffe2b4513","name":"0x588e81fffe2b4513 battery","state_topic":"zigbee2mqtt/0x588e81fffe2b4513","unique_id":"0x588e81fffe2b4513_battery_zigbee2mqtt","unit_of_measurement":"%","value_template":"{{ value_json.battery }}"}'
Info MQTT publish: topic 'homeassistant/sensor/0x588e81fffe2b4513/action/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state"}],"device":{"identifiers":["zigbee2mqtt_0x588e81fffe2b4513"],"manufacturer":"IKEA","model":"TRADFRI shortcut button (E1812)","name":"0x588e81fffe2b4513","sw_version":"Zigbee2MQTT 1.18.1"},"icon":"mdi:gesture-double-tap","json_attributes_topic":"zigbee2mqtt/0x588e81fffe2b4513","name":"0x588e81fffe2b4513 action","state_topic":"zigbee2mqtt/0x588e81fffe2b4513","unique_id":"0x588e81fffe2b4513_action_zigbee2mqtt","value_template":"{{ value_json.action }}"}'
Info MQTT publish: topic 'homeassistant/sensor/0x588e81fffe2b4513/linkquality/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state"}],"device":{"identifiers":["zigbee2mqtt_0x588e81fffe2b4513"],"manufacturer":"IKEA","model":"TRADFRI shortcut button (E1812)","name":"0x588e81fffe2b4513","sw_version":"Zigbee2MQTT 1.18.1"},"icon":"mdi:signal","json_attributes_topic":"zigbee2mqtt/0x588e81fffe2b4513","name":"0x588e81fffe2b4513 linkquality","state_topic":"zigbee2mqtt/0x588e81fffe2b4513","unique_id":"0x588e81fffe2b4513_linkquality_zigbee2mqtt","unit_of_measurement":"lqi","value_template":"{{ value_json.linkquality }}"}'
Info MQTT publish: topic 'homeassistant/sensor/0x588e81fffe2b4513/update_state/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state"}],"device":{"identifiers":["zigbee2mqtt_0x588e81fffe2b4513"],"manufacturer":"IKEA","model":"TRADFRI shortcut button (E1812)","name":"0x588e81fffe2b4513","sw_version":"Zigbee2MQTT 1.18.1"},"icon":"mdi:update","json_attributes_topic":"zigbee2mqtt/0x588e81fffe2b4513","name":"0x588e81fffe2b4513 update state","state_topic":"zigbee2mqtt/0x588e81fffe2b4513","unique_id":"0x588e81fffe2b4513_update_state_zigbee2mqtt","value_template":"{{ value_json['update']['state'] }}"}'
Info MQTT publish: topic 'homeassistant/binary_sensor/0x588e81fffe2b4513/update_available/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state"}],"device":{"identifiers":["zigbee2mqtt_0x588e81fffe2b4513"],"manufacturer":"IKEA","model":"TRADFRI shortcut button (E1812)","name":"0x588e81fffe2b4513","sw_version":"Zigbee2MQTT 1.18.1"},"json_attributes_topic":"zigbee2mqtt/0x588e81fffe2b4513","name":"0x588e81fffe2b4513 update available","payload_off":false,"payload_on":true,"state_topic":"zigbee2mqtt/0x588e81fffe2b4513","unique_id":"0x588e81fffe2b4513_update_available_zigbee2mqtt","value_template":"{{ value_json.update_available}}"}'
Info Configuring '0x588e81fffe2b4513'
Info MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"interview_successful","meta":{"description":"TRADFRI shortcut button","friendly_name":"0x588e81fffe2b4513","model":"E1812","supported":true,"vendor":"IKEA"},"type":"pairing"}'
Info MQTT publish: topic 'zigbee2mqtt/0x588e81fffe2b4513', payload '{"battery":47,"linkquality":47}'
Info MQTT publish: topic 'zigbee2mqtt/0x588e81fffe2b4513', payload '{"battery":47,"linkquality":47,"update_available":false}'
Info MQTT publish: topic 'zigbee2mqtt/0x588e81fffe2b4513', payload '{"battery":47,"linkquality":47,"update":{"state":"idle"},"update_available":false}'
Info MQTT publish: topic 'zigbee2mqtt/0x588e81fffe2b4513', payload '{"battery":47,"linkquality":47,"update":{"state":"idle"},"update_available":false}'
Info Successfully configured '0x588e81fffe2b4513'

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. The same thing happens with the two other buttons i have

lkxnon commented 3 years ago

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.

Tonio16 commented 3 years ago

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: Zigbee2MQTT version 1.18.3 commit: f2e39af1 Coordinator type EZSP v8 Coordinator revision 6.9.1.0 build 214 Frontend version 0.4.0

Antoine

github-actions[bot] commented 3 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

idofr commented 3 years ago

Solved by switching to https://slae.sh/projects/cc2652/

silverl commented 3 years ago

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.

wiuwiu commented 3 years ago

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.

Adapter hardware: CC2652RB from slae.sh (firmware: 20210120)
zigbee2mqtt 1.20.0-1
Ikea Shortcut Button E1812 (firmware: 2.3.075)
MattWestb commented 3 years ago

@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.

JakubTHOC commented 3 years ago

Same problem here

tricoos commented 2 years ago

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 FW date: 20190715 FW version 2.3.015

Zigbee2MQTT Version 1.20.0 commit: 41b67fd

Coordinator

OTA Check Result MQTT publish: topic 'zigbee/bridge/log', payload '{"message":"Failed to check if update available for 'tradfributton1' (Device didn't respond to OTA request)","meta":{"device":"tradfributton1","status":"check_failed"},"type":"ota_update"}' Info MQTT publish: topic 'zigbee/bridge/response/device/ota_update/check', payload '{"data":{"id":"tradfributton1"},"error":"Failed to check if update available for 'tradfributton1' (Device didn't respond to OTA request)","status":"error","transaction":"520v7-1"}' Error Failed to check if update available for 'tradfributton1' (Device didn't respond to OTA request)

Maybe this helps for a cross-check.

tricoos commented 2 years ago

@willu 

Ikea Shortcut Button E1812 (firmware: 2.3.075)

Weird, my second button with the same firmware version just was logged as no update available: MQTT publish: topic 'zigbee/tradfributton2', payload '{"battery":100,"linkquality":30,"update":{"state":"idle"},"update_available":false}'

And that's with version 2.3.0.15 and you have 2.3.075 so there should be an update available. Maybe it helps if everyone with the problem here posts his button firmware version?

froogl commented 2 years ago

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).

AlesZurek commented 2 years ago

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 FW date: 20190715 FW version 2.3.015

zigbee2mqtt_version 1.21.0 commit: 70891ee coordinator_type zStack12 coordinator_revision 20180507 frontend_version 0.5.18

I have Rapsberry PI with Sonoff CC2351.

silverl commented 2 years ago

I'm having this same problem with:

  • ConBee II USB
  • zigbee2mqtt 1.20.0-1
  • Ikea Tradfri E1812
  • Ikea SYMFONISK E1744

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'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.

silverl commented 2 years ago

I just upgraded my ConBee II firmware to deCONZ_ConBeeII_0x26720700.bin.GCF. There has been no change in behavior. Device pairs successfully, but no events are triggered.

Link Quality Indicator and Battery are sampled just once during setup as far as I can tell.

wiuwiu commented 2 years ago

@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.

Thanks for info. You have right. I have another Ikea button which I don't upgraded with Ikea test firmware and it works perfect.

MattWestb commented 2 years ago

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.

tricoos commented 2 years ago

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:

Zigbee2MQTT:info  2021-08-25 17:36:59: MQTT publish: topic 'zigbee/bridge/event', payload '{"data":{"friendly_name":"tradfributton1","ieee_address":"0xb4e3f9fffe5d6e08"},"type":"device_announce"}'
Zigbee2MQTT:info  2021-08-25 17:37:03: MQTT publish: topic 'zigbee/bridge/event', payload '{"data":{"friendly_name":"tradfributton1","ieee_address":"0xb4e3f9fffe5d6e08"},"type":"device_announce"}'
Zigbee2MQTT:info  2021-08-25 17:37:06: MQTT publish: topic 'zigbee/bridge/event', payload '{"data":{"friendly_name":"tradfributton1","ieee_address":"0xb4e3f9fffe5d6e08"},"type":"device_announce"}'
Zigbee2MQTT:info  2021-08-25 22:43:13: MQTT publish: topic 'zigbee/bridge/event', payload '{"data":{"friendly_name":"tradfributton1","ieee_address":"0xb4e3f9fffe5d6e08"},"type":"device_announce"}'
Zigbee2MQTT:info  2021-08-26 07:34:25: MQTT publish: topic 'zigbee/bridge/event', payload '{"data":{"friendly_name":"tradfributton1","ieee_address":"0xb4e3f9fffe5d6e08"},"type":"device_announce"}'
Zigbee2MQTT:info  2021-08-26 07:39:43: Accepting joining not in blocklist device '0xb4e3f9fffe5d6e08'
Zigbee2MQTT:info  2021-08-26 07:39:43: Accepting joining not in blocklist device '0xb4e3f9fffe5d6e08'
Zigbee2MQTT:info  2021-08-26 07:39:43: MQTT publish: topic 'zigbee/bridge/event', payload '{"data":{"friendly_name":"tradfributton1","ieee_address":"0xb4e3f9fffe5d6e08"},"type":"device_announce"}'
Zigbee2MQTT:info  2021-08-26 16:53:24: MQTT publish: topic 'zigbee/bridge/event', payload '{"data":{"friendly_name":"tradfributton1","ieee_address":"0xb4e3f9fffe5d6e08"},"type":"device_announce"}'
Zigbee2MQTT:info  2021-08-26 16:53:27: MQTT publish: topic 'zigbee/bridge/event', payload '{"data":{"friendly_name":"tradfributton1","ieee_address":"0xb4e3f9fffe5d6e08"},"type":"device_announce"}'
Zigbee2MQTT:info  2021-08-26 16:53:30: MQTT publish: topic 'zigbee/bridge/event', payload '{"data":{"friendly_name":"tradfributton1","ieee_address":"0xb4e3f9fffe5d6e08"},"type":"device_announce"}'
Zigbee2MQTT:info  2021-08-26 17:56:47: Accepting joining not in blocklist device '0xb4e3f9fffe5d6e08'
Zigbee2MQTT:info  2021-08-26 17:56:47: Accepting joining not in blocklist device '0xb4e3f9fffe5d6e08'
Zigbee2MQTT:info  2021-08-26 17:56:48: MQTT publish: topic 'zigbee/bridge/event', payload '{"data":{"friendly_name":"tradfributton1","ieee_address":"0xb4e3f9fffe5d6e08"},"type":"device_announce"}'
Zigbee2MQTT:info  2021-08-26 17:56:54: Accepting joining not in blocklist device '0xb4e3f9fffe5d6e08'
Zigbee2MQTT:info  2021-08-26 17:56:54: Accepting joining not in blocklist device '0xb4e3f9fffe5d6e08'
Zigbee2MQTT:info  2021-08-26 17:56:54: MQTT publish: topic 'zigbee/bridge/event', payload '{"data":{"friendly_name":"tradfributton1","ieee_address":"0xb4e3f9fffe5d6e08"},"type":"device_announce"}'
Zigbee2MQTT:info  2021-08-26 20:09:45: MQTT publish: topic 'zigbee/bridge/event', payload '{"data":{"friendly_name":"tradfributton1","ieee_address":"0xb4e3f9fffe5d6e08"},"type":"device_announce"}'
Zigbee2MQTT:info  2021-08-26 20:14:09: MQTT publish: topic 'zigbee/bridge/event', payload '{"data":{"friendly_name":"tradfributton1","ieee_address":"0xb4e3f9fffe5d6e08"},"type":"device_announce"}'
Zigbee2MQTT:info  2021-08-26 20:18:48: MQTT publish: topic 'zigbee/bridge/event', payload '{"data":{"friendly_name":"tradfributton1","ieee_address":"0xb4e3f9fffe5d6e08"},"type":"device_announce"}'
Zigbee2MQTT:info  2021-08-26 22:32:42: MQTT publish: topic 'zigbee/bridge/event', payload '{"data":{"friendly_name":"tradfributton1","ieee_address":"0xb4e3f9fffe5d6e08"},"type":"device_announce"}'
Zigbee2MQTT:info  2021-08-27 00:13:20: MQTT publish: topic 'zigbee/bridge/event', payload '{"data":{"friendly_name":"tradfributton1","ieee_address":"0xb4e3f9fffe5d6e08"},"type":"device_announce"}'
Zigbee2MQTT:info  2021-08-27 00:13:26: MQTT publish: topic 'zigbee/bridge/event', payload '{"data":{"friendly_name":"tradfributton1","ieee_address":"0xb4e3f9fffe5d6e08"},"type":"device_announce"}'
Zigbee2MQTT:info  2021-08-27 00:13:30: Accepting joining not in blocklist device '0xb4e3f9fffe5d6e08'
Zigbee2MQTT:info  2021-08-27 00:13:30: Accepting joining not in blocklist device '0xb4e3f9fffe5d6e08'
Zigbee2MQTT:info  2021-08-27 00:13:31: MQTT publish: topic 'zigbee/bridge/event', payload '{"data":{"friendly_name":"tradfributton1","ieee_address":"0xb4e3f9fffe5d6e08"},"type":"device_announce"}'
Zigbee2MQTT:info  2021-08-27 05:37:28: MQTT publish: topic 'zigbee/bridge/event', payload '{"data":{"friendly_name":"tradfributton1","ieee_address":"0xb4e3f9fffe5d6e08"},"type":"device_announce"}'
Zigbee2MQTT:info  2021-08-27 05:37:31: MQTT publish: topic 'zigbee/bridge/event', payload '{"data":{"friendly_name":"tradfributton1","ieee_address":"0xb4e3f9fffe5d6e08"},"type":"device_announce"}'
Zigbee2MQTT:info  2021-08-27 05:37:35: Accepting joining not in blocklist device '0xb4e3f9fffe5d6e08'
Zigbee2MQTT:info  2021-08-27 05:37:35: Accepting joining not in blocklist device '0xb4e3f9fffe5d6e08'
Zigbee2MQTT:info  2021-08-27 05:37:35: MQTT publish: topic 'zigbee/bridge/event', payload '{"data":{"friendly_name":"tradfributton1","ieee_address":"0xb4e3f9fffe5d6e08"},"type":"device_announce"}'
Zigbee2MQTT:info  2021-08-27 05:37:41: Accepting joining not in blocklist device '0xb4e3f9fffe5d6e08'
Zigbee2MQTT:info  2021-08-27 05:37:41: Accepting joining not in blocklist device '0xb4e3f9fffe5d6e08'
Zigbee2MQTT:info  2021-08-27 05:37:41: MQTT publish: topic 'zigbee/bridge/event', payload '{"data":{"friendly_name":"tradfributton1","ieee_address":"0xb4e3f9fffe5d6e08"},"type":"device_announce"}'
Zigbee2MQTT:info  2021-08-27 07:33:04: MQTT publish: topic 'zigbee/bridge/event', payload '{"data":{"friendly_name":"tradfributton1","ieee_address":"0xb4e3f9fffe5d6e08"},"type":"device_announce"}'
Zigbee2MQTT:info  2021-08-27 07:33:07: MQTT publish: topic 'zigbee/bridge/event', payload '{"data":{"friendly_name":"tradfributton1","ieee_address":"0xb4e3f9fffe5d6e08"},"type":"device_announce"}'
Zigbee2MQTT:info  2021-08-27 07:33:18: Accepting joining not in blocklist device '0xb4e3f9fffe5d6e08'
Zigbee2MQTT:info  2021-08-27 07:33:18: Accepting joining not in blocklist device '0xb4e3f9fffe5d6e08'
Zigbee2MQTT:info  2021-08-27 07:33:18: MQTT publish: topic 'zigbee/bridge/event', payload '{"data":{"friendly_name":"tradfributton1","ieee_address":"0xb4e3f9fffe5d6e08"},"type":"device_announce"}
Zigbee2MQTT:info  2021-08-27 07:33:23: Accepting joining not in blocklist device '0xb4e3f9fffe5d6e08'
Zigbee2MQTT:info  2021-08-27 07:33:23: Accepting joining not in blocklist device '0xb4e3f9fffe5d6e08'
Zigbee2MQTT:info  2021-08-27 07:33:23: MQTT publish: topic 'zigbee/bridge/event', payload '{"data":{"friendly_name":"tradfributton1","ieee_address":"0xb4e3f9fffe5d6e08"},"type":"device_announce"}'

The symptom is that the button does not work until after has joined again.

JHthe4 commented 2 years ago

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. 

info  2021-09-09 17:09:11: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0xb4e3f9fffe5a9fa6","ieee_address":"0xb4e3f9fffe5a9fa6"},"type":"device_joined"}'
info  2021-09-09 17:09:11: Configuring '0xb4e3f9fffe5a9fa6'
info  2021-09-09 17:09:11: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":{"friendly_name":"0xb4e3f9fffe5a9fa6"},"type":"device_connected"}'
debug 2021-09-09 17:09:13: Device '0xb4e3f9fffe5a9fa6' announced itself
info  2021-09-09 17:09:13: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0xb4e3f9fffe5a9fa6","ieee_address":"0xb4e3f9fffe5a9fa6"},"type":"device_announce"}'
info  2021-09-09 17:09:13: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"announce","meta":{"friendly_name":"0xb4e3f9fffe5a9fa6"},"type":"device_announced"}'
error 2021-09-09 17:09:21: Failed to configure '0xb4e3f9fffe5a9fa6', attempt 1 (Error: Bind 0xb4e3f9fffe5a9fa6/1 genPowerCfg from '901' failed (AREQ - ZDO - bindRsp after 10000ms)
    at Timeout._onTimeout (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/src/utils/waitress.ts:64:35)
    at listOnTimeout (internal/timers.js:554:17)
    at processTimers (internal/timers.js:497:7))
debug 2021-09-09 17:11:03: Received MQTT message on 'zigbee2mqtt/bridge/request/device/configure' with data '0xb4e3f9fffe5a9fa6'
info  2021-09-09 17:11:03: Configuring '0xb4e3f9fffe5a9fa6'
debug 2021-09-09 17:11:03: Received Zigbee message from '0xb4e3f9fffe5a9fa6', type 'commandQueryNextImageRequest', cluster 'genOta', data '{"fieldControl":1,"fileVersion":587290161,"imageType":4550,"manufacturerCode":4476}' from endpoint 1 with groupID 0
debug 2021-09-09 17:11:03: Device '0xb4e3f9fffe5a9fa6' requested OTA
debug 2021-09-09 17:11:03: Check if update available for '0xb4e3f9fffe5a9fa6' (TRADFRI SHORTCUT Button)
debug 2021-09-09 17:11:04: Is new image available for '0xb4e3f9fffe5a9fa6', current '{"fieldControl":1,"manufacturerCode":4476,"imageType":4550,"fileVersion":587290161}', latest meta '{"fileVersion":587290161,"url":"http://fw.ota.homesmart.ikea.net/global/GW1.0/01.15.055/bin/10054470-TRADFRI-shortcut-button-2.3.015.ota.ota.signed"}'
debug 2021-09-09 17:11:04: Update available for '0xb4e3f9fffe5a9fa6': NO
info  2021-09-09 17:11:04: MQTT publish: topic 'zigbee2mqtt/0xb4e3f9fffe5a9fa6', payload '{"linkquality":81,"update":{"state":"idle"},"update_available":false}'
debug 2021-09-09 17:11:07: Received Zigbee message from '0xb4e3f9fffe5a9fa6', type 'readResponse', cluster 'genPowerCfg', data '{"batteryPercentageRemaining":74}' from endpoint 1 with groupID 0
info  2021-09-09 17:11:07: MQTT publish: topic 'zigbee2mqtt/0xb4e3f9fffe5a9fa6', payload '{"battery":74,"linkquality":81,"update":{"state":"idle"},"update_available":false}'
info  2021-09-09 17:11:07: Successfully configured '0xb4e3f9fffe5a9fa6'
debug 2021-09-09 17:30:02: Device '0xb4e3f9fffe5a9fa6' announced itself
info  2021-09-09 17:30:03: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0xb4e3f9fffe5a9fa6","ieee_address":"0xb4e3f9fffe5a9fa6"},"type":"device_announce"}'
info  2021-09-09 17:30:03: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"announce","meta":{"friendly_name":"0xb4e3f9fffe5a9fa6"},"type":"device_announced"}'
debug 2021-09-09 17:32:23: Device '0xb4e3f9fffe5a9fa6' announced itself
info  2021-09-09 17:32:23: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0xb4e3f9fffe5a9fa6","ieee_address":"0xb4e3f9fffe5a9fa6"},"type":"device_announce"}'
info  2021-09-09 17:32:23: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"announce","meta":{"friendly_name":"0xb4e3f9fffe5a9fa6"},"type":"device_announced"}'
McMornan commented 2 years ago

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 😁

voltagex commented 2 years ago

Having this issue with a Symfonisk, although I see the following

Sep 16 02:34:51 boxodisks npm[3694108]: Zigbee2MQTT:error 2021-09-16 02:34:51: Failed to configure '0x5c0272fffeac3850', attempt 1 (Error: Bind 0x5c0272fffeac3850/1 genPowerCfg from '0x00124b0001575f2a/1' failed (waiting for response TIMEOUT)

How can I help debug this?

Sep 16 02:42:09 boxodisks npm[3694331]: Zigbee2MQTT:info  2021-09-16 02:42:09: Starting Zigbee2MQTT version 1.21.1 (commit #4a51e0c0)
Sep 16 02:42:09 boxodisks npm[3694331]: Zigbee2MQTT:info  2021-09-16 02:42:09: Starting zigbee-herdsman (0.13.138)
Sep 16 02:42:10 boxodisks npm[3694331]: CREATED DECONZ ADAPTER
Sep 16 02:42:10 boxodisks npm[3694331]: Zigbee2MQTT:info  2021-09-16 02:42:10: zigbee-herdsman started (resumed)
Sep 16 02:42:10 boxodisks npm[3694331]: Zigbee2MQTT:info  2021-09-16 02:42:10: Coordinator firmware version: '{"meta":{"maintrel":0,"majorrel":38,"minorrel":112,"product":0,"revision":"0x26700700","transportrev":0},"type":"ConBee2/RaspBee2"}'
cpuks commented 2 years ago

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?

ristomatti commented 2 years ago

After 10-15 tries it finally worked. But I admit that pita process is not as it should be 😁

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.

ThijSlim commented 2 years ago

Experiencing the same issues. devices pair successfully, but no press events are received..

ristomatti commented 2 years ago

A follow up on my previous comment: All 3/4 IKEA Shortcut buttons I managed to pair with persistence have worked without any issues. As well have the two Symphony dimmers.

But the remaining Shortcut button did not stay on rh network more more than a few hours when I tried it again. I'm pretty sure it's faulty.

MattWestb commented 2 years ago

@ristomatti what coordinator is you using ? I think its problems with that the coordinator is accepting that Zigbee 3 devices like updating there trust center link key and is leaving the network because of that.

ristomatti commented 2 years ago

@ristomatti what coordinator is you using ?

Check couple of messages back.

karlc28 commented 2 years ago

Has anyone got a fix for this issue yet as I have the same issue E1812 pairs fine but shows n/a for action no battery % and no action performed

ristomatti commented 2 years ago

@karlc28 Sorry I've got no fix other than the one I suggested here https://github.com/Koenkk/zigbee2mqtt/issues/7150#issuecomment-927132492. 3/4 of the shortcut buttons I bought still work 100% after the initial issues. The last one I've tried to pair countless times after posting that to no avail. I'm pretty sure it's faulty and I suspect there'd be more picky/faulty units out there given how much issues people here are reporting (while some have got them to work).

I would suggest just return it and see if a replacement helps. I should have also but given the cheap price it felt like too much effort. :grimacing:

karlc28 commented 2 years ago

@karlc28 Sorry I've got no fix other than the one I suggested here #7150 (comment). 3/4 of the shortcut buttons I bought still work 100% after the initial issues. The last one I've tried to pair countless times after posting that to no avail. I'm pretty sure it's faulty and I suspect there'd be more picky/faulty units out there given how much issues people here are reporting (while some have got them to work).

The thing is I can connect it to smartthings hub and use the single click really easily so don't think it's faulty

X52p commented 2 years ago

I have the same problem. It worked fine for about a year. Then I upgraded my USB dongle to a CC2652 (and also updated zigbee2mqtt) Some hours later the first of my two shortcut buttons stopped working, and today (about 24h later) the second one also gave up.

So (I think) it could be changes in Zigbe2mqtt or a problem with the firmware of the dongle.

If I can provide anything useful (like logs or something) please tell me.

jonas740 commented 2 years ago

Pretty much same problem for me. Using stick from slae.sh CC2652RB. Even reflashed it a few times. Removed zigbee2mqtt including config folders and everything and made a clean install.

Managed to get two buttons paired again (E1812 and E1743) wich i bought during summer. The other two i bought last week won´t pair or when they actually do pair they do nothing.

Like somone else said, i paired them all yesterday and got all of them to work. Few hours later they one by one stopped to work and i was not able to pair them again until today as mentioned above.

I have used Zigbee with theese buttons for like a month just to give it a try. But tbh, i am not impressed at all. Setting it up and all that gave me better understanding on how they actually work and it is, atleast according to me, a really poor design except for the fact that they will not consume so much power. I have not had a chance to test that just yet however. Other then that i really hope somone comes up with something better then Zigbee.

MattWestb commented 2 years ago

Is the controllers connected direct to the coordinator or to routers ? I have over 15 of IKEA controllers of different types and no problems at all but i have blocking the coordinator having direct children (= no end device can not connecting direct to the coordinator and must suing routers).

I was 3 week on holiday and my test network that have many of them was the coordinator powered down all the time and all was going on line after some minuter after power it on and no lost device.

2 days later one Aqara weather sensor was going of line then the batty was dead but that was expected :-))

jonas740 commented 2 years ago

Is the controllers connected direct to the coordinator or to routers ? I have over 15 of IKEA controllers of different types and no problems at all but i have blocking the coordinator having direct children (= no end device can not connecting direct to the coordinator and must suing routers).

I was 3 week on holiday and my test network that have many of them was the coordinator powered down all the time and all was going on line after some minuter after power it on and no lost device.

2 days later one Aqara weather sensor was going of line then the batty was dead but that was expected :-))

My Ikea buttons are linked directly to the CC2652RB Coordinator. The buttons are the only Zigbee devices i own so i have no routers. But when pairing the buttons you do this at the coordinator right ? well two of my buttons can no longer pair for some reason. And i am using Ikea tradfri E1812 and E1743.

if it wont work without routers i guess the zigbee buttons goes in the trashcan.

Just wondering about something. How can Zigbees range be so bad ? It uses 2.4ghz and its really really bad. And that made me wonder, why didnt they use something like 400-900mhz instead ? Because the function of the button is pretty much like the good old RF plugs with remote. If the Zigbee coordinator gets the signal then it will report that it got it, so using a frequency at that 2.4ghz must be because you need to sell more equipment to increase the range.

MattWestb commented 2 years ago

By one (or 3) controlled outlet as router (or the "family pack with one E1743) and you have one good router.

You is very likely having interference from WiFi or your coordinator having very bad radio performance.

And one Zigbee network without routers is not good then its have no redundancy that is the key for getting one good working network.

433 Mhz can working but the band is not large enough for building more networks and 800 / 900 Mhz is not free all over the world.

The paring problem is one TI firmware problem not IKEA they is good on connecting to most routers (coordinator is one router with extra functions). Reset / delete the NVM in the coordinator and you can paring the button a gen.

ristomatti commented 2 years ago

I didn't get the IKEA buttons pairing even with an IKEA range extender/router. However got them to pair and stay paired (few weeks and counting) with a Blitzwolf (TuYa) smart socket. :eyes:

MattWestb commented 2 years ago

For CC2652R and other TI user its very likely one firmware problem in the coordinator. https://github.com/Koenkk/zigbee2mqtt/issues/8376 For deCONZ i cant saying but they was having many strange connecting problem and some is reporting that the last firmware is not working at all with direct connected sleeping end device and other is saying the opposite if reading deCONZ issues.

Edit: Sorry was pasting wrong link to the issue :-(( Fixed.

AlesZurek commented 2 years ago

Hi guys, I wanted to share my update. As I wrote before I have this issue that I got no action from ikea shortcut button after pairing.

I had coordinator Sonoff CC2351 in my Rapsberry pi 4. More info zigbee2mqtt_version 1.21.0 commit: 70891ee coordinator_type zStack12 coordinator_revision 20180507 frontend_version 0.5.18

Currently I ordered Sonoff CC2652P coordinator https://itead.cc/product/sonoff-zigbee-3-0-usb-dongle-plus

Today I received it so I tried it and on first try I was able to add my IKEA shortcut button and it is working. Sadly I wasn't able to add my second IKEA shortcut button but maybe it can be malfunctional. Not sure about that but the other one is working fine. I was also able to get working another piece of hardware which wasn't working (no actions received) TuYa TS004F.

That new coordinator have values: Zigbee2MQTT version 1.21.0 commit: 70891ee Coordinator type zStack3x0 Coordinator revision 20210120 Frontend version 0.5.18

So in my case I just need to change my coordinator to get it work.

McMornan commented 2 years ago

Hi,

thanks for sharing. However in my case its not the pairing - that can be done in the vicinity of the coordinator and retrying several times - it's the STAYING PAIRED which ist the problem for me. So would be great if you could give us an update in a few days if the button is still recognized.

Lars

X52p commented 2 years ago

I have the same problem. It worked fine for about a year. Then I upgraded my USB dongle to a CC2652 (and also updated zigbee2mqtt) Some hours later the first of my two shortcut buttons stopped working, and today (about 24h later) the second one also gave up.

So (I think) it could be changes in Zigbe2mqtt or a problem with the firmware of the dongle.

If I can provide anything useful (like logs or something) please tell me.

I updated my CC2652 to the current firmware version (20210708) and re-paired the buttons. I also updated the firmware of the buttons to the newest version (OTA update)

Still, after a few hours, they disconnect again.

Theoreet commented 2 years ago

i'am having some kind of the same issue. Playing aroud with the E1812, running the 2.3.080/20210727 firmware. The Z2M i tried 1.22.0 and latest Edge version. The USB 2652P runs 20210319 firmware version. Frontend version 0.6.30 Pairing seems to be working after several tries, battery seems to be reporting, but the action stays "null". the other remotes reports okay ( this is the only shortcut button i own)

belkone commented 2 years ago

@idofr try this: https://github.com/Koenkk/zigbee2mqtt/issues/9439#issuecomment-956456214

alexwala commented 2 years ago

i'am having some kind of the same issue. Playing aroud with the E1812, running the 2.3.080/20210727 firmware. The Z2M i tried 1.22.0 and latest Edge version. The USB 2652P runs 20210319 firmware version. Frontend version 0.6.30 Pairing seems to be working after several tries, battery seems to be reporting, but the action stays "null". the other remotes reports okay ( this is the only shortcut button i own)

@Theoreet how did you updated to 2.3.080, using z2m ota ? may you can help on https://github.com/Koenkk/zigbee2mqtt/issues/9457

EricV-hue commented 2 years ago

I had just written my experience here: https://github.com/Koenkk/zigbee2mqtt/issues/9457#issuecomment-957760527

To make reading easier:

I also struggled with the updated sensors. Same issue: after updating the 'old' firmware version remained visible in the UI. Stopped zigbee2mqqt in hassio, removed the usb-stick (CC2652RB) and started Z2M again. Firmware version was listed OK then. <

Other issues/observations:

after the update the bindig to a group did not work anymore removing the remote from the zigbee net was only possible by forced removal. after re-pairing binding of the remote to a group was still not possible direct binding to e.g. a bulb is possible now this direct binding can be done without removal of the default_binding_group added 'LevelCtrl' and 'OnOff' bindings to the coordinator, to make the remote accessible for hassio

MaciejR89 commented 2 years ago

I updated the E1812 to version 2.3.080. Initially the button would not send any data when pressed. Binding "LevelCtrl" and "OnOff" of the E1821 button to coordinator fix the problem

Zigbee2MQTT:debug  Received MQTT message on 'zigbee2mqtt/bridge/request/device/bind' with data '{"clusters":["genOnOff","genLevelCtrl"],"from":ikea_shortcut_button/1","to":"Coordinator","transaction":"y1xu9-4"}'
Zigbee2MQTT:debug  binding cluster 'genOnOff' from 'ikea_shortcut_button' to 'Coordinator'
Zigbee2MQTT:debug  binding cluster 'genLevelCtrl' from 'ikea_shortcut_button' to 'Coordinator'
Zigbee2MQTT:info  Successfully bound cluster 'genLevelCtrl' from 'ikea_shortcut_button' to 'Coordinator'
Zigbee2MQTT:info  Successfully bound cluster 'genOnOff' from 'ikea_shortcut_button' to 'Coordinator'
Zigbee2MQTT:info  MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":{"cluster":"genLevelCtrl","from":"ikea_shortcut_button","to":"Coordinator"},"type":"device_bind"}'
Zigbee2MQTT:debug Received Zigbee message from 'ikea_shortcut_button', type 'commandOn', cluster 'genOnOff', data '{}' from endpoint 1 with groupID 0
Zigbee2MQTT:info  MQTT publish: topic 'zigbee2mqtt/ikea_shortcut_button', payload '{"action":"on","battery":60,"linkquality":48,"update":{"state":"idle"},"update_available":false}'
Zigbee2MQTT:info  MQTT publish: topic 'zigbee2mqtt/ikea_shortcut_button/action', payload 'on'
tricoos commented 2 years ago

@MaciejR89 After doing this it wreaks havoc for me (I have a toggle action onClick) as it fires three times now:

MQTT publish: topic 'zigbee/tradfributton1', payload '{"action":"on","battery":100,"linkquality":45,"update":{"state":"available"},"update_available":true}'
Info MQTT publish: topic 'zigbee/tradfributton1', payload '{"action":"on","battery":100,"linkquality":45,"update":{"state":"available"},"update_available":true}'
Info MQTT publish: topic 'zigbee/tradfributton1', payload '{"action":"on","battery":100,"linkquality":45,"update":{"state":"available"},"update_available":true}'
tricoos commented 2 years ago

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.