Tuya thermostatic valve #3821
Comments
|
Can you share the |
|
Hi, sure here are entries for 4 different devices |
|
Thanks, asked for some help in #2778 (comment) |
|
Same issue here: {"id":5,"type":"EndDevice","ieeeAddr":"0xbc33acfffe6eb997","nwkAddr":8048,"manufId":4098,"manufName":"_TZE200_ckud7u2l","powerSource":"Battery","modelId":"TS0601","epList":[1],"endpoints":{"1":{"profId":260,"epId":1,"devId":81,"inClusterList":[0,4,5,61184],"outClusterList":[25,10],"clusters":{"genBasic":{"attributes":{"modelId":"TS0601","manufacturerName":"_TZE200_ckud7u2l","powerSource":3,"zclVersion":3,"appVersion":83,"stackVersion":0,"hwVersion":1,"dateCode":""}}},"binds":[]}},"appVersion":83,"stackVersion":0,"hwVersion":1,"dateCode":"","zclVersion":3,"interviewCompleted":true,"meta":{},"lastSeen":1593875683098}
{"id":6,"type":"EndDevice","ieeeAddr":"0xbc33acfffe6d7fef","nwkAddr":2904,"manufId":4098,"manufName":"_TZE200_ckud7u2l","powerSource":"Battery","modelId":"TS0601","epList":[1],"endpoints":{"1":{"profId":260,"epId":1,"devId":81,"inClusterList":[0,4,5,61184],"outClusterList":[25,10],"clusters":{"genBasic":{"attributes":{"modelId":"TS0601","manufacturerName":"_TZE200_ckud7u2l","powerSource":3,"zclVersion":3,"appVersion":83,"stackVersion":0,"hwVersion":1,"dateCode":""}}},"binds":[]}},"appVersion":83,"stackVersion":0,"hwVersion":1,"dateCode":"","zclVersion":3,"interviewCompleted":true,"meta":{},"lastSeen":1593875621151}
{"id":7,"type":"EndDevice","ieeeAddr":"0xbc33acfffe6d80cf","nwkAddr":29801,"manufId":4098,"manufName":"_TZE200_ckud7u2l","powerSource":"Battery","modelId":"TS0601","epList":[1],"endpoints":{"1":{"profId":260,"epId":1,"devId":81,"inClusterList":[0,4,5,61184],"outClusterList":[25,10],"clusters":{"genBasic":{"attributes":{"modelId":"TS0601","manufacturerName":"_TZE200_ckud7u2l","powerSource":3,"zclVersion":3,"appVersion":83,"stackVersion":0,"hwVersion":1,"dateCode":""}}},"binds":[]}},"appVersion":83,"stackVersion":0,"hwVersion":1,"dateCode":"","zclVersion":3,"interviewCompleted":true,"meta":{},"lastSeen":1593876100210}
{"id":8,"type":"EndDevice","ieeeAddr":"0xbc33acfffe6ec1cc","nwkAddr":38004,"manufId":4098,"manufName":"_TZE200_ckud7u2l","powerSource":"Battery","modelId":"TS0601","epList":[1],"endpoints":{"1":{"profId":260,"epId":1,"devId":81,"inClusterList":[0,4,5,61184],"outClusterList":[25,10],"clusters":{"genBasic":{"attributes":{"modelId":"TS0601","manufacturerName":"_TZE200_ckud7u2l","powerSource":3,"zclVersion":3,"appVersion":83,"stackVersion":0,"hwVersion":1,"dateCode":""}}},"binds":[]}},"appVersion":83,"stackVersion":0,"hwVersion":1,"dateCode":"","zclVersion":3,"interviewCompleted":true,"meta":{},"lastSeen":1593876848311} |
|
Thanks for solution. How did you fix auto Discovery? something like this? or more options? |
|
Added support for this device out-of-the-box now. Changes will be available in the latest dev branch in a few hours (https://www.zigbee2mqtt.io/how_tos/how-to-switch-to-dev-branch.html) |
|
@Koenkk It there any ETA when this will be in the master branch? |
|
@damianpasek it's in the just release zigbee2mqtt 1.14.2, please let me know if it works there. |
|
@Koenkk they are now correctly added to Zigbee2MQTT but at least on Hassio with the addon they are not working properly. on printscreen is what's added from it to my HA, And here on the operation mode I can only set correctly I'm currently using a CC2531 usb stick with 1.2 stack |
|
@Sthopeless good that it is discovered correctly now, I'm not sure if this has been implemented/susposed to work, hopefully others from this thread can help (I don't have the device + original gateway). |
|
Confirmed that valve was discovered correctly and integrated into HA with no (or maybe little?) problems. Right after pairing it is discovered as "cover" (browsed via z2mqtthelper), but after restarting z2m – it shows valve correctly and maked HA integration proper. I can confirm what @Sthopeless said – modes are not working best, but I guess it's more to do with converters than z2m itself. |
|
Same light switch as @Tontze which is supposed to be supported. |
|
I got the same thermostat valve from aliexpress. Mine has a Moes branded box with model number HY368. Maybe add that on the wiki page too? I had to troubles joining the network. Joining the network is explained to work after "short press home (turn on), long press home (enter settings), go to setting 5 (wifi logo), press home (only wifi now showing), long press home (wifi now blinking). I then pressed home every few seconds as it seems to timeout pretty fast. But it never joined the network. Unscrew/rescrew the battery cover suddenly did the trick, it just joined, even I tried that a few times before. |
|
Hi, I also got the two MOES and installed them a few days apart. The one issue I have is that the devices an "AUTO", a "MANUAL" and a "HOLIDAY" mode and if I setup the temperature manually it reports the system mode as "manual" and this generates a log into the HA. I guess this also have something to do with the available modes in the HA for the Climate/MQTT component. The following configuration mode is sent: There seems to be also a firmware difference between the two because one sends also the "auto" configuration for the weekdays and holidays through the main topic and the other one doesn't. |
|
Hi guys, I also have 6 moes branded TRV (TS0601 thermostat ), they all first appeared as curtain motor, but eventually got them to show up as TRV in HA. I have some issues with the mode settings as well. I found out that it's not possible to turn the valves into 'manual' mode unfortunately. To put/hold the TRV in manual mode you have to adjust it on the TRV itself, and only change the temperature trough HA ( so don't do anything with the modes). Battery status is also not working for all 6 off the valves. |
|
Hey, I'm currently working on making some changes to this thermostat implementation. One of them is using Presets instead of Modes. List of modes is fixed set in home assistant so it's not good to use them. Presets are open so you can put there whatever you want.
|
|
@mgrom Nice work!! This would be a perfect solution to put the TRV remotely into manual mode. |
|
Guys,
regarding point 2: mine device was sending temp updates infrequently and skipping some of steps in between like in mine example. So, I was looking for solution, how to force device to make it more often. I've found a way to do that, just send: |
|
Hi,
Curious when your changes will be implemented in the stable version of zigbee2mqtt. Thanks, |
|
@Bart-1992 I've made simple automation: Just change minutes to anything fits you. The same with payload. Finally change topic and make action to run for all your trvs No idea when my changes will be implemented :) sorry, but I'm just a gust here :D One more question:
|
|
Hi @mgrom, I have not tested the schedule mode on the TRV itself, i'm also not planning to use it. There probably is a cheap bad functioning RTC module inside.... if there even is a RTC module allready.... I've implemented your automation, it's working perfectly ;)! However, I have some issues, check the log :
It gives a strange error about siterwell GS361 conversion? I'm not that into Zigbee2Mqtt's internal functioning, but it looks like it's not recognizing it properly? Do you know what it means? Thanks, |
|
@Bart-1992 can you give me some previous messages? I didn't get dp 366 so far. Is it often? about automation, I've found out that it's enough to call this command between 10 and 20 minutes - depends on environment (air conditioning etc), maybe during winter it will be better to call it more often to react on open windows. |
|
Check the log : It appears pretty often as you can see. In this log it's only appearing on the same TRV(0x842e14fffefd9bbe), but in my previous post it was another TRV (0x842e14fffef6ea3e) Indeed maybe 2 minutes is a bit too often, don't know if the battery will drain faster?
|
* Added presets (hold_modes) to climate sensor #3821 and removed thermostatHeatCool as it's partially redundant * Added new configuration to TuYa thermostat TS0601_thermostat * eslint fixes * Added eco and comfort modes. Looks like they are usable. * Update homeassistant.js * Update homeassistant.js Co-authored-by: Koen Kanters <[email protected]>
|
Thanks a lot @drzony , but it doesn't work 😞 . I tried to use the latest dev: but there's exactly the same behavior. I am happy to provide more debug info or even try to code it somehow by myself, but not sure where to start.
it seems like @mesoulrock problem above #3821 (comment), but my model says |
|
@hnykda |
|
Oh, that's really promising, thanks. Do you happen to know if it's possible to add it with the hass.io z2m add-on somehow? Cannot find anything in the docs nor in the filesystem. I guess I will just wait. |
|
#6987 (comment) |
|
OK, then I am doomed, I cannot access the host and hence docker and blabla... Will wait till it's merged, again, really appreciate your work 🙇 |
Hola, tengo el mismo problema. Alguna solución? |
|
Come on people do not be so selfish. Keep it English. |
|
@jmarfer It is easy today using automated translation:
And I don't think that new revision has been implemented yet. Have you tried adding the Manufacturer ID to the old Moes TRV? From the pictures the feature set should be similar. It is worth a try. |
|
I think the same its very likely only one updated display but cant being 100% sure before testing. |
|
Using old moes TRV code works partially: current_heating_setpoint in Z2M is always divided by 10 to what I've set manualy at thermostat. |
|
Good news!! I have managed to link the valve. In HA I have all these entities: image I don't know if the entities can be seen. Now I would have to test an automation to see that everything is going well Something to try? Thank you |
|
@ciB89 wrote:
That's kind of normal. The idea is to avoid that the valve shuts off when the room isn't already warm but only the radiator. I created a couple of automations to work around this and keep the room temperature very steady with the help of an external temperature sensor. More info in this thread, just a bit more up! :) @jmarfer wrote:
Great! To get a starting point for your automations, have a look at my repo: https://github.com/RubenKelevra/Tuya-thermostatic-valve |
The thermostat '_TZE200_b6wax7g0' is very different from its predecessors. Adapting is not an option. I have already completely recreated the converter for '_TZE200_b6wax7g0'. |
|
Spectacular work! It will help me for sure. Thanks! |
|
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days |
|
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days |
|
I can confirm that the firmware update button does indeed brick the TRV. |
|
I can confirm, too, that the Moes BRT-100_TRV Thermostat TS0601 _TZE200_b6wax7g0 is bricked by the firmware update. Same as @thebaron88 mentioned, "The radio will no longer pair and the device will then only be useable as a manual TRV." |
|
Please do not write in this topic, it is already closed. |
It's only closed by a dumb bot. Who cares? Just reopen it and delete the bot. |
|
This topic should really stay closed. Original issue was that this new device was not recognized yet a year ago. Since then it is misused with all kind of other improvements, issues, Q&A etc. Please open new items with clear issue descriptions, otherwise it is not possible to track these different items. Actually it will increase the chance that somebody will look into it and solve it. |
|
I know. It's not about because locked. |
|
Ah, sorry for poking this thread then, didn't see the other topic, just the unanswered post from bruvv. |
and others
Bug Report
What happened
New Tuya thermostatic valve was auto discovered in Zigbee2Mqtt 1.14.0 as Tuya curtain motor. Valve reports model as TS0601 which is occupied already in devices.js by Tuya curtain motor.
https://aliexpress.ru/item/4001043738901.html?spm=a2g0s.9042311.0.0.1b6033edHXNB4c&_ga=2.27185918.2138683156.1593276537-279917533.1590225196
I deleted TS0601 device in devices.js and repaired and got this:
Then I changed devices.js and added TS0601 as Tuya thermostatic valve and deleted curtain part, also fixed homeassistant.js for autodiscovery :
And thermostatic valve works correctly after this.
I bought 4 of them so could you please fix so it is correctly recognized out of the box.
Thanks!
What did you expect to happen
Valve autodiscovered as Tuya thermostatic valve which is actually similar to Moes.
How to reproduce it (minimal and precise)
Start pairing thermostatic valve.
Debug Info
Zigbee2mqtt version: 1.14.0
Adapter hardware: CC2538
Adapter firmware version: zStack30x
The text was updated successfully, but these errors were encountered: