Airzone Cloud Local temperature

Feature Requests
1

Hello, I recently purchased an Aidoo device, is currently working with my ducted air conditioning system and also working with the HA integration, good job!

I have a suggestion/feature request, which at least for me, is very important.

The current temperature that returns the integration is the “work temperature”, like we have in the official app on main screen (I already reported to Airzone), with this I mean that the user really cares little about the working temperature (return temperature).

I have read the code from your Python library and I see that it has a variable where it stores the local temperature: API_LOCAL_TEMP here: const.py

Just reading the data returned by the API of the airzone cloud site, I can see that the local temperature of my room exist in the JSON. I think it is really the temperature that the user wants to see.

For now, work_temp is what is returning the integration and I would like to add the local_temp as a current zone temp or something like that.

Here the JSON of website API:

{
    "isConnected": true,
    "connection_date": "2023-11-13T11:13:22.144Z",
    "ws_connected": true,
    "machineready": true,
    "errors": [],
    "warnings": [],
    "manufacturer": {
        "_id": 13,
        "text": "PAN"
    },
    "heating_available": null,
    "max_heat_setpoint": null,
    "max_heat_setpoint_values": [],
    "cooling_available_readonly": null,
    "cooling_available": null,
    "min_cold_setpoint": null,
    "min_cold_setpoint_values": [],
    "heating_available_readonly": null,
    "step": {
        "fah": 1,
        "celsius": 1
    },
    "units": 0,
    "mode_available": [
        1,
        2,
        3,
        4,
        5
    ],
    "speed_values": [
        0,
        2,
        3,
        4,
        5,
        6
    ],
    "speed_type": 0,
    "tai_temp": {
        "celsius": null,
        "fah": null
    },
    "work_temp": {
        "celsius": 25,
        "fah": 77
    },
    "local_temp": {
        "celsius": 21.5,
        "fah": 71
    },
    "range_sp_cool_air_max": {
        "celsius": 30,
        "fah": 86
    },
    "range_sp_cool_air_min": {
        "celsius": 18,
        "fah": 64
    },
    "range_sp_hot_air_max": {
        "celsius": 30,
        "fah": 86
    },
    "range_sp_hot_air_min": {
        "celsius": 16,
        "fah": 61
    },
    "return_temp": {
        "celsius": 25,
        "fah": 77
    },
    "range_sp_dry_air_max": {
        "celsius": 30,
        "fah": 86
    },
    "range_sp_dry_air_min": {
        "celsius": 18,
        "fah": 64
    },
    "range_sp_auto_air_max": {
        "celsius": 27,
        "fah": 81
    },
    "range_sp_auto_air_min": {
        "celsius": 17,
        "fah": 63
    },
    "fan_speed_real": 1,
    "autochange_time_conf": null,
    "autochange_time_values": [],
    "autochange_diff_temp_conf": null,
    "autochange_diff_temp_values": [],
    "dualsp_auto_conf": false,
    "sp_limits_forced": false,
    "name": "Hab."
}

I tag to @Noltari as integration maintainer.

If there is the possibility of adding it, I would be eternally grateful, since it would save all users from buying an Airzone thermostat or another brand just to know the temperature of the room.

2

Just now playing a little with they cloud API, I found an issue, here the WEB API where you can do the same tests.

The enpoint /devices/{deviceId}/config returns well what I sent in the main message:

  "work_temp": {
    "celsius": 25,
    "fah": 77
  },
  "local_temp": {
    "celsius": 22,
    "fah": 72
  },

but, as it’s normal, you retrieve the data for integration from the endpoint: /devices/{deviceId}/status

  "local_temp": {
    "celsius": 25, 
    "fah": 77
  },

As you can see, work_temp field is missing and the value sent in local_temp is what I have in work_temp in the config endpoint.

TEST:
I have actually carried out the test with a dryer providing hot air (from afar) and I can confirm that at the field local_temp its temperature rises in the /config endpoint

but, in the /status endpoint the field local_temp didn’t changed and have the same value as work_temp that has /config endpoint.
I think they have a problem in the mapping of this data

so @Noltari, there’s not an issue on HA, if they fix on their side we’ll not need to touch the integration.

FYI: I sent this feedback to the airzone development team, I hope they will answer me.

3

Thanks for the info @Adrz,

I will try to forward this to Airzone and see what they can do.

1 Like