Closed fireblade70 closed 3 years ago
Required screenshots as per request template are missing.
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.
Can you please clarify which screenshot is missing? I followed the instructions as per Instructions. I see them clearly in my original post? PS apologies for the delay in responding.
Can you please clarify which screenshot is missing? I followed the instructions as per Instructions. I see them clearly in my original post? PS apologies for the delay in responding.
The cluster screenshots @fireblade70 . https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/How-to-read-Clusters
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.
Drayton TRV Clusters.zip Sorry for delay. I have screenshot of all the clusters attached
@fireblade70 Can you add them seperately?
@fireblade70 Can you add them seperately?
Hello I bought a Drayton Wiser Thermostat Valve, fooled by the fact that was reported as working and supported. After some tests I was only able to pair it with the coordinator (Conbee II), but there's no way to manage it. Battery level and temperature are reported. Does anybody know if it has to be reconfigured, in the Thermostat Cluster perhaps ? Otherwise I have no choice but to return it and look for other working products. Thanks in advance
Hello I bought a Drayton Wiser Thermostat Valve, fooled by the fact that was reported as working and supported. After some tests I was only able to pair it with the coordinator (Conbee II), but there's no way to manage it. Battery level and temperature are reported. Does anybody know if it has to be reconfigured, in the Thermostat Cluster perhaps ? Otherwise I have no choice but to return it and look for other working products. Thanks in advance
I can only currently manage it with a Plugin but it's very hit and miss. Doing some digging, I found other users are experiencing the same. When it works, I only get values on Mode, Setpoint & Temp. All others do not work. I have sent a message on Drayton FB page for a firmware update file but no reply as yet.
Thanks for your feedback @fireblade70 It looks like this product is on the way home :). FYI best results up to now obtained with Eurotronic Spirit.
Does anyone use this TRV? I would really like to buy the thermostats, but based on the comments I'm not sure whether they work with deconz or not.
I have a problem with the iTRV. I connected the thermostat to Deconz and I also see some values. But the battery is always displayed to me at 10 percent. Is there an error there? And can someone help me program the weekly programs and connect them to a room thermostat from the series?
Hi,
can you please share the DDF automatically generated by deconz? I'd recommend to start deconz and wait somewhere between 30 and 60 minutes before doing it, this will collect as much info as possible from the device based on the legacy code. Thanks!
I gave up interfacing this iTRV with ZHA (both with DeCONZ & SONOFF). I bought the wiser hub and I can now fully control the valve via the Drayton integration. I reckon the manufacturer has done some custom zigbee config. Look out for discount offers.
I hope you can do something with it and that I did it right. Otherwise please give instructions on what exactly I have to do.
{
"schema": "devcap1.schema.json",
"manufacturername": "Schneider Electric",
"modelid": "iTRV",
"product": "iTRV",
"sleeper": false,
"status": "Draft",
"path": "/devices/Schneider/itrv.json",
"subdevices": [
{
"type": "$TYPE_THERMOSTAT",
"restapi": "/sensors",
"uuid": [
"$address.ext",
"0x01",
"0x0201"
],
"fingerprint": {
"profile": "0x0104",
"device": "0x0301",
"endpoint": "0x01",
"in": [
"0x0000",
"0x0001",
"0x0201",
"0x0204",
"0x0B05"
]
},
"items": [
{
"name": "attr/id"
},
{
"name": "attr/lastannounced"
},
{
"name": "attr/lastseen"
},
{
"name": "attr/manufacturername"
},
{
"name": "attr/mode",
"description": "Operational mode.",
"default": 1
},
{
"name": "attr/modelid"
},
{
"name": "attr/name"
},
{
"name": "attr/swversion"
},
{
"name": "attr/type"
},
{
"name": "attr/uniqueid"
},
{
"name": "config/battery",
"description": "The current device battery level in 0–100 %.",
"default": 0
},
{
"name": "config/coolsetpoint",
"description": "Target cooling temperature of a thermostat.",
"default": 0
},
{
"name": "config/heatsetpoint",
"description": "Target temperature of a thermostat.",
"read": {
"at": "0x0012",
"cl": "0x0201",
"ep": 0,
"fn": "zcl:attr"
},
"write": {
"at": "0x0012",
"cl": "0x0201",
"dt": "0x29",
"ep": 0,
"eval": "Item.val;",
"fn": "zcl:attr"
},
"parse": {
"at": "0x0012",
"cl": "0x0201",
"ep": 0,
"eval": "Item.val = Attr.val;",
"fn": "zcl:attr"
},
"default": 0
},
{
"name": "config/locked",
"description": "Locks or unlocks the device. This item has to be understood as child-lock.",
"read": {
"at": "0x0001",
"cl": "0x0204",
"ep": 0,
"fn": "zcl:attr"
},
"write": {
"at": "0x0001",
"cl": "0x0204",
"dt": "0x30",
"ep": 0,
"eval": "Item.val",
"fn": "zcl:attr"
},
"parse": {
"at": "0x0001",
"cl": "0x0204",
"ep": 0,
"eval": "Item.val = Attr.val;",
"fn": "zcl:attr"
},
"default": false
},
{
"name": "config/mode",
"description": "Mode of the device."
},
{
"name": "config/offset",
"description": "Relative offset to the main measured value.",
"default": 0
},
{
"name": "config/on"
},
{
"name": "config/reachable"
},
{
"name": "state/lastupdated"
},
{
"name": "state/on",
"description": "True when device is on; false when off.",
"refresh.interval": 5,
"read": {
"at": "0x0000",
"cl": "0x0006",
"ep": 0,
"fn": "zcl:attr"
},
"parse": {
"at": "0x0000",
"cl": "0x0006",
"ep": 0,
"eval": "Item.val = Attr.val",
"fn": "zcl:attr"
}
},
{
"name": "state/temperature",
"description": "The current temperature in °C × 100.",
"parse": {
"at": "0x0000",
"cl": "0x0402",
"ep": 0,
"eval": "Item.val = Attr.val + R.item('config/offset').val",
"fn": "zcl:attr"
},
"default": 0
},
{
"name": "state/valve",
"description": "The open percentage of the thermostat valve.",
"read": {
"at": "0x0008",
"cl": "0x0201",
"ep": 0,
"fn": "zcl:attr"
},
"parse": {
"at": "0x0008",
"cl": "0x0201",
"ep": 0,
"eval": "Item.val = Attr.val;",
"fn": "zcl:attr"
},
"default": 0
}
]
}
]
}
That should do fine for a start, thanks. Needs some amendments, will share something once ready.
Accodrong to the screenshots here in this issue, the device does not support any schedules/weekly programs.
I recreated all screenshots. I think the device supports weekly programs. Or am I wrong?
I think the device supports weekly programs. Or am I wrong?
No, it doesn't. What makes you think it does? That is on-device schedules to be more precise allowing the radiators to be steered when any home automation system or deconz is down. With an home automation system, you can of course implement whatever you want.
Could you please give the DDF here a try? #7801
That´s what I mean, I would store a Programm on the Thermostat. But I found no manual how to do this.
That´s what I mean, I would store a Programm on the Thermostat. But I found no manual how to do this.
Well, as previously said, the device doesn't support it and hence the lack of any supporting documentation.
Hello, the battery is always displayed to me at 10%. The Battery ist new so I think it musst shown with near 100%. FHEM shows me 2 readings "battery" and "batteryPercent" both say 10%. In Phoscon is can see Batterie with the same value. Is ther a Problem in the DDF?
Device
Screenshots