Read-Victron-advertised-data

KO | EN

gitlite — search

#llm #machine-learning #rust #linux #docker #macos #nodejs #cli #vue #awesome-list #pytorch #security #ios #openai

Read-Victron-advertised-data

(★ 60)

Read the Bluetooth advertised data from a Victron Battery Monitor or Solar Charger, without (or in addition to) using the VictronConnect App

Read-Victron-advertised-data Latest Version Download

Download Latest Version (.zip)

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

## Read Victron Advertised Data
This submission provides two Arduino compatible programs (one for any Victron battery monitor the other any Victron solar controller). These programs bring together all the following knowledge to receive, dissect, decrypt, decode and report the current device status and readings from the 'advertised data' that is continually transmitted over Bluetooth Low Energy (BLE) by the Victron device.

### 1. My Hardware
My battery monitors are a [Victron SmartShunt](https://www.victronenergy.com/battery-monitors/smart-battery-shunt) and several [Victron BMV-712 Smart](https://www.victronenergy.com/display-and-panels/bmv-712-smart).

My solar controller is a [Victron BlueSolar MPPT 100/30](https://www.victronenergy.com/solar-charge-controllers/mppt-100-30).

I used the Arduino IDE to develop these programs to run on ESP-32 devices with in-built BLE capability. The code was tested on:

- [SparkFun MicroMod WiFi Function Board](https://www.sparkfun.com/sparkfun-micromod-wifi-function-board-esp32.html) with its in-built ESP32-WROOM-32E.
- [WeMos D1 R32 (ESP32) Development Board](https://www.makerstore.com.au/product/elec-esp32-d1-r32/) that is also fitted with a ESP32-WROOM.

### 2. Key Inputs
There were many challenges along the way and this submission aims to capture the key points in one place, for others wanting to read their Victron device status, without (or in addition to) using the Victron Connect app (VC) on your mobile.

My primary reference is [the Feb 2023 post 'Victron Bluetooth Advertising Protocol' by Victron staff](https://communityarchive.victronenergy.com/questions/187303/victron-bluetooth-advertising-protocol.html). This post included the essential "Extra Manufacturer Data" document and further down the page were two long posts (by Jake Baldwin and Chris Jackson respectively) that I found very useful. Both have been uploaded into this repository for convenience:

- ["Extra Manufacturer Data" by Victron](docs/Victron_Extra_Manufacturer_Data.pdf)

- [Posts by Jake Baldwin & Chris Jackson](docs/Victron_posts_Jake_Baldwin_Chris_Jackson.pdf)

### 3. The Basics
The Victron device continually updates and advertises the data, transmitting it over Bluetooth Low Energy (BLE). You can see the data when running VC on your Android mobile. Here is an example screenshot for my Victron environment showing the advertised data from several devices at once:

Reading the data does NOT require a Bluetooth connection be established ! This means you don't need to know any UUID or Characteristic codes to access the ad data. All you need is the name of the Victron Device (as shown in VC). The device name will be the default Victron name for that device, unless you have changed the name in the VC settings, as I have done.

Another app I found extremely useful is 'nRF connect' (nRF) by Nordic semiconductor. Here are two screenshots from nRF showing my Bluetooth environment. Note I have clicked on 'BATTbank_Smartshunt' to reveal the data being advertised by my SmartShunt, and all WITHOUT establishing a Bluetooth connection. When I click on RAW I get even more detailed information provided as HEX values, plus the ability to copy/share the HEX data string by selecting MORE.

### 4. Dissecting the Bluetooth Data
As you can see from the nRF screenshot above there is around 40 or 50 bytes of data or more in every Bluetooth transmission, depending on length of the ASCII device name. This data is refreshed every 200ms or so. It also contains up to 16 bytes of encrypted 'extra manufacturer data' that we need to extract, decrypt, decode and report.

The two text files following provide a detailed breakdown of example data advertised by a Battery Monitor (BMV-712) and a Solar Controller (MPPT100/30).

- [Ad Data Structure - Battery Monitor](docs/Ad%20Data%20Structure%20-%20Battery%20Monitor.txt)
- [Ad Data Structure - Solar Controller](docs/Ad%20Data%20Structure%20-%20Solar%20Controller.txt)

### 5. Decryption
In the attachments above the Battery Monitor provided 15 bytes of encrypted data (whereas the Solar Controller provides only 12 bytes). We now need to decrypt those 15 HEX bytes to reveal the 15 bytes of actual data they contain.

As explained in "Extra Manufacturer Data" document, Victron use the AES Counter mode (AES-CTR) protocol to encrypt the data. AES-CTR is a [Block Cipher Mode of Operation](https://en.wikipedia.org/wiki/Block_cipher_mode_of_operation#CTR) that turns a block cipher into a stream cipher.

As I'm developing in the Arduino environment I looked to that ecosystem for a suitable decryption library, and soon settled on the wolfssl library  https://www.wolfssl.com/ which can be downloaded and installed in the usual way using the Arduino IDE library manager.

The wolfSSL AES decryption algorithm I used (wc_AesCtrDecrypt) is just a small subset the of many algorithms available in the wolfSSL library. All are documented in the [wolfSSL Manual](https://www.wolfssl.com/documentation/manuals/wolfssl/group__AES.html)

To perform a decryption three user inputs are required:
- The Encryption Key
- An Initialization Vector "IV" (also known as "nonce/counter" or "salt")
- The encrypted data, to be decrypted

All three must be 16 bytes in length when input to the wolfssl decryption algorithm, padded with zeros if needs be.

The Encryption Key is a sequence of 16 bytes unique to each Victron device. It can be found in the Settings using the VC app on each device.
In the App: go to Settings (cog) -> 3 dots (top right) -> Product-Info -> scroll down > encryption key

** BEWARE ** if you copy the key by hand there is a flaw in the VC App where only 31 of the 32 HEX characters defining the key may be visible. The safer option is to use the copy / select all dialogue that pops up if you tap on the key, then share.

An IV is included in every Bluetooth transmission, and it is incremented before (almost) every transmission. It is transmitted unencrypted and arrives as the first pair of bytes in Part 3 of each transmission. Note that the received IV has already been used as an input to the encryption process in the source Victron device, just before Bluetooth transmission. Consequently each decryption must use the specific IV that was transmitted with the encrypted data.

The IV is transmitted "little-endian" and must be input to the wolfssl AES_CTR decryption algorithm in same order, but padded with zeros to form a 16 byte array. In the example data above the IV bytes are `0x790B`, therefore the IV array for input to the wolfssl algorithm would be: `79 0B 00 00 00 00 00 00 00 00 00 00 00 00 00 00`.

The data for decryption is the 15 encrypted bytes (or 12 for a Solar Controller) embedded in each the Bluetooth transmission. As shown in the example data attachment 6 above these are at the end of Part 3 of the transmission. It also must be padded to 16 bytes.

The output of the decryption phase is another 16 byte array containing the actual unencrypted data.

(If you have questions regarding the wolfssl library they have a bunch of user forums at https://www.wolfssl.com/forums/ where you can ask. That is where I posted when I was trying to figure the decryption out. I must say the staff at wolfssl were very professional, knowledgeable and helpful).

### 6. The Code

#### 6.1 [BatteryMonitor](/BatteryMonitor)
This program is built from the following files:

##### [BatteryMonitor.ino](./BatteryMonitor/BatteryMonitor.ino)
The main body, with `setup()` and `loop()` per the Arduino environment

##### [BatteryMonitor/VBM.h](./BatteryMonitor.VBM.h) / [VBM.cpp](./BatteryMonitor/VBM.cpp)
This pair provide the detailed algorithms to read, dissect, decrypt, decode and report data from a Victron Battery Monitor (VBM)

The principles of reading, dissecting and decrypting were introduced above, whereas the following describes decoding of the decrypted data, in preparation for reporting. This is where the bit field definitions in the "Extra Manufacturer Data" document comes into play, in particular the "Battery Monitor" table on page 3.

One Victron design choice added much complication: the data is encoded "little-endian" or in reverse order. This is easy to handle for 16 bit (2 byte) values, just swap the bytes. But some values are 2,9,10,20 or 22 bits in length and this greatly complicates the process of mapping from the decrypted bytes to each value. The following items describe/show these detailed mappings for a Battery Monitor, as text and a drawing:

- [Bit Field Mapping - Battery Monitor.txt](Bit%20Field%20Mapping%20-%20Battery%20Monitor.txt')
- [Byte Mapping - Victron BM.jpg](docs/Byte%20Mapping%20-%20Victron%20BM.jpg)

(As an aside I did spot a couple of small errors in the table. The battery current is a 22 bit signed integer. Consequently its range must be from $-2^{21}$ to $(2^{21}-1)$ or -2097151 to 2097151 mA, i.e half the -4194 to 4194 Amp range shown in the table. And the N/A value must be `0x1FFFFF` not `0x3FFFFF`).

##### [BatteryMonitor/ZZ.h](./BatteryMonitor/ZZ.h) / [ZZ.cpp](./BatteryMonitor/ZZ.cpp)
This pair provide miscellaneous general/global variables or functions, simply to keep the main body clean.

#### 6.2 [SolarController](./SolarController)
This program is built from the following files:

##### SolarController.ino
The main body, with `setup()` and `loop()` per the Arduino environment.

##### [SolarController/VSC.h](./SolarController/VSC.h) / [VSC.cpp](./SolarController/VSC.cpp)
This pair provide the detailed algorithms to read, dissect, decrypt, decode and report data from a Victron Solar Controller (VSC).

The principles of reading, dissecting and decrypting were introduced above.

The decoding of the decrypted data, in preparation for reporting follows similar structure and logic to the VBM routines, except referencing
the "Solar Controller" table on page 3 of the "Extra Manufacturer Data" document. Fortunately the byte mapping is much less complicated in this case and can be readily understood by looking at the code directly.

##### [SolarController/ZZ.h](./SolarController/ZZ.h) / [ZZ.cpp](./SolarController/ZZ.cpp)
This pair provide miscellaneous general/global variables or functions, simply to keep the main body clean.

#### 6.3 Before Compiling
Before compiling you must edit the code to initialize the following information specific to your Victron device:
- `<device_name>`
- `<device_address>`
- `<encryption_key>`

NB: <device_address> and <encryption_key> must be lower case.

See the detailed explanation in the introduction text of the main `.ino` file.

#### 6.4 Libraries & Compiling
Three libraries are used when compiling this program: 
(1) BLE library for Bluetooth Low Energy functionality
(2) wolfssl for the AES-CTR decryption algorithms
(3) Streaming library by Mikal Hart

The BLE library is built into the Arduino IDE these days (I'm using IDE V2.3.6)

The wolfssl library must be added using the library manager of the IDE, just search for wolfssl, check it's from wolfSSL Inc then install.

The Streaming library simply minimises repetitive use of Serial.print().

Before compiling select "`ESP32 Dev Module`" in the IDE pull-down for target board selection.

### 7. Run-Time Outputs

The following test uses the `BatteryMonitor` program.

Run-Time outputs for the SolarController are very similar, just different variables reported and thus different data.

Using a 4ohm dummy load and a pair of 12V batteries (rather worn out) wired to put 24V across the load including my SmartShunt.
This should produce for a current of approximately 24/4 = 6A (depending on the voltage drop as the current increases).

Following are 5 screen snippets taken within a few minutes of each other, during the test described above:
- Arduino IDE Serial Monitor output as `BatteryMonitor` is 'booted up' on ESP32:
<img src="images/BM_output_5.6A.jpg" width="150" height="300">

- Serial Monitor VERBOSE mode output (I entered "V" to toggle ON)
<img src="images/BM_output_5_6A_VERBOSE.JPG" width="250" height="300">

- Screenshot from 'VictronConnect' app on my mobile
<img src="images/VC_screenshot_2.png" width="150" height="300">

- Screenshot #1 from the 'nRF Connect' app on my mobile
<img src="images/nRF_screenshot_SS_2.png" width="150" height="300">

- Screenshot #2 from the 'nRF Connect' app on my mobile, RAW mode
<img src="images/nRF_screenshot_SS_RAW_2.png" width="150" height="300">
----------------------------- / the end / ---------------------------

Read-Victron-advertised-data

Read-Victron-advertised-data Latest Version Download

Today's picks

Was this content helpful?

Recent Feedback

Read-Victron-advertised-data

Read-Victron-advertised-data Latest Version Download

Today's picks

Was this content helpful?

Recent Feedback

Download README