Currently the AirZone integration allows, in the interface, to select in a child zone any mode (heat, cool, fan only). However, AirZone, the devices, only allow this mode setting on the master (parent) zone.
I think it would be interesting to bring this behaviour to the AirZone integration so that in the parent zone you could change the mode, temperature and timer and in the daughters you could only turn on, off, temperature and timer.
Similarly, the daughter zones would only have 2 modes (off and the one considered) when switching to HomeKit integration. This way you wouldn’t have to remember which one you have set on the parent when you go to do just one of the children.
Best regards.
Hola.
Actualmente la integración de AirZone permite, en la interfaz, seleccionar en una zona hija cualquier modo (calor, frio, sólo ventilador). Sin embargo, AirZone, los aparatos, sólo dejan realizar esta configuración de modo en el dispositivo o zona maestra (padre).
Creo que sería interesante llevar este comportamiento a la integración de AirZone de manera que en el dispositivo de la zona padre se pudiera cambiar el modo, la temperatura y el temporizador y en las hijas sólo se pudiera encender, apagar, temperatura y temporizador.
De igual modo que las zonas hijas sólo dispongan de 2 modos (apagado y el que se considere) cuando se pasa a la integración de HomeKit. De esta manera no habría que acordar de cuál tienes puesto en el padre cuando vas a hacer sólo uno de los hijos.
Unfortunately we need to comply with Home Assistant architecture and this isn’t allowed in the current Home Assistant architecture, since there’s no “ON” mode and the “AUTO” mode doesn’t cover that scope.
There’s a discussion open since 2021 and so far it hasn’t been resolved:
I’ve also opened a parallel discussion for abstracting the ON/OFF part from the HVAC mode:
Please, feel free to participate or upvote those discussions so that we can finally get this sorted out.
Is there a way to also select “STOP” in the parent zone? I do not mean “off” - I mean “stop” which also electrically switches off the power to the compressor and therefore is an important mode for me. I can do that in the Airzone app or on the Parent Zone Blueface but as far as I am aware I cannot do that within Homeassistant for now
@Noltari I get why we can’t just turn on/off slaves for now but why couldn’t we just remove set_hvac_mode for slaves like I guess you did in your first implementation, as I mentionned here?
Because this was rejected during the review of the Pull Request by the official Home Assistant developers.
I don’t know why, but I guess that you could open a new PR changing that to the previous behaviour and see what they have to say…
@Noltari
Hello.
I’m using your integration since long time and I’m one of the many trying to solve the problem of the Master Slave while remaining in line with HA guidelines.
I think I have found a solution and it’s perfectly working but I’d need your help to make it 100% integrated.
In few words, I’d need you to add the attributes provided by the integration under the climate entity two additional attributes which are available from the API call.
They are (their API name):
on
mode
Is that possible?
I’m not wasting your time right now to describe my solution but I’m totally available to provide up to the last detail.
Hope you can help.
Thanks
Giacomo
P.S. This is how my frontend looks like now (working)
I can set the mode separately and on/off each zone including the master without affecting the mode
I’m afraid that adding additional attributes to the climate entity will be rejected.
What I can do is create a new switch entity for each zone (both master and slave), which controls the on/off functionality.
And then create a new select entity per master zone which allows changing the HVAC mode on the system without turning on/off that master zone.
@Noltari
I agree with you that adding attributes to the climate entity might be rejected.
Still, the solution that you are proposing would be a big gift for me and the community.
Currently I’m managing to obtain a similar result by using CURL commands but it’s clearly a patch.
If you will be so kind to implement the switch and select entity that you suggest I will be very grateful and ready to immediately test it for you.
I’ll then share the code and lovelace interface when they will be properly modified by using the new entities.
Can’t wait… thanks again
@Noltari thank you for the follow-up.
Local integration is what I’m currently using in my installation, so I’ll be able to test if needed.
I have to confess that I have hard time to understand the “coded language” used in Github so I didn’t add any comment, but if you need any kind of support just let me know.
@Noltari
I just installed 2024.9.0 and, as expected I found the new entity select.xxxx.mode.
It works great !
With small changes to my existing complicated coding I can now change the “mode” of my Airzone installation without touching the current on/off status of the master or slave zone.
I double checked the result of the mode change using the native API command and everything is perfect.
I’m just a bit confused about the other proposed change: the on/off of each zone.
As I already said, I’m not very familiar with the language using in Github, so I don’t understand if the second proposed change (Add Airzone switch entities to zones) which is supposed to give control of the zone’s “on” entity, is either coming with a future version of HA or achievable in a different way.
Could you be so kind and let me know?
Thanks a lot and thanks again for the new entity that gave me already a lot of relief
