Connect MDAS to KODE OS for controller data integration
Overview
Use this integration to connect MDAS to KODE OS. You can discover devices and points, collect sensor data through REST, and receive webhook payloads with file validation when your workflow requires it.Supported Capabilities
- Discover Devices & Points
- Collect Sensor Data
- Receive Webhook Data
- File Validation
Prerequisites
- An active account with MDAS and access to their API or developer portal
- KODE OS environment with access to Data Sources
Configure Connector in KODE OS
- Navigate to Data Sources in your building
- Click API Catalog and search for MDAS
- 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 MDAS 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 MDAS, KODE OS maps them to the following device types and data points:IO Reader / Controller
Canonical Type:IOREADER
What Data You Get
Point History
Time-series readings including Normal, collected at regular intervals from connected devicesPolling Schedule
- Point History
Use Cases
Once connected, this integration enables you to:- Monitor real-time HVAC, lighting, and building automation data from a single dashboard
- Set up automated alerts when equipment deviates from normal operating parameters
- Track energy consumption and optimize building performance with historical trend data
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. Double-check all credential fields match the values from the MDAS platform.
Discovery returns no devices
Discovery returns no devices
Verify the connector credentials have sufficient permissions in the MDAS 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 MDAS API.