Viessmann published advice to change the endpoint

[JueBag]

Bonjour,

I guess you (@thetrueavatar ) have also recieved to mail from Viessmann.

Are you going to implement to adviced change for the new endpoint?

Tried to do the needed change (changing from v1 to v2 in 2 files), however when trying to create a .phar I got only errors.

[thetrueavatar]

No I won't. The main reason of my project was to provide an easy client to consume data provided through the private API behind vicare. Since this api was not designed for home automation but for smartphone app navigation I have implemented such a client base on my reverse engineering of the ViCare service api. Calling it an API as a mistake I have done, It's really just a client. With an official API that is designed for home-automation I hope they will provide an official API contract. OpenAPI is the standard to define in yaml those kind of contract. With this kind of file, client can be generate easealy with a lot of tools without the need to write custom code. So my client is obviously no longer of any relevance. Regards Le ven. 19 févr. 2021 à 10:43, Jürgen Baginski <notifications@github.com> a écrit :

…

Bonjour, I guess you ***@***.*** <https://github.com/thetrueavatar> ) have also recieved to mail from Viessmann. Are you going to implement to adviced change for the new endpoint <https://iam.viessmann.com/idp/v2/authorize>? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#54>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEH4GU7AXAWU3YDE64XSJO3S7YXC7ANCNFSM4X4BSX5A> .

[thetrueavatar]

That's for the middle term plan. I will adapt the part for the current vicare api of course. Regards, Le ven. 19 févr. 2021 à 15:13, thetrueavatar <thetrueavatar@gmail.com> a écrit :

…

No I won't. The main reason of my project was to provide an easy client to consume data provided through the private API behind vicare. Since this api was not designed for home automation but for smartphone app navigation I have implemented such a client base on my reverse engineering of the ViCare service api. Calling it an API as a mistake I have done, It's really just a client. With an official API that is designed for home-automation I hope they will provide an official API contract. OpenAPI is the standard to define in yaml those kind of contract. With this kind of file, client can be generate easealy with a lot of tools without the need to write custom code. So my client is obviously no longer of any relevance. Regards Le ven. 19 févr. 2021 à 10:43, Jürgen Baginski ***@***.***> a écrit : > Bonjour, > > I guess you ***@***.*** <https://github.com/thetrueavatar> ) have > also recieved to mail from Viessmann. > > Are you going to implement to adviced change for the new endpoint > <https://iam.viessmann.com/idp/v2/authorize>? > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <#54>, or > unsubscribe > <https://github.com/notifications/unsubscribe-auth/AEH4GU7AXAWU3YDE64XSJO3S7YXC7ANCNFSM4X4BSX5A> > . >

[JueBag]

Thanks!
Don't know why I failed creating the .phar by myself!

[thetrueavatar]

For information, I have updated the develop branch(1.4.0-SNAPSHOT) to use the v2 of the service. For the 2 provided url, currently it doesn't work(permission denied). I suspect this is a part of the new api(iot is in the url...) and so the client_id-secret from ViCare has more than likely no grant for this. I'm waiting to get my access to test this. Regards, Le ven. 19 févr. 2021 à 15:22, Jürgen Baginski <notifications@github.com> a écrit :

…

Thanks! Don't know why I failed creating the .phar by myself! — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#54 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEH4GU6WXU2AH6PM5WDQSOLS7ZXZ3ANCNFSM4X4BSX5A> .

[JueBag]

For the 2 provided url, currently it doesn't work(permission denied).

So, the manner of publishing anything by Viessmann hasn't changed. Big announcements, always late, errors are common....

[thetrueavatar]

Switch done to new endpoint

[JueBag]

Merci Beacoup.
Is it also working now (from the Viessmann side?) or is only your code part done?

[Edit:] It's working here!

[thetrueavatar]

After some more testing it's working when I'm doing it manually. So this is related to with the way I manage to do the call in my code. Regards Le sam. 20 févr. 2021 à 11:37, Jürgen Baginski <notifications@github.com> a écrit :

…

For the 2 provided url, currently it doesn't work(permission denied). So, the manner of publishing anything by Viessmann hasn't changed. Big announcements, always late, errors are common.... — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#54 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEH4GU5KMR6VQOYCRE4RV7LS76GG7ANCNFSM4X4BSX5A> .

[JueBag]

I had no problem running the calls with the new .phar ( the only thing to remember was changing the the bootstrap.php to the new name).