Noltari
commented
1 year ago Hi @fredericseiler,
Hi Noltari,
First of all, thanks for your work!
Thanks!
Is there any way to add support for domestic hot water to the lib and HA integration (as a water heater entity for example)?
I was about to try to draft a PR (not very comfortable with python tbh), but my main concern is that I don't really know how to distinguish systems that handle DHW from systems that don't.
On my Aidoo Pro HI4 (AZAI6WSPHI4 linked to a Hitachi air/water heat pump), I can get DHW data when I send a POST request to the /hvac endpoint with only the global system ID and no specific zone:
{ "systemID": 0 }
Yes, this is documented in the Airzone Local API. In order to get/update the DHW config systemID should be 0 and there should be no zoneID at all. What does your device return when performing a POST request with both zoneID and systemID?
{
"systemID": 0,
"zoneID": 0
}I need to know how hard it would be to distinguish between HVAC and DHW devices.
And the values returned by the local API:
{ "data": { "systemID": 0, "acs_temp": 43, "acs_setpoint": 45, "acs_mintemp": 30, "acs_maxtemp": 75, "acs_power": 1, "acs_powerful": 0 } }
Luckily those values seem pretty simple, so it shouldn't be hard to support DHW.
I can also set the DHW setpoint, power and powerful operation mode, with a PUT request.
But, if I try the same on my Aidoo Pro HI2 (AZAI6WSPHI2 linked to a Hitachi air/air ducted AC, so no DHW), I get similar results:
{ "data": { "systemID": 0, "acs_temp": 0, "acs_setpoint": 0, "acs_mintemp": 0, "acs_maxtemp": 0, "acs_power": 0, "acs_powerful": 0 } }
Yeah, that seems to be a bug, since that device shouldn't return any of those values. My Airzone Flexa just returns an error stating that there's no DHW device available.
Besides that all values are set to 0, there's no way to tell them apart (same
ws_typews_aidoo, andsystem_type2).All Airzone integration users that don't deal with DHW will have a ghost water heater, that's far from ideal...
We can see if some/all of those values are 0 and avoid exposing the DHW device in that specific case. It's not ideal, but it should work.
What about another integration dedicated to airzone DHW only? Seems redondant?
No, that isn't an option. We should be able to distinguish between both types of devices and expose the corresponding devices (HVAC, DHW...) with the same integration.
fredericseiler
Fonsohome
Hi Noltari,
First of all, thanks for your work!
Is there any way to add support for domestic hot water to the lib and HA integration (as a water heater entity for example)?
I was about to try to draft a PR (not very comfortable with python tbh), but my main concern is that I don't really know how to distinguish systems that handle DHW from systems that don't.
On my Aidoo Pro HI4 (AZAI6WSPHI4 linked to a Hitachi air/water heat pump), I can get DHW data when I send a POST request to the /hvac endpoint with only the global system ID and no specific zone:
And the values returned by the local API:
I can also set the DHW setpoint, power and powerful operation mode, with a PUT request.
But, if I try the same on my Aidoo Pro HI2 (AZAI6WSPHI2 linked to a Hitachi air/air ducted AC, so no DHW), I get similar results:
Besides that all values are set to 0, there's no way to tell them apart (same
ws_typews_aidoo, andsystem_type2).All Airzone integration users that don't deal with DHW will have a ghost water heater, that's far from ideal...
What about another integration dedicated to airzone DHW only? Seems redondant?