Update personal smart charging preferences. Selecting the charger_electricity_rate type assigns the submitted electricityRateId to the charge point.

Only two payloads remove the charge point's electricity rate, and both are subject to the 409 conflict described below. Sending preferences.trackElectricityCosts as null or as an empty object on user_controlled_schedule dissociates a rate that tracking electricity costs had created, while the request is handled. Leaving the charge point with no dynamic-price integration (octopus_agile, octopus_go, nordpool) while its current rate was created by one unlinks that rate asynchronously, after the response. Switching away from charger_electricity_rate to another type, and sending enabled: false, both leave the assigned rate in place.

The update is rejected with 409 while removing the electricity rate would leave a reimbursement policy that resolves the rate from the charge point without a rate, whether the payload clears preferences.trackElectricityCosts or leaves no dynamic-price integration. The whole request is rejected: the submitted preferences are not stored, and the charge point keeps both its electricity rate and the dynamic-price integration the payload would have removed. Submitting charger_electricity_rate with a different electricityRateId replaces the rate and is allowed. The conflict clears only when the configuration changes: detach the policy, or keep an electricity rate on the charge point.