Me and many others are frustrated that the BHT-002 thermostat (sometimes called Moes or Beca Energy) is showing a 5 times too small temperature using the official Tuya integration.
Examples of issues reported in the Home Assistant Core issue tracker are Issue 72703 and Issue 73612.
The reason for the issue with BHT-002 is that the thermostat does not follow the Tuya Open API specification. The temperature values to/from the thermostat should be divided by 10 in spec but BHT-002 divides temperature with 2.
I made a workaround in the Tuya integration for this issue found in the clone here. This workaround is only applied to BHT-002 thermostats based on their ID and thus other thermostats will work as expected.
However, the responsible authors of the Home Assistant Tuya integration refuse to include my changes since they won't include any device specific parts in their implementation.
Fortunately, the changes are possible to install as a custom component that overrides the official integration.
If you have installed the Tuya integration. Delete it in the Home Assistant configuration user interface.
If You are running Home Assistant via Docker, skip this step.
If you are using Home Assistant OS (HASSIO) secure that you have SSH addon up and running. Follow the instruction here
Clone the modified files from the tuya_BHT-002_thermostat_workaround branch.
joel@penguin:~/temp$ git clone -b tuya_BHT-002_thermostat_workaround git@github.com:midstar/homeassistant_core.git
joel@penguin:~/temp/homeassistant_core$ cd homeassistant_core/homeassistant/components/tuya/
The manifest.json file (in tuya directory) needs to include a version number.
It doesn't really matter which version you pick. For example "version": "1.0.0":
{
"domain": "tuya",
"name": "Tuya",
"documentation": "https://www.home-assistant.io/integrations/tuya",
"requirements": ["tuya-iot-py-sdk==0.6.6"],
"dependencies": ["ffmpeg"],
"codeowners": ["@Tuya", "@zlinoliver", "@frenck"],
"config_flow": true,
"iot_class": "cloud_push",
"dhcp": [
{ "macaddress": "105A17*" },
{ "macaddress": "10D561*" },
{ "macaddress": "1869D8*" },
{ "macaddress": "381F8D*" },
{ "macaddress": "508A06*" },
{ "macaddress": "68572D*" },
{ "macaddress": "708976*" },
{ "macaddress": "7CF666*" },
{ "macaddress": "84E342*" },
{ "macaddress": "D4A651*" },
{ "macaddress": "D81F12*" }
],
"loggers": ["tuya_iot"],
"version": "1.0.0"
}Put the modified tuya directory in the config/custom_components directory. You need to create a custom_components directory unless you already have it.
scp -r tuya/ root@192.168.1.103:/root/config/custom_components/
Note that "root/config/custom_components" is the correct directory for Home Assistant OS. Other directories apply to other installation types. Also "root" user might be different in your system. Of course you need to modify the IP address to your Home Assistant IP.
Restart Home Assistant. Then add the integration under configuration in the Home Assistant user interface, i.e. you add it in the same way as you add the official integration. Since you have tuya in custom_components it will override the official integration. Follow the official Tuya configuration guide.
In the file device_specific.py there is a list of devices (keyed on Product Identity) where the base for values and steps can be set.
The device ID of your device can be seen in home assistant if you open the Tuya entity and check what is written below "Entity information".
For BHT-002 it will look like:
thermostat (IAYz2WK1th0cMLmL) by Tuya
Where IAYz2WK1th0cMLmL is the product ID.
If you do changes please add a pull request to my clone of the homeassistant_core repository or add an issue in this repository and I will add it for you.
I will try to keep the custom integration up to date with the official Tuya integration.
Please let me know if you find any issues, would like to add more device specific parts into the code or if there are fixes in the official Tuya integration that should be merged.