Open-device infrastructure
Energy and IoT Device Directory
Find the EpiSensor connection path for third-party meters, sensors and controllers. Each guide starts with the device's documented interface, then shows the Edge hardware, protocol and commissioning work it needs.
Live catalogue foundation
Mass coverage, with a quality gate
We ingest maintained protocol registries into a candidate layer, select energy-relevant records, and add EpiSensor connection guidance before a model page becomes indexable.
- 4501
- Zigbee definitions inspected
- 141
- LoRaWAN profiles inspected
- 1347
- Energy-relevant candidates
- 256
- Manufacturers represented
Structured metadata comes from pinned, permissively licensed releases of zigbee-herdsman-converters and ChirpStack device-profiles. Images follow a separate provenance review, so an image filename can never be mistaken for a registry mapping or a complete product record.
Browse the candidate catalogueReviewed guides
Start with the exact device family
The directory will grow across Zigbee, LoRaWAN, Modbus, BACnet, OPC UA, M-Bus, pulse and analogue devices. A guide is published only when the required interface and Edge route are clear.
1 published
What compatible means
The protocol tells us the route. The model tells us the work.
When a manufacturer documents a protocol that Edge supports, we describe the device as compatible and identify the interface needed to connect it. The guide then deals with the engineering detail that a protocol name does not settle: model variants, wiring, register maps, payload codecs, object profiles, units and commissioning.
Where EpiSensor also has a built-in registry mapping, reusable configuration or proven deployment, the page says so. Those stronger signals add convenience; they are not required for an open-protocol device to work with Edge.