syssi / esphome-pipsolar

ESPHome component to monitor and control a pipsolar inverter via RS232
Apache License 2.0
78 stars 36 forks source link

problem with calling current_max_charging_current #32

Open marcinbc opened 1 year ago

marcinbc commented 1 year ago

Hi, I have a problem with calling the current_max_charging_current service, the current_max_ac_charging_current service on the same settings works great logs_rekuperator_upload.txt

marcinbc commented 1 year ago
output:
  - platform: pipsolar
    pipsolar_id: inverter0
    battery_recharge_voltage:
      id: inverter0_battery_recharge_voltage_out
  - platform: pipsolar
    pipsolar_id: inverter0
    current_max_ac_charging_current:
      id: current_max_ac_charging_current
  - platform: pipsolar
    pipsolar_id: inverter0
    current_max_charging_current:
      id: current_max_charging_current
  - platform: homeassistant
    name: "Solar 20A"
    entity_id: input_boolean.offgrid_20a_ladowanie_ac
    id: solar20A
    internal: false
#
    on_release:
      then:
        - output.pipsolar.set_level:
            id: current_max_ac_charging_current
            value: 20.0

  - platform: homeassistant
    name: "Solar 30A all"
    entity_id: input_boolean.offgrid_30a_ladowanie
    id: solar30A_all
    internal: false
    on_release:
#    on_press:
      then:
        - output.pipsolar.set_level:
            id: current_max_charging_current 
            value: 30.0
marcinbc commented 1 year ago

[21:58:10][D][number:054]: 'pvbrain_axpert_current_max_charging_current_number' - Setting number value [21:58:10][D][number:113]: New number value: 20.000000 [21:58:10][D][number:012]: 'pvbrain_axpert_current_max_charging_current_number': Sending state 20.000000 [21:58:10][D][pipsolar.output:015]: Will write: MCHGC020 out of value 20.000000 / 20 [21:58:10][D][pipsolar:856]: got command: MCHGC020 [21:58:10][D][pipsolar:847]: Command queued successfully: MCHGC020 with length 8 at position 2

[21:58:10][D][pipsolar:807]: Sending command from queue: MCHGC020 with length 8

[21:58:11][D][pipsolar:042]: response length for command OK [21:58:11][D][pipsolar:772]: checking crc on incoming message [21:58:11][D][pipsolar:775]: CRC OK [21:58:11][D][pipsolar:048]: command not successful

gio-dot commented 1 year ago

[21:58:10][D][number:054]: 'pvbrain_axpert_current_max_charging_current_number' - Setting number value [21:58:10][D][number:113]: New number value: 20.000000 [21:58:10][D][number:012]: 'pvbrain_axpert_current_max_charging_current_number': Sending state 20.000000 [21:58:10][D][pipsolar.output:015]: Will write: MCHGC020 out of value 20.000000 / 20 [21:58:10][D][pipsolar:856]: got command: MCHGC020 [21:58:10][D][pipsolar:847]: Command queued successfully: MCHGC020 with length 8 at position 2 [21:58:10][D][uart_debug:158]: >>> "MCHGC020\xD1u\r" [21:58:10][D][pipsolar:807]: Sending command from queue: MCHGC020 with length 8 [21:58:11][D][uart_debug:158]: <<< "(NAKss\r" [21:58:11][D][pipsolar:042]: response length for command OK [21:58:11][D][pipsolar:772]: checking crc on incoming message [21:58:11][D][pipsolar:775]: CRC OK [21:58:11][D][pipsolar:048]: command not successful

Hi, i have the same issue on my MPP Solar PIP 8048, but with command current_max_ac_charging_current. Did you manage to solve it? Can you share the whole esphome configuration? 2022-12-15 11_15_32-HA Virtual 3T 2022-12-15 11_14_58-HA Virtual 3T

As i said the command current_max_charging_current is working for me:

2022-12-15 11_37_36-HA Virtual 3T

gio-dot commented 1 year ago

Ok, i solved my issue.. look here: https://github.com/syssi/esphome-pipsolar/issues/41