telefonicaid / telefonicaid/iotagent-node-lib
NGSI-LD observedAt is ignoring timezone from service or device for multivariable sensor
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 62
- Forks
- 90
- Avg merge
- 2h 35m
- Merged PRs (30d)
- 1
Description
I provision a service with "timezone": "Asia/Tokyo" using MQTT binding.
The sensor push several attributes/measruements. The issue is the timezone for observedAt is always UTC and ignoring any timezone provided by service or device.
Docker image date time: Thu Dec 14 11:53:07 UTC 2023
IoT Agent log -> "observedAt": "2023-12-14T11:53:07.152Z**"
Orion-LD -> "observedAt": "2023-12-14T11:53:07.152Z"
What i expected Orion-LD -> "observedAt": "2023-12-14T20:53:07.152Z"
Maybe the bug is here
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 in lib/services/ngsi/entities-NGSI-LD.js at the linked line and trace how observedAt is generated for multivariable sensors. Compare the configured service or device timezone with the emitted NGSI-LD timestamp, then verify the behavior with the relevant test suite. Done means observedAt honors the configured timezone instead of always using UTC.
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
- Mostly clear
- Newbie friendliness
- 45/100