-
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
for information, futures not working in new api for my OPT1 (Vitoconnect 100) but before working fine #64
Comments
I am very busy at the moment. Some fuetures are no longer available in the new API. I'll try to find the possible bug in the next few days. |
I understand that these functions are less necessary than the basic ones. I wrote for information. If you add them one day, it will simply be easier to integrate with Fibaro, for example |
|
Since ViCare is using the IOT Api, if an information is available in ViCare it should be available then with the IOT API. |
I should take some time to check how the feature are now reorgarnized and clean a bit the way I'm working. For the cache, I'm get the data from the https://api.viessmann.com/iot/v1/equipment/installations/{installationId}/gateways/{gatewaySerial}/devices/{deviceId}/features/ Documentation is not quiete clear atm. Plese note that viessmann has added some features accodring to their changelog https://developer.viessmann.com/en/doc/changelog
|
I use the hot water setpoint in my setup. Since yesterday, the feature getDhwTemperature() (=heating.dhw.temperature) is no longer available. After comparing the complete rawjsondata, I noticed that the feature with the required value is heating.dhw.temperature.main. But this feature is not available in the script or am I wrong? |
Hello, could you please create a specific issue for this one. This will help me to manage issue. I'm already looking at it. |
Not work yet :( |
In the API documentation are two features provided. But I don't know if it is the same. Please try this:
If it works on your installation, we have to do some tests and then we can fix it. |
Ok,, its work via "heating.operating.programs.holiday" |
Thx for this function, I start read new API doc... |
I have updated the code so that $viessmannApi->getScheduledHolidayProgram() is using the right feature |
The text was updated successfully, but these errors were encountered: