Connect Vecos to KODE OS for smart locker data integration
Overview
Use this integration to connect Vecos smart locker systems to KODE OS. You discover lockers and collect availability, access, and operational status over REST.Supported Capabilities
- Discover Devices & Points
- Collect Sensor Data
Prerequisites
- An active account with Vecos and access to their API or developer portal
- API key or token from the Vecos platform
- KODE OS environment with access to Data Sources
Generate API Credentials
- Log in to the Vecos platform or admin console
- Navigate to the API settings, developer section, or account settings
- Generate a new API key or token
- Copy the key and store it securely — you will need it when configuring the connector in KODE OS
Configure Connector in KODE OS
- Navigate to Data Sources in your building
- Click API Catalog and search for Vecos
- Click + Add Datasource
- Fill in the fields below and complete the three-page setup flow
Discover Devices and Points
After configuring the connector, click Discover on the connector detail page. KODE OS will query the Vecos system and return a list of available devices and their data points. Review the discovered items and select the devices you want to register in KODE OS. For more details on the discovery process, see the Discovery guide.Devices and Points
When you discover devices from Vecos, KODE OS maps them to the following device types and data points:smartLocker
Canonical Type:smartLocker
What Data You Get
Point History
Time-series readings including nrOfAllocations, collected at regular intervals from connected devicesPolling Schedule
- Point History — Default polling: 5 minutes (min: 5 minutes, max: 1 hours)
Use Cases
Once connected, this integration enables you to:- Monitor locker availability and assignment status across facilities
- Track parcel delivery and pickup events for tenant services
Troubleshooting
Authentication or connection error
Authentication or connection error
Verify that the credentials are correct and have not expired. Check that the URL is reachable from the KODE OS environment. Ensure the API key or token is valid and has not been revoked or expired in the Vecos platform.
Discovery returns no devices
Discovery returns no devices
Verify the connector credentials have sufficient permissions in the Vecos system to list devices. Run a test connection first to confirm connectivity. Some systems require specific API scopes or roles for device enumeration.
Data collection stops or gaps appear
Data collection stops or gaps appear
Check the connector status on the Data Sources page. If the status shows an error, review the error logs on the connector detail page. Common causes include expired credentials, network changes, or rate limiting by the Vecos API.