You can’t control both the heat & cooling from one entity? I have the same thermostat and I have the “_heating” entity hidden but can still control both the heater & the ac from the “_cooling” entity.
Are you sure? Can you contol auto mode as well?
I could not, while on heat mode, setting the temperature on the cool entity would set the cool temp and viceversa. That’s why I created this custom card plus you have control of both entities on the auto mode using this card.
Yes I can. I un-hid the second device to do some testing and, as far as I can tell, I’m able to completely control my thermostat (2gig CT100) from either device. It looks like any changes I make to one entity are immediately replicated in the other. I can’t do high/low set-points and instead Auto works by turning on the AC or heater if the temp gets 2* above or below the set-point, but I think that’s just a limitation of my thermostat.
This is what the states screen lists for the two devices: https://imgur.com/a/PVVu5Qb
Hello. Thank you so much for this. I’ve been trying to get something like this going on the old UI forever. When I came across this, it’s what made me finally want to switch over to lovelace.
Anyways, I have a question. It might be more of a general lovelace question that something specific to this card type. Is there any way I can make it so that a card will display the basic information(heat/cool mode, current temp, target temp, etc), but doesn’t allow me to change it until I tap on it? Or maybe something that leaves it in read only mode until I turn on an input slider.
I just set all this up 3 days ago, and yesterday, I came home and the 2nd floor was 85 degrees and the thermostat was set to the 90’s. I must have accidentally moved one of the dials by accident. I just want a way to make it difficult to accidentally change the temperature like that.
And also, is there any way to define the max range of the slider? I don’t think I have a need to ever set it lower than 60 or higher than 80, in summer or winter. Yet the slider ranges from 45 to 95.
The slider range comes from the thermostat minimum and maximum supported values. Some thermostats allow you to change these values and therefore will update the slider range. Check the thermostat config under the z-wave admin page.
Lovelace UI - Conditional Question and Suggested Tweaks
Just found this and its great for my zwave thermostat. Any chance you could put this in the core so its easier for other people to find.
@enriqg9, thanks for your help on this. I was able to make some changes to this that allow 2 new options (min_slider and max_slider). They are optional. But if you put them in, it will set the slider min and max to those values. I have created a pull request for that, if you don’t mind taking a look at it. It’s a non-breaking change so any old configs would continue to work.
Again, thanks for this. It’s awesome.
@enriqg9, just what I need. Thanks. @simpat1zq, Thank you for the min/max enhancement. Is it possible to provide separate min/max values for heat and for cool that would override the default, or override the new global setting if specified? Heat and cool min/max set points are quite different (in my house!).
Add an option for displaying thermostat’s humidity sensor and a label indicating which displayed temp is the set point, and the thermostat card would be complete in my opinion. Well, it would if the min/max values were shown at each end of the slider
When developing this I tried to stay as true to the native card as possible adding just a few key features that I thought the native card lacked.
I think that the min/max values need to stay consistent, otherwise the user experience would be odd when you switch to the Auto mode as you would have a mix of both cool and heat ranges.
I see your point about the Auto setting and min/max confusion. We heat, cool, or turn HVAC off entirely here in our Mediterranean climate. Auto has never been set.
Maybe set min/max via a value_template() based on season, HDD/CDD, positive-negative indoor/outdoor temp differential, month, etc. I’m not sure how value_templates are allowed, or not, to set such parameters on cards.
Huge thanks for this, just the solution I had been looking for, for quite some time!
I don’t fully understand why people don’t like to use auto. If it’s really hot out, heat mode is never going to kick on in auto mode and vice versa with cool mode. If you have large temp swings (say overnight), why wouldn’t you want your hvac to compensate? Auto mode ensures the temperature in your home stays in a specific range, what’s not to love?
Suppose I’m in auto mode with a heat setpoint of 60 and a cool setpoint of 80 (super loose, this would be the hardcore energy saving mode). I can think of literally no circumstance when I’m home where I would want heat or cooling to not kick on outside of that range.
We don’t get diurnal temp swings that would call for heat/cool in the same day, or even in the same week. We use the whole-house fan to heat/cool the house with outside air in the shoulder seasons, and at nights in the summer to avoid AC. If only I could open windows automatically, and economically, I’d integrate the whole house fan into the HVAC programming. My CT80 thermostat can control a fresh-air diverter in the HVAC return ducting that could pull outside air rather than recirculate. I may look into that as well.
Fresh air intake/control with HVAC is fantastic, totally get why you’d want that. I also do understand wanting to prioritize cheaper cooling over running the AC, but (from my perspective) if you already have an air conditioning unit installed, why not leave it as a safety net. Surely an auto cooling setup that kicked in at 80 or even 85f would be a nice fallback. It’s hard to imagine anyone with an HVAC unit not wanting to run it if someone is home and the house is actually sitting at 90f.
That all being said, one of the amazing things about HA is the ability to have it function as a thermostat. By changing the actual thermostat’s setpoints and controlling other systems (like intake/exhaust fans) you could do quite a lot.
An ideal thing might be to monitor:
Current power cost
and be programmed with:
target temp (possibly by time of day)
target humidity (possibly by time of day)
target aggressiveness (possibly by time of day)
and make control decisions made on these sensors parameters. Obviously per-room preferences could be included as well.
Is there a way to get this to go to aux heat mode
@enriqg9, I just updated to 86.1 and the icons for heat/cool/auto are overlapping with the fan control drop down. Is that happening to anyone else after the update?
How does your thermostat render the aux heat mode on the native card?
I think the only supported modes are auto, manual, heat, cool, off, fan_only, eco, dry, and idle.
I don’t have an iphone to reproduce, can you see if this happens in your browser as well? this is likely to be a conflict with CSS.
I’m seeing that issue after going to .86.1, oddly enough I’m seeing the actual temperature and the mode icons pushed down into the fan drop down box to the point that I can’t see/select the modes in Opera and in Chrome on the desktop, however it renders fine in Opera or Chrome on my Android phone.