Update details of a user's solar inverter
Modify the data of a solar inverter related to a specific user under a specific organization, with a JSON payload.
Authorizations
The access token received from the authorization server in the OAuth 2.0 flow.
Path Parameters
The organization ID of the user's organization
The user ID of the user whom the solar inverter belongs to
The ID of the modified solar inverter
Body
20Optimize self consumption, Optimize grid balancing, Export all AT, AT_HOURLY, BE, CH, EE, DE_LU, HR, HU, IE_SEM, IT_CNOR, IT_CSUD, IT_NORD, IT_PUN, IT_SARD, IT_SICI, IT_SUD, PT, RO, SE_1, SE_2, SE_3, SE_4, UK When set, the device is considered deleted.
3000.0–1.0; saturates at 16 EV-charging bouts in 30 days
Response
OK
ok, warning, error, unknown ok, warning, error, unknown ok, warning, error, unknown The device's console health tone, and the only verdict a client should render: action_required when a partner-resolvable action is pending, else the worst of connection and monitoring, with not_steered for a healthy device nobody optimizes. Do not re-derive it from connection_status/monitoring_status/steering_status — those three are cue-blind and would report a device asking for reauthentication as healthy. The status filter on GET /org/{org_id}/devices and the tone counts on …/devices/summary grade the three statuses only, so a device with a pending action reads action_required here while being counted and filtered under its status tone.
good, warning, critical, not_steered False for an asset with no household load behind the meter
False for an asset with no on-site PV array
Deprecated — use GET /org/{org_id}/notifications/status for per-device-type counts, or GET /org/{org_id}/notifications/actions?device_id=… for the specifics. True when at least one action is pending against this device and the partner must take that action before the device can resume normal operation.
AT, AT_HOURLY, BE, CH, EE, DE_LU, HR, HU, IE_SEM, IT_CNOR, IT_CSUD, IT_NORD, IT_PUN, IT_SARD, IT_SICI, IT_SUD, PT, RO, SE_1, SE_2, SE_3, SE_4, UK PV array peak capacity in kWp inferred from observed solar production. Null until a supported fit is available; onboarding default assumptions are excluded.
20When set, the device is considered deleted.
2553001000.0–1.0; saturates at 16 EV-charging bouts in 30 days
URL to embeddable onboarding form
Base URL for authorizing with the Podero server
