Github Upload Boards Devices Community Docs Blog

BLE wireless BBQ temperature probe with ESP32

Has anyone looked into integrating the meater probes? Specifically the original without the repeater in the base. It has such a short range but if OMG could be the repeater to HA or other dashboard it would be great.

I have one laying around, they seems to need a connection. So not so out of the box compared to INKBIRD ones

Let me take a look again to it

Also interested in more support for Bbq probes. I guess this one (Meater basic probe) uses Bluetooth right? A bit concerned about product longevity vs high temperatures…

More protocols is always good as it provides flexibility to choose the right product.
However if you need a tested solution meanwhile, I currently use Thermopro products via RTL_433 & MQTT, they broadcast on 433Mhz and work quite well, especially if you have a good antenna for reception (mine is in the attic so I can use a BBQ at the back of my yard)
Also, the manufacturer stands behind its products and offer great support; dead probes are changed free of charge.

Watching thread :slight_smile:

Thx,

I’m progressing on the MEATER integration, should be out soon

1 Like

Here is the PR (work in progress )

I’ve got a ChuGod 6 channel thermometer which reports it is a device name ‘iBBQ’ so it works with the Inkbird IBT-4XS and returns the first 4 of the 6 channels. Is there any chance of adding it ( I can dump BLE data if needed)?

I tried adding it to the source and compiling but Ardiuno compiler gives me errors and I am not experienced enough with Ardiuno to figure out what I did wrong.
here is the error:
main:55:1: error: ‘StaticJsonDocument’ does not name a type
StaticJsonDocument<JSON_MSG_BUFFER> modulesBuffer;

Thanks

Yes we can add it, feel free to share a dump with several sets of manufacturer data the other ibfos seen by the gateway and the expected temperature.

Here is the information I have which includes some from the sources at GitHub - gleeds/cloudbbq: A Bluetooth to MQTT bridge for the Tenergy Solis Digital Meat Thermometer and other similar devices.

[12:29:09][I][ble_client:159]: Service UUID: 0x1800
Generic Access
[12:29:09][I][ble_client:160]: start_handle: 0x1 end_handle: 0xb
[12:29:09][I][ble_client:339]: characteristic 0x2A00, handle 0x3, properties 0x2
Device Name
Value: iBBQ

[12:29:09][I][ble_client:339]: characteristic 0x2A01, handle 0x5, properties 0x2
Appearance
[12:29:09][I][ble_client:339]: characteristic 0x2A02, handle 0x7, properties 0xa
Peripheral Privacy flag
Value 0x00
[12:29:09][I][ble_client:339]: characteristic 0x2A03, handle 0x9, properties 0x8
Reconnection Address Write
[12:29:09][I][ble_client:339]: characteristic 0x2A04, handle 0xb, properties 0x2
Peripheral prefered connection parameters
Value: 0x5000A0000000E803

[12:29:09][I][ble_client:159]: Service UUID: 0x1801
Generic Attribute
[12:29:09][I][ble_client:160]: start_handle: 0xc end_handle: 0xf
[12:29:10][I][ble_client:339]: characteristic 0x2A05, handle 0xe, properties 0x20
Service Changed

[12:29:10][I][ble_client:159]: Service UUID: 0x180A
Device Information
[12:29:10][I][ble_client:160]: start_handle: 0x10 end_handle: 0x22
[12:29:10][I][ble_client:339]: characteristic 0x2A23, handle 0x12, properties 0x2
System Id
Value: 0xCD45270000DE0334
[12:29:10][I][ble_client:339]: characteristic 0x2A24, handle 0x14, properties 0x2
Model Number String
Value: iBBQ
[12:29:10][I][ble_client:339]: characteristic 0x2A25, handle 0x16, properties 0x2
Serial Number String
Value: 00-000000 (0x30302D303030303030)
[12:29:10][I][ble_client:339]: characteristic 0x2A26, handle 0x18, properties 0x2
Firmware revision string
Value: 3.10.2 (0x332E31302E32)

[12:29:10][I][ble_client:339]: characteristic 0x2A27, handle 0x1a, properties 0x2
Hardware Revision String
Value: 3.10.2 (0x332E31302E32)

[12:29:10][I][ble_client:339]: characteristic 0x2A28, handle 0x1c, properties 0x2
Software Revision String
Value: 3.10.2 (0x332E31302E32)
[12:29:10][I][ble_client:339]: characteristic 0x2A29, handle 0x1c, properties 0x2
Manufacturer string
Value: Quilin net (0x51696C696E206E6574)
[12:29:10][I][ble_client:339]: characteristic 0x2A50, handle 0x1c, properties 0x2
PNP ID
Value: (0x010D0000001001)

Custom Service: 0000FFF0-0000-1000-8000-0805F9B34FB
Custom Characteristic: 0xFFF1
UUID: 0x2902: Notifications
UUID: 0x2901: Setting Result
Custom Characteristic: 0xFFF2
Write request
UUID: 0x2901: Account & Verify Pairing
Autopair key: 33,7,6,5,4,3,2,1,-72,34,0,0,0,0,0
Handpair key: 33,7,6,5,4,3,2,1,1,1,1,1,0,0,0
Fuwei` key: 4,-1,0,0,0,0
dianya key: 8,36,0,0,0,0
Read versions key: 8,35,0,0,0,0

Custom Characteristic: 0xFFF3
UUID: 0x2902: Notifications
UUID: 0x2901: History Data

Custom Characteristic: 0xFFF4
UUID: 0x2902: Notifications
UUID: 0x2901: Real Time Data
Same as Inkbird IBT-4XS but Six 16-bit words instead of Four

Custom Characteristic: 0xFFF5
UUID: 0x2902: Notifications
UUID: 0x2901: Setting/Command Data
Set Units to F Command: 0x020100000000
Set Units to C Command: 0x020000000000
Start Temperature Updates Command: 0x0A0100000000
Set Target Temp
Byte 0: 1
Byte 1: Probe
Byte 2-3: TargetTemp low (??)
Byte 4-5: TargetTemp High (??)

The link given seems to use a connection so as to retrieve data. It works but decrease the battery life of the target.
I would prefer to use the data broadcasted instead.
Could you download nRFconnect launch a scan and send me several screenshots like this with the corresponding measured temperature?

image

This way we will be able to make the link between the broadcasted data and the temperatures seen.

Here is the log I did today with probes in 1,2, and 4 reading around 70F I didn’t really see much until I ran the BBQ app and it connected.

Blockquote
nRF Connect, 2021-09-21
iBBQ (34:03:DE:27:45:CD)
V 07:19:55.294 Connecting to 34:03:DE:27:45:CD…
D 07:19:55.294 gatt = device.connectGatt(autoConnect = false, TRANSPORT_LE, preferred PHY = LE 1M)
D 07:19:57.073 [Callback] Connection state changed with status: 0 and new state: CONNECTED (2)
I 07:19:57.073 Connected to 34:03:DE:27:45:CD
V 07:19:57.083 Discovering services…
D 07:19:57.083 gatt.discoverServices()
D 07:19:57.086 [Broadcast] Action received: android.bluetooth.device.action.ACL_CONNECTED
I 07:19:57.435 Connection parameters updated (interval: 7.5ms, latency: 0, timeout: 5000ms)
D 07:20:02.530 [Callback] Connection state changed with status: 8 and new state: DISCONNECTED (0)
E 07:20:02.530 Error 8 (0x8): GATT CONN TIMEOUT
I 07:20:02.530 Disconnected
D 07:20:02.560 [Broadcast] Action received: android.bluetooth.device.action.ACL_DISCONNECTED
D 07:20:32.119 gatt.close()
D 07:20:32.120 wait(200)
V 07:20:32.322 Connecting to 34:03:DE:27:45:CD…
D 07:20:32.322 gatt = device.connectGatt(autoConnect = false, TRANSPORT_LE, preferred PHY = LE 1M)
D 07:20:32.964 [Broadcast] Action received: android.bluetooth.device.action.ACL_CONNECTED
D 07:20:32.989 [Callback] Connection state changed with status: 0 and new state: CONNECTED (2)
I 07:20:32.989 Connected to 34:03:DE:27:45:CD
V 07:20:32.992 Discovering services…
D 07:20:32.992 gatt.discoverServices()
I 07:20:33.324 Connection parameters updated (interval: 7.5ms, latency: 0, timeout: 5000ms)
D 07:20:33.631 [Callback] Services discovered with status: 0
I 07:20:33.631 Services discovered
V 07:20:33.641 Generic Access (0x1800)

  • Device Name [R] (0x2A00)
  • Appearance [R] (0x2A01)
  • Peripheral Privacy Flag [R W] (0x2A02)
  • Reconnection Address [W] (0x2A03)
  • Peripheral Preferred Connection Parameters [R] (0x2A04)
    Generic Attribute (0x1801)
  • Service Changed [I] (0x2A05)
    Client Characteristic Configuration (0x2902)
    Device Information (0x180A)
  • System ID [R] (0x2A23)
  • Model Number String [R] (0x2A24)
  • Serial Number String [R] (0x2A25)
  • Firmware Revision String [R] (0x2A26)
  • Hardware Revision String [R] (0x2A27)
  • Software Revision String [R] (0x2A28)
  • Manufacturer Name String [R] (0x2A29)
  • IEEE 11073-20601 Regulatory Certification Data List [R] (0x2A2A)
  • PnP ID [R] (0x2A50)
    Unknown Service (0000fff0-0000-1000-8000-00805f9b34fb)
  • Unknown Characteristic [N] (0000fff1-0000-1000-8000-00805f9b34fb)
    Client Characteristic Configuration (0x2902)
    Characteristic User Description (0x2901)
  • Unknown Characteristic [W] (0000fff2-0000-1000-8000-00805f9b34fb)
    Characteristic User Description (0x2901)
  • Unknown Characteristic [N] (0000fff3-0000-1000-8000-00805f9b34fb)
    Client Characteristic Configuration (0x2902)
    Characteristic User Description (0x2901)
  • Unknown Characteristic [N] (0000fff4-0000-1000-8000-00805f9b34fb)
    Client Characteristic Configuration (0x2902)
    Characteristic User Description (0x2901)
  • Unknown Characteristic [W] (0000fff5-0000-1000-8000-00805f9b34fb)
    Characteristic User Description (0x2901)
    D 07:20:33.641 gatt.setCharacteristicNotification(00002a05-0000-1000-8000-00805f9b34fb, true)
    D 07:20:33.642 gatt.setCharacteristicNotification(0000fff1-0000-1000-8000-00805f9b34fb, true)
    D 07:20:33.642 gatt.setCharacteristicNotification(0000fff3-0000-1000-8000-00805f9b34fb, true)
    D 07:20:33.643 gatt.setCharacteristicNotification(0000fff4-0000-1000-8000-00805f9b34fb, true)
    I 07:20:33.729 Connection parameters updated (interval: 37.5ms, latency: 0, timeout: 5000ms)
    I 07:20:35.394 Connection parameters updated (interval: 375.0ms, latency: 4, timeout: 6000ms)
    D 07:21:04.644 [Callback] Connection state changed with status: 19 and new state: DISCONNECTED (0)
    W 07:21:04.644 Connection terminated by peer (status 19)
    I 07:21:04.644 Disconnected
    D 07:21:04.668 [Broadcast] Action received: android.bluetooth.device.action.ACL_DISCONNECTED
    D 07:21:28.839 gatt.close()
    D 07:21:28.840 wait(200)
    V 07:21:29.041 Connecting to 34:03:DE:27:45:CD…
    D 07:21:29.042 gatt = device.connectGatt(autoConnect = false, TRANSPORT_LE, preferred PHY = LE 1M)
    D 07:21:30.595 [Callback] Connection state changed with status: 0 and new state: CONNECTED (2)
    I 07:21:30.595 Connected to 34:03:DE:27:45:CD
    V 07:21:30.616 Discovering services…
    D 07:21:30.616 gatt.discoverServices()
    D 07:21:30.627 [Broadcast] Action received: android.bluetooth.device.action.ACL_CONNECTED
    I 07:21:30.959 Connection parameters updated (interval: 7.5ms, latency: 0, timeout: 5000ms)
    D 07:21:31.278 [Callback] Services discovered with status: 0
    I 07:21:31.278 Services discovered
    V 07:21:31.286 Generic Access (0x1800)
  • Device Name [R] (0x2A00)
  • Appearance [R] (0x2A01)
  • Peripheral Privacy Flag [R W] (0x2A02)
  • Reconnection Address [W] (0x2A03)
  • Peripheral Preferred Connection Parameters [R] (0x2A04)
    Generic Attribute (0x1801)
  • Service Changed [I] (0x2A05)
    Client Characteristic Configuration (0x2902)
    Device Information (0x180A)
  • System ID [R] (0x2A23)
  • Model Number String [R] (0x2A24)
  • Serial Number String [R] (0x2A25)
  • Firmware Revision String [R] (0x2A26)
  • Hardware Revision String [R] (0x2A27)
  • Software Revision String [R] (0x2A28)
  • Manufacturer Name String [R] (0x2A29)
  • IEEE 11073-20601 Regulatory Certification Data List [R] (0x2A2A)
  • PnP ID [R] (0x2A50)
    Unknown Service (0000fff0-0000-1000-8000-00805f9b34fb)
  • Unknown Characteristic [N] (0000fff1-0000-1000-8000-00805f9b34fb)
    Client Characteristic Configuration (0x2902)
    Characteristic User Description (0x2901)
  • Unknown Characteristic [W] (0000fff2-0000-1000-8000-00805f9b34fb)
    Characteristic User Description (0x2901)
  • Unknown Characteristic [N] (0000fff3-0000-1000-8000-00805f9b34fb)
    Client Characteristic Configuration (0x2902)
    Characteristic User Description (0x2901)
  • Unknown Characteristic [N] (0000fff4-0000-1000-8000-00805f9b34fb)
    Client Characteristic Configuration (0x2902)
    Characteristic User Description (0x2901)
  • Unknown Characteristic [W] (0000fff5-0000-1000-8000-00805f9b34fb)
    Characteristic User Description (0x2901)
    D 07:21:31.286 gatt.setCharacteristicNotification(00002a05-0000-1000-8000-00805f9b34fb, true)
    D 07:21:31.287 gatt.setCharacteristicNotification(0000fff1-0000-1000-8000-00805f9b34fb, true)
    D 07:21:31.287 gatt.setCharacteristicNotification(0000fff3-0000-1000-8000-00805f9b34fb, true)
    D 07:21:31.289 gatt.setCharacteristicNotification(0000fff4-0000-1000-8000-00805f9b34fb, true)
    I 07:21:31.369 Connection parameters updated (interval: 37.5ms, latency: 0, timeout: 5000ms)
    I 07:21:33.142 Connection parameters updated (interval: 375.0ms, latency: 4, timeout: 6000ms)
    I 07:21:47.772 Notification received from 0000fff1-0000-1000-8000-00805f9b34fb, value: (0x) 21-00-00-00-00-00
    A 07:21:47.772 “(0x) 21-00-00-00-00-00” received
    I 07:21:51.146 Notification received from 0000fff1-0000-1000-8000-00805f9b34fb, value: (0x) 23-03-0B-02-00-00
    A 07:21:51.147 “(0x) 23-03-0B-02-00-00” received
    I 07:21:52.646 Notification received from 0000fff1-0000-1000-8000-00805f9b34fb, value: (0x) FF-0B-00-00-00-00
    A 07:21:52.647 “(0x) FF-0B-00-00-00-00” received
    I 07:21:52.654 Notification received from 0000fff4-0000-1000-8000-00805f9b34fb, value: (0x) DC-00-DC-00-F6-FF-DC-00-F6-FF-F6-FF
    A 07:21:52.654 “(0x) DC-00-DC-00-F6-FF-DC-00-F6-FF-F6-FF” received
    I 07:21:53.397 Notification received from 0000fff1-0000-1000-8000-00805f9b34fb, value: (0x) 24-5A-1C-96-19-00
    A 07:21:53.397 “(0x) 24-5A-1C-96-19-00” received
    I 07:21:53.769 Notification received from 0000fff4-0000-1000-8000-00805f9b34fb, value: (0x) DC-00-DC-00-F6-FF-DC-00-F6-FF-F6-FF
    A 07:21:53.769 “(0x) DC-00-DC-00-F6-FF-DC-00-F6-FF-F6-FF” received
    I 07:21:54.143 Notification received from 0000fff1-0000-1000-8000-00805f9b34fb, value: (0x) FF-02-00-00-00-00
    A 07:21:54.143 “(0x) FF-02-00-00-00-00” received
    I 07:21:54.899 Notification received from 0000fff1-0000-1000-8000-00805f9b34fb, value: (0x) FF-FD-00-00-00-00
    A 07:21:54.899 “(0x) FF-FD-00-00-00-00” received
    I 07:21:54.900 Notification received from 0000fff4-0000-1000-8000-00805f9b34fb, value: (0x) DC-00-DC-00-F6-FF-DC-00-F6-FF-F6-FF
    A 07:21:54.900 “(0x) DC-00-DC-00-F6-FF-DC-00-F6-FF-F6-FF” received
    I 07:21:55.648 Notification received from 0000fff1-0000-1000-8000-00805f9b34fb, value: (0x) FF-03-00-00-00-00
    A 07:21:55.648 “(0x) FF-03-00-00-00-00” received
    I 07:21:55.648 Notification received from 0000fff4-0000-1000-8000-00805f9b34fb, value: (0x) DC-00-DC-00-F6-FF-DC-00-F6-FF-F6-FF
    A 07:21:55.648 “(0x) DC-00-DC-00-F6-FF-DC-00-F6-FF-F6-FF” received
    I 07:21:56.397 Notification received from 0000fff1-0000-1000-8000-00805f9b34fb, value: (0x) FF-12-00-00-00-00
    A 07:21:56.397 “(0x) FF-12-00-00-00-00” received
    I 07:21:56.774 Notification received from 0000fff4-0000-1000-8000-00805f9b34fb, value: (0x) DC-00-DC-00-F6-FF-DC-00-F6-FF-F6-FF
    A 07:21:56.774 “(0x) DC-00-DC-00-F6-FF-DC-00-F6-FF-F6-FF” received
    I 07:21:57.147 Notification received from 0000fff1-0000-1000-8000-00805f9b34fb, value: (0x) FF-01-00-00-00-00
    A 07:21:57.147 “(0x) FF-01-00-00-00-00” received
    I 07:21:57.894 Notification received from 0000fff1-0000-1000-8000-00805f9b34fb, value: (0x) FF-01-00-00-00-00
    A 07:21:57.894 “(0x) FF-01-00-00-00-00” received
    I 07:21:57.894 Notification received from 0000fff4-0000-1000-8000-00805f9b34fb, value: (0x) DC-00-DC-00-F6-FF-DC-00-F6-FF-F6-FF
    A 07:21:57.894 “(0x) DC-00-DC-00-F6-FF-DC-00-F6-FF-F6-FF” received
    I 07:21:58.646 Notification received from 0000fff1-0000-1000-8000-00805f9b34fb, value: (0x) FF-01-00-00-00-00
    A 07:21:58.647 “(0x) FF-01-00-00-00-00” received
    I 07:21:58.647 Notification received from 0000fff4-0000-1000-8000-00805f9b34fb, value: (0x) DC-00-DC-00-F6-FF-DC-00-F6-FF-F6-FF
    A 07:21:58.647 “(0x) DC-00-DC-00-F6-FF-DC-00-F6-FF-F6-FF” received
    I 07:21:59.772 Notification received from 0000fff4-0000-1000-8000-00805f9b34fb, value: (0x) DC-00-D2-00-F6-FF-DC-00-F6-FF-F6-FF
    A 07:21:59.772 “(0x) DC-00-D2-00-F6-FF-DC-00-F6-FF-F6-FF” received
    I 07:22:00.520 Notification received from 0000fff1-0000-1000-8000-00805f9b34fb, value: (0x) 24-6F-1C-96-19-00
    A 07:22:00.520 “(0x) 24-6F-1C-96-19-00” received
    I 07:22:00.896 Notification received from 0000fff4-0000-1000-8000-00805f9b34fb, value: (0x) DC-00-D2-00-F6-FF-DC-00-F6-FF-F6-FF
    A 07:22:00.896 “(0x) DC-00-D2-00-F6-FF-DC-00-F6-FF-F6-FF” received
    I 07:22:01.686 Notification received from 0000fff4-0000-1000-8000-00805f9b34fb, value: (0x) DC-00-D2-00-F6-FF-DC-00-F6-FF-F6-FF
    A 07:22:01.686 “(0x) DC-00-D2-00-F6-FF-DC-00-F6-FF-F6-FF” received
    I 07:22:02.773 Notification received from 0000fff4-0000-1000-8000-00805f9b34fb, value: (0x) DC-00-D2-00-F6-FF-DC-00-F6-FF-F6-FF
    A 07:22:02.773 “(0x) DC-00-D2-00-F6-FF-DC-00-F6-FF-F6-FF” received
    I 07:22:03.937 Notification received from 0000fff4-0000-1000-8000-00805f9b34fb, value: (0x) DC-00-D2-00-F6-FF-DC-00-F6-FF-F6-FF
    A 07:22:03.937 “(0x) DC-00-D2-00-F6-FF-DC-00-F6-FF-F6-FF” received
    I 07:22:04.648 Notification received from 0000fff4-0000-1000-8000-00805f9b34fb, value: (0x) DC-00-D2-00-F6-FF-DC-00-F6-FF-F6-FF
    A 07:22:04.648 “(0x) DC-00-D2-00-F6-FF-DC-00-F6-FF-F6-FF” received
    I 07:22:05.815 Notification received from 0000fff4-0000-1000-8000-00805f9b34fb, value: (0x) DC-00-D2-00-F6-FF-DC-00-F6-FF-F6-FF
    A 07:22:05.815 “(0x) DC-00-D2-00-F6-FF-DC-00-F6-FF-F6-FF” received
    I 07:22:06.893 Notification received from 0000fff4-0000-1000-8000-00805f9b34fb, value: (0x) DC-00-D2-00-F6-FF-DC-00-F6-FF-F6-FF
    A 07:22:06.893 “(0x) DC-00-D2-00-F6-FF-DC-00-F6-FF-F6-FF” received
    I 07:22:07.687 Notification received from 0000fff4-0000-1000-8000-00805f9b34fb, value: (0x) DC-00-D2-00-F6-FF-DC-00-F6-FF-F6-FF
    A 07:22:07.687 “(0x) DC-00-D2-00-F6-FF-DC-00-F6-FF-F6-FF” received
    I 07:22:08.773 Notification received from 0000fff4-0000-1000-8000-00805f9b34fb, value: (0x) DC-00-D2-00-F6-FF-DC-00-F6-FF-F6-FF
    A 07:22:08.773 “(0x) DC-00-D2-00-F6-FF-DC-00-F6-FF-F6-FF” received
    I 07:22:09.937 Notification received from 0000fff4-0000-1000-8000-00805f9b34fb, value: (0x) DC-00-D2-00-F6-FF-DC-00-F6-FF-F6-FF
    A 07:22:09.937 “(0x) DC-00-D2-00-F6-FF-DC-00-F6-FF-F6-FF” received
    I 07:22:10.648 Notification received from 0000fff4-0000-1000-8000-00805f9b34fb, value: (0x) DC-00-D2-00-F6-FF-DC-00-F6-FF-F6-FF
    A 07:22:10.648 “(0x) DC-00-D2-00-F6-FF-DC-00-F6-FF-F6-FF” received
    I 07:22:11.815 Notification received from 0000fff4-0000-1000-8000-00805f9b34fb, value: (0x) DC-00-D2-00-F6-FF-DC-00-F6-FF-F6-FF
    A 07:22:11.816 “(0x) DC-00-D2-00-F6-FF-DC-00-F6-FF-F6-FF” received
    I 07:22:12.894 Notification received from 0000fff4-0000-1000-8000-00805f9b34fb, value: (0x) DC-00-D2-00-F6-FF-DC-00-F6-FF-F6-FF

Could you senda screenshot of NRFconnect app as the one that I have posted.

This screenshot presents 3 important data that I don’t see on your logs:

  • Manufacturer data
  • Service data
  • Local name

The log given is more a “point to point connection” when the smartphone issue a BLE connection to the device. But what I would like to achieve first is to get the data by passively listening for the broadcasted packets.
This is where the screenshot and the data listed above would help.

Here is a schema that sum up the differences

I am probably not using rfconnect right since I don’t see much of anything in the log until I probe the data values. So I logged everything from that device for a while then told it to read the device information attributes before turning on notifications from the data characteristics. I logged all of this and the file is at:
https://drive.google.com/file/d/1LEYtgbwS3no4UwxCQHGe9h_cLpSFHMcR/view?usp=sharing

If this isn’t what you need can you tell me how to get it with rfConnect because I am not doing well.

The steps are the following:

  • launch NrfConnect mobile app
  • click on scan
  • identify your BBQ sensor
  • click on its name (not on connect)
  • screenshot the information like below

1 Like

I suppose that you were seeing on the screen:

Probe 1: 21C
Probe 2: 20C
Probe 3: not connected
Probe 4: 21C
Probe 5: not connected
Probe 6: not connected

isn’t it?

yes that is correct for the probes