OH3 IKEA Tradfri remote control with zigbee2mqtt

Setup, Configuration and Use Beginners
, ,
1

Hi,

I’m trying to set up an Ikea Tradfri Remote Control in OpenHab 3.
The remote control is connected via zigbee2mqtt. The corresponding entries appear in the zigbee2mqtt log files.

Feb 22 22:08:27 openhab npm[5401]: Zigbee2MQTT:info  2021-02-22 22:08:27: MQTT publish: topic 'zigbee2mqtt/schalterWohnEins/battery', payload '60'
Feb 22 22:08:27 openhab npm[5401]: Zigbee2MQTT:info  2021-02-22 22:08:27: MQTT publish: topic 'zigbee2mqtt/schalterWohnEins/action', payload 'toggle'
Feb 22 22:08:27 openhab npm[5401]: Zigbee2MQTT:info  2021-02-22 22:08:27: MQTT publish: topic 'zigbee2mqtt/schalterWohnEins/linkquality', payload '111'

An MQTT brocker is set up in OpenHab, with which a Tradfri socket is already controlled.
Unfortunately, I cannot set up the remote control.

How can I set up the remote control in OpenHab?

EDIT: Device Ikea E1524/1810

2

Can you link to the device from this page?

In the meantime, here’s an IKEA dimmer switch configuration, which uses almost identical parameters:

3

Sorry I forgot the link.

4

Could you elaborate on what your challenge is?
The usual progress would be to create your MQTT broker in OpenHAB and then create each MQTT device as extra thing with its respective channels.
I got multiple remotes (the normal one with only on/off/hold action, not the big one you linked, whereas concept is the same) working.

5

I have already set up an MQTT brocker. In addition, a generic MQTT thing for a socket.
My problem is how do I set up the remote control. How do I have to configure the thing and the channels? In the first step I want to switch the socket with the remote control.

6

I would recommend installing MQTT Explorer, and with that running press all the buttons on your remote and see what happens: this will tell you the correct topics, and what features your remote has. Once you have that, you can fill in the relevant fields in the Thing configuration.

1 Like
7

The triggering of the buttons is transmitted via zigbee2mqtt/switchLight/action. The name of the button is in the message. At that point, however, I’m stuck.
How can I get a wireless socket on/off when I press a button?
All of the examples I’ve found so far relate to OpenHab 2.
I currently have the following configurations:

UID: mqtt:topic:MqttBrocker:SwitchLight1
label: SwitchLight 1
thingTypeUID: mqtt:topic
configuration: {}
bridgeUID: mqtt:broker:MqttBrocker
location: room1
channels:
  - id: button
    channelTypeUID: mqtt:string
    label: button
    description: ""
    configuration:
      stateTopic: zigbee2mqtt/switchLight/action

UID: mqtt:topic:MqttBrocker:socket1
label: socket1
thingTypeUID: mqtt:topic
configuration: {}
bridgeUID: mqtt:broker:MqttBrocker
location: room1
channels:
  - id: socket
    channelTypeUID: mqtt:switch
    label: socket
    description: ""
    configuration:
      commandTopic: zigbee2mqtt/socket1/set/state
      off: OFF
      on: ON
8

Hopefully you mean the name of the action?

You now need a rule which is triggered when the Item that is linked to the mqtt:topic:MqttBrocker:SwitchLight1:button Channel changes state, after which the rule can switch your light on and off.

How are you setting up your rules - files or UI? If it’s files then all the OH2 examples will still work.

9

The problem with this specific remote controller (dubbed “Puck”) is that the button that is supposed to act like a switch only sends one action, toggle. The controller itself doesn’t have a concept of “on/off”.

So far I couldn’t find a way to make it act directly like a switch item but there is one quick (and ugly) workaround: the button, when held for ~2 sec, also sends the action toggle_hold. You can then map toggle as on and toggle_hold as off.

I would, however, prefer a channel type that would act like a toggle switch.

10

Hello @hafniumzinc

Since you’ve documented your use of Zigbee2MQTT I wanted to inquire.

I have a heap of Sonoff Zigbee door sensors, and Sonoff Switches, and Sonoff Motion Sensors in my house, all set up with the Zigbee binding, working perfectly.

I recently got a few Ikea Tradfri Switches IKEA E1743 control via MQTT | Zigbee2MQTT and paired them with the Zigbee binding, and set up just like I have my numerous other sensors and sonoff switches set up, but nothing seems to be working. Openhab detects it as online, but receives no input from it, although unlike my Sonoff SNZB-01’s, the Ikea switch’s channel is detected as MACADDRESS_1_dimmer wheras the sonoffs all show MACCADDRESS_1_switch

Although if I can’t get that working, I may try the Zigbee2MQTT route, but have a question, can it run alongside the regular Zigbee binding, using the same zigbee dongle? I would hate to have to move 6 or 7 doors, 3 motion sensors, and a handful of switches from the Zigbee binding over to Zigbee2MQTT and re-do everything using MQTT instead while it’s all been working (almost)flawlessly.

11

I got this IKEA button working with z2mqtt, would be surprised if it does not work with OH ZigBee binding.
Do you have any log entries?

Re channel, take into account that the button supports 5 actions, 2 of which are dimmer actions (brightness up and down), hence maybe the channel name (there is only one action channel for all 5 actions).

12

Thanks for the reply!

I’ve just enabled debug logging via

log:set debug org.openhab.binding.zigbee
log:set debug com.zsmartsystems.zigbee
log:set info com.zsmartsystems.zigbee.dongle.ember.internal.ash

Although after pressing the buttons (both single taps, and tap and hold on each) the unique device name doesn’t show up in openhab.log at all.

I pressed the Sonoff switch on my desk to manually control my office light and checked the logs and found the entries for it, so I find that a bit strange.

Can you suggest anything else I can check or try to get it working?

I don’t care quite as much about the dimmer states (pressing and holding either button, although that action could be useful) I more thought the on/off button would be good to trigger certain lights on or off, or program some rules to jump through various dim levels (5/10/25/50/75/100%) using the on as a “jump up to next state” and off as "jump down to next state kind of option.

–Edit–
It does appear to be logging, here’s what the log outputs for that particular device

Line 981: 2022-03-07 20:02:00.635 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - 8CF681FFFE2884D2: Node update. NWK Address=6574
	Line 982: 2022-03-07 20:02:00.635 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - 8CF681FFFE2884D2: Node 6574 is not updated
	Line 986: 2022-03-07 20:02:00.638 [DEBUG] [verter.ZigBeeConverterBatteryPercent] - 8CF681FFFE2884D2: ZigBee attribute reports ZclAttribute [cluster=Power Configuration, id=32, name=Battery Voltage, dataType=UNSIGNED_8_BIT_INTEGER, lastValue=30, lastReportTime=Mon Mar 07 20:02:00 MST 2022, implemented=true]
	Line 987: 2022-03-07 20:02:00.638 [DEBUG] [verter.ZigBeeConverterBatteryVoltage] - 8CF681FFFE2884D2: ZigBee attribute reports ZclAttribute [cluster=Power Configuration, id=32, name=Battery Voltage, dataType=UNSIGNED_8_BIT_INTEGER, lastValue=30, lastReportTime=Mon Mar 07 20:02:00 MST 2022, implemented=true]
	Line 988: 2022-03-07 20:02:00.638 [DEBUG] [e.transaction.ZigBeeTransactionQueue] - 8CF681FFFE2884D2: Added transaction to queue, len=1, transaction=ZigBeeTransaction [ieeeAddress=8CF681FFFE2884D2 queueTime=0, state=WAITING, sendCnt=0, command=DefaultResponse [Power Configuration: 0000/0 -> 6574/1, cluster=0001, TID=62, commandIdentifier=10, statusCode=SUCCESS]]
	Line 988: 2022-03-07 20:02:00.638 [DEBUG] [e.transaction.ZigBeeTransactionQueue] - 8CF681FFFE2884D2: Added transaction to queue, len=1, transaction=ZigBeeTransaction [ieeeAddress=8CF681FFFE2884D2 queueTime=0, state=WAITING, sendCnt=0, command=DefaultResponse [Power Configuration: 0000/0 -> 6574/1, cluster=0001, TID=62, commandIdentifier=10, statusCode=SUCCESS]]
	Line 990: 2022-03-07 20:02:00.638 [DEBUG] [transaction.ZigBeeTransactionManager] - 6574/1: Sending ZigBeeTransaction [ieeeAddress=8CF681FFFE2884D2 queueTime=0, state=WAITING, sendCnt=0, command=DefaultResponse [Power Configuration: 0000/0 -> 6574/1, cluster=0001, TID=62, commandIdentifier=10, statusCode=SUCCESS]]
	Line 991: 2022-03-07 20:02:00.638 [DEBUG] [converter.ZigBeeBaseChannelConverter] - 8CF681FFFE2884D2: Channel zigbee:device:7e7c171ea7:8cf681fffe2884d2:8CF681FFFE2884D2_1_batteryvoltage updated to 3 V
	Line 991: 2022-03-07 20:02:00.638 [DEBUG] [converter.ZigBeeBaseChannelConverter] - 8CF681FFFE2884D2: Channel zigbee:device:7e7c171ea7:8cf681fffe2884d2:8CF681FFFE2884D2_1_batteryvoltage updated to 3 V
	Line 991: 2022-03-07 20:02:00.638 [DEBUG] [converter.ZigBeeBaseChannelConverter] - 8CF681FFFE2884D2: Channel zigbee:device:7e7c171ea7:8cf681fffe2884d2:8CF681FFFE2884D2_1_batteryvoltage updated to 3 V
	Line 994: 2022-03-07 20:02:00.639 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 8CF681FFFE2884D2: Updating ZigBee channel state zigbee:device:7e7c171ea7:8cf681fffe2884d2:8CF681FFFE2884D2_1_batteryvoltage to 3 V
	Line 994: 2022-03-07 20:02:00.639 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 8CF681FFFE2884D2: Updating ZigBee channel state zigbee:device:7e7c171ea7:8cf681fffe2884d2:8CF681FFFE2884D2_1_batteryvoltage to 3 V
	Line 994: 2022-03-07 20:02:00.639 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 8CF681FFFE2884D2: Updating ZigBee channel state zigbee:device:7e7c171ea7:8cf681fffe2884d2:8CF681FFFE2884D2_1_batteryvoltage to 3 V
	Line 996: 2022-03-07 20:02:00.639 [DEBUG] [.zigbee.handler.ZigBeeIsAliveTracker] - IsAlive Tracker reset for handler with thingUID=zigbee:device:7e7c171ea7:8cf681fffe2884d2
	Line 998: 2022-03-07 20:02:00.639 [DEBUG] [.zigbee.handler.ZigBeeIsAliveTracker] - IsAlive Tracker cancelled task for thingUID=zigbee:device:7e7c171ea7:8cf681fffe2884d2
	Line 999: 2022-03-07 20:02:00.639 [DEBUG] [.zigbee.handler.ZigBeeIsAliveTracker] - IsAlive Tracker scheduled task for thingUID=zigbee:device:7e7c171ea7:8cf681fffe2884d2 in 14430 seconds
	Line 1003: 2022-03-07 20:02:00.911 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - 8CF681FFFE2884D2: Node update. NWK Address=6574
	Line 1004: 2022-03-07 20:02:00.911 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - 8CF681FFFE2884D2: Node 6574 is not updated
	Line 1008: 2022-03-07 20:02:00.912 [DEBUG] [verter.ZigBeeConverterBatteryVoltage] - 8CF681FFFE2884D2: ZigBee attribute reports ZclAttribute [cluster=Power Configuration, id=33, name=Battery Percentage Remaining, dataType=UNSIGNED_8_BIT_INTEGER, lastValue=87, lastReportTime=Mon Mar 07 20:02:00 MST 2022, implemented=true]
	Line 1009: 2022-03-07 20:02:00.912 [DEBUG] [verter.ZigBeeConverterBatteryPercent] - 8CF681FFFE2884D2: ZigBee attribute reports ZclAttribute [cluster=Power Configuration, id=33, name=Battery Percentage Remaining, dataType=UNSIGNED_8_BIT_INTEGER, lastValue=87, lastReportTime=Mon Mar 07 20:02:00 MST 2022, implemented=true]
	Line 1010: 2022-03-07 20:02:00.912 [DEBUG] [e.transaction.ZigBeeTransactionQueue] - 8CF681FFFE2884D2: Added transaction to queue, len=1, transaction=ZigBeeTransaction [ieeeAddress=8CF681FFFE2884D2 queueTime=0, state=WAITING, sendCnt=0, command=DefaultResponse [Power Configuration: 0000/0 -> 6574/1, cluster=0001, TID=63, commandIdentifier=10, statusCode=SUCCESS]]
	Line 1010: 2022-03-07 20:02:00.912 [DEBUG] [e.transaction.ZigBeeTransactionQueue] - 8CF681FFFE2884D2: Added transaction to queue, len=1, transaction=ZigBeeTransaction [ieeeAddress=8CF681FFFE2884D2 queueTime=0, state=WAITING, sendCnt=0, command=DefaultResponse [Power Configuration: 0000/0 -> 6574/1, cluster=0001, TID=63, commandIdentifier=10, statusCode=SUCCESS]]
	Line 1011: 2022-03-07 20:02:00.912 [DEBUG] [converter.ZigBeeBaseChannelConverter] - 8CF681FFFE2884D2: Channel zigbee:device:7e7c171ea7:8cf681fffe2884d2:8CF681FFFE2884D2_1_batterylevel updated to 43
	Line 1011: 2022-03-07 20:02:00.912 [DEBUG] [converter.ZigBeeBaseChannelConverter] - 8CF681FFFE2884D2: Channel zigbee:device:7e7c171ea7:8cf681fffe2884d2:8CF681FFFE2884D2_1_batterylevel updated to 43
	Line 1011: 2022-03-07 20:02:00.912 [DEBUG] [converter.ZigBeeBaseChannelConverter] - 8CF681FFFE2884D2: Channel zigbee:device:7e7c171ea7:8cf681fffe2884d2:8CF681FFFE2884D2_1_batterylevel updated to 43
	Line 1012: 2022-03-07 20:02:00.912 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 8CF681FFFE2884D2: Updating ZigBee channel state zigbee:device:7e7c171ea7:8cf681fffe2884d2:8CF681FFFE2884D2_1_batterylevel to 43
	Line 1012: 2022-03-07 20:02:00.912 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 8CF681FFFE2884D2: Updating ZigBee channel state zigbee:device:7e7c171ea7:8cf681fffe2884d2:8CF681FFFE2884D2_1_batterylevel to 43
	Line 1012: 2022-03-07 20:02:00.912 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 8CF681FFFE2884D2: Updating ZigBee channel state zigbee:device:7e7c171ea7:8cf681fffe2884d2:8CF681FFFE2884D2_1_batterylevel to 43
	Line 1013: 2022-03-07 20:02:00.912 [DEBUG] [.zigbee.handler.ZigBeeIsAliveTracker] - IsAlive Tracker reset for handler with thingUID=zigbee:device:7e7c171ea7:8cf681fffe2884d2
	Line 1015: 2022-03-07 20:02:00.913 [DEBUG] [.zigbee.handler.ZigBeeIsAliveTracker] - IsAlive Tracker cancelled task for thingUID=zigbee:device:7e7c171ea7:8cf681fffe2884d2
	Line 1016: 2022-03-07 20:02:00.913 [DEBUG] [.zigbee.handler.ZigBeeIsAliveTracker] - IsAlive Tracker scheduled task for thingUID=zigbee:device:7e7c171ea7:8cf681fffe2884d2 in 14430 seconds
	Line 1020: 2022-03-07 20:02:01.680 [DEBUG] [transaction.ZigBeeTransactionManager] - Transaction complete: ZigBeeTransaction [ieeeAddress=8CF681FFFE2884D2 queueTime=1042, state=COMPLETE, sendCnt=1, command=DefaultResponse [Power Configuration: 0000/0 -> 6574/1, cluster=0001, TID=62, commandIdentifier=10, statusCode=SUCCESS]]
	Line 1022: 2022-03-07 20:02:01.680 [DEBUG] [e.transaction.ZigBeeTransactionQueue] - 8CF681FFFE2884D2: transactionComplete, state=COMPLETE, outstanding=0
	Line 1024: 2022-03-07 20:02:01.681 [DEBUG] [transaction.ZigBeeTransactionManager] - 6574/1: Sending ZigBeeTransaction [ieeeAddress=8CF681FFFE2884D2 queueTime=770, state=WAITING, sendCnt=0, command=DefaultResponse [Power Configuration: 0000/0 -> 6574/1, cluster=0001, TID=63, commandIdentifier=10, statusCode=SUCCESS]]
	Line 1034: 2022-03-07 20:02:02.721 [DEBUG] [transaction.ZigBeeTransactionManager] - Transaction complete: ZigBeeTransaction [ieeeAddress=8CF681FFFE2884D2 queueTime=1810, state=COMPLETE, sendCnt=1, command=DefaultResponse [Power Configuration: 0000/0 -> 6574/1, cluster=0001, TID=63, commandIdentifier=10, statusCode=SUCCESS]]
	Line 1036: 2022-03-07 20:02:02.721 [DEBUG] [e.transaction.ZigBeeTransactionQueue] - 8CF681FFFE2884D2: transactionComplete, state=COMPLETE, outstanding=0
	Line 1168: 2022-03-07 20:10:17.046 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 8CF681FFFE2884D2: Polling [zigbee:device:7e7c171ea7:8cf681fffe2884d2:8CF681FFFE2884D2_1_batteryalarm, zigbee:device:7e7c171ea7:8cf681fffe2884d2:8CF681FFFE2884D2_1_batterylevel, zigbee:device:7e7c171ea7:8cf681fffe2884d2:8CF681FFFE2884D2_1_dimmer, zigbee:device:7e7c171ea7:8cf681fffe2884d2:8CF681FFFE2884D2_1_batteryvoltage] channels...
	Line 1168: 2022-03-07 20:10:17.046 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 8CF681FFFE2884D2: Polling [zigbee:device:7e7c171ea7:8cf681fffe2884d2:8CF681FFFE2884D2_1_batteryalarm, zigbee:device:7e7c171ea7:8cf681fffe2884d2:8CF681FFFE2884D2_1_batterylevel, zigbee:device:7e7c171ea7:8cf681fffe2884d2:8CF681FFFE2884D2_1_dimmer, zigbee:device:7e7c171ea7:8cf681fffe2884d2:8CF681FFFE2884D2_1_batteryvoltage] channels...
	Line 1168: 2022-03-07 20:10:17.046 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 8CF681FFFE2884D2: Polling [zigbee:device:7e7c171ea7:8cf681fffe2884d2:8CF681FFFE2884D2_1_batteryalarm, zigbee:device:7e7c171ea7:8cf681fffe2884d2:8CF681FFFE2884D2_1_batterylevel, zigbee:device:7e7c171ea7:8cf681fffe2884d2:8CF681FFFE2884D2_1_dimmer, zigbee:device:7e7c171ea7:8cf681fffe2884d2:8CF681FFFE2884D2_1_batteryvoltage] channels...
	Line 1168: 2022-03-07 20:10:17.046 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 8CF681FFFE2884D2: Polling [zigbee:device:7e7c171ea7:8cf681fffe2884d2:8CF681FFFE2884D2_1_batteryalarm, zigbee:device:7e7c171ea7:8cf681fffe2884d2:8CF681FFFE2884D2_1_batterylevel, zigbee:device:7e7c171ea7:8cf681fffe2884d2:8CF681FFFE2884D2_1_dimmer, zigbee:device:7e7c171ea7:8cf681fffe2884d2:8CF681FFFE2884D2_1_batteryvoltage] channels...
	Line 1168: 2022-03-07 20:10:17.046 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 8CF681FFFE2884D2: Polling [zigbee:device:7e7c171ea7:8cf681fffe2884d2:8CF681FFFE2884D2_1_batteryalarm, zigbee:device:7e7c171ea7:8cf681fffe2884d2:8CF681FFFE2884D2_1_batterylevel, zigbee:device:7e7c171ea7:8cf681fffe2884d2:8CF681FFFE2884D2_1_dimmer, zigbee:device:7e7c171ea7:8cf681fffe2884d2:8CF681FFFE2884D2_1_batteryvoltage] channels...
	Line 1168: 2022-03-07 20:10:17.046 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 8CF681FFFE2884D2: Polling [zigbee:device:7e7c171ea7:8cf681fffe2884d2:8CF681FFFE2884D2_1_batteryalarm, zigbee:device:7e7c171ea7:8cf681fffe2884d2:8CF681FFFE2884D2_1_batterylevel, zigbee:device:7e7c171ea7:8cf681fffe2884d2:8CF681FFFE2884D2_1_dimmer, zigbee:device:7e7c171ea7:8cf681fffe2884d2:8CF681FFFE2884D2_1_batteryvoltage] channels...
	Line 1168: 2022-03-07 20:10:17.046 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 8CF681FFFE2884D2: Polling [zigbee:device:7e7c171ea7:8cf681fffe2884d2:8CF681FFFE2884D2_1_batteryalarm, zigbee:device:7e7c171ea7:8cf681fffe2884d2:8CF681FFFE2884D2_1_batterylevel, zigbee:device:7e7c171ea7:8cf681fffe2884d2:8CF681FFFE2884D2_1_dimmer, zigbee:device:7e7c171ea7:8cf681fffe2884d2:8CF681FFFE2884D2_1_batteryvoltage] channels...
	Line 1168: 2022-03-07 20:10:17.046 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 8CF681FFFE2884D2: Polling [zigbee:device:7e7c171ea7:8cf681fffe2884d2:8CF681FFFE2884D2_1_batteryalarm, zigbee:device:7e7c171ea7:8cf681fffe2884d2:8CF681FFFE2884D2_1_batterylevel, zigbee:device:7e7c171ea7:8cf681fffe2884d2:8CF681FFFE2884D2_1_dimmer, zigbee:device:7e7c171ea7:8cf681fffe2884d2:8CF681FFFE2884D2_1_batteryvoltage] channels...
	Line 1168: 2022-03-07 20:10:17.046 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 8CF681FFFE2884D2: Polling [zigbee:device:7e7c171ea7:8cf681fffe2884d2:8CF681FFFE2884D2_1_batteryalarm, zigbee:device:7e7c171ea7:8cf681fffe2884d2:8CF681FFFE2884D2_1_batterylevel, zigbee:device:7e7c171ea7:8cf681fffe2884d2:8CF681FFFE2884D2_1_dimmer, zigbee:device:7e7c171ea7:8cf681fffe2884d2:8CF681FFFE2884D2_1_batteryvoltage] channels...
	Line 1169: 2022-03-07 20:10:17.046 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 8CF681FFFE2884D2: Polling zigbee:device:7e7c171ea7:8cf681fffe2884d2:8CF681FFFE2884D2_1_batteryalarm
	Line 1169: 2022-03-07 20:10:17.046 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 8CF681FFFE2884D2: Polling zigbee:device:7e7c171ea7:8cf681fffe2884d2:8CF681FFFE2884D2_1_batteryalarm
	Line 1169: 2022-03-07 20:10:17.046 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 8CF681FFFE2884D2: Polling zigbee:device:7e7c171ea7:8cf681fffe2884d2:8CF681FFFE2884D2_1_batteryalarm
	Line 1171: 2022-03-07 20:10:17.047 [DEBUG] [e.transaction.ZigBeeTransactionQueue] - 8CF681FFFE2884D2: Added transaction to queue, len=1, transaction=ZigBeeTransaction [ieeeAddress=8CF681FFFE2884D2 queueTime=0, state=WAITING, sendCnt=0, command=ReadAttributesCommand [Power Configuration: 0000/0 -> 6574/1, cluster=0001, TID=--, identifiers=[62]]]
	Line 1171: 2022-03-07 20:10:17.047 [DEBUG] [e.transaction.ZigBeeTransactionQueue] - 8CF681FFFE2884D2: Added transaction to queue, len=1, transaction=ZigBeeTransaction [ieeeAddress=8CF681FFFE2884D2 queueTime=0, state=WAITING, sendCnt=0, command=ReadAttributesCommand [Power Configuration: 0000/0 -> 6574/1, cluster=0001, TID=--, identifiers=[62]]]
	Line 1173: 2022-03-07 20:10:17.047 [DEBUG] [transaction.ZigBeeTransactionManager] - 6574/1: Sending ZigBeeTransaction [ieeeAddress=8CF681FFFE2884D2 queueTime=0, state=WAITING, sendCnt=0, command=ReadAttributesCommand [Power Configuration: 0000/0 -> 6574/1, cluster=0001, TID=E9, identifiers=[62]]]
	Line 1180: 2022-03-07 20:10:27.047 [DEBUG] [transaction.ZigBeeTransactionManager] - Transaction complete: ZigBeeTransaction [ieeeAddress=8CF681FFFE2884D2 queueTime=10000, state=FAILED, sendCnt=1, command=ReadAttributesCommand [Power Configuration: 0000/0 -> 6574/1, cluster=0001, TID=E9, identifiers=[62]]]
	Line 1182: 2022-03-07 20:10:27.048 [DEBUG] [e.transaction.ZigBeeTransactionQueue] - 8CF681FFFE2884D2: transactionComplete, state=FAILED, outstanding=0
	Line 1183: 2022-03-07 20:10:27.048 [DEBUG] [e.transaction.ZigBeeTransactionQueue] - 8CF681FFFE2884D2: Added transaction to queue, len=1, transaction=ZigBeeTransaction [ieeeAddress=8CF681FFFE2884D2 queueTime=10001, state=WAITING, sendCnt=1, command=ReadAttributesCommand [Power Configuration: 0000/0 -> 6574/1, cluster=0001, TID=E9, identifiers=[62]]]
	Line 1183: 2022-03-07 20:10:27.048 [DEBUG] [e.transaction.ZigBeeTransactionQueue] - 8CF681FFFE2884D2: Added transaction to queue, len=1, transaction=ZigBeeTransaction [ieeeAddress=8CF681FFFE2884D2 queueTime=10001, state=WAITING, sendCnt=1, command=ReadAttributesCommand [Power Configuration: 0000/0 -> 6574/1, cluster=0001, TID=E9, identifiers=[62]]]
	Line 1185: 2022-03-07 20:10:27.049 [DEBUG] [transaction.ZigBeeTransactionManager] - 6574/1: Sending ZigBeeTransaction [ieeeAddress=8CF681FFFE2884D2 queueTime=10002, state=WAITING, sendCnt=1, command=ReadAttributesCommand [Power Configuration: 0000/0 -> 6574/1, cluster=0001, TID=E9, identifiers=[62]]]
	Line 1193: 2022-03-07 20:10:37.049 [DEBUG] [transaction.ZigBeeTransactionManager] - Transaction complete: ZigBeeTransaction [ieeeAddress=8CF681FFFE2884D2 queueTime=20002, state=FAILED, sendCnt=2, command=ReadAttributesCommand [Power Configuration: 0000/0 -> 6574/1, cluster=0001, TID=E9, identifiers=[62]]]
	Line 1195: 2022-03-07 20:10:37.050 [DEBUG] [e.transaction.ZigBeeTransactionQueue] - 8CF681FFFE2884D2: transactionComplete, state=FAILED, outstanding=0
	Line 1196: 2022-03-07 20:10:37.050 [DEBUG] [e.transaction.ZigBeeTransactionQueue] - 8CF681FFFE2884D2: transactionComplete exceeded max retries 2
	Line 1197: 2022-03-07 20:10:37.050 [DEBUG] [zigbee.transaction.ZigBeeTransaction] - Transaction cancelled: ZigBeeTransaction [ieeeAddress=8CF681FFFE2884D2 queueTime=20003, state=CANCELLED, sendCnt=2, command=ReadAttributesCommand [Power Configuration: 0000/0 -> 6574/1, cluster=0001, TID=E9, identifiers=[62]]]
	Line 1198: 2022-03-07 20:10:37.051 [DEBUG] [transaction.ZigBeeTransactionManager] - Transaction complete: ZigBeeTransaction [ieeeAddress=8CF681FFFE2884D2 queueTime=20003, state=CANCELLED, sendCnt=2, command=ReadAttributesCommand [Power Configuration: 0000/0 -> 6574/1, cluster=0001, TID=E9, identifiers=[62]]]
	Line 1199: 2022-03-07 20:10:37.051 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 8CF681FFFE2884D2: Polling zigbee:device:7e7c171ea7:8cf681fffe2884d2:8CF681FFFE2884D2_1_batterylevel
	Line 1199: 2022-03-07 20:10:37.051 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 8CF681FFFE2884D2: Polling zigbee:device:7e7c171ea7:8cf681fffe2884d2:8CF681FFFE2884D2_1_batterylevel
	Line 1199: 2022-03-07 20:10:37.051 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 8CF681FFFE2884D2: Polling zigbee:device:7e7c171ea7:8cf681fffe2884d2:8CF681FFFE2884D2_1_batterylevel
	Line 1201: 2022-03-07 20:10:37.051 [DEBUG] [e.transaction.ZigBeeTransactionQueue] - 8CF681FFFE2884D2: transactionComplete but not outstanding, state=CANCELLED, outstanding=0
	Line 1205: 2022-03-07 20:10:37.051 [DEBUG] [e.transaction.ZigBeeTransactionQueue] - 8CF681FFFE2884D2: Added transaction to queue, len=1, transaction=ZigBeeTransaction [ieeeAddress=8CF681FFFE2884D2 queueTime=0, state=WAITING, sendCnt=0, command=ReadAttributesCommand [Power Configuration: 0000/0 -> 6574/1, cluster=0001, TID=--, identifiers=[33]]]
	Line 1205: 2022-03-07 20:10:37.051 [DEBUG] [e.transaction.ZigBeeTransactionQueue] - 8CF681FFFE2884D2: Added transaction to queue, len=1, transaction=ZigBeeTransaction [ieeeAddress=8CF681FFFE2884D2 queueTime=0, state=WAITING, sendCnt=0, command=ReadAttributesCommand [Power Configuration: 0000/0 -> 6574/1, cluster=0001, TID=--, identifiers=[33]]]
	Line 1207: 2022-03-07 20:10:37.052 [DEBUG] [transaction.ZigBeeTransactionManager] - 6574/1: Sending ZigBeeTransaction [ieeeAddress=8CF681FFFE2884D2 queueTime=0, state=WAITING, sendCnt=0, command=ReadAttributesCommand [Power Configuration: 0000/0 -> 6574/1, cluster=0001, TID=EA, identifiers=[33]]]
	Line 1220: 2022-03-07 20:10:47.053 [DEBUG] [transaction.ZigBeeTransactionManager] - Transaction complete: ZigBeeTransaction [ieeeAddress=8CF681FFFE2884D2 queueTime=10001, state=FAILED, sendCnt=1, command=ReadAttributesCommand [Power Configuration: 0000/0 -> 6574/1, cluster=0001, TID=EA, identifiers=[33]]]
	Line 1222: 2022-03-07 20:10:47.053 [DEBUG] [e.transaction.ZigBeeTransactionQueue] - 8CF681FFFE2884D2: transactionComplete, state=FAILED, outstanding=0
	Line 1223: 2022-03-07 20:10:47.053 [DEBUG] [e.transaction.ZigBeeTransactionQueue] - 8CF681FFFE2884D2: Added transaction to queue, len=1, transaction=ZigBeeTransaction [ieeeAddress=8CF681FFFE2884D2 queueTime=10002, state=WAITING, sendCnt=1, command=ReadAttributesCommand [Power Configuration: 0000/0 -> 6574/1, cluster=0001, TID=EA, identifiers=[33]]]
	Line 1223: 2022-03-07 20:10:47.053 [DEBUG] [e.transaction.ZigBeeTransactionQueue] - 8CF681FFFE2884D2: Added transaction to queue, len=1, transaction=ZigBeeTransaction [ieeeAddress=8CF681FFFE2884D2 queueTime=10002, state=WAITING, sendCnt=1, command=ReadAttributesCommand [Power Configuration: 0000/0 -> 6574/1, cluster=0001, TID=EA, identifiers=[33]]]
	Line 1225: 2022-03-07 20:10:47.054 [DEBUG] [transaction.ZigBeeTransactionManager] - 6574/1: Sending ZigBeeTransaction [ieeeAddress=8CF681FFFE2884D2 queueTime=10002, state=WAITING, sendCnt=1, command=ReadAttributesCommand [Power Configuration: 0000/0 -> 6574/1, cluster=0001, TID=EA, identifiers=[33]]]
	Line 1263: 2022-03-07 20:10:57.054 [DEBUG] [transaction.ZigBeeTransactionManager] - Transaction complete: ZigBeeTransaction [ieeeAddress=8CF681FFFE2884D2 queueTime=20003, state=FAILED, sendCnt=2, command=ReadAttributesCommand [Power Configuration: 0000/0 -> 6574/1, cluster=0001, TID=EA, identifiers=[33]]]
	Line 1265: 2022-03-07 20:10:57.055 [DEBUG] [e.transaction.ZigBeeTransactionQueue] - 8CF681FFFE2884D2: transactionComplete, state=FAILED, outstanding=0
	Line 1266: 2022-03-07 20:10:57.055 [DEBUG] [e.transaction.ZigBeeTransactionQueue] - 8CF681FFFE2884D2: transactionComplete exceeded max retries 2
	Line 1267: 2022-03-07 20:10:57.055 [DEBUG] [zigbee.transaction.ZigBeeTransaction] - Transaction cancelled: ZigBeeTransaction [ieeeAddress=8CF681FFFE2884D2 queueTime=20004, state=CANCELLED, sendCnt=2, command=ReadAttributesCommand [Power Configuration: 0000/0 -> 6574/1, cluster=0001, TID=EA, identifiers=[33]]]
	Line 1268: 2022-03-07 20:10:57.055 [DEBUG] [transaction.ZigBeeTransactionManager] - Transaction complete: ZigBeeTransaction [ieeeAddress=8CF681FFFE2884D2 queueTime=20004, state=CANCELLED, sendCnt=2, command=ReadAttributesCommand [Power Configuration: 0000/0 -> 6574/1, cluster=0001, TID=EA, identifiers=[33]]]
	Line 1269: 2022-03-07 20:10:57.055 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 8CF681FFFE2884D2: Polling zigbee:device:7e7c171ea7:8cf681fffe2884d2:8CF681FFFE2884D2_1_batteryvoltage
	Line 1269: 2022-03-07 20:10:57.055 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 8CF681FFFE2884D2: Polling zigbee:device:7e7c171ea7:8cf681fffe2884d2:8CF681FFFE2884D2_1_batteryvoltage
	Line 1269: 2022-03-07 20:10:57.055 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 8CF681FFFE2884D2: Polling zigbee:device:7e7c171ea7:8cf681fffe2884d2:8CF681FFFE2884D2_1_batteryvoltage
	Line 1271: 2022-03-07 20:10:57.055 [DEBUG] [e.transaction.ZigBeeTransactionQueue] - 8CF681FFFE2884D2: transactionComplete but not outstanding, state=CANCELLED, outstanding=0
	Line 1275: 2022-03-07 20:10:57.056 [DEBUG] [e.transaction.ZigBeeTransactionQueue] - 8CF681FFFE2884D2: Added transaction to queue, len=1, transaction=ZigBeeTransaction [ieeeAddress=8CF681FFFE2884D2 queueTime=0, state=WAITING, sendCnt=0, command=ReadAttributesCommand [Power Configuration: 0000/0 -> 6574/1, cluster=0001, TID=--, identifiers=[32]]]
	Line 1275: 2022-03-07 20:10:57.056 [DEBUG] [e.transaction.ZigBeeTransactionQueue] - 8CF681FFFE2884D2: Added transaction to queue, len=1, transaction=ZigBeeTransaction [ieeeAddress=8CF681FFFE2884D2 queueTime=0, state=WAITING, sendCnt=0, command=ReadAttributesCommand [Power Configuration: 0000/0 -> 6574/1, cluster=0001, TID=--, identifiers=[32]]]
	Line 1277: 2022-03-07 20:10:57.056 [DEBUG] [transaction.ZigBeeTransactionManager] - 6574/1: Sending ZigBeeTransaction [ieeeAddress=8CF681FFFE2884D2 queueTime=0, state=WAITING, sendCnt=0, command=ReadAttributesCommand [Power Configuration: 0000/0 -> 6574/1, cluster=0001, TID=EC, identifiers=[32]]]
	Line 1328: 2022-03-07 20:11:07.056 [DEBUG] [transaction.ZigBeeTransactionManager] - Transaction complete: ZigBeeTransaction [ieeeAddress=8CF681FFFE2884D2 queueTime=10000, state=FAILED, sendCnt=1, command=ReadAttributesCommand [Power Configuration: 0000/0 -> 6574/1, cluster=0001, TID=EC, identifiers=[32]]]
	Line 1330: 2022-03-07 20:11:07.057 [DEBUG] [e.transaction.ZigBeeTransactionQueue] - 8CF681FFFE2884D2: transactionComplete, state=FAILED, outstanding=0
	Line 1331: 2022-03-07 20:11:07.057 [DEBUG] [e.transaction.ZigBeeTransactionQueue] - 8CF681FFFE2884D2: Added transaction to queue, len=1, transaction=ZigBeeTransaction [ieeeAddress=8CF681FFFE2884D2 queueTime=10001, state=WAITING, sendCnt=1, command=ReadAttributesCommand [Power Configuration: 0000/0 -> 6574/1, cluster=0001, TID=EC, identifiers=[32]]]
	Line 1331: 2022-03-07 20:11:07.057 [DEBUG] [e.transaction.ZigBeeTransactionQueue] - 8CF681FFFE2884D2: Added transaction to queue, len=1, transaction=ZigBeeTransaction [ieeeAddress=8CF681FFFE2884D2 queueTime=10001, state=WAITING, sendCnt=1, command=ReadAttributesCommand [Power Configuration: 0000/0 -> 6574/1, cluster=0001, TID=EC, identifiers=[32]]]
	Line 1333: 2022-03-07 20:11:07.057 [DEBUG] [transaction.ZigBeeTransactionManager] - 6574/1: Sending ZigBeeTransaction [ieeeAddress=8CF681FFFE2884D2 queueTime=10001, state=WAITING, sendCnt=1, command=ReadAttributesCommand [Power Configuration: 0000/0 -> 6574/1, cluster=0001, TID=EC, identifiers=[32]]]
	Line 1384: 2022-03-07 20:11:17.058 [DEBUG] [transaction.ZigBeeTransactionManager] - Transaction complete: ZigBeeTransaction [ieeeAddress=8CF681FFFE2884D2 queueTime=20002, state=FAILED, sendCnt=2, command=ReadAttributesCommand [Power Configuration: 0000/0 -> 6574/1, cluster=0001, TID=EC, identifiers=[32]]]
	Line 1386: 2022-03-07 20:11:17.059 [DEBUG] [e.transaction.ZigBeeTransactionQueue] - 8CF681FFFE2884D2: transactionComplete, state=FAILED, outstanding=0
	Line 1387: 2022-03-07 20:11:17.059 [DEBUG] [e.transaction.ZigBeeTransactionQueue] - 8CF681FFFE2884D2: transactionComplete exceeded max retries 2
	Line 1388: 2022-03-07 20:11:17.059 [DEBUG] [zigbee.transaction.ZigBeeTransaction] - Transaction cancelled: ZigBeeTransaction [ieeeAddress=8CF681FFFE2884D2 queueTime=20003, state=CANCELLED, sendCnt=2, command=ReadAttributesCommand [Power Configuration: 0000/0 -> 6574/1, cluster=0001, TID=EC, identifiers=[32]]]
	Line 1389: 2022-03-07 20:11:17.059 [DEBUG] [transaction.ZigBeeTransactionManager] - Transaction complete: ZigBeeTransaction [ieeeAddress=8CF681FFFE2884D2 queueTime=20003, state=CANCELLED, sendCnt=2, command=ReadAttributesCommand [Power Configuration: 0000/0 -> 6574/1, cluster=0001, TID=EC, identifiers=[32]]]
	Line 1391: 2022-03-07 20:11:17.059 [DEBUG] [e.transaction.ZigBeeTransactionQueue] - 8CF681FFFE2884D2: transactionComplete but not outstanding, state=CANCELLED, outstanding=0
13

It looks like it isn’t reporting anything other than it’s _1_dimmer channel, although in my .items file I have it defined as

Switch Switch_UL_TestSwitch "Tradfri Test Switch" {channel="zigbee:device:7e7c171ea7:8cf681fffe2884d2:8CF681FFFE2884D2_1_dimmer"}

I’ve also tried

Dimmer Switch_UL_TestSwitch "Tradfri Test Switch" {channel="zigbee:device:7e7c171ea7:8cf681fffe2884d2:8CF681FFFE2884D2_1_dimmer"}

But any rules based on ‘received update’ such as

rule "Ikea Switch changed"
when
    Item Switch_UL_TestSwitch received update
then
   do something
end

Do not seem to fire.

14

The log seems indeed odd to me.
It seems that somehow the battery channel works, but the dimmer one only appears once.
You should also actually see a log entry even without any rule, just by clicking the button as it should transmit the zigbee signal to the binding (I think, as mentioned, not using the binding).

It also seems the device is not on the bindings documentation list, though some other remotes still worked (?).
I can also only find posts talking about the remote with z2mqtt.

Will keep digging and report if I find anything else.

15

Very much appreciate your time and help on this one! It would be one thing to see logs that it’s firing like my other Zigbee sensors/switches but just nothing.

Would you happen to know if I ended up installing/setting up z2mqtt, if it could co-exist with the regular zigbee binding and both share the same zigbee adapter? Or is it exclusive to one or the other?

I’d be happy to tinker with it if it doesn’t take down the regular zigbee binding, since I know I have to point it to the com port. Just don’t want to install it, configure it, and find it kills the regular binding from communicating with the zigbee dongle.

Thanks, will look forward to an update or anything you’d like me to try out. :slight_smile:

–Edit Nov 2022–

I gave up on the regular zigbee binding. My GoControl HUSBZB-1 adapter’s Zigbee side started malfunctioning (zwave was still fine), certain devices stopped reporting, initially thinking it may have been battery related but more stopped working. Ended up trying to re-pair devices but it was getting really finicky, thinking it may have been a glitch with OpenHAB, nothing seemed to work, even a re-install, so I ordered a new Zigbee adapter Sonoff ZBDongle-P and started fresh with zigbee2mqtt.

I regret not using zigbee2mqtt earlier now, it’s fantastic. All of my Sonoff zigee devices now report battery level, performance actually seems like they respond to events faster, and I have a heap of extra functionality I didn’t before, like my Sonoff SNZB-01 Single-Button remote can now report Single/Double/Long presses, vs just single presses with the old zigbee binding.

My Philips Motion Sensors now have a bunch of extra configuration exposed such as sensitivity, timeout, and ability to enable/disable the LED via zigbee2mqtt as well

Glad the issues happened to me because I couldn’t be happier with all this extra functionality after moving over to zigbee2mqtt.

Just leaving this update as a note for anyone having issues with the zigbee binding, it’s worth switching to zigbee2mqtt, the configuration is a little bit of a pain initially, but it’s worth it. And of course I have the full functionality from the Ikea Tradfri remotes too, On / Off / Brightness Up / Brightness Down / Brightness Stop from the 2 button remote. Too bad I returned the 3 extras when I couldn’t get the 1 to work, now I have to go buy some more.

16

I am also using zigbee2mqtt, but I cannot make it work with IKEA E2001/E2002 control via MQTT | Zigbee2MQTT

I pair the device, and use automatic discovery to create the item

UID: mqtt:homeassistant_zigbee2mqtt_5F0xb4e3f9fffeb358b5:mqtt-broker:interruptor5
label: interruptor5
thingTypeUID: mqtt:homeassistant_zigbee2mqtt_5F0xb4e3f9fffeb358b5
configuration:
  topics:
    - update/0xb4e3f9fffeb358b5/update
    - sensor/0xb4e3f9fffeb358b5/battery
    - sensor/0xb4e3f9fffeb358b5/action
    - binary_sensor/0xb4e3f9fffeb358b5/update_available
    - sensor/0xb4e3f9fffeb358b5/linkquality
    - sensor/0xb4e3f9fffeb358b5/update_state
  basetopic: homeassistant
bridgeUID: mqtt:broker:mqtt-broker

I create an item for channel action, and I can create a rule to be triggered when item receives a command (aka button is pressed); but I don’t know how to get which button/action is pressend; when checking ‘myItem.state’ I get nothing.

I have defined the action channel as a point:string

imatge
imatge725×406 33.9 KB

I have jinja, json and map transformations; don’t know if it helps.

How can I make it work?

17

I have set this up manually. Here is my Thing config.

UID: mqtt:topic:swHallwayRemote
label: Hallway remote
thingTypeUID: mqtt:topic
configuration: {}
bridgeUID: mqtt:broker:MosquittoMqttBroker
channels:
  - id: update_available
    channelTypeUID: mqtt:switch
    label: Update available
    description: null
    configuration:
      retained: false
      postCommand: false
      formatBeforePublish: "%s"
      stateTopic: zigbee2mqtt/swHallwayRemote/update_available
      off: "false"
      on: "true"
  - id: battery
    channelTypeUID: mqtt:number
    label: Battery level
    description: null
    configuration:
      retained: false
      postCommand: false
      step: 1
      formatBeforePublish: "%s"
      stateTopic: zigbee2mqtt/swHallwayRemote/battery
  - id: linkquality
    channelTypeUID: mqtt:number
    label: Link quality
    description: null
    configuration:
      retained: false
      postCommand: false
      step: 1
      formatBeforePublish: "%s"
      stateTopic: zigbee2mqtt/swHallwayRemote/linkquality
  - id: action
    channelTypeUID: mqtt:string
    label: Action
    description: null
    configuration:
      retained: false
      postCommand: false
      formatBeforePublish: "%s"
      stateTopic: zigbee2mqtt/swHallwayRemote/action
18

Thanks, I will check as soon as I can.

I am starting to lose faith in automatic thing detection with zigbee2mqtt :frowning:
(Adding ikea switch using zigbee2mqtt miss some channels)

19

I’m not using the automatic detection anymore, but noticed the same. Cause is likely the relevant topics only get created when posted to, ie when all the options of a device have been passed through zigbee2mqtt.

My way of working was to first switch all the options(either physically when a button, or via interface when it’s a switchable component) after which a scan on OH revealed the other channels as well.

Now when adding components I just use a previously added component of same type as a base and adjust accordingly.

20

It worked. Thanks a lot!

To make it work with automatic detection, should a patch be sent to openhab or zigbee2mqtt?