Battery BMS data
Posted: Tue Jul 28, 2026 5:19 pm
Removing the MITM feature.
THIS IS A MAJOR COURSE CHANGE
In the MITM mode (bms relay) the Bosmonitor would intercept the battery BMS data then forward it to the EG4 cloud.
This had severl issues.
1. Bossmonitor had to be in the middle of the communication path for the BMS data.
2. Required a setup to be placed in the middle then restored upon reset or power glitches.
3. Slowed the timing between the cloud and the inverters.
So the BMS data will be gathered by the rs485 interface. If per pack data is not required then battery SOC reported will be the aggregate of all batteries. If individual battery data is desired the rs485 cable is attached to the batteries.
What got removed: 423 lines of TCP server, SoftAP, DNS proxy, cloud proxy, and dongle IP redirect logic. What
replaced it: 90 lines of passive RS485 listener.
still under development
THIS IS A MAJOR COURSE CHANGE
In the MITM mode (bms relay) the Bosmonitor would intercept the battery BMS data then forward it to the EG4 cloud.
This had severl issues.
1. Bossmonitor had to be in the middle of the communication path for the BMS data.
2. Required a setup to be placed in the middle then restored upon reset or power glitches.
3. Slowed the timing between the cloud and the inverters.
So the BMS data will be gathered by the rs485 interface. If per pack data is not required then battery SOC reported will be the aggregate of all batteries. If individual battery data is desired the rs485 cable is attached to the batteries.
What got removed: 423 lines of TCP server, SoftAP, DNS proxy, cloud proxy, and dongle IP redirect logic. What
replaced it: 90 lines of passive RS485 listener.
still under development