-
Notifications
You must be signed in to change notification settings - Fork 92
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
Comments
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. |
Thank you for your quick reply. I changed:
to
This solved my Problem using v32. The |
@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). |
Out of curiosity, it could be that the values have just moved. Do those numbers fit your previous ones? @firewiremb ![]() |
Thank you for inquiring again. No, unfortunately these are not the values I miss. |
I suggest that you ask in the Viessmann community about the data point. The support may tell if they moved something. |
I made a request in the Viessmann community: |
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
The text was updated successfully, but these errors were encountered: