Problem with Airzone integration ("fan_only" mode) #96994

jjromper · 2023-07-21T09:16:51Z

The problem

When I select the "fan_only" mode of operation, the "Airzone" integration fails and is no longer available. The only way to make this integration available again is to change the mode of operation on the physical device or in the "Airzone Cloud" App. This situation only occurs with the "fan_only" operating mode.

What version of Home Assistant Core has the issue?

core-2023.7.2

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Airzone

Link to integration documentation on our website

https://www.home-assistant.io/integrations/airzone

Diagnostics information

home-assistant_airzone_2023-07-20T17-33-19.800Z.log

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Logger: homeassistant.components.airzone.coordinator
Source: components/airzone/coordinator.py:40
Integration: Airzone (documentation, issues)
First occurred: 19:19:15 (7 occurrences)
Last logged: 19:25:24

Unexpected error fetching airzone data: 'setpoint'
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 283, in _async_refresh
    self.data = await self._async_update_data()
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/airzone/coordinator.py", line 40, in _async_update_data
    await self.airzone.update()
  File "/usr/local/lib/python3.11/site-packages/aioairzone/localapi.py", line 246, in update
    self.parse_system_zones(system_data)
  File "/usr/local/lib/python3.11/site-packages/aioairzone/localapi.py", line 279, in parse_system_zones
    self.zones[system_zone_id].update_data(zone_data)
  File "/usr/local/lib/python3.11/site-packages/aioairzone/zone.py", line 165, in update_data
    self.temp_set = float(zone_data[API_SET_POINT])
                          ~~~~~~~~~^^^^^^^^^^^^^^^
KeyError: 'setpoint'

Additional information

No response

home-assistant · 2023-07-21T09:16:56Z

Hey there @Noltari, mind taking a look at this issue as it has been labeled with an integration (airzone) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of airzone can trigger bot actions by commenting:

@home-assistant close Closes the issue.
@home-assistant rename Awesome new title Renames the issue.
@home-assistant reopen Reopen the issue.
@home-assistant unassign airzone Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

airzone documentation
airzone source
_{^{(message by IssueLinks)}}

jjromper · 2023-07-21T09:21:55Z

In case it's relevant, I'm using an Aidoo PRO connected to a Daikin machine.

Noltari · 2023-07-22T07:03:50Z

@jjromper it seems that your device stops providing the setpoint when it's in fan_only mode. My device still provides the setpoint value in that case...
That's the issue with Airzone devices, every device is different to each other 🥲
Anyway, this should be easy to fix, so I will try to fix it next week.

jjromper · 2023-07-22T08:51:46Z

Gracias Álvaro. Es una funcionalidad que no había probado hasta ahora. El modo ventilación no lo había usado antes, así que no sé si eso ocurre en otras versiones. Muchísimas gracias. El sáb., 22 jul. 2023 9:04, Álvaro Fernández Rojas ***@***.***> escribió:

…

@jjromper <https://github.com/jjromper> it seems that your device stops providing the setpoint when it's in fan_only mode. My device still provides the setpoint value in that case... That's the issue with Airzone devices, every device is different to each other 🥲 Anyway, this should be easy to fix, so I will try to fix it next week. — Reply to this email directly, view it on GitHub <#96994 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A55PIQHVLBGKKKA3SACJDQ3XRN3ODANCNFSM6AAAAAA2SSG6KI> . You are receiving this because you were mentioned.Message ID: ***@***.***>

BelMaseto · 2023-08-08T21:57:34Z

Hola Alvaro,

Same problem here with Aidoo PRO Fujitsu version when selecting fan_only. Error log is identical.

Waiting for the fix...

Noltari · 2023-08-10T11:33:00Z

@jjromper should be fixed with #98163

Waiting for the fix...

@BelMaseto in the future try to refrain from saying things like this.
You need to understand that I do this on my free time so I will fix things when I have time.

jjromper · 2023-08-10T11:54:00Z

Thank you very much Noltari!
Sorry for my stupid question, but how to update my HA to the new version that contains the fix? Is it just adding back the Airzone integration? Thank you!

Noltari · 2023-08-10T12:15:50Z

Thank you very much Noltari! Sorry for my stupid question, but how to update my HA to the new version that contains the fix? Is it just adding back the Airzone integration? Thank you!

Since this is a bugfix it would be great to have it cherry-picked to the next 2023.8.X release. However, if this doesn't happen you'll have to wait to the next Home Assistant 2023.9 release.

jjromper · 2023-08-10T12:19:27Z

Perfect!
I can wait.
Thanks again.

BelMaseto · 2023-08-10T13:38:10Z

@Noltari
I said that as you said you've found the issue, so in this context I'm waiting for the fix...whenever it comes.
Of course, thanks a lot for your work.
Regards.

Noltari · 2023-08-12T09:25:52Z

@jjromper @BelMaseto the fix is included in the 2023.8.2 release
When you have time confirm if it's working or if it requires further changes.

BTW, I'm interested in testing the following 2 cases:

The Airzone device is configured in a different mode from fan_only before upgrading or reloading Home Assistant or the Airzone integration and then it's changed to fan_only mode. This one should work with my changes and the setpoint should still show the last configured value before changing to fan_only mode, but I don't know what happens if you change the setpoint while in fan_only mode, could you try that? Does the API return an error?
The Airzone device is configured in fan_only* mode before restarting Home Assistant or reloading the integration. Does it work? Is it possible to change to a different HVAC mode? What happens with the setpoint? It should be Null at first and then it should appear after the HVAC is changed to a different mode (probably after waiting 1 minute without changing anything else, which is the scan interval).

@Noltari I said that as you said you've found the issue, so in this context I'm waiting for the fix...whenever it comes. Of course, thanks a lot for your work. Regards.

No problem, sorry for the misunderstanding.

jjromper · 2023-08-12T11:07:09Z

I will update to version 2023.8.2 at the beginning of September, and I will test the use cases that you mention. Thanks a lot!

BelMaseto · 2023-08-18T07:34:05Z

Hi Alvaro,

Just updated to 2023.8.2

Fan_only now works as expected: no more NA when changing to this mode from cool

On HA reload while in fan_only mode it starts in NA state but after a while it changes to correct Fan mode.

Thanks one more time for the work.

jjromper · 2023-08-18T09:15:45Z

Perfect! Thanks for testing! El vie, 18 ago 2023 a las 9:34, BelMaseto ***@***.***>) escribió:

…

Hi Alvaro, Just updated to 2023.8.2 Fan_only now works as expected: no more NA when changing to this mode from cool On HA reload while in fan_only mode it starts in NA state but after a while it changes to correct Fan mode. Thanks one more time for the work. — Reply to this email directly, view it on GitHub <#96994 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A55PIQBDNC4LZRP7UKJH7E3XV4LHTANCNFSM6AAAAAA2SSG6KI> . You are receiving this because you were mentioned.Message ID: ***@***.***>

BelMaseto · 2023-08-18T20:55:31Z

Alvaro, seems that something different is not working now.

After some time, selected temperature changes itself to 6553.5, but only in HA, not in the Airzone App or the physical AC controller itself.

Clicking down (I use Mushroom Climate Card) goes to 30º (my maximum), but after some time, it changes again to 6553.5,

This is the output of the API command called via curl:

{
	"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
		}]
}

Maybe this is api related, but not seen before.

Noltari · 2023-08-21T06:28:07Z

Alvaro, seems that something different is not working now.

After some time, selected temperature changes itself to 6553.5, but only in HA, not in the Airzone App or the physical AC controller itself.

The Airzone App is based on the Cloud API, so the information available on each one might be different.

Clicking down (I use Mushroom Climate Card) goes to 30º (my maximum), but after some time, it changes again to 6553.5,

This is the output of the API command called via curl:

{
	"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
		}]
}

Maybe this is api related, but not seen before.

Hi @BelMaseto,

Unfortunately, this seems to be a different bug and since the Local API is returning an incorrect value of 6553.5 for [coolsetpoint, heatsetpoint, setpoint] it's an Airzone bug so there's not much we can do about it in the Home Assistant integration but to try to work around it.
We can probably check the value of the setpoint and ignore it if it's greater than [coolmaxtemp, heatmaxtemp, maxTemp]. This might work and hopefully we don't break other devices.

Can you open a new issue on the library repo? https://github.com/Noltari/aioairzone/issues
Please, include all the information there so we can look into it and send it to the Airzone staff:

Airzone device model.
The output of the API command called via curl.

Best regards,
Álvaro.

BelMaseto · 2023-08-21T06:51:23Z

New issue created.

By the way, no need to implement a workaround, I've created my own automation to set a value of 25º when this happens.

Regards.

home-assistant bot added the integration: airzone label Jul 21, 2023

joostlek mentioned this issue Aug 10, 2023

Update aioairzone to v0.6.5 #98163

Merged

20 tasks

joostlek closed this as completed in #98163 Aug 10, 2023

github-actions bot locked and limited conversation to collaborators Sep 20, 2023

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Problem with Airzone integration ("fan_only" mode) #96994

Problem with Airzone integration ("fan_only" mode) #96994

jjromper commented Jul 21, 2023

home-assistant bot commented Jul 21, 2023

jjromper commented Jul 21, 2023

Noltari commented Jul 22, 2023

jjromper commented Jul 22, 2023 via email

BelMaseto commented Aug 8, 2023

Noltari commented Aug 10, 2023

jjromper commented Aug 10, 2023

Noltari commented Aug 10, 2023

jjromper commented Aug 10, 2023

BelMaseto commented Aug 10, 2023

Noltari commented Aug 12, 2023

jjromper commented Aug 12, 2023

BelMaseto commented Aug 18, 2023

jjromper commented Aug 18, 2023 via email

BelMaseto commented Aug 18, 2023

Noltari commented Aug 21, 2023 •

edited

Loading

BelMaseto commented Aug 21, 2023

Problem with Airzone integration ("fan_only" mode) #96994

Problem with Airzone integration ("fan_only" mode) #96994

Comments

jjromper commented Jul 21, 2023

The problem

What version of Home Assistant Core has the issue?

What was the last working version of Home Assistant Core?

What type of installation are you running?

Integration causing the issue

Link to integration documentation on our website

Diagnostics information

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

home-assistant bot commented Jul 21, 2023

jjromper commented Jul 21, 2023

Noltari commented Jul 22, 2023

jjromper commented Jul 22, 2023 via email

BelMaseto commented Aug 8, 2023

Noltari commented Aug 10, 2023

jjromper commented Aug 10, 2023

Noltari commented Aug 10, 2023

jjromper commented Aug 10, 2023

BelMaseto commented Aug 10, 2023

Noltari commented Aug 12, 2023

jjromper commented Aug 12, 2023

BelMaseto commented Aug 18, 2023

jjromper commented Aug 18, 2023 via email

BelMaseto commented Aug 18, 2023

Noltari commented Aug 21, 2023 • edited Loading

BelMaseto commented Aug 21, 2023

Noltari commented Aug 21, 2023 •

edited

Loading