# Homey Self-Hosted Server on Windows | Megathread

**URL:** <https://community.homey.app/t/homey-self-hosted-server-on-windows-megathread/146434>\
**Category:** Homey Self-Hosted Server\
**Tags:** homey-self-hosted\
**Created:** [December 5, 2025, 2:10pm UTC](https://community.homey.app/t/homey-self-hosted-server-on-windows-megathread/146434 "2025-12-05T14:10:55Z")\
**Posts on this page:** 20\
**Page:** 2

<div class="post-metadata">

**Author:** ![Stijn\_Lentfert](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/stijn_lentfert/32/121247_2.png) [@Stijn\_Lentfert](https://community.homey.app/u/Stijn_Lentfert)\
**Post date:** [December 28, 2025, 8:47pm UTC](https://community.homey.app/t/homey-self-hosted-server-on-windows-megathread/146434/24 "2025-12-28T20:47:01Z")

</div>

nat

---

<div class="post-metadata">

**Author:** ![Dijker](https://avatars.discourse-cdn.com/v4/letter/d/b9bd4f/32.png) [@Dijker](https://community.homey.app/u/Dijker)\
**Post date:** [December 28, 2025, 8:48pm UTC](https://community.homey.app/t/homey-self-hosted-server-on-windows-megathread/146434/25 "2025-12-28T20:48:00Z")

</div>

Please Change it to Bridged and restart the guest OS.

---

<div class="post-metadata">

**Author:** ![Stijn\_Lentfert](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/stijn_lentfert/32/121247_2.png) [@Stijn\_Lentfert](https://community.homey.app/u/Stijn_Lentfert)\
**Post date:** [December 28, 2025, 8:48pm UTC](https://community.homey.app/t/homey-self-hosted-server-on-windows-megathread/146434/26 "2025-12-28T20:48:16Z")

</div>

doet het ook niet

---

<div class="post-metadata">

**Author:** ![Stijn\_Lentfert](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/stijn_lentfert/32/121247_2.png) [@Stijn\_Lentfert](https://community.homey.app/u/Stijn_Lentfert)\
**Post date:** [December 28, 2025, 8:49pm UTC](https://community.homey.app/t/homey-self-hosted-server-on-windows-megathread/146434/27 "2025-12-28T20:49:35Z")

</div>

no operating system found now 😦

---

<div class="post-metadata">

**Author:** ![Dijker](https://avatars.discourse-cdn.com/v4/letter/d/b9bd4f/32.png) [@Dijker](https://community.homey.app/u/Dijker)\
**Post date:** [December 28, 2025, 8:50pm UTC](https://community.homey.app/t/homey-self-hosted-server-on-windows-megathread/146434/28 "2025-12-28T20:50:45Z")

</div>

> This is the English Category,

there is already a topic for [Homey Self-Hosted Server on Windows | Megathread](https://community.homey.app/t/homey-self-hosted-server-on-windows-megathread/146434)

> Therefor Moved.

---

<div class="post-metadata">

**Author:** ![Michael\_Warrer](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/michael_warrer/32/81907_2.png) [@Michael\_Warrer](https://community.homey.app/u/Michael_Warrer)\
**Post date:** [January 3, 2026, 6:29pm UTC](https://community.homey.app/t/homey-self-hosted-server-on-windows-megathread/146434/30 "2026-01-03T18:29:33Z")

</div>

Running a self-hosted server on VMware (with bridged) on Windows. The Windows firewall is disabled, but the MQTT client cannot connect and the Homey link times out. any good suggestions?

---

<div class="post-metadata">

**Author:** ![smarthomesven](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/smarthomesven/32/79712_2.png) [@smarthomesven](https://community.homey.app/u/smarthomesven)\
**Post date:** [January 3, 2026, 11:34pm UTC](https://community.homey.app/t/homey-self-hosted-server-on-windows-megathread/146434/31 "2026-01-03T23:34:44Z")

</div>

HomeyLink shouldn’t time out, as it should use the cloud connection if it can’t use the local connection. Can you access your Homey SHS remotely (anywhere outside your LAN)?

---

<div class="post-metadata">

**Author:** ![Michael\_Warrer](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/michael_warrer/32/81907_2.png) [@Michael\_Warrer](https://community.homey.app/u/Michael_Warrer)\
**Post date:** [January 4, 2026, 7:52am UTC](https://community.homey.app/t/homey-self-hosted-server-on-windows-megathread/146434/32 "2026-01-04T07:52:36Z")

</div>

Yes. But i will hope homeylink use lan-lan, so speed is best. HSH is 12.10.1 but i have not “beta enables” and on HSH update page is say 12.10, but HP2023 is in beta 12.10.1 ?

---

<div class="post-metadata">

**Author:** ![Michael\_Warrer](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/michael_warrer/32/81907_2.png) [@Michael\_Warrer](https://community.homey.app/u/Michael_Warrer)\
**Post date:** [January 4, 2026, 4:06pm UTC](https://community.homey.app/t/homey-self-hosted-server-on-windows-megathread/146434/33 "2026-01-04T16:06:21Z")

</div>

Homeylink From SHS to HP2023. From HP2023 to SHS it works. From SHS to SHS it works. I have 200 devices in HP2023, maybe that is the case ?

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/f/0/f0614d28e174eb766488b940acb02bf4adb5ffab.png)

---

<div class="post-metadata">

**Author:** ![smarthomesven](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/smarthomesven/32/79712_2.png) [@smarthomesven](https://community.homey.app/u/smarthomesven)\
**Post date:** [January 4, 2026, 6:44pm UTC](https://community.homey.app/t/homey-self-hosted-server-on-windows-megathread/146434/34 "2026-01-04T18:44:31Z")

</div>

Yes that means the page has crashed (likely out of RAM, maybe you can close a few apps/tabs on your PC to reduce the RAM usage and try again)

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [January 5, 2026, 5:47am UTC](https://community.homey.app/t/homey-self-hosted-server-on-windows-megathread/146434/35 "2026-01-05T05:47:26Z")

</div>

Same screen here, it’s basically caused by a script running for too long.  
So I “fought” for a while with adding my Pro 2026 to SHS and Pro19 with HomeyLink, and almost reported to support.  
The Pro 2026 here has lots of devices, around 250.  
(Adding the Pro 2019 went fine (having a handful devices)).

But somehow I got the idea unavailable devices might slow down the discovering process, causing it to freeze or time-out. I had 39 of those 🫣 😆

- You’d use the mobile app instead
- Remove or fix any unavailable devices (with the red triangle) on the Pro 2023
- Try again

That was the fix for me.

---

<div class="post-metadata">

**Author:** ![Giovanni4312](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/giovanni4312/32/155115_2.png) [@Giovanni4312](https://community.homey.app/u/Giovanni4312)\
**Post date:** [January 5, 2026, 5:51pm UTC](https://community.homey.app/t/homey-self-hosted-server-on-windows-megathread/146434/36 "2026-01-05T17:51:50Z")

</div>

I can’t start the server, these are my settings on virtualbox..can anyone help me?

 ![Immagine 2026-01-05 185107](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/c/5/c510add6de738fd66a854373c2bf49cbc050a18c.jpeg)

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [January 6, 2026, 1:33am UTC](https://community.homey.app/t/homey-self-hosted-server-on-windows-megathread/146434/37 "2026-01-06T01:33:44Z")

</div>

Instead of NAT:

> [@Dijker](#):
>
> Please Change it to Bridged and restart the guest OS.

And please eleborate on “can’t start”? @Giovanni4312  
When the VM can’t start, an error message appears.  
When you can’t find it in the Homey app, it’s probably the network setting

---

<div class="post-metadata">

**Author:** ![Giovanni4312](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/giovanni4312/32/155115_2.png) [@Giovanni4312](https://community.homey.app/u/Giovanni4312)\
**Post date:** [January 6, 2026, 10:53am UTC](https://community.homey.app/t/homey-self-hosted-server-on-windows-megathread/146434/38 "2026-01-06T10:53:53Z")

</div>

![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/6/e/6e586818629345f131f54a83f12c5356069bcec5.png)I don’t think an IP address is assigned…

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [January 7, 2026, 1:05am UTC](https://community.homey.app/t/homey-self-hosted-server-on-windows-megathread/146434/39 "2026-01-07T01:05:14Z")

</div>

Did you change network NAT to Bridged mode?

If you think it’s the 0.0.0.0 lines, that’s normal:

 ![Screenshot_20260107_015848_Firefox](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/1/e/1e326f056a5df66f29d9db16f886a58f3c78072b.jpeg)  
When I open the app, and add a new SHS, it finds the SHS

Weird, I also got this notification:

 ![Screenshot_20260107_015912_Firefox](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/a/2/a20114f3d9a6d8b35b6295fbec33e3eb7a0a8344.jpeg)

But, after that it started to download the homey-shs container (it"s around 230MB).

On your VM log it doesn’t show any sign of that.

This could be because the network mode is still in NAT

---

<div class="post-metadata">

**Author:** ![Giovanni4312](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/giovanni4312/32/155115_2.png) [@Giovanni4312](https://community.homey.app/u/Giovanni4312)\
**Post date:** [January 7, 2026, 10:39am UTC](https://community.homey.app/t/homey-self-hosted-server-on-windows-megathread/146434/40 "2026-01-07T10:39:19Z")

</div>

![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/d/c/dc1964dcd559f87e754c994e945b7c4f7f50988a.png)

If I open the app, it doesn’t find anything (my phone and PC are on the same wifi network)

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/e/8/e8beb158776eaaf323785fe9e7182c7578c342d6.jpeg)

---

<div class="post-metadata">

**Author:** ![Michael\_Warrer](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/michael_warrer/32/81907_2.png) [@Michael\_Warrer](https://community.homey.app/u/Michael_Warrer)\
**Post date:** [January 7, 2026, 11:35am UTC](https://community.homey.app/t/homey-self-hosted-server-on-windows-megathread/146434/41 "2026-01-07T11:35:57Z")

</div>

How can the disk be expanded on SHS when it’s running on VMware? VMware has a 16GB disk, but only 8GB is shown in SHS. I’ve tried various Linux commands directly in the SHS console, but without success.

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [January 7, 2026, 11:27pm UTC](https://community.homey.app/t/homey-self-hosted-server-on-windows-megathread/146434/42 "2026-01-07T23:27:17Z")

</div>

Is the host running Virtual box on the same subnet as your phone running the Homey app?  
When not, allow Homey & Virtual box host IP addresses to reach eachother.

Do you use any network tools, like PiHole, AdGuard?  
When true, temporary disable those.

Is a firewall active on the host?  
When true, did you open required ports?

Is the virtual box’s network setting, “Promiscuous mode”, set to Deny, or Allow VMs?  
When true, try “Allow all”.

---

<div class="post-metadata">

**Author:** ![Giovanni4312](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/giovanni4312/32/155115_2.png) [@Giovanni4312](https://community.homey.app/u/Giovanni4312)\
**Post date:** [January 8, 2026, 2:43pm UTC](https://community.homey.app/t/homey-self-hosted-server-on-windows-megathread/146434/43 "2026-01-08T14:43:04Z")

</div>

Regarding the firewall, I’ve also tried disabling it completely, but the issue persists.  
At startup I also get a graphics card–related error, and I’m not sure if that could somehow be related to this problem.

What makes me think it’s more of an IP/network issue is that previously the Homey app did show the server once: on the HTTPServer line it displayed a 192.168.x.x address. Now, instead, all those values are 0.0.0.0.  
Because of this, it seems to me that the virtual machine is not being assigned an IP address at all, rather than it being an issue of a different nature.

![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/c/e/ce2d5e8efee3f1e1a5fa67e741fedb6ab773af9b.png)

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/2/0/20f896b284321d4d776f2d863bd584ba7a15c7c6.jpeg)

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [January 8, 2026, 10:09pm UTC](https://community.homey.app/t/homey-self-hosted-server-on-windows-megathread/146434/44 "2026-01-08T22:09:52Z")

</div>

The vmwgfx is a virtual box issue,  
probably the vm quits because of that!  
At “Display” tab, you should choose an other Graphics Controller like vmsvga.

[Previous page](https://community.homey.app/t/homey-self-hosted-server-on-windows-megathread/146434.md?page=1)

[Next page](https://community.homey.app/t/homey-self-hosted-server-on-windows-megathread/146434.md?page=3)
