I’m trying to setup a heater with tuya-local. It works fine with the normal tuya integration, but I like it to be local only. When I setup the heater with tuya-local, it picks it up right away, which is awesome, but once setup en going to the climate entity, the set temperature is off by a factor of 10: when the set temp is 23 degrees Celsius, it shows the set temp as 2,3 degrees Celsius.
I’ve also tried to set up the heater with localtuya which I didn’t get working. I get as far as being able to set which ID belongs where, but when that is setup it just shows an empty climate entity. During the setup I can see that the problem is the other way around: the current temperature is a factor 10 to high.
Any idea how I can fix this issue while still being able to control the device locally? Thanks!
Not sure if the climate integration will take a template directly so create a template sensor that reads that entity & multiplies it. Then plug the template sensor into the climate thing.
It seems the temperature sensor is reported correctly, it’s only the set temp (the 2,3 C) that has the issue. Is there a mechanism to alter the set temp only? (I haven’t looked into the docs yet)
I haven’t found anything to alter the set temp only and multiply it by 10.
@Sir_Goodenough, when setting the temp on the physical device to i.e. 20 C, the value reported to Home Assistant is 2,0 C. So it is not something I set in Home Assistant
In that case, I would set up an automation to listen for set temp calls OR set something up that allows you to react to set temp calls (and have logic to catch if it’s a weird temp call; 2.3 C set point is not normal) if that functionality isn’t available natively.
Something like: when climate is set to X and (0 >= X <= 4) : Y = X * 100, re-set temp = Y. (2.3 * 100) = 230, when whatever is mangling the set temp gets it, 230 / 10 = 23.
0 >= X <= 4 : the set temp is greater than or equal to 0 and is less than or equal to 4. so if the set point was mangled from 0-40 C to 0.0 - 4.0 C, deal with it and hopefully the set point is re-mangled into what you actually want. 0-4 C should be a safe bet, most home thermostats dont use those set points.
Just food for thought. I’d open an issue in localtuya / tuyalocal repos with debug logs to see if they can help with the set point.
Edit: If this works, it would result in more calls and unknown issues with that situation.
I’m having a similar issue with trying to integrate a BAC-006 thermostat (from China) into Home Assistant. Using the Tuya integration the thermostat adds fine but reads the temp and setpoint at divide by 5. so at 22C, the HA dashboard reads 4.4C. Really frustrating.
I tried to install tuya-local, but could not get the device installed properly, probably all the IDs and everyting.
I tried to download the AllessandroTischer/tuya_climate_multi_edit into HACS and it never seems to show up. Anyone else have this issue? Let me know if there is an established work around consensus here.
It seems like I should be able to just add a 5x on the display but maybe I’m not understanding how HA works in a detailed way. Can’t I just edit the card to display 5x on everything?
Anyway. Let me know if this is now a solved issue.
The potential multipliers in tuya official integrations (or local tuya neither) may not match what you need (as I have experienced) - there is only a set of multipliers like 1, 1/10, 1/10- etc. The multiplier integration made by Alessandro fixes this, but - as far as I remember - you need to install a custom repository and then you can get it into ha. I remember it was quite straight forward and it works in my case till now flawless. Hope this helps. J.
OK, thanks - JurekCh1968! I am trying to do this at work using HA cloud, so maybe it will work when I get home. Just didn’t seem to want to include the Repo into HACS when I tried. I put in his repo, hit the “ADD” button, but then nothing, and no sign of the repo afterwards.
