Hi @Doekse and the Homey team 
Thanks for bringing up @willemvanoorschot5507’s question in the podcast. I think the question is really about the desire to combine SHS (on a VM/Docker with more resources) with dedicated radio hardware as a coordinator — while still keeping Homey’s user experience.
I get the argument that Homey Bridge is cheaper than using a Homey Pro as a bridge under SHS. But as @DaneedeKruyff already points out: it overlooks those who already own a Homey Pro and now want to build on top of it with SHS — and I’m probably not the only one in that situation. 
And that brings me to something a bit broader. Limited history on sensor data in Insights, instability when building a larger Thread setup (documented here), and hardware that doesn’t always live up to expectations in practice. These are limitations that users feel in their day-to-day — and that kind of feedback is worth listening to. 
It would be great if Homey could eventually open up to external radio hardware — not because the existing lineup is bad, but because it would give users the flexibility to build the setup that fits their specific needs. There are dedicated coordinators from the likes of SMLIGHT or Nabu Casa that are purpose-built for Zigbee and Thread. That requires more openness in the platform — but that’s exactly the kind of flexibility that would make it even stronger. 
For many, one all-in-one unit is the perfect solution — and that’s precisely Homey’s strength. But for those with larger setups or more specific needs, the ability to distribute tasks across multiple instances with dedicated resources could be really valuable. Not a requirement for everyone — just an option for those who want it.
The new Ask feature shows you’re thinking in that direction — and that’s great. Could something similar work for updates in general — both OS and apps? I currently check manually myself, because I don’t want to risk coming home to a setup that’s fallen apart after an update I didn’t know was coming. Notify the user, show release notes, let the user approve — ideally with a time-based reminder. More control, fewer surprises.
I say this as someone who genuinely likes Homey — from what I’ve tried, the user experience and UI are hard to beat. This isn’t a demand or a criticism, it’s an invitation. Maybe others in the community feel the same — and maybe that’s exactly the kind of conversation that could lead to exciting partnerships with hardware manufacturers down the line. 
Thanks for listening — keep up the great work! 
