Sounds pretty similar to my Honeywell Evohome 12 zone system, though mine is radiator based rather than forced air. It does have individual set points and on/off per zone/room, global on/off, only thing it doesn’t have is the master zone.
I personally don’t see any problem with having all the individual thermostats for each room (how the evohome integration works), and then adding one sensor and some service calls for the global on/off and myzone settings… Evohome also has a global thermostat and some service calls to set the more global settings like home/away mode, guest mode, etc.
Anyway, I’d say go look at the evohome integration for inspiration, it does pretty much everyhing you are asking for.
How do you style your input numbers? I actually like them.
I have a different setup (a custom appdaemon app to control zones based on localised temperatures, while also allowing individual manual overrides and conditions), my target temp sensor uses the custom number-box card - but I find it a little to compact.
Inside a vertical stack and entities card, also using the number-box card. I want the vertical spacing to be a bit more compact but the input number and +/- need to have some larger font and padding. Unfortuantely some of my styling changes play with margins/padding and increase vertical spacing, but it is ok for now… (open to improvements if you are bette with CSS than I am!)
If you have temp sensors in your Zones the integration creates both climate entities (which has target and current temp values) but also creates a sensor entity with the current temp (which is disabled by default). The current temp should work all the time but I can’t actually confirm that as I don’t have sensors in my zones.
Would people be interested in me creating a second integration which can perform the zone damper control for systems without the official temperature sensors? Basically take the existing Node Red implementations, but create new climate entities that control the Advantage Air ones?
I could just add it as a feature to Advantage Air, but figure a separate integration could then be used to control other systems too.
yes please. I am building my own system, using a mixture of KNX dampers, ESPhome/DHT22 temperature sensors and 2 Daikin duckted systems. I am tring to bring it all together is a similiar way to advantage air using Hassio and node Red.
Hey @Brett_Adams
I have installed the system today - working a treat!
Thanks heaps for all your work.
FYI - I have the temp sensors in each zone and can see the current temp even with the system off. I moved them around and they update even when the system is off also.
@Tockers I am pulling my hair out trying to get my dashboard card to look like yours.
I have all the zone set points adjusting with input numbers and automations.
I am struggling a bit with the zone on/off control
I have used a switch template to give me the on/off status and control
My issue is, when the hvac_mode gets changed from the air cond app (wife uses this ) the switch status does not update. I tried the line commented out in the above template but it results in the switch turning the hvac_mode to fan-only but it won’t turn it off and the switch status remains off.
@zacolly I just used simple button entities with a toggle tap action to open/close a zone. It also receives state updates from the ezone system if that is used (through the integration). Full ezone card:
Thanks heaps!
Now I know what the difference is. I have a MyAir not a eZone so I have a climate entity for each zone, not a cover.
Do you know how I can use a button to toggle the entity attribute hvac_mode from fan_only and ‘off’?
My switch template above does it but the switch on/off status doesn’t update when the hvac_mode is changed using the MyAir App.
aircond_living_zone_on:
alias: AirCond Living Zone ON
sequence:
- service: climate.set_hvac_mode
target:
entity_id: climate.living
data:
hvac_mode: fan_only
mode: single
icon: hass:fan
aircond_living_zone_off:
alias: AirCond Living Zone OFF
sequence:
- service: climate.set_hvac_mode
target:
entity_id: climate.living
data:
hvac_mode: 'off'
mode: single
icon: hass:fan-off
Interesting little wrinkle overnight for my climate automation. Part of my automation triggers on a temperature change request - so even if the system is inactive, changing climate.ac temperature triggers the system to come on, assuming that you want a change based on the input.
That’s working very well - until last night we had a 1am 1 minute power-out and climate.ac temperature went to null… That change was ignored as it was not to a valid value, but when the power came back on, and climate.ac temperature was reset to 22, automation saw this as a change to 22 (correctly), and the air-con came on.
I need a condition in the automation to check if the trigger’s previous state was numerically valid (and not empty), so it does not interpret recovery from a power-out as a temp change request.
The trigger is this:
trigger:
- platform: state
entity_id: climate.ac
attribute: temperature
From searching on here, I think I need a condition to check the previous state, i.e. trigger.from_state.state, but I’m not sure on the best way to do this.
Would this work, or is there a better way to check (the minimum settable temperature on the system is 16, so the test should pass if it’s set).
condition: template
value_template: "{{ trigger.from_state.state | int >= 16 }}"
Haven’t had another power-cut to test this, but one thing I have worked out is that the value_template for a trigger based on the AC unit’s temperature on a change needs to be (in case anyone else runs into this):
value_template: '{{ trigger.from_state.attributes.temperature | int >= 16 }}'
not…
value_template: "{{ trigger.from_state.state | int >= 16 }}"
Would people be interested in me creating a second integration which can perform the zone damper control for systems without the official temperature sensors? Basically take the existing Node Red implementations, but create new climate entities that control the Advantage Air ones?
I could just add it as a feature to Advantage Air, but figure a separate integration could then be used to control other systems too.
yes please! Has this been done anywhere?
I have a 5 zone system but not the eZone sensors. I have the Xiaomi temperature sensors in each zone and would desperately like to be able to change the dampers or master zone temp to prevent the rooms from over/under cooling
Second this - NodeRed works great but needs some work to get it going.
If you do decide to add damper control with external temp sensors, would be great to include confgurables like min/max cover positions, degrees C range, and cover change amount. E.g. I updated your NodeRed config to increase the cover chance %age to get quicker results.
) the switch status does not update. I tried the line commented out in the above template but it results in the switch turning the hvac_mode to fan-only but it won’t turn it off and the switch status remains off.
