PicoCharging

Gets the active charging data of a pico station

get/pico/charging/{id}

Request

  • Base URL: https://api.smart-me.com (the document declares no server; this is the origin it was published from)
  • URL: https://api.smart-me.com/pico/charging/{id}
  • Auth: one of:
    • OAuth 2 (authorization code, authorization URL /oauth/authorize, token URL /oauth/token; client credentials, token URL /oauth/token)
    • HTTP basic

Path parameters

idstring uuid required

Response

OK

state0 | 1 | 2 | 3 | 4 | 5 | 6 | 7

State of a (pico) charging station<p>Members: </p><ul><li><i>0</i> - Booting</li><li><i>1</i> - ReadyNoCarConnected</li><li><i>2</i> - ReadyCarConnected</li><li><i>3</i> - StartedWaitForCar</li><li><i>4</i> - Charging</li><li><i>5</i> - Installation</li><li><i>6</i> - Authorize</li><li><i>7</i> - Offline</li></ul>

activeChargingPowernumber double

The power of the active charging (in kW)

activeChargingEnergynumber double

The energy used by this active charging (in kWh)

durationinteger

The duration of this charging in seconds

valueDatestring date-time

The date of this values

maxAllowedChargingCurrentinteger

Max allowed charging current in A

minStationCurrentinteger

Min. current of the station in A

maxStationCurrentinteger

Max. current of the station in A

maxLoadmanagementGroupCurrentinteger

Max. current of the loadmanagement group of this station (if there is any) in A

maxDynamicCurrentinteger

Max. dynamic current (e.g. set over API or Modbus TCP) of this station or the loadmanagement group of the station if the station is in a group. in A

currentL1number double

The current on phase L1 in A

currentL2number double

The current on phase L2 in A

currentL3number double

The current on phase L3 in A

loadSheddingState0 | 1 | 2 | 3

Enumeration of the Load-Shedding state<p>Members: </p><ul><li><i>0</i> - MaxCurrent</li><li><i>1</i> - HalfCurrent</li><li><i>2</i> - MinCurrent</li><li><i>3</i> - NoCurrent</li></ul>

loadmanagementGroupNamestring nullable

The name of the loadmanagement group. Or string.empty if the station is not in a group

connectionMode0 | 1 | 2 | 3 | 4 | 5 | 6
<p>Members: </p><ul><li><i>0</i> - NetworkToCloudConnectionMode_NoConnection</li><li><i>1</i> - NetworkToCloudConnectionMode_DirectWiFiConnection</li><li><i>2</i> - NetworkToCloudConnectionMode_GPRSConnection</li><li><i>3</i> - NetworkToCloudConnectionMode_NBIotConnection</li><li><i>4</i> - NetworkToCloudConnectionMode_LteCatM1Connection</li><li><i>5</i> - NetworkToCloudConnectionMode_MeshWiFiConnection</li><li><i>6</i> - NetworkToCloudConnectionMode_MeshMobileConnection</li></ul>
rssiinteger

Received Signal Strength Indicator for the connection mode (wifi or mobile). -127 (min) to 0 (Max)

lastWarningOrError1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | 257 | 65535
<p>Members: </p><ul><li><i>1</i> - This event is reserved for a meter value datalogger entry</li><li><i>2</i> - The meter has been restarted</li><li><i>3</i> - We have power down on all phases. The meter shuts down</li><li><i>4</i> - The power has been disconnected from phase 1 on the meter.</li><li><i>5</i> - The power has been disconnected from phase 2 on the meter.</li><li><i>6</i> - The power has been disconnected from phase 3 on the meter.</li><li><i>7</i> - The meter has detected a "open cover"</li><li><i>8</i> - The meter has detected a magnetic field. If this occurs, the meter must be visited due to a fraud mistake</li><li><i>9</i> - The RTC clock was adjusted.</li><li><i>10</i> - The voltage on all phases has exceeded the limit for overvoltage detection</li><li><i>11</i> - The voltage on all phases has exceeded the limit for undervoltage detection.</li><li><i>12</i> - The voltage on L1 has exceeded the limit for overvoltage detection</li><li><i>13</i> - The voltage on L2 has exceeded the limit for overvoltage detection</li><li><i>14</i> - The voltage on L3 has exceeded the limit for overvoltage detection</li><li><i>15</i> - A charging transaction from a pico charging station</li><li><i>16</i> - A panic message from the pico controller</li><li><i>17</i> - A panic message from the pico MID service</li><li><i>18</i> - Pico Warning: the RCD has triggered</li><li><i>19</i> - Pico Warning: the cable can not be locked</li><li><i>20</i> - Pico Warning: a diode failure</li><li><i>21</i> - Pico Warning: pico has detected a current overload</li><li><i>22</i> - Pico Warning: the internal temperature is too high</li><li><i>23</i> - A LogBook Entry when a parameter has changed (e.g. Impulse Values)</li><li><i>24</i> - A LogBook Entry when the device went down (with date/time) and comes up again (with date/time)</li><li><i>25</i> - A LogBook Entry when there was a general phase error. More Data in the error code field</li><li><i>26</i> - The general error was reset (everything is fine again)</li><li><i>27</i> - A fatal error (see details in the error code)</li><li><i>28</i> - The Magnet Field is fine again</li><li><i>29</i> - The tamper detection is fine again (cover is closed)</li><li><i>30</i> - The clock was adjusted with the old date/time and the new date/time</li><li><i>31</i> - The update of the MSP430 Firmware (with OldFirmware Version and NewFirmware Version)</li><li><i>32</i> - The update of the communication Module Firmware (with OldFirmware Version and NewFirmware Version)</li><li><i>33</i> - Event that the internal logbook of the meter is full</li><li><i>257</i> - Loadprofile (Datalogger values) with Active Energy import and export and the reactive energy. And the OCMF signature</li><li><i>65535</i> - InvalidValue</li></ul>
lastWarningOrErrorMessagestring nullable

The message of the last warning or error of the station.

lastWarningOrErrorTimestring date-time nullable

The time when the LastWarningOrError happend

lastSeenstring date-time nullable

The time when we last see the charging station

Changes

No recorded changes to this operation across all 1 revision of this API.