Always parse the timestamp field with a UTC parser before converting to local time.
Keep sensors on a secured VLAN, restricting API access to authorized server IPs or API gateways. 3. Core API Endpoints and Data Retrieval
Returns operational metrics of the sensor (CPU usage, temperature, uptime). Sample Response: xovis api documentation
Instead of lines, zones monitor defined geometric areas. The API delivers real-time information regarding:
GET /api/v1/data/history : Fetch count data for a specific time range (requires from and until parameters). Always parse the timestamp field with a UTC
"sensor_id": "SNSR_001", "location_id": "LOC_NYC_05", "data": [
: The GitHub repository sdu-cfei/xovis-driver provides an open-source example of a driver designed to receive this pushed data. Its configuration guide, which matches the manual's instructions, suggests settings like: Data Type : Line count data, Interval : 1 minute, Granularity : 1 minute, Protocol : HTTP(S), and Data push format : JSON. The URL would be the endpoint of the receiving service. Core API Endpoints and Data Retrieval Returns operational
: The API enables the management of specialized AI plugins, such as Gender Statistics (PIGES) and Staff Exclusion (PISTE) , allowing for more granular data filtering and analysis.
In smart buildings, API data triggers automation rules. If the API reports "Zone Occupancy" is below a threshold, the system sends an MQTT command to the HVAC system to reduce air conditioning in that area, saving energy. If occupancy is high, it triggers a cleaning alert for facility management.
This section provides a step-by-step guide for setting up your first data integration using the Data Push method. This is the most common path for sending count data to an external system.