LIDL SilverCrest Smart Radiator Thermostat

[synatis]

Device

• Product name: LIDL SilverCrest Smart Radiator Thermostat
• Manufacturer: _TZE200_chyvmhay
• Model identifier: TS0601
• Device type : Thermostat

Screenshots

Endpoint and Node Info

Basic

Groups

Scenes

Thermostat

[synatis]

Let me know if more info is required!

[holzmichel6]

Hallo, bei mir lassen sich diese thermostate auch nicht steuern ...

[Element2]

+1 for adding support.

[Smanar]

It seem it use same command than the "Tuya_THD BTH-002 Thermostat".
Someone is able to compile the code to test changes ?

[synatis]

@Smanar I bet you'll get this question a lot:
I would like to test it but can I do that as a pleb? Are there any instructions what I have to do?

Edit: nvm. Found something https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/Compiling-the-REST-plugin-for-device-specific-testing

[Smanar]

Yep sorry, you just need a linux machine with full OS (I can't help you for dockers), I will give you command to use.

[synatis]

I'll try setting up an Ubuntu VM tomorrow and let you know when I'm ready to test.

[Smanar]

Sure, you just need to have deconz installed on the VM (using package method if possible, will be easier later).
You can switch the conbee from your prod machine to your dev machine without problem (just for tests, somes minuts) , network config is on the conbee but devices config is on the host.

[holzmichel6]

hallo, wie lange dauert das in der regel bis neue bzw unbekannte geräte in phoscon bzw deconz eingebunden werden oder ist es ehr unwahrscheinlich das diese lidl silver crest zigbee thermostate überhaupt eingebunden werden ? würde mich über eine antwort freuen, habe nämlich 10 stück hier rumligen und kann leider so nichts mit anfangen

[zoschfrosch]

I tried to use the Lidl Silvercrest Radiator Thermostat with the deconz plugin in Home Assistant...I see the thermostat in deconz and Home Assistant but cannot change the temperature. I'm glad that you are working on a solution. I have an Ubuntu machine, so if I can help, please let me know.

[synatis]

@Smanar
I'm ready

[Mimiix]

hallo, wie lange dauert das in der regel bis neue bzw unbekannte geräte in phoscon bzw deconz eingebunden werden oder ist es ehr unwahrscheinlich das diese lidl silver crest zigbee thermostate überhaupt eingebunden werden ? würde mich über eine antwort freuen, habe nämlich 10 stück hier rumligen und kann leider so nichts mit anfangen

Can you please keep it English?

[Smanar]

Ok so first try

You have the procedure here https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/Compiling-the-REST-plugin-for-device-specific-testing
So for you, after having installed deconz :

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

The code make lot of thing, but still missing some feature like the "windows open", just tell me that is working or missing.
It use the last library version (2/3 days ago) So it's possible you have some error during compilation, but It works on my side.

tuya device can need 2 inclusions to work (without deleting it)

[synatis]

Compiled without an error and Thermostat is controllable via HA but there is a lot of stuff that doesn't make sense to me.
I ran out of time and have to continue tomorrow and create a detailed list.

[Smanar]

Yeah It seem this device have somes specials features, can set more temperature, for exemple eco temperature.

When you use manualy a feature, it s possible to see in log the command to use to do same with code, but I will explain later.

[synatis]

This is what I see:

Changing temperature works in all 3 modes (the buttons below: "Auto", "Heat" and "Off" from left to right) but only pushes it on the device if mode is set to "Heat".
If it's set to Off and I change the temp. it switches to "Auto" but doesn't push the new temp. on it. Same if it's already in Auto-mode - no changes.

The buttons represent Operation:

With Preset I get the following options but only "auto" doesn't give an error:
Failed to call service climate/set_preset_mode. /sensors/2/config/heatsetpoint Could not set attribute

The error if I switch to anything but "auto":
Failed to call service climate/set_preset_mode. /sensors/2/config/heatsetpoint Could not set attribute

Hope that helps a bit 😅

[MisterPascal]

Hi, @synatis do you use a ZigBee Hub from Silvercrast or how did you manage to connect the device? I bought one today and cant find it in my Phoscon App...

[Mimiix]

@passi1995 it won't show in phoscon. Only in the API.

[MisterPascal]

@Mimiix okay but I also cant see it there...

[synatis]

Hi, @synatis do you use a ZigBee Hub from Silvercrast or how did you manage to connect the device? I bought one today and cant find it in my Phoscon App...

Press the top button of the Thermostat until you see PAIr then go over to Phoscon App and add a new sensor. Should take no more than 1min until your "sensor is ready". After that you can see it in deCONZ like the first screenshot of this thread.

[MisterPascal]

Thank you @synatis! I didn't find pairing function. Got it in HA now but without any function. Let me know if I can help to integrate this device...

[Smanar]

"Preset" can't work, It s not used for TRV (but I think we will need it for this one, because of it s special features), It s only used for thermostat, not valve.
If I m right you haven't it in the json ?

And for auto, there is a problem I don't have HA, so idk how it work

If it's set to Off and I change the temp. it switches to "Auto" but doesn't push the new temp. on it. Same if it's already in Auto-mode - no changes.

I can't say if it s the device that switch itself to "auto" when receve a temperature, or if it s from HA.

If you still are on the GUI, can you take a look in logs with "info" "info_l2" and trying the same procedure.
I need logs with "tuya" inside pls.
It can depend of order, if HA send first the temperature before the mode, so perhaps I need to memorise it somewhere because there is not the same issue on other devices with HA too, something specific to this one ...

[synatis]

Hey, are those the json you need to see?

Info for switching temp while device is set to off

19:03:44:636 create node 0xCC86ECFFFE4EAF03 seen by 2 neighbors
19:03:44:969 Send Tuya request 0xB4E3F9FFFEC74CBF : Dp_type: 0x02, Dp_identifier 0x10, data: 00000016
19:03:45:115 create node 0x5C0272FFFECA638F seen by 2 neighbors
19:03:45:324 Tuya debug 4 : Address 0xB4E3F9FFFEC74CBF Payload 00101002000400000016
19:03:45:324 Tuya debug 5 : Status: 0 Transid: 16 Dp: 528 (0x02,0x10) Fn: 0 Data 22
19:03:45:445 Tuya debug 4 : Address 0xB4E3F9FFFEC74CBF Payload 00101002000400000016
19:03:45:445 Tuya debug 5 : Status: 0 Transid: 16 Dp: 528 (0x02,0x10) Fn: 0 Data 22
19:03:47:036 create node 0x5C0272FFFEF5B403 seen by 2 neighbors
19:03:47:516 create node 0x5C0272FFFED1D6EE seen by 2 neighbors
19:03:47:997 create node 0xCC86ECFFFE4EAF03 seen by 2 neighbors
19:03:48:476 create node 0x5C0272FFFECA638F seen by 2 neighbors
19:03:49:916 create node 0x5C0272FFFED1D6EE seen by 2 neighbors
19:03:50:396 create node 0x5C0272FFFEF5B403 seen by 2 neighbors
19:03:50:854 Device TTL 2220 s flags: 0x7
19:03:52:316 create node 0xCC86ECFFFE4EAF03 seen by 2 neighbors
19:03:52:326 Tuya debug 4 : Address 0xB4E3F9FFFEC74CBF Payload 00020204000100
19:03:52:326 Tuya debug 5 : Status: 0 Transid: 2 Dp: 1026 (0x04,0x02) Fn: 0 Data 0
19:03:52:437 Tuya debug 4 : Address 0xB4E3F9FFFEC74CBF Payload 00020204000100
19:03:52:437 Tuya debug 5 : Status: 0 Transid: 2 Dp: 1026 (0x04,0x02) Fn: 0 Data 0
19:03:52:796 create node 0x5C0272FFFECA638F seen by 2 neighbors
19:03:54:715 create node 0x5C0272FFFEF5B403 seen by 2

Info_l2

19:10:27:733 Erase task req-id: 160, type: 37 zcl seqno: 137 send time 3, profileId: 0x0104, clusterId: 0xEF00
19:10:27:837 CTRL skip creating node 0x5C0272FFFECA638F while permit join is disabled
19:10:27:917 Tuya debug Request : Address 0xB4E3F9FFFEC74CBF, Endpoint 0x01, Command 0x02, Payload 00020204000102
19:10:29:278 CTRL skip creating node 0x5C0272FFFED1D6EE while permit join is disabled
19:10:29:757 CTRL skip creating node 0x5C0272FFFEF5B403 while permit join is disabled
19:10:30:833 Daylight now: sunsetEnd, status: 200, daylight: 0, dark: 1
19:10:31:228 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0xE1A7
19:10:31:228 neigbor 0x0c4314fffe619d00 is unknown child
19:10:31:677 CTRL skip creating node 0xCC86ECFFFE4EAF03 while permit join is disabled
19:10:32:144 Websocket 192.168.178.25:43764 send message: {"config":{"battery":100,"heatsetpoint":1300,"locked":false,"mode":"off","offset":0,"on":true,"preset":"auto","reachable":true,"schedule":{},"schedule_on":false,"setvalve":false},"e":"changed","id":"2","r":"sensors","t":"event","uniqueid":"b4:e3:f9:ff:fe:c7:4c:bf-01-0201"} (ret = 273)
19:10:32:156 CTRL skip creating node 0x5C0272FFFECA638F while permit join is disabled
19:10:32:636 CTRL skip creating node 0x0C4314FFFE619D00 while permit join is disabled
19:10:33:286 Erase task req-id: 178, type: 37 zcl seqno: 138 send time 1, profileId: 0x0104, clusterId: 0xEF00
19:10:33:479 Tuya debug Request : Address 0xB4E3F9FFFEC74CBF, Endpoint 0x01, Command 0x02, Payload 0010100200040000001a
19:10:33:655 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
19:10:34:077 CTRL skip creating node 0x5C0272FFFEF5B403 while permit join is disabled
19:10:34:556 CTRL skip creating node 0x5C0272FFFED1D6EE while permit join is disabled
19:10:35:036 CTRL skip creating node 0xCC86ECFFFE4EAF03 while permit join is disabled
19:10:35:516 CTRL skip creating node 0x5C0272FFFECA638F while permit join is disabled
19:10:36:956 CTRL skip creating node 0x5C0272FFFED1D6EE while permit join is disabled
19:10:37:436 CTRL skip creating node 0x5C0272FFFEF5B403 while permit join is disabled
19:10:37:832 DB save zll database items 0x00000080
19:10:37:832 DB sql exec REPLACE INTO sensors (sid, name, type, modelid, manufacturername, uniqueid, swversion, state, config, fingerprint, deletedState, mode, lastseen, lastannounced) VALUES ('2', 'Thermostat 2', 'ZHAThermostat', 'TS0601', '_TZE200_chyvmhay', 'b4:e3:f9:ff:fe:c7:4c:bf-01-0201', '', '{"lastupdated":"2021-10-14T17:10:22.331","on":false,"temperature":2190}', '{"battery":100,"heatsetpoint":1300,"locked":false,"mode":"off","offset":0,"on":true,"preset":"auto","reachable":true,"schedule":null,"schedule_on":false,"setvalve":false}', '{"d":769,"ep":1,"in":[61184,0,513,61184],"p":260}', 'normal', '1', '2021-10-13T17:44Z', '')
19:10:37:839 DB saved in 6 ms
19:10:38:912 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0xE1A7
19:10:38:912 neigbor 0x0c4314fffe619d00 is unknown child
19:10:39:356 CTRL skip creating node 0xCC86ECFFFE4EAF03 while permit join is disabled
19:10:39:836 CTRL skip creating node 0x5C0272FFFECA638F while permit join is disabled

[Smanar]

19:03:44:969 Send Tuya request 0xB4E3F9FFFEC74CBF : Dp_type: 0x02, Dp_identifier 0x10, data: 00000016

Dp_identifier 0x10 = DP_IDENTIFIER_THERMOSTAT_HEATSETPOINT_3
It mean you have set the 0x16 = 22 degréé value at set heat point

19:03:45:324 Tuya debug 4 : Address 0xB4E3F9FFFEC74CBF Payload 00101002000400000016
19:03:45:324 Tuya debug 5 : Status: 0 Transid: 16 Dp: 528 (0x02,0x10) Fn: 0 Data 22

This is just the confirmation from the device

19:03:52:326 Tuya debug 4 : Address 0xB4E3F9FFFEC74CBF Payload 00020204000100
19:03:52:326 Tuya debug 5 : Status: 0 Transid: 2 Dp: 1026 (0x04,0x02) Fn: 0 Data 0

0x02 is the mode and data = 0 mean "auto"

On the logs with L2

19:10:27:917 Tuya debug Request : Address 0xB4E3F9FFFEC74CBF, Endpoint 0x01, Command 0x02, Payload 0002 0204 00 01 02

You hare setting the mode 0x02 = "off"

19:10:32:144 Websocket 192.168.178.25:43764 send message: {"config":{"battery":100,"heatsetpoint":1300,"locked":false,"mode":"off","offset":0,"on":true,"preset":"auto","reachable":true,"schedule":{},"schedule_on":false,"setvalve":false},"e":"changed","id":"2","r":"sensors","t":"event","uniqueid":"b4:e3:f9:ff:fe:c7:4c:bf-01-0201"}

Ok confirmation by websocket "mode" = "off"

19:10:33:479 Tuya debug Request : Address 0xB4E3F9FFFEC74CBF, Endpoint 0x01, Command 0x02, Payload 0010 1002 00 04 0000001a

Setting the set heat point to 0x1a = 26 degree.

19:10:37:832 DB sql exec REPLACE INTO sensors (sid, name, type, modelid, manufacturername, uniqueid, swversion, state, config, fingerprint, deletedState, mode, lastseen, lastannounced) VALUES ('2', 'Thermostat 2', 'ZHAThermostat', 'TS0601', '_TZE200_chyvmhay', 'b4:e3:f9:ff:fe:c7:4c:bf-01-0201', '', '{"lastupdated":"2021-10-14T17:10:22.331","on":false,"temperature":2190}', '{"battery":100,"heatsetpoint":1300,"locked":false,"mode":"off","offset":0,"on":true,"preset":"auto","reachable":true,"schedule":null,"schedule_on":false,"setvalve":false}', '{"d":769,"ep":1,"in":[61184,0,513,61184],"p":260}', 'normal', '1', '2021-10-13T17:44Z', '')

But the heatsetpoint" is locked at 13.00 .....

Have updated the code to prnint more debug line, visible with "info", they will start by "Debug tuya 77", if you can update your code and restart the same procedure (can enable info and info_l2 in same time)

cd deconz-rest-plugin
git pull
qmake && make -j2
sudo cp ../libde_rest_plugin.so /usr/share/deCONZ/plugins

From your log it seem

• it s the device than change the mode, when receiving a new set heatpoint value (ok, logic)
• the return value for it is not updated in deconz

Edit:
Ok, have found the problem, give me 10 mn.

Edit2:
Sorry I need more test from you.
From that I m reading the value need to be / 2, so if you try to set a 22 degree value for heat setpoint the value visible in the tuya request need to be 44 = 0x2C and not 0x16.

And when you set 26 degree, the value in the json is 13, because divided by 2.
Something you can do is using manualy the device, and look at return in log, for exemple setting a 20 degree value for heatpoint and look for log

19:03:45:445 Tuya debug 4 : Address 0xB4E3F9FFFEC74CBF Payload 001010020004000000XX
19:03:45:445 Tuya debug 5 : Status: 0 Transid: 16 Dp: 528 (0x02,0x10) Fn: 0 Data XX

[synatis]

Set mode to manual directly on the device and turned up the value from 13°C to 20°C
It's amazing what you can do, just by looking at logs :'D

15:37:35:069 Idle timer triggered
15:37:35:292 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0xE1A7
15:37:35:292 neigbor 0x0c4314fffe619d00 is unknown child
15:37:35:741 create node 0xCC86ECFFFE4EAF03 seen by 2 neighbors
15:37:35:741 CTRL skip creating node 0xCC86ECFFFE4EAF03 while permit join is disabled
15:37:36:220 create node 0x5C0272FFFECA638F seen by 2 neighbors
15:37:36:221 CTRL skip creating node 0x5C0272FFFECA638F while permit join is disabled
15:37:36:701 CTRL skip creating node 0x0C4314FFFE619D00 while permit join is disabled
15:37:37:720 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
15:37:38:141 create node 0x5C0272FFFED1D6EE seen by 2 neighbors
15:37:38:142 CTRL skip creating node 0x5C0272FFFED1D6EE while permit join is disabled
15:37:38:620 create node 0x5C0272FFFEF5B403 seen by 2 neighbors
15:37:38:621 CTRL skip creating node 0x5C0272FFFEF5B403 while permit join is disabled
15:37:39:101 create node 0x5C0272FFFECA638F seen by 2 neighbors
15:37:39:101 CTRL skip creating node 0x5C0272FFFECA638F while permit join is disabled
15:37:39:568 DB save zll database items 0x00000084
15:37:39:569 DB sql exec REPLACE INTO auth (apikey, devicetype, createdate, lastusedate, useragent) VALUES ('19426F394B', 'pydeconz', '2021-10-13T18:07:01', '2021-10-17T13:37:15', 'HomeAssistant/2021.10.4 aiohttp/3.7.4.post0 Python/3.9')
15:37:39:569 DB sql exec REPLACE INTO sensors (sid, name, type, modelid, manufacturername, uniqueid, swversion, state, config, fingerprint, deletedState, mode, lastseen, lastannounced) VALUES ('2', 'Thermostat 2', 'ZHAThermostat', 'TS0601', '_TZE200_chyvmhay', 'b4:e3:f9:ff:fe:c7:4c:bf-01-0201', '', '{"lastupdated":"2021-10-17T13:37:03.589","on":false,"temperature":1600}', '{"heatsetpoint":2000,"locked":false,"mode":"heat","offset":0,"on":true,"preset":"auto","reachable":true,"schedule":null,"schedule_on":false,"setvalve":false}', '{"d":769,"ep":1,"in":[61184,0,513,61184],"p":260}', 'normal', '1', '2021-10-13T17:44Z', '')
15:37:39:574 DB saved in 5 ms
15:37:39:575 Daylight now: solarNoon, status: 170, daylight: 1, dark: 0
15:37:39:582 create node 0xCC86ECFFFE4EAF03 seen by 2 neighbors
15:37:39:583 CTRL skip creating node 0xCC86ECFFFE4EAF03 while permit join is disabled
15:37:39:589 Master: read param with arg 0x19
15:37:39:604 Device TTL 3259 s flags: 0x7
15:37:40:286 Tuya debug Request : Address 0xB4E3F9FFFEC74CBF, Endpoint 0x01, Command 0x02, Payload 00101002000400000028
15:37:40:286 Tuya debug 4 : Address 0xB4E3F9FFFEC74CBF Payload 00101002000400000028
15:37:40:286 Tuya debug 5 : Status: 0 Transid: 16 Dp: 528 (0x02,0x10) Fn: 0 Data 40
15:37:40:286 Debug tuya 77 : 1
15:37:40:287 Debug tuya 77 : 2
15:37:40:389 Tuya debug Request : Address 0xB4E3F9FFFEC74CBF, Endpoint 0x01, Command 0x02, Payload 00101002000400000028
15:37:40:389 Tuya debug 4 : Address 0xB4E3F9FFFEC74CBF Payload 00101002000400000028
15:37:40:389 Tuya debug 5 : Status: 0 Transid: 16 Dp: 528 (0x02,0x10) Fn: 0 Data 40
15:37:40:389 Debug tuya 77 : 1
15:37:40:390 Debug tuya 77 : 2
15:37:41:020 create node 0x5C0272FFFED1D6EE seen by 2 neighbors
15:37:41:020 CTRL skip creating node 0x5C0272FFFED1D6EE while permit join is disabled
15:37:41:501 create node 0x5C0272FFFEF5B403 seen by 2 neighbors
15:37:41:501 CTRL skip creating node 0x5C0272FFFEF5B403 while permit join is disabled
15:37:42:974 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0xE1A7
15:37:42:974 neigbor 0x0c4314fffe619d00 is unknown child
15:37:43:420 create node 0xCC86ECFFFE4EAF03 seen by 2 neighbors
15:37:43:421 CTRL skip creating node 0xCC86ECFFFE4EAF03 while permit join is disabled
15:37:43:901 create node 0x5C0272FFFECA638F seen by 2 neighbors
15:37:43:902 CTRL skip creating node 0x5C0272FFFECA638F while permit join is disabled
15:37:44:381 CTRL skip creating node 0x0C4314FFFE619D00 while permit join is disabled
15:37:45:275 Tuya debug Request : Address 0xB4E3F9FFFEC74CBF, Endpoint 0x01, Command 0x02, Payload 001818020004000000dc
15:37:45:275 Tuya debug 4 : Address 0xB4E3F9FFFEC74CBF Payload 001818020004000000dc
15:37:45:275 Tuya debug 5 : Status: 0 Transid: 24 Dp: 536 (0x02,0x18) Fn: 0 Data 220
15:37:45:277 Websocket 192.168.178.25:57266 send message: {"e":"changed","id":"2","r":"sensors","state":{"lastupdated":"2021-10-17T13:37:45.276","on":false,"temperature":2200},"t":"event","uniqueid":"b4:e3:f9:ff:fe:c7:4c:bf-01-0201"} (ret = 175)
15:37:45:397 Tuya debug Request : Address 0xB4E3F9FFFEC74CBF, Endpoint 0x01, Command 0x02, Payload 001818020004000000dc
15:37:45:397 Tuya debug 4 : Address 0xB4E3F9FFFEC74CBF Payload 001818020004000000dc
15:37:45:397 Tuya debug 5 : Status: 0 Transid: 24 Dp: 536 (0x02,0x18) Fn: 0 Data 220
15:37:45:413 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
15:37:45:820 create node 0x5C0272FFFED1D6EE seen by 2 neighbors
15:37:45:821 CTRL skip creating node 0x5C0272FFFED1D6EE while permit join is disabled
15:37:45:885 Node data 0x5c0272fffe03af80 profileId: 0x0104, clusterId: 0x0702
15:37:45:886 No consumption sensor found for 0x5C0272FFFE03AF80, endpoint: 0x01
15:37:45:886 ZCL attribute report 0x5C0272FFFE03AF80 for cluster: 0x0702, ep: 0x01, frame control: 0x08, mfcode: 0x0000
15:37:45:886 payload: 000025573400000000
15:37:46:300 create node 0x5C0272FFFEF5B403 seen by 2 neighbors
15:37:46:301 CTRL skip creating node 0x5C0272FFFEF5B403 while permit join is disabled
15:37:46:589 APS-DATA.indication from unknown node 0x5C0272FFFECA638F
15:37:46:781 create node 0x5C0272FFFECA638F seen by 2 neighbors
15:37:46:781 CTRL skip creating node 0x5C0272FFFECA638F while permit join is disabled
15:37:47:261 create node 0xCC86ECFFFE4EAF03 seen by 2 neighbors
15:37:47:262 CTRL skip creating node 0xCC86ECFFFE4EAF03 while permit join is disabled
15:37:48:701 create node 0x5C0272FFFED1D6EE seen by 2 neighbors
15:37:48:702 CTRL skip creating node 0x5C0272FFFED1D6EE while permit join is disabled
15:37:49:180 create node 0x5C0272FFFEF5B403 seen by 2 neighbors
15:37:49:181 CTRL skip creating node 0x5C0272FFFEF5B403 while permit join is disabled
15:37:49:569 Daylight now: solarNoon, status: 170, daylight: 1, dark: 0
15:37:50:646 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0xE1A7
15:37:50:646 neigbor 0x0c4314fffe619d00 is unknown child
15:37:51:101 create node 0xCC86ECFFFE4EAF03 seen by 2 neighbors
15:37:51:102 CTRL skip creating node 0xCC86ECFFFE4EAF03 while permit join is disabled

[Smanar]

Lol, it s because I know well tuya stuff now

15:37:40:286 Tuya debug 5 : Status: 0 Transid: 16 Dp: 528 (0x02,0x10) Fn: 0 Data 40

So it s that, we realy need to divide by 2.
But on this try the "heatsetpoint" was already 2000 (and not 1300) before the change, so the value is not updated.

Changing temperature works in all 3 modes (the buttons below: "Auto", "Heat" and "Off" from left to right) but only pushes it on the device if mode is set to "Heat".
If it's set to Off and I change the temp. it switches to "Auto" but doesn't push the new temp. on it. Same if it's already in Auto-mode - no changes.

So with new code it will work for "heat" and "auto", IDK yet for "off", but as it switch itself from "off" to "auto" it can work, perhaps not on the first seconds, but on next notification from device.

Have too removed "preset" and "valve", but you need to restart or reinclude the device for the json be updated, so we will check that later.

cd deconz-rest-plugin
git pull
qmake && make -j2
sudo cp ../libde_rest_plugin.so /usr/share/deCONZ/plugins

[synatis]

In HA:
Switching modes works now correctly. Off is something like holiday mode, shown as a suitcase.
Each mode remembers their value.

E.g.:

• Off = 17°C
• Heat ("Manu" on the device display) = 18°C
• Auto = 19°C

HA always shows the value I last set. Let's say I was in auto and changed to 20

Off is still 17. Heat 18. Auto 20. Now when I switch to Off via HA, it shows:

which is incorrect because the device shows 17.

Switches automatically from Off to Auto if value is changed via HA. Doesn't switch from Heat/Manu to Auto, which is nice.

preset is gone as you said 👍

Let me know if more logs are needed. Awesome work so far!

[Smanar]

Huuu, you have a temperature for "off" ?
It's hidden but in reality the device have lot of heatpoint, I m using 2, the heat setpoint and the auto setpoint, there is probably too away, confort and eco, but nothing about "off".

In my mind the mode "off" turn off the device, not setting a lower temperature. IDK what you want to do but

• On "off" mode, it display 17, but if the temperature go under 17 degree, does it turn "on" ?
• Do you want I send a Set point value at 0 degree to disable it on "off" mode ?
• Can you show me log when you go from "heat" to "off" for exemple ? To capture the command for the "off" set heatpoint.

[deafloo]

Hey, since there are some TRVs available via DDF now, maybe there is a chance to integrate this one. I am willing to help with logs and coding but I have very little experience with DDF so far. Maybe @Smanar can have a look at this again?

[Smanar]

Some days ago, with @TheHaf we have made a PR to support tuya TRV.
The PR is not yet valided #6054

But if you can compile the code, can try to make a DDF for this device too.

[markus274]

Is anyone still working on implementing this TRV with DDF?

[Smanar]

The PR to support tuya TRV is not validated, so to use a DDF for this device, you need to be able to compile the code yourself ?

[github-actions]

As there has not been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs.

[deafloo]

This is still open. Waiting for #6054 so we have access to tuya TRV tools.

[containerguy]

+1 for keeping this alive

[Element2]

@Smanar
Is it possible to make a temporary DDF for this device only for changing the setpoint?
I tried to make a DDF for that, using the DDF cheatsheet, but ended up with another bulb flashing ON/OFF when changing the setpoint :(

[Smanar]

Nope, this device use the tuya cluster (for setpoint too), and the only way to change them using DDF is the PR in waiting list.

[Element2]

Ok, thnx.

[langemar]

Hi,

can someone tell me the current state of the integration? Do you need someone to test the pending changes? I would like to support you getting this issue closed soon, or before heating session starts ;)
For #6054 shows some closed and some still open PR's, I can provide testing for the LIDL TRV's and also for (the besides labeling as far as i can see) identical TRV's from wesmartify.

best regards

[Smanar]

Hello,
IDK, for the moment I m waiting for return, to know if the PR is ok or If I need to edit some part.
He is working so I don't think we need more tests.

[deafloo]

I just want to inform you that I bought those TRVs over a year ago and I am still waiting for them to work with deconz. I am quite disappointed about your communication about tuya TRV integration in general. There is a working PR in #6054 and you know it prevents a lot of other TRV integrations, but it became quiet for a few weeks now and it gets colder and colder outside.
I tried to control all my zigbee devices with zigbee2mqtt yesterday and it took me 10 minutes to set up everything including the TRVs in this issue. I really liked the conbee stick and the deconz UI but it is just unbearable for me to wait for such a long time

[Mimiix]

I agree with @deafloo . But i think it's best to address this to @manup as @Smanar has no influence on this.

[deafloo]

Just to make this clear, I do not complain about @Smanar's work here. I very much appreciate what you have contributed and all the tuya devices you have set up so far.

[markus274]

It's really a shame. I also have these TRVs for one year now and couldn’t use them. Why is the PR still pending?

[langemar]

Hi @markus274 ,

this issue is still waiting for #6054 as stated earlier. As i understand @Smanar in his last comment as soon as this pull request is merged a lot of device support packages can be merged and finally used.

best regards

[steff75]

A few weeks ago I had already taken the same step as @deafloo.
Besides the pending PR, the Home Assistant addon was also decisive for me, where there is no real possibility for the management and editing of own DDF files.

Otherwise I have to thank Smanar for his work to get this and many other devices up and running. 👍
Of course I still have the Conbee 2 in the drawer and will keep an eye on the project.

Thank you!

[Christoph-Wagner]

I really liked the conbee stick

Just in case someone else is wondering, the Conbee stick is perfectly useable with Zigbee2MQTT. I switched today as well and while the interface is not as user-friendly as Phoscon, Zigbee2MQTT not only supports the Lidl device (the first of which I just installed), it also seems faster and exposes more advanced setting better than the Deconz app.

[snitzelhammer]

Why is this still not merged?

[Smanar]

Long story but it will be probably never merged as it.
This PR use the c++ code, and this device will be probably added using DDF (but the PR to permit that is in waiting list too)

[langemar]

Why is this still not merged?

Besides stated by @Smanar read comments above to get further information (for example the mentioned pr in waiting list).
There you'll find some hints about progress to support this specific device, and other tuya devices, using other methodes then c++ code - which might never be merged.

[markus274]

I just saw my nearly forgotten TRVs in a drawer after two saisons with no usage. Is there any hope this device will be supported next season?

[Smanar]

IDK, can try with DDF

{
  "schema": "devcap1.schema.json",
  "manufacturername": "_TZE200_chyvmhay",
  "modelid": "TS0601",
  "vendor": "Lidl",
  "product": "Silvercrest TRV",
  "sleeper": false,
  "status": "Gold",
  "subdevices": [
    {
      "type": "$TYPE_THERMOSTAT",
      "restapi": "/sensors",
      "uuid": [
        "$address.ext",
        "0x01",
        "0xef00"
      ],
      "meta": {
        "values": {
          "config/mode": {"auto": 0, "heat": 1, "off": 2}
        }
      },
      "items": [
        {
          "name": "attr/id"
        },
        {
          "name": "attr/lastannounced"
        },
        {
          "name": "attr/lastseen"
        },
        {
          "name": "attr/manufacturername"
        },
        {
          "name": "attr/modelid"
        },
        {
          "name": "attr/name"
        },
        {
          "name": "attr/swversion"
        },
        {
          "name": "attr/type"
        },
        {
          "name": "attr/uniqueid"
        },
        {
          "name": "config/battery",
          "parse": {"fn": "tuya", "dpid": 35, "eval": "Item.val = Attr.val ;"},
          "read": {"fn": "none"}
        },
        {
          "name": "config/heatsetpoint",
          "parse": {"fn": "tuya", "dpid": 16, "eval": "Item.val = Attr.val * 2;"},
          "write": {"fn": "tuya", "dpid": 16, "dt": "0x2b", "eval": "Item.val / 2;"},
          "read": {"fn": "tuya"}
        },
        {
          "name": "config/unoccupiedheatsetpoint",
          "parse": {"fn": "tuya", "dpid": 105, "eval": "Item.val = Attr.val * 2;"},
          "write": {"fn": "tuya", "dpid": 105, "dt": "0x2b", "eval": "Item.val / 2;"},
          "read": {"fn": "none"}
        },
        {
          "name": "config/locked",
          "parse": {"fn": "tuya", "dpid": 40, "eval": "Item.val = Attr.val;"},
          "write": {"fn": "tuya", "dpid": 40, "dt": "0x10", "eval": "Item.val;"},
          "read": {"fn": "none"}
        },
        {
          "name": "config/on"
        },
        {
          "name": "config/reachable"
        },
        {
          "name": "config/mode",
          "values": [
              ["auto", 0], ["heat", 1], ["off", 2]
          ],
          "parse": {"fn": "tuya", "dpid": 2, "eval": "if (Attr.val == 0) { Item.val = 'auto' } else if (Attr.val == 1) { Item.val = 'heat' } else { Item.val = 'off' }"},
          "write": {"fn": "tuya", "dpid": 2, "dt": "0x30", "eval": "if (Item.val == 'auto') { 0 } else if (Item.val == 'heat') { 1 } else { 2 }"},
          "read": {"fn": "none"}
        },
        {
          "name": "state/lastupdated"
        },
        {
          "name": "state/temperature",
          "parse": {"fn": "tuya", "dpid": 24, "eval": "Item.val = Attr.val * 10;"},
          "read": {"fn": "none"}
        }
      ]
    }
  ]
}

the problem is this device have more than 1 heatpoint value, and the code is only able to handle
"config/unoccupiedheatsetpoint" and "config/heatsetpoint" for the moment.

If you try the DDF can you give me the value you have, and the value you need to have for convertion value ?

[markus274]

Is there some sort of how to? I wasn’t involved in developing or testing so far, so I have basically no experience, unfortunately.

[Smanar]

Depend of OS.
To resume you just need to create a text file called whatyouwant.json in a "devices" folder, with this contain, then restart deconz.

All DDF provided directly with deCONZ typically reside in /usr/share/deCONZ/devices/ on a Linux system and are loaded first. However, files residing in the home directory of the user running deCONZ (e.g. /home//.local/share/dresden-elektronik/deCONZ/devices) will override the pre-packaged files to allow users to amend and keep their own files if desired.

For HA https://forum.phoscon.de/t/how-to-add-edit-a-ddf-on-home-assistant-using-text-editor/1839 (need to use the /data/.local/share/dresden-elektronik/deCONZ/devices/ folder)