Why Home-A-Genius Did Not Build on Home Assistant, Even Though We Could

We Could Build on Home Assistant. Here's Why We Don't.
TL;DR
- Home-A-Genius has the technical capability to build on Home Assistant. We have chosen not to.
- Home Assistant can do impressive things, but "easy for our engineers" is not the same as "right for your family."
- We use a defined range of devices and supported combinations so we can support everything we connect.
- Neither "proprietary" nor "open source" is a security guarantee. What matters is who can access the system, how remote access is secured and who keeps it updated.
- If you value extensive customisation and direct technical control, Home Assistant may be exactly what you want. We build for families who want a home that asks less of them.
It's 11:47 p.m. You're carrying a half-asleep toddler. You walk into the hallway.
The lights should come on.
You are not interested in which integration handles the sensor, whether a software update changed something, or who remembers the administrator password.
You just want to get your child to bed.
That moment explains our platform decision better than a list of technical specifications ever could.
At Home-A-Genius, we have the technical capability to build a smart-home offering on Home Assistant. Its established foundation and extensive integrations would give our engineers a substantial head start.
We have chosen not to.
Home Assistant can do impressive things. But "easy for our engineers" is not the same as "right for your family."
Who Is Home-A-Genius Built For?
Homeowners who love what technology does, without wanting to look after the technology itself.
There is a particular kind of person who hears "I spent the weekend rebuilding my automations" and thinks, That sounds fun.
We understand those people. We have engineers too.
But perhaps your ideal weekend involves breakfast with the children, a good coffee and absolutely no interest in why a sensor has stopped reporting.
That is the homeowner we build for.
Our goal is to make the system-administrator role unnecessary for their everyday life, rather than turning every customer into a more capable one.
What Happens After a Smart Home Is Installed?
Real life happens, and someone has to look after the system. The showroom demo is the easy part.
A light turns on. A curtain opens. Someone says, "Wow."
Good start. But nobody lives in a demonstration.
In an actual home:
- The router gets replaced.
- A device fails.
- Software changes.
- The person who understands the setup goes overseas, while everyone else would quite like the living room to keep behaving normally.
That is where the less glamorous questions matter:
- Who checks updates?
- Who investigates a problem across several devices?
- Who restores the setup if something goes wrong?
Home Assistant has tools for updates, backups and recovery. A good professional can maintain a reliable installation around it. But those tools do not make responsibility disappear. Someone still has to do the work.
The same is true for us.
Starting with an existing platform could save development effort. It would not save us from the responsibility of looking after the finished experience.
We have chosen to put that effort into our own platform and the way we deliver it.
Does More Device Compatibility Mean a Better Smart Home?
Not on its own. "Can connect" is a surprisingly low bar.
Imagine choosing a family car because it accepts the greatest number of aftermarket parts.
Useful? Potentially. The first thing you would ask about? Probably not.
You would want to know how it drives, how it behaves when something goes wrong and who can take care of it.
Smart homes deserve the same questions.
Home Assistant's breadth is a genuine strength. But a long compatibility list does not, on its own, tell you how a particular combination will behave in your home.
For our core offering, we choose a defined range of devices and supported combinations. Sometimes that means saying no to something we could technically connect.
Connecting it is only the beginning. We also need to be prepared to support it.
Is Open-Source Smart Home Software Less Secure?
Not automatically. Neither "proprietary" nor "open source" is a security guarantee. Security is not a game of hide-and-seek.
"If hackers can read the source code, surely it is easier to attack?"
It is a fair question. Public code can help attackers look for weaknesses, and AI can accelerate parts of that search.
But the same visibility lets maintainers and independent researchers inspect the code and help fix vulnerabilities. AI can help defenders too.
Neither side gets an automatic win.
And keeping code private is not a digital invisibility cloak. Attackers can probe software without having its source.
The questions that matter are practical:
- Who can access the system?
- How is remote access secured?
- What has been installed?
- Who keeps it updated?
Home Assistant's own security guidance recommends strong passwords, multi-factor authentication, updates and secure remote access. Those are ongoing responsibilities, not boxes to tick once on installation day.
Our approach is to keep our supported offering clearly defined, including the components and combinations we need to understand and maintain.
That does not make us immune to vulnerabilities. It makes the scope of our responsibility clearer.
Your family should not discover, after installation, that someone has quietly appointed you head of cybersecurity.
What If You Want Someone Else to Maintain Your System Later?
That is a sensible question, and you deserve clear answers about dependence on us.
Home Assistant's open-source foundation and wider pool of knowledgeable users and professionals can give homeowners more options for future maintenance and handover. That is a real advantage.
Choosing our own platform means we owe customers clear answers about dependence on us, too:
- What runs locally?
- What requires continued support?
- What happens if a hub fails?
Those are different questions. "It works locally" cannot answer all three. And using standard device protocols does not mean every feature transfers unchanged to another platform.
Trust comes from explaining those distinctions, not waving them away.
Is Home Assistant or Home-A-Genius Right for You?
It depends on how much of the system you want to manage yourself. Home Assistant is not the wrong choice for every homeowner.
| Home Assistant | Home-A-Genius | |
|---|---|---|
| Foundation | Open source, with extensive integrations | Our own platform and product direction |
| Devices | Long compatibility list | Defined range of devices and supported combinations |
| Maintenance | Tools for updates, backups and recovery, but someone still has to do the work | We accept the development and maintenance work that comes with our platform |
| Future handover | Wider pool of knowledgeable users and professionals | Clear answers about what depends on us |
| Best for | Homeowners who value extensive customisation and direct technical control | Families who want a home that asks less of them |
If you value extensive customisation and direct technical control, Home Assistant may be exactly what you want.
But technical possibility is not our deciding factor.
We have chosen to invest in our own product direction, supported combinations and family experience, accepting the development and maintenance work that comes with that choice.
We are building for the person carrying the sleeping toddler.
For the partner who does not know what an integration is, and should not need to.
For the family who wants a home that asks less of them.
That is why we do not build Home-A-Genius on Home Assistant, even though we could.
You have enough to manage. Your home should not be another thing on the list.
References
- Home Assistant: Securing your Home Assistant - guidance on authentication, system updates and secure remote access.
- Home Assistant: Updating Home Assistant, apps, and devices - documentation on managing updates, backups and changes that require manual intervention.