Closed MortenVinding closed 1 year ago
MortenVinding
commented
1 year ago Not really sure if any of the data from Home Assistant is of any use, but en LightBlue I have found a value there seems to change with temperature, although I haven't been able to figure out if it's HEX, DEC or F or C. UUID: 7EDDA774-045E-4BBF-909B-45D1991A2876
Ernst79
commented
1 year ago I had a look, I see two (passive) messages
0cff7b03002da55321c1b50961
and
05ff037b0000
I don't see anything changing. Did you made this log during heating up (if not, can you try?)
As example, the short messages
05 = length (5 bytes)
ff = manufacturer specific data
037b = company id
0000 = data (off?)
MortenVinding
commented
1 year ago I had a look, I see two (passive) messages
I don't see anything changing. Did you made this log during heating up (if not, can you try?)
thank you. so nice of you to look in to this.
no this is all at room temperature. I’m on vacation right now, but I will try to make a capture while heating up, once I get back home.
MortenVinding
commented
1 year ago I had a look, I see two (passive) messages
I don't see anything changing. Did you made this log during heating up (if not, can you try?)
So I tried to do logging while heating it up, but I don't see any changes (even when filtering trough "uniq") :(
bluetoothctl reports:
[bluetooth]# info B8:1F:5E:1C:42:95
Device B8:1F:5E:1C:42:95 (public) Name: MEATER Alias: MEATER Paired: no Trusted: yes Blocked: no Connected: no LegacyPairing: no UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb) UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb) UUID: Vendor specific (a75cc7fc-c956-488f-ac2a-2dbc08b63a04) ManufacturerData Key: 0x7b03 ManufacturerData Value: 00 00 .. ManufacturerData Key: 0x037b ManufacturerData Value: 00 2d a5 53 21 c1 b5 09 61 .-.S!...a RSSI: -75 AdvertisingFlags: 06 .
Noting seems to change there either during heating up.
Do you have any suggestions to what else I might try, or is it just not feasible for ble monitor?
Ernst79
commented
1 year ago In that case, the device requires a Bluetooth connection. This is not possible with BLE monitor. You could try with ESPhome BLE cliënt. Im Vlissingen the issue here, as there is nothing I can do in BLE monitor.
MortenVinding
commented
1 year ago I have made a ESPHome yaml to use a MEATER probe in HA.
Need to specify ESP type (currently set to ESP32C3) and MEATER probe MAC address.
And the MEATER probe can unfortunately only connect to one device at at time.
pissten
commented
5 months ago @MortenVinding I have been using your ESPhome yaml for almost a year now, thank you so much for your great efforts on putting this together! But, recently it seems like the meater probe won't connect anymore :/ Are you experiencing the same? I have upgraded HA to 2024.3.1 prior to seeing these connection issues, and also ESPhome (2024.2.2). Maybe related to something changed in the newest releases?
MortenVinding
commented
5 months ago @MortenVinding I have been using your ESPhome yaml for almost a year now, thank you so much for your great efforts on putting this together! But, recently it seems like the meater probe won't connect anymore :/ Are you experiencing the same? I have upgraded HA to 2024.3.1 prior to seeing these connection issues, and also ESPhome (2024.2.2). Maybe related to something changed in the newest releases?
Thank you.
To be honest I myself lost interest in this when I realized that the probe can’t be used with the app at the same time.
I have move my yaml to my gist, think it’s easier to keep it there: https://gist.github.com/MortenVinding/a513c0094d0df41a4425612257b3cabc
But I can try and have a look and at least see if I still can make it connect
pissten
commented
5 months ago @MortenVinding Yeah, it was unfortunate that the probe didn't support coexisting connections for both app and epshome. But I just hate that the probe has to seize my phone during a long time cooking also. With your Esphome integration I've been happy with the functionallity, becasue I've implemented a dashboard that's beeing casted to my google hub, and also made some automations that broadcasts notifications upon temp theshold etc..
were you able to connect to your probe still, using the esphome solution?
Sensor Description
The Original MEATER
Additional information
Hi,
I have a MEATER bluetooth LE cooking thermometer: https://store-eu.meater.com/products/meater 2
Meater produces 3 versions: The original MEATER, MEATER plus and MEATER Block
The last one is supported using the MEATER integration, but it relies on a cloud service and uses wifi.
All 3 versions is using self-contained bluetooth LE probes that can connect by bluetooth directly to a phone. I have used LightBlue (app) to sniff trafik from it, and it seems to use simple unencrypted bluetooth, so I believe it should be reasonably simple to implement a direct integration, possibly using ESPHome bluetooth proxy.
But this is way out of my abilities :frowning: If anyone is up for this task, I’m more than willing to provide any info I can gather from LightBlue or what ever app’s that might be helpful.
Collected data is done at room temperature.
BLE advertisements