core: MoesGo WiFi Thermostat is not properly controllable using the new Tuya integration
The problem
I have 4 thermostats, and all of them not only report incorrect temperature but also do not allow to change the operation mode from HASS. The operation mode is always off
, and the temperature is 5 times less than set on the thermostat.
With the previous version, everything was warning like a charm.
What is version of Home Assistant Core has the issue?
2021.10.0
What was the last working version of Home Assistant Core?
2021.9.7
What type of installation are you running?
Home Assistant Container
Integration causing the issue
Tuya
Link to integration documentation on our website
https://www.home-assistant.io/integrations/tuya/
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
I tried collecting the device info/specifications as described in https://github.com/tuya/tuya-home-assistant/wiki/How-to-get-the-log, but the current logs do not show any info like this.
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 46 (11 by maintainers)
Home Assistant 2022.2 (now in beta, feel free to join!), will have a diagnostics dump tool on the device page, which contains information to share in issues like these.
It can be helpful if all of you having issues with these MoesGo thermostats posted their diagnostics results here. I will allow finding a solution (or worst case, conclude there is none).
Thanks Frenck for all your work
Update on the Tuya Developer IoT Platform / App solution:
UPD 01.27: I got a message that the delay in response is due to the Chinese New Year holidays, which according to the web are:
@frenck, thanks for the update anyway.
Any chance you can add some temporary ugly workaround for 2021.11? Like an option to add an attribute
__tuya_multiplier
for a thermostat entity via customizations. If Tuya decides to shut down the old API before the fix is ready — everybody using the affected thermostats will have to update their automation to adjust the temperature.P.S. I wonder how the Smart Life app works appropriately while the API has no idea about the multiplication. Also, I’m surprised that the temperature displayed in HA has to be multiplied by 5, while the temperature visible in Tuya IoT debug has to be divided by 2 to get the correct temperature 😃
Well, I have some more information. As it seems, this device has customizations, specifically for this manufacturer/device. Thus isn’t supported/being able to support the cloud API (according to Tuya).
This makes it hard to implement. From an API consumer perspective (Home Assistant), we currently do not have a way to differentiate between this device and others.
I’ve added some extra information in the upcoming Home Assistant release, that might help to find and implement a solution. But this means for 2021.11, this issue won’t be fixed.
same issues with MoesHouse BHT-002-GBLW WiFi thermostats and SASWELL SEA801 / SASWG-01-RF-WiFi thermostats:
Hi Franck! Thanks indeed! Mine diagostic file is here: https://gist.github.com/alexanderznamensky/5168b2031998e7221cf93f7c7e897043
Thank you, Franck, for not giving up on us! 😃 Here’s what I have: https://gist.github.com/andrey-yantsen/fbf856451e0b0b36c269d334a04d36a9.
Target temperature = 19 ºC Current temperature = 21.5 ºC
@alexanderznamensky yeah, I set it up yesterday, working like a charm. I used values from https://github.com/rospogrigio/localtuya/pull/548#pullrequestreview-793253904 but removed the mode control altogether as it was somewhat broken for me. I’m using Schedy anyway, and just set the required temperature to 19ºC when don’t need the heating.
I don’t think I would be able to help you with any questions, but it definitely will be better to continue the discussion in the PR to LocalTuya and not here, to avoid being too much off-topic.
P.S. During the config flow the integration was failing to add the device, but after a few more attempts — it was indeed added.
@mowl111 nope, unfortunately, it’s not really possible. As it was said multiple times, Tuya will deprecate the old API sometime soon, and the old integration will stop working. You can try raising a ticket with Tuya (via their https://iot.tuya.com interface), but the chances are low.
As an alternative, you can use LocalTuya — they just released thermostat support today, or you can use the old integration via HACS, installing it from the repo andrey-yantsen/home-assistant-tuya-old.
Hi, I also need this one to work (for BHT-002-GCLW).
According to these tickets, it’s not very optimistic: https://github.com/tuya/tuya-home-assistant/issues/361 https://github.com/tuya/tuya-home-assistant/issues/502 https://github.com/tuya/tuya-home-assistant/issues/676 https://github.com/tuya/tuya-home-assistant/issues/675 https://github.com/tuya/tuya-home-assistant/issues/670 https://github.com/tuya/tuya-home-assistant/issues/547 https://github.com/tuya/tuya-home-assistant/issues/542 https://github.com/tuya/tuya-home-assistant/issues/535 https://github.com/tuya/tuya-home-assistant/issues/502
The main problem for me is that
current_temperature
is not reported at all.Well, that’s understandable, but I had to try 😃
Thanks!
P.S. Don’t hesitate to poke me if you’ll get any ideas on how I can assist here.
@frenck yup, sorry, I forgot about it. Added to the original comment. set=23º, current=22.5º.
Hey @frenck! Thanks for the update!
I just tried the latest dev build available in docker (2021.11.0.dev20211016), and actually, it’s become a bit worse than with stable version 😃
Now I can turn the thermostat off and on, but it’s pretty much all I can do: