Bug Report HVAC Mode Issue

[stelau81]

I use a Rapsberry 4 with HA, SD Card., HA Version: 12.1, Core: 2024.4.0

Got a Better Thermostat Protocol Information:

Logger: homeassistant.components.climate
Quelle: components/climate/init.py:367
Integration: Klima (Dokumentation, Probleme)
Erstmals aufgetreten: 20:51:35 (4 Vorkommnisse)
Zuletzt protokolliert: 20:51:35

Entity None (<class 'custom_components.better_thermostat.climate.BetterThermostat'>) implements HVACMode(s): heat, off and therefore implicitly supports the turn_on/turn_off methods without setting the proper ClimateEntityFeature. Please create a bug report at https://github.com/KartoffelToby/better_thermostat/issues

Can you fix this?

Thank You

[Panoramiac]

Have the same and one of my Thermostats is always not available.

Logger: homeassistant.components.climate
Quelle: components/climate/init.py:367
Integration: Klima (Dokumentation, Probleme)
Erstmals aufgetreten: 08:36:52 (8 Vorkommnisse)
Zuletzt protokolliert: 08:36:52

Entity None (<class 'custom_components.better_thermostat.climate.BetterThermostat'>) implements HVACMode(s): heat, off and therefore implicitly supports the turn_on/turn_off methods without setting the proper ClimateEntityFeature. Please create a bug report at https://github.com/KartoffelToby/better_thermostat/issues

[tco99ttocs]

got a similar problem, but i hav a TRV 801W which has the following HVAC modes: "off", heat_cool, heat_cool
Maybe this could be fixed

[E5TO]

I got the same error.

I tried to get around with some automation. I guess this could work out till an update comes:

alias: Map heat to heat_cool
description: "set hvac mode from heat to heat_cool"
triggers:
  - trigger: state
    entity_id:
      - climate.termo_schlafzimmer
    to: heat
actions:
  - action: climate.set_hvac_mode
    metadata: {}
    data:
      hvac_mode: heat_cool
    target:
      entity_id: climate.termo_schlafzimmer

[folfy]

@stelau81, @Panoramiac You're probably using outdated BT versions, this should be fixed long ago (02/2024, like v1.5.0 or v1.5.1+), otherwise let us know - closing issue

@tco99ttocs, @E5TO Your issue is something completly different, and also was already reported before #1322 and fixed #1533, so please update / try v1.7.0b3

Actually @E5TO Your request seems different, you seem to want heat_cool for an entity that actually/apparently supports mode heat. This shouldn't be required - When adding the entity also as cooling entity, this should already ensure BT is setting mode cool as required afaik.

[E5TO]

@folfy Updated to 1.7.0b1 but still got the Note:

Logger: homeassistant.components.climate
Quelle: components/climate/init.py:618
Integration: Klima (Dokumentation, Probleme)
Erstmals aufgetreten: 19:14:53 (2 Vorkommnisse)
Zuletzt protokolliert: 19:15:08

tuya::TuyaClimateEntity sets the hvac_mode heat which is not valid for this entity with modes: off, heat_cool. This will stop working in 2025.4 and raise an error instead. Please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+tuya%22

Edit:

Got on 1.7.0b3
And get different errors

Logger: homeassistant.components.switch
Quelle: helpers/entity_platform.py:773
Integration: Schalter (Dokumentation, Probleme)
Erstmals aufgetreten: 19:21:03 (2 Vorkommnisse)
Zuletzt protokolliert: 19:21:03

Platform tuya does not generate unique IDs. ID tuya.bf7b92aad7a13b8701mtp8child_lock already exists - ignoring switch.arbeitszimmer_kindersicherung
Platform tuya does not generate unique IDs. ID tuya.bf20af11d8c2127a95kuc0child_lock already exists - ignoring switch.termo_schlafzimmer_kindersicherung

[folfy]

@E5TO Yeah, as said you need at least b3, but you noticed you mixed that up.

The stated log message is not related to BT at all, we don't even care about any kind of "lock" entity. So you have to go to the tuya integration development with this, if that particular problem is actually causing trouble for you.