Dual Thermostat Card

Share your Projects!
186

I realize this card was developed to combine Tstats that create separate entities for heat and cool into 1 control. As stated by others, most recently @nzhook, most thermostats expose a single entity with a heat/cool mode, which require a separate heat and cool setpoint range.

Problem is, I’ve not found any control with a UI to select these 2 setpoints in such a way as this dual thermostat card does, which would be perfect if it could support a single climate entity for its heat/cool mode.

How does anyone manage to use their single entity Tstat heat/cool mode if the control doesn’t support dual setpoints?

187

Usually when you change the mode, the setpoint is changed for that mode ie: Mode = Heat, Heat Setpoint get’s adjusted

188

Thanks for the tip @firstof9! That makes perfect sense. It’s not working for me though, so I’ll need to track down if this is an issue with the Homekit/thermostat component.

189

With “Climate 1.0” adjusting the set point on cool should adjust it on heat as well from what I can tell.

190

I’m having an issue with this where I’m not seeing the auto-mode:

34%20PM
34%20PM936×808 28.2 KB

I think the setup is fairly standard:

resources:
  - type: js
    url: /community_plugin/dual-thermostat/dual-thermostat.js

cards:
  - type: custom:dual-thermostat
    name: Home
    entities:
      - entity: climate.honeywell_th6320zw2003_t6_pro_series_thermostat_cooling_1
        type: cool
      - entity: climate.honeywell_th6320zw2003_t6_pro_series_thermostat_heating_1
        type: heat
    fan_control: true
    min_slider: 12
    max_slider: 32

Not sure if I’m missing something here or if its just not working. Anyone have any thoughts on what might be going on here?

191

Check the dev-tools->states for climate.honeywell_th6320zw2003_t6_pro_series_thermostat_cooling_1 and see if hvac_modes shows auto as an option.

192

Ah okay, I misunderstood. I thought the auto mode was a function of the plugin rather than the climate entity. That makes more sense, thanks!

193

I’m looking for help in making the inner background transparent to match the rest of my theme. I know jack squat about css. I’d like the card to have transparency like the light entity cards:

dual lamps transparent

dual thermostat
dual thermostat345×648 77.1 KB

Any help is much appreciated!

Thanks,
Justin

194

I’m running haos installed in a virtualenv, so I have a config/ directory with all my .yaml files in it. Where should clone this repo and which yaml do I need to modify to use this?

Been looking for this for a while

195

Use HACS to install this card into your lovelace UI.

196

I dont have HACS … mine is not a hassio, it’s just hass inside venv

197

Install HACS with these instructions, it makes installing this card and many additional custom components/cards/themes 100% easier.

198

you create a custom_components folder inside your config directory. just drop the files in there.

199

I did that but i’m not getting very far. After restarting homeassistant, trying to add the integration shows an un-labeled line for hacs. Following the wizard is almost impossible, no visible text labels on the dialogs.

The home-assistant log gives a warning

2019-12-11 04:30:00 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.

Is there another way to do this or a way around this problem?

200

I didn’t mention anything about using hacs

201

Sorry, someone else suggested that. I followed the guide to install hacs, but not having too much luck

[EDIT]
Finally got hacs installed. Looks like somehow it was missing a hidden directory called .translations . Once I copied that over to config/custom_components/hacs its all good.

202

For anyone else using this because of z-wave thermostats, HA 0.103 contains a change that now presents z-wave thermostats as one. You may not need this anymore.

1 Like
203

I see a single control UI for a z-wave thermostat in 0.103, although it did change my entity name for whatever reason.

204

Probably because before they had identification in the name to identify the heat and cooling controls.

1 Like
205

Yep,
All good after updating the cards with the updated entity names.

Now, 0.103 also broke my lutron_caseta integration, I now need to go figure out what happened there.