Cant pair IKEA Tradfri ON/OFF Switch E1743

[fabian3dprint]

Bug Report

What happened

I cant pair it with zigbee2mqtt. I try 2 different CC2531 and 2 different systems with new software. I Cant pari it. If I use the debug funktion and i try pairing, nothing is showing me that im trying to pair.

I have 2 ON/OFF Switches and both can connect to the IKEA Gateway and can connect with the Zigbee Binding from OpenHab. But cant connect with zigbee2mqtt. Any Ideas i can try?

What did you expect to happen

That it pair or just show in the debug "log" that im trynig to pair.

Debug Info

zigbee2mqtt version: CC2531 firmware version:1.6.0

[lolorc]

I paired 2 of them 2 days ago, I followed the pairing instructions and it worked, but I had to move the switches very near to the coordinator, it didn't worked when the switch was 2 meters away. (but still, my debug logs were showing them trying to pair)

I'm using the dev branch.

can't find a way to bind them to my new ikea bulbs but that's another story :) (oh I guess I have to bind them very close to the bulb, will try this evening)

[fabian3dprint]

Thank you for your fast replay.

I hold the Buttons 2cm away from the coordinator but it didn't worked. Any other tips?

[lolorc]

and still no log entries concerning your switches ? I see you're running 1.6, you might want to try dev version with herdsman edit: i'm still not been able to bind a E1743 switch to an ikea bulb, I guess there's some trick with the groupid to do.

[fabian3dprint]

OK I tryed this https://www.zigbee2mqtt.io/how_tos/how-to-switch-to-dev-branch.html and try to pair agin, but no chance. How exactly do you connect it? Is the link the right way to change to dev version?

Im sorry men. That sounds not good.

This is my starting log:

zigbee2mqtt@1.6.0 start /opt/zigbee2mqtt node index.js

zigbee2mqtt:info 2019-10-24T20:39:37: Logging to directory: '/opt/zigbee2mqtt/data/log/2019-10-24.22-39-37' zigbee2mqtt:debug 2019-10-24T20:39:37: Loaded state from file /opt/zigbee2mqtt/data/state.json zigbee2mqtt:info 2019-10-24T20:39:38: Starting zigbee2mqtt version 1.6.0 (commit #a813663) zigbee2mqtt:info 2019-10-24T20:39:38: Starting zigbee-herdsman... zigbee2mqtt:debug 2019-10-24T20:39:38: Using zigbee-herdsman with settings: '{"network":{"panID":6754,"extenedPanID":[221,221,221,221,221,221,221,221],"channelList":[11],"networkKey":"HIDDEN"},"databasePath":"/opt/zigbee2mqtt/data/database.db","backupPath":"/opt/zigbee2mqtt/data/coordinator_backup.json","serialPort":{"baudRate":115200,"rtscts":true,"path":"/dev/ttyACM0"}}' zigbee2mqtt:info 2019-10-24T20:39:39: zigbee-herdsman started zigbee2mqtt:info 2019-10-24T20:39:39: Coordinator firmware version: '{"type":"zStack12","meta":{"transportrev":2,"product":0,"majorrel":2,"minorrel":6,"maintrel":3,"revision":20190608}}' zigbee2mqtt:debug 2019-10-24T20:39:39: Zigbee network parameters: {"panID":6754,"extendedPanID":"0xdddddddddddddddd","channel":11} zigbee2mqtt:info 2019-10-24T20:39:39: Currently 0 devices are joined: zigbee2mqtt:warn 2019-10-24T20:39:39: permit_join set to true in configuration.yaml. zigbee2mqtt:warn 2019-10-24T20:39:39: Allowing new devices to join. zigbee2mqtt:warn 2019-10-24T20:39:39: Set permit_join to false once you joined all devices. zigbee2mqtt:info 2019-10-24T20:39:39: Zigbee: allowing new devices to join. zigbee2mqtt:info 2019-10-24T20:39:39: Connecting to MQTT server at mqtt://broker.mqttdashboard.com zigbee2mqtt:info 2019-10-24T20:39:39: Connected to MQTT server zigbee2mqtt:info 2019-10-24T20:39:39: MQTT publish: topic 'fabian/zigbee/bridge/state', payload 'online' zigbee2mqtt:info 2019-10-24T20:39:39: MQTT publish: topic 'fabian/zigbee/bridge/config', payload '{"version":"1.6.0","commit":"a813663","coordinator":{"type":"zStack12","meta":{"transportrev":2,"product":0,"majorrel":2,"minorrel":6,"maintrel":3,"revision":20190608}},"log_level":"debug","permit_join":true}

[lolorc]

hi,

what's wrong ? I can't see the issue you're having in this log ? You might want to upgrade your fw to the source routing one, but I don't really know if this is needed, I'm basing my comments on the other github issues, I'm using a cc2652r on my side

[fabian3dprint]

With this log i want To Show That there is ne pairing.

[lolorc]

looks like you've lost the pairing while upgrading, what about trying to pair the e1743 switch ?

[fredrikgk]

What do you do on the switch to initiate the pairing?

[sjorge]

I managed to get mine paired after 3 attempts, I have to keep clicking the on/off button to keep the device awake during the interview process. Not had much lock with binding bulbs to it though :(

zigbee2mqtt:info  2019-11-02T10:50:13: Successfully bound cluster 'genOnOff' from '0x14b457fffeca351b' to 'bedroom/night_light'
zigbee2mqtt:info  2019-11-02T10:50:13: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"device_bind","message":{"from":"0x14b457fffeca351b","to":"bedroom/night_light","cluster":"genOnOff"}}'
zigbee2mqtt:info  2019-11-02T10:50:14: MQTT publish: topic 'zigbee2mqtt/0x14b457fffeca351b', payload '{"linkquality":52,"click":"on"}'
zigbee2mqtt:info  2019-11-02T10:50:15: Successfully bound cluster 'genLevelCtrl' from '0x14b457fffeca351b' to 'bedroom/night_light'
zigbee2mqtt:info  2019-11-02T10:50:15: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"device_bind","message":{"from":"0x14b457fffeca351b","to":"bedroom/night_light","cluster":"genLevelCtrl"}}'

Seems OK (I unbound the coordinator first) but the bulbs doesn't do anything. Will play with it some more.

[sjorge]

Good news, I got it to work.

• pair device (keep clicking on/off alternating until interview is complete, might take a few tries)
• create a group with id 99
• add lamps to group 99 < works fine >
• remove lamps from group 99
• unbind group 99
• delete group 99
• create group 123
• add lamp to group 123 (tried both trådfri and hue)
• bind group 123 to remote < works fine with lamps in group 123 >

[lolorc]

I also managed to pair with group 99 created, I just unbound switch from 99. (didn't add/remove bulb to/from 99, didn't not remove the group)

[fabian3dprint]

Thx sjorge. I tryed but nothing is showed in the log. How log did you pressed the pair button?

[sjorge]

I counted to 4 and then pressed the on or off button. I think the pairing usually fails because the remote goes back to sleep before the interview is complete.

If you spam the button it also does not seem to complete the interview process either.

Also I don't think creating the group 99 is needed when using dev but I am not sure, would be nice of @Koenkk could onfirm that.

[Koenkk]

In the dev branch the remote is not added to a group anymore indeed and should work out-of-the-box.

[sjorge]

Nice, that would also explain my failed unbind's for that group.

So we can just bind the group we want immediately?

[Koenkk]

Yes (as it is not bound to anything by default). HOWEVER when upgrading from a zigbee2mqtt 1.6 installation you need to do this, zigbee2mqtt 1.6 bound it to the group.

To start fresh once on the dev branch, repair (factory reset) the device to let it forget its bindings.

[sjorge]

OK, than that mirrors my experience yesterday... I punted a lot on trying to unbind the group that was never bound to begin with.

[fabian3dprint]

I installed now version 1.7.1 and still not able to pair. I dont know what im doing wrong. I tryed this instruction https://www.zigbee2mqtt.io/devices/E1743.html and try many other paring methodes, but nothing seams to work.

[fabian3dprint]

OK it works now. I dont know how but after a couple of restarts i can pair it.

1. 4 times press the connect button
2. wait until the lights stop flashing
3. light start glowing
4. wait until the light stopo glowing

now they are paired

[Alestrix]

Hi @sjorge

• unbind group 99

How did you unbind a group? I can see in the docs how to add/remove devices to/from a group and how to bind/unbind one device to another, but how do you unbind from a group?

I can't get the Tradfri switch to work. It pairs fine (provided "interview successful" means that pairing was successful), but I cannot see any state updates when pressing on/off. I do not intent to bind it to some other device or group, only to use it as a switch in my Home Automation setup.

Regards Alex

[sjorge]

I create a group with ID 99, without devices.

Then I used the binding docs to unbind the group from the remote.

~ sjorge

On 29 Dec 2019, at 10:58, Alestrix notifications@github.com wrote:

 Hi @sjorge

unbind group 99 How did you unbind a group? I can see in the docs how to add/remove devices to/from a group and how to bind/unbind one device to another, but how do you unbind from a group?

I can't get the Tradfri switch to work. It pairs fine (provided "interview successful" means that pairing was successful), but I cannot see any state updates when pressing on/off. I do not intent to bind it to some other device or group, only to use it as a switch in my Home Automation setup.

Regards Alex

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

[Alestrix]

I create a group with ID 99, without devices. Then I used the binding docs to unbind the group from the remote.

Thanks for the info @sjorge , helped me to get slightly farther (didn't fail with "unknown group" this time), but it failed to unbind the switch from the group and I still cannot see switch state changes in the logs or MQTT. I guess I'll have to open another issue.

[Alestrix]

Just fyi, after upgrading the controller firmware to the current version, everything works for me.