If you’re running a Victron-powered energy system and using Home Assistant, there’s a good chance you’ve already looked for a clean way to bring your battery data into your smart home setup. Victron has a few different integration paths, and they are often confused with each other.

This post is about the official Victron BLE integration in Home Assistant:

https://www.home-assistant.io/integrations/victron_ble

It is important to be clear from the start: this is not the same as the custom Modbus-based integration (like https://github.com/sfstar/hass-victron). That Modbus setup is powerful and works well for GX devices and wired networks, but it’s a completely different architecture. We’ll stay focused on the BLE approach here.

---

What the Victron BLE integration actually does

The Victron BLE integration connects Home Assistant directly to supported Victron devices using Bluetooth Low Energy (BLE). That means no GX device, no MQTT bridge, and no Modbus configuration. Just a nearby device broadcasting data.

Typical supported devices include:

• Victron SmartShunt
• Victron BMV battery monitors (Bluetooth-enabled models)
• Victron SmartSolar MPPT charge controllers with built-in Bluetooth
• Other Victron devices that broadcast via VictronConnect BLE protocol

Instead of polling over a network, Home Assistant listens to BLE advertisements and builds entities from that data.

This makes it especially useful for:

• Off-grid cabins
• Vans and RVs
• Small solar systems without Venus OS or Cerbo GX
• Simple battery monitoring setups

---

How the system is structured

To understand how this integration fits into Home Assistant, it helps to break it down into components.

1. Victron device (data source)

This is your physical hardware, such as a SmartShunt or SmartSolar MPPT.

It continuously measures and broadcasts:

• Battery voltage (V)
• Battery current (A)
• Power (W)
• State of charge (%)
• Energy yield (kWh)
• Solar input metrics (if applicable)

Everything is calculated and exposed locally on the device.

---

2. Bluetooth Low Energy (BLE)

BLE is the transport layer.

Key points:

• Devices broadcast small packets of data
• No pairing is required in most cases
• Range is typically 5–15 meters indoors
• Walls and metal enclosures reduce signal quality

For stable setups, the Home Assistant machine (or a BLE proxy) should be reasonably close to the Victron hardware.

---

3. Home Assistant Victron BLE integration

Once enabled, Home Assistant:

• Detects Victron BLE advertisements
• Identifies supported devices automatically
• Creates entities based on available data

You will typically see entities like:

• sensor.victron_battery_voltage
• sensor.victron_battery_current
• sensor.victron_state_of_charge
• sensor.victron_power
• sensor.victron_yield_today

Each device becomes a structured set of sensors you can use in dashboards, automations, and energy tracking.

---

4. Home Assistant entities and energy system

Once exposed, these sensors integrate directly into:

• Energy dashboard (kWh tracking)
• Automations
• Historical graphs
• Notifications

For example, battery state of charge becomes a triggerable value, not just a number in an app.

---

Setting it up (high-level)

Setup is intentionally simple:

1. Enable Bluetooth on your Home Assistant host (or use a BLE proxy)
2. Install the Victron BLE integration from Home Assistant
3. Power on your Victron device with Bluetooth enabled
4. Wait for automatic discovery

If everything is within range, devices typically appear within seconds to a few minutes.

No manual configuration is usually required unless you have multiple overlapping devices.

---

What makes BLE different from Modbus setups

It’s worth separating this clearly because it is a common point of confusion.

The Modbus-based Victron integration (like the one discussed in my earlier post https://roenning.net/2024/03/25/integrating-victron-with-home-assistant/) requires:

• A Victron GX device (Cerbo GX, Venus OS, etc.)
• Network connectivity (Ethernet/Wi-Fi)
• Modbus TCP or MQTT configuration

The BLE integration, by contrast:

• Does NOT require a GX device
• Does NOT require network setup between Victron and Home Assistant
• Works directly over Bluetooth
• Is more lightweight but less scalable

In short:

• BLE = simple, local, close-range monitoring
• Modbus = structured, scalable system integration

---

Practical use case: smart energy load control

Victron BLE in Home Assistant offers applications that are highly useful. One such application is automatic load control. It operates based on battery state of charge and solar production.

Let’s say you have:

• A Victron SmartShunt monitoring a 12V or 24V battery system
• A smart plug controlling a water heater or space heater
• Solar panels feeding your system

You want to only run heavy loads when the battery is sufficiently charged.

Example logic

• If battery SOC is above 85%, enable the load
• If SOC drops below 60%, disable it
• Only allow heating when solar production is strong enough

---

YAML automation example

Here is a practical Home Assistant automation using Victron BLE sensors:

alias: "Solar surplus - enable water heater"
mode: singletrigger:
  - platform: numeric_state
    entity_id: sensor.victron_state_of_charge
    above: 85
  - platform: numeric_state
    entity_id: sensor.victron_state_of_charge
    below: 60action:
  - choose:
      - conditions:
          - condition: numeric_state
            entity_id: sensor.victron_state_of_charge
            above: 85
        sequence:
          - service: switch.turn_on
            target:
              entity_id: switch.water_heater
      - conditions:
          - condition: numeric_state
            entity_id: sensor.victron_state_of_charge
            below: 60
        sequence:
          - service: switch.turn_off
            target:
              entity_id: switch.water_heater

This creates a simple but effective energy buffer system:

• You consume surplus energy when available
• You protect the battery from deep discharge
• You automate decisions you would otherwise make manually

---

Adding solar production awareness

You can improve the logic further by combining battery SOC with solar yield:

condition:
  - condition: numeric_state
    entity_id: sensor.victron_solar_power
    above: 800

This ensures loads only run when there is actual solar surplus (values depend on your system size).

---

Why this integration is especially useful

The Victron BLE integration shines in setups where simplicity matters.

You get:

• Fast setup
• No extra hardware
• Local-only communication
• Reliable battery visibility

It is especially useful for mobile or remote systems where adding a GX device is unnecessary overhead.

However, it does come with limitations:

• Short Bluetooth range
• Limited scalability (few devices per area)
• No advanced system-wide coordination like Venus OS

So it’s best seen as a lightweight monitoring and automation layer, not a full system controller.

---

Final thoughts

The Victron BLE integration is one of the easiest ways to bring real energy awareness into Home Assistant. It turns raw battery and solar data into something actionable, without requiring a full Victron GX setup or network configuration.

For smaller systems, it often hits the sweet spot: simple, local, and immediately useful.

If you later scale up into a more complex installation, you can always move toward Modbus or Venus OS-based integrations. But for many setups, BLE is more than enough.