Troubleshooting
Cannot access the Web Interface
Check the device IP address: The KNX Bridge's IP address is shown on a label on the device, or can be found in your router's DHCP client list. Try opening http://<ip-address>/app/ in your browser.
Check network connectivity: Make sure your computer is on the same local network as the KNX Bridge. If the bridge is connected via Ethernet, verify the cable and switch. If using WiFi, confirm the bridge joined the network successfully.
Try a reboot: If the device is unreachable, try rebooting the KNX Bridge and reconnecting. If the issue persists, boot into safe mode.
KNX devices not responding in the app
Verify group address configuration: Open the Group Monitor in the Web Interface and trigger the KNX device. Confirm that a telegram appears with the correct group address.
Check the KNX bus connection: In the Web Interface under KNX, the physical address should be shown (e.g. 15.15.255). If the status shows disconnected, check the KNX TP bus wiring at the bridge's terminal ④.
Check ETS programming: If you imported an ETS project, verify that the group addresses in the Accessory Manager match those in your ETS project. Re-import the .knxproj file if necessary.
Matter or HomeKit pairing not working
Check which ecosystem is active: The KNX Bridge can only run in one mode at a time: either Apple HomeKit or Matter. Check System Settings to confirm which is enabled, and disable the other before pairing.
Use the correct pairing code: The HomeKit pairing code is displayed in System Settings → Apple HomeKit. For Matter, use the QR code shown after enabling Matter.
Remove and re-pair: If a previous pairing is stuck, use Remove Pairing in System Settings, then start the pairing process again from your smart home app.
See the full Pairing Guide for platform-specific instructions.
ETS project loading fails (HTTP 503)
This error appears when the bridge is restarting or the ETS project is still being processed. Wait 30 seconds, refresh the page, and try the import again. If it persists, restart the device from System Settings → Restart and retry.
DALI bus shows as disconnected
Check that the DALI power supply is connected and powered on. If you are using the DALI power supply of the KNX Bridge, enable the DALI power supply option in System Settings → DALI.
Firmware update not available
If the firmware update button is greyed out or shows a locked message, your device may be locked to a specific firmware version by your installer. Contact info@atios.ch to request an unlock.
Apple Home is broken after a firmware update
Symptoms include devices showing as "Matter Accessory 1, 2, 3..." instead of their names, all rooms collapsed into one, most accessories missing, or the Matter QR code disappearing after the upgrade.
Wait the full 2 minutes after firmware install: rebooting before the confirmation window closes reverts the firmware to the previous version. The Reset Button is greyed out during the wait. See Firmware Updates.
Check your firmware version: open the Web Interface, go to System → About. If older than 2.4.50, update to the latest stable. The room-collapse and renamed-accessory bugs were fixed in 2.4.50.
Re-pair if symptoms persist: remove the bridge from Apple Home, then re-pair it. Names and rooms repopulate correctly on 2.4.50+.
RGBW LED strip doesn't show colour control in Apple Home
Most LED-strip drivers are not DT8-capable, even if the strip itself supports RGBW. Without DT8, colour control cannot be exposed to Matter or HomeKit.
Use a DT8-capable driver: confirmed working examples include the Sunricher SRP-2309. Non-DT8 multi-channel drivers (e.g. Eldoled 720d) cannot be mapped to RGBW colour control through the bridge.
RGBWAF is not yet supported: only RGBW (no amber, no white-amber fade). Support may be added in a later firmware.
HSV is the colour format: on the KNX side, the HSV datapoint maps to XY on DALI. There is no separate dimming address, brightness is part of HSV.
Configuration changes in the Web Interface don't show up in Apple Home or Google Home
The bridge needs an explicit save and reboot to push changes through to the Matter or HomeKit controller.
Save the configuration: in the Web Interface, click Save Configuration. Without this step, your changes stay in memory only and are lost on the next reboot.
Reboot the bridge: System Settings → Reboot. The reboot forces a re-sync with the Matter or HomeKit controller.
If problems persist after reboot: check that you didn't recently switch protocols (HomeKit ↔ Matter). Switching wipes the pairing, you must remove and re-pair the bridge in Apple Home or Google Home before changes will land.
Getting Further Help
If you still need help, contact info@atios.ch.