The information is not very clear on their website, I’ve found description of the Vitoconnect OT2 interface, in Polish it says:
“Vitoconnect OT2 is compatible with all new Viessmann heaters with an OpenTherm interface manufactured after October 2017 and additionally in the following models: ● Vitodens 1xx W (WB1B, WB1C, B1HA, B1KA, B1LA, B1LB, B1HC, B1KC, B1LD ) ● Vitodens 050-W (BPJC, BPJD)”
But on English site it says:
“Vitoconnect OT2 is for the remote control of the Vitodens 100 range of boilers using the ViCare App on your smart phone or mobile device.
The following types of boilers are supported:
Vitodens 050-W (BPJC, BPJD)
Vitodens 100-W (WB1B, WB1C, B1HA, B1KA, B1HC, B1KC)
Vitodens 111-W (B1LA, B1LB, B1LD)”
Is there somewhere a specification of which boiler has an OpenTherm interface?
Hi,
I have a Vitocal heatpump and the integration is working like a charm 
Are there any attributes to read out the current compressor capacity and the current power consumption?
in Developer tools / states, entity column : filter on vicare This should display all exposed sensors.
Hi Tommmii,
I already checked this. Unfortunately the compressor capacity is not included 
When trying to change to “Comfort” mode I get an error, same with Eco mode:
2021-12-23 11:42:41 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140344949958688] (PyViCareCommandError(...), 'Command failed with status code 502. Reason given was: COMMAND_NOT_FOUND') Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 185, in handle_call_service await hass.services.async_call( File "/usr/src/homeassistant/homeassistant/core.py", line 1495, in async_call task.result() File "/usr/src/homeassistant/homeassistant/core.py", line 1530, in _execute_service await handler.job.target(service_call) File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 209, in handle_service await self.hass.helpers.service.entity_service_call( File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 663, in entity_service_call future.result() # pop exception if have File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 896, in async_request_call await coro File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 700, in _handle_entity_call await result File "/usr/src/homeassistant/homeassistant/components/climate/__init__.py", line 486, in async_set_preset_mode await self.hass.async_add_executor_job(self.set_preset_mode, preset_mode) File "/usr/local/lib/python3.9/concurrent/futures/thread.py", line 52, in run result = self.fn(*self.args, **self.kwargs) File "/usr/src/homeassistant/homeassistant/components/vicare/climate.py", line 330, in set_preset_mode self._circuit.deactivateProgram(self._current_program) File "/usr/local/lib/python3.9/site-packages/PyViCare/PyViCareDevice.py", line 399, in deactivateProgram return self.service.setProperty(f"heating.circuits.{self.circuit}.operating.programs.{program}", "deactivate", {}) File "/usr/local/lib/python3.9/site-packages/PyViCare/PyViCareCachedService.py", line 29, in setProperty response = super().setProperty(property_name, action, data) File "/usr/local/lib/python3.9/site-packages/PyViCare/PyViCareService.py", line 52, in setProperty return self.oauth_manager.post(url, post_data) File "/usr/local/lib/python3.9/site-packages/PyViCare/PyViCareAbstractOAuthManager.py", line 91, in post self.__handle_command_error(response) File "/usr/local/lib/python3.9/site-packages/PyViCare/PyViCareAbstractOAuthManager.py", line 67, in __handle_command_error raise PyViCareCommandError(response) PyViCare.PyViCareUtils.PyViCareCommandError: (PyViCareCommandError(...), 'Command failed with status code 502. Reason given was: COMMAND_NOT_FOUND')
Home Assistant 2021.12.4 in docker
Vitodens 222-W boiler.
For some boilers it is not possible to set Eco and Comfort modes via the API. Can you do it via the mobile app?
yes… works fin in the app… And the integration also picks it up after some seconds.
Hi there, nice job on the integration and the transition to UI setup with respect to the existing configuration.
Is there an intention to read the solar production, not a PV?
ideally I would like to see this production additionally in the energy management. I think solar (not PV) is missing there at all.
Cheers
erm… Translation Error , thankfully the integration functions as before.
Where and when exactly did you see this? Wikipedia? Website of NASA?
It’s written right in the screenshot. Since you ask so nicely and without snark, I’ll spell it out for you :
“Set up ViCare Integration.”
Thanks. Now I have a chance to try to reproduce without prior meditation about context.
Api is down? Integration stopped working for me.
Nope. Working for me.
I also had a short downtime today after a restart of HA. About 30 minutes later another restart brought the connection back up again.
After restart my integration started working.
Thanks for sharing details. Good reading in this thread.
Same impression here. I am adding more and more functionality to our home and I am just getting issues how to get their products to one common system like home assistant. Having dozen of clouds and apps is nightmare. If I purchase another system to my automation, I will definitely prefer the one without any cloud and having support for hass or at least possibility to get their integration in.
IMHO the current strategy of Viessmann is a rather faint hearted approach towards the future. Thinking publicly of charging for their cloud API without opening a cost free non-cloud option will definitely not convince any smart home users. We need to integrate a dozen suppliers in our homes. I gladly pay €5 a month to Nabu Casa for helping me with this integration nightmare on the top level. But I will not pay to each system supplier in my home. Not to a single one off them actually. Sorry.
they should provide both options. there are users who use cloud and are happy to pay, others want to stay away for exposing their devices and rather use them only locally (I prefer staying local).
I have locally vitotrol at the moment and considering updating to vicare but I’ll wait and see how this goes.
I have the Vicare app connected through Vitoconnect to my Vitocal 222 heat pump. And the only way to get it connected to HA is through the Viessmann cloud.
Additionally I have a Vitovent ventilation system with an LB1 controller in my living room. This system is currently not connected to anything. Not to Vicare, not to HA. I could in fact also connect it to Vitocal through an additional Modbus connection. But Vitovent can only be connected to one controller. So it is either LB1 or Vitocal+Vicare. I would loose my LB1 interface in the living room and control would only be possible either through Vicare & HA or through the Vitocal control panel down in my cellar. This is not what I want.
This whole Viessmann strategy is all closed up and rather convoluted. What would really help us HA users would be a documentation of Viessmann’s Modbus data endpoints. This would open up all options to bridge to HA. But Viessmann actively refuses to disclose this documentation.
Hi,
I see the same error.
Its when HA disovered my Viessmann Gas Boiler, then i tried to supply all data, got all api keys and so on, and after clicking submit - The intl string context variable “name” was not provided to the string “{name}” and thats it. Cant register my Viessman device