Network requirements (for IT)
Give this page to your IT department or to your network technician. It shows what the network must allow for HAM devices to work.
How a device connects
Section titled “How a device connects”- The device connects to your WiFi and gets an address from DHCP.
- The device finds its server with DNS.
- The device opens a TLS connection to TCP port 9002 on the server.
- The device and the server do mutual authentication.
The device always opens the connection outwards. All requirements below are outbound connections.
Device requirements
Section titled “Device requirements”| Requirement | Details |
|---|---|
| 2.4 GHz WiFi | All WiFi devices work only on 2.4 GHz. A 5 GHz only network does not work. |
| WPA2-PSK | WPA3 only networks and enterprise (802.1X) networks are not supported. |
| 20 MHz channel width | Only for the older numeric families (8, 10, 14, 15, 20, 25, 29). The eNN families also support 40 MHz. |
| DHCP | The device gets its address only from DHCP. For a fixed address, use a DHCP reservation on the router. |
| Outbound TCP 9002 | The device data channel (TLS) to the device servers under *.hamsystems.eu. Firewalls often block this port. |
| Outbound TCP 443 | HTTPS for the API and for firmware updates. |
| DNS | The device must resolve *.hamsystems.eu names. Captive portals and DNS filtering stop the connection. |
| No client isolation | Guest networks and client isolation stop the setup. |
| No SSL inspection | A transparent TLS proxy breaks the mutual authentication. Exclude HAM devices from SSL inspection. |
| Signal at the install point | Check the signal where the device will stay, for example inside the panel or the fridge. The device antenna is smaller than the antenna of a phone. |
A separate network for IoT devices
Section titled “A separate network for IoT devices”You can put the HAM devices on a separate SSID or VLAN. This network must meet the requirements in the table:
- 2.4 GHz and WPA2-PSK.
- An address from DHCP.
- Outbound connections to
*.hamsystems.euon the ports in the table. - No client isolation and no captive portal.
During setup, the phone must be connected to the same SSID as the device.
App requirements
Section titled “App requirements”The mobile app and the web app need only:
| Port | Use |
|---|---|
| TCP 443 | HTTPS to app.hamsystems.eu, api.hamsystems.eu and the device servers. |
| TCP 9001 | Live data over WebSocket (wss) to the device servers. |
Device MAC address
Section titled “Device MAC address”An address reservation needs the MAC address. You can find it in two ways:
- In the client list of the router, after the device connects.
- On the device page, in the Firmware section, on the MAC row. Only users with admin access to the device see this row.
When a device shows offline
Section titled “When a device shows offline”Each device family sends a keep-alive signal at a fixed interval. The interval is usually 240 seconds. If the server does not hear from the device within this interval plus a small margin, the device shows offline.
During a short network outage the device keeps its readings in memory. It sends them when it connects again.
Device settings for the network
Section titled “Device settings for the network”The device settings have two settings for the network:
- Force IPv4: the device connects only over IPv4. It is on by default.
- Allow LAN commands: other devices on the local network can control the device. It is off by default.
See device settings.