Impossible to pair eWelink zigbee devices

Configuration Zigbee
1

I have to say in advance that I know I’m doing something wrong, but I can’t figure what.

I have bought some cheapo AE zigbee devices:

  • Ewelink smart A60 bulb
  • Ewelink smart GU10 bulb
  • Smart button ZB-K1

BUT I didn’t notice during the purchase that the “eWelink” thingy could become a problem. In fact, I didn’t notice at all, I just read “zigbee” and that was good enough for me. So, as you might imagine by now, I’m being uncapable to pair this devices to my HAOS instalation. Of course, I’m doing it accordingly to the manual, in pairing “breathe” mode.
My ZB dongle is a Silicon Labs EFR32MG21, updated today to latest firmware, you know, just in case. No luck.
The rest of my system is the usual, ZB2MQTT, more than 25 zigbee devices beautifuly running. So far so good for now.

I’m beginning to suspect that it might be not possible to pair this damn ewelink devices just out-of-the-box. The case is that in the article coments many guys refer to this devices as “Perfectly working in my HA”, which is very confusing.

FYI, I’m trying to avoid any eWelink app and cloud for now, privacy matters to me.

Many thanks for the help in advance, and regards.

2

Can’t see any of those in the Z2M devices list. Have you looked at their “new devices” instructions?

3

I didn’t thought about that as far as many people, in the coments of the Aliexpress item description, afirm that has been able to integrate the devices in their Home Assistant systems.

Because of that I guessed that it’s some kind of bad configuration on my side.
Anyway, it’s very interesting your comment, and I’m looking on it for sure. Your link says that ALL the zigbee devices can be connected (but not necessarily operated), so I’ll try that approach, and maybe I can contribute with some new devices.

In the meanwhile, I’ve updated the zb dongle driver to ember, because the log is empty except for some info about that driver regarding to my recent update of the dongle firmware. After that, the situation remains the same.

My next move is dig into the logs and try get some info about why it can’t connect at all.

4

Did you manage to connect to the devices eventually? Can’t seem to interview the devices as well.

5

Did you figure this out?

I got these (the Zigbee 18W version) and also getting the Unsupported error when trying to interview.

What’s frustrating is I bought these a few months ago and they worked just fine - same seller and everything.

6

Update: of the 15 or so I bought, about 1/3 will go into pairing mode.

If it helps, here’s the external definition:

const m = require(‘zigbee-herdsman-converters/lib/modernExtend’);

const definition = {
zigbeeModel: [‘CK-BL702-AL-01(7009_Z102LG03-1)’],
model: ‘CK-BL702-AL-01(7009_Z102LG03-1)’,
vendor: ‘eWeLink’,
description: ‘Automatically generated definition’,
extend: [m.light({“colorTemp”:{“range”:[142,500]},“color”:{“modes”:[“xy”,“hs”],“enhancedHue”:true}})],
meta: {},
};

module.exports = definition;

7

That bulb is already supported in Z2M, but the manufacturer is listed as Tuya. It’s a quite common occurrence and all you have to do is raise a support request in the Z2M Github to have eWeLink listed as a whitelabel for the device.

8

Ive also just got the buttons (zb-k1), managed to add them to HA but they don’t appear in automation actions like others do:

1000095797
10000957971440×2839 160 KB

1000095798
10000957981440×2839 206 KB

Anyone any tips? Tempted to just stick with the Sonoff SNZP-01P (Button 1 in the images)

9

Try pressing the button once (and maybe restart HA after that). Most times, that’s enough to get the event to show up in the automation.

If that doesn’t work, you will need to use an event trigger. Go to Dev tools > Events, and enter zha_event > Start listening. Pressing the button should fire an event which you can use in your automations.

1 Like
10

I also came across this cheap button on AliExpress. I ordered one. It appears as CK-TLSR8656-SS5-01(7000) by eWeLink on my device, but the box says zb-k1.

Based on ShadowFist’s post, I managed to figure out that it can generate three types of events (single click → toggle, double click → “on”, long press → “off”). Based on this, I was able to create an automation trigger for it.

image
image1082×812 24.1 KB

You can find your device’s uniqe_id here.

image
image943×677 19.8 KB

11

Hi @gyandor, I have the same problem with these button.
I found the unique_id in the listen section, but I dont’ understand what is the section in the first image, or how to go foward for obtain an action when I push the button…
Sorry for my ignorance.
Thanks for any advice!