question

greatlake avatar image
greatlake asked

Some Modbus TCP battery sensors not available

Hi all,

I am trying to set up a Home Assistant dashboard for my battery bank using the Modbus TCP integration. VenusOS 3.12 runs on a Raspberry Pi 3B and pulls the data from my BMV-712 Smart battery monitor.
While some of the address values for device_class: battery are working flawlessly it is unable to read the sensor config of

- name: BMV_712 Time to go

unit_of_measurement: "seconds"

slave: 238

address: 303

input_type: holding

data_type: uint16

scale: 0.01

precision: 2

device_class: battery

state_class: measurement

and

- name: BMV_712 Time since last charge

unit_of_measurement: "seconds"

slave: 238

address: 289

input_type: holding

data_type: uint16

scale: 0.01

precision: 2

device_class: battery

state_class: measurement

The sensors don't show up in the list of entities after having restarted Home Assistant although I used the proper registers from the current list.
modbus-battery-time-fail.png
What I am trying to achieve is having the Battery Summary & Battery History entries from VRM available in Home Assistant.
vrm-battery-summary-history.pngAm I missing something here?

Thanks in advance.

BMV Battery MonitorModbus TCP
2 |3000

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

1 Answer
greatlake avatar image
greatlake answered ·

I found the cause myself. In my sensors config there were duplicate address entries. Both sensors appeared on the list once I had altered them.

2 |3000

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.