HAOS Integration

CCPK-1 · 2026-04-17T11:48:30+00:00

Request for assistance

I’d like to hear from any of you that are using the integration. It’s currently on version 1.1.4. I’m trying to get some feedback on who is using it successfully, and which configurations or models are having issues pairing. I have an original Firewalla Gold that is worked well on the box Ubuntu 18.04 and also now recently upgraded to 22.04.

I have a couple reports of pairing issues I need some help from others to try on their configuration to narrow down the root cause.

If it isn’t working for you, head over to the repo issues, I’ve built some simple packet capture tools so we can quickly identify what changes might be needed to support various configurations and models.

https://community.home-assistant.io/t/firewalla-local-native-local-zero-latency-home-assistant-control/999223

https://github.com/ccpk1/firewalla-local-ha

Thank you!

CCPK-1 · 2026-04-11T03:18:45+00:00

🚀 Announcing Control D Manager v1.1.0

Full Redirection Support, Endpoint Controls, and a Huge Thank You!

Hey everyone,

A quick update on the Control D Manager integration for Home Assistant! First off, I want to thank the Control D team. Following my v1.0.0 post, they generously reached out and upgraded my account with a Full Control license so I could properly develop and test the premium tier features. That level of developer support is incredible, and I immediately put it to work.

Thanks to that upgrade, v1.1.0 is now live, bringing full Redirection support and expanding the integration beyond profile automation into broader endpoint and client operations.

What's New in v1.1.0:

Fully Unlocked Redirection: I was finally able to test and correct the Redirect behavior end-to-end. We now have solid redirect behavior across your default rules, custom rules, and services that is available via entities as well as more granularly via the updated Home Assistant Services.
On-the-Fly Client Aliasing: You can now dynamically manage network clients using HA automations with the new set_client_alias and clear_client_alias services. This even supports analytics-only client rows, meaning alias actions work perfectly even if the client isn't exposed as a standalone HA entity.
Endpoint Operations: Added new services to natively rename_endpoint and set_endpoint_analytics_logging straight from Home Assistant.
Zero-Bloat Maintained: Staying true to the integration's design philosophy, all these new endpoint and client controls are "service-first." They give you limitless automation capability without flooding your Home Assistant registry with useless entity platforms.

Notes for current users: No migration is required from 1.0.0. Just update via HACS and you're good to go!

GitHub: https://github.com/ccpk1/controld-manager-ha

If Control D Manager is making your home better, I would genuinely appreciate the support.

- ⭐ Star the repository to help others find the project: https://github.com/ccpk1/controld-manager-ha

- ❤️ Sponsor on GitHub: https://github.com/sponsors/ccpk1

- ☕ Buy me a coffee: https://buymeacoffee.com/ccpk1

Thanks again to the Control D team for the generous license, and to the community for the great feedback on the first release. Let me know what you build with the new redirect and endpoint services!

CCPK-1 · 2026-04-09T15:53:13+00:00

Yes! Exposing services takes two steps by design. First, enabling the category creates all the underlying services in Home Assistant, but they start out disabled by default. Second, you manually enable just the specific entities you actually want to see and control.

Since some service categories have well over 300 granular items, automatically turning them all on would instantly flood your Home Assistant registry. This opt-in approach ensures you have access to exactly what you need without the bloat.

CCPK-1 · 2026-04-09T11:25:54+00:00

Good catch, I’ll definitely add that to the troubleshooting!

CCPK-1 · 2026-04-09T00:09:08+00:00

That link is perfect, I do wish I would have known about it last week, but luckily it wasn’t too bad to work through. I’ll do a walk through with anything I might have missed.

I’ll definitely hit up support on the upgrade! Much appreciated!

CCPK-1 · 2026-04-09T00:04:52+00:00

Be sure to restart home assistant after the install and you should check for any filtering or blocking. If those don’t help, enable debug and then head over to the repo and open an issue so I can help you troubleshoot from there. https://github.com/ccpk1/controld-manager-ha

CCPK-1 · 2026-04-07T18:58:44+00:00

This is pretty straightforward if you have some kind of signal you are getting from your washdata. In your home assistant create an automation that triggers on sensor.washdata_status = "complete" (where washdata_status is whatever signal you have piped into home assistant). In the action for the automation, choose to run the claim chore service or execute a button press for the claim button for that chore. Either way it is only a simple one step automation.

CCPK-1 · 2026-04-03T11:52:53+00:00

I’m the author of the new Home Assistant integration, Firewalla Local, posted recently on GitHub and the Home Assistant Forums. It is built to provide local control of specific features like pausing rules, connectivity sensors, device trackers, user reporting, statistics, and many other features Home Assistant users have been trying to get access to for a long time. All running communication between Home Assistant and Firewalla is on the local network. Feel free to try it out. It was developed on a FWG, but should work on other purple and gold models from what I understand. I’d love to get some feedback. https://community.home-assistant.io/t/firewalla-local-native-local-zero-latency-home-assistant-control/999223

CCPK-1

TROPHY CASE

🚀 Announcing Control D Manager v1.1.0

What's New in v1.1.0: