Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Certain data no longer available via API #359

Open
firewiremb opened this issue Feb 4, 2024 · 7 comments
Open

Certain data no longer available via API #359

firewiremb opened this issue Feb 4, 2024 · 7 comments

Comments

@firewiremb
Copy link

I have been using PyViCare for a long time. Until recently I used version 2.28.1. Since I noticed that the error PyViCareNotSupportedFeatureError('getHoursLoadClass1') was occurring in my log files, I carried out an update. I suspected that the API had changed and this might be fixed with a newer version.

After the update to version 2.32.0, not a single feature of the API was available anymore.

I was able to find out that version 2.31.0 is the last version that works for my circumstances. (The PyViCareNotSupportedFeatureError('getHoursLoadClass1') still occurs with this version.)

See also files in the appendix.

dump.2.28.1.JSON
dump.2.31.0.JSON
dump.2.32.0.JSON

@CFenner
Copy link
Member

CFenner commented Feb 4, 2024

I guess you have a Opto1 connected? Viessmann changed their api that the gateway is the first device to return in the list. Also with v32 the opto1 is handled as a gateway class and not as a hearing device. Make sure you access your heating device instead.

@firewiremb
Copy link
Author

Thank you for your quick reply.
Yes, I have connected a Vitoconnect 100 OPTO1 to my heat pump.

I changed:

device = vicare.devices[0]

to

device = vicare.devices[1]

This solved my Problem using v32.

The PyViCareNotSupportedFeatureError('getHoursLoadClass1') however still occurs.
The last day this feature was available and providing data according to my log files was October 9, 2023.
Has this feature been disabled within the Viessmann API or is something wrong with my code?

@woehrl01
Copy link
Collaborator

woehrl01 commented Feb 4, 2024

@firewiremb yes, it's likely that viessmann disabled that data for your device. It could be that it moved to the paid tier (no guarantees).

@woehrl01
Copy link
Collaborator

woehrl01 commented Feb 5, 2024

Out of curiosity, it could be that the values have just moved. Do those numbers fit your previous ones? @firewiremb

Bildschirmfoto 2024-02-05 um 09 02 03

@firewiremb
Copy link
Author

Thank you for inquiring again. No, unfortunately these are not the values I miss.
I found an older dump.json file that I created when the feature was still active. The values I'm missing are hoursLoadClassOne, ...Two, ...Three, ... and so on.

grafik
dump.json

@CFenner
Copy link
Member

CFenner commented Feb 5, 2024

I suggest that you ask in the Viessmann community about the data point. The support may tell if they moved something.

@firewiremb
Copy link
Author

firewiremb commented Feb 22, 2024

@firewiremb firewiremb reopened this Feb 22, 2024
@firewiremb firewiremb changed the title Version 2.32.0 no longer works for my use case Certain data no longer available via API. Feb 22, 2024
@firewiremb firewiremb changed the title Certain data no longer available via API. Certain data no longer available via API Feb 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants