Any questions just ask. I recommend reading the DVCC chapter in the cerbo manual. It is very good and details the various options and settings with examples for different architectures.
I have a questionâŠ
Youâll be using a shunt/BMV.
When the battery BMS requires for the charger to lower the voltage - it could happen, right? - , because it needs to protect itself, how the shunt/BMV will relay that to the inverter and how the inverter/charger will do that?
Is it possible that it wont do that - to lower the voltage - and the battery will still be supplied with a much higher voltage than needed/desired?
Is it possible that the battery to log these high voltage chargings when it requested lower voltages and in the case of a warranty problem the manufacturer to deny the warranty because of an abusive charging?
In this moment, the voltage is dropping when itâs requested - more than necessary because of the DVCC implementation and Pylontech-like assumption - and the battery wont charge more than 95% - no warranty problem here.
But when heâll be using a shunt/BMV, the voltage will not drop, so possible high/over voltages - possible warranty problem, imhoâŠ
We are talking here, right? Because he asked for an opinion and he has the right to know all the implications/consequences, etc.
You are pushing the BMV/shunt solution that will mean more money spent on Victron products, then to spend time to find/guess the correct voltages to be set in order for the battery to properly function, when it clearly saying what it needs, but the DVCC fails to do that⊠Of course, because the manufacturer is sending the Pylontech ID.
I am curious, @RobertSV , is there any other setting in the BMS to emulate a different protocol than Victron/Pylontech?
Did you tried them? Who knows, then it will send another Product ID and youâll not be locked anymore in this conundrum with wrong voltagesâŠ
There are other CAN communication settings, but I am not sure that they correspond to actual battery profiles. One of them, for example, is Growatt, which suggests to me that it is a setting for Growatt inverters.
Those settings will be to enable comms for other manufacturerâs CAN specs. It wonât change how the BMS works.
Your best solution is for the battery manufacturer to improve the firmware or tweak the settings.
If you fancy a bit of a dev project, while still unsupported it at least uses a supported framework, you could create a virtual battery in nodred that is fed by the actual BMS but overides the CVL settings.
This may be a bit much for you depending on your background and it also comes with some challenges, but it is at least a workaround.
Lithium batteries donât have to be managed, most support old school charging and will offer more conservative values to use it in this way. That is another question for the manufacturer.
There are many users with commercial batteries charged this way without issue but it does take a bit of adjustment to ensure it works well.
Many existing optics on this subject.
Iâve asked you because other BMS manufacturers offers many different protocols that are still compatible with Pylontech, but it may send different IDs. For example, for a certain BMS manufacturer, the below CAN V1.2, CAN V2.0, CAN VICTRON, all works with Cerbo as Pylontech, but send different Product ID.
The Ecoworthy batteries use the JBD Smart UP16S Series BMS.
This morning I updated the firmware on all the batteries and have been in conversation with the manufacturer about this issue. The first suggestion was doing a couple of deep discharge and recharge cycles. The system is powering an offgrid family and that is not really a great option at this time, as the amount of sun lately has been very variable.
The virtual battery project sounds interesting but time to work on that is not readily available.
I manage several systems and this is the only one with all these âfancyâ interfaces and configurations - everything else is old school âdumbâ charging with simple reading of SOC from the MPPTâs or inverterâs displays. The Cerbo display is certainly nicer to look at for a quick view of how everything is working 
Indeed, this seems to be one of the first âgo-toâsâ when a battery doesnât behave.
Interesting side note. The BMS in this unit retails at $52. The one in many of my sites is $440, at least I now appreciate what the other $388 does 
After updating to the firmware version indicated by the manufacturer, the batteries, at least for now, seem to be behaving properly.
This afternoon they reached 100% and stayed there, not doing the sudden discharge back down to 94%. The MPPTs stayed in Bulk mode and everything seems to be working properly.
I will monitor them closely to see that this behaviour continues over the coming days.
The CVLs are the same, or they changed something there? Those 58.4 and 54.4?
If they changed the 54.4 to anything above 55V, for example 55.2, all will work OK.
Progress. What a difference some firmware can make.