Figured it out, reflashed, rewrote and magically it fixed itself. Thanks again for the card!
@edwardreed81 Were you able to figure something out? This might be related to thermostat, 3 persons with similar issues and same thermostat. See open issue on GitHub.
Nope, I gave up on my zwave thermostat and reinstalled the Nest I had. I like the idea of keeping everything local, but I donāt have the energy to fight with this stuff.
Thanks for the reply! No, itās not a problem with the thermostat sending data back to HA.
I created two standard thermostat cards ā one for the cooling entity, and one for the heating entity of the same thermostat. When I change the target temperature on the physical thermostat, they both show the new number. (I.e., the heating card shows the correct heating target temp, and the cooling card shows the correct cooling target temp.)
But on the dual-thermostat card, the new target temperature only gets updated for cooling (or whichever entity is listed first). If the thermostat is in heating mode, the target temp doesnāt update on the card, since cooling is listed first. So I think itās a problem with the dual-thermostat card.
@enriqg9 I have a feature request. Is there any chance you could make it possible to add a humidity reading onto this card? A while back I was able to look at the code to add in that min/max slider option, but Iām looking at it now and I canāt wrap my head around it enough to be able to add in a value from a sensor.
Hi!
My thermostat supports the operation modes Energy Heat, Heat, Cool and Off, but I only have the entities climate.thermofloor_as_heatit_thermostat_tf_021_energy_heat and climate.thermofloor_as_heatit_thermostat_tf_021_heating available to configure, so I guess the only modes the thermostat actually supports is Energy Heat and Heat (in addition to Off, of course). How would this dual thermostat card handle this - as āCoolā doesnāt take as a valid operation mode?
The operation modes are rendered from the first entity, some thermostats define all modes on both entities.
Im new at this can somone tell me why I only have AC not Heat. there is only a snowflake not a flame. I thought this was a dual thermostat. please help
Show us what u have done so far
I put the dual-thermostat.js in the www/local/dual-thermostat/
this is my ui-lovelace.yaml
resources:
- name: dual-thermostat
type: js
url: /local/dual-thermostat/dual-thermostat.js?v=1
title: Home
views: - cards:
- entities:
- entity: climate.upstairs_ac
type: cool - entity: climate.upstairs_heat
type: heat
min_slider: 50
max_slider: 90
name: Upstairs
type: ācustom:dual-thermostatā
fan_control: false
icon: āhass:home-assistantā
id: home
title: Home
type: vertical-stack
- entity: climate.upstairs_ac
- entities:
This is one single thermostat that defines 2 entities correct? Check what modes are defined by your thermostat on each entity. The card will grab the available modes from the first provided entity.
I thought it was 2 entities that shows up this is what I think is should look like
It should have fire and snow flake but it doesnāt
mineā¦
If your climate.upstairs_heat
and climate.upstairs_ac
are not the same device with 2 entities, this is not the card for you.
Great stuff. any way to show current mode in auto, something like Auto: Heat or Auto: Cool?
Not currently supported, sorry.
Iām not familiar with Zones but the actions look good to me, try setting operation_mode to āautoā if supported by your thermostat.
Has this functionality been replicated with the 0.96 update? It looks like they have the option of having a temperature range on the built in climate card with that release.
No, the purpose of this card is that the climate devices are split into a heating entity and cooling entity.
The devices that utilize this card while in heating mode only allow set points via the heating entity and vice versa.
I took the plunge and updated to the .96 release and the cards arenāt showing up at all. Any ideas what might be causing that? Iām guessing itās related to the updates to the climate component.
Iām not on 0.96 yet Iāll try to update tomorrow and debug.