4.0.11 is broken for some vrf modules.

[meirlo]

Installed the latest version 4.0.11
The climate become unavailable with the following exception in logs. 4.0.10 works fine

Logger: homeassistant.components.climate
Source: helpers/entity_platform.py:725
Integration: Climate (documentation, issues)
First occurred: 12:05:55 AM (1 occurrence)
Last logged: 12:05:55 AM

Error adding entity climate.guest_room for domain climate with platform gree
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 725, in _async_add_entities
await self._async_add_entity(
entity, False, entity_registry, config_subentry_id
)
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 1127, in _async_add_entity
await entity.add_to_platform_finish()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1444, in add_to_platform_finish
await self.async_added_to_hass()
File "/config/custom_components/gree/climate.py", line 1032, in async_added_to_hass
await self.async_update()
File "/config/custom_components/gree/climate.py", line 744, in async_update
await self.SyncState()
File "/config/custom_components/gree/climate.py", line 691, in SyncState
self.UpdateHAStateToCurrentACState()
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
File "/config/custom_components/gree/climate.py", line 494, in UpdateHAStateToCurrentACState
self.UpdateHACurrentTemperature()
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
File "/config/custom_components/gree/climate.py", line 429, in UpdateHACurrentTemperature
temp_c = self._process_temp_sensor(self._acOptions["TemSen"])
File "/config/custom_components/gree/helpers.py", line 46, in call
self._evaluate() # evaluate every time, so it can change it's mind as needed
~~~~~~~~~~~~~~^^
File "/config/custom_components/gree/helpers.py", line 51, in _evaluate
penalty_no = self._penalty(lo, hi)
File "/config/custom_components/gree/helpers.py", line 59, in _penalty
if lo < self._lo_lim:
^^^^^^^^^^^^^^^^^
TypeError: '<' not supported between instances of 'str' and 'float'

[RobHofmann]

I assume it must be in here:
a44dc6e

Would you be so kind to verify?

[meirlo]

Thanks @RobHofmann — I dug into it. It's not really a44dc6e (#445) itself; the actual cause is that VRF sub-units report TemSen (and OutEnvTem / DwatSen) as strings like "25", while the code assumes integers.

TempOffsetResolver compares the raw value against float limits (lo < self._lo_lim), which raises TypeError: '<' not supported between instances of 'str' and 'float' when the value is a string. #445 just made TemSen reliably fetched/probed on these units, which is what surfaces the pre-existing type assumption — 4.0.10 happened not to hit this path the same way.

I've opened #536 with a fix: coerce the raw sensor values to float before use (in TempOffsetResolver and the three UpdateHA… sensor methods), degrading gracefully if a value isn't numeric. Verified on my GR-Gcloud V3.2.M gateway (4 VRF units that report TemSen as a string) + a standalone unit on 4.0.11 — all entities load again and standalone units are unaffected.