Frontend: Nest thermostat showing "null - null"

[bachya]

Our Nest Thermostat is currently set to heat at a single target temperature; starting today, the UI began showing this:

Although this data is correct (in that min and max targets are, indeed, null):

...shouldn't the platform show the target temperature?

EDIT: had an incorrect second screenshot.

[balloob]

Which version of Home Assistant are you using?

[bachya]

@balloob 0.66.0 (sorry, should have included that).

The only anecdotal info I can give: it seemed to happen this morning when I randomly tried the climate.turn_off and climate.turn_on service calls. Can't imagine that's a problem, but FYI.

[balloob]

So it is caused by #1037. But the bug is in the backend: we should not include a target temp range if operation mode is set to heat.

[balloob]

And the backend bug is related to https://github.com/home-assistant/architecture/issues/22

[balloob]

@c727 do you think that we should include temporary null checks for attributes?

[c727]

Hmz. Someone else has to fix it please, currently not at home

[balloob]

Done

[moskovskiy82]

I also have this bug. But not only with the nulls but also extra controls are now shown. Wasn't the case in 0.65

[titilambert]

We have the same issue with ecobee climate

[moskovskiy82]

For me the fix in 0.66.1 didn't work Still the same. Mysensors HVAC component

[MartinHjelmare]

Have you done a hard refresh of the browser page? Ctrl + shift + r in chrome.

[bachya]

@MartinHjelmare is right on the money: a hard refresh does the trick!

[moskovskiy82]

OK nulls are gone. But the problem with several temp controls is still there

[MartinHjelmare]

It might be related to supported features. I think we need to make those conditional now in the mysensors platform. I think this is a separate issue.

[NovapaX]

There's two approaches to this. Either change supported features, or disable/hide controls based on the state.
I would prefer the latter (like we do with the light controls) as supported features is a given for a device, and should not change based on its state/operation mode...

[MartinHjelmare]

Mysensors is a bit special as the features depends on the sketch the user writes. We have to support different sketches. It's comparable to different types of devices.

[moskovskiy82]

@MartinHjelmare Shall i open a separate issue on HA? I believe you are the main driving force for mysensors platform so you are already aware of the issue,,,

[MartinHjelmare]

Yes I'm aware and it's now on my todo. You can open an issue if you want. It doesn't hurt.