Covering 29+ verified field devices across metering, industrial sensing & control, building & environment, and smart agriculture. Search by name, model, or protocol — every device comes with complete integration documentation.
Why a "Device Catalog"?
In IoT projects, the hardest part isn't the technology itself — it's figuring out "can I connect this device?"
- The client's site has a Schneider Electric power meter with Modbus RTU. Can it go LoRaWAN?
- A heating retrofit project uses CJ/T 188 heat meters on an M-Bus. How do you take them wireless?
- An Acrel multi-circuit power meter — how many circuits per collector? In the traditional LoRaWAN ecosystem, answering these means: digging through sensor datasheets, scouring ChirpStack codec repositories, writing your own parsing scripts — every step costs time.
ThinkLink's Integrated Device Library was built to solve exactly this.
Device-First Search Logic
The core philosophy is simple: don't start from platform features — start from what's in the field.
Open https://www.think-link.net/zh/devices/ and you'll see a clean search interface:
- Search by device name — type "ADW2xx" or "three-phase meter", go straight to the target
- Filter by model — exact model matching supported
- Filter by protocol — Modbus RTU / DL/T 645 / CJ/T 188 / native LoRaWAN, at a glance No need to understand ThinkLink's architecture first. No need to know what EdgeBus is. Whatever device you're holding, start there.
Four Categories Covering Mainstream Retrofitting Scenarios
1. Metering (11 devices)
Covers the most common meter types for building energy monitoring and heating/water metering.
2. Industrial Sensing & Control (12 devices)
Industrial sites are characterized by diverse device types, inconsistent protocols, and harsh environments. The library covers the complete sensing chain from temperature, level, and RPM to oil spill detection, with KC11/KC21 collectors providing a unified RS-485-to-LoRaWAN access layer.
3. Building & Environment (5 devices)
4. Smart Agriculture (1 device, packed with capability)
A single KC21 supports up to 3 soil sensors, covering multi-dimensional farmland sensing in one deployment.
Three Access Paths, One Card Tells the Whole Story
Every device card on the library shows not just the name, model, category, and protocol — it also labels the access path:
And every device card comes with complete integration documentation. Click "View Integration Guide" on any card and you'll jump directly to that device's step-by-step manual, which covers:
- Wiring diagrams (which wire goes to which KC collector terminal)
- EdgeBus configuration (function codes, register addresses, data formats)
- Thing model parsing scripts (pre-written JS parsing logic)
- Parameter configuration tables (upload interval, read interval, COV thresholds, slave address)
- Key caveats (e.g., DL/T 645's +0x33 offset encoding, CZ580's register unlock command)
More Than a List — It's an Integration Decision Tool
The library's value goes beyond "looking things up" — it helps integrators make technical decisions:
Scenario 1: A client says "We have Acrel ADW2xx meters and want energy monitoring."
→ Search the library → Confirm Modbus RTU protocol → Open the integration guide → Learn that 1 KC21 handles 1 ADW2xx with 4 circuits uplinked independently → Assess feasibility in under 10 minutes.
Scenario 2: A heating retrofit project has Jingquan LXSY-15E cold water meters on site.
→ Search "CJ188" → Confirm KC22 + M-Bus + EdgeBus access → The guide provides complete frame format, data identifiers, and thing model parsing → No need to dig through the CJ/T 188 national standard.
Scenario 3: Comparing a weighing transmitter vs. ultrasonic level sensor for the right fit.
→ Search both devices → Compare accuracy, response time, power requirements, and integration complexity from the documentation → Make an informed selection based on actual parameters.
A Growing Device Ecosystem
ThinkLink's device library is not static. Every time a new device is validated for integration, its documentation is added. The library currently covers:
- Protocols: Modbus RTU, DL/T 645-2007, CJ/T 188-2004, native LoRaWAN
- Collectors: KC11 (220 VAC powered, Class C), KC21 (battery powered, IP65), KC22 (M-Bus dedicated)
- Brands: Schneider Electric, Acrel, ZENNER, Huizhong, Elitech, Renke, Zhuowen, Disen, Dianyingpu, Shenling, GXHY, Tianwei, Ringder, and more
If you have a device not yet listed, ThinkLink's EdgeBus framework supports rapid adaptation. Using EBHelper's JSON configuration or EBSDK's TypeScript scripting, most Modbus RTU devices can be protocol-adapted and added to the library within 30 minutes.
Conclusion
The ThinkLink Integrated Device Library is more than the number "29 verified devices." Its real value lies in:
- Lowering the technical evaluation barrier — integrators don't need to become LoRaWAN experts first; just look up the device by name to know if it works
- Shortening project startup time — the complete path from wiring to data-on-platform is already documented for every device
- Eliminating repeated trial-and-error — DL/T 645 offset encoding, M-Bus parity settings, sensor-specific unlock commands — all battle-tested knowledge is baked into the docs, no need to rediscover it on every project Start from the device, not the platform. That's ThinkLink's answer to the IoT retrofit market.
Top comments (0)