Add sensors for heating.power.consumption dhw+heating+total

[tescnovonesis]

Fix for home-assistant/core#155695

Tested for Vitocal 252-A

values of heating.power.consumption.summary.dhw and heating.power.consumption.summary.heating is not being updated. A reboot of the "Communication module" in the ViCare Android App would update the values, but then become frozen day after.

But following values seems indeed to update nicely. heating.power.consumption.dhw, heating.power.consumption.heating and heating.power.consumption.total.

Writing a mail to developer mail of Viesmann, with the subject: "Energy consumption data is not updating and gateways require daily reboots" and adding Gateway serial number, found in the ViCare app, did not yield any response. (home-assistant/core#130273 (comment))

Therefore, these new values are proposed to be extracted

[tescnovonesis]

Branch for PR is here:
https://github.com/tlinnet/PyViCare/tree/core_issue_155695

It seems I am not able to create a PR

[CFenner]

This is weird, no idea why it's restricted.

[tlinnet]

Can you make the PR?

And for reference, there was a service window for ViCare API 18/11-2025.
Some values that before was reported 0, is now showing something.

So maybe something IS moving.

In any case, I would be happy to have these properties available, so it's easier to prepare to core

[tlinnet]

If this PR makes it through, a follow up PR should be made to:
https://github.com/home-assistant/core/blob/dev/homeassistant/components/vicare/sensor.py

Adding

ViCareSensorEntityDescription(
	key="energy_consumption_heating_year",
	translation_key="energy_consumption_heating_year",
	native_unit_of_measurement=UnitOfEnergy.KILO_WATT_HOUR,
	value_getter=lambda api: api.getPowerConsumptionHeatingYear(),
	unit_getter=lambda api: api.getPowerConsumptionHeatingUnit(),
	device_class=SensorDeviceClass.ENERGY,
	state_class=SensorStateClass.TOTAL_INCREASING,
	entity_registry_enabled_default=False,
),
ViCareSensorEntityDescription(
	key="energy_consumption_dhw_year",
	translation_key="energy_consumption_dhw_year",
	native_unit_of_measurement=UnitOfEnergy.KILO_WATT_HOUR,
	value_getter=lambda api: api.getPowerConsumptionDomesticHotWaterYear(),
	unit_getter=lambda api: api.getPowerConsumptionDomesticHotWaterUnit(),
	device_class=SensorDeviceClass.ENERGY,
	state_class=SensorStateClass.TOTAL_INCREASING,
	entity_registry_enabled_default=False,
),

[CFenner]

I invited you as a collaborator, try again, please.

[tescnovonesis]

Can I ask for invitaiton to tlinnet
Just to separate home from work accounts

[tlinnet]

I am really bad at this...
I was able to make PR, when I was in my own account
#667

[tlinnet]

After rename, sensors in https://github.com/home-assistant/core/blob/dev/homeassistant/components/vicare/sensor.py

    ViCareSensorEntityDescription(
        key="energy_consumption_heating_this_year",
        translation_key="energy_consumption_heating_this_year",
        native_unit_of_measurement=UnitOfEnergy.KILO_WATT_HOUR,
        value_getter=lambda api: api.getPowerConsumptionHeatingThisYear(),
        unit_getter=lambda api: api.getPowerConsumptionHeatingUnit(),
        device_class=SensorDeviceClass.ENERGY,
        state_class=SensorStateClass.TOTAL_INCREASING,
        entity_registry_enabled_default=False,
     ),
    ViCareSensorEntityDescription(
        key="energy_consumption_dhw_this_year",
        translation_key="energy_consumption_dhw_this_year",
        native_unit_of_measurement=UnitOfEnergy.KILO_WATT_HOUR,
        value_getter=lambda api: api.getPowerConsumptionDomesticHotWaterThisYear(),
        unit_getter=lambda api: api.getPowerConsumptionDomesticHotWaterUnit(),
        device_class=SensorDeviceClass.ENERGY,
        state_class=SensorStateClass.TOTAL_INCREASING,
        entity_registry_enabled_default=False,
    ),

[CFenner]

If you rename existing functions, use @deprecated to keep compatibility for ~4 months. Just search the code, we‘ve done that before.

[tlinnet]

If you rename existing functions, use @deprecated to keep compatibility for ~4 months. Just search the code, we‘ve done that before.

Thanks :)
I think I am still implementing "new" functions. And just aligning "best" name for these :)
I was first inspired by the "summary" functions, but now inspired by the non-summary functions.