telefonicaid / telefonicaid/iotagent-node-lib
404 Not Found "No device was found with id:" and the orion object updates successful
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 62
- Forks
- 90
- Avg merge
- 2h 35m
- Merged PRs (30d)
- 1
Description
In my application I need the TimeInstant metada in each attribute and because of that I enable the timestamp option in the config-blank.js file. However, there is a problem, after that, the IDAS UL agent is always returning no device found with id, but the entity is updated in the context broker with the right attribute values and timestamps. I'm running the last version available using the docker-compose.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the timestamp option in config-blank.js and reproduce the behavior using the docker-compose setup described. Trace the IDAS UL agent response alongside the Orion entity update; the issue is resolved when enabling timestamps no longer produces the device-not-found response while updates retain the expected attribute values and timestamps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100