Device Connectivity Overview
Device Connectivity Goals
Device connectivity is one of the core functions of the IoT platform. ThingsPanel supports multiple device onboarding methods, aiming to help users quickly and conveniently connect various IoT devices to the platform for data collection and management. Key achievements include:
- Multi-protocol Support: Supports mainstream IoT protocols (e.g., MQTT, CoAP, HTTP, Modbus), meeting the access needs of different devices.
- Full Scenario Coverage: Supports manual addition, batch import, addition by ID, and third-party platform integration, adapting to different scales and types of device onboarding scenarios.
- Simplified Access Process: Provides intuitive user interface and operation flow.
- Efficient Device Management: Supports batch addition, automatic addition, and scan code addition, improving device management efficiency.
Four Ways to Connect Devices in ThingsPanel
| Access Method | Operation Workflow | Core Features | Applicable Scenarios |
|---|---|---|---|
| Manual Add | Enter device name, select device template (template can match arbitrary protocols like MQTT, Modbus), complete device addition | Simple operation, no complex configuration, strong protocol adaptability | Small number of devices, rapid deployment of single devices |
| Batch Add | Download device template → Fill in device data → Select template to import, realizing batch device creation | Efficient and convenient, supports large-scale device batch creation | Scale device onboarding, such as adding thousands to tens of thousands of devices at once |
| Add via ID | Pre-register devices in system product management, then access via device ID (corresponds to mobile scan code addition) | Requires pre-registration, standardized access process, adapted for mobile operations | Access for pre-registered devices, scenarios requiring quick binding via mobile scan |
| Add via Third-party | Connect to third-party platforms/services, batch add devices at once, synchronize device telemetry data and support downlink control | Strong cross-platform integration capability, supports batch access and data interaction | Integrating devices from external platforms, such as migration/integration of third-party devices like China Mobile OneNet, China Telecom IoT Platform, video access platforms |
Supported Protocols
| Category | Name/Protocol | Applicable Device Types | Core Description (Features, Scenarios, Industry Characteristics) |
|---|---|---|---|
| Protocol Component | MQTT | Sensors (temp/humidity, light), smart terminals, gateways, low-power devices (NB-IoT modules) | - Lightweight pub/sub protocol, low bandwidth, low power, supports QoS levels (0/1/2); - Suitable for cross-network device communication, massive terminal data reporting, widely used in smart home, IIoT, environmental monitoring. |
| Protocol Component | Modbus TCP RTU | Industrial sensors (pressure, flow, level), PLCs, VFDs, smart meters (electric, water) | - Industrial standard protocol. TCP for Ethernet, RTU for serial (RS485/232); - Supports register read/write, coil control. Simple structure, strong compatibility. Core for industrial automation control and status monitoring. |
| Protocol Component | Modbus TCP Direct | LAN PLCs, industrial controllers, smart meters (power, flow), industrial sensors | - Ethernet direct connection version based on Modbus, omitting Serial-to-TCP conversion, direct data interaction via LAN; - Low latency, high stability. Suitable for peer-to-peer communication in LAN environments like factories and monitoring rooms, e.g., real-time interaction between PLC and monitoring host, production line linkage control. |
| Protocol Component | GB28181 National Video Protocol | Network Cameras (IPC), NVRs, Video Encoders, Video Platform Devices | - China's mandatory standard for security video monitoring. Supports device registration, real-time video transmission (RTP/RTSP), playback, alarm linkage; - Suitable for urban security, park monitoring, traffic checkpoints, ensuring interoperability between different vendors. |
| Protocol Component | OPC-UA | Industrial controllers, sensors, SCADA systems, MES systems, smart devices | - Industrial IoT cross-platform communication protocol. Cross-OS, cross-device type. Provides security (SSL/TLS), data modeling, historical data access; - Suitable for industrial data integration, inter-device collaborative control. One of the core protocols of Industry 4.0. |
| Protocol Component | Beidou 2/3 | Vehicle terminals, maritime devices, outdoor monitoring (weather, geological), mobile terminals | - China Beidou Satellite Navigation System protocol. Supports positioning, velocity, timing (PNT), short message communication (Beidou 3 enhanced); - Suitable for outdoor operations, transportation, emergency rescue, agriculture, and other scenarios requiring high-precision positioning. |
| Protocol Component | Hydrology SL651-2014 | Hydrological monitoring devices (water level gauge, flow meter, rain gauge), RTUs, Hydrology station devices | - Hydrology industry standard protocol. Specifies format and interface for hydrological data collection, transmission, and storage; - Suitable for water conservancy departments, hydrology stations to report water volume and quality data. Supports flood control and water resource dispatch decisions. |
| Protocol Component | Water Resources SL/T427—2021 | Water resource monitoring devices (flow meter, water level sensor), metering terminals, engineering monitoring devices | - Water resource management industry recommended standard. Standardizes requirements for water resource data collection, transmission, and statistical analysis; - Suitable for total water resource control, water usage supervision, water conservancy engineering monitoring. |
| Protocol Component | IEC104 Protocol | Power telemetry terminals, substation devices, power monitoring devices (RTU, DTU), SCADA systems | - Power industry standard telecontrol communication protocol based on TCP/IP. Supports telemetry (analog), telesignal (digital), telecontrol (commands); - Suitable for power system scheduling, substation monitoring, distribution automation, ensuring real-time power data transmission. |
| Protocol Component | GB26875.3-2011 Alarm Transmission | Alarm terminals (smoke, heat detectors), security alarm hosts, emergency linkage devices, monitoring platforms | - Domestic alarm system communication standard. Specifies alarm info format, transmission method, and linkage logic; - Suitable for security alarms, emergency rescue, industrial safety monitoring. Supports rapid alarm reporting and multi-device linkage response. |
| Third-party Integration | Hikvision Integrated Security Platform (iSecure Center) | Hikvision cameras, NVRs, access control, alarm hosts, smart analysis devices | - Integrated security management platform by Hikvision. Supports video monitoring, access control, alarm linkage, AI analysis; - Suitable for parks, buildings, urban security. Can access Hikvision and GB28181 compatible third-party devices, providing integrated security solutions. |
| Third-party Integration | China Mobile OneNet | IoT modules (NB-IoT, 4G/5G), sensors, smart terminals, gateways (LoRa, WiFi) | - China Mobile's open IoT platform. Supports MQTT/CoAP/HTTP access. Provides device management, data storage, API services; - Suitable for smart cities, smart homes, industrial monitoring, consumer electronics. Supports massive device onboarding and carrier-grade network assurance. |
| Third-party Integration | China Telecom CTWing | Telecom IoT modules (NB-IoT, 4G/5G), smart terminals, sensors, industry devices | - China Telecom IoT platform. Supports multi-protocol access, edge computing, data visualization. Provides industry solutions (smart healthcare, smart traffic); - Advantages in telecom network coverage (especially NB-IoT), suitable for industry applications with high network stability requirements. |
| Third-party Integration | LoRaWAN Gateway (ChirpStack) | LoRa sensors, LoRa terminals, LoRa gateways, low-power IoT devices | - ChirpStack is an open-source LoRaWAN network server. Supports LoRa device access, data parsing, device management; - Suitable for low-power, long-distance, small data volume scenarios (smart agriculture, park environment monitoring). Requires LoRa gateways. Flexible deployment (private/public). |
*Note: The above are some of the listed protocols. According to ThingsPanel's design, it can support various forms of connection protocols. The supported protocols and third-party platforms will increase with the continuous update of the ThingsPanel platform. Please refer to the latest official documentation for specific supported protocols and platforms.