Core: HASS.IO v0.97.1 Lovelace Card not displaying correct KNX Operation Modes

[G8YTZ]

In the States UI thermostats appear with the ability to select one of the 4 KNX Operation Modes. With 0.97 the Lovelace Card only displays 3 Operation modes and these do not work to change the Operation mode. The picture shows the Graphic that is incorrect, but the "drill-down" is ok.

[probot-home-assistant[bot]]

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!

[G8YTZ]

0.97.2 has the same issue

[elupus]

This look like it's correct. HA only display modes in GUI. Presets are only in the drop-down.

So graphics will only show: off, auto, heat, cool.

[G8YTZ]

Until 95.4 it all worked properly, Colour changed and all buttons worked and am were present, definitely a bug in the latest release and 0.96

Sent from my Remington Rand UNIVAC
www.g8ytz.com

On 13 Aug 2019, at 12:28, Joakim Plate [e-mail] wrote:


This look like it's correct. HA only display modes in GUI. Presets are only in the drop-down.

So graphics will only show: off, auto, heat, cool.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

[elupus]

Climate changed in 0.96: https://www.home-assistant.io/blog/2019/07/17/release-96/

[G8YTZ]

HI, this issue is far from closed. The issue relates specifically to the Lovelace Climate Card not displaying the 4 KNX operation modes from 0.96.x, it is not fixed in 0.97.x either. Look at my config above, it is to the book

To summarise: There are no issues using the STATES-UI, neither are there any issue using the LOVELACE UI using a simple thermostat, for example:

- type: entities title: Lounge entities: - entity: climate.lounge_south_climate icon: mdi:radiator

But using the Thermostat Card is where it all goes wrong. MY configuration in UI-LOVELACE.yaml is as follows:

` - type: vertical-stack # column 2
cards:

      - type: horizontal-stack
        cards:
          - type: thermostat
            entity: climate.master_suite_climate
            name: Master Bedroom`

So something has gone badly wrong with the Thermostat Card from 0.96

[elupus]

It is not that broken. There are not that many modes to display. "Comfort" is no longer a mode for climate. It's a profile. Lovelace card will only display valid modes, not profiles.

Yes it's reduction in function. Motivation is to keep modes in line with Alexa and Google Assistant.

[G8YTZ]

That just cannot be true, as I say it is only the Thermostat Card in Lovelace that is broken (the most important user interface) The fundamental STATES-UI work perfectly ok, so how can Lovelace be anything to do with Alexa?

OK so how should profiles be configured? The documentation is either incorrect or missing something really important. If it is intentional then I believe a re-think should be in order, grief even the documentation shows the Lovelace-UI example that worked for me a couple of weeks ago.

[elupus]

Can you link the documentation that you mention?

[elupus]

I don't fullt understand why you say graphics is wrong. It shows icons for selecting the mode. Ie off, auto, heat, cool.

There is no graphics for comfort, away, sleep, eco. Those you need to drill down into. Same goes for small also large Lovelace card, no difference there.

[G8YTZ]

Sure, the KNX Page shows the configuration.yaml entries, mine are identical (apart from the addresses of course) and worked perfectly. In the UI- Lovelace .yaml the configuration for a thermostat card, until 0.95.4 everything worked well - you saw the 4 modes and as you switched modes the ocular changed, so did the set point and as you switched modes this would be reflected in the graphics. Now there are only 3 modes shown and none of them work and the colours don't change.

KNX Climate:
https://www.home-assistant.io/components/climate.knx/

Lovelace
https://www.home-assistant.io/lovelace/thermostat/ - Note the 4 KNX modes!

KNX is the worldwide standard for building control - it's a professional solution for systems integrators:

The issue seems to be with the Thermostat Card as the STATES-UI is just fine. Many thanks for your help in anticipation.

[G8YTZ]

I was going to say, we could do a WebEX if you would like to see the problem first hand.

[selfisch]

Hey,
I dont exactly understand your initial Post

The picture shows the Graphic that is incorrect, but the "drill-down" is ok.
But in your screenshot, everything seems fine.

For me nothing changed. Here an example of my configuration:

- platform: knx
  name: Wohnzimmer
  min_temp: 17.0
  max_temp: 23.0
  temperature_address: '1/1/11'
  target_temperature_state_address: '1/1/12'
  setpoint_shift_address: '1/1/13'
  operation_mode_address: '1/1/19'

Lovelace UI config:
  - type: entities
    title: Wohnzimmer
    show_header_toggle: false
    entities:
      - entity: climate.wohnzimmer

and a screenshot of the UI:

and last but not least, a screenshot of knx debug log:

So if I switch to one of the 4 modes, everything is fine.
I am running HA0.97.2

[G8YTZ]

In the Lovelace UI Thermostat card only 3 modes are shown, but on the STATES UI all 4 are shown and this work properly. Also the mode buttons no longer work on the Lovelace UI and the state colours are not shown either.

The Lovelace UI Thermostat card has been useless since v 0.96, yet it worked perfectly on previous versions.

The key issue is with the Lovelace Thermostat Card. The picture here shows only three operation modes available when there should be 4 like there always was before.

[MartinHjelmare]

I think you will get better visibility if we transfer this issue to the frontend repo, since it sounds like it's a frontend issue. Although it sounds like there has already been an answer to the change of behavior.

https://github.com/home-assistant/home-assistant/issues/25904#issuecomment-521810026

[G8YTZ]

I did see that comment about reduction in functionality, but that cannot be true, frankly if this does not work I'm wasting my time going with Home Assistant.

KNX is the worldwide BMS standard with massive adoption, Google and the like are just toys.

[balloob]

No functionality was reduced, it's just accessible as a preset instead of an hvac mode.

[G8YTZ]

The whole Lovelace Thermostat interface is now basically useless, but the documentation does not say this. How is the current operation mode displayed? How is it usable from a finger on an iPhone or on a car dashboard or a touchscreen phone like the Gigaset Maxwell 10?
This was what was so brilliant - easy to use and not it does not work with the leading BMS system. That cannot be right.

[selfisch]

In the Lovelace UI Thermostat card only 3 modes are shown, but on the STATES UI all 4 are shown and this work properly. Also the mode buttons no longer work on the Lovelace UI and the state colours are not shown either.

The Lovelace UI Thermostat card has been useless since v 0.96, yet it worked perfectly on previous versions.

The key issue is with the Lovelace Thermostat Card. The picture here shows only three operation modes available when there should be 4 like there always was before.

Now I got the point, sorry for that!
You are absolutely right.
I am currently not using that kind of card in lovelace ui, but hopefully those modes wont be taken away completely from the knx climate integration :-)

[G8YTZ]

Cool! here is what the thermostat page looks like (prior to 0.96) on my Tesla Screen/ Nabu Casa, you can see the thermostats have all modes and can easily be operated by a finger. My plan is to buy the Gigaset Maxwell 10S VOIP phone for my Asterisk system and use the Android OS on the phone to install the HA App and use it to control functions for that room, situated next to the sofa on the coffee table. I think that would be great use for HA as a room controller.

[G8YTZ]

A video also....

https://youtu.be/10nqj6f0uwc

[Mariusthvdb]

wow, looking mightily impressive. But please don't tell us you have 12 thermostats ..? (sorry if this diverges from the OP)

[G8YTZ]

The house is KNX, only diverges for things like Yale Conexis integration (via Smartthings Hub) external web sensors, HIK Vision Cameras, Cars etc. I took a KNX certification course 10 years ago when planning the house self-build.

The heating consists of a Mitsubishi Ecodan air-water Heat Pump, Theben HMT12 actuator that controls 11 underfloor zones and then there are 4 electric towels radiators in the bathrooms, so there are actually 15 zones, though several are dual heat zones.

The thing I like about KNX is that it's and open protocol and a "walled garden" - one configuration tool for all manufacturers and 100% compatibility between manufacturers is gauranteed. The design life of the kit is about 25 years, no software updates required. It just works and does not become obsolete.

Next integration challenge is the Resol solar thermal controller, might do the PV too, but right now I use a Zennio KEX KNX current sensor to measure power.

[G8YTZ]

Hi, is anyone looking at this issue since 0.96? It has completely broken the KNX thermostat integration. Someone has not thought these changes through, a major backward step that writes off HASS for use with KNX which is the largest professional BMS out there.

[iantrich]

The card shows modes, not presets. You can access the more-info dialog which shows the presets by clicking the top right icon. I don't consider this issue based on your description. The modes of the integration changed, not our display.

[G8YTZ]

Yes the Operation Modes don't work anymore. It has completely destroyed the UI with Lovelace how can the card show and control the operation modes correctly again? There must be a fix. Whatever had been done has ruined the interface. Check out how the colours used to change with mode too, not any more.

[iantrich]

I see. People seemed to be focusing on the number of modes rather than the failure of the buttons and is what I picked up on as well.

So to be clear, all the mode buttons on the card no longer work for you but selecting from the drop-down does work?

[G8YTZ]

Yes, that's correct, also you see only 3 operation mode buttons and before there were 4. The picture on the Tesla Dash vs the other (post 0.96) pictures I took. The Lovelace card lends itself very well to a touchscreen, the drop-down does not.

[iantrich]

Let's not conflate the two issues. I think the buttons working is of importance. The modes was a bacoend choice which can be discussed in another issue.

[G8YTZ]

Nothing wrong with the back-end controls at all - the dropdown works as it always did. The issue as you say is that the Lovelace card no longer works correctly and does not display the correct operation modes. In my first picture I showed the dropdown was ok with all the modes.

[iantrich]

That drop-down is not modes, it's presets. You're conflating the two issues again. Presets will not be in the card.

[G8YTZ]

They are defined a "Operation Modes" in KNX. It worked properly before 0.96. Also how do you explain that the Card thermostat trace colours no longer change in the Lovelace Card? They are all grey.

[iantrich]

I'm not going to debate operation modes with you, that was a decision by the core backend devs to better align integrations. They are effectively presets/actions in terms of what the frontend sees.

As for "traces", I don't know what that means and is again a different tangent.

[iantrich]

@pvizeli is what I'm saying accurate for climate 1.0?

[G8YTZ]

OK, look at the Tesla dashboard picture, you see green and orange thermostat traces according to KNX operation modes (call them presets if you like, but the correct KNX term is operation mode) Also look at why not all of the "presets" are displayed anymore there should be 4.
Whatever the backend devs have decided they have broken a very important integration and broken Lovelace too, so the best thing is to revert or add a switch in the software, but I think this is a serious oversight or at best a bug.

[G8YTZ]

Now always grey and only 3 "presets"
The 4 operation modes or presets should be:
Frost Protect
Comfort
Away
Sleep/Night

[pvizeli]

I think the issue is:
Before 0.96 - Our Climate Object was based on the integration (in your case KNX)
Now - We have our own Climate Handling / The integration map this to interface

That means, whatever your KNX say, that does not mean it is mapped like this into Home Assistant.

That it shows wrong on UI is, because the KNX team on HA did not integrate our model correct. I move this issue back to Home Assistant and ping the KNX team. I can not promise that they are active and fix that soon.

Referenz: https://developers.home-assistant.io/blog/2019/07/03/climate-cleanup.html

[pvizeli]

@Julius2342 I think the issue is that on preset, it does not map an hvac mode.

[G8YTZ]

Hi! Many thanks! I think you have hit the nail on the head, if this can be fixed. Actually I am a KNX professional, but my real job is in telecoms. I did the KNX certification for my self-build house. I've been using a commercial remote control system, but it is proving too restrictive in integrating IoT and other things, like cars, locks, media, weather, Velux, plant monitors, and lots of the things. When I found Home Assistant (I also looked at Open HAB and others) I saw it was just ideal and probably the best solution out there.

For me removing this important feature/capability for KNX has undermined its usefulness, so I do hope this issue is addressed. The other thing is we do need to get to a LTS version where it can run for years without having to touch it and there is a straightforward way of upgrading to the latest LTS version. Here I'm thinking like Asterisk is where we should get to.

I am looking at using Asterisk (I already have it and SNOM phones) with a Gigaset (or similar) Maxwell 10s Android phone and having the 10" touchscreen be the room controller via a Home Assistant page, so you have a dedicated room plan with controls on the phone in each room. That's why touch screen thermostats are so important to this idea, the Lovelace Thermostat card is perfect - as it previously worked.

Best regards - Justin

[elupus]

Well. I think backend is correct according to HA behavior.

OPERATION_MODES = {
    # Map DPT 201.105 HVAC control modes
    "Auto": HVAC_MODE_AUTO,
    "Heat": HVAC_MODE_HEAT,
    "Cool": HVAC_MODE_COOL,
    "Off": HVAC_MODE_OFF,
    "Fan only": HVAC_MODE_FAN_ONLY,
    "Dry": HVAC_MODE_DRY,
}

PRESET_MODES = {
    # Map DPT 201.100 HVAC operating modes to HA presets
    "Frost Protection": PRESET_ECO,
    "Night": PRESET_SLEEP,
    "Standby": PRESET_AWAY,
    "Comfort": PRESET_COMFORT,
}

The problem is that @G8YTZ consider the Lovelace gui completely broken if it isn't able to control presets directly. As you can see above on presets those would never map to HA HVAC modes.

So I still see this as a GUI issue, or no issue at all.

[elupus]

I tend to the GUI fault, since the likely thing you want to do is change the profile of your HVAC, not turn it completely on/off.

[G8YTZ]

Yes,

I agree it’s a GUI issue, but it’s an issue because the back end changed and the GUI did not.

Justin.

Sent from my Remington Rand UNIVAC
www.g8ytz.com

On 13 Sep 2019, at 14:03, Joakim Plate [e-mail] wrote:


Well. I think backend is correct according to HA behavior.

OPERATION_MODES = {
# Map DPT 201.105 HVAC control modes
"Auto": HVAC_MODE_AUTO,
"Heat": HVAC_MODE_HEAT,
"Cool": HVAC_MODE_COOL,
"Off": HVAC_MODE_OFF,
"Fan only": HVAC_MODE_FAN_ONLY,
"Dry": HVAC_MODE_DRY,
}
PRESET_MODES = {
# Map DPT 201.100 HVAC operating modes to HA presets
"Frost Protection": PRESET_ECO,
"Night": PRESET_SLEEP,
"Standby": PRESET_AWAY,
"Comfort": PRESET_COMFORT,
}
The problem is that @G8YTZ consider the Lovelace gui completely broken if it isn't able to control presets directly. As you can see above on presets those would never map to HA HVAC modes.

So I still see this as a GUI issue, or no issue at all.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

[probot-home-assistant[bot]]

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!

[pvizeli]

@elupus you need also map an hvac state if a preset is active

[elupus]

@pvizeli, even if that was a bug in backend, it won't help here.

Eco and FrostProtection profiles will both be mapped to heat_cool HVAC mode.

There will be no way from Lovelace card to directly switch between eco and frostprotection, they map to same HVAC mode. There is no profile selection. And both would be under the single button for heat_cool.

[G8YTZ]

The lack of a frost protect mode I could live with, though not ideal. Frankly when something was not broken why fiddle with it? I think the best way forward is to back out this change that was made in 0.96 and have a re-think on the strategy. There was noting wrong with thermostats before this.

[moustic999]

wow, looking mightily impressive. But please don't tell us you have 12 thermostats ..? (sorry if this diverges from the OP)

I have my home fully equipped in KNX and I have 22 thermostat. 1 per room. Each one manage temperature for it's own room. plus 1 which manage heater.

[G8YTZ]

I’d dearly love this issue fixed... Just back out the failed change.

[moustic999]

Most of the people having KNX thermostat @home rely on operation mode of KNX. Only very few people , and moslty Commercial building use the HVAC mode of KNX. The issue is that with the new climate and Lovelace UI, only HVAC modes are in use ( operation mode become presets and need multiple action to be usable). @G8YTZ I have the same issue here at home, and I really hope a solution will be found. Maybe posting a entry in the architecture issues could help, at least to have a discussion on this.

[stale[bot]]

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.

[G8YTZ]

Now at 103.x and still this issue persists. Is there any hope of this ever being looked at? I think this "Architectural clean-up" caused some major issues.

[SergeRPM]

106.2 has the same issues.

Please make the operation mode (presets) worked as it was in the 0.96 version!

[G8YTZ]

I agree, it is most annoying that this bug as not been fixed for months!

Justin.

Sent from my Remington Rand UNIVAC
www.g8ytz.com

On 3 Mar 2020, at 18:48, SergeRPM [e-mail] wrote:


106.2 has the same issues.

Please make the operation mode (presets) worked as it was in the 0.96 version!

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

[elupus]

That is because it's not a bug. It may be a lack of the feature to set presets directly from GUI. But it's not a bug.

[G8YTZ]

It’s a design fault then, it uses to work perfectly and now this error prevents the worldwide professional KNX BMS standard thermostat working properly with Home Assistant.

That’s a massive hit to the usefulness of HA. Remember the majority of new homes built in Germany use KNX, it has massive penetration in the hotel industry. Heathrow Airport? KNX of course.....

Justin.

Sent from my Remington Rand UNIVAC
www.g8ytz.com

On 3 Mar 2020, at 19:08, Joakim Plate [e-mail] wrote:


That is because it's not a bug. It may be a lack of the feature to set presets directly from GUI. But it's not a bug.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

[elupus]

My home run knx.. I know what it is. But pressing the more info button to get to profiles is not that huge a problem.
Also, it should not be too hard to install the custom GUI https://github.com/nervetattoo/simple-thermostat to be able to control that.

[G8YTZ]

Actually that’s very fiddly to do on a touch screen interface. The plan was to use an Android desk phone for each room as a room controller, but this issue prevents that.

Sent from my Remington Rand UNIVAC
www.g8ytz.com

On 4 Mar 2020, at 05:49, Joakim Plate [e-mail] wrote:


My home run knx.. I know what it is. But pressing the more info button to get to profiles is not that huge a problem.
Also, it should not be too hard to install the custom GUI https://github.com/nervetattoo/simple-thermostat to be able to control that.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

[pvizeli]

@Julius2342 was the maintainer and is not active around that anymore. So you need to wait until a new developer or exists developer buys a KNX and will fix that. Since KNX is not just cheap, I don't think that will happen soon.

[cyberjunky]

@pvizeli, too bad @Julius2342 doesn't maintain the KNX integration anymore, I use KNX too.
I also created the toon_climate custom component, and had to fiddle with the code too to get it working after 0.96. Alas only mode settings are available in lovelace main thermostat card, you need the three dot menu to reach presets. Or use simple-thermostats like suggested above and option:

control:
          - preset

But I see the modes are also not displayed correctly (at least on/off heating should be there?)
Will have a look for what it's worth.

[cyberjunky]

Actually, simple-thermostat,js works like you want I guess.
Below your example. above the simple-thermostat like this:

      - entity: climate.wohnzimmer
        control:
          - preset
        type: 'custom:simple-thermostat'

Never mind the bogus temp settings, my thermostat is working on other ga's.

[cyberjunky]

Frontend devs should add a preset control flag and icons to the thermostat card as well.

[Julius2342]

Two kids at home don't scale. @pvizeli : Is there anybody on hass team, who can help us fixing the Climate integration, mainly how to convert the new settings into KNX climate modes?

Or more specific: tell me what was changed on HASS side which broke the climate modes on KNX. From what i see, the core of the problem is, that HASS introduced new climate modes - and oriented on modern devices like NEST. These modes are incompatible with KNX Modes and all mitigations yet did not work. Or made it even worse.

[cyberjunky]

What I noticed just now is that KNX climate doens't have hvac_action() implemented, which should return something like this (pseudo code)

    @property
    def hvac_action(self) -> Optional[str]:
        """Return the current running hvac operation."""
        if self._heating:
            return CURRENT_HVAC_HEAT
        if self._off:
            return CURRENT_HVAC_OFF
        else:
            return CURRENT_HVAC_IDLE

Will have a look

[cyberjunky]

Looking at config page and code, it all seems to work as designed (to new lovelace/climate standard)

climate presets:
All presets are available (but only via three dot menu, this is by design, unless changed)
Can be made more user friendly using simple-thermostat and control preset setting. or by change in design of lovelace thermostat. (frontend devs)

climate operation modes:
In my first attempt, and in some screenshots above only the auto mode icon is visible.
But if you specify on_off_address and on_off_state_address the device is seen as on_off capable and also shows the heat and off icon.

If not correct, please specify clearly what is missing/wrong, the long thread above is difficult to read through.

[G8YTZ]

I still don't understand why this Lovelace bug has not been fixed. Why can't we just roll back to as t was in 0.96 when it worked perfectly? Nobody asked for this change.

What people would like is an integrated scheduler (including thermostats where the operation mode change is available in the scheduler and with a decent user interface for the wife to use.

[elupus]

Because it's not a bug

[G8YTZ]

Everything worked perfectly before 0.97 and then it did not - so its a bug or fault my book. Faulty design perhaps. The designer failed to understand the consequences for a proper professional smart building solution like KNX and the power of knx operation modes in energy management.

[elupus]

You can then easily afford the time to write a custom Lovelace card to support your need for direct touch access to profiles. They work perfectly fine from the sub menu.

[G8YTZ]

If I was a coder... Which I am not, but system integration and telecommunications I do well.

Sent from my Remington Rand UNIVAC
www.g8ytz.com

On 29 Apr 2020, at 13:02, Joakim Plate [e-mail] wrote:


You can then easily afford the time to write a custom Lovelace card to support your need for direct touch access to profiles. They work perfectly fine from the sub menu.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

[stale[bot]]

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.

[G8YTZ]

No, I’m afraid the issue is still present on 0.113.3. It’s a real problem that requires fixing as the Lovelace Thermostat is more or less useless.

Justin.

Sent from my Remington Rand UNIVAC
www.g8ytz.com

On 29 Jul 2020, at 06:13, stale[bot] [e-mail] wrote:


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.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

[marvin-w]

@G8YTZ You should have a read through https://github.com/home-assistant/architecture/issues/22. This was the architectural design decision that forced us to implement a proper mapping to the available HomeAssistant HVACModes in the backend.

Please also read specifically this comment that makes it clear that we actively participated there: https://github.com/home-assistant/architecture/issues/22#issuecomment-454539431

From an architecture perspective this has been a tremendously huge change involving a lot of integrations and will not be rolled back (as it was a perfectly fine move from HA to streamline the climate entity).

Let me clarify this: The old lovelace card is not going to come back, you will always need to use the presets in order to do what you are trying to achieve.

Consider moving to the custom card mentioned by @cyberjunky if you can't afford to open the three dot menu.

I think there still is some weird issue with the duplicated HVAC_HEAT_MODE that should be fixed with the next release of xknx (if I recall correctly).

From my perspective the issue reported here is not an issue, but rather a result of a new architecture (and the related frontend changes).

Please also note one more thing: Due to the fact that XKNX supports literally all KNX devices for a specific type it's very hard to test if everything is working correctly since one usually doesn't own all needed devices from all vendors in all different variations in order to make a complete test.

[G8YTZ]

I still can’t understand a strategy that ignores a major worldwide standard in BMS systems in favour of the numerous smart home “toys” that come and go on the market. The fact remains that there was a perfectly working solution that now does not work.

Don’t get me wrong, I think Home Assistant is a fantastic project and I love the solution, but to ignore compatibility with such a major BMS standard is beyond comprehension to me and others who use KNX and it’s longevity and industrial strength qualities.

Sent from my Remington Rand UNIVAC
www.g8ytz.com

On 23 Aug 2020, at 19:19, Marvin Wichmann [e-mail] wrote:


@G8YTZ You should have a read through home-assistant/architecture#22. This was the architectural design decision that forced us to implement a proper mapping to the available HomeAssistant HVACModes in the backend.

Please also read specifically this comment that makes it clear that we actively participated there: home-assistant/architecture#22 (comment)

From an architecture perspective this has been a tremendously huge change involving a lot of integrations and will not be rolled back (as it was a perfectly fine move from HA to streamline the climate entity).

Let me clarify this: The old lovelace card is not going to come back, you will always need to use the presets in order to do what you are trying to achieve.

Consider moving to the custom card mentioned by @cyberjunky if you can't afford to open the three dot menu.

I think there still is some weird issue with the duplicated HVAC_HEAT_MODE that should be fix with the next release of xknx (if I recall correctly).

From my perspective the issue reported here is not an issue, but rather a result of a new architecture (and the related frontend changes).

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

[marvin-w]

I mean it still is compatible, you just have to click one more button or just use that custom card that was mentioned.

We know the integration isn't perfect, but you have to make compromises in order to support multiple smart home solutions. Please test it. There will not be any improvement to the current lovelace card in terms of usability for KNX as this would break the integration for other climate platforms.

[G8YTZ]

Why not offer the old solution as an option? There are plenty of people who are not impressed with this change.

Sent from my Remington Rand UNIVAC
www.g8ytz.com

On 23 Aug 2020, at 20:53, Marvin Wichmann [e-mail] wrote:


I mean it still is compatible, you just have to click one more button or just use that custom card that was mentioned.

We know the integration isn't perfect, but you have to make compromises in order to support multiple smart home solutions. Please test it. There will not be any improvement to the current lovelace card in terms of usability for KNX as this would break the integration for other climate platforms.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

[farmio]

This should be fixed. The default climate havc_mode is now "heat" since https://github.com/home-assistant/core/pull/35154 so it isn't viewed as "off" (grey) anymore.

[marvin-w]

You can always roll back to HA < 0.97 but this change will not come back. Feel free to use one of the alternatives provided or write your own custom lovelace card.

[G8YTZ]

I think it is time for a long term supported version. There are so many changes, constant changes to entity naming conventions for example it is difficult to keep a stable operational or supportable environment. An awful lot of investment in time is required where what’s really required is solution that once it is in an working stays working, even after an upgrade. Hopefully it will get there one day, but still this whole thermostat thing is a mess and before 0.97 is was so good.

One of the reasons that I went for KNX in my home is because the solution just works, you out it in on day one, configure it and it will work for 25 years or so without touching it or ever upgrading any firmware or software. My KNX installation is now 20 years old, I commissioned it in my self-build house, built 2010.

I’m not a software engineer, my background is radio and electronics and telecommunications/telemetry and BMS systems, though I have dabbled with software since 1974 and given time can work out most things, I just love the range of integrations in Home Assistant, but boy I wish when an upgrade was pushed that old working integrations carried on working.

Sent from my Remington Rand UNIVAC
www.g8ytz.com

On 23 Aug 2020, at 22:45, Marvin Wichmann [e-mail] wrote:


You can always roll back to HA < 0.97 but this change will not come back. Feel free to use one of the alternatives provided or write your own custom lovelace card.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.