Differences / Advantages over Victron integration by sfstar

[andreas-bulling]

Hi,

I've been using the Victron integration offered by sfstar (https://github.com/sfstar/hass-victron) for quite a while.

I am wondering about the differences to this new integration, particularly advantages/disadvantages, given that the sfstar integration is not that actively developed anymore but a migration will require updating quite a lot of automations, scripts etc.

So I am trying to figure out if it'll be worth it ;)

Thanks!

[tomer-w]

Hi @andreas-bulling, great question!

Disclaimer: I used AI to research the sfstar integration, so take the comparison below with a grain of salt — I'm not an expert on his codebase. If anything is inaccurate, please correct me!

Architecture & Setup

	ha-victron-mqtt	hass-victron (sfstar)
Protocol	MQTT (direct to GX built-in broker)	Modbus TCP
External broker needed	No (optional bridging supported)	N/A
Auto-discovery	Yes (SSDP)	No (manual IP + register scan)
Dependency conflicts	None	pymodbus can conflict with HA built-in modbus
GX device side-effects	None	Register scan causes (harmless) errors on GX
Maintenance	Active (last commit: June 2026)	Dormant (last commit: Feb 2026, 28 open issues)
Official HA	Basis for the new official HA Victron integration	No

Entity Coverage Comparison

Both integrations cover the core Victron devices. Here is a device-by-device breakdown (AI-researched from source code):

Device Category	ha-victron-mqtt	hass-victron (sfstar)
VE.Bus / Multi	93 topics	~110 registers
Battery / SmartShunt	53 topics	~80 registers
Solar Charger (MPPT)	30 topics	~40 registers
Grid Meter	16 topics	~30 registers
System (GX)	42 topics	~30 registers
Settings / ESS	46 topics	~20 registers
Inverter	18 topics	~50 registers
EV Charger (EVCS)	16 topics	~17 registers
Generator / Genset	8 topics	~30 registers
Tank	5 topics	8 registers
Temperature	8 topics	~12 registers
GPS	8 topics + device_tracker	7 registers
Digital Input	5 topics	4 registers
PV Inverter	6 topics	~20 registers
Meteo	7 topics	5 registers
AC Load	9 topics	~12 registers
Heat Pump	9 topics	not supported
Alternator	9 topics	not supported
DC-DC Converter	8 topics	not supported
DC Load	3 topics	not supported
DC System	4 topics	not supported
EV (vehicle data)	In progress	not supported
Computed entities	Yes (energy split, Riemann sums)	not supported
Pulse Meter	not supported	2 registers
Motor Drive	not supported	6 registers
Microgrid	not supported	~20 registers

Summary

• ha-victron-mqtt is wider - covers more device types (39 categories), especially newer ones like heat pumps, alternators, DC-DC converters, and DC loads that sfstar does not have.
• sfstar is deeper on some legacy/niche devices - particularly genset (detailed error codes), inverter (per-tracker statistics), microgrid control registers, and motor drive.
• ha-victron-mqtt has computed entities - derived values like battery charge/discharge power split and Riemann sum energy calculations that are useful for HA energy dashboards.
• ha-victron-mqtt is actively maintained and continues to add new devices (e.g., EV vehicle data is in progress).

Bottom line: If you are already on sfstar and everything works, there is no urgency. But if you are considering a move, ha-victron-mqtt offers broader device support, active development, simpler setup, no dependency conflicts, and is aligned with the official HA integration direction.

Hope this helps! Others who have used both - please chime in with your experience.

[Off-Grid-Garage]

I used to use the fstar solution for ~2 years. It was OK'ish but hat quite a few stability problems, forgot about some devices, stopped updating entities or, completely re-assigned all device IDs which destroyed all my automations.
A year ago I switched to the MQTT integration and had no trouble any more since. The compatibility with my devices is great, config is simple and straight forward, no forgotten or frozen entities any more, everything just works for me. So, yeah, ha-victron-mqtt for the win!🥳