switching from solar-1F to smart leaves 2nd contactor on 1F

[jonkerj]

Describe the bug
I'm using the second contactor to switch between 1F/3F, am using a switch to switch between solar/smart, and have configured contactor 2 as "solar off" (which means I'm always charging 1F in solar mode). When I switch from solar to smart, I'd expect to charge at 3F, but often (or maybe always) it will charge at "Smart-1F".

I think I got out of this situation a few times by re-plugging the car, but I recall at least one occasion where I head to reset the smartevse in order to get back in Smart-3F.

Upload your config

{
  "version": "v3.7.4",
  "serialnr": REDACTED,
  "mode": "SOLAR",
  "mode_id": 2,
  "car_connected": true,
  "wifi": {
    "status": "WL_CONNECTED",
    "ssid": "REDACTED",
    "rssi": -70,
    "bssid": "REDACTED"
  },
  "evse": {
    "temp": 27,
    "temp_max": 65,
    "connected": true,
    "access": true,
    "mode": 2,
    "loadbl": 0,
    "pwm": 264,
    "custombutton": false,
    "solar_stop_timer": 0,
    "state": "Connected to EV",
    "state_id": 1,
    "error": "None",
    "error_id": 0,
    "rfid": "Not Installed"
  },
  "settings": {
    "charge_current": 155,
    "override_current": 0,
    "current_min": 6,
    "current_max": 16,
    "current_main": 25,
    "current_max_circuit": 16,
    "current_max_sum_mains": 600,
    "max_sum_mains_time": 0,
    "solar_max_import": 0,
    "solar_start_current": 4,
    "solar_stop_time": 10,
    "enable_C2": "Solar Off",
    "mains_meter": "Sensorbox",
    "starttime": 0,
    "stoptime": 0,
    "repeat": 0,
    "lcdlock": 0
  },
  "mqtt": {
    "host": "REDACTED",
    "port": 31883,
    "topic_prefix": "REDACTED",
    "username": "",
    "password_set": false,
    "status": "Disconnected"
  },
  "ocpp": {
    "mode": "Disabled",
    "backend_url": "",
    "cb_id": "",
    "auth_key": "",
    "auto_auth": "Disabled",
    "auto_auth_idtag": "",
    "status": "Disconnected"
  },
  "home_battery": {
    "current": 0,
    "last_update": 0
  },
  "ev_meter": {
    "description": "Disabled",
    "address": 12,
    "import_active_power": 0,
    "total_kwh": 0,
    "charged_kwh": 0,
    "currents": {
      "TOTAL": 0,
      "L1": 0,
      "L2": 0,
      "L3": 0
    },
    "import_active_energy": 0,
    "export_active_energy": 0
  },
  "mains_meter": {
    "import_active_energy": 0,
    "export_active_energy": 0
  },
  "phase_currents": {
    "TOTAL": -144,
    "L1": -39,
    "L2": -54,
    "L3": -51,
    "last_data_update": 1747317852,
    "original_data": {
      "TOTAL": -144,
      "L1": -39,
      "L2": -54,
      "L3": -51
    }
  },
  "backlight": {
    "timer": 0,
    "status": "OFF"
  },
  "color": {
    "off": {
      "R": 0,
      "G": 0,
      "B": 0
    },
    "normal": {
      "R": 0,
      "G": 255,
      "B": 0
    },
    "smart": {
      "R": 0,
      "G": 255,
      "B": 0
    },
    "solar": {
      "R": 255,
      "G": 170,
      "B": 0
    },
    "custom": {
      "R": 0,
      "G": 0,
      "B": 255
    }
  }
}

Upload a debug log
There is a car charging for a while now, so I cannot flash/reboot the unit at the moment, if this is needed for further analysis, please tell me and I'll do so.

To Reproduce
Steps to reproduce the behavior:

1. Configure unit to switch between Smart and Solar
2. configure C2 to "solar off"
3. cycle between modes

Screenshots
n/a

[dingo35]

The C2 contactor cannot just switch on and off during a charging session; some EVs dont like it, and it isnt following the ISO/IEC standards.

So the CONTACTOR2 setting is taken into account when starting a session.
So in your case, do Solar-Off-Smart and the session will be properly ended and restarted with the right C2 setting taken into account.

[mstegen]

I use the same setup, charge on 1P on Solar, and charge 3P when in Smart mode.
I don't have any issues. The EVSE stops 1P charging, and starts charging at 3 phases when switching from Solar -> Smart.

However, i did notice that the display does sometimes keep telling that it's charging at 1P, while in fact it is actually charging at 3 Phases.
Could that be the issue?