[Device Support Request] TS0601 Thermostat #1109
Comments
|
Its looks like one that is partly supported by one quirk that one user have doing. You can try installing that quirk as local quirk and adding your device manufacturer and model ID in the signature and see if its working OK. |
Thanks, I did this and did a reconfigure and it did add a thermostat entity however this does not work with my device. The status is not updated when changed either in HASS or on the device. Any button presses in the thermostat lovelace card does nothing, so unfortunately I don't think this quirk works for this device. |
|
Do ZHA loading the quirk (you is getting one thermostat on the device card) ? restarting HA and then its stable take the power from the thermostat for one minute and putting it back. That is all commands is using and can being used for making one working quirk for it. |
|
@monstermuffin Did this work? I've got the same Thermostat so I'm very curious |
|
@monstermuffin @karel314 Someone need to enable debug mode in configuration.yaml and resend the pairing log. Without it we see nothing. We need some effort form the user to write 500 lines of code - you understand that. |
I have not no.
I'm sure the pairing log in this first post was what was required but I can resend a new log no problems. Should I leave the non-working ZHA quirk enabled for repairing or remove it? |
Please leave it Please also enable debug logging in configuration.yaml and the resend pairing log. But please take the log not from the pairing window, but from HA LOGS. It should look lie this: |
Thanks for your help, I've removed the device and readded using the logger settings you provided. Here is the log output: https://paste.muffn.io/?3da32eb4a22ae629#FarV8cRE8gXzcuRrou2Csr53NLNvXBVTkexw7Nkfg4QW @karel314 Might be worth you also doing one with your Thermostat? EDIT: Added a better log with more time after adding the device. |
|
Actually that didn't help. There's actually no data from the Thermostat in the logs. There were totally no data after this. Or, if it has that function, make reset after pairing, or even take out and put in batteries. |
|
Looks only one zhaquirks.tuya request is being made: |
Thanks for all your help. I just removed the device and readded it, I let it sit for a while during which time I power cycled it a fair few times (the device is mains powered.) Doing a search for https://paste.muffn.io/?f0c01dc52d424164#Bd62Mg57WqXGLWkccMuGbsujLjovo85pLrBiqkXHwnPN
I am almost certain it's being loaded, as without it I do not get any entities, and with it I get the entities but they just do nothing. I can see the following lines in the log linked in this post too:
|
|
After some text magic we got kinda unique 90 lines |
Excellent, I was hoping those lines would be helpful and was referencing the right device! |
|
I see that the user in Z2M used typical Moes code Please do some test:
Try to debug yourself also a child lock. Enable/Disable and search for [0]/[1] as a return value. |
|
Switching between AUTO and Manual: Changing temp: I actually have no idea how to engage the child lock, I've done it before by accident and not been able to remove it without a power cycle, so let me try and find the documentation and I will follow up with more logs on the child lock. |
|
Child lock logs: Setting child lock ON: Setting child lock OFF: I think these are the right log lines based on the times I turned the lock on/off and your comments on what to look for. |
|
So we still have problem with LOGS. |
My child lock logs here use 0x0128? #1109 (comment) Unless I'm missing something? |
|
Also oddly enough I do not see a value change when switching modes, 0x0101 is always [1] with AUTO and Manaul modes when looking at 0x0101. |
|
Yep, but the logs above DOESN'T contain any 0x0128. So if we missing one, probably we are missing lot more. Just switch Manual/Auto and search what changes [0]/[1] |
Okay so I believe MODE is Manual: Auto: |
|
https://github.com/zigpy/zha-device-handlers/blob/dev/zhaquirks/tuya/ts0601_trv.py |
Okay we seem to have some kind of functionality happening.
The temperature and target temperature is now being read, and the flame button does wake the device up. Target temp/real temp seems to be divided by 10 for some reason which is screwing with some things, so 21c is showing as 2.1c, and the target temp is also doing the same. I think I will need to modify the modes in the quirk too as the logs I showed do not align with the quirk, the mode button currently does nothing on that panel. This is some great progress though thank you so much for your help so far! |
|
Ok. So you still need a modified quirk. But most of the attributes shares same numbers |
|
@monstermuffin How the status of your Thermostat? If you don't have it working we could now take care of that device. |
Hey, I have been rather busy recently so it's not gotten any further from where we got last time, so it's not working as of yet. |
|
I'll try to write some code then. Will get back with dev version |
|
@monstermuffin put that file below in the quirk folder. |
|
@jacekk015 thanks again for all your help. I removed the device, added the quirk, restarted and readded the device and now have different behaviour: I get entities as follows: number.tze200_ye5jkfsb_ts0601_3a927cfe_analog_output_temperature_calibration - This silder appears to change the 'real temp' on the thermostat. Slider is very odd. switch.tze200_ye5jkfsb_ts0601_3a927cfe_on_off - This enables/disables the child lock. climate.tze200_ye5jkfsb_ts0601_3a927cfe_thermostat - Seems to be what the target temp is but this does not work, always reading '0.2'. sensor.tze200_ye5jkfsb_ts0601_3a927cfe_thermostat_hvac_action - This stays 'off' regardless of what is pressed on the thermostat, or if the thermostat is set to higher/lower than current temp. Here is a big log file: https://paste.muffn.io/?add92e04b795497c#FU6GrENForqFBsUbHz82pYTEaqVDwcqhhm3Sj5EFs9nu When changing the setpoint on the thermostat, these appear to be the relevant log lines: |
|
@monstermuffin Nice job! Will write some findings in a moment. In the logs I've found few attributes that Zigbee2Mqtt didn't present, but your device presents them - symbols:
It changed here -> Received value[0] from [1]: Here again [1]
Maybe you can play some switches/options and check logs for changing values. [edit]
Didn't touch it right now. If we find some attribute, above, that Thermostat sends we can use it to signal that. |
|
@ssalorinne HVAC action state is based on the attribute 0x0424 Thermostat has some icon to show on/off state of heating. BTW you have very low LQI [Link Quality] - that Thermostat is probably far from other device/router or controller. |
|
Regarding the question of the device not setting the date/time automatically, I have pasted the debug log here: https://pastebin.com/ua1CBqaP The device has name climate.zolder_rob_avatto_thermostat, the log is just before the re-pairing until a couple of minutes after the re-pairing |
|
Regarding the question from @ssalorinne about the icon to show on/off state of heating.. here is debug log, I changed temperature several times from 10 to 26 to 10 and the heating icon shows/disappeared |
|
@RobDaPraia I've added, in quirk below, EnchantedDevice class. |
|
@RobDaPraia @ssalorinne |
|
Thanks for the update. Unfortunate it sems that the datetime doesn't get adjusted. Then we have to stick to manual update. I did the following: Install the new ts0601_thermostat_avatto.py Anyway, thanks for the update |
|
It seems that the Heating/Idle is inverted? When I set the target to a lower temperature, the thermostat changed to heating Then setting the target to a higher temperature, the thermostat changed to idle |
|
Unfortunately for me the latest version does not seem to work at all. The device pairs succesfully, but nothing works.
Pairing starts at 15:31 after which I try to change values and turn on the childlock. Also note that the default value for the calibration is back to NaN. The only remaining issue I had with the previous version was that the heating status was shown as always on if the thermostat was on. On my other devices it shows heating (with the flame icon) when the relay is actually turned to the on position. For automations it would help if this can be corrected. |
|
@ssalorinne BTW How it's possible to not work if same TRV on that code works for @RobDaPraia ?? |
|
I have seen its version of this device and i hope they is having the same firmware version on the MCU. |
|
@MattWestb ssalorinne has device_version = 1 |
|
That is the version of the Zibee module. zha-device-handlers/zhaquirks/tuya/__init__.py Lines 43 to 44 in a16c153 And one function is here: I dont knowing how its working but some have getting the version from the MCU. |
|
@RobDaPraia For Heating/Idle is inverted - corrected in the file below. @ssalorinne Lets clarify this. AVATTO users gave me specific attribute to make it on/off Corrected quirk below: |
|
@jacekk015 Thanks Didn't know I had to remove the device, ok, now I did the following, see attached log
At this moment the thermostat did not work in HA. But after I switched off/switched the thermostat device, the thermostat started to work in HA It seems that thermostat in HA is working correctly:
Unfortunately, datetime is not set, so have to do that manually once |
|
Some screenshot of the card with heating/idle/off, seems good
|
|
@RobDaPraia Looks good. Magic packet for date/time sync was sent on initialization process: Thermostat just doesn't respond to that, and also don't ask for time sync. If you're happy with results remember to disable DEBUG level logging. |
|
Was looking in the current quirk and is 2 devices that looks working better with this quirk If not getting feedback we is leaving the Great work done !! |
|
Z2M uses same code for those TRV's And also have other for _TZE200_2ekuz3dz Becasue they are 80-90% compatible [I mean attributes] I made it in just one quirk. |
|
The original Becca is your first from Z2M and we is only having the first one. and one is having device class with ZGPP endpoing but i think all other is without. Edit: |
|
If you are sure about this I can add them to the quirk. |
|
Z2M Avatto from https://github.com/Koenkk/zigbee-herdsman-converters/blob/29f1f442e981db8d5138cde930387d5fc4c52454/devices/moes.js#L98-L105 You have one with ZGPP OK. |
Hi! I have tested this quirk with my _TZE200_u9bfwha0. Added my device id to the Avatto section, Beok did not work at all. Most things seem to work.
|
|
@JonasEnstrom80 Enable debug logging. Restart HA. Remove device. Pair like new one. Wait still up to 10 minutes. Post HA logs as a file. Don't cut anything from logs. |
|
Here are my loggs. Found 1 more issue. |
|
@JonasEnstrom80 It's not a bug, not in the quirk. Maybe you can set half degree on the Thermostat, but that half is missing in transmission to HA. Even when you sent it from HA: |
|
@JonasEnstrom80 |
|
Room temp reading is working as it should now. Thanx! |
Is your feature request related to a problem? Please describe.
I would like to use this thermostat with HASS via ZHA. When added via ZHA the device is added but no entities are created.
This is the thermostat I ordered: https://www.aliexpress.com/item/1005002960679997.html?
Describe the solution you'd like
Ideally all functions would be available, including creating/modifying the timers, however this can be done via HASS easily enough so at a minimum being able to turn on/off the heating and read the temperature value would allow for basic functionality.
Device signature:
Logs after adding new:
Additional context
N/A
The text was updated successfully, but these errors were encountered: