EEBus support / Local Vitoconnect access

[idstein]

As Viessmann has committed also to EEBus and started with new product such as GridBox into the ESS space it would be really create to have a local solution to interact with the VitoConnect.

You can enable the EEBus communication in your local Vitoconnect by going to http://vitoconnect.local/cgi-bin/eebus.cgi and login with user admin. The password is the WPA2 number on your sticker, e.g. 12345678.

According to my quick research communication is based on a discovery/registration protocol similar to bonjour called SHIP and SPHINE. As the entire EEBus initiate is a German thing we will not see broad international development support to get local communication.

If my time allows it I will do further research into protocols and try to prototype. Viessmann Cloud is sort of unreliable for me and I would like to have local internet independent access to my home automatisation (including solar energy mgmt and direct heat pump control).

[adorobis]

Which vitoconnect device is needed? It does not work with mine - can't open that page. I have the Vitoconnect 100 OPTO1.

[idstein]

It is a VitoConnect Opto 2 running firmware version 2.47.0.0.

[adorobis]

Could you please share where you have found the information about the EEBus being enabled on vitoconnect devices? Or how could I validate if the OPTO1 version should support that?

[idstein]

My local network security scanner noticed that the VitoConnect is listening on port 80. Hence, I did a bit of research and stumbled across the following related to Gridbox:

https://www.viessmann-community.com/t5/Konnektivitaet/Vitoconnect-Gridbox/td-p/174644

It could be that VitoConnect Opto1 is not supported for this.

[adorobis]

Many thanks, so it looks like the OPTO2 version is needed. Will consider the upgrade (150 USD) if there is good progress with integrating the EEBUs with HA :)

[idstein]

Using EVCC EEBus implementation I could not establish a simple EEBus communication. It looks like discovery works (spine) but the correct connection / association fails.

I'm no investigating how the official EEBUS Viessman product "GridBox 2.0" is establishing its local connection to VitoConnect Opto2.

It looks like the GridBox 2.0 is actually produced by gridX and is simply a Raspberry Pi Compute Module 3 B+ system. So a rather open system.

At least from the developer APIs it looks like we can register a GridBox 2.0 and go via gridX APIs to retrieve its measurement points. (So one needs to grab some IDs via web development tools when interacting with Viessmann Servers).
https://developer.gridx.ai/docs

It looks like Viessmann is not only selling you a GridBox for that sort of money, but all along a lot goes to third party developer gridX and its servers. Your data is stored on GridX Cloud and Viessmann never mentioned GridX in its data privacy policies.

After successful pairing with a GridBox one can see the following data points via the (not EEBus web socket):

ws://admin:<WPA2_PW>@vitoconnect.local/ws

SgReady: NotActive
SgReadyFunc: Inactive
SgPossible: WarmWater=yes BufferCylinder=yes Heating=yes Cooling=yes CoolingBuffer=yes 
SgWarmWaterSetpoint: 0
SgHeatingBufferSetpoint: 0
SgHeatingSetpoint: 0
ElectrPowerHeatpump1: 0
ElectrPowerHeatpump2: 0
RelaisStatusElectrHeatingLevel1: 0 (00000000)
RelaisStatusElectrHeatingLevel2: 0 (00000000)
StatusStateMachineHeatpump1: kOff
StatusStateMachineHeatpump2: kOff
CalculatedTotalPowerConsumption[W]: 0
CalculatedTotalEnergyConsumption[Wh]: 49800

Minor update: Gridx Gridbox internally uses an EEBus implementation from Keo GmbH which seems to be free if you are a customer of Keo Gmbh, but otherwise closed source.

[zoogian]

Interesting to be able to get local access, have a OPT2.