This is a service for bridging Victron Energy's VE.Direct protocol to MQTT. Originally written and tested using Raspberry Pi 3B+ with Victron BMV-702. With enough interest and the help of others, this may be expanded to interface with other devices in the same family.
Requires mosquitto runtime and development libraries (websockets not used)
> sudo apt-get update
> sudo apt-get upgrade
> sudo apt-get install mosquitto libmosquitto-dev mosquitto-clients libsystemd-dev
Ensuring that the mosquitto MQTT broker is functioning properly is beyond the scope of this document. There are plenty of other resources, but do make sure it's working before proceeding.
On a Raspberry Pi 3B+, make sure to disable the serial shell using the configuration tool [Interface Options --> Serial, enable the port but not the shell]. The installation script will copy the executable and start as a service.
> sudo raspi-config
Connect the Raspberry Pi's serial port with the device's VE.Direct port. MAKE SURE THE VOLTAGES ARE COMPATIBLE. VE.Direct ports are not all the same voltage! The BMV-702 used initially was 3.3V so this works with the Raspberry Pi's voltage.
Raspberry Pi VE.Direct
GND GND
Rx Tx
TX Rx
Get a copy of the project, build and install it
> cd ~
> git clone https://github/com/TheWandrr/vedirect_to_mqtt
> cd vedirect_to_mqtt
> sudo make install
Use the mosquitto_sub tool to verify that MQTT data is being published. You could also use anything else that subscribes to a MQTT broker, like a smartphone app.
> mosquitto_sub -t 'bmv/#' -v
You should see something like the following repeating at about 1-2 second intervals:
bmv/hex/soc 65.46
bmv/hex/main_voltage 12.95
bmv/hex/consumed_ah -68.30
bmv/hex/current_coarse -12.20
bmv/text/max_discharge -160.896
bmv/text/last_discharge -68.268
bmv/text/average_discharge -38.254
bmv/text/num_cycles 77
bmv/text/num_full_discharge 0
bmv/text/cumulative_ah -14869.411
bmv/text/min_voltage 0.002
bmv/text/max_voltage 14.533
bmv/text/time_since_full_charge 24821
bmv/text/num_auto_sync 101
bmv/text/num_low_volt_alarm 0
bmv/text/num_high_volt_alarm 0
bmv/text/energy_discharged 192.270
bmv/text/energy_charged 171.130
bmv/text/id 0
bmv/text/main_voltage 12.905
bmv/text/current_fine -15.468
bmv/text/power -200
bmv/text/consumed_ah -68.268
bmv/text/soc 65.400
bmv/text/ttg 127
bmv/text/alarm_state 0
bmv/text/relay_state 0
bmv/text/alarm_reason 0
bmv/text/sw_version 308
bmv/text/max_discharge -160.896
bmv/text/last_discharge -68.272
bmv/text/average_discharge -38.254
bmv/text/num_cycles 77
bmv/text/num_full_discharge 0
bmv/text/cumulative_ah -14869.415
bmv/text/min_voltage 0.002
bmv/text/max_voltage 14.533
bmv/text/time_since_full_charge 24822
bmv/text/num_auto_sync 101
bmv/text/num_low_volt_alarm 0
bmv/text/num_high_volt_alarm 0
bmv/text/energy_discharged 192.270
bmv/text/energy_charged 171.130
You can control which of the HEX values are requested and published by modifying the array in the main source file and rebuilding.
struct VEPeriodicRequest periodic_request_list[] = {
{ true, "soc", 3, 0 },
{ true, "current_coarse", 3, 0 },
{ true, "consumed_ah", 3, 0 },
{ true, "main_voltage", 3, 0 },
};
- TheWandrr - Initial work - TheWandrr
See also the list of contributors who participated in this project.
This project is licensed under the MIT License - see the LICENSE.md file for details