This repository has been archived by the owner on Jul 9, 2024. It is now read-only.
Enable AVSystem Coiote integration #550
coderbyheart
started this conversation in
Ideas
Replies: 1 comment
-
The JSON content Coiote is sending to update the device's whole shadow in AWS: {
"33605": {},
"33606": {
"0": {
"0": "Dummy_OBU_ID",
"1": "PL 473N0",
"2": "01-345678-901234",
"3": "26000007",
"4": "8926000000073",
"5": "60.0",
"6": "26001.0",
"7": "GMSK",
"8": "GMSK",
"9": "1950.0",
"10": "2140.0",
"11": "6069.0",
"12": "11503.0",
"13": "0.0",
"14": "0.0",
"15": "4.5218974"
}
},
"33607": {
"0": {
"0": "",
"1": "0.0",
"2": "0.0",
"3": "0.0",
"4": "0.0",
"5": {
"noValue": true
},
"6": "0.0",
"7": "0.0",
"8": "0.0",
"9": "0.0",
"10": "0.0",
"11": "0.0",
"12": "0.0"
}
},
"33608": {},
"33609": {
"0": {
"0": "0.0",
"1": "",
"6": {
"noValue": true
}
}
},
"Accelerometer": {
"0": {
"Max Range Value": "42.0",
"Min Range Value": "0.0",
"Sensor Units": "m/s2",
"X Value": "6.0",
"Y Value": "31.0",
"Z Value": "13.0"
}
},
"BinaryAppDataContainer": {},
"Connectivity Monitoring": {
"0": {
"APN": {
"0": "internet"
},
"Available Network Bearer": {
"0": "0",
"1": "2",
"2": "6",
"3": "21",
"4": "22"
},
"IP Addresses": {
"0": "10.10.53.53"
},
"Router IP Addresses": {
"0": "10.10.0.1"
},
"Cell ID": "12345",
"Link Quality": "255",
"Link Utilization": "50",
"Network Bearer": "2",
"Radio Signal Strength": "-79",
"SMCC": "0",
"SMNC": "0"
}
},
"Connectivity Statistics": {
"0": {
"Average Message Size": "0",
"Collection Period": "0",
"Max Message Size": "0",
"Rx Data": "0",
"SMS Rx Counter": "0",
"SMS Tx Counter": "0",
"Start": {
"noValue": true
},
"Stop": {
"noValue": true
},
"Tx Data": "0"
}
},
"Device": {
"0": {
"Available Power Sources": {
"0": "0"
},
"Error Code": {
"0": "0"
},
"ExtDevInfo": {
"0": "/33606/0"
},
"Power Source Current": {
"0": "7"
},
"Power Source Voltage": {
"0": "31198"
},
"Battery Level": "0",
"Battery Status": "0",
"Current Time": "2022-08-11T10:00:11Z",
"Device Type": "",
"Factory Reset": {
"noValue": true
},
"Firmware Version": "2db65dadf",
"Hardware Version": "",
"Manufacturer": "test",
"Memory Free": "0",
"Memory Total": "0",
"Model Number": "demo-client",
"Reboot": {
"noValue": true
},
"Serial Number": "device-62ece663bdac4a482e471ea9",
"Software Version": "",
"Supported Binding and Modes": "UQ",
"Timezone": "Europe/Warsaw",
"UTC Offset": "+01:00"
}
},
"Event Log": {
"0": {
"LogClass": "0",
"LogData": "",
"LogStart": {
"noValue": true
},
"LogStatus": "1",
"LogStop": {
"noValue": true
}
}
},
"Firmware Update": {
"0": {
"Firmware Update Protocol Support": {
"0": "0",
"1": "1",
"2": "2",
"3": "3",
"4": "4",
"5": "5"
},
"Firmware Update Delivery Method": "2",
"Package": {
"noValue": true
},
"Package URI": "",
"State": "0",
"Update": {
"noValue": true
},
"Update Result": "0"
}
},
"LWM2M APN Connection Profile": {},
"LWM2M Cellular Connectivity": {
"0": {
"6": "0.0",
"Activated Profile Names": {},
"Active Power Saving Modes": "3",
"Active Timer": "2",
"PSM Timer": "600",
"Release Assistance Indication Usage": "0",
"eDRX parameters for NB-S1 mode": "00",
"eDRX parameters for WB-S1 mode": "00"
}
},
"Location": {
"0": {
"Altitude": "0.0",
"Latitude": "50.08345252257777",
"Longitude": "19.901341675428398",
"Radius": "0.0",
"Timestamp": "2022-08-11T10:00:07Z",
"Velocity": "00c20003"
}
},
"LwM2M Access Control": {},
"LwM2M Server": {
"1": {
"Binding": "U",
"Bootstrap on Registration Failure": {
"noValue": true
},
"Communication Retry Count": "1",
"Communication Retry Timer": "0",
"Communication Sequence Delay Timer": "1",
"Communication Sequence Retry Count": "0",
"Disable": {
"noValue": true
},
"Lifetime": "60",
"Mute Send": "false",
"Notification Storing When Disabled or Offline": "true",
"Registration Update Trigger": {
"noValue": true
},
"Short Server ID": "1"
}
},
"Portfolio": {},
"Push button": {
"0": {
"Application Type": "Fake demo Button",
"Digital Input Counter": "0",
"Digital Input State": "false"
}
},
"Temperature": {
"0": {
"Max Measured Value": "39.0",
"Max Range Value": "42.0",
"Min Measured Value": "5.0",
"Min Range Value": "0.0",
"Reset Min and Max Measured Values": {
"noValue": true
},
"Sensor Units": "Cel",
"Sensor Value": "31.0"
}
}
} |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
AVSystem is a Nordic Partner that provides LwM2M connectivity for the 9160.
We want to demonstrate using the nRF Asset Tracker how the data provided by devices connected to Coiote can be made available in AWS so customers can use AWS services for their own business needs and build IoT products using the nRF9160.
For this we can leverage the existing nRF Asset Tracker for AWS implementation and add components that convert the data model that Coiote's AWS integration uses, to convert it to the nRF Asset Tracker data model for AWS, so it can be used by the existing implementation.
These components should be implemented as transparent pluggable modules, so users can follow the Getting Started Guide to set up the nRF Asset Tracker for AWS, and then enable the additional modules for the Coiote integration.
This will be implemented using a two step conversion process:
lwm2m-types
which defines a compact JSON notation for expressing LwM2M. This has advantages over using Coiote's format directly because it is not conflict free in it's keys and uses verbose english strings as which adds unnecessary overhead to the JSON document. Coiote's format is also currently not documented. Coiote devices are named using the formaturn:imei:NNNNNNNNNNNNNNN
and they have adatamodel
named shadow.Object definitions
Objects are defined by customers, through uploading the LwM2M XML schema.
The conversion uses HOCON to express the values in JSON.
Objects that are written by the Coiote service are documented in this JSON file.
The format is not conflict free, and the expression use string values for numbers, which is both to this being a proof of concept.
Related
Previous notes: #338
Beta Was this translation helpful? Give feedback.
All reactions