This repository has been archived by the owner on Mar 25, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 15
Move management points out of the DAIKIN_CMD_SETS #86
Labels
enhancement
New feature or request
Comments
At the same moment we should rename the internal name of each entity to include the name of the management point, that way we can have for example a status flag for the climate and tank with the same field (fe error_code) |
jwillemsen
referenced
this issue
in jwillemsen/daikin_onecta
Oct 30, 2023
…ing on the data, see #86 * custom_components/daikin_residential_altherma/device.py: * custom_components/daikin_residential_altherma/water_heater.py:
#186 does update this for the water heater |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The code currently uses DAIKIN_CMD_SETS to define the possible command sets, but the fact that the management point (climateControlMainZone/gateway/domesticHotWaterTank) is cmd[0] results in a lot of code duplication, would be much easier overal when the getData/getValue calls pass the management point as first argument, that way for a lot of status flags we don't need accessors, now a lot of code is duplicated for the climate and for the hot water tank
The text was updated successfully, but these errors were encountered: