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
If anyone is up for this task (@bdraco ?), Iām more than willing to provide any info I can gather from LightBlue or what ever appās that might be helpful.
I think the best way would be to see if the BLE Passive monitor integration could handle this.
The framework for catching the BLE data and pass them on to HA is already there, so it is just a matter of decoding the device communication.
BTW: always remember to vote for your suggestions.
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
Any update on the Meater BLE soultion? Would be great to have a bluetooth proxy and/or a direct blueooth integration for HA. Meater is great, but I donāt like to āwasteā my phone for cooking purposes for hours
I have made a ESPHome yaml config to get it in to HA.
But the MEATER probe can only handle one bluetooth connection a time, so you canāt have it both in HA and connected to the app.
What I really would like to do, is to have ESPHome broadcast the MEATER data either as UDP packages or send it to the MEATER MQTT cloud server.
It looks like the MEATER block, and the MEATER app does both.
Notice itās for a ESP32-C3, but will also compile for classic ESP32.
You will have to find your MEATERās MAC address and ad to the yaml
Hi,
I just received my Wemos D1 Mini EPS32 and would like to try this. How did you get the Mac of the meater?
It is not on the device and hwn it is connecte dto my Iphone I canĀ“t find it and my Windows PC does not even want to connect to it at all. Any hint on how to easily get the Mac?
Hi @MortenVinding, Iāve taken the code you posted above and it seems to be working, although my Meater is showing the same value for ambient and tip. Have you come across this?
I think that this is a Meater feature rather than a bug. In the Meater app the ambient sensor doesnāt report back under 40 degrees (docs), in this case the code above reports back the same values for both.
First of all, great work and thanks for sharing the esphome code! But in line with earlier questions, do you you ever get different readings for tip and ambient? Just tested it with some hot water where the probe is submerged in hot water, just above ālineā and the black part is clearly on the outside.
Even at 90C, the reading stays the same for both ambient and tip, so I guess there is something amissā¦either in my probe, or in the codeā¦
Update: Never mindā¦that was an evening wastedā¦I had in my mind that the minimum of the tip should be over 40C to show differencesā¦but of course this should be that the ambient should be over 40C to see it changingā¦Put my test setup in a preheating oven and quickly saw the ambient temperature rising whereas the tip stayed the same. Ah wellā¦did learn some new stuffā¦
Hi
Just noticed your post. I am exeriencing exactly the same disconnectoin after a while.
If connected to the Meater app it does not happen. I suspect there is some kind of keep-alive signal sent to the thermometer to keep it running.
Anyone have a suggestion how to pick this up between the app and the probe? Then it would probably be fairly straight forward to add this to the ESPHome code.