Endpoint missing and writing method not quiet clear

[thetrueavatar]

Hello,

I have jumped my former client into the niew API. 

However, I have noticed that some endpoint are still missing. For instance, I wanted to get my slope and shift but didn't find the 

heating.curve

features.

Moreover, it's not quite clear on how to set data(program, mode, ....) in the documentation. Maybe that it's still the same format as the ViCare one but it's not clearly explained imo.

Regards 

[MichaelHanna]

Hi @thetrueavatar ,

I'm happy to hear you are working on integrating the new API!

The heating curve feature is currently not available via the basic version of the API. But similar to the other threads about "missing" data points compared to the old / unauthorized client, we are happy to receive your feedback and are currently working on a solution to support you on your requests. I hope you and the other developers / API enthusiasts can have a bit more patience.

Concerning setting data for e.g. programs or modes, there shouldn't be any changes. Please try it out in the way you are used to and let me know if there are any problems.

Best,

Michael

[thetrueavatar]

Hello, thank your for your explanation.

By the way we did receive a warning email from Viessmann about old api key being shutting down.

It's not clear to me what it does implies. Does it means, we won't be able to use the old api behind ViCare or just that we will have to use our own key to accès to the former appi ?

Regards

[MichaelHanna]

@thetrueavatar your second assumption is correct. The API key you are currently using within your pugin will be disabled. So every user will need their own personal key, which can be obtained via the Developer Portal.

I assume there is a difference in the authentication compared to the old key. The authentication is described here: https://developer.viessmann.com/en/doc/authentication. However, the API itself is still the same as before, except for current availability of certain feature, as explained before.

Let me know if you have further questions!

Best,

Michael

[thetrueavatar]

Hello,

I have switched my code to use the developper authentication method to get the code and try to access to the old api with my own key. However, this doesn't seems to work and I receive an error:

{"viErrorId":"req-440132bd2f744883b70b91106fedd11f","statusCode":404,"errorType":"RESOURCE_NOT_FOUND","message":"Required resource was not found","extendedPayload":{}}

The error message is quite confusing(maybe for security reason) since the resource https://api.viessmann.com/general-management/installations works while using the old authentication process.

My guess is that I didn't receive the required grant for the former api with the new token process.

I have tried to use the old authentication method with my own api key. I'm able to get the authorization token but failed to get the authenticationToken from the https://iam.viessmann.com/idp/v2/token which respond with:

{"error":"invalid-token-request"}

It looks like the authentication token requires a consumer secret which I don't have.

To sum up things:

1. Using the authentication process from https://developer.viessmann.com/en/doc/authentication grant me a token but which doesn't have access to the old api

2. Using the undocumented Vicare authentication process isn't working with my own api key from the dev portal

I guess this makes sense since the api behind ViCare has never been ment to support third party application except ViCare itself.

Regards

[MichaelHanna]

Hello,

could you share an example of what you are trying to call using the token obtained by your own key (for which you are receiving an error)?

In general, if you want to for example request the features of your device with your own key, this should work using the call

curl -X GET https://api.viessmann.com/iot/v1/equipment/installations/{{installationId}}/gateways/{{gatewaySerial...

Best,

Michael

[thetrueavatar]

Hello,

The url your a providing me is the IOT url. I was talking about the api behind ViCare which is https://api.viessmann.com/general-management/installations

[MichaelHanna]

Hi,

the URL you are referring to is deprecated. For getting information on your installation, please use the URL 

https://api.viessmann.com/iot/v1/equipment/installations

We refer to this endpoint within the overview for the IoT section: https://developer.viessmann.com/en/doc/iot/overview

This endpoint should provide you with all relevant information on your installation, especially the installation ID. You can also optionally add the query parameter ?includeGateways=true, to receive information about the gateway and device within the same call.

[thetrueavatar]

Ok so the old api key problem is only for the iot api ?

If so then it's fine and I will keep the old implementation as it is and continue to migrate the new version to iot.

[MichaelHanna]

Hi @thetrueavatar,

referring to your initial post in this thread, we recently added some features that were missing to the basic version of the API. The information we just shared on the Change Log within the Documentation: https://developer.viessmann.com/de/doc/changelog

This is especially to provide you with a smooth transition switching from the old API client to the Developer Portal with your own personal API keys.

Best,

Michael