KNX Climate and Alexa

[sagitt]

Home Assistant release with the issue:
0.103.4

Last working Home Assistant release (if known):
n/a

Operating environment (Hass.io/Docker/Windows/etc.):
Hass.io

Integration:
https://www.home-assistant.io/integrations/climate.knx/

Description of problem:
With HomeKit all works fine, but with alexa, if configured as below won't work.
only works with "on_off_address\state_address" or with "controller_mode_address\mode_state_address" configured.

This happen because Alexa NEED the "hot" or "cold" mode. My thermostat only have to set the temperature, not have a manual on\off or controller_mode, when it feel the right temperature activate valves.

If i set the on\off, i'm not able to set te temparature without before start it, and for start it i need to set the temperature.

For now, i configured the controller_mode_address with (for now not used) daikin knx module, and all works fine. I'm using it with a knx\ip interface, but i have "Thinka" gateway too and it ask if the thermostat is heating only or not and not need any controller mode.

I think the climate knx integration need a virtual setup for this thing or fix it for alexa.

thanks

HomeKit

• platform: knx
  name: 'Riscaldamento [Zona Giorno] HomeKit'
  temperature_address: '3/0/0'
  target_temperature_address: '3/1/0'
  target_temperature_state_address: '3/2/0'
  min_temp: 7.0
  max_temp: 35.0

Alexa

• platform: knx
  name: 'Riscaldamento [Zona Giorno] Alexa'
  temperature_address: '3/0/0'
  target_temperature_address: '3/1/0'
  target_temperature_state_address: '3/2/0'
  controller_mode_address: '6/1/2'
  controller_mode_state_address: '6/1/3'
  min_temp: 7.0
  max_temp: 35.0

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

Traceback (if applicable):

Additional information:

[probot-home-assistant]

Hey there @home-assistant/cloud, @ochlocracy, mind taking a look at this issue as its been labeled with a integration (alexa) you are listed as a codeowner for? Thanks!

[ochlocracy]

Can you provide the following attributes for your climate entity.

hvac_modes:
preset_modes:
supported_features:

[sagitt]

See this:

Test is without on/off

Now i have problems with homekit too. For example thinka gateway only show temperature set. I’m now using this only for this.

[ochlocracy]

https://github.com/home-assistant/home-assistant/blob/b4d6d238e5647a74d9bd7f4dd8b6810a178d1d8f/homeassistant/components/alexa/capabilities.py#L902-L917

For situations like this where hvac_modes is None. It may be possible to report thermostatMode as AUTO or the undocumented CUSTOM mode instead of raising the UnsupportedProperty. I will test the implications of this against the Alexa API.

Otherwise this may need to be handled in the KNX integration.

[pvizeli]

The issue is the KNX handles the climate model wrong, and there is no maintainer on KNX; they can fix the problem. KNX is currently unmaintained. We need not fix alexa, someone need fix the KNX.

[probot-home-assistant]

Hey there @Julius2342, mind taking a look at this issue as its been labeled with a integration (knx) you are listed as a codeowner for? Thanks!

[Julius2342]

KNX has an own understanding of climate modes (and within different KNX climate modules it is terribly complicated already to have a good abstraction, bc the devices of every manufacturer handle these modes slightly different.).

There was huge trouble when HASS introduced the new UI and the different climate modes were handled less dynamic compared to the way before.

[Julius2342]

@sagitt : as KNX does (as far as i know) not have any hot or cold mode defined, what would be the expected climate mode, the device should be set to after saying: "make room x hot" ?

[sagitt]

@sagitt : as KNX does (as far as i know) not have any hot or cold mode defined, what would be the expected climate mode, the device should be set to after saying: "make room x hot" ?

Hi, my knx climate only set the temperature and activate valves (floor heating)

This is what i see with my gateway thinka. Now i’m using it only for this.

Biticino LN4691KNX is the model

[Julius2342]

@pvizeli : we would need some help, what the expected behaviour of a component should be, if there is no heat/cool mode supported by the device but other components (e.g. Alexa) expect such functionality. Wouldn't this be something which should be solved within either the base component or Alexa itself?

[stale]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[sagitt]

i tested it with new releases. same problem

[balloob]

@Julius2342 the climate entity should return heat as current mode and [heat] for available hvac modes.

[Julius2342]

@balloob : the knx/climate entity has some advanced logic for hvac-modes. Would it fix the problem, if the entity defaults to HEAT if nothing is configured?

[sagitt]

I tested it with 0.109, same issue. I don’t know if there is a specific configuration for this type. Anyway my thinka knx gateway still works in right way and don’t need on/off but only temperature setpoint.

Thinka:

Hass:

[balloob]

@Julius2342 yes. You should always return an HVAC mode. It's mandatory.

[farmio]

@sagitt
Is this issue resolved now with 0.110?

[sagitt]

@sagitt
Is this issue resolved now with 0.110?

TESTED NOW!!!
Finally WORKS

See "TEST2" items, "TEST1" have on\off and not works.

thanks!