Network

Ethernet

10/100 Mbit, Auto-MDIX, up to 100 m on CAT5. This is the normal path: the controller and the devices it talks to sit on the same installation network.

USB

There is exactly one USB 2.0 type A port, and it is the reason the controller does not need variants. WiFi, a second isolated network, another field bus, or a firmware stick — all of it arrives through that port, and the drivers ship with the firmware, so there is nothing to enable in the web interface first.

The constraints are physical and worth knowing before you buy adapters:

So WiFi, a second LAN and a firmware stick are mutually exclusive. Which one the site needs is a decision, not a configuration.

The supported adapter families are listed on USB adapters.

Addressing

On the Ethernet port the controller takes its address from the network's DHCP server, normally the router. To find it:

• By name. It announces itself over multicast DNS as <model>-<serial>.local, with model and serial number as on the nameplate. Open https://<model>-<serial>.local from a device on the same network.
• By QR code. The QR code on the nameplate holds that local address.
• By IP address. The router's list of connected devices shows the address it handed out.

If the cabinet has no network yet, a USB WiFi adapter gives the controller a setup hotspot: an open network OptiBee-XXXX (last four characters of the serial number), with the interface at http://192.168.242.1. It comes up by itself whenever WiFi is not configured or not connected.

The steps from there — certificate warning, login — are on First connection.