ramack
commented
1 year ago I face similar problems and think that we should allow a dedicated mapping from serialnumbers as read by the low level drivers to instance numbers. That would also help in setups with multiple batteries.
mr-manuel
My apologies if this has been covered elsewhere. I searched but didn't find anything. Describe the bug If the cerbo is reboot for any reason, often times the bms gets assigned a different instance number which then requires changing settings and reconnecting nodes in node red.
To Reproduce Steps to reproduce the behavior: Reboot cerbo, then battery alarm 'low voltage' because bms has been assigned a different number. Seems to bounce back and forth between 1 and 2.
Expected behavior I would expect the bms to always be assigned the same number.
Screenshots If applicable, add screenshots to help explain your problem.
VenusOS (please complete the following information):
Battery/BMS (please complete the following information):
Additional context I have a rs485 to USB adapter plugged into the first USB port which runs a external relay board. Plugged into the second USB port is a powered USB hub with a mppt on ve.direct to USB, a USb bt dongle, tank140, and the uart Daly adapter. All other devices survive reboots with no issues.
I have posted this issue on the victron board and victrons response is that it is a bms driver issue.