No ability to change the unique ID about dbus-serialbattery HOT 10 CLOSED

With the latest nightly you can set this in the config file.

https://github.com/mr-manuel/venus-os_dbus-serialbattery/blob/1cc775d29cd8a7431acdd4e45584187693edf35b/etc/dbus-serialbattery/config.default.ini#L386-L390

from dbus-serialbattery.

This is not a bug. just read the complete error log. I copy the relevant part over for you:

2024-04-12 15:06:19.600923500 ERROR:SerialBattery:Change the battery capacities to be unique.
2024-04-12 15:06:19.601649500 ERROR:SerialBattery:Example for batteries with 280 Ah:
2024-04-12 15:06:19.602291500 ERROR:SerialBattery:- Battery 1: 279 Ah
2024-04-12 15:06:19.602859500 ERROR:SerialBattery:- Battery 2: 280 Ah
2024-04-12 15:06:19.603398500 ERROR:SerialBattery:- Battery 3: 281 Ah
2024-04-12 15:06:19.603923500 ERROR:SerialBattery:This little difference does not matter for the battery.

from dbus-serialbattery.

Fair enough - it's asking me to do something that I believe may be impossible.

from dbus-serialbattery.

On every BMS you need to be able to change the capacity. Is it custom build or did you buy it as it is?
a) Custom build: You already had to set the capacity. Just set it again
b) You bought it: Ask your dealer on how you can change the capacity or if you get the protocol documentation because you need to read the serial number via serial connection.

from dbus-serialbattery.

I bought them - they are EG4 Lifepower batteries. I am checking with them to confirm, but even their own software doesn't read the serial number nor give a way to change the capacity.

from dbus-serialbattery.

Let's wait what they answer. Maybe there is another unique parameter we can read.

from dbus-serialbattery.

Temporarely you could try to add

    def unique_identifier(self) -> str:
        return self.port

before

Keep attention at the indentation when copying the code.

Anyway this is only a possible temporary solution and not recommended.

from dbus-serialbattery.

Oh, that's genius. I'll give it a try. That would at least get me on the latest code while I figure out a better long-term solution.

from dbus-serialbattery.

No response from them - it's kind of expected since they don't have a published spec for reading from their batteries in this way.

Utilizing the port as a unique ID has been working perfectly. It allowed me to use the latest version and now I have clean logs.

from dbus-serialbattery.

Ok, only when changing ports it will also change custom names and VRM ID's.

from dbus-serialbattery.