nat
Please Change it to Bridged and restart the guest OS.
doet het ook niet
no operating system found now 
This is the English Category,
there is already a topic for Homey Self-Hosted Server on Windows | Megathread
Therefor Moved.
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?
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)?
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 ?
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 ?
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)
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.
Instead of NAT:
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
Did you change network NAT to Bridged mode?
If you think itâs the 0.0.0.0 lines, thatâs normal:
When I open the app, and add a new SHS, it finds the SHS
Weird, I also got this notification:
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
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.
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â.
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.
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.
