You need to enable JavaScript to run this app.
优惠活动
大模型
产品
解决方案
定价
更多

请求提供互联传感器协同工作的技术示例(含平台中转/直连)

Got it, let's walk through two concrete, real-world examples of interconnected sensors/devices working together—one leveraging the Cumulocity (C8Y) platform as a broker, and another using direct device-to-device communication, just like you asked.

Scenario 1: C8Y Platform Mediates Device X → Device Y Workflow

Let’s use a warehouse environmental monitoring setup as an example:

  • Device X: A wireless温湿度传感器 placed in perishable goods storage.
  • Device Y: A combined dehumidifier + environmental data logger installed in the same zone.

How it plays out:

  1. Device X detects that relative humidity has spiked above 70% (the threshold for mold risk). It sends an event payload to the C8Y platform via MQTT or REST API:
    {
      "type": "humidity_alarm",
      "time": "2024-05-20T14:30:00Z",
      "source": { "id": "device-x-123" },
      "text": "Relative humidity exceeded 70% (current: 72%)",
      "humidity": 72
    }
    
  2. The C8Y platform has a pre-configured Event Trigger Rule that listens for humidity_alarm events. When it receives this event:
    • First, it sends a request to Device Y to pull its current operational status (e.g., is the dehumidifier already running?) using the C8Y REST API endpoint: GET /inventory/managedObjects/{device-y-id}/measurements
    • If the dehumidifier is idle, the platform triggers an operation on Device Y via POST /devicecontrol/operations:
      {
        "deviceId": "device-y-456",
        "description": "Start dehumidifier and log humidity every 5 mins",
        "operation": {
          "dehumidifier": "start",
          "data_log_interval": 300
        }
      }
      
  3. Device Y executes the operation: it turns on the dehumidifier, starts logging humidity every 5 minutes, and sends those measurements back to C8Y until the humidity drops below 60%.
Scenario 2: Direct Device-to-Device Trigger (No Platform Middleman)

Let’s take an industrial machinery monitoring use case:

  • Device X: A vibration sensor mounted on a factory motor.
  • Device Y: A high-definition inspection camera pointed at the motor’s bearing assembly.

How it plays out:

  1. Device X continuously monitors vibration frequency. When it detects a sudden spike (indicating potential bearing wear), it sends a direct trigger command to Device Y over a local LoRaWAN network or MQTT broker (no cloud platform involved):
    • Using MQTT, Device X publishes a message to the topic device/trigger/camera/motor-789 with this payload:
      {
        "trigger_type": "vibration_anomaly",
        "vibration_level": 1.8,
        "target_area": "bearing_assembly",
        "duration": 60
      }
      
  2. Device Y is subscribed to this specific MQTT topic. As soon as it receives the message:
    • It immediately starts recording a 60-second high-res video of the bearing assembly.
    • It saves the video locally on an SD card and sends a compressed 10-second clip to the on-site edge gateway for quick analysis.
    • After recording, it sends a confirmation message back to Device X: {"status": "recording_completed", "file_path": "/sdcard/motor-789-202405201435.mp4"}
  3. Device X stops sending trigger commands until another vibration anomaly is detected.

内容的提问来源于stack exchange,提问作者Catalin

相关产品推荐
方舟 Agent Plan

超全模态模型 × Harness 升级,最新支持 Deepseek-V4.1-Flash、GLM-5.3 系列、Doubao-Seedream-5.0-pro、Kimi-K3 (部分), 限时 9.9 元起

最近更新时间:2026.05.28 09:43:43