Wireless M-Bus Range Extender /
/
User Manual Version 1.0
Page 26 of 32
{
"applicationID":"30",
"applicationName":"applicationName",
"deviceName":"deviceName",
"devEUI":"qqu7zN3u7/8=",
"rxInfo":[
{
"gatewayID":"ESIzRFVmd4g=",
"time":null,
"timeSinceGPSEpoch":null,
"rssi":-66,
"loRaSNR":7,
"channel":7,
"rfChain":1,
"board":0,
"antenna":0,
"fineTimestampType":"NONE",
"context":"8/68TA==",
"uplinkID":"7lpqX2uSSzyrlulk989yeA=="
}
],
"txInfo":{
"frequency":868500000,
"modulation":"LORA",
"loRaModulationInfo":{
"bandwidth":125,
"spreadingFactor":7,
"codeRate":"4/5",
"polarizationInversion":false
}
},
"adr":true,
"dr":5,
"fCnt":11,
"fPort":68,
"data":"gPoAqV4mQxEiM0RVZneIGgACAwQFBgcICQoLDA0ODxAREhMUFRYXGBkaG//6AKle
J0MRIjNEVWZ3iBsAAgMEBQYHCAkKCwwNDg8QERITFBUWFxgZGhsc//oAqV4oQxEiM0RVZneI
HAACAwQFBgcICQoLDA0ODxAREhMUFRYXGBkaGxwd//oAqV4pQxEiM0RVZneIHQACAwQFBgcI
CQoLDA0ODxAREhMUFRYXGBkaGxwdHv8=",
"objectJSON":"",
"tags":{
}
}
and is located in the following code snippets in the parameter
.
deviceEvent
Javascript offers the possibility to access the values of the json data via the property names.
To identify the uploaded WM-Bus packets, the port must be considered (see
)
: