Airzone API: bad 6553,5 value for coolsetpoint, heatsetpoint, setpoint

[BelMaseto]

Seems that in some context the Airzone API is returning an incorrect 6553,5 value for coolsetpoint, heatsetpoint, and setpoint.

Airzone device: Aidoo Pro Fujitsu GEN2 (AZAI6WSPFU2); device firmware according to Airzone App is 10.01/6.09.

This is the curl return for API call when this happens:

{
    "data": [{
            "systemID": 1,
            "zoneID":   1,
            "name": "xxxxxxx",
            "on":   1,
            "double_sp":    0,
            "coolsetpoint": 6553.5,
            "coolmaxtemp":  30,
            "coolmintemp":  18,
            "heatsetpoint": 6553.5,
            "heatmaxtemp":  30,
            "heatmintemp":  18,
            "maxTemp":  30,
            "minTemp":  18,
            "setpoint": 6553.5,
            "roomTemp": 25.700000762939453,
            "sleep":    0,
            "temp_step":    0.5,
            "modes":    [7, 4, 2, 3, 5],
            "mode": 2,
            "speed_values": [0, 1, 2, 3, 4],
            "speeds":   4,
            "speed_type":   0,
            "speed":    0,
            "humidity": 0,
            "units":    0,
            "errors":   [],
            "air_demand":   1,
            "cold_demand":  1,
            "heat_demand":  0,
            "master_zoneID":    1
        }]
}

[Noltari]

Workaround added at https://github.com/Noltari/aioairzone/commit/6e808d2e5b66f19c332555f67c1752ac0da09257. I will try to contact Airzone about this so that they can check this bug and possibly release a firmware update that fixes it.

[BelMaseto]

Alvaro, one more thing about this.

The 6553,5 º setpoint issue has not been seen here since last time I reported it, but something different is happening:

Occasionally setpoint changes itself to 25º in HA without any interaction, while the device still keeps the previous value in the physical control remote as well as in Airzone App. This happens three/five times each day without any logic.

For example, right now both control screen and Airzone App are showing a target temperature of 20º, the one I've set some hours ago, but HA shows 25º, that is also the value returned by a direct API call. It changed itself two hours ago.

Maybe this can help to diagnose the local API setpoint issue.

Regards.

[BelMaseto]

Additional info: 6553,5 º value appears again at HA restart.

[Noltari]

@BelMaseto have you observed any changes in the latest version of Home Assistant? I haven't contacted Airzone yet, but I have done as much as I can from the Home Assistant integration point of view. This still looks like a firmware bug to me which will require an Airzone firmware update...

[BelMaseto]

Morning Alvaro, No, both issues are still there. Regards.

[Noltari]

@BelMaseto is this still happening? If it is, could you please send an email to devapps@altracorporacion.es so the Airzone staff can assist you? When you do, please include the issue URL and your device's MAC address.