Hi!
Recently stopped receiving data from the container. The container logs show login attempts with no result or error code. Apparently, the API address has changed. Or is this just me?
1 Like
Hi. It is not only you. I have the same problem since the same time. I hope someone has an idea to fix it.
Same here. Vitotrol app still working so it has to be API adress?
fixed, the API url changed to Vitotrol Interface Web Service. Don’t forget to use the updated Dockerfile and rebuild using docker-compose build --no-cache
3 Likes
Respect, you’re the best
Really great work. Thank you very much for your fast fix 
is it possible to get this working with a vitocal 161-a? the device appears to be sending mqtt messages but I can’t get it to appear in my viessmann developer portal
Hey, I’m afraid I don’t really understand your question. What do you mean with the “my viessmann developer portal”? The Vitotrol2MQTT tool connects to the vitotrol app. Does the Vitocal 161-a use this? Then it should theoretically work. Any specifics you’re struggling with?
for those who are still using this, checkout GitHub - benvanmierloo/ha-vitotrol: Home Assistant integration for Viessmann Vitotrol heating systems
It should be a lot easier to setup, but its a complete rewrite, so might contain bugs. Feedback welcome!
That sounds very good. If I find some time the next days I will be glad to test it.
I think I should deactivate the Docker Version first?
Do you have an idea to use the same sensors than my Docker Version does? It would be nice not to loose my statistic data.
Thank you for your great work to those old Viessmann heating systems.
No need to deactivate the Docker version first. I’m running them side by side with no issues so far.
As for the same sensors, that will be difficult. It’s a completely different integration with different unique identifiers, so HA treats them as entirely separate entities. Statistics won’t carry over automatically.
There might be a workaround (untested) that might preserve long-term statistics (no guarantees, results seem inconsistent based on community reports):
- Note down your current MQTT entity IDs
- Delete (not just disable) the old MQTT entities from the entity registry
- Set up the native integration
- Rename the new entity IDs to match the old ones
The idea is that the orphaned statistics in the database (keyed by entity_id) should become accessible to the renamed entity. Looking at Rename entity ids and retain statistics it’s going to be tricky, so back up your database first. If I find a more reliable solution, I’ll definitely let you know.
When testing the integration, could you look at how many entities your Viessmann system creates? I only have 1 Viessmann system, and all the entities from my system are now “known attributes”. Unknown attributes will be autodiscovered, but will get their original name (like info_waermemenge_fcu_r-0x2639 or something) and the integration guesses
the type of sensor it should become. (You can rename the entities, but the type of sensor is fixed).
My goal would be to create a complete list of all possible attributes, so we have control on the type of sensor, class, unit, …
There is a small discovery script available in the repository to get all possible attributes from your system:
pip install -r scripts/requirements.txt
python scripts/discover.py --user YOUR_EMAIL --password YOUR_PASSWORD --values
If you have many unknown attributes, would you be willing to share the output of this script?
Thanks!
I have installed the Integration now and what should I say? WOW. Very easy to install and 79 entitys. Realy great. I have unknown attributes but I am not good enough with IT to use your script. In the docker Version I had done this command: docker-compose exec vitotrol /vitotrol --login XXX --password XXX rget all. Bring this the same result than the script? I can send you the result from the Terminal Command.
there is a discovery script in the new repository, which you can use
pip install -r scripts/requirements.txt
python scripts/discover.py --user YOUR_EMAIL --password YOUR_PASSWORD --values --json > dump.json
Where do I have to paste your script in? In the Terminal direct in HA?
oh my bad, didnt read properly. Its a script you run on the commandline somewhere where you have python installed. Probably wont work in the terminal in HA.
But running the old command is also usefull
docker-compose exec vitotrol /vitotrol --login XXX --password XXX rget all
You can DM me the output if you want. That was i can extend the “known attributes” in the integration. Makes life better for everyone 