As promised, I reviewed and installed Homey's published install script and documentation to see how Homey Self-Hosted Server actually works with Proxmox. The short version: it looks better from the outside than it actually is. I had to make serious edits to the install script because of these assumptions Homey made about a Proxmox environment.
What was promised
They announced Homey Self-Hosted Server. The idea is to run the Homey Pro operating system on your own hardware - Proxmox, Raspberry Pi, Synology, Docker, TrueNAS, and others. $149 lifetime license or $4.99/month. Sounded compelling to me.
The install script
I pulled apart their install script and it raises some concerns for anyone running a proper homelab.
Network configuration is essentially nonexistent. It drops everything on vmbr0 with DHCP and no VLAN tagging option. If you're running IoT isolation (and you should be), this doesn't fit. No static IP, no DNS override, no VLAN tag parameter.
The template is hardcoded to a specific Debian 13.1 release with no dynamic lookup. Right now it looks like they are only supporting 13.1 specifically.
The Docker container runs with --privileged and --network host inside the LXC. That bypasses all network namespace isolation. The whole point of putting it in an LXC is containment - they defeat that immediately.
Every time the LXC boots, it pulls whatever image is current from Athom's registry. No version pinning, no digest verification. They can push anything to that container and it executes on your hardware automatically on next reboot.
I modified the script to properly set the container ID and place it on my IoT VLAN — that part works — but the --privileged and --network host flags inside the container remain Homey's defaults.
License - The Elephant in the Room
This is the real issue. The "lifetime license" is not a license key you hold locally. Their own documentation states initial activation requires internet connectivity and ties to your account. The pull-on-boot model isn't just for updates - it's almost certainly how ongoing license validation works. Let the subscription lapse or lose connectivity to their registry and you likely get a non-functional image on next restart.
This isn't self-hosted in any meaningful sense. It's a cloud-dependent subscription product that happens to run a container on your hardware.
What motives does LG have?
Here's the part that doesn't get enough attention. Homey's parent is / was Athom and it was acquired by LG Electronics in 2024.
We've seen this movie before. Samsung acquired SmartThings in 2014. At acquisition it was an independent, community-focused platform with a passionate user base. Samsung's strategic interest wasn't your home automation reliability - it was making Samsung appliances and TVs stickier in the ecosystem. The roadmap gradually shifted to reflect that. Hub hardware was sunset. The platform moved progressively cloud-dependent. A significant portion of this community exists because of how that story ended.
LG already has their own smart home platform - ThinQ. They acquired Athom because ThinQ never gained real traction with the broader smart home community. So now LG has two platforms and an integration story to figure out. Where Homey SHS fits in that consolidation is an open question - and it will be answered in a boardroom in Seoul, not by the homelabber or home automation communities.
The "lifetime license" question gets darker in this context. Athom as an independent company had reputational skin in the game. As an LG subsidiary, the decision to honor $149 lifetime commitments gets made by people whose primary concern is LG's appliance ecosystem roadmap. Wink, SmartThings, Iris - they all worked great right up until a corporate decision made them not work at all.
My Final Thoughts
Homey software looks like polished software with a good app ecosystem. For someone coming from a plug-and-play hub background the UI is genuinely impressive. But it's not the offline appliance model this I would be looking for. As I may make the same assumption for why we are on Hubitat.
The plus to Hubitat's model - firmware update when you want, hub you own and it works indefinitely on your LAN with zero upstream dependency, radios on the device - is a fundamentally different architecture.