Connect Fludia to KODE OS for meters data integration
Overview
Use this integration to connect Fludia wireless metering endpoints to KODE OS. You can discover meters and collect historical point data—such as signal quality, activity, and low-battery indicators—on your configured polling interval.Supported Capabilities
- Discover Devices & Points
- Collect Sensor Data
Prerequisites
- An active account with Fludia and access to their API or developer portal
- Username and password credentials for the Fludia system
- 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 Fludia
- 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 Fludia 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 Fludia, KODE OS maps them to the following device types and data points:Meter
Canonical Type:default
What Data You Get
Point History
Time-series readings including snr, rssi, active, low_battery, collected at regular intervals from connected devicesPolling Schedule
- Point History — Default polling: 15 minutes (min: 15 minutes, max: 1 hours)
Use Cases
Once connected, this integration enables you to:- Aggregate utility consumption data (electricity, gas, water, steam) in a unified dashboard
- Detect abnormal consumption patterns and potential waste or leaks
- Generate utility cost reports and benchmark buildings in your portfolio
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. Verify the username and password are correct and the account has not been locked in the Fludia system.
Discovery returns no devices
Discovery returns no devices
Verify the connector credentials have sufficient permissions in the Fludia 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 Fludia API.