Victron integration in Home Assistant

Modifications
, , , ,
1

Hello everyone,

I’m using Home Assistant 17.1 and have added Victron Remote Monitoring as an integration/service.

However, I only see 18 entities, all of them under these categories:

  • Estimated Energy Consumption

  • Estimated Energy Production

  • Highest Consumption Peak

  • Highest Peak Time

I was expecting to access many more entities from my Victron system (battery, inverter/charger, PV, loads, etc.).

Is there a way to expose additional entities from VRM to Home Assistant?
Or do I need to configure something differently (GX device settings, MQTT, modbus, HA integration options, etc.)?

Any guidance would be greatly appreciated!

Thanks in advance.

2

Hi im using this integration from the hacs store

I got over 500 entities with this setup

3

Hi,

I’m using the Victron MQTT Integration. It works flawlessly and you can use the MQTT bridge to reduce network traffic. It delivers in my setup more than 300 entities.

Best

Thomas

4

I’m using modbus; no integrations. All entities I am interested made in the configuration.yaml like this:

There is a victron “modbus TCP register XLXS” file with all register values.

5

Thanks, do you know the names or Adress from this Sensors?

and from this:

image
image2493×306 6.44 KB

image
image2634×307 5.4 KB

6

“aus dem Netz” is not a plain sensor.

In HA can this constructed via reading of energy values from the energy meter (VM3 modbus or grid meter mqtt), put this into a HA “energy meter” and the build your own display parameters, last hour, week, month aso.

“von der Batterie” as the same way. Here read out the battery modbus registers from Battery History or build your own templates with power integrations.

…

But if you use the HA Energy dashboard and fill the right sensors of your integration HA do all the work.

Screenshot_20260320-085515 (1)
Screenshot_20260320-085515 (1)998×498 34.3 KB

For example: mqtt from the grid meter (hitchi reader)

#Tasmota, Energy Meter ZS

    - name: 'Energy Total In'
      unique_id: energy_total_in
      state_class: total_increasing
      unit_of_measurement: 'kWh'
      device_class: energy
      state: >
        {{ states('sensor.1_8_0')  }}
             
    - name: 'Energy Total Out'
      unique_id: energy_total_out
      state_class: total_increasing
      unit_of_measurement: 'kWh'
      device_class: energy
      state: >
        {{ states('sensor.2_8_0')  }}
7

this pr: https://github.com/home-assistant/core/pull/156090 was just merged, so I assume an official victron mqtt integration is comming to the next HA release. This will probably be limited to just a few sensors, given HA’s policy to only add a few things at a time in a new PR, but I expect steady updates the comming releases to this integration as tomer-w has already created a new pr to add an extra HA platform: Add binary_sensor platform to victron_gx integration by tomer-w · Pull Request #167527 · home-assistant/core · GitHub

8

The new built in integration contains all the entities from the custom one other than the reboot Cerbi button which will be added in the next HA version.

9

Victron integration now released into core HA

10

Cool. Thanks for letting us know. I’m not an HA expert at all, so pardon the stupid question that follows. I have installed the MQTT custom integration that I installed via HACS. But now I don’t see it listed as in the HACS section on my HA server/hub. Do I just update the core and OS and that’s it? Thanks!

11

Hey Tomer, isn’t the official non HACS version also missing the ability to use mosqitto and also the ability to specify the update frequency? Or did I miss something?

12

Nevermind. It just worked. Thanks.

13

Just had set-up a new system (inverter, battery and Color GX) and integration into HA is seamless. Just enable MQTT on the display and install the official Victron integration. All 3 devices appeared with many entities. The display device exposed lots of unneeded and unused entities, so I disabled it. Important data is visible on the Inverter and Battery device.

However, update rate is very slow. Up to 5-10 seconds before actual change is visible in HA.

image
image838×926 40.5 KB

14

You could try the integration from HACS the official one is based on: GitHub - tomer-w/ha-victron-mqtt: Home Assistant Victron GX integration based on MQTT · GitHub

According to tomer-w he intends to continue to support this one in parallel - it does have a configurable interval.

15

@OGPS

The official Victron HA Integration need an update of HA. It provides similar entities like the HACS Victron MQTT integration.
Currently I am migration. Still have to find out how to move my old statistics so I am not loosing old energy graph…

16

We have verified that the “Charge batteries to 100%” / Bulk Charge function does not appear to be exposed as a working writable MQTT topic on the local GX device. We can control other Victron functions through Home Assistant, including inverter mode and AC input current limit, but this specific charge-to-100% action appears to remain controlled only through the Cerbo GX / VRM interface.

This suggests the function may be triggered through VRM two-way communication or an internal Venus OS command path rather than through the standard local MQTT W/ namespace.

For Home Assistant automation, this is an important missing control point. My system already evaluates battery SOC, overnight consumption, daytime usage, outside temperature, solar production, and future solar forecast. If poor solar production, storms, or extended cloud cover are predicted, Home Assistant should be able to proactively trigger the same “Charge batteries to 100%” function while shore power is available.

Can Victron expose this function through one of the supported local control paths, such as MQTT, Modbus, D-Bus, Node-RED, or the official VRM API? If the function is already available through an internal Venus OS or VRM endpoint, can the correct supported method be documented so Home Assistant integrations can safely use it?

IMG_1246
IMG_12462778×1284 200 KB

IMG_1245
IMG_12452778×1284 193 KB

17

Hi Joe,

As also mentioned at Charge battery to 100% option · tomer-w/ha-victron-mqtt · Discussion #247 · GitHub, this uses the MQTT topic /Dc/0/PreferRenewableEnergy. As this option is available and writable in the new gui, it MUST also be available via MQTT, as the new remote GUI is using only MQTT to communicate with the venus device, just like the HA integration.

So to get this in the HA integration, please create on issue at the HA core repository at Issues · home-assistant/core · GitHub or at the underlying library repository at Issues · tomer-w/ha-victron-mqtt · GitHub.

Or ask @tomer-w nicely :wink:

With kind regards,
Thiemo van Engelen

18

Thiemo, thanks for the reply, but reading back on the topic I had with Tomer, he asked you if you could help. We are in the US so I don’t know if this is something that is only available as an option in ESS (something we are not allowed to have) This seems to be the only option that is not active by the new integration or the MQTT addon. Do you have a setup you would suggest for dual multiplus 48V 5000 inverters that I could compare to, trying to see why this would not be working if its available. Thanks for any help you can give, I am on the latest firmware v3.73

19

@thiemovanengelen , why dont I see any of those topics here: dbus · victronenergy/venus Wiki ? I thought that should be the official place for all of thpose details.

Anyhow, this is now implemented in the custom integration v2026.5.3.

Will be glad to get feedback on the integration issue list as I find it hard to track this community as well (specially if I’m not tagged).

20

Thiemo it looks like prefer renewable energy lives under the ESS section as I don’t see that option in my VEconfigure file. We are in the US so ESS is not available to us. Could this option be broken out for your US customers? Tomer has added it to the MQTT HA integration but the entity is not showing up.