-
Notifications
You must be signed in to change notification settings - Fork 37
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
Some features broken (?) #73
Comments
Hi soeffi, same issue here. I see that Viessmann does not provide the data for the feature e.g. for burners. So there is no issue on the part of this API. I do not know if it will only be for a short time. In the API Documentation from Viessmann are no further information. |
same for me. One way to fix that would be to find the right feature name by sniffing network from viCare to viessmann's server. I only succeed this by using android sdk emulator+ mitmproxy which takes me a bit of effort. Didn't succeed with vpn traffic sniffer such ash Packet Capture. |
there is a bug in the feature construction for statistics. should be heating.burners.0.statistics not heating.burners.0.heating.burners. W |
I have fixed the problem with statistics. Will check for burner active. |
BTW One easy way to get all the feature available is to disable caching in the boostrap-dev.php and use:
|
burner is now under feature heating.burners.0 did a fix for this. |
For my part issue is closed. Feel free to reopen if not |
Same here. Works with the latest 2.1.1 snapshot. Thanks a lot for the quick response! |
Hi all,
since today morning I'm getting some errors in my scripts, related to burner information. I see:
Unable to get data for feature heating.burner from isHeatingBurnerActive()
Unable to get data for feature heating.burners.0.heating.burners from getHeatingBurnerStatistics()
Yet another API change? I'm using the latest (2.1.1) snapshot. Anyone else with the same issue?
Thanks!
The text was updated successfully, but these errors were encountered: