[AI-generated for clarity]
Hey all,
I love the Homey Pro – the hardware is rock solid, the radios are all in one place, and the software is refreshingly easy to use. But as much as I enjoy the Homey ecosystem, I’ve always longed for the larger community, add-ons, and flexibility of Home Assistant. I’ve run HA before on dedicated hardware, and I kept wishing there was a way to bring the two worlds together.
That’s what led me to build Cassa HA - Core Automation & Smart System Assistant
The core idea
- A Homey Pro backup (
.homeyprobackup) is just a raw.imgfile with some header data. - My tool modifies that backup image in place — no OS redistribution, nothing proprietary bundled.
- The result: a Homey Pro that boots directly into Home Assistant.
- All Homey services are disabled so only Home Assistant runs on the device.
In other words, you can turn your Homey Pro into a dedicated Home Assistant box using just your own backup file.
Why this is exciting
- Homey Pro hardware + HA’s massive community = best of both worlds.
- No second device needed — everything runs on the Homey Pro itself.
- No redistribution of proprietary files; the magic happens on your backup.
- You can always restore a stock backup to roll back.
Coprocessor bridge add-on (WIP)
I’m also working on a Homey Coprocessor bridge add-on for HA:
- Currently focused on Z-Wave and LED integration.
- Zigbee is already directly exposed to the OS, so no bridge needed there.
- Still very WIP — I only have one device to test with, and it’s hacky.
- To respect Athom’s IP, I’m not distributing binaries — just glue code built from what I learned by reverse engineering.
How it works
- Back up your Homey Pro (you get a
.homeyprobackupfile). - Run my tool — it unpacks the header, modifies the raw
.img, and bootstraps Home Assistant. - Restore that backup to your device.
- Boot into a dedicated Home Assistant system on Homey Pro hardware.
Repo
GitHub: MrDaGree/cassa-ha
Docs, usage, and a breakdown of how the bootstrap works are in the README. I’d appreciate any support/broken reporting utilize Github Issues.