Created question in FIWARE Q/A platform on 13-03-2017 at 11:03
Please, ANSWER this question AT http://stackoverflow.com/questions/42761660/querying-lwm2m-active-attribute-in-orion

Question:
Querying lwm2m active attribute in Orion

Description:
I have the following configuration for an active lightweightm2m-iotagent attribute (a temperature sensor value). Fiware's IoT agent turns IPSO objects into lazy attributes but I add a mapping to make it an active attribute as in the documentation:

types: {
'Type': {
service: 'service',
subservice: '/service',
commands: [],
lazy: [],
active: [

],
lwm2mResourceMapping: {
"t":

}
},

According to the documentation for the iotagent-node-lib:

NGSI queries to the context broker will be resolved in the Broker database.

However, when I query my active attribute in Orion, Orion also queries the lightweightm2m-iotagent, requesting a bogus /3303/0/0 path which doesn't even exist in the IPSO definition.

curl -H "Fiware-service: service" -H "Fiware-servicepath: /service" http://172.17.0.1:1026/v2/entities/entity1:Type/attrs/t/value

How can I set up the configuration to get the behavior stated in the documentation, resolving a query for an active attribute in the broker database and avoiding these bogus queries?