Eclipse Vorto语义归一化中间件未映射消息及Bosch IoT Hub发布问题咨询

Let’s walk through the most likely issues causing your problem, and how to fix them step by step:

1. First: Validate the mosquitto_pub Command & Message Format #

Your current setup has a couple of critical details that might be breaking things:

• Unstructured message payload: You’re sending '"103.3223","3.2322"' — this is just two string values without attribute names. The Vorto Semantic Normalizer relies on structured JSON with key-value pairs that match your Vorto model’s property names. For example, if your model defines latitude and longitude properties, your payload should look like:

  {"latitude": 103.3223, "longitude": 3.2322}
  

  Without these clear keys, the normalizer has no way to map your raw values to semantic attributes.

• Missing verbose debug output: Add the -v flag to your mosquitto_pub command to get detailed logs. This will tell you if the connection to Bosch IoT Hub succeeded, if the message was sent, or if there’s an authentication/network error. Here’s the updated command:

  mosquitto_pub -h mqtt.bosch-iot-hub.com -p 8883 -u 4712@t65a6a75c6b4f429981ba16d1b3d5f414 -P secret -t telemetry/t65a6a75c6b4f429981ba16d1b3d5f414/4712 -m '{"latitude":103.3223,"longitude":3.2322}' --cafile iothub.crt -v
  

  Look for lines like Client ... sending CONNECT and Client ... sending PUBLISH — if these don’t appear, you’ve got a connection or authentication issue.

• CA certificate path: Double-check that iothub.crt is in your current working directory, or use an absolute path (e.g., /home/yourname/certs/iothub.crt) to avoid path-related errors.

2. Verify Bosch IoT Hub Authentication & Topic #

• Credentials check: Ensure your username (4712@t65a6a75c6b4f429981ba16d1b3d5f414) and password (secret) match exactly what’s configured for your device in the Bosch IoT Hub console. Typos or extra spaces here will silently fail authentication.
• Topic correctness: Your telemetry topic telemetry/t65a6a75c6b4f429981ba16d1b3d5f414/4712 follows the correct Bosch IoT Hub format (telemetry/<tenant-id>/<device-id>), but confirm the tenant ID and device ID are spelled correctly (they’re case-sensitive!).

3. Fix Vorto Semantic Normalizer Mapping #

If the message reaches the hub but isn’t being mapped, these are the key checks:

• Model binding: Make sure your device is linked to the correct Vorto information model in the Bosch IoT Hub console. Without this association, the normalizer doesn’t know which semantic schema to apply.
• Payload type matching: Ensure the data types in your JSON payload match the Vorto model’s definitions. For example, if your model expects a float for latitude, send a numeric value (not a string like "103.3223").
• Middleware configuration: Confirm the Vorto Semantic Normalizer is configured to listen to your device’s telemetry topic. If it’s only monitoring a different topic, your messages will be ignored entirely.

Quick Test Steps to Isolate the Problem #

1. Run the verbose mosquitto_pub command above. If you see no errors and the publish is confirmed, the issue is likely with the Vorto setup, not message delivery.
2. Check the Bosch IoT Hub device logs (in the console under your device’s "Logs" tab) — look for entries related to authentication failures, rejected messages, or model mismatches.
3. Send a simple, fully structured JSON payload that exactly matches your Vorto model’s properties, then check if the normalizer processes it.

内容的提问来源于stack exchange，提问作者jeff