Porovnávané verzie

Kľúč

  • Tento riadok sa pridal
  • Riadok je odstránený.
  • Formátovanie sa zmenilo.

...

Value typeAddress
(address type)
Description
Ai, Di, Ci, Qi, TxtI
Kotva
pt_payload
pt_payload
Payload

I/O tags parsed from payload. Address (Address) depends on device type (Device Type parameter). Address is not case sensitive.
A special case is a blank address - the I/O tag will contain the entire payload (after relevant decoding depending on Payload Encoding parameter).
The following tables indicate the addresses for each device type:

Payload addresses for device type of OEM Device
address depends on the specific implementation (dll library).

Payload addresses for device type Adeunis RF Field Test Device

AddressDescription
StatusStatus byte of device.
TriggerAccelerometerThe True value means that the message sending was initiated by an accelerometer.
TriggerButtonThe True value means that the message sending was initiated by a button.
TemperatureMeasured temperature (-128 °C .. 127°C).
GpsLatitudeLatitude (0-90 degrees) from GPS sensor.
Note: GPS data may be missing if the device has no GPS signal.
HemisphereSouthThe True value means that the latitude is south (the device is in the southern hemisphere).
GpsLongitudeLongitude (0-180 degrees) from the GPS sensor.
HemisphereWestThe True value means that the latitude is west (the device is in the western hemisphere).
GpsQualityReceptionGPS signal reception quality: 1 Good, 2 Average, 3 Poor
QpsQualitySatellitesNumber of visible GPS satellites.
UplinkCounterPacket uplink counter (packets sent from the device to the LoRaWAN gateway).
DownlinkCounterPacket uplink counter (packets sent to the device from the LoRaWAN gateway).
BatteryLevelBattery voltage in mV.
RSSIIndicator of strength of the received signal (Received Signal Strength Indicator) - value between 0-255. Payload contains the field only if  it has previously been written to the device (sending data from the LoRaWAN gateway to the device).
SNRSignal Noise Ratio v dB (-128 .. 127). Payload contains the field only if  it has previously been written to the device (sending data from the LoRaWAN gateway to the device).



Payload addresses for device type SolidusTech IndoorUNI Sensor

AddressDescription
ADRAdaptive Data Rate (optimizing data transfer speed and energy consumption). Value True indicates that ADR is on.
DataRateData Rate (data transmission rate) 0-5.
SNRSignal Noise Ratio v dB (-128 .. 128).
BatteryLevelBattery voltage in mV.
TemperatureTemperature (-125.99°C .. 125.99°C) with 0.1°C resolution.
HumidityRelative humidity (0.0%-100%) with 0.1% resolution.
PowerAdapterThe True value means that the device is connected to a power adapter, the False value means that it is powered by battery (always False for firmware version FW 0.2.2 and lower).
ContactThe True value means that an auxiliary contact is switched on (always False for firmware version FW 0.2.2 and lower).



Payload addresses for device type SolidusTech miniUNI DS18B20 Sensor

AddressDescription
BatteryLevelBattery voltage in mV.
SNRSignal Noise Ratio of previous payload in dB. It applies after ACK is received. Value 127 indicates an undefined value (no ACK or downlink packet was received from LoRaWAN gateway).
TemperatureTemperature (-25°C .. 85°C) with resolution 0.1°C.


Payload addresses for device type Adeunis RF LoRaWAN TEMP (ARF8180BA)

AddressDescription
FrameCounterInternal message counter going from 0 to 7.
BatteryLowLow battery indicator. Has values True or False.
HWErrorIndicator of hardware error in a device (temperature sensor error etc.).
InternalTempThe value of the temperature sensor located in the device housing with a resolution of 0.1 °C.
ExternalTempThe value of the temperature sensor located on external wire with a resolution of 0.1 °C.


Payload addresses for device type  Codea WZU-SG (Landis+Gyr Ultraheat T550)

AddressPopis
Energy
Aktuálne prepravené množstvo tepla (v stotinách
Current amount of energy (in hundredths of GJ)
Volume
Aktuálne prepravený objem vody (v desatinách
Current volume (in tenth of m3)
ErrorFlag
Chybový príznak

Error flag

MissingTime
Počet poruchových hodín (v hod
Number of error hours (in hours)
StatusStatus
modulu-dôvod odoslania správy
of module-reason for sending data:

0x00 - Ok
0x10 -

Chyba čítania merača (zlý formát dát

Error of reading a meter (bat format of E,V data..)
0x20 - Install
0x30 - JMP
0x40 -

Porucha merača

Error of meter


Ai, Di, Ci, Qi, TxtI
Kotva
pt_envelope
pt_envelope
Envelope
I/O tag parsed from envelope of message. The address is the name of the field in the envelope of message.
Note: For JSON messages that can be structured, the syntax level1.level2.level3 ... is supported, e.g. rx.moteeui and if they contain fields (indexed from 1) then also level1[index1].level2[index2].level3 ... syntax, e.g. rx.gwrx[1].time.

Example of JSON message for Connection Type=Kerlink IoT Station SPN (added spacing and alignment for better legibility):
{ 
  "rx": {
    "moteeui": "00-00-00-00-00-1e-fc-1d", 
    "userdata": {
        "seqno": 77, 
        "port": 1, 
        "payload": "NzM3RjAwZTgwMA==", 
        "motetx": {
            "freq": 868500000,
	    "modu": "LoRa",
	    "datr": "SF7BW125",
	    "codr": "4/5"
	}
     },
     "gwrx": [
        {
         "time": "2017-07-05 16:06:52",
	 "chan": 2,
	 "rfch": 0,
	 "rssi": -33,
	 "lsnr": 7.5
        }
     ]
  }
}
	
I/O tags of envelope may have addresses e.g. rx.moteeui, rx.userdata.seqno, rx.userdata.motetx.freq, rx.gwrx[1].time.

Example of JSON message for Connection Type=MQTT Client (JSON via MQTT) (added spacing and alignment for better legibility):
{
  "app_id":"ipesoft-test",
  "dev_id":"fieldtestdevice",
  "hardware_serial":"0018B2000000147D",
  "port":2,
  "counter":549,
  "payload_raw":"niNJElVwAYQ5UBYfBBBN",
  "metadata":{
    "time":"2017-08-10T08:12:26.06860368Z",
    "frequency":867.5,
    "modulation":"LORA",
    "data_rate":"SF7BW125",
    "coding_rate":"4/5",
    "gateways":[
      {
        "gtw_id":"eui-000000000003080b",
	"timestamp":705621508,
	"time":"2017-08-10T08:12:26.434682Z",
	"channel":5,
	"rssi":-34,
	"snr":7.8,
	"latitude":49.20927,
	"longitude":18.73184,
	"altitude":359
      }
    ]
  }
}
	
I/O tags of envelope may have addresses e.g. dev_id, metadata.time, metadata.gateways[1].latitude.
TxtI
Kotva
pt_all_data
pt_all_data
All data
I/O tag, that will contain the complete received message - the whole envelope (e.g. JSON message). The I/O tag is intended for debugging purposes and for eventual processing of the entire message in the script.
TxtO
Kotva
pt_write_mqtt
pt_write_mqtt
Write (MQTT)
I/O tag for writing. Currently implemented just for Connection Type=MQTT client and tested towards cloud TheThings.Network.
The value of I/O tag is considered to be a payload that will be encoded (depending on the Payload Encoding parameter) and inserted into the message template defined by the MQTT Publish Format parameter, where it will replace the #PAY# string. The resulting message will be sent to the MQTT server.

...