Charge Point Sensors

🚗 Quick Introduction to Charge Point Sensors

Charge Point Sensors allow operators to explore different use cases where the sensors can improve the real time experience when using a charge point.

📖 Supported Sensor Types

• occupancy: For sensors that Indicate whether the charging point is occupied. Possible values: true, false, or null.

🗓️ valueUpdatedAt vs. updatedAt

Our API has two distinct timestamps related to sensor data updates:

• valueUpdatedAt – This timestamp represents when the sensor last updated its value. It reflects the actual moment the measurement was taken, which may differ from the time an API request is made. Usually this data is available from your sensor integration (otherwise you can just use NOW())
• updatedAt – This timestamp indicates when the value was processed or stored in our system. It reflects the last time our system registered a change, which could be due to an API call or internal updates.

Example Scenario

• A sensor reports a new value at 10:00 AM → valueUpdatedAt = 10:00 AM
• The API retrieves this data at 10:05 AM → updatedAt = 10:05 AM

This means that while your API request was made at 10:05 AM, the latest recorded sensor reading occurred at 10:00 AM.

Why This Matters

• If updatedAt is recent but valueUpdatedAt is old, the sensor might not have reported new data recently.
• We use valueUpdatedAt to determine how fresh the sensor data is, rather than relying solely on updatedAt.