Firewalla Local: Native, local, zero-latency Home Assistant control

Of course I have been looking for something like this and never found anything. I built my own MQTT version that only pulls statistics. I’ll have to check this one out.

1 Like

Firewalla Local 1.1.6 is now available

Install via HACS → Integrations → Firewalla Local and restart Home Assistant.

What’s new since 1.1.5

  • WAN-scoped speed test sensors — the old global sensor is replaced with per-WAN download, upload, and latency entities. :warning: Breaking change — update any automations or dashboards using the old sensor.
  • Rule transparency — rule switches now show applies_to, applies_to_kind, and category attributes so you can see who or what each rule targets.
  • Better identity labels — group-backed names (watched-users, watched-devices, device trackers) now show the app-visible name instead of internal group IDs.
  • WireGuard peer support — standalone VPN peers are now selectable as watched devices.
  • Full pairing protocol documented in the repo for anyone curious how the QR → cloud → local key exchange works.
  • Enhanced capture tooling for users willing to help debug remaining pairing issues (details below).

Pairing is working across all Firewalla models (Gold, Gold Plus, Gold SE, Purple confirmed) and the core path has been solid through a month of alpha/beta testing with no regressions.

A small number of users are hitting pairing failures that look environment- or version-specific. I’ve exhausted everything I can debug without packet-level data.

[!IMPORTANT]
If you’re experiencing pairing failures, the capture tooling now makes it easy to generate a redacted analysis report that’s safe to share publicly. Please open an issue at GitHub - ccpk1/firewalla-local-ha: 🔥 Native Home Assistant control for Firewalla. 100% local data, zero latency, and no cloud middleman. · GitHub and follow the instructions in WINDOWS_PACKET_CAPTURE_USAGE.md. I need a few users to step up with captures to close this out.

I may have missed this in the documentation or this thread, but is it possible to use this integration to enable/disable a wi-fi network that’s being broadcast from a Firewalla AP7? Or is this integration just for the Firewalla gateway products? I only ask because it seems the functionality through this integration seems to mimic what the app can do.

The integration was originally built around the Firewalla gateway products rather than their newer Wi-Fi gear—and since I don’t own any of the AP7 products, I haven’t looked into it.

However, it’s highly likely we can extend the integration to support AP7 features. Since the AP7 relies on a Firewalla gateway, its Wi-Fi configurations are almost certainly managed and stored on the gateway itself, using the same API endpoints as the rest of the network settings.

If you’re up for some collaborative troubleshooting, I’d be willing to look into this with you. Here is how we can get started:

  1. Open a Feature Request: Head over to the GitHub repo and open a new feature request so we can track this. ccpk1/firewalla-local-ha: :fire: Native Home Assistant control for Firewalla. 100% local data, zero latency, and no cloud middleman.
  2. Gather Data: We’ll need some configuration details and network packet captures of the app toggling the Wi-Fi network.
  3. Analyze: I recently updated the packet capture tooling (which makes this pretty straightforward to run from a Windows system), so capturing the right API calls should be relatively painless.

Let me know.

1 Like

Firewalla Local 1.1.8 is now available

Pairing fix — this is the big one

If you tried setting up the integration before and got stuck with a pairing failure, please try again. Several users have confirmed that the issue is resolved for them across various models that were affected. The root cause was a difference in how some Firewalla boxes handle key derivation during provisioning, and the integration now handles both paths correctly.

New: route rule toggle support

Route rules (like “route category Tiktok for VLAN IOT”) can now be selected as switch entities just like allow, block, and QoS rules. Pick them in the options flow and toggle them on and off from your dashboard. They also work with the existing pause and resume services.

Upgrading

Go to HACS → Integrations → Firewalla Local and install version 1.1.8. Restart Home Assistant. No config entry changes needed — existing setup continues to work as before.

:heart: Support the Project

As always, building and maintaining local-first integrations takes a massive amount of time, testing, and coffee. If Firewalla Local is making your smart home better, please consider supporting the project!

:star: Star the repository on GitHub! (Free & easy way to help the project grow)
:hot_beverage: Sponsor on GitHub or Buy Me A Coffee

Firewalla Local 1.2.0 is now available

Device tracker fix

If you’ve configured device trackers and noticed devices showing up as unavailable or losing their proper name, please check again. The root cause was that the Firewalla box only returns recently-active hosts by default, so any device that dropped out of the recent-activity window lost its name and reported unavailable — even if it was still configured. The integration now requests the full host inventory (including inactive hosts / past hosts which Firewalla defines as those that have not been online for more than 7 days), so your tracked devices keep their names and stay available. We also added a safety guard so a transient empty inventory can never wipe out your configured devices.

New: delete host service

You can now remove a host from your Firewalla directly from Home Assistant via the firewalla_local.delete_host service. It accepts one or many MAC addresses, requires an explicit confirm: true gate (it’s destructive — no accidental deletions), skips any MAC it can’t find, and returns a per-host result so you can see exactly what succeeded and what didn’t.

New: Amnezia WG peer support

Firewalla recently added Beta Amnezia VPN support. Amnezia WG (AWG) peers now appear in the host inventory just like WireGuard peers, so you can select them as watched devices and monitor their online/offline status as binary sensors.

AP7 wireless status (view-only for now)

We’ve added get_wireless_status services for the AP7 wireless config. Note: this is view-only / experimental until we can confirm the write contract with packet captures — the goal is full sensor and control support for the Wi-Fi access points in a future release. There is an open enhancement request in the github repo for any of you that have these devices and want to get involved in testing and feature implementation. [Feature]: Wireless Network Toggle for AP7 · Issue #21 · ccpk1/firewalla-local-ha

Diagnostics improvements

The diagnostic download now includes the raw runtime init payload (with best-effort redaction of sensitive values like JWTs, MACs, IPs, and emails) so you can share useful data for troubleshooting without exposing secrets.

Upgrading

Go to HACS → Integrations → Firewalla Local and install version 1.2.0. Restart Home Assistant. No config entry changes needed — existing setup continues to work as before.

:heart: Support the Project

As always, building and maintaining local-first integrations takes a massive amount of time, testing, and coffee. If Firewalla Local is making your smart home better, please consider supporting the project!

:star: Star the repository on GitHub! (Free & easy way to help the project grow)
:hot_beverage: Sponsor on GitHub or Buy Me A Coffee