DMT01

1. Introduction

1.1 What is DMT01 Wireless Meat Thermometer

The DMT01 is a professional-grade wireless meat thermometer engineered for accurate, real-time temperature monitoring in commercial cooking environments. Ideal for restaurants, central kitchens, catering services, and food processing facilities, the DMT01 ensures consistent results across various cooking methods—including grilling, smoking, roasting, deep-frying, sous vide, baking, and more. Its precise monitoring helps improve cooking efficiency, ensure food safety, and meet HACCP compliance standards.

The system consists of two components:

Food-grade BLE High-Temperature Probe – A durable, high-heat resistant probe that measures internal food temperature during cooking.
Charging Base with BLE to LoRAWAN converter – This base not only charges the probe but also acts as a communication bridge. It receives temperature data from the BLE probe and transmits it via the LoRaWAN long-range wireless protocol to your IoT platform or monitoring system.

With its dual wireless support (BLE for close-range/small design and LoRaWAN for long-range data transmission), the DMT01 is ideal for both home cooking enthusiasts and commercial kitchen environments seeking smart, connected temperature monitoring.

1.2 Features

Wireless Meat Thermometer – Designed for accurate and reliable cooking temperature monitoring
Food-Grade Probe – Safe for food contact and dishwasher-compatible for easy cleaning
BLE 5.1 Broadcasting – Supports real-time local data transmission via Bluetooth Low Energy
LoRaWAN Connectivity – Enables long-range, low-power data transmission to IoT platforms
Smart Uplink Triggering – Supports periodic data reporting and real-time alerts on temperature thresholds

1.3 Specification

Common DC Characteristics:

Supply Voltage: +5v via USB Type-C
Operating Temperature:

Food Probe Spec:

Length: 126mm
Diameter: 6mm
Food temperature: -30 ~110 °C, Accuracy: ±0.5°C
Ambient temperature: 0 ~380°C, Accuracy: ±5°C
Wireless: BLE 5.1
Distance: ≥ 30m (In an open environment)
Battery: 4mAh
Recharge time: ＜ 2 hours
Battery Duration: ＞30 hours
IP Rate: IP67, Dish Washer proof

Charger Spec:

BLE v5.1 + LoRaWAN
Power Input: USB Type-C, +5v
Battery: Li-ion , 3000mAh
Recharge time: ＜ 2 hours

1.4 Applications

Commercial Kitchen
Restaurant
Catering
Food Processing
Central Kitchen
Cloud Kitchen
HACCP Monitoring
Food Safety
Meat Factory
Industrial Cooking

1.5 Product Apperance

1.6 Working mode

**Deep Sleep Mode: **Sensor doesn't have any LoRaWAN activate. This mode is used for storage and shipping to save battery life.

Working Mode: In this mode, Sensor will work as LoRaWAN Sensor to Join LoRaWAN network and send out sensor data to server. Between each sampling/tx/rx periodically, sensor will be in IDLE mode), in IDLE mode, sensor has the same power consumption as Deep Sleep mode.

1.7 LED Status

The DMT01 uses a dual-color LED to indicate system status:

LED Behavior	Description
Green breathing effect	Probe is inserted and charging (LED turns off immediately when probe is removed)
Red solid (3 seconds)	Mode switched successfully
Red blinking (15 seconds)	Charging base low battery (≤20% capacity)
Red/Green alternating blink (3 seconds)	Device reset in progress (after 3s long press)
Single green blink	BLE connection established between probe and base
Single red blink	The charger/repeater box has entered sleep and the probe is removed (blinks once after probe removal)
Green light: On for 1.5 seconds and Red light: Flashes once(Execute twice)	The charger/repeater box enters deep sleep

1.8 Bluetooth Connection Management

This section describes the Bluetooth connection and reconnection behavior between the charging base and the probe.

Reconnection Process:

When the Bluetooth connection is disconnected, the charging base will automatically initiate a reconnection process.
The base will make 10 consecutive reconnection attempts, each attempt lasting 30 seconds.
The total reconnection duration is 300 seconds (5 minutes).

Probe Behavior:

After disconnection from the charging base, the probe will enter Bluetooth broadcast mode.
In this mode, the probe can be discovered by other Bluetooth devices.
The probe's Bluetooth broadcast name is: K10-BTS-P

Connection Recovery:

If the probe returns within effective Bluetooth communication range within 5 minutes, the connection will be automatically restored. (Note: The actual effective range may vary depending on the usage environment)
If the probe remains out of effective communication range for more than 5 minutes, it will maintain broadcast mode.
To manually re-establish the connection: return the probe to the charging base and then remove it.

1.9 Button Function

Behavior on ACT	Function	Action
>3s	Active Device	Red and Green LEDs blink alternately for 3 seconds. DMT01 will enter working mode and start joining the LoRaWAN network. Please remove the probe before performing the activation operation. When the probe is placed in the repeater for charging, the green LED on the charger/repeater box will display a breathing effect. The LED turns off when the probe is removed. Note: Each time the device is activated, the DMT01 will automatically switch to the default BLE/LoRa mode.
×3 times	Entering a deep sleep state	When the device successfully enters the low power state, the LED light will flash green and red. When the light goes out, it successfully enters the low power state. When you need to wake up the device, you need to reset the device. Note: The probe needs to be safely placed in the relay box.

Note: When the device is in deep sleep state and needs to be started, you need to take out the probe first, and then press and hold the ACT button on the charger/repeater box for 3 seconds. The charger/repeater box will reset the LoRa module and re-apply to join the LoRa network.

1.10 Power on device and Recharge Probe

When the repeater is charging, the charging indicator light will be solid red.
When the repeater is fully charged, the charging indicator will be solid green.

Warning: Use Only Supplied Cable

For optimal performance, please use the dedicated white USB cable provided to charge your DMT01 Repeater. This cable is designed with a specific charging protocol to ensure compatibility and safe charging. The use of third-party cables is not recommended and may prevent the device from charging properly.

Note: Due to uncertain transit and storage duration, your DMT01 may arrive with a depleted battery. It is recommended to charge the device immediately upon receipt using the dedicated white USB cable provided. If the LED on the front of the repeater does not show a green breathing light effect during charging, try removing the probe and reinserting it into the repeater.

2. Use DMT01

2.1 How it works

DMT01 include two parts,

The food grade probe: Used to measure the temperature inside meat.
The Charger with an integrated LoRaWAN End device: Connects the probe via BLE, retrieves the temperature, and sends it via LoRaWAN to the network server.

Consider the BLE coverage. There are two modes:

Connection Mode: The probe is nearby the charger/repeater box, within BLE range.

The probe will establish a connection to the charger/repeater box via BLE, and the data flow is as shown below.

Broadcast Mode: The probe is far away from the charger, outside the BLE range.

The probe will automatically switch to BLE broadcast mode and transmit the data via BLE. Any BLE scanner can pick up the signal and send it to the IoT server.

For example:

1) The user can use the BH01 BLE-to-LoRaWAN converter to pick up the BLE signal and forward it to the IoT server.

2) The user can use a mobile phone to receive the broadcast signal and process it further.

2.2 Activate Device

To activate the DMT01:

Use the provided registration information (DevEUI, AppEUI, AppKey) to register the device with the LoRaWAN Network Server to enable OTAA (Over-the-Air Activation).
Make sure there is LoRaWAN network coverage in your area that supports the network server you have chosen. If not, you can use a LoRaWAN gateway to extend the network coverage
Press the button on the DMT01 for more than 3 seconds. The DMT01 will start connecting to the LoRaWAN network.
After the DMT01 joins the LoRaWAN network, remove it (the probe) from the charger/repeater. The probe will start measuring temperature, and you will be able to see the data on the server.

2.3 Quick guide to connect to a LoRaWAN server (OTAA)

In this example, we use The Things Stack as the LoRaWAN network server to show you how to register the DMT01 with a LoRaWAN network server and how to activate it using OTAA. In this network diagram, the probe sends data packets to the charger/repeater unit via BLE. The repeater then converts those BLE data packets to LoRa packets and sends them to the Network Server.

In this example, we use the LPS8v2 as the LoRaWAN gateway.

Step 1: Create a device in The Things Stack with the OTAA registration information (keys) from DMT01.

Each DMT01 is shipped with a unique DevEUI, AppEUI, and AppKey. You can find it inside the package of the device. Please keep your registration information in a safe place and don't share with anyone.

You can enter this key in the LoRaWAN Network Server portal.

The following steps describe how to do it with The Things Stack network server portal. Follow the screenshots for correct configuration:

Create the application.

On the home screen, click the + Add application button.

On the Create application page, enter an Application ID to identify your **application **within The Things Stack and provide an Application name. Read https://thethingsindustries.com/docs/integrations/adding-applications for more information on how to do that.
Click the Create application button.

Add devices to the created Application

After creating the application, you will be redirected to the Application overview page.
On the Application overview page, click the + Register end device button.

Enter end device specifics manually

We use Over The Air Activation (**OTAA) **to activate DMT01 with The Things Stack. OTAA is the most secure way of activating an end device with a LoRaWAN network server.

On the Register end device page, select the ‘Enter end device specifics manually’ option under the input method.
Select the correct Frequency plan and LoRaWAN version. The Regional parameters version will appear automatically based on the LoRaWAN version

The Frequency plan should match the frequency of the DMT01.

Using the registration information sheet that comes with the DMT01,

Fill the JoinEUI. The DMT01 uses **AppEUI **instead of JoinEUI. You can enter it in the JoinEUI text box. Then click the **Confirm **button.

Add DevEUI and AppKey

Enter the **DevEUI **and AppKey.
Enter an End device ID that can be used to identify your DMT01 within this application.

Click the Register end device button.

**Step 2: **Add decoder

LoRaWAN uplink and downlink payloads are encoded. To understand the data, you need a small script to decode them. We use a JavaScript function for this. It is called a payload formatter. It reads the payload and extracts useful information, such as relay status, event type, and timestamp. We have written a JavaScript function to decode uplinks from the DMT01 device.

To add an uplink payload formatter code to The Things Stack, follow the steps below:

Go to your DMT01 device page and click Payload formatters.
Click, Uplink.
Select Custom Javascript formatter from the **Formatter type **drop-down list.
Now copy the Uplink Formatter code from here: https://github.com/dragino/dragino-end-node-decoder/tree/main/
Then paste it in the **Formatter code **box:

You can now test the formatter code with a sample payload.

Enter 68 90 7A 1F 01 C1 23 09 25 0F 1A 64 50 D7 00 D1 00 D7 D1 00 D7 00 D1 00 in the Byte payload box.
Change the **FPort **to 2 (because our payload formatter only accepts uplinks from FPort 2).
Click the Test decoder button.

The payload will be decoded into the following JSON object and shown in the Decoded test payload box.

To save the payload formatter, click the Save changes button.

After applying the uplink payload formatter, you can see that all uplink payloads shown in the Live Data section are decoded into fields.

Step 3: Activate the DMT01

Press the **ACT **button for 3 seconds to activate the DMT01. After a successful join, it will start uploading messages to The Things Stack, and you can see them in the Live data panel.

2.3 LoRaWAN Payload

DMT01 uses different types of LoRaWAN payload formats.

2.3.1 Probe In-Place Detection and Status Reporting, FPort=6

This port is used for reporting probe placement status, charging events, and periodic keep-alive messages.

There are three primary triggering scenarios:

When the probe is inserted into or removed from the charger/repeater box, an event packet is sent uplink.
When the probe has reached full charge while placed in the charger/repeater box, a charging completion event packet is sent uplink.
When the probe remains inserted in the charger/repeater box (without the box being manually put into deep sleep), a keep-alive status packet is automatically sent every 2 hours.

The payload includes the Timestamp, ProbeEvent, and the battery level of the charger/repeater box. The format is as follows:


Device Status (FPort=6)
Size (bytes)	4	1	1
Value	Timestamp	ProbeEvent	charger/repeater box battery level (BoxBat)

Example in The Things Stack:

Timestamp: 0x68946BB4

ProbeEvent:

0x04 = KEEP_ALIVCE (indicates that the charger/repeater box is online)

**0x03 **= PROBE_FULL (indicates that the probe is fully charged)

**0x02 **= PROBE_OUT (indicates that the probe is taken out of the charger/repeater box)

**0x01 **= PROBE_IN (indicates that the probe is placed in the charger/repeater box)

BoxBat: 0x32 = 50%

2.3.1 Device Status, FPort=5

You can use the downlink command (0x26 01) to request DMT01 to send its configuration details, including the device configuration status. DMT01 will uplink a payload to the LoRaWAN Network Server via FPort = 5.

The Payload format is as below.


Device Status (FPort=5)
Size (bytes)	1	2	1	1
Value	Sensor Model	Firmware Version	Frequency Band	Sub-band

Example in The Things Stack:

Sensor Model: For DMT01, this value is 0x4B

Firmware Version: 0x0101, which means v1.0.1

Frequency Band:

0x01: EU868

0x02: US915

0x03: IN865

0x04: AU915

0x05: KZ865

0x06: RU864

0x07: AS923

0x08: AS923-1

0x09: AS923-2

0x0a: AS923-3

0x0b: CN470

0x0c: EU433

0x0d: KR920

0x0e: MA869

Sub-Band:

AU915 and US915: value 0x00 ~ 0x08

CN470: value 0x0B ~ 0x0C

Other Bands: Always 0x00

2.3.2 Sensor Data, FPort=2

This port is used for uplinking sensor data readings. After the DMT01 is connected to the LoRaWAN network and is in normal operation mode, once the probe is removed from the charger/repeater box, a BLE connection is established between the probe and the box. The charger/repeater box will then uplink sensor data packets periodically via FPort=2.

The uplink interval is determined by the probe sampling interval multiplied by the number of samples, as configured in the Multi-Sampling command. By default, the sampling interval is 6 seconds with 10 sample groups, resulting in an uplink every 60 seconds. Therefore, the charger/repeater box transmits this data packet every 1 minute by default.

The Payload format is as below.

Size(bytes)	4	1	6	1	1	2	2
Value	Timestamp	DevMode	MACaddr	ProbeBat	BoxBat	Food temperature	Ambient temperature

Unix Timestamp

UNIX Timestamp Example: 689085D7(H) = 1754301911(D)

Convert the decimal value using (https://www.epochconverter.com)) to get the corresponding time.

DevMode

Example：

If the payload is 0x01: BLE_LoRa

If the payload is 0x02: LoRa

If the payload is 0x03: BLE

MACaddr

Example:

If the payload is C12309250F1A, the MACaddr is C12309250F1A

ProbeBat

Example:

If the payload is 0x64 = 100%

BoxBat

Example:

If the payload is 0x46 = 70%

Food temperature

Because the food temperature data is in little-endian format, the order of the bytes needs to be swapped during decoding.

Example:

If the payload is: D300 = 00D3(H) , (00D3 & 8000 == 0), the **temp **=00D3H/10 = 211 /10 = 21.1 ℃

If the payload is: 7D80 = 807D(H), (807D & 8000 == 1), the **temp **= -(807D & 7FFF)/10 = -125/10=-12.5 ℃.

Ambient temperature

Because the food temperature data is in little-endian format, the order of the bytes needs to be swapped during decoding.

Example:

If the payload is: D300 = 00D3(H) , (00D3 & 8000 == 0), the **temp **=00D3H/10 = 211 /10 = 21.1 ℃

2.4 Bluetooth Broadcast Payload

2.4.1 Relay Box Broadcast Payload

When the relay box is connected to the probe via Bluetooth, it periodically broadcasts its own status and measurement data of probe. Use a third-party mobile app (such as nRF Connect) to scan and obtain the broadcast data from the relay box.

Operation Steps:

1. Open the nRF Connect application

2. Start scanning for Bluetooth devices

3. Look for the device named in the scan results

4. Click on the DMT01 device to establish a connection

5. Once connected, view and capture the raw broadcast data

Example:

The following broadcast payload was captured using nRF Connect for Mobile app when connected to a DMT01 relay box:

If the scanned payload is 0x0201060609444D5430310EFF **01C12309250F1AD100CD006446 **0512E001E001

**Note: **

The first 12 bytes in the payload are the Bluetooth packet header data and do not need to be decoded.
The last 6 bytes in the payload are the Bluetooth packet trailer data and do not need to be decoded.

So the payload is：01C12309250F1AD100CD006446

Bluetooth data packet frame header

Example: 0x0201060609444D5430310EFF

DevMode

Example:

If the payload is 0x01: BLE_LoRa

If the payload is 0x02: LoRa

If the payload is 0x03: BLE

MACaddr

Example:

If the payload is C12309250F1A, the MACaddr is C12309250F1A

ProbeBat

Example:

If the payload is 0x64 = 100%

BoxBat

Example:

If the payload is 0x46 = 70%

Food temperature

Because the food temperature data is in little-endian format, the order of the bytes needs to be swapped during decoding.

Example:

If the payload is: D100 = 0x00D1(H), (00D1 & 8000 == 0), the temp = 00D1H/10 = 209/10 = 20.9 ℃

If the payload is: BD80 = 80BD(H), (80BD & 8000 == 1), the **temp **= -(80BD & 7FFF)/10 = -189/10=-18.9 ℃.

Ambient temperature

Because the food temperature data is in little-endian format, the order of the bytes needs to be swapped during decoding.

Example:

If the payload is: CD00 = 0x00CD(H), (00CD & 8000 == 0), the temp = 00CDH/10 = 205/10 = 20.5 ℃

Bluetooth data packet frame tail

Example: 0x0512E001E001

2.4.2 Probe Broadcast Payload

When the Bluetooth connection between the relay box and the probe is disconnected, the probe will automatically enter independent broadcast mode. In this state, the probe can be directly scanned and accessed using a mobile application such as nRF Connect. The probe broadcasts under the name K10-BTS-P, and can also be identified by its unique MAC address (e.g., 6C:B3:4D:03:26:8F). Example:

Operation Steps:

1. Disconnect the Bluetooth connection between the relay box and the probe: The distance between the relay box and the probe exceeds the effective Bluetooth range, causing an automatic disconnection.

2. Open the nRF Connect application on your mobile device.

3. Start scanning for nearby Bluetooth devices.

4. Look for the device named K10-BTS-P in the scan results.

5. Select the target probe to connect.

6. View and capture the raw broadcast data transmitted by the probe.

Example:

A typical broadcast payload from the probe may appear as follows:

The raw data from the probe includes broadcast data and scan response data, which are parsed as follows:

**broadcast data: **

**Field Descriptions: **

scan response data:

The scan response packet contains the Bluetooth name, formatted as follows:

If the scanned payload is 0x020106 17FF4852010000000000000000 9EF1024DB36C 2401 1601 32 0303F5FE 0A094B31302D4254532D50

BLE Flags

Example:

If the payload is 0x02: Indicates a byte length of 2 bytes.

If the payload is 0x01: Indicates data type 1.

If the payload is 0x06: Indicates Bluetooth flag bit 06.

BLE address

Example:

The BLE address is 6C:B3:4D:02:F1:9E

Food temperature

Ex1:

If the payload is:

Because the food temperature data is in little-endian format, the order of the bytes needs to be swapped during decoding.

If the payload is 2401 = 0x0124(H), (0124 & 8000 == 0), the temp = 0124H/10 = 292/10 = 29.2 ℃

Ex2:

If the payload is: BD80 = 80BD(H), (80BD & 8000 == 1), the **temp **= -(80BD & 7FFF)/10 = -189/10=-18.9 ℃.

Ambient temperature

Ex1:

If the payload is:

Because the Ambient temperature data is in little-endian format, the order of the bytes needs to be swapped during decoding.

If the payload is 1601 = 0x0116(H), (0116 & 8000 == 0), the temp = 0016H/10 = 278/10 = 27.8 ℃

Battery level

If the payload is 0x32 : 0x32(H)=50(D), Indicates Battery level is 50%.

2.5 Use the BH01-LB to capture the Bluetooth Payload

When the meat probe is out of the DMT01 Bluetooth range, it will automatically switch to BLE broadcast mode, and the sensor data can be captured by the BH01-LB via BLE and sent to the LoRaWAN Network Server.

2.5.1 BH01-LB Scanning Operation

By default, the BH01-LB/LS device supports scanning for DMT01 probes and uploading data via LoRaWAN.

The BH01-LB/LS device can scan multiple probes simultaneously and upload their data at the same time. Uploaded data can be viewed on a LoRaWAN platform (e.g., The Things Stack).

You can modify the scanning mechanism of the BH01-LB/LS to disable scanning for other beacons and restrict it to scanning only DMT01 probes:

Method 1: Send AT+MODEL=0300 via the serial port to disable scanning for other Bluetooth beacons.

Method 2: Send 0x080300 via the platform to disable scanning for other Bluetooth beacons.

2.5.2 Payload of BH01-LB/LS (For The Things Stack)

In this mode, the uplink payload contains a total of 18+n bytes. Uplink packets use FPort=2.

Note: The maximum size of a data packet is 252 bytes. If the data packet exceeds 252 bytes, the packet will be split into multiple packets for uplink transmission.

decoder file：BH01-LB_Decode_V1.0.1.txt

After parsing the BH01-LB data using our standard decoder, the probe data can be viewed intuitively, example in TTN:

For example, the payload 0xD143A468C12309250F1A0406D000D10064CB equals 18 bytes.

Unit timestamp

Because the food temperature data is in little-endian format, the order of the bytes must be swapped during decoding.

Example (UNIX Timestamp): D143A468 (hex) = 68A443D1 (decimal)

Paste the decimal value into (https://www.epochconverter.com)) to get the corresponding time.