Hi everyone,
I’m reaching out for help with an issue I’ve run into after migrating my Home Assistant setup to a new device.
Background:
I’ve been running Home Assistant and Homebridge on a Raspberry Pi 5B with great success, 38 devices, lots of automation scripts, and everything has been super reliable. However, the RPI is starting to show its limits, especially with things like Unifi Protect. So, I decided to upgrade.
New Setup:
- Minisforum NUC running Windows Pro
- Home Assistant OS in Hyper-V with a static IP and external switch (bridge) configured
- Firewall disabled for testing
- Zigbee coordinator connected via POE and working (e.g., controls my sprinkler system)
- Home Assistant mobile app works fine
- Old RPI setup still running in parallel for now
The Issue:
When I try to connect the new Home Assistant instance to HomeKit via the built-in HomeKit Bridge:
- Pairing works just fine.
- HomeKit detects the test lights and 6 Zigbee water valves I’ve added so far.
- Devices are added without errors.
BUT:
After setup, all devices show “No Response” in the Home app. Nothing is controllable from HomeKit, although everything still works perfectly inside HA.
I checked with a Bonjour browser and the _hap._tcp. service shows up with the correct IP address.
Also when pinging from my iPhone to the ip and port that i found in the Bonjour browser it shows as open.
What I’ve Tried:
- Confirmed network bridge and IP settings in Hyper-V
- Disabled Windows Firewall entirely
- Restarted both HA and the iOS Home app
- Made sure only one HomeKit bridge is exposed (from the new HA instance)
- Moving to VMware workstation (same problem)
Any advice would be appreciated! Has anyone seen this kind of issue when running HA in Hyper-V?
Thanks in advance!