Velbus Signum

First Launch and the Automatic Dashboard

Opening the Velbus Signum app for the first time triggers something unexpected. Instead of a blank screen or a setup wizard asking endless questions, the app builds a complete dashboard on its own. Every connected device in your Velbus installation — lights, blinds, thermostats, sensors — appears as a widget without any manual configuration. This happens because the Signum gateway already knows your entire wired bus system. The app pulls that data over the local network and presents it immediately. No scanning, no pairing, no entering device IDs. For someone who just finished wiring a Velbus panel, this is a relief. The alternative in many home automation apps involves adding each device one by one, which takes time and invites mistakes.

The dashboard uses small interactive tiles. Tap a light icon and it switches on. Slide a thermostat slider and the temperature updates. The widgets reflect the current state of each module in real time. This works over LAN and WiFi, and the app also supports USB connection for direct programming via VelbusLink. The developer notes that port forwarding is still required for remote access, with a cloud solution in development. That limitation matters for anyone hoping to control their home from outside the local network without extra router configuration. The app itself is free, and the gateway hardware handles the heavy lifting of communicating with the Velbus bus.

When Customization Clashes with Automation

The Signum runs a customized version of Home Assistant, optimized for Velbus hardware. This gives it power beyond a simple remote control. But the automatic dashboard, while convenient, becomes a point of tension for users who enable Advanced Mode. Advanced Mode unlocks configuration.yaml, HACS, and custom integrations. Once you start adding third-party components or writing automations, the pre-built dashboard no longer matches your setup. The widgets still show the original devices, but they don't reflect new entities or custom sensors. You end up rebuilding the interface manually, which defeats the purpose of the automatic generation. One user on the Velbus forum noted that the Signum shows 429 devices and 1,416 entities, while their own Home Assistant instance only displays 58 devices and 16 entities. That gap highlights the difference between what the gateway sees on the bus and what a customized system chooses to expose.

This friction is not a bug. It is a design trade-off. The automatic dashboard serves the majority of users who want a working interface out of the box. The Advanced Mode serves tinkerers who want full control. But the two modes do not blend smoothly. A user who enables Advanced Mode must accept that the initial convenience fades. The app does not warn about this during setup. The changelog shows ongoing work to fix color display issues on RGBW channels and edge lights, but nothing about reconciling the automatic dashboard with custom configurations. For a system marketed as both simple and flexible, this gap creates a real workflow problem.

Performance, Delays, and Real-World Use

Controlling devices through the app feels responsive when you are on the same network. Tap a light, it changes instantly. Adjust a blind, it moves without hesitation. The trouble starts when you use the API or connect through third-party integrations. One forum user reported delays of up to 30 seconds when controlling blinds or lights through the Signum's API. That is not a typo. Thirty seconds between pressing a button and seeing a blind move makes the system unusable for daily interaction. The same user noted that the Signum uses a Raspberry Pi CM3 internally, which has limited RAM. The Home Assistant website itself warns that Pi 3 models do not have enough RAM to run stable. The Signum's optimized version strips down Home Assistant to fit within those limits, but performance suffers when you add extra integrations or custom automations.

The app also has reliability issues on iOS. Multiple forum threads describe the Signum app crashing on iPhone 13 with the latest iOS update. Users report connection problems, and some cannot see temperature readings or control heating at all after an update. The changelog for the Android version mentions a bugfix for connections showing offline while they are online, indicating that network state detection has been problematic. For a system that controls lighting and heating, false offline status is more than an annoyance. It creates uncertainty about whether your home is actually responding to commands.

Hardware Limitations and the Disabled USB Port

The Velbus Signum gateway mounts on a DIN rail inside your electrical panel. It connects to the Velbus bus via a Molex cable and to your network via Ethernet. The hardware itself is compact and fits in existing distribution boards, which makes it suitable for renovation projects. But the USB port on the front is disabled. You cannot plug in a Zigbee stick, a Z-Wave dongle, or any other USB peripheral directly. This is a deliberate choice by Velbus. The company recommends using Ethernet-based Zigbee gateways instead, such as a Zigbee2MQTT bridge connected to your network. If you want the USB port enabled, you must send a request to help.velbus.eu to have your Signum unlocked. Once unlocked, the Signum automatically receives an update that enables the USB interface. However, this process requires agreeing to release support from Velbus, and you lose the ability to return to the locked-down version without losing extra functions.