Rovsun / Tuya AC Target Setpoint Bug - Showing 165°F instead of 74°F

Configuration
1

Hi everyone,

I’m managing a multi-unit AirBnB setup in Florida with 10 Rovsun Mini Split ACs integrated via the official Tuya/SmartLife integration. My Home Assistant instance is set to Imperial (Fahrenheit) globally.

I’ve hit a bizarre scaling issue that seems to be firmware-dependent:

  • The Problem: 8 of my 10 units show an incorrect target setpoint in HA. If the AC is set to 74°F on the remote/app, Home Assistant reports it as ~165°F.
  • The Clue: The “Current Temperature” and all other sensors report perfectly in Fahrenheit. Only the target_temperature is scaled wrong.
  • The Split: Units purchased/installed after Spring 2025 work perfectly. Units from 2024 and earlier all have this bug.

Technical Findings from Diagnostics:
I pulled the JSON diagnostics for a “Bad” vs “Good” unit and found the discrepancy in the temp_set Data Point:

  • Bad Unit (PID: hw50w7qvxluhslkk): Reports a max of 880 and a scale of 1. It seems to be sending Celsius × 10 (e.g., 24.5°C as 245) but tagging it as Fahrenheit, which HA then misinterprets.
  • Good Unit (PID: hrzr8mr0mtgfwwri): Reports a scale of 1 but correctly caps at 310 (31.0°C), and HA handles the conversion perfectly.

I am currently using a Template Sensor workaround to “math” the 160s back down to 70s, but this is messy for 10 units and breaks the standard climate card.

Has anyone found a way to “force” the Tuya integration to respect a different scaling factor (0.1) for specific PIDs? Or is this a “wait for Tuya to fix their cloud schema” situation?

Any advice from fellow Tuya/Midea users would be greatly appreciated!

2

I don’t know the specifics of whats going wrong, but it looks like a conversion issue in that:

74C ~= 165F

I had similar issues at one point (with another device) I was okay with just switching everything to Celsius (and that worked), however I would have gone through looking for something set wrong, if I wanted everything in Fahrenheit.