diy solar

diy solar

Is there an esphome for lifepower4

Well, ascii can be represented in hex and there are some hex that can’t be printed like all the voltage values so everything is done in hex.
 
Well, ascii can be represented in hex and there are some hex that can’t be printed like all the voltage values so everything is done in hex.
Yeah, I get that... but as I read it I think you need to do math as ASCII values rather than just as Hex. Why the hell someone would think that is logical is beyond me.
 
My crude hack will do. Now I have to extend it to request from a number of packs and i'm set. It will talk over TCP serial port or directly connected (haven't tried) and also post to MQTT

Code:
Starting up...
Loading config.yaml
Connection Type: IP
MQTT connected with result code 0
Connecting to BMS...
trying to connect 192.168.10.218:8002
BMS socket connected
BMS Version: QT-YS00-16SV100A-V3.10
BMS Serial Number: 16778846
Cells:  16
V Cell1: 3331 mV
V Cell2: 3331 mV
V Cell3: 3331 mV
V Cell4: 3331 mV
V Cell5: 3331 mV
V Cell6: 3331 mV
V Cell7: 3331 mV
V Cell8: 3331 mV
V Cell9: 3331 mV
V Cell10: 3331 mV
V Cell11: 3331 mV
V Cell12: 3331 mV
V Cell13: 3331 mV
V Cell14: 3331 mV
V Cell15: 3331 mV
V Cell16: 3331 mV
I Pack: 0.0 A
I Remaining Capacity: 78.8 Ah
I Design Capacity: 97.8 Ah
Temp1: 20 C
Temp2: 20 C
Temp3: 19 C
Temp4: 19 C
MOS_Temp: 20 C
Ambient_Temp: 20 C
Pack 2, Cycles: 136
Pack 2, V Pack: 53.29 V
Pack 2, SOH: 97.8 %
SOC: 80.57 %
Script running....
HA Discovery Disabled
1684483703803.png
 
message me privately if someone wants to help test out the code. I updated it to support a list of pack IDs to get and they will all appear in MQTT.

1684565785651.png
 
@goldserve did you put the info on GitHub?
Btw, I am running a m5stickc with Tasmota to monitor my EG4LLv2 batteries. I use the Modbus TCP bridge and query the data and publish from another machine (the one that runs HA). The code is on GitHub at https://github.com/gonzalop/wombatt (screenshot and HA dashboard YAML here). It supports Modbus RTU, Modbus TCP and direct serial connection to the batteries. For inverters, I use the same tool but through a TCP to RS232 bridge running on an Atom lite.

Adding support for lifepower4 should be straightforward, but I would need someone who is willing and able to test things (nothing destructive, the monitoring command only issues 'read register' Modbus commands).

1000009751.jpg

The pic shows the M5Stick with an RS485 hat, and 2 atoms with the RS232 interface, one for each inverter, and a USB hub powered by a small UPS. The RS485 hat is connected to a wago where all the batteries RS485 wires are plugged into.
 
Last edited:
I have a fork of goldserve master branch minor tweaks for my environment and changes to the HA discovery I am using this devices and the script runs in a docker container619v5umsDxL._AC_SL1100_.jpg
 
Btw, I am running a m5stickc with Tasmota to monitor my EG4LLv2 batteries. I use the Modbus TCP bridge and query the data and publish from another machine (the one that runs HA). The code is on GitHub at https://github.com/gonzalop/wombatt (screenshot and HA dashboard YAML here). It supports Modbus RTU, Modbus TCP and direct serial connection to the batteries. For inverters, I use the same tool but through a TCP to RS232 bridge running on an Atom lite.

Adding support for lifepower4 should be straightforward, but I would need someone who is willing and able to test things (nothing destructive, the monitoring command only issues 'read register' Modbus commands).

View attachment 176700

The pic shows the M5Stick with an RS485 hat, and 2 atoms with the RS232 interface, one for each inverter, and a USB hub powered by a small battery. The RS485 hat is connected to a wago where all the batteries RS485 wires are plugged into.
I am down to test
 
Back
Top