Connect Accuenergy to KODE OS for meters data integration
Overview
Use this integration to connect your Accuenergy power meters, submeters, and communication devices to KODE OS over MQTT. You can discover devices and points, then pull snapshot sensor readings on a schedule so consumption and status stay current in your building model.Supported Capabilities
- Discover Devices & Points
- Collect Sensor Data
- MQTT Data Collection
- File Validation
Prerequisites
- Access to the MQTT broker used by Accuenergy
- Broker hostname, port, and credentials
- 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 Accuenergy
- 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 Accuenergy 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 Accuenergy, KODE OS maps them to the following device types:- Electric Meter (
electricMeter)
What Data You Get
Point History
Time-series sensor readings such as temperature, humidity, CO2, occupancy counts, energy consumption, light levels, and other measurable values from physical sensorsPolling Schedule
- Point History — Default polling: 5 minutes (min: 1 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
No data arriving from MQTT broker
No data arriving from MQTT broker
Verify the MQTT broker hostname, port, and credentials. Check that the topic patterns match the topics being published by the Accuenergy devices. Ensure the MQTT client has subscribe permissions.
Discovery returns no devices
Discovery returns no devices
Verify the connector credentials have sufficient permissions in the Accuenergy 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 Accuenergy API.