Closed MLopezJ closed 1 year ago
- Update
undefine
values in expected output
Implemented here: https://github.com/MLopezJ/asset-tracker-cloud-coiote-azure-converter-js/pull/12
Values:
ID | Object | Prop | Name | Expects | LwM2M Def |
---|---|---|---|---|---|
6 | Location | 0 | Latitude | float | link |
6 | Location | 1 | Longitude | float | link |
3304 | Temperature | 5700 | Sensor Value | float | link |
3304 | Humidity | 5700 | Sensor Value | float | link |
3315 | Barometer | 5700 | Sensor Value | float | link |
Originally posted by @MLopezJ in https://github.com/MLopezJ/asset-tracker-cloud-coiote-azure-converter-js/issues/7#issuecomment-1424426763
- What does all the values has in similar?
- Are those values telemetry data?
- The
min-max
value is present in YouTube video tutorial as well?
Are those values telemetry data? Yes! Were set here as Telemetry resources
What does all the values has in similar? Values were set as "Value Tracking" in Coiote: link here
The min-max
value is present in YouTube video tutorial as well?
Not visible on the following videos:
min-max
value is present in YouTube video tutorial as well?~undefine
values in expected output~In mind time I can set up an Azure function to be trigger from IoT Hub updates