Is there a way to disable target_temperature_low/target_temperature_high being set on the vtherm climate entities in cooling/heating mode?

[stuartparmenter]

Hey there I'm using versatile thermostat w/ a bunch of LG mini split units and it has been great so far!.

I noticed in the logs that I'm getting a bunch of errors from LG's thinq integration, i.e.:

Error executing service: <ServiceCall climate.set_temperature (c:XXXXXXXXXXXXXXX): entity_id=['climate.main_bathroom_ac'], target_temp_high=64.0, target_temp_low=64.0, temperature=64.0>
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/lg_thinq/entity.py", line 98, in async_call_api
await target
File "/usr/local/lib/python3.13/site-packages/thinqconnect/integration/homeassistant/api.py", line 695, in async_set_target_temperature_low
raise ThinQAPIException("0001", "The control command is not supported.", {})
thinqconnect.thinq_api.ThinQAPIException: ThinQAPIException: UNKNOWN_ERROR (0001) - The control command is not supported.

The thermostats are set to cooling (central mode cool only), so I wouldn't expect it to be setting low and high unless I was in heat_cool or auto mode (which I can't generally use since I've got multiple mini splits on the same compressor/heatpump and they all need to agree).

It does seem like the temp settings are making it through, but would love to remove the errors.

Wasn't sure if I was missing a setting somewhere, if this is an upstream issue (can't see obvious place in the code, but not sure) or if I should file it as an issue, so per the template wanted to start as a discussion. Thanks in advance!

For reference, on the underlying climate devices, I see supported_features: 395 and I see 411 for the vtherm

[stuartparmenter]

After doing some more digging, I'm guessing this is a combo of two things:

https://github.com/home-assistant/core/blob/dev/homeassistant/components/lg_thinq/climate.py#L131-L135 looks like it just gets set once (and since it is supported, in some modes, makes sense), but isn't changed on the model based on mode.

and https://github.com/jmcollin78/versatile_thermostat/blob/main/custom_components/versatile_thermostat/underlyings.py#L694-L700.

Would it maybe make sense to add a check for mode being heat_cool or auto here? I'll try hacking that in and see if the errors go away.

[stuartparmenter]

Adding and self.underlying_climate.hvac_mode in [HVACMode.HEAT_COOL, HVACMode.AUTO] to the RANGE check does seem to make the low temp errors go away.

Was also seeing thinq errors from setting non-integer temps (coming from regulation that had the default 0.5 regulation threshold set -- changing it to 1 seems to make those go away. Also looks like they just pushed a change upstream to just truncate floats to ints

[stuartparmenter]

Maybe related to some errors I'm seeing -- I had also been experimenting with auto on/off (w/ very slow). I definitely see a few things where it sets it to off, then immediately to cool, then immediately to off again. I suspect some errors may be related to the machines being off and being slow to respond to changes. Will turn that off for a bit and see how things go.

[jmcollin78]

Hello,

If the range is supported by the underlying, then VTherm uses the range mode. Is that your point ? (sorry I don't understand all your post)

[stuartparmenter]

tldr: I ended up filing a bug upstream for the RANGE/target_high/target_low issue -- home-assistant/core#147530

It could also be fixed in versatile thermostat by only sending target_high and target_low when in auto or heat_cool mode here: https://github.com/jmcollin78/versatile_thermostat/blob/main/custom_components/versatile_thermostat/underlyings.py#L694-L700

The other errors I'm seeing (sometimes) seem like latency issues between the thinq integration & versatile thermostat. Will spend some more time trying to diagnose them, but most seem like they should probably be fixed upstream as well.

[jmcollin78]

It could also be fixed in versatile thermostat by only sending target_high and target_low when in auto or heat_cool mode here:

But it wont work anymore for others no ?