Hi Kenny,
Over the weekend, I had this event happening.
Any idea what could be the trigger for this to happen?
I am currently on version 0.3.3 and a restart solved the issue.
In the official Vicare app from Viessmann, there was no alarm shown.
Hi Kenny,
Great work again, I see it getting better and better, nice man. Something is wrong with the compressor data for me. Looks like an invalid date issue.
Maybe for your roadmap, the temperatures of the boiler would also be a nice addition. I think I have 3 values, bottom, top and main
Hello, same issue.
Could you guys elaborate on that? Maybe a screen shot?
but of course, below screenshot. when item clicked you normally get the time in sec/hours/days of the last update. now the message of not valid date.
Yeah, I am also attaching screen where is visible that it shows that circulation pump runs for 2 days already which is not possible I guess. Also would it be possible to have there current temperature of hot water in boiler? It is quite weird that it seems to be impossible to add there power consumption, because original Viessmann app shows quite nice graphics where consumption is visible and even divided in to Hot water and heating.
Hello guys,
I’ve pushed a new version (v0.6.0) which should fix the compressor statistics, and add more statistics in general. This version is now also published in the app store as a stable version, since I want to get as much as people people to use it and I do believe that we can now easily support all Vitodens and Vitocal devices, with the generic device support and the new authentication logic.
Related to the power consumption for VItocal devices, until now I cannot find it inside your features.json file, which indicates me that Viessmann hides it after some paying plan.
If anyone has another VIessmann device he likes to add, please feel free to reach out: I want to expand where possible !
Kind regards,
2 Likes
hi Kenny,
I still have no data on a few properties. always invalid date issue or so it seems. Below is a representation of this.
Exactly same issue and data not available.
Hey guys,
There was a typo in the compressor value name, I fixed that one in v0.6.1. This version is now published to test, and submitted for final approval too.
It can be that some metrics don’t appear on your side, some metrics are unavailable for certain devices. I’ll look if I can hide them in that case.
Kind regards,
2 Likes
Compressor stats are working 
yep, the compressor stats working now, only boiler temp (bottom and main) not working (invalid date). The boiler temp top works!
Hi Kenny,
Great work!
Authentication works perfectly now. However I seem to have problems connecting to a Vitodens 300 through the generic Vitodens.
I am getting “null - circuit 0” as a new device. When I choose this new device, all possible device data is empty.
When looking into both “installations.json” and “features.json” everything needed appears to be present.
BTW: the Vitodens 300 works perfectly in HA since years and is also imported via the Home Assistant Community app into my Homey Pro 2023. Works perfectly from within Homey with all whistle and bells present. Could there be some “interference” between both implementations (both present simultaneously in Homey)? I suspect not. Besides of course the usage of API calls.
The goal is to get rid of the HA version in Homey when I get your solution working 
Could you provide me the installations.json / features.json? You can send them by email (see PM), I can have a look then.
Yes, you cannot use both integrations (Homey & HA) at the same time. Or you can, but only 1.450 calls per day are allowed.
See post above.
Yes, thanks Jan. I am aware of the API calls limitation. Not quite there on total calls for today though.
I will only use one instance in the future 
The HA Viessmann integration was the only reason I am using the Home Assistance Community app (besides the very good dashboarding with many years of HA data in Influx + Grafana). And yes, I am one of those who used HA for many years and converted to Homey 
Yeah, exactly this.
Thanks a lot Kenny for looking into this. I will send both files later today.
Kind regards,
How did you manage to minimize the calls?
Good work!
Thank you for 0.6.1!
Maybe, somewhere down the road, an [%] symbol can be added to the burner modulation?
There is something off with the names of these variables. I guess the left one is for DHW?
Maybe the eco-symbol could be replaced to better represent the function? Today, both symbols are the same.
