Has anyone had any experience with this? I understand that you can’t use it as an Opportunity Load just yet. That’s supposed to be coming in one of the next versions.
But even just the integration and visualisation via EEBUS would be a great feature.
Good to hear establishing connection between the two devices worked as expected.
In terms of the data available, we do support energy counters, but I believe in your case the heat pump is not reporting that data.
At the moment it seems like your heat pump is only reporting power consumption, but not the energy consumed counter.
When your heat pump is running, have you seen power readings above 0W?
Let me know if you still believe that something is wrong and we can dig deeper into your installation.
I’m getting the LWP to heat some water now. It’s currently drawing 2 kW. I can’t see anything in the EEBUS Heat Pump device, the Remote Console, or DBUS.
It seems to me that both devices recognise each other as trusted, but no data is coming from Vaillant.
On my system, the EEBUS integration with my NIBE VVM S325 is already working and I can see the heat pump in Remote Console V2 under AC Loads.
When the heat pump is running, Remote Console V2 shows its actual power consumption. When the compressor is not running, it normally shows only around 39 W standby consumption. I have also seen the heat pump consumption go above 2 kW while it is operating.
In VRM, the integration also appears to be working with Dynamic ESS. I can see a separate heat forecast (Värmeprognos) in the consumption forecast, so VRM is already including the expected heat-pump demand in its planning.
The only thing I do not currently see is accumulated energy in kWh for the NIBE device itself in Remote Console V2 — only the instantaneous power in watts.
So from my experience, the EEBUS integration and visualization are already quite useful, especially because Dynamic ESS can take the heat-pump forecast into account when planning battery operation and grid import/export.
The issue has been identified, some older Vaillant heat pumps do not report their power consumption in the expected way.
We will add support for those older models in a future release.
However, be aware that those older models won’t support all the features (e.g power limiting).
Hi Nils, I tested this on a Cerbo GX running Venus OS 3.85 with a Vaillant aroTHERM split (VWL 125/5 AS outdoor unit, VWL 127/5 IS indoor unit), a multiMATIC VRC 700 controller and a VR 920 gateway running firmware 357.40.40.
I can confirm that the GX receives live compressor power over EEBUS. During a normal heating cycle, heatpump/99/Compressor/Ac/Power went from 35 W to 73 W, then to 1,845 W. I confirmed on the Vaillant side that the compressor was running. The GX reported 1,845 W in six consecutive readings over 42 seconds.
The Vaillant device page in Remote Console shows 0 W under AC Totals. In the GX diagnostics, /Ac/Power shows --. The EEBUS use case listed for this device is /HeatPumpAppliance_3/Compressor_1/MA_MPC. In VRM Advanced, the custom widget device selector does not list this heat pump, and I couldn’t find a measured compressor power parameter under System.
Is there a supported way to display /Compressor/Ac/Power on the existing Vaillant device page and graph it in VRM Advanced? If this needs a change, a separate Compressor power (W) reading would be ideal. That label would make clear exactly what the gateway measures. I’m happy to test it on this setup.
I’ve sent you a private message.
It appears to be the exact same issue mentioned in this thread.
We can install the version with the fix to confirm.
No, but the fix will make the reported compressor power as if it was the overall heat pump power.
At this point the compressor power is not planned to be displayed.
It is for an upcoming feature to make use of the compressor flexibility with Opportunity Loads.