0.81: New thermostat card not working with Danfoss thermostat?

Configuration
1

Hi,

I just gave v0.81 a try and added an instance of the new thermostat glance card to my lovelace config:

  - id: 81419d30758741938645c8f08131ea95  # Automatically created id
    type: thermostat
    entity: climate.danfoss_office_heating_1

The referenced thermostat is a Danfoss 014G0013 Z-Wave thermostat.

But instead of the new thermostat card, nothing appears on the screen, not even one of those red error cards.
Lovelace still seems to generate “something”, because when I remove the card definition, the whole page layout changes from 3 columns to 2.
Also, it looks like with the included card definition, the column where the thermostat card would render is shifted a few pixels downwards - looking like an invisible card with only a few pixels height is “displayed”.

Sebastian

EDIT: This is how it looks now:

40
40697×52 9.62 KB

2

I can confirm this is exactly the case with the Netatmo Thermostat.

In configuration.yaml I have:

netatmo:
  api_key: !secret netatmo_api_key
  secret_key: !secret netatmo_secret_key
  username: !secret netatmo_username
  password: !secret netatmo_password
  discovery: false

climate:
  - platform: netatmo

In ui-lovelace.yaml I have:

  - id: 3d7936ff038a4b01b65fe9313a79fc3c  # Automatically created id
    type: thermostat
    entity: climate.netatmo
3

Getting the same with my Netatmo, thought the 0.81.1 update would fix it but the same issue.

4

0.81.1 didn’t change anything for me either.

I wonder why this did not come up during the last week’s “beta phase”.
Are not enough people testing the release candidates?

Sebastian

5

Same here with netatmo thermostat.
No card display in the frontend.

6

I have similar problem… Thermostat card showed up with default theme, but when using any custom theme, it does’t show up as it should

7

The same problem with the generic thermostat:

In ui-lovelace.yaml I have:
- type: thermostat
entity: climate.Stud

In configuration.yaml I have:
climate:

  • platform: generic_thermostat
    name: Stud
    heater: switch.torsher
    target_sensor: sensor.temperature_158d0002270b28
    min_temp: 15
    max_temp: 21
    ac_mode: False
    target_temp: 17
    cold_tolerance: 0.3
    hot_tolerance: 0
    min_cycle_duration:
    seconds: 5
    keep_alive:
    minutes: 3
    initial_operation_mode: “off”
    away_temp: 16
8

I’m using the broadlink climate component with this and my ‘fan’ mode is missing. In 0.81.0 it had an invisible ‘fan’ button, but with 0.81.1 it disappeared completely. I see a lot of pictures of other people’s cards have the fan function present.

9

Do any of you have errors in the console? And if every could upgrade to 0.81.2 and then let me know if you are still having issues

10

@zsarnett same issue with netatmo thermostat with 0.81.2 unfortunately.

Edit : can’t see any error in logs nor in chrome’s console

11

If you go to dev-state page, can you screen shot the full state and attributes of your climate device. @SNoof85

12

@callifo There is only Operation Mode Functionality. The Fan you are seeing is coming from the operation mode for off

13

This issue has a PR that has been merged. Will be in 0.81.3 if there is one or 0.82 release.

1 Like
14

image

There it is

1 Like
15

I’m on 0.81.2 since shortly after it was released. Nothing changed for me.
I see no errors on the console or home-assistant.log.
Here’s the screen shot of one of my thermostats:

08
081042×313 27.3 KB

Sebastian

16

Looks like this fix was not in 0.81.2 as I had previously thought. I am tagging the next Hotfix with a fix for all the issues in the Post. Hopefully :stuck_out_tongue_winking_eye:

17

Same Problem with HomematicIP. In normal ui everything is fine.

18

Same problem with broadlink climate component.

It exists:

image
image740×233 14.1 KB

but no card is shown in Lovelace (I know it’s there because if I make a typo in config the red error box appears)

19

As I said, it should be fixed in 0.81.3 only thing that isn’t fixed in 0.81.3 is the theme for the card. 0.82 will fix it so you can change the background

20

I can confirm that 0.81.4 fixed the issue for me.

Sebastian

1 Like