search

sfstar / hass-victron

Integration for Home Assistant to fetch data from the victron gx device via modbusTCP
Apache License 2.0
157 stars 24 forks source link

Two batteries - Integration only one showing #217

Open Levanterman opened 4 days ago

Levanterman commented 4 days ago

Hi

Great integration, love it, but slight problem, with the integration I have two batteries , and although the SoC and Soc2 are showing, they are identical, you can see the screen shots of the Cerbo showing two batteries, but this integration showing two identical readings in the integration.

I have 2 x settings showing in the integration, but one battery, the settings and battery components show the same % of one of the battery, no sign of the other battery.

vic4

Thanks

vic5 vic6 vic1
sfstar commented 2 days ago

Thank you for opening this issue. Could you perhaps share the unit id's of the batteries that are connected in your system? You can find them under: "Settings -> services -> Modbus TCP -> available services"

Levanterman commented 2 days ago

Thank you for opening this issue. Could you perhaps share the unit id's of the batteries that are connected in your system? You can find them under: "Settings -> services -> Modbus TCP -> available services"

Thanks for the reply, I went to Available Services and now I can see why the second battery is not showing. image

only 1 battery is being publlished by Modbus, and then i remembered that when you add the second battery to the system you do not connect the second battery to the BMS-CAN, here is a snippet from the Drift Pro Manual:

image

So both batteries show up in the Cerbo but one is connected to the BMS-CAN and the other to VE-CAN

image

So as well as Modbus I enabled MQTT, and I can see the other battery on the Cerbo MQTT image

so i added entities in the configuration.yaml from the MQTT and used those entities for the second battery, Soc, Volt, Current and you can see in the graphical integration

image

Looks like the instanceID might be 512, but its not being published by Modbus so maybe not accessible by your integration, but thank you , it great.