In this guide, you will learn how to make the Velux KIG 300 gateway discoverable via the HomeKit Controller integration in Home Assistant when the gateway and Home Assistant reside in separate network segments. This setup is intended for advanced users operating a dedicated IoT network.
Prerequisites
- A Linux-based gateway (such as a Raspberry Pi) acting as a bridge between the regular LAN and the IoT VLAN.
- Appropriate permissions to modify the configuration on this gateway system.
- Avahi is installed on the gateway system.
- A working Home Assistant instance on the LAN and a configured Velux KIG 300 on the IoT VLAN (2.4 GHz Wi-Fi).
Step 1: Back Up the Configuration File
Before modifying network services, create a backup copy of your existing Avahi configuration so you can revert any misconfigurations at any time.
Step 2: Enable the mDNS Reflector in Avahi
If the KIG 300 resides in a separate IoT VLAN with its own IP range, the HomeKit Controller integration in Home Assistant on the regular LAN will not discover it automatically. To make the gateway discoverable across networks, configure Avahi as an mDNS reflector. Open the Avahi configuration file and adjust the [reflector] section as follows:
[reflector]
enable-reflector=yes
reflect-ipv=noStep 3: Restart the Avahi Service
To apply the modified settings and have Avahi operate as a reflector, restart the service.
sudo systemctl restart avahi-daemonStep 4: Restart Home Assistant and Pair the Device
Restart the Home Assistant host or service via the web interface so the device can be detected. Afterwards, the Velux KIG 300 will appear in Home Assistant under notifications or as a new HomeKit device. To pair it, enter the HomeKit pairing code located on the back of the KIG 300 gateway.
Verification
First, verify on the gateway that the Avahi service is running without errors:
sudo systemctl status avahi-daemonThe output should display the status active (running). The KIG 300 will now be listed in the Home Assistant web interface, and paired roof windows or roller shutters will show up as entities.
Troubleshooting
- Device not discovered despite reflector: If the Velux app on your smartphone prompts you to complete the HomeKit setup, do not finish this process on your phone; restart Home Assistant instead. If the gateway was previously paired with HomeKit, you may need to remove it there or reset the KIG 300 using its configuration button (press and hold until the LED turns red).
- KIG 300 loses Wi-Fi connection: The gateway only supports 2.4 GHz Wi-Fi. Ensure that the 2.4 GHz band is active and accessible during setup.
Reverting Changes
To disable the reflector feature, restore the backed-up configuration file and restart the Avahi service.
Conclusion
Using Avahi’s reflector functionality allows you to bridge VLAN boundaries for the Velux KIG 300 HomeKit integration without sacrificing network isolation. Once paired, your Velux devices are available in Home Assistant for dashboards and automations.
Sources: Forum: Simon42 – Forum, community.home-assistant.io, community.simon42.com