As the title suggests, is there a way to lock the thermostat card? Or at least make it so a change requires more than a simple swipe? The boiler was set to 27c/80c early this morning. I can only guess it happened by accident while one of us was looking at the app on our phone, probably half sleep or something and didn’t notice it get changed. With a touch screen it is very easy to set a different temperature as you are scrolling up or down the app, I’ve done it and I’ve seen it happen by others in the house. Not cool with energy prices as they are.
If there is not a simple setting that can be changed on the thermostat card, with out requiring knowledge of css or scripting, there needs to be soon.
jchh
(my username is my initials (and my first name isn't John))
2
I get round this by displaying (read only) info using custom:button-card on my main dash and keep changes to cards like thermostat on a second dash. That way I don’t have to worry about accidentally changing things.
I also use a lot of hold_action: to avoid accidental changes (of which there used to be many).
The hold_action I do not believe is available for the thermostat card?
And I do have it set on a second page. Bottom line is if the thermostat card is used simply scrolling past it means a change can inadvertently be made.
Take a look at this post that then jumps to another post showing card-mod solution.
If you don’t want to use card-mod then I would suggest setting up an input_boolean to display the card or not using the conditional card on the thermostat card. This way you are only displaying the card when you set the input_boolean.
You might also want to add an automation that alerts you to the fact that the t-stat has changed.
Not a direct answer, but when we are away our daughter house-sits for us. She thinks nothing of setting the AC to 60°F in the summer or 76°F in the winter. So I have automations that change the setpoints of the thermostats if she had set the thermostat out of my comfort range.
alias: Heat-upstairs-limit
description: If the heat is set above 72 ° for 5 minutes, set it back to 70°
trigger:
- platform: numeric_state
entity_id:
- climate.upstairs
for:
hours: 0
minutes: 5
seconds: 0
attribute: temperature
above: 72
condition:
- condition: state
entity_id: climate.upstairs
state: heat
action:
- service: climate.set_temperature
data:
temperature: 70
target:
entity_id: climate.upstairs
mode: single
This gives the illusion that the heat or A/C will be responding to the thermostat for five minutes then it gets set to a sensible temperature. She hasn’t caught on yet.
I had the same problem on my phone and switched to the “simple-thermostat” card found in HACS, It is minimalist and make it much harder to change the temp with a simple swipe on the phone.
I tried to write up an automation that did something similar because the wife likes to periodically bump up the heat. I was unable to get it to work. For some reason it would not see changes to the climate entity. I couldn’t even get a notification to work. I abandoned the idea because it would only be a degree or two and I would always notice after a while.
This really sounds like an issue that should be addressed in HA. If people are looking at workarounds and using hac’s just to get around one single issue, it is indicative of a design flaw of that card. We’re not even talking about adding functionality, just preventing accidental changes to something that can have real consequences. It’s now 1:30pm and my house is still cooling off nearly 12 hours after the adjustment was made.
Agreed, messing about with dashboards and cards I have set my heating by accident a few times. Yesterday I found my house a degree hotter than it should.
My old smarthome dashboard simply had buttons to adjust. The slider looks sleek and stylish, but is not safe. Especially since you don’t actually need to adjust the slider and can just tap it anywhere to change. So a fix would be that you’d need to touch or hold the dot first and then slide.
Hm… If a wife “periodically tends to bump up the heat” (just example taken above) then it’s far from design flaw of HA card, but rather a domestic issue. If you (or I) think that temperature is correct and a wife thinks it’s too cold, then it’s time for “house meeting”, not for HA card update… If you lock up the card, it’s just a matter of time when a wife will find the way to unlock it…
I never suggested this particular incident was the wife adjusting the thermostat a few degrees. I mentioned that she has done that before, but this was NOT one of those cases. Reread what happened a little closer. A jump of 10f at 4:30 am when everyone is warm in bed is not the wife purposely increasing the temperature. Especially when she was one complaining about how hot it was too.
While I appreciate the flexibility that is HA, jumping threw hoops using work arounds, hac’s, and custom cards to correct a behavior that introduces unexpected results is not best practice and is a design flaw.
