Smartfire 5.0 Home Assistant integration

Unofficial, local Home Assistant integration for the Smartfire 5.0 BBQ controller.

Home Assistant Community discussion

Status: alpha / read-only. This project is not affiliated with or endorsed by Smartfire. Undocumented write, OTA, filesystem, Wi-Fi and system RPC calls are intentionally not exposed.

Smartfire 5.0 can expose useful cooking data directly on the local network. This integration reads that data through the controller's local WebSocket RPC interface, so Home Assistant sensor updates do not require IFTTT or a cloud webhook.

• Local LAN communication
• Pit temperature and pit target
• Food probes 1–3 and their targets
• Disconnected probes reported as unknown
• Fan percentage
• Wi-Fi RSSI and Wi-Fi/cloud connectivity
• Mode and alarm state
• Celsius/Fahrenheit display selection
• Home Assistant UI config flow

1. Open HACS → Integrations.
2. Open the menu and choose Custom repositories.
3. Add https://github.com/jkrchd/home-assistant-smartfire as category Integration.
4. Install Smartfire 5.0.
5. Restart Home Assistant.
6. Go to Settings → Devices & services → Add integration and search for Smartfire 5.0.
7. Enter the controller's LAN address and choose the preferred temperature unit.

1. Copy custom_components/smartfire to /config/custom_components/.
2. Restart Home Assistant.
3. Go to Settings → Devices & services → Add integration.
4. Search for Smartfire 5.0.
5. Enter the controller LAN address and choose the temperature unit.

The initial development and testing has been performed against a Smartfire 5.0 controller. Reports from other firmware versions are especially useful while the integration is in alpha. Please add results to the compatibility testing issue in this repository.

The current Smartfire 5.0 local RPC authentication uses a device-family credential recovered from Smartfire's publicly served browser-side recovery code, rather than a credential supplied by the Home Assistant user. It is therefore present in the integration implementation. Treat the local Smartfire RPC service as trusted-LAN-only and do not expose port 80/RPC to the Internet.

The integration is intentionally read-only. The device exposes additional configuration, filesystem, OTA, Wi-Fi and reboot RPC methods whose behavior has not been sufficiently verified.

Local cooking-control support is being investigated conservatively. Write support will only be added after the official app's behavior has been observed and the relevant calls can be reproduced without relying on unsafe trial-and-error.

See docs/PROTOCOL.md for protocol notes and confidence levels.

Entity IDs depend on the Home Assistant device name. Typical entities include pit temperature/target, three food probes and targets, fan, RSSI, Wi-Fi/cloud connectivity and the temperature-unit selector.

Reports from other Smartfire 5.0 owners are welcome. Please include controller firmware, Home Assistant version, installation method, relevant logs, and which entities work or fail. Remove private network details, credentials and webhook URLs before posting.

MIT.