Advantage-Air integration - add option to set MYZONE

Tags: #<Tag:0x00007f3264d50aa0>

The advanatage air integration has the option to define a “MYZONE”. It appears in the get result as shown below.

					{"error":0,"maxDamper":100,"measuredTemp":25.2,"minDamper":0,"motion":0,"motionConfig":1,"name":"Master Bed","number":2,"rssi":42,"SensorUid":"001224","setTemp":24.0,"state":"open","tempSensorClash":false,"type":1,"value":100
					{"error":0,"maxDamper":100,"measuredTemp":24.9,"minDamper":0,"motion":0,"motionConfig":1,"name":"Ollie\u0027s Room","number":3,"rssi":52,"SensorUid":"0010b0","setTemp":24.0,"state":"open","tempSensorClash":false,"type":1,"value":90
					{"error":0,"maxDamper":100,"measuredTemp":25.0,"minDamper":0,"motion":0,"motionConfig":1,"name":"Jack\u0027s Room","number":4,"rssi":54,"SensorUid":"001223","setTemp":24.0,"state":"open","tempSensorClash":false,"type":1,"value":100

This value specifies which zone the AC unit will use as a overall setpoint - and the ac will control its fan / and setpoint based on that zone …interesting I have noted setting it means the AC setTemp stays at 16.

I was actually going to ring advantage air to confirm why this is the case.

This was my idea but I am just not familiar enough with python

    def my_zone_id(self):
        """Return the current my_zone zone id"""
        return self._ac["myZone"]
    async def set_myzone_id(self, my_zone_id):
        """Set the MyZone ID"""
        await self.async_change({self.ac_key:{"info":

In this case the myzone id is a integer that ranges based on the number of zones for that ac

However it may be better to transalte from the zone names.

Hey @Narimm, as code owner of this integration I wasn’t even notified as far as I can tell about your request. So sorry for the delay.

I would be more than happy to implement this for you. I’ll update my dev environment tomorrow and get a pull request raised.

So I’m adding a service where you can set the zone climate entity as the MyZone. This intentionally will exclude zone cover entities since I believe you must have a temperature sensor for it to be a MyZone.

However, how do you think I should tell the user which zone is currently the MyZone? Options are:

Numeric Attribute on the main climate entity
Boolean Attribute on the zone climate entity
Sensor with the numeric or name of the MyAir zone
Boolean Sensor for each zone climate entity.

I have so far avoided attributes and would set any new sensors as disabled by default, so am leaning towards one of the last two. The Boolean Sensor seems the most consistent.

You are dead right you cant actually use MyZone unless you have Temp sensors. As far as I can tell the MyZone function simply tells the system which zone to use as the set point. The other thing I just realized might be helpful to know is constant zones. They are listed in the main ac config. The reason they are important is that they are auto switched on if the pressure inside the unit builds up. In my case its Zone 1 and Zone 2 as above.

As far as what type on sensor for both the constant and myzone its should be a boolean sensor I agree

So I have a PR raised with the service. I’ll try sneak the Boolean sensors in now.