Uploaded image for project: 'Help-Desk'
  1. Help-Desk
  2. HELP-22063

[fiware-stackoverflow] How to realize the ERROR Path for Commands using MQTT-binding of the FIWARE IoT-Agent-JSON

    Details

    • Type: Monitor
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: FIWARE-TECH-HELP
    • Labels:

      Description

      Created question in FIWARE Q/A platform on 24-08-2023 at 09:08
      Please, ANSWER this question AT https://stackoverflow.com/questions/76967925/how-to-realize-the-error-path-for-commands-using-mqtt-binding-of-the-fiware-iot

      Question:
      How to realize the ERROR Path for Commands using MQTT-binding of the FIWARE IoT-Agent-JSON

      Description:
      from the FIWARE IoT-Agent-Json documentation I understand that there is the happy path and error path for command execution (https://fiware-iotagent-json.readthedocs.io/en/latest/usermanual.html#commands)
      Using the MQTT-binding, sending a payload on the topic /json/<APIKey>/<DeviceId>/cmdexe always results in an update of the corresponding command-info to OK. This is fine as long the device does the right thing about receiving the command. However, how can I trigger an ERROR, e.g. the device receives the command, but can not execute it. Somehow with MQTT, I currently onyl understand the _info to be on either PENDING or OK once the IoT-Agent published the command to the device.
      In which case will the _info udpated to ERROR? I could not find anything in the code about this scenario.
      Thanks, for any help on this.

        Activity

        Hide
        backlogmanager Backlog Manager added a comment -

        2023-08-25 05:31|CREATED monitor | # answers= 0, accepted answer= False

        Show
        backlogmanager Backlog Manager added a comment - 2023-08-25 05:31|CREATED monitor | # answers= 0, accepted answer= False

          People

          • Assignee:
            mapedraza Miguel Ángel Pedraza
            Reporter:
            backlogmanager Backlog Manager
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated: