[Backlogmanager] [FIWARE-JIRA] (HELP-17244) [fiware-stackoverflow] Cannot register commands in IoT Agent Fiware

[Fernando Lopez (JIRA)]

     [ https://jira.fiware.org/browse/HELP-17244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Fernando Lopez resolved HELP-17244.
-----------------------------------
    Resolution: Done

> [fiware-stackoverflow] Cannot register commands in IoT Agent Fiware
> -------------------------------------------------------------------
>
>                 Key: HELP-17244
>                 URL: https://jira.fiware.org/browse/HELP-17244
>             Project: Help-Desk
>          Issue Type: Monitor
>          Components: FIWARE-TECH-HELP
>            Reporter: Backlog Manager
>            Assignee: Jason Fox
>              Labels: agent, broker, fiware
>
> Created question in FIWARE Q/A platform on 21-12-2020 at 02:12
> {color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/65386590/cannot-register-commands-in-iot-agent-fiware
> +Question:+
> Cannot register commands in IoT Agent Fiware
> +Description:+
> I'm using IoT Agent with Ultralight run directly (not as a dockerized component). I'm able to register new device, which is mapped in Orion Context Broker. However I have an issue with registering Actuators which require commands within configuration data. I use:
> curl -iX POST \
>   'http://MYIP:4061/iot/devices' \
>   -H 'Content-Type: application/json' \
>   -H 'fiware-service: openiot' \
>   -H 'fiware-servicepath: /' \
>   -d '{
>   "devices": [
>     {
>       "device_id": "lamp003",
>       "entity_name": "urn:ngsi-ld:Lamp:003",
>       "entity_type": "Lamp",
>       "protocol": "PDI-IoTA-UltraLight",
>       "transport": "MQTT",
>       "commands": [
>         {"name": "on","type": "command"},
>         {"name": "off","type": "command"}
>        ]}
>   ]
> }
> And in response I'm hit with:
> op=IoTAgentNGSI.DeviceProvisioning | from=n/a | srv=n/a | subsrv=n/a |
> msg=Device provisioning failed due to the following error:  |
> comp=IoTAgent Request error connecting to the Context Broker:
> {"code":"400","reasonPhrase":"Bad Request","details":"missing isDomain
> value for registration attribute"}
> I tried adding "isDomain": "false" to elements of command table, but no luck. It used to work before and furthermore similar solution is presented on official guide.



--
This message was sent by Atlassian JIRA
(v6.4.1#64016)