dresden-elektronik / deconz-rest-plugin

deCONZ REST-API plugin to control ZigBee devices
BSD 3-Clause "New" or "Revised" License
1.89k stars 497 forks source link

Essentials Smart Home Premium Radiator Thermostat #5386

Closed cova-fe closed 2 years ago

cova-fe commented 2 years ago

Device

Screenshots

Basic

image image

Identify

Alarms

Device Temperature

Groups

image

Scenes

image

On/Off

Level Control

Color Control

Simple Metering

Diagnostics

Other clusters that are not mentioned above

scarre commented 2 years ago

Ok, can you guide me a bit on where to find this info for config/mode ? Before I recompiled deConz v2.13.4, the node had a thermostat cluster entry 0201, but the thermostat cluster info was empty after executing a read (all lines grayed out). With the recompiled version, the node no longer has the thermostat cluster entry (see image), but behaves correctly as a thermostat, apart from the heat on/off status. Here is the json from deConz api: {"config":{"battery":97,"heatsetpoint":1500,"locked":false,"offset":0,"on":true,"preset":"manual","reachable":true,"schedule":{},"schedule_on":false,"setvalve":true,"windowopen_set":true},"ep":1,"etag":"2f98774485ee76f73efd71bdab487a33","lastannounced":"2022-01-21T08:14:26Z","lastseen":"2022-01-24T10:13Z","manufacturername":"_TZE200_jeaxp72v","modelid":"TS0601","name":"Thermostat 27","state":{"lastupdated":"2022-01-24T09:44:26.837","on":false,"temperature":2160},"type":"ZHAThermostat","uniqueid":"84:fd:27:ff:fe:a2:4c:17-01-0201"} I use Home Assistant on a second raspberry pi to control my Phoscon Gateway. In HA, the heat indicator is always off, even when the radiator is physically heating, so it probably reads this info from the "on" field in the reported state ? TZ200_jeaxp72v_node_deconz_modified

Smanar commented 2 years ago
{
  "config": {
    "battery": 97,
    "heatsetpoint": 1500,
    "locked": false,
    "offset": 0,
    "on": true,
    "preset": "manual",
    "reachable": true,
    "schedule": {},
    "schedule_on": false,
    "setvalve": true,
    "windowopen_set": true
  },
  "ep": 1,
  "etag": "2f98774485ee76f73efd71bdab487a33",
  "lastannounced": "2022-01-21T08:14:26Z",
  "lastseen": "2022-01-24T10:13Z",
  "manufacturername": "_TZE200_jeaxp72v",
  "modelid": "TS0601",
  "name": "Thermostat 27",
  "state": {
    "lastupdated": "2022-01-24T09:44:26.837",
    "on": false,
    "temperature": 2160
  },
  "type": "ZHAThermostat",
  "uniqueid": "84:fd:27:ff:fe:a2:4c:17-01-0201"
}

So yes I have some explanations:

AND BTW your device is not yet in the code, need this PR https://github.com/dresden-elektronik/deconz-rest-plugin/pull/5404

scarre commented 2 years ago

OK, thanks very much for the clarifications. I was kind of expecting that the device itself did not support a heat on/off indication. I am aware that the device is not yet in code and requires PR #5404. This is why I patched the code of v2.13.4 myself and recompiled to be able to use the device. Any idea why the device thermostat cluster (0201) for this device does not appear in deConz GUI after patching the code as proposed in #5404 (see image in my post above) ?

Smanar commented 2 years ago

Any idea why the device thermostat cluster (0201) for this device does not appear in deConz GUI after patching the code as proposed in #5404 (see image in my post above) ?

Not realy, tuya sometime hide the cluster, so need deconz detect it to display it, but in all case, this device don't use it and use instead the tuya cluster, so I can't explain the result, but you lost nothing.

scarre commented 2 years ago

@bmgit26 (from #5745)

I compiled the not yet merged branch from https://github.com/dresden-elektronik/deconz-rest-plugin/pull/5404. I see more infos now from the Rest-API coming from deconz/thermostat, but I still can't set a new heatpoint that is accepted by the thermostat:

Make sure that you physically have the thermostat on manual (displays a red hand below the temperature), then it will respond to changes of heatset point from deconz. If physically in schedule or anti-freeze mode, it does not respond.

bmgit26 commented 2 years ago

Yes, thanks, this is working. Even setting the mode via restapi/home assistant, and then setting the Heatpoint.

pingu077 @.***> schrieb am Sa., 5. Feb. 2022, 12:12:

@bmgit26 https://github.com/bmgit26 (from #5745 https://github.com/dresden-elektronik/deconz-rest-plugin/issues/5745)

I compiled the not yet merged branch from #5404

https://github.com/dresden-elektronik/deconz-rest-plugin/pull/5404. I see more infos now from the Rest-API coming from deconz/thermostat, but I still can't set a new heatpoint that is accepted by the thermostat:

Make sure that you physically have the thermostat on manual (displays a red hand below the temperature), then it will respond to changes of heatset point from deconz. If physically in schedule or anti-freeze mode, it does not respond.

— Reply to this email directly, view it on GitHub https://github.com/dresden-elektronik/deconz-rest-plugin/issues/5386#issuecomment-1030602476, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA3VI2C3BCE3WZM7FBIC3MTUZUAZ5ANCNFSM5GE57ABQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you were mentioned.Message ID: @.***>

Floyer007 commented 2 years ago

Works for me now as well with https://github.com/dresden-elektronik/deconz-rest-plugin/pull/5404 Manual-mode did the trick.

How did you disabled the window-open detection @appleonkel?

scarre commented 2 years ago

How did you disabled the window-open detection

curl -X PUT -d "{\"windowopen_set\": false}" http://your_deconz_ip/api/your_api_key/sensors/your_sensor_id/config

herrmarten commented 2 years ago

hey @scarre i am missing exactly that config "windowopen_set" but my thermostat shows the window icon. do you have an idea how i can get it under control?

"config": {
        "battery": 100,
        "heatsetpoint": 1750,
        "offset": 0,
        "on": true,
        "reachable": true,
        "schedule": {},
        "schedule_on": false
},
scarre commented 2 years ago

You are also missing "locked", "offset", "preset", "setvalve". Have you recompiled and replaced the deconz lib with the changes from #5404 ?

herrmarten commented 2 years ago

thanks for your response @scarre sorry, i am super new to this. i am running deconz in a docker-container. guess i will switch to install it directly or is there a way to get #5405 on docker?

i try to investigate further into it.

scarre commented 2 years ago

If you don't want to mess around with your live setup, you could recompile the lib in another container or similar setup, and just copy it to your live setup when done. Full instructions to recompile are here : https://github.com/dresden-elektronik/deconz-rest-plugin Just make sure that you checkout and modify the version corresponding to your current setup.

bmgit26 commented 2 years ago

BTW, is the current configuration from #5404 meant to stay like that?

I mean everything is "working", but in HomeAssistant there are quite a few glitches that make it differ from other thermostats:

Is this on HomeAssistant or deconz? I tend to say deconz, as my other thermostats work nicely in homeassistant.

Thanks Max

herrmarten commented 2 years ago

@scarre thank you so much again for your advises. i tried around, compiling the restplugin etc. but i ran in multiple different problems even after compiling successfully. i ended up unpairing all devices by accident by starting zigbee2mqtt to change the windowopen_set via zigbee2mqtt (which worked) ... i just finished pairing the devices i had paired to deconz before. luckily it were just a few. most is still on huebridge (as i said, i am quite new to using an own solution)

github-actions[bot] commented 2 years ago

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.

github-actions[bot] commented 2 years ago

As there has not been any response in 28 days, this issue will be closed. @ OP: If this issue is solved post what fixed it for you. If it is not solved, request to get this opened again.

bmgit26 commented 2 years ago

Any idea why this thermostat is not behaving as others in Home Assistant? (https://github.com/dresden-elektronik/deconz-rest-plugin/issues/5386#issuecomment-1034654864)

Smanar commented 2 years ago

Hello. The DDF core will be able soon to support Tuya cluster, so I don't think the PR will be merged.

But If you want to try using DDF I can help you, but you will be the first one, not sure how far we can go. You need a recent deconz version, the new code is not yet in stable https://github.com/dresden-elektronik/deconz-rest-plugin/pull/5868

bmgit26 commented 2 years ago

I'm now on deconz 2.15.0 beta, this #5868 should be in this one?

at least I can see it in the changelog of raktak/2.15.0beta

Smanar commented 2 years ago

Yep it was in it DDF support Tuya manufacturer specific cluster https://github.com/dresden-elektronik/deconz-rest-plugin/pull/5868

So can start a DDF, as it will be nor reconized at all, you will have to set all the DDF. You have a video here https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/DDF-cheat-sheet

Now the device will be reconised as thermostat, but not working at all.

Can you copy paste the DDF, I will edit it to add the temperature and the offset (I will try at least)

bmgit26 commented 2 years ago

Hey @Smanar, thanks a lot, I will definitely give this a try but dont know exactly when i can get to this. Most likely on Friday or the weekend.

tebeso commented 2 years ago

So whats the state? Just bought the same and have the same problem. Should i return it and get another device? (if yes, which works and also with which api endpoint do i control these things?)

Smanar commented 2 years ago

There is a PR in waiting list to support tuya TRV using DDF.

Getting another device is hard because tuya make so much clone, almost impossible to be sure having the good one. On the code as supported natively Tuya TRV there is

    // Tuya Thermostat / TRV
    {"_TYST11_zuhszj9s", "uhszj9s", "HiHome", "Tuya_THD WZB-TRVL TRV"},
    {"_TZE200_zuhszj9s", "TS0601", "HiHome", "Tuya_THD WZB-TRVL TRV"},
    {"_TYST11_KGbxAXL2", "GbxAXL2", "Saswell", "Tuya_THD SEA801-ZIGBEE TRV"},
    {"_TYST11_c88teujp", "88teujp", "Saswell", "Tuya_THD SEA801-ZIGBEE TRV"},
    {"_TZE200_c88teujp", "TS0601", "Saswell", "Tuya_THD SEA801-ZIGBEE TRV"},
    {"_TYST11_ckud7u2l", "kud7u2l", "Tuya", "Tuya_THD HY369 TRV"},
    {"_TZE200_ckud7u2l", "TS0601", "Tuya", "Tuya_THD HY369 TRV"},
    {"_TZE200_ywdxldoj", "TS0601", "MOES/tuya", "Tuya_THD HY368 TRV"},
    {"_TZE200_fhn3negr", "TS0601", "MOES/tuya", "Tuya_THD MOES TRV"},
    {"_TZE200_aoclfnxz", "TS0601", "Moes", "Tuya_THD BTH-002 Thermostat"},
    {"_TYST11_jeaxp72v", "eaxp72v", "Essentials", "Tuya_THD Essentials TRV"},
    {"_TZE200_jeaxp72v", "TS0601", "Essentials", "Tuya_THD Essentials TRV"},
    {"_TYST11_kfvq6avy", "fvq6avy", "Revolt", "Tuya_THD NX-4911-675 TRV"},
    {"_TZE200_kfvq6avy", "TS0601", "Revolt", "Tuya_THD NX-4911-675 TRV"},
    {"_TYST11_zivfvd7h", "ivfvd7h", "Siterwell", "Tuya_THD GS361A-H04 TRV"},
    {"_TZE200_zivfvd7h", "TS0601", "Siterwell", "Tuya_THD GS361A-H04 TRV"},
    {"_TYST11_yw7cahqs", "w7cahqs", "Hama", "Tuya_THD Smart radiator TRV"},
    {"_TZE200_yw7cahqs", "TS0601", "Hama", "Tuya_THD Smart radiator TRV"},
    {"_TZE200_cwnjrr72", "TS0601", "MOES", "Tuya_THD HY368 TRV"},
    {"_TZE200_b6wax7g0", "TS0601", "MOES", "Tuya_THD BRT-100"},

Else can use TRV but from other brand than tuya, missing models can be added using a DDF

WhiteBahamut commented 1 year ago

tl;dr: Not sure if people still look for that. My ConBee II detect the thermostat, but does not show it in the sensors (or anywhere else).

I can access the sensor via the API and set config values. Also HA detects the sensor and I can set temperatures. In HA the "heat" and "on/off" button do not seem to work. Also switching to preset modes seems doable. Tho I dont know what the buttons and the modes should ;D It would be great if the Phoscon PWA would also show the sensor. I had 3 tries until I realized it was added but just not displayed (added via the PWA). For completeness I post my sensor

{
  "config": {
    "battery": 100,
    "heatsetpoint": 700,
    "locked": false,
    "offset": 0,
    "on": true,
    "preset": "auto",
    "reachable": true,
    "schedule": {},
    "schedule_on": false,
    "setvalve": true,
    "windowopen_set": true
  },
  "ep": 1,
  "etag": "xxxxxx",
  "lastannounced": "2022-09-28T20:46:26Z",
  "lastseen": "2022-09-29T13:55Z",
  "manufacturername": "_TZE200_jeaxp72v",
  "modelid": "TS0601",
  "name": "Thermostat 3",
  "state": {
    "lastupdated": "2022-09-29T12:46:54.682",
    "on": false,
    "temperature": 1760
  },
  "type": "ZHAThermostat",
  "uniqueid": "xxxxxx"
}
Smanar commented 1 year ago
  "manufacturername": "_TZE200_jeaxp72v",
  "modelid": "TS0601",

This device haven't the config/mode so action like heat/on/off are not available, but preset yes.