pongo

This is fw they installed
MAX_7.2K_69.06.7z
Could you check, please?
They told me that this has 80A charge limit (against 120A of 88.02), has SoC % for parameters 12, 13, 29 when battery type <> USER.
Could you check, please?

Hello,
finally my supplier has updated my inverter firmware from 88.02 to 69.06 (DSP 28066) to solve 90V bug.
I will check next days if it truly solves this bug and let you know.
I requested also to have original 88.02, so should be patched, but not yet received.

Thanks, I confirm now it works

Would you share your code?

I implemented dynamic data from BMS to ModBus github/gianfrdp/esphome_yaml/jkbms-voltronic.simple.yaml.
EspHome reads relevant BMS data from MQTT and sends over RS485 ModBus RTU.
Tested reading values with a python script and it works. Now I'm going to attach it to inverter.
I cannot use esphome-jkbms and this implementation on the same ESP32 because esphome-jkbms use framework esp-idf, instead modbus-server
component I'm using is only compatible with framework arduino.
If I can port modbus-server to esp-idf, maybe I could use just one ESP32, without reading values from MQTT (another possible point of failure).
 
EDIT: I connected ESP32 to inverter, Axpert asks data, ESP32 responses but after some time goes in error 61 (communication lost).
Maybe I'm sending something wrong.
[15:12:58][I][ON_READ:187]: address=0x33, value=61 [15:12:58][D][uart_debug:114]: <<< 01:03:00:33:00:01:74:05 [15:12:58][D][uart_debug:114]: >>> 01:03:02:00:3D:79:95 This is from LIB protocol documentation:

But searching in another project I saw:

Response format is different:
| Slave Address | Function | Data Len n (1 byte) | n * bytes | CRC (2 bytes) |
vs
| Slave Address | Function | Data Len n (2 bytes) | 2 * n * bytes | CRC (2 bytes) |
 
Using "Modbus Slave" fot test:
DEBUG:pymodbus.transaction:Current transaction state - IDLE DEBUG:pymodbus.transaction:Running transaction 1 DEBUG:pymodbus.transaction:SEND: 0x1 0x3 0x0 0x33 0x0 0x1 0x74 0x5 DEBUG:pymodbus.client.sync:New Transaction state 'SENDING' DEBUG:pymodbus.transaction:Changing transaction state from 'SENDING' to 'WAITING FOR REPLY' DEBUG:pymodbus.transaction:Changing transaction state from 'WAITING FOR REPLY' to 'PROCESSING REPLY' DEBUG:pymodbus.transaction:RECV: 0x1 0x3 0x2 0x0 0x3d 0x79 0x95 DEBUG:pymodbus.framer.rtu_framer:Getting Frame - 0x3 0x2 0x0 0x3d seems response format ESP32 is sending is correct... so I don't understand why Voltronic reports error 61
jkbms-voltronic.simple.yaml

It needs to connect battery to see inverter asking modbus values. Now it works.
These are registers my Axpert Max 7200 is asking:
01:03:00:01:00:02:95:CB
01:03:00:33:00:01:74:05
01:03:00:34:00:02:85:C5
01:03:00:70:00:01:85:D1
01:03:00:71:00:01:D4:11
01:03:00:72:00:01:24:11
01:03:00:73:00:01:75:D1
01:03:00:74:00:01:C4:10
01:03:02:00:32:39:91
01:03:02:00:C0:B8:14
01:03:02:01:E0:B8:5C
01:03:02:01:F4:B8:53
01:03:02:02:44:B9:17
01:03:02:03:E8:B8:FA
01:03:04:00:04:45:C0:89:32
Continuing testing and trying to send BMS values
Thanks
 

@pongo ma sei italiano?

You have to attach an RS485/ttl to a ESP8266 (or better a ESP32), as said in previous posts.
Or use an all-in-one ESP32+RS485, for example m5stack atom lite RS485 (as I did) and install on it esphome custom rom.
But you have to read and learn how to do it: esphome is a custom rom project for ESPs born to integrate with HomeAssistant, but can work also stand-alone (webserver for sure works on ESP32).
You can use my yaml configuration file for ESPHome as reference.
This is how atom is connected to inverter (inverter also powers ESP32):

This is EspHome webserver on ESP, you can see values in real-time and also change parameters:

And this is HomeAssistant integration:

If you use esp8266 you can install esphome enabling web server and you can see data using a browser in real-time.
Or, alternatively, you can use tasmota compiling by yourself adding modbus support (harder way)

Solpiplog is for "MPP Solar" like inverters, non for ModBus ones
Different protocols (pip solar)

sensor: - platform: modbus_controller modbus_controller_id: easun name: "Battery Capacity of SOC" id: battery_capacity_soc register_type: holding address: 0x0100 unit_of_measurement: "%" value_type: U_WORD select: - platform: modbus_controller modbus_controller_id: easun id: output_priority name: "Output Priority" address: 0xE204 value_type: U_WORD optionsmap: "SOL": 0 "UTI": 1 "SBU": 2  

Hello,
Also I'm looking for easun SMX II 5.6 kW protocol.
Edit: I found that SMX II 5.6 is compatible with SRNE inverters protocol.
I tried https://github.com/shakthisachintha/SRNE-Hybrid-Inverter-Monitor
and it works. I tested with a raspberry pi connected to USB port.
I'm going to use Modbus protocol on EspHome on a ESP32(m5stack atom rs485) and add all needed registers and integrate into Home Assistant 
Regards