The /clife-svc/pu/air_duct_energy gateway endpoint returns hourly breakdown data alongside electricTotal, which get_daily_energy_kwh() currently discards.
Available data
{
"resultData": {
"electricTotal": 0.0,
"electricCurve": {"0": "0.00", "1": "0.00", ..., "23": "0.00"},
"coolingCurve": {"0": "0", ..., "23": "0"},
"heatingCurve": {"0": "0", ..., "23": "0"},
"durationTotal": 0,
"costTotal": "0.00",
"costCurve": {"0": "0.00", ..., "23": "0.00"}
}
}
Open questions
- What are the units for cooling/heating curves? Minutes? On/off cycles?
- Is
costTotal/costCurve based on a configurable electricity price?
- Is this useful for HA energy dashboard, or only for custom sensors?
HA integration considerations
- HA energy dashboard expects
total_increasing state class sensors
- Hourly data could feed statistics or be exposed as attributes
- Polling frequency: consider calling only every Nth poll in the coordinator
The
/clife-svc/pu/air_duct_energygateway endpoint returns hourly breakdown data alongsideelectricTotal, whichget_daily_energy_kwh()currently discards.Available data
{ "resultData": { "electricTotal": 0.0, "electricCurve": {"0": "0.00", "1": "0.00", ..., "23": "0.00"}, "coolingCurve": {"0": "0", ..., "23": "0"}, "heatingCurve": {"0": "0", ..., "23": "0"}, "durationTotal": 0, "costTotal": "0.00", "costCurve": {"0": "0.00", ..., "23": "0.00"} } }Open questions
costTotal/costCurvebased on a configurable electricity price?HA integration considerations
total_increasingstate class sensors