Configuring Connect for Ethernet & Wi-Fi

Nimbus Connect is a low‑power IoT device that connects to the Nimbus cloud using one of the following paths:

• Cellular
• Ethernet
• Wi‑Fi

When multiple paths are configured, the device automatically selects the lowest‑latency path and maintains the remaining as failover(s). Failover paths generate minimal background traffic and are periodically health‑checked.

Network Behaviour Considerations

Due to the low‑traffic nature of the device—particularly on failover paths— network features such as the below should be applied to Connects switch port or wireless profile with careful consideration:

• MAC address lockdown
• Link‑state tracking
• Inactive port shutdown
• Per‑port network access control (NAC)
• Or similar technologies

The device may need to communicate across VLAN boundaries before reaching the Internet firewall (or fire panel when Ethernet is used for panel connectivity). Care should be taken to ensure internal network policies do not block this traffic.

Firewall & Security Requirements

The following must be permitted:

• Outbound TCP port 5684
• Destination: nimbus.lancontrolsystems.com
• Source: Nimbus Connect device

Ethernet Configuration

Ethernet can be configured using DHCP or a static IP.

If a static IP is required, provide:

• IP address
• Subnet mask
• Default gateway
• DNS server 1
• DNS server 2 (optional)

Wi‑Fi Configuration

Supported Wi‑Fi

• Standards: 802.11 a/b/g/n
• Bands: 2.4 GHz and 5 GHz
• Security: WPA or WPA2‑Personal (Pre‑Shared Key)

Unsupported Wi‑Fi

• WEP‑encrypted networks
• Open (no‑password) networks
• Hidden SSIDs
• Username/password (802.1X) authentication
• Captive portals or browser‑based authentication