System Requirements
To successfully install and operate the nomos system Controller, please ensure that the following system requirements are met:
- Power Supply: A reliable power source is required to continuously power the Controller and ensure uninterrupted operation.
- Network Connection: A stable LAN connection is essential for the operation of the nomos system Controller. It is important that the router is set up by a qualified professional to ensure that it is optimally adapted to your specific network structure. This careful setup is crucial to ensure reliable communication and effective integration of all connected devices.
- Router: The router used must support DHCP without exception.
- Checked systems and documentation: All deployed systems must be fully tested and handed over in working condition. Necessary documentation, such as for KNX, should be available and up to date to ensure smooth integration and maintenance.
Meeting these requirements ensures that your nomos system Controller operates at its best and delivers a seamless smart home experience.
Controller hardware
Since version 2.8.0, the nomos software runs on controllers with a 64-bit ARM v8 SoC. Controllers with an ARM v7 SoC are no longer supported; the last version for them is 2.7.0.
Ports on the local network
The controller uses the following ports on the local network. They only need to be reachable for the devices that use the respective function. Do not forward any of these ports from the router to the internet; for access on the go, use Remote Access and Direct VPN.
| Port | Protocol | Direction | Use |
|---|---|---|---|
| 80 | TCP | inbound | Configuration, nomos app and API over HTTP, including MCP at /mcp |
| 443 | TCP | inbound | as port 80, encrypted over HTTPS (self-signed certificate) |
| 1883 | TCP | inbound | built-in MQTT broker, also for Shelly devices |
| 1880 | TCP | inbound | Node-RED; the browser is sent straight to this port |
| 44880 | TCP | inbound | Project Editor, only while it is open |
| 5540 | UDP | both | Matter |
| 5353 | UDP (multicast) | both | mDNS: device discovery, Matter and HomeKit |
| 49999–50002 | TCP | inbound | HAP (Apple HomeKit) |
| 3671 | UDP | both | KNX over IP, tunnelling to the interface or routing via 224.0.23.12 (see KNX Settings) |
| 3001 | TCP | inbound, only via VPN | USB Serial over VPN (default, configurable) |
Connections to the internet
The controller opens all connections to the internet itself. Cloud, remote access and Direct VPN need no port forwarding on the router. A firewall must allow the following outbound connections, as well as name resolution through the configured DNS servers (see Network).
| Purpose | Destination | Port |
|---|---|---|
| Software updates and licence, online library, weather, push notifications, switching on remote access and Direct VPN, sign-in to cloud skills, diagnostic and crash data (if shared) | apis.nomos-system.com | TCP 443 (HTTPS) |
| Cloud account | account.nomos-system.com | TCP 443 (HTTPS) |
| Cloud connection (Amazon Alexa, Google Home, Cloud Synchronization) | AWS IoT Core, region eu-west-1 (*.iot.eu-west-1.amazonaws.com) | TCP 8883 (MQTT over TLS) |
| Remote Access | nomos relay server, assigned when switched on | set by the service |
| Direct VPN | nomos VPN server (WireGuard), assigned when switched on | UDP, set by the service |
| Support VPN | nomos support server (OpenVPN) | set by the service |
| Cameras: relaying the WebRTC video transmission | stun1.nomos-system.com, turn1.nomos-system.com | UDP 19302 (STUN), 3478 (TURN) |
| Latency test of the security check | nomos-system.com, google.com, apple.com | ICMP (ping) |
| Cloud skills such as Miele, Netatmo or Spotify | the respective manufacturer's servers | TCP 443 (HTTPS) |
App and browser
- nomos system app: iPhone and iPad with iOS 17 or later (App Store), Android version 8 or later (Google Play). The controller accepts apps from version 2.0.0; an older app receives the message A newer app version is available.
- Configuration: a current version of Safari, Chrome, Edge or Firefox on a computer on the same network as the controller.