Must inverter ESPHome configuration for ESP32

inverter-monitor.yaml

substitutions:
  inverter_id: inverter
  updates: 5s
  api_key: xxx
  ota_password: xxx

esphome:
  name: inverter-monitor
  comment: "Inverter monitor"

esp32:
  board: esp32dev
  framework:
    type: esp-idf

wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password

captive_portal:

logger:
  level: DEBUG

api:
  encryption:
    key: ${api_key}

ota:
  password: ${ota_password}

uart:
  - id: uart_inverter
    baud_rate: 19200
    tx_pin: GPIO19
    rx_pin: GPIO18
    stop_bits: 1
    parity: NONE
    data_bits: 8
    debug:
      direction: BOTH
      dummy_receiver: false

modbus:
  - id: modbus_inverter
    uart_id: uart_inverter
    send_wait_time: 200ms

modbus_controller:
  - id: must_inverter
    address: 0x04
    modbus_id: modbus_inverter
    command_throttle: 200ms
    setup_priority: -10
    update_interval: ${updates}

sensor:
  # charger sensors
  - platform: modbus_controller
    modbus_controller_id: must_inverter
    address: 15201
    name: "PV Charger Workstate"
    register_type: holding

  - platform: modbus_controller
    modbus_controller_id: must_inverter
    address: 15202
    name: "PV Charger MPPT state"
    register_type: holding

  - platform: modbus_controller
    modbus_controller_id: must_inverter
    address: 15203
    name: "PV Charger Charging state"
    register_type: holding
    
  - platform: modbus_controller
    modbus_controller_id: must_inverter
    address: 15205
    name: "PV Charger Voltage"
    register_type: holding
    unit_of_measurement: "V"
    accuracy_decimals: 1
    icon: mdi:sine-wave
    filters:
      multiply: 0.1

  - platform: modbus_controller
    modbus_controller_id: must_inverter
    address: 15206
    name: "PV Charger Battery voltage"
    register_type: holding
    unit_of_measurement: "V"
    accuracy_decimals: 1
    icon: mdi:sine-wave
    filters:
      multiply: 0.1

  - platform: modbus_controller
    modbus_controller_id: must_inverter
    address: 15207
    name: "PV Charger Current"
    register_type: holding
    unit_of_measurement: "A"
    accuracy_decimals: 1
    icon: mdi:current-dc
    filters:
      multiply: 0.1

  - platform: modbus_controller
    modbus_controller_id: must_inverter
    address: 15208
    register_type: holding
    name: "PV Charger power"
    unit_of_measurement: "W"
    accuracy_decimals: 1
    icon: mdi:flash
  
  - platform: modbus_controller
    modbus_controller_id: must_inverter
    address: 15209
    register_type: holding
    name: "PV Charger Radiator temp"
    unit_of_measurement: "°C"
    accuracy_decimals: 1
    icon: mdi:temperature-celsius

  # - platform: modbus_controller
  #   modbus_controller_id: must_inverter
  #   address: 15210
  #   register_type: holding
  #   name: "PV Charger External temp"
  #   unit_of_measurement: "°C"
  #   accuracy_decimals: 1
  #   icon: mdi:temperature-celsius

  - platform: modbus_controller
    modbus_controller_id: must_inverter
    address: 15212
    register_type: holding
    name: "PV Relay"
    icon: mdi:electric-switch

  - platform: modbus_controller
    modbus_controller_id: must_inverter
    address: 15217
    register_type: holding
    id: charger_total_mwh
    internal: true

  - platform: modbus_controller
    modbus_controller_id: must_inverter
    address: 15218
    register_type: holding
    id: charger_total_kwh
    internal: true
    filters:
      multiply: 0.1

  - platform: template
    name: "PV Charger Accumulated charger power"
    unit_of_measurement: kWh
    lambda: !lambda 'return (id(charger_total_mwh).state * 1000.0 + id(charger_total_kwh).state );'
    accuracy_decimals: 1
  
  - platform: modbus_controller
    modbus_controller_id: must_inverter
    address: 15219
    register_type: holding
    name: "PV Charger Accumulated day"
    unit_of_measurement: "W"
    accuracy_decimals: 1
    icon: mdi:flash

  - platform: modbus_controller
    modbus_controller_id: must_inverter
    address: 15220
    register_type: holding
    name: "PV Charger Accumulated hour"
    unit_of_measurement: "W"
    accuracy_decimals: 1
    icon: mdi:flash

  - platform: modbus_controller
    modbus_controller_id: must_inverter
    address: 15221
    register_type: holding
    name: "PV Charger Accumulated minute"
    unit_of_measurement: "W"
    accuracy_decimals: 1
    icon: mdi:flash

# inverter sensors
  - platform: modbus_controller
    modbus_controller_id: must_inverter
    address: 25201
    register_type: holding
    name: "Inverter Work state"

  - platform: modbus_controller
    modbus_controller_id: must_inverter
    address: 25205
    name: "Inverter Battery Voltage"
    register_type: holding
    unit_of_measurement: "V"
    accuracy_decimals: 1
    icon: mdi:sine-wave
    filters:
      multiply: 0.1

  - platform: modbus_controller
    modbus_controller_id: must_inverter
    address: 25206
    name: "Inverter Voltage"
    register_type: holding
    unit_of_measurement: "V"
    accuracy_decimals: 1
    icon: mdi:sine-wave
    filters:
      multiply: 0.1

  - platform: modbus_controller
    modbus_controller_id: must_inverter
    address: 25207
    name: "Inverter Grid voltage"
    register_type: holding
    unit_of_measurement: "V"
    accuracy_decimals: 1
    icon: mdi:sine-wave
    filters:
      multiply: 0.1

  - platform: modbus_controller
    modbus_controller_id: must_inverter
    address: 25207
    name: "Inverter Grid voltage"
    register_type: holding
    unit_of_measurement: "V"
    accuracy_decimals: 1
    icon: mdi:sine-wave
    filters:
      multiply: 0.1

  - platform: modbus_controller
    modbus_controller_id: must_inverter
    address: 25208
    name: "Inverter BUS Voltage"
    register_type: holding
    unit_of_measurement: "V"
    accuracy_decimals: 1
    icon: mdi:sine-wave
    filters:
      multiply: 0.1

  - platform: modbus_controller
    modbus_controller_id: must_inverter
    address: 25209
    name: "Inverter Control current"
    register_type: holding
    unit_of_measurement: "A"
    accuracy_decimals: 1
    icon: mdi:current-dc
    filters:
      multiply: 0.1

  - platform: modbus_controller
    modbus_controller_id: must_inverter
    address: 25210
    name: "Inverter Current"
    register_type: holding
    unit_of_measurement: "A"
    accuracy_decimals: 1
    icon: mdi:current-dc
    filters:
      multiply: 0.1

  - platform: modbus_controller
    modbus_controller_id: must_inverter
    address: 25211
    name: "Inverter Grid current"
    register_type: holding
    unit_of_measurement: "A"
    accuracy_decimals: 1
    icon: mdi:current-ac
    filters:
      multiply: 0.1

  - platform: modbus_controller
    modbus_controller_id: must_inverter
    address: 25212
    name: "Inverter Load current"
    register_type: holding
    unit_of_measurement: "A"
    accuracy_decimals: 1
    icon: mdi:current-ac
    filters:
      multiply: 0.1

  - platform: modbus_controller
    modbus_controller_id: must_inverter
    address: 25213
    name: "Inverter Power"
    register_type: holding
    unit_of_measurement: "W"
    accuracy_decimals: 1
    icon: mdi:flash

  - platform: modbus_controller
    modbus_controller_id: must_inverter
    address: 25214
    name: "Inverter Grid power"
    register_type: holding
    unit_of_measurement: "W"
    accuracy_decimals: 1
    value_type: S_WORD
    icon: mdi:flash

  - platform: modbus_controller
    modbus_controller_id: must_inverter
    address: 25215
    name: "Inverter Load power"
    register_type: holding
    unit_of_measurement: "W"
    accuracy_decimals: 1
    icon: mdi:flash

  - platform: modbus_controller
    modbus_controller_id: must_inverter
    address: 25216
    name: "Inverter System load"
    register_type: holding
    unit_of_measurement: "%"
    accuracy_decimals: 1
    icon: mdi:flash

    # MOST INFO

  - platform: modbus_controller
    modbus_controller_id: must_inverter
    address: 25233
    register_type: holding
    name: "Inverter AC radiator temp"
    accuracy_decimals: 1
    unit_of_measurement: "°C"
    icon: mdi:temperature-celsius

  - platform: modbus_controller
    modbus_controller_id: must_inverter
    address: 25234
    register_type: holding
    name: "Inverter Transformer temp"
    unit_of_measurement: "°C"
    accuracy_decimals: 1
    icon: mdi:temperature-celsius

  - platform: modbus_controller
    modbus_controller_id: must_inverter
    address: 25235
    register_type: holding
    name: "Inverter DC Radiator temp"
    unit_of_measurement: "°C"
    accuracy_decimals: 1
    icon: mdi:temperature-celsius

  - platform: modbus_controller
    modbus_controller_id: must_inverter
    address: 25237
    register_type: holding
    name: "Inverter Relay state"
    icon: mdi:electric-switch

  - platform: modbus_controller
    modbus_controller_id: must_inverter
    address: 25238
    register_type: holding
    name: "Inverter Relay state Grid"
    icon: mdi:electric-switch
    
  - platform: modbus_controller
    modbus_controller_id: must_inverter
    address: 25239
    register_type: holding
    name: "Inverter Relay state Load"
    icon: mdi:electric-switch
    
  - platform: modbus_controller
    modbus_controller_id: must_inverter
    address: 25240
    register_type: holding
    name: "Inverter Relay state NLine"
    icon: mdi:electric-switch

  - platform: modbus_controller
    modbus_controller_id: must_inverter
    address: 25241
    register_type: holding
    name: "Inverter Relay state DC"
    icon: mdi:electric-switch
    
  - platform: modbus_controller
    modbus_controller_id: must_inverter
    address: 25242
    register_type: holding
    name: "Inverter Relay state Earth"
    icon: mdi:electric-switch

# Inverter Accumulated discharge power
  - platform: modbus_controller
    modbus_controller_id: must_inverter
    address: 25247
    register_type: holding
    id: discharger_total_mwh
    internal: true

  - platform: modbus_controller
    modbus_controller_id: must_inverter
    address: 25248
    register_type: holding
    id: discharger_total_kwh
    internal: true
    filters:
      multiply: 0.1

  - platform: template
    name: "Accumulated discharger power"
    unit_of_measurement: kWh
    accuracy_decimals: 1
    lambda: !lambda 'return (id(discharger_total_mwh).state * 1000.0 + id(discharger_total_kwh).state);'

# Inverter Accumulated buy power
  - platform: modbus_controller
    modbus_controller_id: must_inverter
    address: 25249
    register_type: holding
    id: buy_mwh
    internal: true
  
  - platform: modbus_controller
    modbus_controller_id: must_inverter
    address: 25250
    register_type: holding
    id: buy_kwh
    internal: true
    filters:
      multiply: 0.1
  
  - platform: template
    name: "Accumulated buy power"
    unit_of_measurement: kWh
    lambda: |-
     return (id(buy_mwh).state * 1000.0 + id(buy_kwh).state);
    accuracy_decimals: 1

# Inverter Accumulated sell power
  - platform: modbus_controller
    modbus_controller_id: must_inverter
    address: 25251
    register_type: holding
    id: sell_mwh

  - platform: modbus_controller
    modbus_controller_id: must_inverter
    address: 25252
    register_type: holding
    id: sell_kwh
    filters:
      multiply: 0.1

  - platform: template
    name: "Accumulated sell power"
    unit_of_measurement: kWh
    accuracy_decimals: 1
    lambda: !lambda return (id(sell_mwh).state * 1000.0 + id(sell_kwh).state);

# Inverter Accumulated load power
  - platform: modbus_controller
    modbus_controller_id: must_inverter
    address: 25253
    register_type: holding
    id: load_mwh
    internal: True

  - platform: modbus_controller
    modbus_controller_id: must_inverter
    address: 25254
    register_type: holding
    id: load_kwh
    internal: True
    filters:
      multiply: 0.1
  
  - platform: template
    name: "Accumulated load power"
    unit_of_measurement: kWh
    accuracy_decimals: 1
    lambda: !lambda return (id(load_mwh).state * 1000.0 + id(load_kwh).state);

  - platform: modbus_controller
    modbus_controller_id: must_inverter
    address: 25273
    register_type: holding
    value_type: S_WORD
    name: "Inverter Battery power"
    unit_of_measurement: "W"
    accuracy_decimals: 1
    icon: mdi:flash

  - platform: modbus_controller
    modbus_controller_id: must_inverter
    address: 25274
    register_type: holding
    value_type: S_WORD
    name: "Inverter Battery current"
    unit_of_measurement: "A"
    accuracy_decimals: 1
    icon: mdi:current-dc

  - platform: modbus_controller
    modbus_controller_id: must_inverter
    address: 25275
    register_type: holding
    value_type: S_WORD
    name: "Inverter Battery grade"
    unit_of_measurement: "V"
    icon: mdi:alpha-V

  - platform: modbus_controller
    modbus_controller_id: must_inverter
    address: 25277
    register_type: holding
    name: "Inverter Rated power"
    unit_of_measurement: "W"
    accuracy_decimals: 1
    icon: mdi:flash


select:
  - platform: modbus_controller
    modbus_controller_id: must_inverter
    id: energy_use_mode
    name: "Inverter Energy use mode (parameter 00)"
    address: 20109
    optionsmap:
      "SBU (Solar/battery/utility)": 1
      "SUB (Solar/utility/battery)": 2
      "UTI (Utility only)": 3
      "SOL (Solar only)": 4

  - platform: modbus_controller
    modbus_controller_id: must_inverter
    id: charger_source_priority
    name: "Inverter Charger source priority (parameter 10)"
    address: 20143
    optionsmap:
      "CSO (Solar first)": 0
      "SNU (Solar and utility)": 2
      "OSO (Solar only)": 3

  - platform: modbus_controller
    modbus_controller_id: must_inverter
    address: 20111
    id: inverter_ac_input_voltage_range
    name: "Inverter AC input voltage range (02)"
    optionsmap:
      "VDE (184-253VAC)": 0
      "UPS (170-280VAC)": 1
      "APL (90-280VAC)": 2
      "GEN (Generator)": 3


number:
  - platform: modbus_controller
    id: batt_float_voltage
    name: "PV Charger Float voltage"
    unit_of_measurement: "V"
    address: 10103
    value_type: U_WORD
    multiply: 10

  - platform: modbus_controller
    id: batt_absorb_voltage
    name: "PV Charger Absorb voltage"
    unit_of_measurement: "V"
    address: 10104
    value_type: U_WORD
    multiply: 10

  - platform: modbus_controller
    id: batt_stop_dischg
    name: "Inverter Battery stop discharging voltage"
    unit_of_measurement: "V"
    address: 20118
    value_type: U_WORD
    lambda: "return x * 0.1; "
    write_lambda: |-
      return x * 10 ;

  - platform: modbus_controller
    id: batt_stop_chg
    name: "Inverter Battery stop charging voltage"
    unit_of_measurement: "V"
    address: 20119
    value_type: U_WORD
    multiply: 10

  - platform: modbus_controller
    id: batt_low_voltage
    name: "Inverter Battery low voltage"
    unit_of_measurement: "V"
    address: 20127
    value_type: U_WORD
    multiply: 10

  - platform: modbus_controller
    id: batt_high_voltage
    name: "Inverter Battery high voltage"
    unit_of_measurement: "V"
    address: 20128
    value_type: U_WORD
    multiply: 10

  - platform: modbus_controller
    id: solar_charger_current
    name: "Inverter Charger current"
    unit_of_measurement: "A"
    address: 20132
    value_type: U_WORD
    multiply: 10

Tested with PV18 series.

In a couple of weeks I'm going to try it with a PV18-3024 VMPK.
I have a question. What pins of the RS232 cable I need to conect to gpio18 and gpio19?
Wouldn't it be possible to connect to the inverter via Bluetooth?

What pins of the RS232 cable

The connector on the inverter side is RJ-45 (8P8C). It uses RS485 (Modbus) for communication, so you need an additional module called RS485 to UART. You should check the manual for your inverter to be sure for pinout, but in my case the 1 pin of RJ-45 is RS485-B, the 2 pin is RS485-A and the 3 pin is GND.

conect to gpio18 and gpio19

I used it in my ESP, your ESP version could differ, so you can use any other GPIO (preferably with hardware uart). Check the pinout for your ESP variant.

Wouldn't it be possible to connect to the inverter via Bluetooth?

I don't know anything about Bluetooth in Must inverters. If it exists somewhere, it may use a different protocol, so it's not compatible with the current configuration.

Ok, many thanks!!!

I am getting this error,,

*** [.pioenvs/inverter-monitor/src/esphome/components/modbus_controller/text_sensor/modbus_textsensor.o] Source src/esphome/components/modbus_controller/text_sensor/modbus_textsensor.cpp' not found, needed by target .pioenvs/inverter-monitor/src/esphome/components/modbus_controller/text_sensor/modbus_textsensor.o'.

========================= [FAILED] Took 26.38 seconds =========================

any idea why ?

I am getting this error,,

*** [.pioenvs/inverter-monitor/src/esphome/components/modbus_controller/text_sensor/modbus_textsensor.o] Source src/esphome/components/modbus_controller/text_sensor/modbus_textsensor.cpp' not found, needed by target .pioenvs/inverter-monitor/src/esphome/components/modbus_controller/text_sensor/modbus_textsensor.o'.

========================= [FAILED] Took 26.38 seconds =========================

any idea why ?

idk. Try to clean the build files if you changed something before.
Also, try to update ESPHome to the latest version. I used this configuration a few days ago, and it works without any issues.

Thanks for the solution, i have tried clean build files and it worked :D

However now am unable to read any data and giving me the following error

[22:40:21][D][uart_debug:114]: >>> 04:03:3B:61:00:03:59:64
[22:40:21][D][uart_debug:114]: >>> 04:03:3B:61:00:03:59:64
[22:40:21][D][uart_debug:114]: >>> 04:03:3B:61:00:03:59:64
[22:40:22][D][uart_debug:114]: >>> 04:03:3B:61:00:03:59:64
[22:40:22][D][uart_debug:114]: >>> 04:03:3B:61:00:03:59:64
[22:40:22][D][modbus_controller:043]: Modbus command to device=4 register=0x3B61 countdown=0 no response received - removed from send queue
[22:40:22][D][uart_debug:114]: >>> 04:03:62:75:00:0C:4B:F8
[22:40:22][W][modbus_controller:136]: Duplicate modbus command found: type=0x3 address=10103 count=2
[22:40:22][W][modbus_controller:136]: Duplicate modbus command found: type=0x3 address=15205 count=5
[22:40:22][W][modbus_controller:136]: Duplicate modbus command found: type=0x3 address=15212 count=1
[22:40:22][W][modbus_controller:136]: Duplicate modbus command found: type=0x3 address=15217 count=5
[22:40:22][W][modbus_controller:136]: Duplicate modbus command found: type=0x3 address=20109 count=1
[22:40:22][W][modbus_controller:136]: Duplicate modbus command found: type=0x3 address=20111 count=1
[22:40:22][W][modbus_controller:136]: Duplicate modbus command found: type=0x3 address=20118 count=2
[22:40:22][W][modbus_controller:136]: Duplicate modbus command found: type=0x3 address=25205 count=12
[22:40:22][W][modbus_controller:136]: Duplicate modbus command found: type=0x3 address=25233 count=3
[22:40:22][W][modbus_controller:136]: Duplicate modbus command found: type=0x3 address=25237 count=6
[22:40:22][W][modbus_controller:136]: Duplicate modbus command found: type=0x3 address=25247 count=8
[22:40:22][W][modbus_controller:136]: Duplicate modbus command found: type=0x3 address=25273 count=3
[22:40:22][W][modbus_controller:136]: Duplicate modbus command found: type=0x3 address=25277 count=1
[22:40:22][W][component:214]: Component modbus_controller took a long time for an operation (0.08 s).
[22:40:22][W][component:215]: Components should block for at most 20-30ms.
[22:40:22][D][uart_debug:114]: >>> 04:03:62:75:00:0C:4B:F8
[22:40:23][D][uart_debug:114]: >>> 04:03:62:75:00:0C:4B:F8
[22:40:23][D][uart_debug:114]: >>> 04:03:62:75:00:0C:4B:F8
[22:40:23][D][uart_debug:114]: >>> 04:03:62:75:00:0C:4B:F8
[22:40:23][D][modbus_controller:043]: Modbus command to device=4 register=0x6275 countdown=0 no response received - removed from send queue
[22:40:23][D][uart_debug:114]: >>> 04:03:62:91:00:03:4B:CB
[22:40:23][D][uart_debug:114]: >>> 04:03:62:91:00:03:4B:CB
[22:40:24][D][uart_debug:114]: >>> 04:03:62:91:00:03:4B:CB
[22:40:24][D][uart_debug:114]: >>> 04:03:62:91:00:03:4B:CB
[22:40:24][D][uart_debug:114]: >>> 04:03:62:91:00:03:4B:CB
[22:40:24][D][modbus_controller:043]: Modbus command to device=4 register=0x6291 countdown=0 no response received - removed from send queue
[22:40:24][D][uart_debug:114]: >>> 04:03:62:95:00:06:CA:09
[22:40:25][D][uart_debug:114]: >>> 04:03:62:95:00:06:CA:09
[22:40:25][D][uart_debug:114]: >>> 04:03:62:95:00:06:CA:09
[22:40:25][D][uart_debug:114]: >>> 04:03:62:95:00:06:CA:09
[22:40:25][D][uart_debug:114]: >>> 04:03:62:95:00:06:CA:09
[22:40:25][D][modbus_controller:043]: Modbus command to device=4 register=0x6295 countdown=0 no response received - removed from send queue
[22:40:25][D][uart_debug:114]: >>> 04:03:62:9F:00:08:6B:CF
[22:40:26][D][uart_debug:114]: >>> 04:03:62:9F:00:08:6B:CF
[22:40:26][D][uart_debug:114]: >>> 04:03:62:9F:00:08:6B:CF
[22:40:26][D][uart_debug:114]: >>> 04:03:62:9F:00:08:6B:CF
[22:40:26][D][uart_debug:114]: >>> 04:03:62:9F:00:08:6B:CF
[22:40:26][D][modbus_controller:043]: Modbus command to device=4 register=0x629F countdown=0 no response received - removed from send queue
[22:40:26][D][uart_debug:114]: >>> 04:03:3B:65:00:05:98:A7
[22:40:27][D][uart_debug:114]: >>> 04:03:3B:65:00:05:98:A7
[22:40:27][D][uart_debug:114]: >>> 04:03:3B:65:00:05:98:A7
[22:40:27][D][uart_debug:114]: >>> 04:03:3B:65:00:05:98:A7
[22:40:27][W][modbus_controller:136]: Duplicate modbus command found: type=0x3 address=10103 count=2
[22:40:27][W][modbus_controller:136]: Duplicate modbus command found: type=0x3 address=15201 count=3
[22:40:27][W][modbus_controller:136]: Duplicate modbus command found: type=0x3 address=15205 count=5
[22:40:27][W][modbus_controller:136]: Duplicate modbus command found: type=0x3 address=15212 count=1
[22:40:27][W][modbus_controller:136]: Duplicate modbus command found: type=0x3 address=15217 count=5
[22:40:27][W][modbus_controller:136]: Duplicate modbus command found: type=0x3 address=20109 count=1
[22:40:27][W][modbus_controller:136]: Duplicate modbus command found: type=0x3 address=20111 count=1
[22:40:27][W][modbus_controller:136]: Duplicate modbus command found: type=0x3 address=20118 count=2
[22:40:27][W][modbus_controller:136]: Duplicate modbus command found: type=0x3 address=20127 count=2
[22:40:27][W][modbus_controller:136]: Duplicate modbus command found: type=0x3 address=20132 count=1
[22:40:27][W][modbus_controller:136]: Duplicate modbus command found: type=0x3 address=20143 count=1
[22:40:27][W][modbus_controller:136]: Duplicate modbus command found: type=0x3 address=25201 count=1
[22:40:27][W][modbus_controller:136]: Duplicate modbus command found: type=0x3 address=25273 count=3
[22:40:27][W][modbus_controller:136]: Duplicate modbus command found: type=0x3 address=25277 count=1
[22:40:27][W][component:214]: Component modbus_controller took a long time for an operation (0.09 s).
[22:40:27][W][component:215]: Components should block for at most 20-30ms.
[22:40:27][D][uart_debug:114]: >>> 04:03:3B:65:00:05:98:A7
[22:40:27][D][modbus_controller:043]: Modbus command to device=4 register=0x3B65 countdown=0 no response received - removed from send queue
[22:40:28][D][uart_debug:114]: >>> 04:03:3B:6C:00:01:49:66
[22:40:28][D][uart_debug:114]: >>> 04:03:3B:6C:00:01:49:66
[22:40:28][D][uart_debug:114]: >>> 04:03:3B:6C:00:01:49:66
[22:40:28][D][uart_debug:114]: >>> 04:03:3B:6C:00:01:49:66
[22:40:28][D][uart_debug:114]: >>> 04:03:3B:6C:00:01:49:66
[22:40:28][D][modbus_controller:043]: Modbus command to device=4 register=0x3B6C countdown=0 no response received - removed from send queue

@omarmeleis Try to swap RX/TX and/or A/B on the RS485 converter

Already tried that,, i will try another RS485 to UART board and update

Already tried that,, i will try another RS485 to UART board and update

I used this one, works ok:
https://www.aliexpress.com/item/1005001621746811.html

I also connected it to the USB port of the inverter. It uses the same RS485 (at least on the PV1800 series, as far as I know), but additionally has 5V to power the ESP and adapter, so you don't need to use an additional power supply.

So, in my case, 5V connected to the ESP, GND connected to the RS485 converter board GND and to the GND of the ESP, and middle USB pins to A/B (not sure which one is which, try to swap if it does not work). The 3.3V from the ESP connected to the other side of the RS485 converter board to the VCC, RX/TX to the ESP and swapped, and the ESP GND to the board GND.

i am using this exact module :D as the one you are using,,,,, but getting my A/B wires not from the usb port but from the ethernet jack,, where pin 1 in B and pin 2 is A

I am using a 3k must Pv1800 series

I will try using the pins from the USB port now and update u