ViCare: Vitocal 252-A current power consumption and heat production are available via API but not exposed as entities #4793
Unanswered
metalcreep
asked this question in
Integration enhancements
Replies: 1 comment
|
🏷️ I've automatically added the |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Integration name
Viessmann ViCare
Link to integration documentation on our website
https://www.home-assistant.io/integrations/vicare/
Describe the enhancement
I am using the built-in Viessmann ViCare integration with a Viessmann Vitocal 252-A.
The Viessmann API response for my device contains the following live values:
Both features are enabled, ready and connected and return numeric values in kW.
However, Home Assistant Core 2026.9.0 does not expose either value as an entity.
I checked the ViCare entities in Home Assistant:
The existing Inverter power entity is a different value and should not be considered equivalent to:
The API exposes inverter power separately from the system-level current electrical power consumption.
Expected behavior
The ViCare integration should expose the existing API features
as Home Assistant sensor entities.
For example:
Both values are reported by the Viessmann API in kW.
Actual behavior
No Home Assistant entities are created for these two API features.
The related live entities currently exposed include:
but not:
Example API data
For current electrical power consumption:
{
"feature": "heating.power.consumption.current",
"isEnabled": true,
"isReady": true,
"properties": {
"value": {
"type": "number",
"value": 0,
"unit": "kilowatt"
},
"status": {
"type": "string",
"value": "connected"
}
}
}
For current heat production:
{
"feature": "heating.heat.production.current",
"isEnabled": true,
"isReady": true,
"properties": {
"value": {
"type": "number",
"value": 0,
"unit": "kilowatt"
},
"status": {
"type": "string",
"value": "connected"
}
}
}
The example values above were captured while the compressor was idle, therefore 0 kW is expected.
Environment
Home Assistant Core: 2026.9.0
Integration: Viessmann ViCare
Device: Viessmann Vitocal 252-A
Product family: VC252
Viessmann IoT API: v2
On this Vitocal 252-A the relevant features are available at system level:
heating.power.consumption.current
heating.heat.production.current
The existing inverter power value is exposed separately by the API and represents a different data point.
I can provide an anonymized feature dump and test a proposed fix if needed.
Use cases
Having both values available as entities would also make it possible to calculate a momentary COP:
This is different from the existing seasonal performance factor, which represents efficiency over an accumulated period rather than the current operating point.
Anything else?
No response
All reactions