[App][Pro] Viessmann App for Homey Pro

0.2.3 did the trick.
When installing the 0.2.0 from the official store, the error already disappeared.

thank you, 0.2.3 is running just fine.
I will test the functionality over the next days.

A first remark: Is it possible to make the “Comfortmodus” and “Spaarwerking” (Eco mode) into a toggle switch? When using these in flows, one always has to activate one of them AND deactivate the other. This makes two cards. A toggle switch could cover this and avoid conflicts where both are activated.


Conflicting setting originating in Homey:

Hey,

It serms the saving of the settings fails in this case. I am going to dig deeper in the authentication and attempt to improve it later on.

Do you get the saved message when trying to save the settings? Or does a message Come up there with an error?

Kind regards,

Thanks for wending the files, I will try to integrate your device during the next days.

Could you be so kind to share a photo of Your device to me too? Without images I will be u able to add it to homey.

Good idea! I will dig into it.

Great with a Viessmann app!!

When I try do add my Client ID and login credentials I get “Error: fetch is not defined” and “Error: The Viessmann API ClientID was not specified. You should provide one in the settings of the app.

I had a client from before but I deleted it and created a new one. Any ideas?
I use 0.2.0.

Hello all,

Those who have issues with the settings, could you try if the same error appears with v0.2.4, it is published as test version:

Thanks!

Hello all,

I noticed there were several crashes of the app with the missing of the sensor of the room temperature. I added a quick fix for this, not perfect, because i want to understand why it happens.

Therefore, if you notice your actual room temperature is -1 °C, be sure to submit your features.json towards me, this can be by PM or email (which I will supply by PM then).

Thanks!

When I save I get the fetch error. I just read sombody else had the same issue. But I van der my devices but on adding the error about client id is missing.


Hey Marijn,

If you don’t see the “Saved!” message, but get a fetch error, the credentials won’t be saved, and it is normal that you get the error about the client ID missing.

So we should dig first deeper into the fetch error. Could you show me more about that? In the developers tools I have one exception trace related to fetch, but unsure if this is what you are experiencing.

Hi Kenny,

Normally is that not a problem. The next days I’m not able to do. Next weekend is for my the only option.

Hi, I have tried the 0.2.4 version and the same issues appears. “Error: fetch is not defined

Hi Kenny,
The installation (version 0.2.4) worked without any problems. The device (Vitodens 222-F) was found without any problems. However, after adding it, the error message “Cannot read properties of undefined (reading ‘value’)” appears.

I have a long password for the Vicare App/site. My password is 27 characters long.

Could you provide me with the features.json / installations.json?
You can retrieve them from the settings and send them to me. I have the impression that in your case something is slightly different from the other Vitodens 2xx devices I have encountered.

Hi Sundlof,

I have the same issue, Kenny needs som extra hulp/detail. I cannot provide this information now, can you do that?

Yes, but I am not sure what you need and how I get it. Please provide some more details and I will do what I can.

Maybe you can provide me a screenshot of the error page also? That might give me some hints already.

Hi Kenny,

I only have my iPhone of iPad now. Bellow the images. When I make mistakes to the client Id or username and password the same error. When I lieve one or more field empty I get a correct error about missing info. Also try to enter from the web app directly from the honey site, but the same error when I use the iOS App.



I can confirm that I have the exact same issue with the same error codes.

Please note that the viessmann API accepts only 1poll/minute/day (1.445 calls/day to be precise).
Therefor, if you have another integration activated , the API will be unresponsive by the end of the day.