Zigbee Radiator Actuator / _TZE200_cpmgn2cf / TS0601 #7139
Comments
llugo
changed the title
|
Apparently this is a dupe of #6381 (comment) |
|
@Smanar still not possible |
|
Can try this DDF The dpid for mode can be 106 instead of 4. |
This is what i get from the API after loading the DDF, tried both dpid values (106 and 4) in "parse" and "write" lines in config/mode section... |
|
Lol ok, so it seem the DDF is working bu I have wrong for ALL dpid ? Can you enable log in deconz / help / debug view with flag "info"
|
|
|
This one need to be setheatpoint, and I m using same
It need to work .... Nothing special in logs using "DDF" and "info" ? You are not using HA or docker ? |
no just deconz v2.22.2. Somehow the device seems to pick up a wrong ddf when connecting... Screenshot after connecting the node: Screenshot after hot reloading Sreenshot after closing the DDF editor an opening it again DDF location ist /home/[USER]/.local/share/dresden-elektronik/deCONZ/devices/tuya/ |
|
Ok, I think you have more than 1 DDF for the same device. You have one called tuya_ts601.json and one called _TZE200_cpmgn2cf.json |
|
Oh good point. |
|
This is the API response now. EDIT: |
|
So 260 * 10 give 2600, nothing strange ! Still no value for temperature ? if not you can enable the flag "DDF" in same time. |
After doing some more API requests, it's reporting temperature correctly now! Great! @Smanar Thanks a thousand once again! |
|
I m just seing this device have native support in c++ code
IDK why it haven't worked ... Perhaps because device detection is harder without DDF. And this device haven't battery support, so bad you have Edit: |
|
I changed batteries, API response now looks like that: Just to double check for "integral" deCONZ support I removed the DDF file then deleted the node then restarted deCONZ and reconnected the node. EDIT: just saw you edited your comment... |
Interestingly, altough "lowbattery" is reported as false deCONZ shows a low battery symbol: |
|
deconz can't get battery level, this device is a tuya one, nothing standard.
Ha nice the value was updated (it's no more "null'), it was good or bad battery ? |
Oh, I see.
I'm not sure what you mean with good or bad battery? |
If you have used full battery it's ok (because we had `"lowbattery": false,) but if you have used empty battery (to simulate a low battery), the value is reversed ^^. |
|
Sorry but apparantly the case isn't closed i'm afraid. Besides connecting it, and changing battereies i never changed anything on the device itself. edit: I didn't change anything in deconz nor the ddfs after my last post, when it was working and the device audibly turned the valve after changing heatsetpoint |
|
Wasn't the max 2700? |
Yeah i can only say that when I initially tested it temps where about 2400 or so, so that would explain it. edit: when setting it to 2650 it also jumps back to 1500 quickly. But this might be because measured temp is above heatsetpoint? |
|
You haven"t other mode to try ? And BTW, note for later : remove the "config/battery". And this device probably support "preset" The DDF need to be in the same folder than "tuya_trv_preset_set.js" |
Ok, i tried to change things on the rather complicated UX of the device itself.
After having a look at I'll try adding the preset lines to the DDF. |
Looks like this worked! It is possible to change the preset to 'manual' via an API request. So if my hypothesis about 'auto' mode, which i hereby expand to 'eco' mode, is correct it should work now. We'll see! |
|
I will be happy if you can describe the working mode for next time ^^, not something evident for tuya. In my mind you need to have mode=auto (for the device auto regulate the temperature) and preset=auto too ? |
|
So, after waiting for a day just to see if anything changed, the preset 'manual' is still set and i can set the desired heatsetpoint.
'Mode' seems useless yes. While trying different things on the device again I still didn't get any other value for 'mode' than 'off'. |
Yes, surely, so the actual DDF need to be |
|
It's probably bad since it's my first attemp at writing a bash script with more than 5 lines, but anyways:
It was only tested with OPs device on Raspian buster. Needs curl and jq. edit: I'd be glad if someone had a look at it or even could suggest improvements. |
|
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. |
|
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. |
|
@Smanar my bad all the time i was using above json only, sorry for the confusion.
|
|
State/valve is a bool, so it can be only true or false, the DPID 109 is a bool too.
|
|
@Smanar is there any way to get this Information? I am happy to do some tests if you want to try out something |
|
But you need to have it using This value don't move from true to false ? |
|
This works fine as you described, it is 0 when closed and 1 when open. I just checked the zigee2mqtt docs and found that valve open percentage is not readable. They have 3 values for this as described below If all you need is to control on and off, you can set "force" with topic zigbee2mqtt/FRIENDLY_NAME/set. The payload values are: Can we achieve something similar? |
|
You have the z2m doc page ? (so much clone with tuya) |
|
@Smanar On the other thread I also found that the %valve is being read and displayed in HomeAssistant, I was quite amazed to see that. I have asked for details on the used integration, but I haven't got any response yet. |
|
So on your page I can read there is a valve detection but it don't mean "valve position" ? |
|
Perfect, See what i got in the response. Thank you @Smanar |
|
@Smanar for both config/locked and config/windowopen_set
|
|
Do you have the GUI ? |
|
for windowopen_set via api change on trv |
|
When you have changed it on the TRV, nothing was returned, dpid 0x03 is only temperature report. You can enable APS log (need APS+APS_l2), you will see something
Will be the raw request, but I m almost sure it will finish by 00 01 12 01 00/01 Your device probably don't support it, or use a different dpid. |
|
I shared here the logs, not sure if this helps. To be honest, if this does not work, its ok. However, I wanted to know if there is any way to open/close the valve from API, without using preset? Something like force operation is described here. message from francisp https://www.zigbee2mqtt.io/devices/TS0601_thermostat.html Other set operations are also useful like set schedule set comfort and eco temperature and boost time. |
|
Those TRV are not designed to work like that, to prevent battery drain, it's lazy device. You set a heatpoint and the device work alone and you don't touch it, if you don't like it's regulation, try another TRV. To know if this device support for exemple the "lock" feature, You need to see it in logs when you use it manualy.
It's the dpid 0x12 for the "lock" We can use too the 'config/unoccupiedheatsetpoint' to set a second heatpoint, but IDK how work this device. Do you want to use comfort or eco ? it work with preset ? |
|
In the post above for z2m it is the same trv being used and they have implemented the force opening/closing the valve. How do you conclude that trv is not designed to work like that? I used preset (set via API )and they work as expected, no issues there. Anyways the main question here is to control the valve forcefully, sample below from z2m. |
Just make a try yourself. The "force" mode is the dpid 106, type enum, value 0 - normal, 1 - open, 2 - close I m agree "config/interfacemode" is ugly, but mode and preset are already used, and the one resting are not famous, make a test, create a new field will be easier after, on last DDF version you can create "custom" field. But it 's just a mode, like 0 - auto, 1- heat, 2 - off Edit |
|
I'm also interested to get the _TZE200_cpmgn2cf working with deconz. I also have the Tuya Zigbee hub running with the tuya adapter on iobroker. If relevant for support I can share data points generated by the tuya dapter in iobroker... |
|
Hello can try this DDF |
Device
Screenshots
Endpoints and clusters of the node
Node Info panel
Cluser info panel
Additional Notes
Since there is a "Generic Tuya TRV DDF" (#6829) which I unsuccessfully tried to load on the device, I thought I'd give it another chance here.
It was bought here: https://www.aliexpress.com/item/1005002212605653.html?spm=a2g0o.order_list.order_list_main.5.54a85c5fRUkOms&gatewayAdapt=glo2deu
The text was updated successfully, but these errors were encountered: