Lovelace custom cards don’t belong in the custom components folder. They need to be accessible by the web-based frontend, so they go into the {config dir}/www folder (or a subdirectory of it). See the manual installation directions here: https://github.com/nervetattoo/simple-thermostat#installation-manual
Lovelace custom cards are different than Home Assistant Custom Components. Conceptually, Lovelace content is the frontend (like a content you see on a webpage) and components are the backend (database, server, etc.).
I’m using this card to control my heated floors. The temperature that’s displayed is showing as “70.0” instead of just “70”. I’d like to get rid of the unnecessary “.0”. Is it possible to format the number to just a whole number?
Not at the moment. I live in a metric world so a decimal number always made sense to me. I realise now that for fahrenheit you might be better off without it. I guess if step size gets set to 1 we can opt in for pure integer formatting. Will keep that in mind, or you can add an issue at github if you have an account.
Also, if my wife turns the aircon on using the remote, I have HA setting the respective climate component as “on”. However the bottom in your lovelace card does not slide over to the “on” even though the sate is “on” See my phone screenshot above. Any suggestions? edit - got this to work with an automation!
Can someone explain me how to achieve this? also is it possibble to give the buttons an icon and highlight the icon and tekst and delete the square box?
Just updated to .20.0. I like the mode buttons, and have everything tweaked the way I want, there’s just one last thing I’d like to change; but I’m not sure if it’s my config, HA version(0.88.2, preparing to update to .89.2 soon), or the card. I don’t like the look of the selected mode being ‘greyed out’/disabled.
Here’s what it looks like now(notice the greyed “Heat” button):
Here’s what I’d like it to look like(achieved this image using Chrome developer tools to remove ‘disabled’ from the mwc-button for Heat):
Possibly relevant, I have a theme I created many Home Assistant versions ago to make some text items and page elements green (I also have red and blue versions with the same variables modified, but am only really focused on green right now). I haven’t (yet) gone down the path of checking on how/if themes have changed in recent versions. So just shout at me if it’s something easy I can find in the docs :-).
So is it possible for me to change something in my setup to achieve this look permanently, or would the card code need to be modified (and if so, would you please consider this a feature request @nervetattoo?) It’d be cool if the color changed relevant to the current state (red for heating, remain grey just for idle, and blue for cooling), but I’d be satisfied if it just wasn’t greyed out when selected.
I did the same too, with Chrome dev tools. Deleted ‘disabled’ and get what to see the button…
Hmmm, i suppose we have to inject this ‘mwc-button disabled’ into the selected theme. Wonder how to do that…
The operation_list variable is (at least for my Honeywell thermostat) the exact list of modes I needed to use in simple-thermostat. Also, fwiw, I did not use quotes, except around the ‘off’ mode.
This is the netatmo.py that is used in Ha to manage the Netatmo Thermostat.
The states are the same that I used, heat and idle for sure.
I’ve tried also only those two, without quotes, with no success.
I’m not much into theming myself as I prefer to stay as vanilla as possible, but know that HA made a move towards mwc-button over paper-toggle-button in a 0.88, which is what you seem to be targeting. I’m guessing that is the reason why you can’t theme them. The card only uses the provided states of that button so its themability should be intact.
I see a lot of people not liking the fact that the current active mode is set as a disabled button so I’m on the verge of agreeing there. Visually it’s a bit weird that its disabled, but semantically it shouldn’t be possible to click on already-selected mode as that makes no sense.
This seems like it should work really. Are you absolutely sure its not related to browser caching? Try to clear out the cache for HA and see if that helps.
A lot of people are confused by the quotes but the rule of thumb is: no quotes on keys in yaml, the only exception is for the few keywords which the YAML parser will convert to true/false, namely “on” and “off”.
There is a reason the documentation only uses quotes around those
I’ve tried clearing cache (normally I use a Chrome plugin to clear it, but now I’ve done thru Settings) and tried also Opera as browser, but nothing changed.
I think that most probably the Netatmo Thermostat component have just two states, idle and heat.
Some other states, like away, are not sees as state but are seen as an attribute, as in screenshot below.
In this case, simple-thermostat should show the two button idle and heat?
It looks like it’s trying to make me set a range (min/max), which I don’t want. Any ideas how to disable this?
When I set it to “auto”, the 2 range temperatures appear. I don’t want that though. I don’t want to have AUTO enabled, just heat or cool. I removed “auto” from the modes, but it still wants to show the 2 temperatures.
