Skip to content

chore(testdata): Update Vitocal 250A data - #418

Merged
CFenner merged 4 commits into
masterfrom
CFenner-patch-1
Oct 3, 2024
Merged

chore(testdata): Update Vitocal 250A data#418
CFenner merged 4 commits into
masterfrom
CFenner-patch-1

Conversation

@CFenner

@CFenner CFenner commented Oct 2, 2024

Copy link
Copy Markdown
Member

with advanced api plan

@CFenner
CFenner marked this pull request as ready for review October 3, 2024 05:42
@CFenner
CFenner merged commit 9350ad3 into master Oct 3, 2024
@CFenner
CFenner deleted the CFenner-patch-1 branch October 3, 2024 05:42
@stho

stho commented Jan 17, 2025

Copy link
Copy Markdown

Hi @CFenner,

does that mean that I need the advanced api plan to get data about power consumption?

            'heating.compressors.0.power.consumption.current',
            'heating.compressors.0.power.consumption.dhw',
            'heating.compressors.0.power.consumption.heating',
            'heating.compressors.0.power.consumption.total',

I have issues to get this information in the homeassistant integration for vicare.

@CFenner

CFenner commented Jan 17, 2025

Copy link
Copy Markdown
Member Author

@stho you can find the tier level of the data points here: https://documentation.viessmann.com/static/iot/data-points

@CFenner

CFenner commented Jan 17, 2025

Copy link
Copy Markdown
Member Author

Please note that consumption data is somehow broken in the Viessmann API. It stops working every night for some users.

@stho

stho commented Jan 17, 2025

Copy link
Copy Markdown

Ok, so I should be able to receive the consumption data. They are available in the basic tier.

Yeah, read the homeassistant issue on that, but wondered if there can be some issues on my end.

@CFenner

CFenner commented Jan 17, 2025

Copy link
Copy Markdown
Member Author

I have legacy devices (VitoConnect, non-E3) and these do not provide consumption data.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants