Symptoms:
- The controller is visible in the app, but its settings cannot be accessed via its IP address.
- The device’s configuration page does not open in the app.
- A search for devices on the local network fails to find a driver.
- The controller responds via the cloud, but is not accessible locally.
Possible causes:
- Client isolation (AP Isolation / Client Isolation) is enabled on the router or access point.
- The computer or telephone is on a different subnet or VLAN from the controller.
- Firewall rules block communication between devices on a local network.
- The guest Wi-Fi network (Guest Network) prevents communication between clients.
- Incorrect routing configuration between VLANs.
Suggested solutions:
- Check that the control unit and the controller are on the same IP network.
- Check whether the AP Isolation / Client Isolation function is enabled on the router or access point.
- Please ensure that you are not using the guest Wi-Fi network.
- Check the VLAN configuration and the routing rules between them.
- Check the firewall settings on your router and your end device.
- Try accessing the controller directly using its IP address.
- In the case of complex networks, consult the network administrator regarding the configuration.
Note for the installer:
For local communication to function correctly, BleBox controllers require direct communication between devices on the network. Enabling client isolation or placing devices in separate VLANs without the appropriate routing rules will prevent access to the devices’ settings.