Daniel Calvo's profile - activity

Hi, in order to reproduce your problem, could you please explain us the process you have followed to run this simulation? Thanks in advance.

Hi,

Thanks for your question.

If you are reading https://github.com/telefonicaid/iotag..., pre-provision and provision terms are used in places with the same purpose.

Nevertheless, IoT Agents framework contain a couple of interesting features that avoid repeating the device provisioning operation for devices with the same characteristics, i.e., multiple motes with temperature, moisture and pollution sensors deployed within a Smart City. In this case, you can use configurations (https://github.com/telefonicaid/iotag...) feature.

This functionality is clearly used by the lwm2m IoT Agent, where you can provide a configuration and devices matching it will be auto-provisioned the first time they connect to the agent.

BR,

Daniel on behalf of ATOS team

Hi,

Thanks for your question and interest in using the FIWARE LoRaWAN IoT Agent. :)

Could you please open an issue in https://github.com/Atos-Research-and-..., explaining with further details which problems are you facing? It would be nice also if you could share some logs from the IoT Agents and Orion Context Broker.

BR,

Daniel on behalf of ATOS team

Hi,

First of all, thank you for your question, we are glad to receive feedback and suggestions from the community!

To the best of my knowledge, what you intend to do is not possible with the current version of the IoT Agents so far. You can find a detailed explanation on the following GitHub issue: https://github.com/telefonicaid/iotag...

In which use-cases do you think that this feature would be useful? We could study if it is an interesting functionality to be added to the IoT Agents.

Thanks again,

Daniel