Unable to pair battery powered Zemismart Chain Roller Shades Driver M515EGBZTN in v2.10.1

[PhilipsGorniczy]

Hello

I am unable to properly pair Zemismart Chain Roller Shades Driver M515EGBZTN on v2.10.1 and v2.10.2
In the release notes for v2.10.1 it was marked as supported, but pairing does not complete. A new device appears in Deconz GUI, but nothing appears in Phoscon.
I have searched and read previous issues - most people were able to pair it and see it from HomeAssistant. Mine does not show up anywhere.
Is it supposed to work, or we just getting multiple devices under the same name, model and manufacturer and this one is not supported?

Device

• Product name: Zemismart M515EGBZTN
• Manufacturer: _TZE200_xuzcvlku
• Model identifier: TS0601
• Device type : Cover

Screenshots

Basic

###Node

[Smanar]

I don't remember if the device is visible in phoscon.
Have you tried to include it 2 time, and without deleting anything between both ?

[PhilipsGorniczy]

Yes, both times as a light.

[Smanar]

Can you share the log during inclusion ?
You can have them in deconz (deconz/help/log with "info" and "info_l2".

To make it easy

• start logging
• in phoscon take "add new light"
• in deconz read basic attribute (cluster 0x0000, button "read", it need to fill the table)

It will trigger an inclusion.

[PhilipsGorniczy]

Weird thing is now happening. I found old Conbee I and I have spare PC, so I decided to do debug on separate zigbee network.

First try was unsuccessful. After that when I start up deconz the zemistmart driver appears even without pairing:

When I try to delete it it comes back. I tried to pair it again, but for some reason I get:
17:16:39:595 Node 0x5C0272FFFEECC56D is known by 1 neighbors, last seen 3 s

Full log attached.
zemismartmotor.txt

[PhilipsGorniczy]

I managed to clean up the entry - I did full gateway reset.
Then started dumping logs and tried to add the driver to deconz.
Log from that attached:
zemismartmotor2.txt

[Smanar]

On your capture the device is not yet included, miss a circle on the node.

Remember making 2 inclusions

17:37:21:045 Tuya debug 7 : Missing manufacture name for 0x5c0272fffeecc56d
17:37:21:045 Tuya debug 7 : Missing manufacture name, till missing in DB.

You can have thoses logs only on first one, because on the second one the value is on the DB.

[PhilipsGorniczy]

Ok, I retried.

1. I reset the gateway and restarted deconz container.
2. I started "Add new light" (I set it for 10 MINS)
3. State after first pairing:
   
   Cluster info got populated by then.
4. Second pairing (light search is still active) -> after 18:10:58 from logs
5. Nothing changed.
6. Third attempt. Still nothing. In the logs:

18:12:31:691 	asdu: 89a9246dc5ecfeff72025c80
18:12:31:692 unknown node 0x5C0272FFFEECC56D (0x24A9), lqi: 183
18:12:31:692 0xBD2E nwk changed to 0x24A9
18:12:31:693 APS-DATA.indication from child 0x24A9
18:12:31:694 ZDP device announce: 0x5C0272FFFEECC56D, 0x24A9, 0x80
18:12:31:695 FP indication 0x0000 / 0x0013 (0x5C0272FFFEECC56D / 0x24A9)
18:12:31:695                       ...     (0x5C0272FFFEECC56D / 0xAE7A)
18:12:31:695 device announce 0x5C0272FFFEECC56D (0x24A9) mac capabilities 0x80
18:12:31:696 FP indication 0x0000 / 0x0013 (0x5C0272FFFEECC56D / 0x24A9)
18:12:31:696                       ...     (0x5C0272FFFEECC56D / 0xAE7A)
18:12:31:696 device announce 0x5C0272FFFEECC56D (0x24A9) mac capabilities 0x80
18:12:31:755 MAC Poll 0x02 0x24A9, life time: 4294967295 sec, dev timeout: 4294967295 sec
18:12:31:757 CTRL skip polling while permit join is set

And the same. Device did not pair fully.
Log:
zemismartmotor3.txt

Is there some mistake in my understanding how to pair it?

[Smanar]

If I add some debug line in the code, are you able to compile it to test something ? (just need a linux machine)

[PhilipsGorniczy]

Yes, no problem. I have MiniPC with Ubuntu 20.04. I can run deconz without docker, straight on the OS.

[Smanar]

Nice, I have asked some help (because you are the third one with similar issue), if I haven't a way, I will make you a special version for tommorow.

[andys73]

Hello,
I have the exact issue with another device, a switch from Moes / ZTS-EU3-W (3 Gang)...

It does not pair at all but I can see it in VNC. I have tried to remove it and add it several times..

I can try the special version too :)

[Smanar]

@andys73 your device is a new one, pls make a new issue, will take some time, because your device use a new mac adress range and have the same cluster than TRV #4401 so need to find a way to reconize it.

@PhilipsGorniczy I think I have find the problem
The device is battery one, but there is no sensor created for it.
So when the light part check for the device, it can't use the sensor entry.

So I see 2 solutions.

• create a battery sensor, and this will be usefull.
• include the device using deconz

To include using deconz

• on phoscon : add new light
• on deconz read basic attribute 2 time, cluster 0x0000, button read, it need to fill the table.

[PhilipsGorniczy]

Thanks @Smanar !

Is there an additional step to create battery sensor?

I did those steps:

To include using deconz

    on phoscon : add new light
    on deconz read basic attribute 2 time, cluster 0x0000, button read, it need to fill the table.

nothing changes. Still the same errors.

[PhilipsGorniczy]

More details what exactly I do:

1. First pairing (reseting the device to join zigbee) - table is empty:
   
   After clicking read first time:
   
   After clicking read second time:
   
   Now the second pairing (reseting the device to join zigbee). And now it gets stuck again:

deconz    | 14:45:59:893 skip device discovery while end devices is added
deconz    | 14:46:00:133 Node 0x5C0272FFFEECC56D is known by 1 neighbors, last seen 8 s
deconz    | 14:46:00:373 skip device discovery while end devices is added
deconz    | 14:46:00:613 Node 0x5C0272FFFEECC56D is known by 1 neighbors, last seen 8 s

Logs:
zemismart_1403.txt

[PhilipsGorniczy]

By the way, this device should be already added via this PR:
https://github.com/dresden-elektronik/deconz-rest-plugin/pull/4274/files

Does it mean, that Zemismart is shipping different devices under name _TZE200_xuzcvlku?

[Smanar]

No reset.
just set phoscon in permit join (add new light) and read basic attribute on deconz (2 time)

[PhilipsGorniczy]

Tried that. Did not help.
Logs:
zemismart_1403_3.txt

Phoscon still empty. API also shows only the coordinator:

{"1":{"etag":"1349c37a58a930f2503cff2214d6d2df","hascolor":false,"lastannounced":null,"lastseen":"2021-03-14T15:03Z","manufacturername":"dresden elektronik","modelid":"ConBee","name":"Configuration tool 1","state":{"reachable":true},"swversion":null,"type":"Configuration tool","uniqueid":"00:21:2e:ff:ff:04:09:82-01"}}

Sensor was not created. In sensor there is only the default day/night sensor:

{"1":{"config":{"configured":true,"on":true,"sunriseoffset":30,"sunsetoffset":-30},"etag":"eb3da059e4411b3fe693ae07095a3f20","manufacturername":"Philips","modelid":"PHDL00","name":"Daylight","state":{"dark":false,"daylight":true,"lastupdated":"2021-03-14T15:00:47.278","status":170,"sunrise":"2021-03-14T04:57:25","sunset":"2021-03-14T16:43:57"},"swversion":"1.0","type":"Daylight","uniqueid":"00:21:2e:ff:ff:04:09:82-01"}}

[Smanar]

Still nothing in your log, I realy don't understand, no new inclusion triggered.

I will make the battery device creation, give me 1 h

[Smanar]

Can you try this modification ?

You have the procedure here https://github.com/dresden-elektronik/deconz-rest-plugin#install-deconz-development-package-optional-linux-only
So for you

sudo apt install deconz-dev
git clone --branch covering_7 https://github.com/Smanar/deconz-rest-plugin.git
cd deconz-rest-plugin
qmake && make
sudo cp ../libde_rest_plugin.so /usr/share/deCONZ/plugins

With this code you will have a new sensor for battery, and the light part will be able to use it for light device creation.

[PhilipsGorniczy]

Ok, so I installed xfce on the LAB box. Then I complied the code, accordingly to the instruction.
md5 after the compilation.
91be7fd9199f694a78f5fbde39d82b81 /usr/share/deCONZ/plugins/libde_rest_plugin.so

I was able to start the gui via vnc and start deconz app. Phoscon is also up.
I reset the gateway and then started add light process - for the first time it did not work.
I changed the light search duration to 10mins and restarted the process.

I was able to get the driver added to deconz. A the beginning cluster 0x0000 was empty. I clicked read two times.

And nothing much more happened. Still no sensors available.
Log:
deconzlog.txt

[PhilipsGorniczy]

Some more verbose debug from second attempt:
secondattempt.txt

In the logs there is mention of battery entitiy:

16:50:12:306 HTTP API GET /api/12D42A5129/sensors/new - 10.0.0.121
16:50:12:307 ApiMode: 0
16:50:12:307 {"2":{"name":"Battery 2"},"lastscan":"active"}
16:50:12:710 enqueue event config/localtime for /config/
16:50:12:711 APS-DATA.request id: 10, addrmode: 0x03, addr: 0x00212effff040982, profile: 0x0000, cluster: 0x0033, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
16:50:12:712 Mgmt_Bind_req id: 10 to 0x00212EFFFF040982 send
16:50:12:762 Node 0x5C0272FFFEECC56D is known by 1 neighbors, last seen 0 s
16:50:12:780 APS-DATA.confirm id: 10, status: 0x00 SUCCESS
16:50:12:780 APS-DATA.confirm request id: 10 -> confirmed, timeout 1615740612
16:50:12:806 HTTP client hdr detected:
GET /api/12D42A5129/sensors/new HTTP/1.1

[PhilipsGorniczy]

Actually new sensor is visible via api:

{"1":{"config":{"configured":false,"on":true,"sunriseoffset":30,"sunsetoffset":-30},"etag":null,"manufacturername":"Philips","modelid":"PHDL00","name":"Daylight","state":{"dark":null,"daylight":null,"lastupdated":"none","status":null},"swversion":"1.0","type":"Daylight","uniqueid":"00:21:2e:ff:ff:04:09:82-01"},"2":{"config":{"on":true,"reachable":true},"ep":1,"etag":"b841b1c9cf6eed1fba80a6cecf15fac9","lastseen":"2021-03-14T16:52Z","manufacturername":"_TZE200_xuzcvlku","modelid":"TS0601","name":"Battery 2","state":{"battery":null,"lastupdated":"none"},"type":"ZHABattery","uniqueid":"5c:02:72:ff:fe:ec:c5:6d-01-ef00"}}

Yay!
I will check whether I can see the device in Homeassistant.

[Smanar]

When you include a tuya device , for light one, the code search for the manufacture name.

• in the deconz app > not working for you
• in the sensor database

As you have the battery sensor, I think it will help the API to reconize it.

[PhilipsGorniczy]

Unfortunately, new sensor is visible only from deconz api via call:
`curl -X GET -i '10.0.0.125/api/KEY/sensors'
Lights endpoint does not show any new lights:

{"1":{"etag":"232b0008fee1d8da6aa4c6666d8ecea4","hascolor":false,"lastannounced":null,"lastseen":"2021-03-14T17:03Z","manufacturername":"dresden elektronik","modelid":"ConBee","name":"Configuration tool 1","state":{"reachable":true},"swversion":null,"type":"Configuration tool","uniqueid":"00:21:2e:ff:ff:04:09:82-01"}}

[Smanar]

If I m right on log starting by "Tuya debug 7" the code need to find a manufacture name.
And don't delete the battery sensor.

[Smanar]

Have you try a last inclusion "add new light" ?

On previous log you had

17:37:21:045 Tuya debug 7 : Missing manufacture name for 0x5c0272fffeecc56d
17:37:21:045 sql exec SELECT manufacturername FROM nodes WHERE mac LIKE '5c:02:72:ff:fe:ec:c5:6d%' COLLATE NOCASE
17:37:21:045 Tuya debug 7 : Missing manufacture name, till missing in DB.

But now you have the battery sensor, so the API will found a manufacture name and be able to use it.

[Smanar]

Have find a possible issue, can you try this branch pls

sudo apt install deconz-dev
git clone --branch tuya_14 https://github.com/Smanar/deconz-rest-plugin.git
cd deconz-rest-plugin
qmake && make
sudo cp ../libde_rest_plugin.so /usr/share/deCONZ/plugins

[GreyEarl]

@Smanar Today I received my Zemismart and it's the M515EGBZTN one. Can I try the above branch without loosing my current setup , or is it specifically meant for the other user?

[mhin76]

Hi all. I have a similar issue with my Zigbee. I had a nice network with several Xiaomi temp and door sensors (and others). after suddenly loosing one door sensor and not able to add it again (it worked for several days but trying to add it I only get in deconz v2.10.4 the short 0x ID but nothing in Phoscon) I resetted the gateway. now I cannot add anymore any of the Xiaomi temp nor door sensor. all other lights, motion sensor, plugs work. I tried differet Conbee firmwares. no luck. will try the approach written above and hope it will work

[Smanar]

I have a similar issue with my Zigbee

"Similar", this issue is about Chain roller Shades ...

If you can't add new device, check if the firwmare number is visible on phoscon, try with an USB extension usb cordon and check the deconz logs, but pls create a new issue for that.

Can too restore an old backup made with phoscon.

[mhin76]

Hi Smanar. Thanks for your fast reply. Similar in term of connecting the device and only seeing the short 0x ID, but yes I will create a new issue and not on this plugin because issue is rather with phoscon-app-beta (trouble started after I have upgraded to v2.11.1), saw something on #265.
Yes, firmware is visible, have extended cord. All worked before and works with other devices, just not with the aquara temp and door sensor anymore. I can keep you posted. Kind regards, Martin

[Smanar]

What is the relation with phoscon ?
You can have the same issue with all third app.
You issue is just about devices not reconized ?

[mhin76]

Hi Smanar. Issue is that when I pair any Xiaomi Temp or Door sensors via ConBee II plugged in to my Raspberry deCONZ is adding a new item but keeps it as unknown device with short 0x ID. Nothing shows up in the REST API nor Phoscon. But using same deCONZ version and ConBee II on my laptop (windows) it works just fine (as it worked before with my Raspberry). I found a workaround that I first pair on windows, then backup the gateway, restore it on my Raspberry and pair it there again. Very cumbersome but seems to work. No idea, why it stopped pairing fully on the RaspBerry, it seems it cannot read the additional info that is required to identify the device.
I have described all my steps under dresden-elektronik/phoscon-app-beta#378.
Uff, I give it up. I had added successfully three devices and one as unknown. After closing deCONZ and starting it again, two of the just added devices disappeared.

[Smanar]

For me you have connexions issue. Incomplete inclusion was removed after a restart.
Try to prevent the device go to sleep during inclusion by pressing shortly the button every 2s after the long press.

[mhin76]

Thanks, appreciate any ideas. strange is that while running deCONZ on windows it paired like a charm. same as it did before on Raspberry. I will analyze now both log files to see what the difference are and will try your approach. Strange that the devices were gone from deCONZ after restart. that is how it all started with my about 40th device.
I just reset Conbee II and plugged it in to my windows machine again, which before worked all perfectly. but now first node, door sensor, does not work anymore. :( I only got until the 0x ID. Even I kept it awake by sending data. I see in the log that it requests "get node descriptor for 0x..." but that never comes back. Well, I will keep on debugging :)
Edit: I see that after a gateway reset the zll.db of deconz still has entries. That might cause some issues. Will further investigate.

[mhin76]

Hi Smanar. After all it might be something for this deconz-rest-plugin. I have reset everything in windows. paired successfully the Xiaomi Multi Senors but only half way the door sensor. with half I mean in deCONZ is shows the 0xXXXX ID and it does not appear in Phoscon nor in the deCONZ REST API. But the device works, it sends update and even in deCONZ under Cluster Info I see if door is open or closed. I will open a new issue here.

[jscheurwater]

For everyone who is struggling with the issue of not being able to pair this Zemismart M515EGBZTN:
I managed to do this by completing the steps @PhilipsGorniczy, @GreyEarl and @Meatballs1 did also.

When I first visited this topic and Github (2 months ago) I used Home Assistant OS on a Raspberry Pi 4 and the DeCONZ add-on. With this set-up, I could not use the REST-API to test the custom code @Smanar provided.
I decided to change my setup. Right now I'm using Raspbian OS on my Raspberry Pi. On Raspbian OS I installed Home Assistant Supervised. I also installed DeCONZ directly on the Pi (using the command line to install).

When my previous HA and DeCONZ setup and devices were fully restored, I took the following steps to add this device:
Firstly I added the custom code below, provided by @Smanar

sudo apt install deconz-dev
git clone --branch tuya_14 https://github.com/Smanar/deconz-rest-plugin.git
cd deconz-rest-plugin
qmake && make
sudo cp ../libde_rest_plugin.so /usr/share/deCONZ/plugins

Then, when I added the light using Phoscon trought the DeCONZ REST-API, a light appeared.
I changed the name and also added this code to customize.yaml:
Thanks for this @GreyEarl

<entity_name>:
  assumed_state: true

Then, I was able to use both the up- and down buttons.

Many thanks to @Smanar!

My next steps are to buy a proper (beaded) chain because my current chain does not have beads on it. The chain is gliding right now. Side question: @GreyEarl @Meatballs1 @PhilipsGorniczy which chains do you use for this device?

[stevewull]

@Smanar: Are there plans to merge the custom code into the main deCONZ release? Using v2.11.3 (Windows version), I still have problems recognizing the M515EGBZTN.

In response to a question posed by @PhilipsGorniczy early in this thread. Yes, Zemismart has two different versions with identical Manufacturer Name (_TZE200_xuzcvlku) and Model Identifier (TS0601). The M515EGB (ZB) has a wall plug that acts as a Zigbee repeater. The newer M515EGBZTN operates on a battery as described above.

I have both. The wall plug version works great in the deCONZ and HA. The battery version is still not working for me in v2.11.3. I can pair. It appears in the deCONZ gui. I read the basic cluster twice. But it does not appear in the API or Phoscon.

[Smanar]

From that I m reading the V2.11.3 have all last patch.
If I m right at first inclusion (even with phoscon) you will have a sensor entry for the battery, it s this one that help to reconize the device on the second inclusion.

If you haven't it can you show your device mac adress (at least the 6 first number) and your manufacture number (visible in node info panel)

And BTW what is the difference between both, same manufacture number, only one is show as router and the second one as end device ?

[stevewull]

I paired both by searching for Light in Phoscon. After pairing, neither appears anywhere in the Phoscon UI. There is no sensor entry. I paired the wall plug version several months ago. (PS: thanks for the correcting the up/down direction.)

Within the deCONZ, the two are shown. The one on left is battery version, the one on the right is the wall plug version. Wall plug version shows as router and has connections to all of my Ikea range extenders. Mac addresses are there.

.

Mac address for battery version: 0x5c0272fffec20952
Mac address for wall plug version: 0x5c0272fffe8c6f5c

Looking at the Basic cluster, the only difference I see is the Power Source.

Battery version:

Wall plug version:

The literature from Zemismart is vague. Gives the impression that they are retiring the wall plug version and shipping the battery version going forward. Hard to tell for sure.

[stevewull]

Correction: There is a sensor entry in the API for the battery version. No lights entry:

The wall plug version shows up as a Window Covering Device in the Lights section:

[GreyEarl]

I paired both by searching for Light in Phoscon. After pairing, neither appears anywhere in the Phoscon UI. There is no sensor entry. I paired the wall plug version several months ago. (PS: thanks for the correcting the up/down direction.)

Within the deCONZ, the two are shown. The one on left is battery version, the one on the right is the wall plug version. Wall plug version shows as router and has connections to all of my Ikea range extenders. Mac addresses are there.

Remove the left one manually in DeCONZ. Pair again.

The literature from Zemismart is vague. Gives the impression that they are retiring the wall plug version and shipping the battery version going forward. Hard to tell for sure.

Correct. I ordered two separate from each other. In both cases I received the battery versions.

[stevewull]

Node info for Battery version:

Node info for wall plug version:

[Meatballs1]

@stevewull I'm on v2.11.00 / 14/03/2021 and the battery one shows up as Fairy Lights in the Phoscon UI?

[Smanar]

I realy don't see problem in code, and your mac adress range is same for both.

Can you share logs (with "info" and "info_l2") during the inclusion procedure ?

• You need to have the battery sensor
• Start logging
• In phoscon "add new light"
• make the procedure.

Perhaps you need to delete the plug device if you have it, but it seem you don't ave it

[stevewull]

Thanks everyone for quick your replies. It works!

I missed the last step, mentioned by @GreyEarl. After the initial pairing, I needed to manually delete the node and pair a second time. Once I did this, the cover appeared as Fairly Lights in the Phoscon UI.

It also was immediately detected by the Home Assistant deCONZ integration. I can control the shade from HA. Direction arrows are correct.

Thank you.

[schweppy]

Just thought I’d add to this as I have just received the new TN battery version.

I have the motor appearing as fairy lights in phoscon and homebridge-hue shows as a blind in homekit which is great, however, there is no battery information in Deconz and therefore homekit shows warning low battery.

anyone else had this issue?

[Smanar]

Can you share the device JSON you have ?
Remember battery is on the battery sensors, not the light entry.

[GreyEarl]

Can you share the device JSON you have ?
Remember battery is on the battery sensors, not the light entry.

I think he means the NULL state:

{
    "config": {
      "on": true,
      "reachable": true
    },
    "ep": 1,
    "etag": "0901c533da9f6c88a7a056cb3d40c6d4",
    "lastseen": "2021-06-16T05:08Z",
    "manufacturername": "_TZE200_xuzcvlku",
    "modelid": "TS0601",
    "name": "Battery 2",
    "state": {
      "battery": null,
      "lastupdated": "none"
    },
    "type": "ZHABattery",
    "uniqueid": "5c:02:72:ff:fe:ec:b8:d7-01-ef00"
  }

[Smanar]

Ha yes I remember, it s missing yes.
But this device don't use power configuration cluster , so if it send the battery level it s with the tuya cluster, and I don't have the DP value used.
It s missing too on other zigbee project, have you tried with the tuya application to see if the device send it ?

[schweppy]

I tried deleting the device and discovering again, this time I get a Battery sensor show in “Hue Essentials” app. The only way to have control of the device is to delete battery sensor and do a discovery for “Switches” in Phoscon App.

Then I get this information but no battery info.

[Smanar]

No I mean with the offical gateway, the tuya one, to be sure this feature exist on the original one.

[schweppy]

I don’t have a Tuya gateway, only Deconz. 😔

…

On 18 Jun 2021, at 15:36, Smanar ***@***.***> wrote:  No I mean with the offical gateway, the tuya one, to be sure this feature exist on the original one. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[antonoal]

For the sake of people also trying to add a battery powered motor and facing an issue like me, sharing my experience.
I've tried following the steps described in this thread, but alas whenever I deleted the battery node, when I tried discovering the device again deconz would add back it a a battery node. A day of battling later I tried resetting the battery node instead of deleting it, and then added a new light. This time it has worked.
Another reason why I might have been struggling is that I didn't set the limits on the motor before trying to add it to deconz.

[jscheurwater]

Hi everyone, I had some problems with my Zemismart device and tried to pair it again.
The custom code @Smanar provided before did not work this time.

When I try to pair the device, a battery node appears, but the Zemismart device is not recognised.
Can somebody help me with this issue?

[Smanar]

I have spend some hours without someone else #5527
The inclusion is event based, so can be random.

If the battery node appear, it can be a good start, it mean the API now know the manufacture name.

The better way is set phoscon in permit join "add new light" for the maximum of time, and try inclusions with and without deleting the device (read basic attribute / simple descriptor can trigger inclusion too)

Will be solved with DDF in some versions, but ATM there is no universal method to include tuya battery powered covering, just retry and cross finger.

[jscheurwater]

Yes, you are right. I tried it multiple times and eventually it worked!