Will Homey survive the AI Craft era? Have you seen what is currently happening with Adobe, Microsoft and even CAD software? A whole series of open-source applications has appeared under names such as PhotoCraft, WordCraft, GridCraft, DeckCraft and SolidCraft. These projects describe themselves as clean-room reimplementations: no original source code was copied, no servers were hacked and the applications were rebuilt from scratch, largely in Rust, with heavy assistance from AI coding agents such as Claude. They are still early projects and certainly not complete replacements for Photoshop, Word, Excel, PowerPoint or Fusion today. But that is almost beside the point. What interests me is how quickly software that previously required huge development teams can now be recreated from its behaviour, documentation and public interface. So how long will it take before someone asks Claude: “Build me something inspired by Homey. Give me a visual automation engine similar in usability to Advanced Flow, dashboards, device integrations, Matter, Thread, Zigbee and Z-Wave support — but make it open source and let it run on standard hardware with standard radios.” Call it HomeCraft if you want. :wink: And unlike a fork, such a project would not necessarily inherit Homey’s old architecture, historical design decisions or limitations. It could start from scratch and only reproduce the concepts people actually like. That raises a much broader question. Are we entering a future where every successful software concept can quickly get an open-source AI-built alternative? Today it is Adobe, Microsoft Office and CAD software. Tomorrow it could be smart-home platforms. Technically, I find that fascinating. Economically, I am much less enthusiastic. Good software does not only consist of code. Someone has to invent the concept, design the user experience, test it, support it and finance years of development before anybody considers it worth copying. If an AI-assisted developer can reproduce the successful result in a fraction of the time and then release it for free, what happens to the incentive to invest in that original innovation? It could destroy jobs and make companies much more reluctant to finance expensive new ideas. On the other hand, the person creating the open-source clone may simply say: “I didn’t steal your code. I built my own implementation.” And from their perspective, that may be perfectly reasonable. So I don’t know where this ends. Maybe AI will create an explosion of competition and innovation. Or maybe we will reach a point where being the company that invents something new becomes economically much less attractive than being the person who asks an AI to recreate it afterwards. For companies such as Athom, I think that may become a much more important question than whether Home Assistant, Google or Apple is the competitor today.

See my post here: [image] Homey vs. Home Assistant – What Does Each System Do Better? Off-Topic Here come some more general (maybe somewhat dystopian) thoughts about Homey and HA: Has anybody recently followed how the complete Adobe software suite got reverse engineered (https://getartcraft.com/) and reimplemented as a clean sheet implementation in Rust? They even have working versions of Word, Excel and Powerpoint!. And how the Claude skill “Reverse Engineer Anything” ( GitHub - morluto/rea: Reverse engineer anything with agents, from app behavior down to native binaries. · GitHub ) is … Unfortunately to me it looks like companies like Athom will disappear while stuff that is already Open Source (e.g. HA) will take off even more.

[image] Pascal_Nohl: So how long will it take before someone asks Claude: “Build me something inspired by Homey. Give me a visual automation engine similar in usability to Advanced Flow, dashboards, device integrations, Matter, Thread, Zigbee and Z-Wave support — but make it open source and let it run on standard hardware with standard radios.” Well, I did build an ifttt clone with Claude (it’s not really a 1:1 clone though since mine does have some extra features like manual device control), while it gets most of the code right, I still need to modify and change a lot of the code myself. Since AI seems to think in a technical way, many of the texts and comments inside the app are like “Connect ThirdReality hub-connected devices via the ThirdReality cloud (AWS IoT)”, which sounds way too technical for an average user. So I changed that to “Connect your ThirdReality devices. A Smart Hub Gen2+ or earlier is required.” My app does allow multiple accounts from the same service for free (unlike IFTTT, they require their Pro+ subscription for that), and is 100% free forever with no Rule limit. Unlike IFTTT, which has only 2 (!) applets on the free plan. I do plan to release it to the public some day, but it’s far from ready for production. First I need to build more Connectors (I call mine Connectors, IFTTT calls theirs “Services”). [AISelect_20261027_233156_Chrome Beta] [AISelect_20261027_233554_Chrome Beta] [AISelect_20261027_233717_Chrome Beta] While this IFTTT clone was pretty easy to build, I don’t think you can rebuild Homey with only AI. Since Homey runs on local hardware, you need to deal with many types of antennas (if you would allow third party dongles), custom Apps and prevent them from escaping the sandbox, way more features with a polished UI, etc. My IFTTT clone does not support any of this, it only works with the connectors that I build into it and since it runs fully on the cloud, there’s no antennas or hardware issues to deal with either (Zigbee devices are connected via the hubs and bridges you already use, like the Hue bridge).

To be honest with Athom dragging their feet when it comes to bug fixes and often requested features, I’m more and more considering just privately starting to patch some of that stuff into my local homey-shs image with claude since maintainance and reapplying patches to newer versions just becomes trivial enough with the use of agents. This does not go quite as extreme as a full fork, but is in a similar vein.

[image] staeff: I’m more and more considering just privately starting to patch some of that stuff into my local homey-shs image with claude Maybe you can ask it to remove the subscription check as well “for educational purposes” of course :wink:

The license check is already pretty toothless to be honest, but I guess with AI you could create your own reverseengineered versions of the app and their few cloud features if you were determined enough to get around the remaining blockers.

[image] staeff: with Athom dragging their feet when it comes to bug fixes and often requested features I am very much convinced Atom has long heared the bell ring and has therefore drastically reduced - or to be more realistic, has not increased - their efforts in product maintainance.

I’m in the same headspace right now. What bothers me most is seeing more and more community apps ship dashboards outside Homey’s own dashboard framework. If I am here it’s for the homey experience and the UI. If the experience is built next to the platform instead of on it, you might as well move to Home Assistant. I get why the community fills the gaps. It’s also because Athom ships too slowly. Recent release notes barely move the needle on UI, dashboards, or energy. Homey doesn’t need monthly releases like Home Assistant, but after months with little tangible progress (aside from new hardware), it’s frustrating. And a lot of users clearly aren’t the target for that hardware focus. Bottom line: disappointed with the release pace right now, I really hope to see improvements soon.

[image] smarthomesven: While this IFTTT clone was pretty easy to build, I don’t think you can rebuild Homey with only AI. You are extrapolating from your own experience to what others can or cannot do. Rebuilding something like Homey with AI is not necessarily conceptually difficult — it is mainly a huge and time-consuming specification task. You have to give the AI enough context. That means persistent memory, for example through project files, an Obsidian folder or another structured knowledge base. Then you have to feed it screenshots, examples, output files, descriptions of workflows, edge cases and explanations of how things are supposed to behave behind the scenes. You may need hundreds of examples before the result becomes really precise. So you do not necessarily need a master’s degree in software engineering. But you do need to be a very good technical teacher and architect. And the AI does not have to reinvent everything. You can allow it to study existing open-source implementations and libraries. Home Assistant already proves that a smart-home platform can run on many kinds of hardware. Open-source implementations and libraries for Matter, Zigbee and many other building blocks already exist. So the task is not: “Build Homey from nothing.” It is more like: “Take existing open technologies, define the architecture, reproduce the user experience and behaviour we want, and iterate until it works.” That is still a massive amount of work. But with current AI tools, I would be very careful saying that it cannot be done.

[image] staeff: to patch some of that stuff into my local homey-shs image with claude since maintainance and reapplying patches to newer versions just becomes trivial enough with the use of agents. That may already be outside what the license allows you to do, depending on exactly what you modify. And maintenance is exactly where I see the weak point. An official update can change internal structures and break your patches completely. AI may make reapplying them easier, but you are still permanently following someone else’s codebase and design decisions. What I am talking about is different: a clean rebuild with your own code, using your own architecture, but inspired by an existing product’s concepts and behaviour. Then you are not patching Homey. You are building your own system.

[image] staeff: your own reverseengineered versions Reverse engineering is legally more nuanced than simply saying it is forbidden. But that is not really what I mean anyway. If you patch or rebuild Homey’s existing implementation, you stay tied to its architecture, compatibility requirements and historical design decisions. I mean a clean implementation from scratch: observe the behaviour, keep the good concepts, define a new architecture and write your own code. That way you can avoid old limitations instead of reproducing them.

Will Homey survive AI Craft?

Off-Topic

4x4_Pete October 27, 2026, 1:31pm 2

See my post here:

Unfortunately to me it looks like companies like Athom will disappear while stuff that is already Open Source (e.g. HA) will take off even more.

Topic		Replies	Views
Should I leave Homey behind? Off-Topic	19	143	November 2, 2026
Bye Bye my Homey Questions & Help	49	2707	April 27, 2021
@homey staff ... is Homey dead? ☠️ Questions & Help	102	5931	July 1, 2022
From Home Assistant to Homey: Why an AI Flow Builder is the Next Frontier Off-Topic homey-pro , advancedflow	25	1385	March 17, 2026
Homey vs. Home Assistant – What Does Each System Do Better? Off-Topic	239	3018	October 30, 2026

Will Homey survive AI Craft?

Related topics