Find answers, ask questions, and connect with our <br>community around the world.

  • charly3333

    Member
    March 5, 2026 at 12:03 am

    Hello, the gloomy weather is drawing to a close, the sunshine is beginning and the old problems with the new firmware are back.

    How can we solve this problem?

    In my opinion, nothing has visibly changed in the new firmware SPBMS16SRPV1.5.29.C16. In the meantime, I’ve read the data from the 128 cells hidden in the 8 E-Boxes via the console connection and saved it in Home Assistant’s InfluxDB database. I now select the cell with the highest voltage. When it rises to 3.45V, I currently manually reduce the charging current from the two DEYE inverters. This prevents an abrupt charging stop by the Pytes BMS. I limit the charging current to 10A. In the PytesBat, you can see that the capacity of the other batteries is slowly increasing, indicating a balancing process.

    I would have expected a similar procedure from the Pytes BMS in a professional system. I’m not sure if the BMS interface between DEYE and PYTES even supports this.

    Is my approach correct, or could the charging behavior be handled differently?

    As a next step, I plan to automatically limit the charging current via Modbus/RTU telegrams before a sudden charging termination is triggered.

    I think this method won’t affect the protocol between PYTES and DEYE, but rather complement it with a useful extension.

    It seems to me that balancing within an E-Box with its 16 cells works correctly, but it doesn’t take into account the other E-Boxes in the system.

    Is PYTES developing anything in this direction, or does every PYTES E-Box owner have to take care of regulated balancing themselves?

    Kind regards