LumiRing AUTOMATION User manual

AUTOMATION
Industrial MQTT Gateway
Manual

2022
Automation
Manual_En_V3.0

2022
Automation
Manual_En_V3.0
CONTENTS
PURPOSE AND GENERAL INFORMATION 3
Usage diagram 4
Specification 4
Connection and sockets description 6
Indication description 6
Relay work mode 7
Relay Dry mode 7
Relay Wet mode 8
INSTALLATION RECOMMENDATIONS 8
Wiegand device connection 8
Heave loads switching 9
Inductive loads connection 9
EXT1 and EXT2 example of connection 9
LUMIRING RFID reader 10
Specification 10
MQTT CONNECTION SETTING 11
DHCP Settings (Zero touch provision) 11
Web-based interface 12
Network settings 12
Local Wi-Fi Access point settings 13
MQTT Connection 13
MQTT Topic settings 14
CONFIGURATION BY MQTT 15
Device Inputs 16
Multifunctional device ports EXT 1 & EXT 2 17
Sensor Tool 19
Device Outputs 20
Example of device configuration 21
CONTROL COMMANDS 23
Set Date & Time 23
Device restart 23
Control device outputs 23
DEVICE DATA PUBLICATION 24
FAQ 25

2022
Automation
Manual_En_V3.0
PURPOSE AND GENERAL INFORMATION
The MQTT Gateway controller provides a simple way to collect information from various
sensors and automation systems while, at the same time, giving control to actuators and
other devices. The universal Wiegand port allows connectivity of cost-effective solutions
that work with RFID tags, QR, and barcodes. Device functionality can be extended by
support of any BLE sensor: water leak sensor, smoke sensor, motion sensor etc.
With native MQTT API protocol, you can quickly and efficiently integrate virtually any
system by embedding a data stream into a website, service, or control software like SCADA.
Mass scale configuration and central management – manage thousands of devices. From
initial no-touch Configuration to any updates, changes, adjustments – you name it.
●Centralized Device Management
●Highly configurable, Automated
Deployment
●Reliable, Industry approved
technology
●MQTT Protocol, IP V4, DHCP, DNS,
NTP
●Galvanic input isolation
●Triple power source:
o12v
o24v
oPOE 24W IEEE802.3at and
IEEE802.3af compliant
●Two communication channels:
oWi-Fi
oEthernet
●Interface RS 485 (Modbus)
●Universal Wiegand interface:
oRFID reader support
oQR-code/BAR–code reader support
oKeypad support
●DALLAS 1-WIRE support
●Two modes for the relay out:
●Dry/Wet relay. Output Interfaces as potential free contact or 24V level
oDry relay mode is not directly provided with power from the switch and is used in
switching devices that provide isolation and give a wide variety of output voltage
options.
oWet relay mode is automatically given power when the switch has power, and
the main advantages are the simplicity of wiring and the consistency of voltage
levels, making troubleshooting much easier.
●The Device can be installed in the field or in the cabinet on a DIN rail

2022
Automation
Manual_En_V3.0
Unlimited customization options and simple integration allow the gateway to be used
in automation systems of any level.
Cloud or on-premise MQTT servers supported. You can run such a server on any
Linux machine, even Raspberry PI. For device management, customers can use any
SCADA or automation system which can work with MQTT server data.
Usage diagram
Specification
#
Parameters
Value
Electrical
1 Power supply 12-24V
2
POE 24W IEEE802.3at and IEEE802.3af compliant
(option)
YES
3
Average rated current consumption (at a voltage of
12V):
0,11А
- Output without load, no more
4
Maximum current consumption (at a voltage of 12V):
0,3А
- Output without load, no more

2022
Automation
Manual_En_V3.0
5
Maximum switching current:
12в 3А
24в 5А
Relay out
EXT 5
6
Maximum switching load voltage outputs:
Relay out
24V
EXT 5
24V
7
Power input protection: Short circuit Polarity reversal
EXT4 output protection Overheating
Short circuit
Power output protection EXT1 and EXT2 Overheating
Short circuit
Functional
8
Communication channels
Wi-Fi 2,4Ghz / Ethernet
9
Events memory during standalone operation
1024
10
EXT 1
Mode: Logic level In/Logic level Out
2 Inputs / 2 Outputs
Mode: Wiegand
Wiegand interface
2 Outputs
Mode: 1-Wire
2 x 1-Wire interfaces
2 Outputs
11
EXT 2
Mode: Logic level In/Logic level Out
2 inputs / 2 outputs
Mode: Wiegand
Wiegand interface
2 Outputs
Mode: 1-Wire
2 x 1-Wire interfaces
2 Outputs
12
EXT 3 - Logic level input
2
13
EXT 4 - Logic level input
2
14
EXT 5 - Open collector output (max 1.5A)
1
15
Relay out
1
16
Setup configuration
Web-based interface
17
Support for OTA / NTP / MQTT
YES
18
Support initial configuration from DHCP
YES
19
Internal sensor test tool
YES
20
Integration way
MQTT API
21
Maximum wired interface distance:
-RS485 (Modbus RTU)
-Wiegand
-Dallas 1-WIRE
-Ethernet
1000 m / 3280 ft
100 m /328 ft
100 m /328 ft
100 m /328 ft
Operational
22 Dimensions
(L)110x(W)75х(H)35 mm
(L)4.3x(W)2.9x(H)1.37 inch
23 Working temperature range
-30 ~ + 70 С
-22 ~ 158 F
24
Housing material
ABS plastic

2022
Automation
Manual_En_V3.0
Connection and sockets description
The Device has two multifunctional ports EXT 1 and EXT 2. Users can set each mode
independently by a configuration JSON file. Each port can be set to one of three modes:
●Mode IN/OUT – logic level Inputs / Outputs. In this mode, each port EXT1 and EXT2
has 2 Inputs and 2 Outputs.
●Mode Wiegand & Outputs – Wiegand device connection mode. Suitable for
connecting any Reader with Wiegand Interface – such as RFID reader, QR Code
reader, barcode reader. Device is supported by the following Wiegand modes:
Wiegand 26, Wiegand 34. In this mode, the device still has 2 Outputs which can be
used to control Led in any third-party readers or to control any actuators.
●Mode 1-WIRE & Outputs - In this mode, each port is configured as two 1-Wire
interfaces. Each 1-WIRE interface can support up to 10 sensors. In total Device can
aggregate information from 40 such sensors. The delay period for querying each
sensor must be taken into consideration - it will take up to 43 seconds to poll all
sensors. In this mode, device still has 2 Outputs that can be used to control any
actuators.
Indication description
LED
OFF
ON
BLINK

2022
Automation
Manual_En_V3.0
D1
Power trouble
D2
Relay Dry
mode
Relay Wet
mode
D3
No power
Power ON
D4
Not used
Not used
Not used
D5
No Ethernet
connection
Ethernet
connected
OTA update
in progress
Relay work mode
To change the operating mode of the relay, First, de-energize and dismantle the Device.
Remove the top cover by unscrewing the four fixing screws from the bottom of the case. Remove
the top cover by unscrewing the four screws from the bottom of the case. Select the necessary
mode using the switch on the board according to the picture. Re-energize the Device. Make sure
the D2 LED is on. Close the cover and re-fasten the screws of the Device.
Relay Dry mode
Relay Dry mode The «DRY MODE» is the most common mode which can be used in the
following scenarios:
●When your actuator needs a different power supply: to switch to an external power, select
DRY MODE and use NO or NC and C, and wire to the external supply. That allows the ability
to control the actuators (lock, etc.), which use different power supplies.
●If your actuator needs to shortcut, two contacts to be activated
Example: Different power source for actuators
Example: 2 contact shortcuts

2022
Automation
Manual_En_V3.0
Relay Wet mode
The «WET MODE» is a special mode that
provides power directly to the actuators (Lock, etc.). To
power actuators (Lock, etc.) without an external
supply, select «WET MODE» and connect locking
hardware to NO and GND (for fail-secure locks) or NC
and GND (for fail-safe locks). In this work mode, relay
out works in the same algorithm as open collector out.
INSTALLATION RECOMMENDATIONS
Wiegand device connection
The length of the communication line via the Wiegand interface should be no more than
100 m (328 ft). This interface standard has limited protection against interference - we do not
recommend laying it parallel to power cables or next to other possible sources of interference
(daylight lamps, etc.). The minimum distance to power cables is at least 0.5m (1,64 ft). If your
communication line exceeds that length - we recommend using a UTP 5E cable. If you need to
supply power from the Device to any third-party reader, you must be sure the third-party reader
supports 24VDC. You must use a separate power supply if the third-party reader does not support
24VDC.

2022
Automation
Manual_En_V3.0
Example: Wiring for connecting the Device to a third-party reader if the wiring distance exceeds
5 m(1,64 ft).
Heave loads switching
If you need galvanic isolation from the
controlled Device (lock, gate, etc.), or you
need control of high-voltage devices or
devices with significant current consumption
(exceeding the rated current for the output), it
is recommended to connect these devices
via a relay. It also improves the reliability of the
system.
Inductive loads connection
When using inductive loads (electromagnetic,
electromechanical locks or motors and etc.), we
strongly recommend using a protective diode. Suitable
diodes 1N5400, 1N5408, 1N5821, HER301, and similar.
Instead of diodes, with varistors no need to check
polarity. Varistors VCR-07D101K S07K60, TVR07101,
GNR-07D101K, or similar are suitable.

2022
Automation
Manual_En_V3.0
EXT1 and EXT2 example of connection
LUMIRING RFID READER
The Smart reader is designed to work with any controller
of the access control system. The reader supports work with RFID
identifiers at 125Khz frequencies. The initial setup of the reader
must be made via a Web-based interface, which allows for
changing settings and updating device firmware. Please use
RS485 connection for high-speed RFID read
Specification
#
Parameter
Value
Electrical
1
Supply voltage
9-24 V
2 Average rated current consumption (at voltage 12V):
- No-load output, not more 0,11А
3 Maximum current consumption (at voltage 12V):
- No-load output, not more 0,5А
Functional
4 Wireless interfaces Wi-Fi 2,4Ghz
Bluetooth 4.1
5 Wired interfaces Wiegand
RS485
6
Support for 125Khz identifiers
EM Marine series
YES

2022
Automation
Manual_En_V3.0
7
Maximum distance of wired interface:
-RS485
-Wiegand
1000 m / 3280 ft
100 m /328 ft
Operational
8
Overall dimensions
(D)60x(H)15 mm
(D)2.36x(H)0.59 inch
9 Working temperature range
-30 ~ +70 C
-22 ~ 158 F
11
IP Protection Level
IP65
11
Enclosure material
ABS Fire Retardant
MQTT CONNECTION SETTING
DHCP Settings (Zero touch provision)
To connect a device to the MQTT server, you need to set up the connection settings. The
Device has two configuration options:
1. Through the Web interface of the Device. You must set up devices one by one.
2. Through the DHCP server (Default). You can fast deploy many devices at the same time. The
feature works the same as Zero Touch Provision.
In the case of working through a DHCP server, the connection parameters must first be
set in the additional fields of the DHCP server. The connection parameters are specified as a JSON
string. The DHCP server option code must be 226!
Figure 1. Example of an additional parameter on a DHCP server

2022
Automation
Manual_En_V3.0
A string from the Value field might look like this:
Description
"location"
prefix for building MQTT topics.
"ipv4Mqtt"
the ip address of the MQTT server.
"ipv4MqttPort"
MQTT server port.
"mqttUser"
login to the MQTT server.
"mqttPassword"
password for the MQTT server.
"timeOffset"
time offset according to the local time zone, specified in seconds.
Web-based interface
A description of all configuration and management options will be described below. Also,
the connection parameters of the configured Device, if necessary, can be changed directly by
the corresponding command via the MQTT server. The new connection settings, in this case, will
be applied after the Device is rebooted.
An alternative option for specifying connection parameters is the Device's Web interface.
The default IP address of the Device is 192.168.1.120. For first-time entry, leave the “Login” and
“Password” fields empty – just press «Submit» We strongly recommend you set your own Login
and Password for web-interface access.
{
"location":"lumiring",
"ipv4Mqtt":"192.168.1.36",
"ipv4MqttPort":1883,
"mqttUser":"admin",
"mqttPassword":"admin",
"timeOffset":7200
}

2022
Automation
Manual_En_V3.0
Network settings
The network settings of the Device can be changed on the tab Configuration (1)->Network
(2)->Main (3)
Users can select Network type (4). Ethernet
(Default) or Wi-Fi.
Connection type (5) give possibilities to use
DHCP (Default) or manual network settings.
The Default HTTP port is 80(6). Port used
for access to Web-based interface. It can
be changed depending on customer
needs.
Local Wi-Fi Access point settings
The local access point can operate in three modes. The choice of the mode is made by
the selector (1)
- Always-ON
The Device's local hotspot is always on
and is displayed when other devices are
scanning the Network.
- Always-ON + Hidden
The Device's local hotspot is always
enabled but does not show up when
scanning the Network with other devices.
Connection is possible if the SSID is
known.
- Timed ON (default)
The local point of the Device is activated for the time specified in the Timer field (2). The
countdown starts from the power supply of the Device. After the timer expires, the Wi-Fi point
will be turned off.
By default, the local hotspot is not password protected. We strongly recommend that you set
your own SSID name (3) and SSID password (4) during the initial setup.
MQTT Connection
Connection parameters to the MQTT server can be specified on the Configuration (1)-
>Network (2)->Cloud (3)-Server (4) tab. To manually specify the parameters for connecting to
MQTT, switch the "Cloud requirements source" (5) to the "Manual" position. In «DHCP mode,» the
Device tries to receive all information from your DHCP server through the Zero touch provision

2022
Automation
Manual_En_V3.0
feature – which gives you the possibility fast deploy many devices through settings pointed in
the DHCP string in your router.
Required parameters are «MQTT Address»
(6) and «MQTT port» (7).
To set MQTT server credentials, you must
On the Configuration (1) ->Network
(2) ->Cloud (3) ->User Credentials tab (4) -
specify the Login (5) and password (6) for
the MQTT server.

2022
Automation
Manual_En_V3.0
MQTT Topic settings
On the Configuration (1) ->Network (2) ->Cloud (3)->Topic settings tab (4) - specify the
"Location" (5) field, and the rest of the topics will be built automatically. To apply the settings,
click the "Update" (6) button. And reboot your Device.
After receiving the connection
parameters, the Device will connect to the
MQTT server and publish its serial number
and the current time in the
"lumiring/presence/" topic(5). The Device
will repeat the message at the preset
interval. You should pay attention to the
fact that all the names of topics with which
the Device will work will be built, taking into
account the prefix from the "location"(6)
parameter!
For example, if "location" = "lumiring," then
the Device will subscribe to the following
topics:
"lumiring/operate/”(7) - To receive control
commands.
“lumiring/config/”(8) - To receive configuration commands.
The Device will post messages on the following topics:
“lumiring/ack/”(9) - Confirmation of received commands.
“lumiring/events/”(10) - Device events.
“lumiring/presence/”(5) - Heart-Bit signals.
Important! In published messages, the Device will identify itself with its serial number in the
“device” field. Also, the Device will only accept the control command in which the “device” field
matches its serial number.
CONFIGURATION BY MQTT
The Device has four ports for connecting external sensors and actuators (EXT-1, EXT-2,
EXT-3, EXT-4). To use the Device, you need to tell it how and in what mode its inputs / outputs
of ports will be used. The Configuration is set using the appropriate parameters in JSON format.
Operation legend: R – Read-only; WR – Write only; R/WR – Read & Write
Common device settings
Parameter
Data type
Description
Operation
device
String(16)
Device serial number (HEX)
R
location
String(16)
Prefix for building MQTT topics
R/WR

2022
Automation
Manual_En_V3.0
operateTopic
String(64)
The topic for control commands
R/WR
ackTopic
String(64)
The topic for acknowledging
received commands
R/WR
eventsTopic
String(64)
Event topic
R/WR
configTopic
String(64)
Configuration topic
R/WR
presenceTopic
String(64)
Topic for Heart-Bit
R/WR
ipv4Address
String(16)
IP address
R/WR
ipv4Mask
String(16)
Network mask
R/WR
ipv4Gw
String(16)
Gateway IP address
R/WR
ipv4Ntp
String(16)
NTP Server address
R/WR
ipv4Mqtt
String(64)
MQTT Server address
R/WR
ipv4MqttPort
Uint16
MQTT Server port
R/WR
mqttUser
String(32)
MQTT Username
R/WR
mqttPassword
String(32)
MQTT Password
R/WR
mqttTimeOut
Uint16
MQTT Connection Timeout (ms)
R/WR
mqttKeepAlive
Uint16
MQTT KeepAlive (ms)
R/WR
мessageDelay
Uint16
The delay between messages
(s)
R/WR
systemReboot
Uint8
Device reboot: «1»-On; «0»-Off
R/WR
systemRebootTime
String(8)
Schedules device reboot time
(Example 23:59). Default status:
Not set.
WR
timeOffset
Int16 Time offset according to the
local time zone (s) WR
sensorUnit
string
Temperature scale selection. «С» -
Сelsius. «F» - Fahrenheit
WR
presenceHeartBitInteval
Uint16
Heart–bit signal period (s)
WR
Device Inputs
The name of the input parameter is strictly assigned to the hardware input of the Device.
For the convenience of presenting data about the state of the input, when configuring, you can
override its name, for example:
In such a case, the Device will publish the name "switch1"
instead of "inputSensorName_0" and so on.
{
…….
"inputSensorName_0":"switch1",
"inputSensorName_1":"switch2"
}

2022
Automation
Manual_En_V3.0
TTL Inputs settings
Port name
Parameter
Type
Description
EXT 1
IN1
inputSensorReverse_0
Uint8
0 – active «0»,
1 – active «1»
inputSensorName_0
String(32) Input name
IN2
inputSensorReverse_1
Uint8 0 – active «0»,
1 – active «1»
inputSensorName_1
String(32) Input name
EXT 2
IN3
inputSensorReverse_2
Uint8
0 – active «0»,
1 – active «1»
inputSensorName_2
String(32) Input name
IN4
inputSensorReverse_3
Uint8
0 – active «0»,
1 – active «1»
inputSensorName_3
String(32) Input name
EXT 3
IN5
inputSensorReverse_4
Uint8
0 – active «0»,
1 – active «1»
inputSensorName_4
String(32) Input name
IN6
inputSensorReverse_5
Uint8
0 – active «0»,
1 – active «1»
inputSensorName_5
String(32) Input name
EXT 4
IN7
inputSensorReverse_6
Uint8
0 – active «0»,
1 – active «1»
inputSensorName_6
String(32) Input name
IN8
inputSensorReverse_7
Uint8
0 – active «0»,
1 – active «1»
inputSensorName_7
String(32) Input name
Multifunctional device ports EXT 1 & EXT 2
The 1W.x inputs of each port, EXT 1 and EXT 2 can be configured to work in 3 modes:
●Wiegand readers;
●Temperature sensors (1- Wire);
●Additional low-voltage TTL inputs;
The 1W.x inputs are configured in pairs. In other words, both 1W.x inputs of the same port can
only have one mode of operation at the same time. Port operating modes are set by the
“ext1_mode” and “ext2_mode” parameters, respectively. The operating modes are shown in the
tables below:

2022
Automation
Manual_En_V3.0
“ext1_mode”:
”RFID”
“tempSensor”
“extraInput”
1W.1
Wiegand input
Temperature sensor input [0..9]
TTL Input (0-5 v)
1W.2
Wiegand input
Temperature sensor input [10..19]
TTL Input (0-5 v)
OUT.1
TTL Out
TTL Out
TTL Out
OUT.2
TTL Out
TTL Out
TTL Out
“ext2_mode”:
”RFID”
“tempSensor”
“extraInput”
1W.3
Wiegand input
Temperature sensor input [19..29]
TTL Input (0-5 v)
1W.4
Wiegand input
Temperature sensor input [30..39]
TTL Input (0-5 v)
OUT.3
TTL Out
TTL Out
TTL Out
OUT.4
TTL Out
TTL Out
TTL Out
Parameter
Type
Description
Note
Output name 1W.1
tempSensor_id_0
String(16:32)
Sensor ID
(HEX)
tempSensorCalibrate_0
float
Correction factor
tempSensor_id_1
String(16:32)
Sensor ID
(HEX)
tempSensorCalibrate_1
float
Correction factor
tempSensor_id_2
String(16:32)
Sensor ID
(HEX)
tempSensorCalibrate_2
float
Correction factor
tempSensor_id_3
String(16:32)
Sensor ID
(HEX)
tempSensorCalibrate_3
float
Correction factor
tempSensor_id_4
String(16:32)
Sensor ID
(HEX)
tempSensorCalibrate_4
float
Correction factor
tempSensor_id_5
String(16:32)
Sensor ID
(HEX)
tempSensorCalibrate_5
float
Correction factor
tempSensor_id_6
String(16:32)
Sensor ID
(HEX)
tempSensorCalibrate_6
float
Correction factor
tempSensor_id_7
String(16:32)
Sensor ID
(HEX)
tempSensorCalibrate_7
float
Correction factor
tempSensor_id_8
String(16:32)
Sensor ID
(HEX)
tempSensorCalibrate_8
float
Correction factor
tempSensor_id_9
String(16:32)
Sensor ID
(HEX)
tempSensorCalibrate_9
float
Correction factor
Output name 1W.2
tempSensor_id_10
String(16:32)
Sensor ID
(HEX)
tempSensorCalibrate_10
float
Correction factor
tempSensor_id_11
String(16:32)
Sensor ID
(HEX)
tempSensorCalibrate_11
float
Correction factor
tempSensor_id_12
String(16:32)
Sensor ID
(HEX)
tempSensorCalibrate_12
float
Correction factor
tempSensor_id_13
String(16:32)
Sensor ID
(HEX)
tempSensorCalibrate_13
float
Correction factor
tempSensor_id_14
String(16:32)
Sensor ID
(HEX)
tempSensorCalibrate_14
float
Correction factor
tempSensor_id_15
String(16:32)
Sensor ID
(HEX)
tempSensorCalibrate_15
float
Correction factor
tempSensor_id_16
String(16:32)
Sensor ID
(HEX)
tempSensorCalibrate_16
float
Correction factor
tempSensor_id_17
String(16:32)
Sensor ID
(HEX)
tempSensorCalibrate_17
float
Correction factor

2022
Automation
Manual_En_V3.0
tempSensor_id_18
String(16:32)
Sensor ID
(HEX)
tempSensorCalibrate_18
float
Correction factor
tempSensor_id_19
String(16:32)
Sensor ID
(HEX)
tempSensorCalibrate_19
float
Correction factor
Output name 1W.3
tempSensor_id_20
String(16:32)
Sensor ID
(HEX)
tempSensorCalibrate_20
float
Correction factor
tempSensor_id_21
String(16:32)
Sensor ID
(HEX)
tempSensorCalibrate_21
float
Correction factor
tempSensor_id_22
String(16:32)
Sensor ID
(HEX)
tempSensorCalibrate_22
float
Correction factor
tempSensor_id_23
String(16:32)
Sensor ID
(HEX)
tempSensorCalibrate_23
float
Correction factor
tempSensor_id_24
String(16:32)
Sensor ID
(HEX)
tempSensorCalibrate_24
float
Correction factor
tempSensor_id_25
String(16:32)
Sensor ID
(HEX)
tempSensorCalibrate_25
float
Correction factor
tempSensor_id_26
String(16:32)
Sensor ID
(HEX)
tempSensorCalibrate_26
float
Correction factor
tempSensor_id_27
String(16:32)
Sensor ID
(HEX)
tempSensorCalibrate_27
float
Correction factor
tempSensor_id_28
String(16:32)
Sensor ID
(HEX)
tempSensorCalibrate_28
float
Correction factor
tempSensor_id_29
String(16:32)
Sensor ID
(HEX)
tempSensorCalibrate_29
float
Correction factor
Output name 1W.4
tempSensor_id_30
String(16:32)
Sensor ID
(HEX)
tempSensorCalibrate_30
float
Correction factor
tempSensor_id_31
String(16:32)
Sensor ID
(HEX)
tempSensorCalibrate_31
float
Correction factor
tempSensor_id_32
String(16:32)
Sensor ID
(HEX)
tempSensorCalibrate_32
float
Correction factor
tempSensor_id_33
String(16:32)
Sensor ID
(HEX)
tempSensorCalibrate_33
float
Correction factor
tempSensor_id_34
String(16:32)
Sensor ID
(HEX)
tempSensorCalibrate_34
float
Correction factor
tempSensor_id_35
String(16:32)
Sensor ID
(HEX)
tempSensorCalibrate_35
float
Correction factor
tempSensor_id_36
String(16:32)
Sensor ID
(HEX)
tempSensorCalibrate_36
float
Correction factor
tempSensor_id_37
String(16:32)
Sensor ID
(HEX)
tempSensorCalibrate_37
float
Correction factor
tempSensor_id_38
String(16:32)
Sensor ID
(HEX)
tempSensorCalibrate_38
float
Correction factor
tempSensor_id_39
String(16:32)
Sensor ID
(HEX)
tempSensorCalibrate_39
float
Correction factor
Sensor Tool