Device attributes
Shared and server attributes hold state and control parameters.
Features · Control & Automation
Make every downlink part of a traceable control loop
JavaScript unifies RPC, triggers, alarms and schedules. Device parameters, AI-assisted decisions and execution results stay on one path.
RPC EXECUTION TRACESource / input / device response / operatorManual / Trigger / schedule / MQTT
One automation path from parameters to results
RPC
Backfill parameters, send commands and receive responses.
Trigger + Skill
JavaScript handles events and invokes AI-assisted analysis.
Alarms & notices
Independent thresholds, notification groups and channels.
Scheduled runs
Batch-execute RPC across device groups.
Complete logs
Trace sources, parameters, downlinks and responses.
PARAMETER-AWARE RPC
RPC can use the device's current parameters
Inputs can be backfilled from shared attributes or server attributes. Results can update attributes so platform and device state remain aligned.
- Fixed values, shared attributes and server attributes
- Closed-loop attribute updates and device responses
- External systems can invoke RPC through MQTT
TRIGGER + PRIVATE SKILL
After an alarm, AI uses the device Skill to assist decisions
Each device can carry independent thresholds and a private Skill. A Trigger invokes that Skill with the current device context for customized analysis.
- JavaScript handles uplink events and device context
- Initial parameter alarms can start device-specific analysis
- Skills hold private decision rules and recommendations
Per-device context
Thresholds, location, attributes and history enter the analysis.
Private processing logic
A Skill card carries device-specific rules and recommendations.
ALARM ROUTING
Give every device its own alarm strategy
Multi-parameter alarms, device-specific thresholds and notification groups work together. One event can be recorded, analyzed through a Skill and delivered across channels.
- Independent multi-parameter thresholds per device
- Traceable alarm creation, recovery and notification
- Reusable notification groups across channels
WeComDingTalkSlackEmail
SCHEDULED DEVICE ACTION
Run recurring fleet controls without repeating work
Scheduled tasks bind device actions and batch-call the same RPC for parameter synchronization, recurring control and device inspection.
- Batch RPC across a device group
- Recurring schedules and execution counts
- Task execution linked to RPC logs
EXECUTION OBSERVABILITY
Every RPC has complete execution evidence
See who triggered it, the exact input, what the platform sent and how the device responded. Filter and audit the complete path.
- Filter by Dev EUI, RPC and time
- Expand exact input parameters and complete device responses
- Relate manual, Trigger, scheduled and external sources
Call sourceManual / Trigger
Execution targetRPC / Dev EUI
Input & responseParams / All Data
Audit contextTime / Operator
Integrate external systems with clear boundaries
MQTT is an entry point for external RPC calls and a channel for automation output. RPC and Trigger publish natively to a designated Topic.
External systems
Platforms, business systems and third-party services
ThinkLink JavaScript automation runtime
RPC / Trigger / Skill / Alarm / Schedule
Designated Topic
Native RPC and Trigger publishing
Arbitrary Topic：Use the MQTT forwarder to route to any target Topic and connect existing systems.