core
core copied to clipboard
Tuya integration shows the wrong temperature values for my MOES thermostat.
See the solution in this link: https://github.com/home-assistant/core/issues/104164#issuecomment-1826135261
The problem
hello, I think I have the same problem. I have 3 MOES thermostats from aliexpress (https://es.aliexpress.com/item/1005005982273274.html)
The thermostats are set at more than 20 degrees Celsius and on your screen as well as in the "smart life" app they read 23 degrees. I am using tuya integration into my home assistant.
But in home assistan they show about 5 degrees. It is as if there is a scale error since the ambient temperature is also close to those 5 degrees.
When you put 4.2 grados centigrados they are real 21 When you put 4.9 grados centigrados they are real 24.5 When you put 5.2 grados centigrados they are real 26
3,8 ->19 3,9 ->19,5 4,0 ->20 4,1 ->20,5 4,2 ->21 4,3 -> 21,5 4,4 -> 22 4,5 -> 22,5 4,6 -> 23 4,7 -> 23,5 4,8 -> 24 4,9 -> 24,5 5,0 -> 25 5,1 -> 25,5 5,2 -> 26 5,3 -> 26,5 5,4 -> 27 5,5 -> 27,5 5,6 -> 28 5,7 -> 28,5 5,8 -> 29 5,9 -> 29,5
any solution?
What version of Home Assistant Core has the issue?
core-2023.11.2
What type of installation are you running?
Home Assistant OS
See the solution in this link: https://github.com/home-assistant/core/issues/104164#issuecomment-1826135261
Hey there @tuya, @zlinoliver, @frenck, mind taking a look at this issue as it has been labeled with an integration (tuya
) you are listed as a code owner for? Thanks!
Code owner commands
Code owners of tuya
can trigger bot actions by commenting:
-
@home-assistant close
Closes the issue. -
@home-assistant rename Awesome new title
Renames the issue. -
@home-assistant reopen
Reopen the issue. -
@home-assistant unassign tuya
Removes the current integration label and assignees on the issue, add the integration domain after the command. -
@home-assistant add-label needs-more-information
Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. -
@home-assistant remove-label needs-more-information
Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.
(message by CodeOwnersMention)
tuya documentation tuya source (message by IssueLinks)
I also have the same problem here with all my MOES thermostats.
I have not been able to solve it but by setting the step to 0.1 at least I can set the target temperature I want by applying this equivalence table:
3,8 ->19 3,9 ->19,5 4,0 ->20 4,1 ->20,5 4,2 ->21 4,3 -> 21,5 ...
To set the step to 0.1 you have to add this in the configuration.yaml homeassistant: customize: !include customize.yaml
in the customize.yaml climate.el_termostato: target_temp_step: 0.1
I hope that soon there will be a solution and we will be able to work with real temperatures.
See the solution in this link: https://github.com/home-assistant/core/issues/104164#issuecomment-1826135261
I have found many people with the same problem: https://github.com/home-assistant/core/issues/72703 https://github.com/home-assistant/core/issues/73612
There is even a module they have created to solve this: https://github.com/midstar/homeassistant_tuya_with_bht-002_support But in my case I have used another method.
https://github.com/home-assistant/core/issues/104164#issuecomment-1826135261
Solution here
I have found a CLON module of tuya that can be installed at the same time as tuya original. That is, you can have both modules installed at the same time!!!. This clone module works perfectly with MOES thermostats.
The steps I have followed are:
-
Add the repository in my HACS: https://github.com/AlessandroTischer/tuya_climate_mult_edit
-
Download in HACS "Tuya Climate Multiplier Edit".
-
In devices and services add integration "Tuya Climate Multiplier Edit".
-
We must configure this new integration data generated in app TUYA o SmartLife.
-
Here you can see an image of the thermostat integrated with the original application "yours" that wrongly marks the temperature, and just below the thermostat integrated with this application which marks well. So now you will have 2 thermostats, one correct and one incorrect.
As you can see in the image we now have duplicate devices, those of the original app and those of the clone. And we can use the one we want in our integrations. Being a separate module, the original can be updated whenever there is a new version.
THANK YOU, it's been a long time I try to fix this problem with my thermostat ! I didn't use Home assistant unti now because of this problem. Now I will shut down my old Jeedom box and use Home Assistant.
You're welcome, this solution has existed for more than 1 year, it just wasn't very widespread in the forums, etc... and with minimal instructions... let's see if now it's spread and people manage to fix this kind of errors.
I've been working with this integration for a week now and it's working perfectly! If you have the problem that your MOES thermostat does not dial correctly, here is a simple solution without losing the official integration. Because you can have both at the same time.
Hi, thanks, it works!!!!! What it is weird it's that even in the new proyect I have only 4 thermostat, in home assistant it is detecting all other devices in the tuya_climate_mult_edit integration. I have configured this integration with the new proyect, and Tuya module with the old one.
Regards, Carlos
I have heard that in the next update of homeassistant the official tuya app will stop working because from now on there is a new pairing system with the tuya app. You no longer have to enter the developers website, or create a project or anything ....
With the update 2024.2.0 the official integration of TUYA has changed the way of connection to yours servers. And as soon as this version is installed, the connection to TUYA integration is lost. But, good news, those of you who have the modified version for the thermostat MOES continues to work normally: https://github.com/AlessandroTischer/tuya_climate_mult_edit
3 hours ago the repository https://github.com/AlessandroTischer/tuya_climate_mult_edit has been modified adapting the module to the new system of connection of yours that appeared in 2024.2.0
The integration works perfectly as of 02/25/2024 @AlexTischer
Today I tested the new integration with the new login method. The new login system works perfectly,
my MOES thermostat works perfectly and keeping the names and rules in working order.
May thanks Javi, it works now for me also!
I'm glad you guys are finding my alternative integration useful! If you want, it's always a good idea to leave a star on the repository 😉
Yes indeed! Done. Many thanks also to you Alessandro ++
star added! :-)
Thank you @javifly! I have the same problem with a different thermostat and it gives me some hope I can solve it.
Could you give more details about the step 4? I don't see any difference after added the "Tuya Climate Multiplier Edit" integration and don't understand what needs to done in https://iot.tuya.com/.
Thank you @javifly!
Hi! I'm replying to you since I made this solution, though @javifly had the good idea to share it here (I previously shared it in some other threads, but didn't see this)
I have the same problem with a different thermostat and it gives me some hope I can solve it.
We'll get there👍
Could you give more details about the step 4?
Unfortunately the guide in this thread is outdated, so don't worry if you can't follow it to the letter. I'll update my README in the repository whenever I find some time to do so.
I don't see any difference after added the "Tuya Climate Multiplier Edit" integration
Did you install my edited integration via HACS and configured it in HA integrations?
and don't understand what needs to done in https://iot.tuya.com/.
Nothing is to be done in iot.tuya.com anymore.
Hi! Thanks for the quick reply.
I did download your integration via HACS, but I don't see anything in HA integrations to configure. However I noticed a change in my local tuya integration, but I guess it's not related.
I'll wait for the updated README and take it from there.
With the recent change in yours integrations the process has changed a bit. I have updated the guide post. https://github.com/home-assistant/core/issues/104164#issuecomment-1826135261
Works great, thanks a lot!
Thanks to @AlessandroTischer for their great work
With the recent change in yours integrations the process has changed a bit. I have updated the guide post. https://github.com/home-assistant/core/issues/104164#issuecomment-1826135261
Maybe I'll use your guide to update the Readme, if it's ok for you
Of course, no problem. The work is yours, I am very grateful.
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.