https://thesunpays.com/downloads/files/hubble_am-2_manual.pdf

@DaveMM see pinout in the Hubble AM 2 manual, this corresponds to the layout malek94 posted as well

On 2022/12/05 at 5:56 PM, malek94 said:

for RG 11 - rs232

Pin3：TX
Pin4:RX
Pin5:GND 

Both the AM series and Revov R100/B100's use the same cable according to https://solar-assistant.io/shop/products/pace_rs232

This will be the pinout I'm going to try once my parts arrive for the ESP32 setup.

 

Hi,
great way to get battery details. Works for me with Titansolar 10 kWh packs and waveshare RS232 to (Power Over) Ethernet device - at least for the first pack. For the second pack I get

 

Error parsing BMS analog data: Cannot read multiple packs

Error retrieving BMS analog data: Error parsing BMS analog data: Cannot read multiple packs

-> Outgoing Data:  b'~250146A60000FD97\r'

<- Incoming data:  b'~25014600400C37B54E204E20FB00\r'

SOI:  0x7e

VER:  b'25'

 

Any idea how to get both packs' data into MQTT broker ?

Best Regards

Volker

 

Edited January 10, 20251 yr by VW67

I just realized that this is pulling in a crap tone of entities for packs it shouldn't.

EG I have 4 batteries so I'm expecting Pack1 - 4 readings which I'm getting but in my entity list I'm seeing entities for up to pace 241?

Is there a way to limit MQTT to read only the first 4 packs so that it doesn't create this massive list which I suspect is the cause that some things in HA is working very slowly.

 

Hello, when I was doing the integration for my batteries, I looked at your work too, to understand the basic principles. 
Perhaps you want to try loading the register map for your BMS into my integration? I tried to make it as universal 
and scalable as possible for batteries from other vendors.

You can see my code here: https://github.com/mamontuka/ritar-bms-ha
Register map template, i think can be ajusted for any RS485 battery: https://github.com/mamontuka/ritar-bms-ha/blob/main/modbus_registers.py

Anyway, if you're interested, you can try it. I'm trying to figure out how universal I've managed to make it.

WBR

sorry for copy past from google translator )

Edited July 7, 2025Jul 7 by mamont

https://github.com/mamontuka/ritar-bms-ha/blob/main/united_bms/README.md

Edited July 10, 2025Jul 10 by mamont

Hello. Can anyone help me solve the problem?

Hello BMS Pace
Starting up...
Loading options.json
Config: {"mqtt_host": "192.168.100.100", "mqtt_port": 1883, "mqtt_user": "mqtt", "mqtt_password": "mqtt", "mqtt_ha_discovery": true, "mqtt_ha_discovery_topic": "homeassistant", "mqtt_base_topic": "bmspace", "connection_type": "IP", "bms_ip": "192.168.100.220", "bms_port": 9999, "bms_serial": "/dev/", "scan_interval": 7, "debug_output": 3, "force_pack_offset": 0, "zero_pad_number_cells": 0, "zero_pad_number_packs": 0}
Connection Type: IP
MQTT connected with result code 0
Connecting to BMS...
trying to connect 192.168.100.220:9999
BMS socket connected
-> Outgoing Data:  b'~250146C10000FD9A\r'
<- Incoming data:  b'~2\x00\x00\x00\x0c6C10000FD9A\r'
SOI:  0x7e
VER:  b'2\x00'
ADR:  b'\x00\x00'
CID1 (Type):  b'\x0c6'
RTN:  b'C1'
LENGTH:  b'0000'
 - LCHKSUM:  48
 - LENID:  b'000'
 - LENID (int):  0
INFO:  b''
CHKSUM:  b'FD9A'
Calc CHKSUM:  FE58
Received and calculated CHKSUM does not match: Received: FD9A, Calculated: FE58
...for incoming data: b'~2\x00\x00\x00\x0c6C10000FD9A\r' |Hex: 7e 32 00 00 00 0c 36 43 31 30 30 30 30 46 44 39 41 0d
Length of incoming data as measured: 18
SOI:  0x7e
VER:  b'2\x00'
ADR:  b'\x00\x00'
CID1 (Type):  b'\x0c6'
RTN (decode!):  b'C1'
LENGTH:  b'0000'
 - LCHKSUM:  48
 - LENID:  b'000'
 - LENID (int):  0
INFO:  b''
CHKSUM:  b'FD9A'
Error retrieving BMS version number
-> Outgoing Data:  b'~250146C20000FD99\r'
<- Incoming data:  b'~2\x00\x00\x00\x0c6C20000FD99\r'
SOI:  0x7e
VER:  b'2\x00'
ADR:  b'\x00\x00'
CID1 (Type):  b'\x0c6'
RTN:  b'C2'
LENGTH:  b'0000'
 - LCHKSUM:  48
 - LENID:  b'000'
 - LENID (int):  0
INFO:  b''
CHKSUM:  b'FD99'
Calc CHKSUM:  FE57
Received and calculated CHKSUM does not match: Received: FD99, Calculated: FE57
...for incoming data: b'~2\x00\x00\x00\x0c6C20000FD99\r' |Hex: 7e 32 00 00 00 0c 36 43 32 30 30 30 30 46 44 39 39 0d
Length of incoming data as measured: 18
SOI:  0x7e
VER:  b'2\x00'
ADR:  b'\x00\x00'
CID1 (Type):  b'\x0c6'
RTN (decode!):  b'C2'
LENGTH:  b'0000'
 - LCHKSUM:  48
 - LENID:  b'000'
 - LENID (int):  0
INFO:  b''
CHKSUM:  b'FD99'
Error: Checksum error
Error retrieving BMS and pack serial numbers. This is required for HA Discovery. Exiting...
Script exiting

Edited August 20, 2025Aug 20 by sikorb

@sikorb ,

I'm no expert on this, but if I compare my working system, I would say your incoming data from the battery is not correct.

So either you have a misconfigured data/speed setting (9600,8,N,1) - unlikely, as i read that this is cast in stone in the S/W, so not really configurable, or you have some kind of wiring problem.

This is what a good incoming stream should look like.

Hello,

I've modified a repo for seplos and adapted it to report telemetry data directly to Home Assistant, you can use an RS232 interface with ESP32 or if you have an ESI interface and by any change they've given you the wifi module with esp32 inside, you can just upload the program there and specify everything you'll need: https://github.com/SaschaKP/esphome-pace-bms
(of course you can use an ESP32 or whatever you have with an RS232 interface)

Edited September 25, 2025Sep 25 by SaschaKP

Good day. Is it possible to add charge/discharge MOSFET control to this add-on?