iotagent-json
iotagent-json copied to clipboard
Improvement: When start the component and if not find iotamanager alive then dont retry automatically
Improvement: When start the component and if not find iotamanager alive then dont retry automatically
Twin issue: https://github.com/telefonicaid/iotagent-ul/issues/325
(However, note IOTA->IOTAManager interaction is in the northbound API so probably this is an issue in the iotagent-node-lib library. We will move to there in that case)
@cesarjorgemartinez @fgalan connect the iotmanger (https://github.com/telefonicaid/iotagent-manager) and hit device provisioning API but didn’t get any response by iot manager. Although device successfully register. Use debugger in the source code of the iotagent but didn’t get any flow.
- API use for device provisioning
curl -iX POST
'http://localhost:4041/iot/devices'
-H 'Content-Type: application/json'
-H 'fiware-service: openiot'
-H 'fiware-servicepath: /'
-d '{ "devices": [ { "device_id": "motion001", "entity_name": "urn:ngsi-ld:Motion:001", "entity_type": "Motion", "timezone": "Europe/Berlin", "attributes": [ { "object_id": "c", "name": "count", "type": "Integer" } ], "static_attributes": [ { "name":"refStore", "type": "Relationship", "value": "urn:ngsi-ld:Store:001"} ] } ] } '
if i am missing anything let me know.
Just to check if I have understood your report correctly...
- You have a setup with IOTA-Manager + IOTA-JSON. Could you share de details? e.g. docker-compose.yml used to create the setup
- You send the request you cite (curl) in your comment to the IOTA-Manager. Doubt: 4041 is the IOTA-Manager port?
- You don't get any response from IOTA-Manager. Doubt: if you don't get any response, what other situation do you get? Timeout expiration in the HTTP request? The curl "hangs" the terminal without response? Other?
- You get your device successfully registered at IOTA-JSON. Doubt: how do you check that the device has been registered?
Is my understanding correct? Could you answer the questions above, please?