Midea (and Tuya) A/C shows 160–176°F setpoints in Home Assistant – persists across new accounts, devices, and re-pairing

Configuration
,
1

Hi everyone,

I’m running into a persistent issue with Midea window AC units in Home Assistant where the climate setpoint is completely wrong (around 160–176°F). I’m trying to confirm whether this is a known limitation or if there is still something I can do.

The problem

For multiple Midea window ACs, the Home Assistant climate entity shows:

  • absurd Fahrenheit setpoints (≈160–176°F)
  • incorrect min/max temperature ranges
  • behavior consistent with a Celsius-native device being misinterpreted

Because of this, setpoint-based automations are not possible, since HA cannot reliably know what temperature was actually set.

What I have already tried

This is not a first-time setup. I have tested extensively:

  • HA system units set to Fahrenheit
  • Restarted HA multiple times
  • Reloaded the Midea Auto Cloud integration
  • Removed and re-added devices
  • Factory reset the AC units
  • Created a brand-new Midea account
  • Used a different iPhone
  • Installed a fresh Midea / NetHome Plus / SmartHome app
  • Paired a window AC fresh to that account
  • Added the second Midea account as a separate integration in HA
  • Result: same ~167°F setpoint behavior
  • Compared HA diagnostics before/after reload → no meaningful change

This strongly suggests it is not caching, not account-related, and not onboarding-context related.

What this seems to indicate

From everything I can tell:

  • These Midea window ACs appear to be Celsius-native at firmware/cloud level
  • HA is faithfully consuming the cloud schema
  • Once created, the climate entity cannot be reinterpreted or reset
  • Re-pairing always results in the same behavior

What I am NOT looking for

  • Room-temperature-based workarounds
  • Blind IR overrides
  • Hiding the issue with templates

I’m looking for authoritative setpoint telemetry, not heuristics.

My question

At this point, I’m trying to determine:

  1. Is this a known, unavoidable limitation of certain Midea window AC models when used with Home Assistant?
  2. Or is there any supported or unsupported way to:
    • force HA to rebuild the climate entity with correct unit semantics, or
    • bind HA to a different setpoint datapoint (if one exists)?

If the answer is simply “this is not possible with these devices,” that’s fine — I just want a definitive answer so I can make architectural decisions.

I can provide redacted diagnostics or model numbers if helpful.

Thanks for any insight.