Updates a controller
Updates a controller. Required permission: asset:controllers:update
Authorizations
OAuth2 Bearer Authorization
Path Parameters
UUID of the Controller
^[a-f0-9]{8}\-[a-f0-9]{4}\-4[a-f0-9]{3}\-[89ab][a-f0-9]{3}\-[a-f0-9]{12}$Body
Updates a controller. Required permission: asset:controllers:update
Controls whether OCPP message logging is enabled for this controller. When enabled, all messages exchanged between the controller and the ChargeCloud backend are recorded.
Indicates whether fair-mode load balancing is enabled for this controller. When active, available power is distributed evenly across all connected charge points
The software type used by this controller, selected per manufacturer. This information is required for firmware update management and must match the actual hardware configuration.
mennekes, mennekes_ecu, mennekes_amtron_non_eichrecht, mennekes_amedio_eichrecht, mennekes_amedio_non_eichrecht, mennekes_4you_500, mennekes_4business_700, mennekes_4business_700_eichrecht, nidec, ebg, phoenix, ecotap, abb, abb_terra_ac, alfen, amperfied, ampure, hubject, kathrein, keba, kostad_sissy2, heliox, innogy, ochp, ebee, enercharge, chargeamps, schneiderelectric, tritium, walther, vinci_proxy, vestel, volkswagen, chargehere, schrack, ebemobility, kostad, circontrol, eluminocity, abl, abl_em4, bauer_gen3, bauer_gen4, gewiss, getpower, delta, photon, porsche, powerjames, ads_tec, siemens, siemens_sicharge_d, smight, aixacct, alpitronic, stoehr, meenergy, whbcharging, starchargeaurora, compleo_solo, evboxdc, evboxliviqo, unknown, smappee, hager_witty_share, hager_witty_park, hager_witty_pro, zaptec, peblar, rzb, kempower, spelsberg "ABB"
The name of the controller, which must exactly match the chargeBoxIdentity configured on the physical device. Avoid mixed case, umlauts, special characters, or spaces. Use underscores instead. Maximum recommended length is 20 characters per the OCPP specification.
50The protocol and transport type used for communication between the controller and the ChargeCloud backend (e.g. OCPP 1.6 JSON, OCPP 2.0.1, or manufacturer-specific protocols such as MENNEKES_BINARY). Must match the configuration on the physical device.
ocpp_1_5, ocpp_1_6_soap, ocpp_1_6_json, ocpp_1_6_json_v2, ocpp_201_json The mobile network standard used by the controller's SIM card for data transmission (e.g., GSM, LTE).
DSL, GSM, WLAN The hardware model designation of the charging station. Can be found on the purchase receipt, in the station's documentation, or via the serial number in the boot notification.
20Indicates whether the controller communicates with the backend over an SSL-encrypted connection. Not required for OCPP 1.6 JSON connections; mandatory for all other backend communication types.
The IP address used to reach the controller. If an ICC-ID is provided, this value is assigned automatically from the linked SIM card configuration.
The DNS hostname of the controller, used as an alternative to a static IP address for backend connectivity.
The IP port on which the controller accepts incoming connections. Required for direct IP-based communication setups.
The port used when the controller communicates through a proxy server. Only relevant in network environments where direct connections are not available.
The name of the hardware manufacturer of the controller. Used for internal documentation and device management.
The mobile phone number associated with the controller's SIM card.
25The Integrated Circuit Card Identifier (ICC-ID) of the SIM card installed in the controller. When set, the system automatically assigns the corresponding IP address to the controller.
25The International Mobile Subscriber Identity (IMSI) of the SIM card.
30The International Mobile Equipment Identity (IMEI) of the controller's modem.
30A label for the SIM card installed in the controller.
50The RADIUS authentication password associated with the controller's SIM card. Required in network environments that use RADIUS-based access control.
50The PIN code of the SIM card installed in the controller. Required to unlock the SIM card on boot if PIN protection is enabled.
5The PUK (Personal Unblocking Key) of the SIM card. Used to unlock the SIM card if it has been blocked after multiple incorrect PIN attempts.
8An optional override for the global heartbeat interval, in seconds. Defines how frequently the controller sends a heartbeat signal to the backend. The recommended value is 900 seconds (every 15 minutes). Min: 60, Max: 7200. Note: not applicable for OCPP 1.6 JSON controllers.
60 <= x <= 7200An optional override for the global meter values interval, in seconds. Defines how frequently the controller transmits energy meter readings to the backend. Min: 60, Max: 7200.
60 <= x <= 7200An optional alternative FTP server address used for firmware update delivery. If not set, the system uses the globally configured default FTP host.
55The manufacturer-assigned serial number of the controller hardware.
16The manufacturer's article or part number for this controller model.
16A list of RFID UIDs that are explicitly authorized to use the charge points connected to this controller. Only relevant when whitelist_only is enabled. Only cards whose UIDs appear in this list will be granted access.
Response
Controller edited
Controller