Netris1

Description of the device

The model NETRIS®1 is a WIKA radio unit to which standard sensors can be connected in order to bring the measured data wirelessly to a cloud for big-data analysis. It uses the licence-free LoRaWAN® and Bluetooth® radio standards and is used, for example, on mobile equipment and remote measuring points. Thanks to intelligent measurement and transmission control and a replaceable battery, the radio unit can be operated over a long battery life. The radio unit receives the data via connected measuring instruments with a standard signal of 0 ... 10 V or 4 ... 20 mA or an RTD in accordance with the Pt100/Pt1000 standard in 2- or 3-wire technology. The fully encapsulated instrument with IP65 ingress protection transmits the received data continuously to a cloud via configurable data packets with LoRaWAN® or Bluetooth®. Wireless transmission via LoRaWAN® (“Long Range Wide Area Network”) is based on LPWAN technology (“Low Power Wide Area Network”) to enable high transmission ranges and long battery life. A version made of stainless steel is available or applications with harsh ambient conditions. The instrument can be easily configured via the cloud and the LoRaWAN network or via the Bluetooth® interface. Thanks to the compatibility with numerous WIKA measuring instruments and the two available radio standards, LoRaWAN® for the kilometre range, and Bluetooth® for the metre range, the radio unit can be flexibly configured. Configuration is possible both via the cloud and on-site using Bluetooth® and the “myWIKA wireless device” app. The WIKA radio unit NETRIS®1 is part of the WIKA IIoT solution. With this, WIKA offers a holistic solution for your digitalisation strategy.

---

For more information see product site.

NETRIS1 Parser Quick Start

Parser API

All functions are pure (no global mutation) except setMeasurementRanges which updates internal range configuration for subsequent decodes.

Types:

Input types:

interface UplinkInput {
  fPort: number // LoRaWAN FPort
  bytes: number[] // Raw payload as array of unsigned bytes (0-255)
  recvTime?: string // Optional ISO timestamp (if your LNS provides it)
}

interface HexUplinkInput {
  fPort: number // LoRaWAN FPort
  bytes: string // Raw payload as hex-encoded string (case-insensitive, even length)
  recvTime?: string // Optional ISO timestamp (if your LNS provides it)
}

Return type (shared by all decode helpers):

type Result = {
  data: Record<string, any> // Parsed key/value pairs
  warnings?: string[] // Non-fatal anomalies
} | {
  errors: string[] // Fatal or structural issues only
}

To understand the data field, take a look at the examples and the schema definition.

Supported channels to identify different sensors by:

// Is used in the returned data
type ChannelName = 'measurement'

Channels that support adjusting the measurement range:

type AdjustableChannelName = 'measurement'

Channel Configuration:

Channel Name	Default Min	Default Max	Unit	Configurable
measurement	0	10	°C/°F/V/mA/%	Yes

*Unit and range depend on device configuration. Check device specifications or identification frames for actual unit and range.

decodeUplink(input)

function decodeUplink(input: UplinkInput): Result

decodeHexString(hexInput)

function decodeHexString(hexInput: HexUplinkInput): DecodeResult

bytes must have even length; case-insensitive.

setMeasurementRanges(channel, range)

// Will throw on invalid channel name or if the channel disallows range updates
function setMeasurementRanges(
  channelName: AdjustableChannelName,
  range: {
    start: number
    end: number
  }
): void

Applies to future decodes only.

adjustRoundingDecimals(decimals)

// Smartly adjust number of decimals for rounded values
// Impacts all numeric values in all outputs
// Default is 4
function adjustRoundingDecimals(decimals: number): void

Applies to future decodes only.

Verifying Measurement Ranges

Critical: The default measurement range (0-10) is a placeholder and likely does not match your device. NETRIS1 devices are highly configurable and support various sensor types (temperature, current, voltage, resistance). Always verify the actual range and unit from one of these sources:

1. Device specifications from your purchase order or datasheet
2. Identification frames sent by the device after activation

Using incorrect ranges will result in incorrect measurement values in all data messages.

TULIP3 Identification Frames

For devices using TULIP3 protocol, the first uplinks after device activation include identification messages (message type 20/0x14, subtype 1/0x01) that report the actual measurement configuration:

Example TULIP3 identification frame:

{
  "data": {
    "messageType": 20,
    "messageSubType": 1,
    "identification": {
      "sensor1": {
        "channel1": {
          "measurand": "Temperature",
          "unit": "°C",
          "minMeasureRange": -40,
          "maxMeasureRange": 85,
          "channelName": "measurement"
        }
      }
    }
  }
}

TULIP2 Identification Frames

For devices using TULIP2 protocol, identification messages (message type 6/0x06) report similar information:

Example TULIP2 identification frame:

{
  "data": {
    "messageType": 6,
    "configurationId": 1,
    "productIdName": "NETRIS1",
    "channels": [
      {
        "channelId": 0,
        "channelName": "measurement",
        "measurand": "Temperature",
        "measurementRangeStart": -40,
        "measurementRangeEnd": 85
      }
    ]
  }
}

---

Quick Start

1. Check your device's actual measurement range and unit from purchase configuration, device specifications, or identification frames (see above)
2. Add configuration code below at the bottom of your parser file
3. Add wrapper function if your network server is non-compliant: function decode(input) { return decodeUplink(input) }

Configuration code (add at bottom of parser file):

// Replace values with your device's actual measurement range from specifications or identification frames
setMeasurementRanges('measurement', { start: -40, end: 85 })

NPM Module Inclusion

Device	Included	Factory function
NETRIS1	❌	❌