无法将Sigfox设备连接至Fiware Sigfox IoTAgent求助

Let’s walk through the issues you’re hitting—your setup makes sense, but there are a few common pitfalls with Sig-Fiware integrations that might be tripping you up.

1. Fix the Orion Context Broker Endpoint First #

The 404 error is a clear sign the URL path you’re using doesn’t match what Fiware Orion expects. The /update endpoint you referenced is from Orion v1 (deprecated). For modern Orion versions (v2+), you need to use standardized REST API paths:

• To update a single entity’s attributes, use /v2/entities/<entity-id>/attrs
• For batch updates, use /v2/op/update

Your current GET request to /update won’t resolve in v2, hence the 404.

2. Switch to POST (GET Isn’t Ideal for Fiware Updates) #

Sigfox allows GET callbacks, but Fiware Orion is designed to handle POST requests for context updates—this avoids query string length limits and lets you structure data properly. Here’s a corrected callback setup:

• Method: POST
• URL: http://<your-ip>:17428/v2/entities/sigfoxtest/attrs
• Headers: Add Content-Type: application/json
• Body: Map the Sigfox {data} payload to a specific attribute in your entity. For example:

  {"sigfoxPayload": {"value": "{data}", "type": "String"}}
  

  Make sure sigfoxPayload is an existing attribute in your sigfoxtest entity (adjust to match your entity’s schema if needed).

3. Verify Your Entity Exists (Double-Check!) #

Even if you think the entity is created, confirm it with a manual curl request:

curl -X GET http://<your-ip>:17428/v2/entities/sigfoxtest

If this returns a 404, your entity wasn’t created correctly. Recreate it with a POST to /v2/entities:

curl -X POST http://<your-ip>:17428/v2/entities \
  -H "Content-Type: application/json" \
  -d '{
    "id": "sigfoxtest",
    "type": "Device",
    "sigfoxPayload": {"type": "String", "value": ""}
  }'

Note: Orion entity IDs are case-sensitive—ensure sigfoxtest matches exactly what’s in your Fiware setup.

4. Debug with Orion’s Detailed Logs #

Enable debug logging in Orion to see exactly what’s happening when the Sigfox callback hits. Set the LOG_LEVEL=DEBUG environment variable when starting Orion, then check the logs for:

• The full request Sigfox sends (headers, body/query params)
• Exact error details about why the context element isn’t found

This will help you pinpoint if the issue is with request structure, entity mismatch, or something else.

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