Automatically find devices, points, schedules, and assets from your connected systemsDiscovery is the process of querying a connected external system to automatically find and register all available entities — devices, data points, schedules, and assets — without requiring manual configuration for each individual item.
How Discovery Works
When you run discovery on a connector, KODE OS queries the external system’s API to retrieve a list of all available entities. The discovery process follows this flow:Not all integrations support discovery. Check the specific integration’s page to see if discovery is available. Integrations that only receive data via webhooks or MQTT typically do not have a discovery step.
What Gets Discovered
Devices
A device represents a physical piece of hardware or a logical grouping in the external system — a thermostat, a sensor hub, a door controller, a meter, or a camera. Each discovered device includes:Points
Points are the individual data values or control endpoints associated with a device. For a thermostat, points might include current temperature, setpoint, humidity, and operating mode. Each discovered point includes:Schedules
For integrations that support schedule management (e.g., Niagara, Distech), KODE OS can discover existing schedules configured in the external system. Discovered schedules include their name, type (weekly or calendar), current values, and linked point references. See the Schedules guide for more details on schedule types and management.Assets
Assets are physical or virtual objects that KODE OS tracks for metadata purposes — unlike devices, they do not have time-series data points. Asset discovery is available for integrations that manage inventory-type data. Examples of assets:- Network equipment (routers, switches, servers)
- Furniture (desks, chairs, whiteboards)
- Safety equipment (fire extinguishers, AEDs)
- Any physical item requiring metadata tracking
Running Discovery
Step 1 — Navigate to the Connector
Go to Data Sources in your building, then select the connector you want to discover from.Step 2 — Start Discovery
Click the Discover button on the connector detail page. KODE OS authenticates with the external system and begins querying for available entities.Step 3 — Review Results
The discovery results are presented in a list showing all found devices and their associated points. Each item shows:- Device/point name
- External system identifier
- Type and category
- Whether it’s new or already registered
Step 4 — Select and Register
Select the devices and points you want to register in KODE OS. You can select individual items or use “Select All” for bulk registration. Once registered, these devices and points become available for data collection across the platform.Discovery Behavior by Protocol
How discovery works depends on the communication protocol used by the integration:Rediscovery
You can run discovery multiple times on the same connector. When you rediscover:- New items are shown as available for registration
- Existing items are shown as already registered and can be updated
- Removed items (no longer found in the external system) are flagged for review
Troubleshooting
Discovery returns no devices
Discovery returns no devices
Verify that the connector credentials have the correct permissions in the external system. Some vendor APIs require specific roles or scopes to list devices. Also check that the URL and authentication settings are correct by running a test connection first.
Discovery times out
Discovery times out
Large systems with thousands of devices may take longer to discover. If the discovery times out, try narrowing the scope by configuring a specific folder, site, or building filter in the connector settings (if the integration supports it).
Discovered devices are missing points
Discovered devices are missing points
Some integrations discover devices and points in separate steps. After registering devices, you may need to run discovery again or navigate to the device detail page to see its individual points. Also verify that the external system’s API exposes point-level data.