Traeger WiFIRE
johnvoipguy/Traeger-WiFire · vv1.0.3c
Home Assistant Traeger WiFire Integration
In Apple Home through HomeKit Bridge
What HomeKit Bridge makes of each kind of entity this integration creates, read from its source code. A device only gets the ones that apply to it.
| Entity | Shows up as | Note |
|---|---|---|
switch | Switch or outlet | |
climate | Thermostat | |
sensor | Sensor (temperature, humidity, air quality…) | |
select | Mode picker (as switches) |
What people report
Traeger grills work through the cloud-based integration; models lacking a pellet hopper sensor needed a fix, and probe support depends on user-supplied API data.
- Partly works2
| Device | In Home Assistant | In Apple Home | What they said | Source |
|---|---|---|---|---|
| Traeger Pro 780 | Partly works | No pellet sensor; firmware reports 0, now shown as unavailableSaved copyProblem On grill models without a physical pellet hopper sensor (e.g. Pro 780), Traeger firmware always reports `pellet_level: 0` in the MQTT status payload as a sentinel value, not a real reading. This causes the Pellet Level entity in Home Assistant to permanently display 0%, which is misleading because the entity appears functional but is silently reporting a hardcoded value. ## Root cause The `TraegerSensor.native_value` for `pellet_level` falls through to the generic `state["status"]["pellet_level"]` return, which blindly returns `0` regardless of whether a sensor is physically present. … Excerpt saved from GitHub on 2026-10-23. | PR #17 · 2026-05 | |
| Traeger Timberline (2023) | Partly works | Meater probes initially missing; contributor got probe data workingSaved copy… work, the integrations looks very good so far. I've noticed that my Meater Probes are not visible at the moment. Maybe I'm just missing something? Using a Traeger Timberline (2023) with most recent firmware. Regards, Tweak90 Excerpt saved from GitHub on 2026-10-23. | Issue #1 · 2025-09 |
Gathered from GitHub issues, pull requests, discussions and docs, and from r/homeassistant. These are individual reports, so check the linked thread and the date before you buy.
How it connects
Cloud push
Goes through the maker’s cloud, which sends updates as they happen. Needs the internet and an account.
Details
| Installs (analytics) | 589 (0.08%) |
|---|---|
| GitHub stars | 15 |
| Latest version | v1.0.3c (2026-06-05) |
| Set up in the UI | Yes |
| Maintainers | @johnvoipguy |
| License | MIT |
Notable forks
Forks with stars, or with code pushed at least 90 days after the original’s last push. Useful when the original goes quiet.
| Fork | Stars | Last push | Description |
|---|---|---|---|
| frenck/Traeger-WiFire Newer code | ★ 0 | 2026-10-07 | Home Assistant Traeger WiFire Integration |
| timgrov/Traeger-WiFire Newer code | ★ 0 | 2026-10-19 | Home Assistant Traeger WiFire Integration |
In ReReHome
Whatever HomeKit Bridge shares reaches Apple Home as normal HomeKit accessories behind your Home Assistant bridge, so ReReHome shows and controls them like any other.
Bridges get their own settings page listing the accessories behind them.
Sources
- Documentation: https://github.com/johnvoipguy/hacs-Traeger-WiFire
- Source code: https://github.com/johnvoipguy/Traeger-WiFire
- Issues: https://github.com/johnvoipguy/hacs-Traeger-WiFire/issues
- HACS: https://hacs.xyz
