Add support for H5192 (2-probe) and H5194 (4-probe) meat thermometers #4108
Unanswered
bwright86
asked this question in
Integration enhancements
Replies: 1 comment
-
|
🏷️ I've automatically added the |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Integration name
Govee-BLE
Link to integration documentation on our website
https://www.home-assistant.io/integrations/govee_ble
Describe the enhancement
Requesting support for two additional Govee meat thermometer models that are close variants
of the already-supported H5191:
H5192 — Strong case for near-identical support
The H5192 shares the same FCC ID as the H5191 (
2A7VD-H5192) and the same user manual(
GoveeLife H5191/H5192 Smart Wireless Meat Thermometer). They are the same hardwareplatform — the H5192 simply includes a second wireless probe.
Given the shared FCC ID and firmware base, the BLE advertisement format is very likely
identical or a simple extension of the H5191 (additional probe data channel). It may be
as simple as aliasing
H5192to the existing H5191 parser and adding a second probeentity.
BLE advertisement name:
GoveeLife_H5192_XXXX(last 4 chars of MAC, same pattern as H5191)Active scan required: Yes — same as H5191 (device does not advertise passively).
Product page: https://us.govee.com/products/goveelife-smart-wireless-meat-thermometer-h5192
H5194 — 4-probe variant
The H5194 is the 4-probe model in the same product family. While I don't own this unit,
requesting it here alongside H5192 since the parser work for multi-probe devices would
be shared.
Product page: https://us.govee.com/products/ (search H5194)
What I can provide
I own an H5192 and can:
bluetoothctlorhcidump) if neededPlease let me know what BLE advertisement data would be most useful and I'll capture it.
Environment
Use cases
BBQ / smoker monitoring — Simultaneously monitoring multiple cuts of meat at
different target temperatures (e.g., brisket flat vs. point, or multiple racks of
ribs), with HA automations triggering alerts or adjusting vent/fan controllers when
targets are reached.
Home Assistant automations — Using probe temperatures as triggers: notify when
meat hits target temp, log cook history to InfluxDB/Grafana, or integrate with
a smoker controller (e.g., automatically shut down a pellet grill via a smart plug
when the target is hit).
Multi-zone oven/grill cooking — Tracking both the internal meat temperature and
the ambient grill temperature simultaneously across two or more probes for
precision cooking.
Historical tracking — Recording temperature curves over long cooks (brisket,
pork shoulder) in HA's history / Grafana for repeatable results.
Anything else?
No response
Beta Was this translation helpful? Give feedback.
All reactions