Default lovelace thermostat eco button lost, text too big after upgrade

Just upgraded home assistant to 0.101.3 and noticed that my thermostat (default lovelace with the round circle) looks off. I used to have three buttons - heat (comfort), heat (eco) and off, but the eco button is now gone. Since I use it often, I find having to go through the pop-up dialog cumbersome. Anybody know how to get this button back?
Also, any way to change font size for the name of the thermostat - lovelace no longer seems to care if the text touches the circle:
image

As I implemented my modes in Node RED I didn’t even notice that disappearing but I’m also suffering from the giant text, especially on the smartphone :smiley:

Modes only show up in that card if they are called auto, heat, cool, eco, ‘fan only’.

Can you change your modes to match one of those?

Wouldn’t know how, these thermostats are automatically pulled in from FritzBox home automation in configuration.yaml:

fritzbox:
  devices:
    - host: fritz.box
      username: xxxxxxxx
      password: yyyyyyyy

They appear as Operation = Heat/Off, Preset=Eco/Comfort:
image

You might have to talk to the author about getting it standardized in line with what the card uses.

The author of what exactly? How do I find him/her? This is the page about the integration, no author identified:

The second question was about the formatting issue. Any ideas on that?

Ah OK, inbuilt one, would have thought the team would have already aligned it correctly. You might be able to raise it as a bug maybe? Otherwise not sure.

Have you tried different web browsers? Might be an issue with the way the page is being rendered?

For comparison - this is how it looks like in v0.99.3 and v0.97.2:
image
Can’t downgrade to v0.95.4 without losing my panel configurations, so can’t show the eco button, but I must have run this or below before…

Restored to the original from a backup - I was running v0.94.4 and it looked like this there:
image
Note the eco button (leaf) in the middle. The reason probably is, that everything was mapped into the single “Operation” attribute instead of “Operation”+“Preset”:
image
Definitely a regression, first the altered mapping, then the graphical issue.

Yeah I suspect that would be the case, interesting that ‘Heat + Comfort’ works though, it must just be ‘^Heat*’ as long as it starts with ‘Heat’ it finds it.