
Troubleshooting The few things that go wrong, and what to do. I can't open iconet.local Try the IP address instead: your router's device list shows it as iconet (or the hostname you set). Check the Ethernet link light; on PoE, check the port delivers power. Give it a minute after power‑up. Some networks block mDNS between wireless and wired segments: use the IP, or set a static one in Settings › Network. I changed to a static IP and lost it If the address or gateway you typed was wrong, the gateway falls back to DHCP on its own so you keep access. Look it up in the router again. A device says Offline KNX: the status pill must read Bus connected. Check the bus voltage and the terminal wiring; open Monitor to see whether telegrams arrive. DALI: Bus has no power means the external DALI power supply is missing or off. Never add a second one. Zigbee: battery devices report rarely; the tile shows the age of the last value. Mains devices that stay offline: remove and pair again close to the gateway. Thread / Matter: factory‑reset the device and pair again; keep it near the gateway the first time. Cameras: wrong address or credentials. Edit the camera; it comes online by itself once reachable. Third‑party controllers: wireless controllers answer slower than wired ones; a controller that dropped reappears when it reconnects. Apple Home / Google / Alexa show "No response" Wait a few minutes: after a bridge reload the apps rediscover it. If it persists, remove the bridge from the app, Reset & re‑pair all bridges in Integrations › Matter › Bridge, and pair again. The weather card is empty Set the address in Settings › Device (or the wizard). The forecast needs internet and refreshes hourly. An AI client can't connect Tokens work on the local network only: the client must be on the same network as the gateway. Check the token isn't revoked or expired, and that it has the permissions the request needs. Settings › Access › Activity shows every attempt and why it was refused. The `npx` connector needs Node.js on that computer. Something else Settings › System › Identify device blinks the front LEDs so you find the right unit in a cabinet. Reboot gateway takes about a minute. Export configuration before any drastic step; Factory reset is the last resort. Write to support@iconet.io with the serial number and versions from Settings › Device. Previous Updates Next Frequently asked questions

Troubleshooting

The few things that go wrong, and what to do.

I can't open iconet.local

Try the IP address instead: your router's device list shows it as iconet (or the hostname you set).
Check the Ethernet link light; on PoE, check the port delivers power. Give it a minute after power‑up.
Some networks block mDNS between wireless and wired segments: use the IP, or set a static one in Settings › Network.

I changed to a static IP and lost it

If the address or gateway you typed was wrong, the gateway falls back to DHCP on its own so you keep access. Look it up in the router again.

A device says Offline

KNX: the status pill must read Bus connected. Check the bus voltage and the terminal wiring; open Monitor to see whether telegrams arrive.
DALI: Bus has no power means the external DALI power supply is missing or off. Never add a second one.
Zigbee: battery devices report rarely; the tile shows the age of the last value. Mains devices that stay offline: remove and pair again close to the gateway.
Thread / Matter: factory‑reset the device and pair again; keep it near the gateway the first time.
Cameras: wrong address or credentials. Edit the camera; it comes online by itself once reachable.
Third‑party controllers: wireless controllers answer slower than wired ones; a controller that dropped reappears when it reconnects.

Apple Home / Google / Alexa show "No response"

Wait a few minutes: after a bridge reload the apps rediscover it. If it persists, remove the bridge from the app, Reset & re‑pair all bridges in Integrations › Matter › Bridge, and pair again.

The weather card is empty

Set the address in Settings › Device (or the wizard). The forecast needs internet and refreshes hourly.

An AI client can't connect

Tokens work on the local network only: the client must be on the same network as the gateway.
Check the token isn't revoked or expired, and that it has the permissions the request needs. Settings › Access › Activity shows every attempt and why it was refused.
The npx connector needs Node.js on that computer.

Something else

Settings › System › Identify device blinks the front LEDs so you find the right unit in a cabinet. Reboot gateway takes about a minute. Export configuration before any drastic step; Factory reset is the last resort.

Write to support@iconet.io with the serial number and versions from Settings › Device.

Updates

Frequently asked questions