Updates editable grid code parameters and settings for the charger identified by evseId.

This is a partial update: included fields are changed, omitted or null fields stay unchanged.

Rules:

• evseId must use format NOZAPE<serial>, for example NOZAPEZPR000090.

• At least one editable field must be provided.

• GET metadata contains all known fields; fields with editable: false are read-only for PUT.

• Unknown, read-only, out-of-range, and invalid-step fields return 400.

• Do not PUT a full GET response back unchanged; remove read-only fields first.

Example request

{
  "fuse_limit": 32,
  "dso_max_export_limit": 16,
  "grid_code_settings": {
    "v_min_normal": 0.85,
    "f_min_normal": 49.0,
    "threshold_over_frequency": 50.2
  }
}

Validation examples

Valid examples:

• f_min_normal: 49.0

• max_under_frequency: 49.8

• under_frequency2_time: 0.1

• restore_time_after_fault_rt: 60

Invalid examples:

• max_under_frequency: 49.85 - because the step is 0.1

• under_frequency2_time: 0.05 - because the minimum is 0.1

• under_frequency2_time: 5.1 - because the maximum is 5.0

• restore_time_after_fault_rt: 60.5 - because it is an integer field

• f_max_normal - because it is returned by GET but is read-only for PUT

Error response example

{
  "type": "https://tools.ietf.org/html/rfc9110#section-15.5.1",
  "title": "One or more validation errors occurred.",
  "status": 400,
  "errors": {
    "grid_code_settings.max_under_frequency": [
      "Field must use a step of 0.1."
    ]
  }
}

Editable top-level parameters

Editable grid code settings

---

Normal operating range

---

Ride-through

---

Protection

---

Automatic reconnection

---

Active power response to over-frequency (LFSM-O)

---

Active power response to under-frequency (LFSM-U)

---

Active power response to overvoltage

---

Reactive power control