Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
BelMaseto opened this issue Aug 21, 2023 · 5 comments
Open
Assignees
Labels
hw bug Hardware bug

Comments

@BelMaseto
Copy link

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
Copy link
Owner

Noltari commented Aug 21, 2023

Workaround added at 6e808d2.
I will try to contact Airzone about this so that they can check this bug and possibly release a firmware update that fixes it.

@Noltari Noltari added the hw bug Hardware bug label Aug 21, 2023
@Noltari Noltari self-assigned this Aug 23, 2023
@BelMaseto
Copy link
Author

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
Copy link
Author

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

@Noltari
Copy link
Owner

Noltari commented Sep 21, 2023

@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
Copy link
Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hw bug Hardware bug
Projects
None yet
Development

No branches or pull requests

2 participants