Wiki source code of DMT01

Version 50.1 by Mengting Qiu on 2025/08/04 18:46

version	line-number	content
1.1	1
	2
5.1	3	[[image:1753592237986-145.png\|\|height="354" width="118"]] [[image:1753592287802-550.png\|\|height="237" width="341"]]
1.1	4
	5
	6	Table of Contents:
	7
	8	{{toc/}}
	9
	10	(% aria-label="macro:toc widget" contenteditable="false" role="region" tabindex="-1" %)
	11	(((
	12	(% style="background-image:url(http://wiki1.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==\|\|height="15" role="presentation" title="Click and drag to move" width="15"]]
	13	)))
	14
	15
	16
	17	= 1. Introduction =
	18
6.1	19	== 1.1 What is DMT01 Wireless Meat Thermometer ==
1.1	20
	21
6.1	22	The DMT01 is a (% style="color:blue" %)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.
1.1	23
6.1	24	The system consists of two components:
	25	- (% style="color:blue" %)Food-grade BLE High-Temperature Probe(%%) – A durable, high-heat resistant probe that measures internal food temperature during cooking.
	26	- (% style="color:blue" %)Charging Base with BLE & LoRaWAN Forwarder(%%) – 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.
1.1	27
12.1	28	With its dual wireless support ((% style="color:blue" %)BLE for close-range/small design(%%) and (% style="color:blue" %)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.1	29
	30	== 1.2 Features ==
6.2	31
6.1	32	* Wireless Meat Thermometer – Designed for accurate and reliable cooking temperature monitoring
	33	* Food-Grade Probe – Safe for food contact and dishwasher-compatible for easy cleaning
	34	* BLE 5.1 Broadcasting – Supports real-time local data transmission via Bluetooth Low Energy
	35	* LoRaWAN Connectivity – Enables long-range, low-power data transmission to IoT platforms
	36	* Smart Uplink Triggering – Supports periodic data reporting and real-time alerts on temperature thresholds
1.1	37
	38	(% style="display:none" %)
	39
	40	== 1.3 Specification ==
	41
	42
	43	(% style="color:blue" %)Common DC Characteristics:
	44
13.1	45	* Supply Voltage: +5v via USB Type-C
	46	* Operating Temperature:
1.1	47
6.2	48	(% style="color:blue" %)Food Probe Spec:
1.1	49
19.2	50	* Length: 126mm
	51	* Diameter: 6mm
19.3	52	* Food temperature: -30 ~~110 °C, Accuracy: ±0.5°C
	53	* Ambient temperature: 0 ~~380°C, Accuracy: ±5°C
19.2	54	* Wireless: BLE 5.1
19.3	55	* Distance: ≥ 30m
	56	* Battery: 4mAh
19.18	57	* Recharge time: ＜ 2 hours
19.12	58	* Battery Duration: ＞30 hours
19.6	59	* IP Rate: IP67, Dish Washer proof
1.1	60
	61
	62
19.12	63	(% style="color:blue" %)Charger Spec:
1.1	64
19.16	65	* BLE v5.1 + LoRaWAN
19.18	66	* Power Input: USB Type-C, +5v
	67	* Battery: Li-ion , 3000mAh
19.19	68	* Recharge time: ＜ 2 hours
1.1	69
17.27	70
17.26	71
20.2	72
1.1	73	== 1.4 Applications ==
	74
6.2	75	* Commercial Kitchen
7.1	76	* Restaurant
	77	* Catering
	78	* Food Processing
	79	* Central Kitchen
	80	* Cloud Kitchen
	81	* HACCP Monitoring
	82	* Food Safety
	83	* Meat Factory
	84	* Industrial Cooking
1.1	85
16.1	86	== 1.5 Product Apperance ==
1.1	87
14.33	88	(% class="wikigeneratedid" %)
	89	[[image:1753594523550-152.png\|\|height="462" width="416"]]
1.1	90
14.31	91
14.33	92	== 1.6 Working mode ==
14.31	93
14.33	94
20.4	95	(% style="color:blue" %)Deep Sleep Mode:(%%) Sensor doesn't have any LoRaWAN activate. This mode is used for storage and shipping to save battery life.
1.1	96
20.4	97	(% style="color:blue" %)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.1	98
	99
14.33	100	== 1.7 LED Status ==
1.1	101
	102
20.5	103	The DMT01 uses a dual-color LED to indicate system status:
	104
23.2	105	(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:503px" %)
23.6	106	\|(% style="background-color:#4f81bd; color:white; width:196px" %)LED Behavior\|(% style="background-color:#4f81bd; color:white; width:305px" %)Description
	107	\|(% style="width:196px" %)Green breathing effect\|(% style="width:305px" %)Probe is inserted and charging
23.5	108	(LED turns off immediately when probe is removed)
23.6	109	\|(% style="width:196px" %)Red solid (5 seconds)\|(% style="width:305px" %)Mode switched successfully (after 1-3s button press)
	110	\|(% style="width:196px" %)Red blinking (15 seconds)\|(% style="width:305px" %)Charging base low battery (<15% capacity)
26.2	111	\|(% style="width:196px" %)Red/Green alternating blink (3 seconds)\|(% style="width:305px" %)Device reset in progress (after 3s long press)
23.7	112	\|(% style="width:196px" %)Single green blink\|(% style="width:305px" %)BLE connection established between probe and base
20.5	113
	114
	115
14.33	116	== 1.8 Button Function ==
1.1	117
29.2	118	[[image:1754120439617-600.jpg\|\|height="404" width="404"]]
1.1	119
27.1	120	(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:536.222px" %)
	121	\|=(% style="width: 147px; background-color: rgb(79, 129, 189); color: white;" %)Behavior on ACT\|=(% style="width: 130px; background-color: rgb(79, 129, 189); color: white;" %)Function\|=(% style="width: 254px; background-color: rgb(79, 129, 189); color: white;" %)Action
	122	\|(% style="background-color:#f2f2f2; width:147px" %) [[image:1754045287749-587.png]]>3s\|(% style="background-color:#f2f2f2; width:130px" %)Active Device\|(% style="background-color:#f2f2f2; width:254px" %)(((
26.4	123	Red/Green alternating blink (3 seconds), DMT01 will enter working mode and start to JOIN LoRaWAN network.
26.5	124	When the probe is placed in the repeater to charge, the green LED above the relay box will have a breathing effect. When the probe is taken out, the LED light will go out.
26.2	125	)))
27.1	126	\|(% style="background-color:#f2f2f2; width:147px" %)[[image:1754045287749-587.png]] 1~~3s\|(% style="background-color:#f2f2f2; width:130px" %)Switch working mode\|(% style="background-color:#f2f2f2; width:254px" %)(((
	127	There are three operating modes:
26.7	128	Default LoRaWAN and Bluetooth broadcast mode,
27.1	129	Separate LoRaWAN mode
	130
	131	Separate Bluetooth broadcast mode.
26.7	132	(% style="color:red" %)Note:(%%) To switch modes, remove the probe and press the button; otherwise, the mode will not switch.
27.1	133	)))
26.2	134
	135
	136
16.1	137	== 1.9 Power on device and Recharge Probe ==
14.31	138
14.33	139
29.3	140
	141
9.1	142	= 2. Use DMT01 =
1.1	143
14.2	144	== 2.1 How it works ==
1.1	145
	146	(((
	147	(((
	148
14.2	149
18.2	150	DMT01 Include two parts,
	151
	152	1. The food grade probe : used to measure the meat temperature
18.7	153	1. The Charger which is also a LoRaWAN End node: used to connect the probe via BLE and get the temperature and send via LoRaWAN to IoT server.
18.2	154
18.8	155
	156
	157	Consider the BLE coverage , there is two cases:
	158
19.2	159	=== Connection Mode: Probe is near by the Charge, within BLE range ===
18.9	160
	161	Probe will establish connection to the charge via BLE. and the data flow is as below.
1.1	162	)))
	163
14.7	164	[[image:1753622303925-386.png]]
1.1	165
14.2	166
19.2	167	=== Broadcast Mode: Probe is far away from the Charge, out of BLE range ===
18.10	168
18.14	169	Probe will auto swtich to BLE broadcast mode and broadcast the data via BLE. Any BLE Scaner can pick up the signal and send to IoT server.
18.10	170
18.14	171	For example:
18.10	172
18.14	173	1) User can use BH01 BLE to LoRaWAN converter to pick up the BLE signal to IoT Server
	174
18.22	175	2) User can use Mobile phone to get the broadcast signal and further process.
18.14	176
	177
14.8	178	== 2.2 Activate Device ==
	179
	180	To use DMT01 send data to LoRaWAN network, user need to:
	181
	182	1. Input the OTAA Keys in LoRaWAN Network Server
14.10	183	1. Make sure there is LoraWAN network
14.13	184	1. Press the button on the DMT01 for more than 3 seconds, DMT01 will start to connect to LoRaWAN network
14.14	185
	186
	187
14.27	188	After the DMT01 Join LoRaWAN network, once user take out the probe, the probe will start to measure temperature and user will be to see the data on the server.
1.1	189	)))
	190
	191
31.1	192	== 2.2 How it works? ==
1.1	193
31.1	194	(((
	195	(((
	196
	197	)))
1.1	198
31.3	199	The DMT01 is configured as (% style="color:#037691" %)LoRaWAN OTAA Class A(%%) mode by default. It has OTAA keys to join LoRaWAN network. To connect a local LoRaWAN network, you need to input the OTAA keys in the LoRaWAN IoT server and press the button to activate the DMT01. It will automatically join the network via OTAA and start to send the sensor value.
1.1	200
31.1	201	(((
31.3	202	On each uplink, DMT01 will get the temperature from the sensor and send it to the server.
31.1	203	)))
	204	)))
1.1	205
	206
31.1	207	== 2.3 Quick guide to connect to LoRaWAN server (OTAA) ==
1.1	208
	209
31.1	210	Following is an example for how to join the [[TTN v3 LoRaWAN Network>>url:https://console.cloud.thethings.network/]]. Below is the network structure; we use the [[LPS8v2>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/228-lps8v2.html]] as a LoRaWAN gateway in this example.
	211
	212	The LPS8V2 is already set to connected to [[TTN network >>url:https://console.cloud.thethings.network/]], so what we need to now is configure the TTN server.
	213
34.2	214	[[image:1754298519453-808.jpg\|\|height="211" width="951"]]
31.1	215
	216
31.3	217	(% style="color:blue" %)Step 1:(%%) Create a device in TTN with the OTAA keys from DMT01.
31.1	218
31.3	219	Each DMT01 is shipped with a sticker with the default device EUI as below:
31.1	220
34.2	221	[[image:1754298588891-599.jpeg]](% style="display:none" %)
31.1	222
	223	You can enter this key in the LoRaWAN Server portal. Below is TTN screen shot:(% style="display:none" %)
	224
	225	(% style="color:blue" %)Create the application.
	226
39.2	227	[[image:1754298671647-982.png]]
31.1	228
39.2	229	[[image:1754298685721-106.png]]
31.1	230
	231	(% style="color:blue" %)Add devices to the created Application.
	232
39.2	233	[[image:1754298708270-733.png]]
31.1	234
39.2	235	[[image:1754298719336-394.png]]
31.1	236
	237	(% style="color:blue" %)Enter end device specifics manually.
	238
40.2	239	[[image:1754298737089-161.png]]
31.1	240
	241	(% style="color:blue" %)Add DevEUI and AppKey.
	242
	243	(% style="color:blue" %)Customize a platform ID for the device.
	244
40.2	245	[[image:1754298751553-229.png]]
31.1	246
	247
	248	(% style="color:blue" %)Step 2: (%%)Add decoder
	249
	250	In TTN, user can add a custom payload so it shows friendly reading.
	251
	252	Click this link to get the decoder: [[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/>>url:https://github.com/dragino/dragino-end-node-decoder/tree/main/]]
	253
	254	Below is TTN screen shot:
	255
41.2	256	[[image:1754298862776-783.png\|\|height="609" width="1426"]]
31.1	257
44.1	258	[[image:1754299076396-787.png]]
31.1	259
32.2	260	(% style="color:blue" %)Step 3:(%%) Activate on DMT01
31.1	261
32.2	262	Press the button for 3 seconds to activate the DMT01.
31.1	263
	264	After join success, it will start to upload messages to TTN and you can see the messages in the panel.
	265
41.2	266	[[image:1754298481895-828.png\|\|height="441" width="1387"]]
31.1	267
	268
	269
30.2	270	== 2.3 LoRaWAN Payload ==
1.1	271
45.2	272	=== 2.3.1 Device Status, FPORT~=5 ===
30.2	273
	274
46.1	275	Users can use the downlink command(0x26 01) to ask DMT01 to send device configure detail, include device configure status. DMT01 will uplink a payload via FPort=5 to server.
45.2	276
	277	The Payload format is as below.
	278
	279	(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
	280	\|(% colspan="6" style="background-color:#4f81bd; color:white" %)Device Status (FPORT=5)
45.3	281	\|(% style="width:103px" %)Size (bytes)\|(% style="width:91px" %)1\|(% style="width:98px" %)2\|(% style="width:103px" %)1\|(% style="width:112px" %)1
	282	\|(% style="width:103px" %)Value\|(% style="width:91px" %)Sensor Model\|(% style="width:98px" %)Firmware Version\|(% style="width:103px" %)Frequency Band\|(% style="width:112px" %)Sub-band
45.2	283
	284	Example in TTN:
	285
	286	[[image:1754299464263-797.png\|\|height="274" width="1384"]]
	287
	288
	289	(% style="color:#037691" %)Sensor Model(%%): For DMT01, this value is 0x4B
	290
45.3	291	(% style="color:#037691" %)Firmware Version(%%): 0x0101, Means: v1.0.1 version
45.2	292
	293	(% style="color:#037691" %)Frequency Band(%%):
	294
	295	0x01: EU868
	296
	297	0x02: US915
	298
	299	0x03: IN865
	300
	301	0x04: AU915
	302
	303	0x05: KZ865
	304
	305	0x06: RU864
	306
	307	0x07: AS923
	308
	309	0x08: AS923-1
	310
	311	0x09: AS923-2
	312
	313	0x0a: AS923-3
	314
	315	0x0b: CN470
	316
	317	0x0c: EU433
	318
	319	0x0d: KR920
	320
	321	0x0e: MA869
	322
	323	(% style="color:#037691" %)Sub-Band(%%):
	324
	325	AU915 and US915:value 0x00 ~~ 0x08
	326
	327	CN470: value 0x0B ~~ 0x0C
	328
	329	Other Bands: Always 0x00
	330
	331
46.2	332	=== 2.3.2 Sensor Data. FPORT~=2 ===
45.2	333
46.2	334
	335	Sensor Data is uplink via FPORT=2
	336
47.2	337	(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
46.2	338	\|=(% style="width: 60px;background-color:#4F81BD;color:white" %)(((
47.2	339	Size(bytes)
48.7	340	)))\|=(% style="width: 40px;background-color:#4F81BD;color:white" %)4\|=(% style="width: 90px;background-color:#4F81BD;color:white" %)1\|=(% style="width: 150px; background-color: #4F81BD;color:white" %)6\|=(% style="width: 80px; background-color: #4F81BD;color:white" %)1\|=(% style="width: 80px; background-color: #4F81BD;color:white" %)1\|=(% style="width: 80px; background-color: #4F81BD;color:white" %)2\|=(% style="width: 80px; background-color: #4F81BD;color:white" %)2
46.2	341	\|(% style="width:99px" %)Value\|(% style="width:69px" %)(((
47.20	342	Timestamp
47.19	343
	344
	345	)))\|(% style="width:130px" %)DevMode\|(% style="width:194px" %)MACaddr\|(% style="width:106px" %)ProbeBat\|(% style="width:97px" %)(((
48.7	346	BoxBat
	347	)))\|(% style="width:97px" %)Food temperature\|(% style="width:97px" %)Ambient temperature
47.19	348
47.3	349	[[image:1754300947187-648.png\|\|height="641" width="1351"]]
46.2	350
	351
48.4	352
50.1	353	==== (% style="color:#4472c4" %)Unit timestamp(%%) ====
46.2	354
48.6	355	Unit TimeStamp Example: 689085D7(H) = 1754301911(D)
46.2	356
48.2	357	Put the decimal value into this link([[https:~~/~~/www.epochconverter.com)>>https://www.epochconverter.com]])to get the time.
46.2	358
	359
50.1	360	==== (% style="color:#4472c4" %)DevMode(%%) ====
46.2	361
49.2	362	Example：
46.2	363
49.1	364	If payload is 0x01: BLE_LoRa
46.2	365
49.1	366	If payload is 0x02: LoRa
48.8	367
49.1	368	If payload is 0x03: BLE
48.10	369
	370
50.1	371	==== (% style="color:#4472c4" %)MACaddr(%%) ====
46.2	372
49.2	373	Example:
46.2	374
49.1	375	If the payload is C12309250F1A, the MACaddr is C12309250F1A
46.2	376
48.11	377
50.1	378	==== (% style="color:#4472c4" %)ProbeBat(%%) ====
46.2	379
	380	Example:
	381
49.2	382	If payload is 0x64 = 100%
46.2	383
	384
50.1	385	==== (% style="color:#4472c4" %)BoxBat(%%) ====
48.3	386
49.2	387	Example:
48.3	388
49.2	389	If payload is 0x46 = 70%
48.3	390
	391
50.1	392	==== (% style="color:#4472c4" %)Food temperature(%%) ====
46.2	393
50.1	394	Because the food temperature data is a little-endian sequence, the order of the front and back bytes needs to be swapped during decoding.
	395
47.9	396	Example:
47.8	397
50.1	398	If payload is: D300H = 00D3H, temp = 00D3H /10 = 21.1 degree
47.8	399
50.1	400	If payload is: 3FFFH = FF3F , temp = (FF3FH - 65536)/10 = -19.3 degrees.
47.8	401
47.9	402
50.1	403	==== (% style="color:#4472c4" %)Ambient temperature(%%) ====
47.9	404
50.1	405	Because the food temperature data is a little-endian sequence, the order of the front and back bytes needs to be swapped during decoding.
47.9	406
47.11	407	Example:
47.9	408
50.1	409	If payload is: D200H = 00D2H, temp = 00D2H /10 = 21.0 degree
47.9	410
50.1	411	If payload is: 3FFFH = FF3F , temp = (FF3FH - 65536)/10 = -19.3 degrees.
47.11	412
	413
	414
30.2	415	== 2.4 Bluetoothe Broadcast Payload ==
	416
50.1	417	=== 2.4.1 Scanning Tools ===
30.2	418
50.1	419	Scan and obtain BPT01 device broadcast data through a third-party mobile phone app (such as nRF Connect)
30.2	420
50.1	421	Example：
30.2	422
50.1	423	Note: The following data is obtained through the nRF Connect tool.
30.2	424
50.1	425
	426
	427
	428
14.31	429	= 3. Configure DMT01 ~-~- 需要修改 =
1.1	430
	431	== 3.1 Configure Methods ==
	432
17.1	433	User can use LoRaWAN downlink command to configure the DMT01
1.1	434
	435	(((
	436	(((
17.23	437	== 3.2 Downlink Commands Set ==
1.1	438
	439
	440	(% class="box infomessage" %)
	441	(((
	442	To be updated...
	443	)))
	444	)))
	445	)))
	446
	447
17.16	448	= 4. Firmware update =
1.1	449
	450
17.7	451	Firmware download link (% class="mark" %)(To be updated...)
	452
17.6	453	User can upgrade the firmware for DMT01 charger. The charger include two piece of software:
1.1	454
17.8	455	* For LoRa part: OTA firmware update via LoRa:.
17.6	456
17.9	457	* For BLE and controller part.
1.1	458
17.17	459	== 4.1 Update LoRa software ==
17.10	460
17.13	461
17.17	462	== 4.2 Update BLE software ==
17.14	463
1.1	464
	465	(((
	466
	467	)))
	468
17.17	469	= 5. FAQ =
1.1	470
	471
	472
17.18	473	= 6. Order Info =
1.1	474
	475
7.2	476	Part Number: (% style="color:blue" %)DMT01-XX
1.1	477
	478	(% style="color:red" %)XX:
	479
17.19	480	* EU433: Frequency bands EU433
17.20	481	* EU868: Frequency bands EU868
	482	* KR920: Frequency bands KR920
17.21	483	* CN470: Frequency bands CN470
	484	* AS923: Frequency bands AS923
17.22	485	* AU915: Frequency bands AU915
17.23	486	* US915: Frequency bands US915
	487	* IN865: Frequency bands IN865
	488	* CN779: Frequency bands CN779
1.1	489
17.18	490	= 7. Packing Info =
1.1	491
	492
	493	(% style="color:#037691" %)Package Includes:
	494
10.1	495	* DMT01 - Digital Meat Thermoneter x 1
1.1	496
	497	(% style="color:#037691" %)Dimension and weight:
	498
	499	* Device Size: cm
	500	* Device Weight: g
	501	* Package Size / pcs : cm
	502	* Weight / pcs : g
	503
17.19	504	= 8. Support =
1.1	505
	506
	507	* Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule.
	508	* Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:http://../../../../../../D:%5C%E5%B8%82%E5%9C%BA%E8%B5%84%E6%96%99%5C%E8%AF%B4%E6%98%8E%E4%B9%A6%5CLoRa%5CLT%E7%B3%BB%E5%88%97%5Csupport@dragino.com]].

Wiki source code of DMT01

Applications