[ https://jira.fiware.org/browse/HELP-22063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fernando Lopez reassigned HELP-22063: ------------------------------------- Assignee: Miguel Ángel Pedraza > [fiware-stackoverflow] How to realize the ERROR Path for Commands using MQTT-binding of the FIWARE IoT-Agent-JSON > ----------------------------------------------------------------------------------------------------------------- > > Key: HELP-22063 > URL: https://jira.fiware.org/browse/HELP-22063 > Project: Help-Desk > Issue Type: Monitor > Components: FIWARE-TECH-HELP > Reporter: Backlog Manager > Assignee: Miguel Ángel Pedraza > Labels: fiware, iot, mqtt > > Created question in FIWARE Q/A platform on 24-08-2023 at 09:08 > {color: red}Please, ANSWER this question AT{color} 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. -- This message was sent by Atlassian JIRA (v6.4.1#64016)
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy