OpenIoT | Code repository for Project OpenIoT

I manage to make it to work with one service group (/iot/d). So Post requests to append a sensor goes from /iot/d service group. I use docker images (compiled with docker compose, like the example). I also have modified in docker file the IOTA_DEFAULT_RESOURCE just in case to be: IOTA_DEFAULT_RESOURCE= I've used the latest IoT Agent JSON 1.15.0 and the previous Version 2.4.0 of Orion.

I found a solution... adding the type in the url make the context take account of the value... weird.

The final url must be :

In this document you can see a good reference on how to send commands using the NGSIv2 API:

If you take a look to the previous device example, you can find that a "ping" command was defined. Any update on this attribute “Ping” at the NGSI entity in the ContextBroker will send a command to your device. For instance, to send the "Ping" command with value "Ping request" you could use the following operation in the ContextBroker API:

There are two fixes to that problem. First thing that differs from the tutorial is the provider you need to register with a command. Instead of orion:1026/v1 register the IoT-Agent. It should look something like this with the IOTA_PROVIDER_URL from your docker-compose.yml as provider:

The problem is that the IoT Agent assumes that the device will respond with JSON. Requestbin's default answer is the string "ok". This caused a crash in the agent.

The request is successful if the device returns {}, and it's even more successful if it returns some info on the result of the command. E.g.

first import the following

Not sure if that could be related with the cause of the problem, but using Content-Type: application/json while the actual payload is not JSON (it is t|23, which I understand corresponds to text/plain) seems to be wrong.