If you connect via TCP the velbus serial device should not be mounted anymore…
The velbus snap package will own the device, so no need to add it to the docker
2 Likes
After using the by-id path for years, because there was only one Velbus idProduct, I’ve had to come back to your solution.
I’ve expanded it a little, to include the three varieties of Velbus IDs.
Creating this file
/etc/udev/rules.d/V80-usb-serial-velbus.rules
With this content
SUBSYSTEM=="tty", ACTION=="add|change", ATTRS{idVendor}=="10cf", ATTRS{idProduct}=="0b1b", SYMLINK+="ttyVelbus-VMBRSUSB"
SUBSYSTEM=="tty", ACTION=="add|change", ATTRS{idVendor}=="10cf", ATTRS{idProduct}=="0b1c", SYMLINK+="ttyVelbus-VMBUSB-20"
SUBSYSTEM=="tty", ACTION=="add|change", ATTRS{idVendor}=="10cf", ATTRS{idProduct}=="0516", SYMLINK+="ttyVelbus-VMBSIG"
on a reboot or replug of the USB, the OS will create an easily identifiable Symlink when the module is (re)plugged in.
My output looks like this with this command
ls -l /dev/ttyV*
lrwxrwxrwx 1 root root 7 Jul 27 08:13 /dev/ttyVelbus-VMBRSUSB -> ttyACM1
lrwxrwxrwx 1 root root 7 Jul 27 08:13 /dev/ttyVelbus-VMBSIG -> ttyACM2
lrwxrwxrwx 1 root root 7 Jul 27 08:13 /dev/ttyVelbus-VMBUSB-20 -> ttyACM0
@Stef_Coene
Thank you so much for suggesting this and sharing your solution.
Taking this thought a stage further, I’m trying to work out how to recreate the Auto-Restart that @jeroends has with VelServ.
Does anyone fancy testing this for me?
A uDev rule to restart velbus-tcp when the USB is plugged in.
udev rule /etc/udev/rules.d/v90-USB-serial-velbus-tcp.rules
SUBSYSTEM=="tty", ACTION=="add|change", ATTRS{idVendor}=="10cf", ATTRS{idProduct}=="0b1b", RUN+="sleep 2s & sudo snap restart velbus-tcp"
SUBSYSTEM=="tty", ACTION=="add|change", ATTRS{idVendor}=="10cf", ATTRS{idProduct}=="0b1c", RUN+="sleep 2s & sudo snap restart velbus-tcp"
SUBSYSTEM=="tty", ACTION=="add|change", ATTRS{idVendor}=="10cf", ATTRS{idProduct}=="0516", RUN+="sleep 2s & sudo snap restart velbus-tcp"
Everything I have been working on can be found in this ZIP file
https://www.velbus.co.uk/dl/velbus/velbus-tcp.zip
An experimental thought…
Does anyone know if a single rule like this would work?
/etc/udev/rules.d/v99-USB-serial-velbus-tcp-reset.rules
SUBSYSTEM=="tty", ACTION=="add|change", ATTRS{idVendor}=="10cf", ATTRS{idProduct}=="0b1b", SYMLINK+="ttyVelbus-VMBRSUSB", RUN+="sleep 2s & sudo snap set velbus-tcp serial.port=/dev/ttyVelbus-VMBRSUSB"
SUBSYSTEM=="tty", ACTION=="add|change", ATTRS{idVendor}=="10cf", ATTRS{idProduct}=="0b1c", SYMLINK+="ttyVelbus-VMBUSB-20", RUN+="sleep 2s & sudo snap set velbus-tcp serial.port=/dev/ttyVelbus-VMBUSB-20"
SUBSYSTEM=="tty", ACTION=="add|change", ATTRS{idVendor}=="10cf", ATTRS{idProduct}=="0516", SYMLINK+="ttyVelbus-VMBSIG", RUN+="sleep 2s & sudo snap set velbus-tcp serial.port=/dev/ttyVelbus-VMBSIG"
Theory being that when a Velbus USB device is plugged in, the rule will set a symlink, wait 2 seconds, set the SNAP Package to the new ttyVelbus-xxxxx port, which will cause it to restart
@PrzemoF @RCZ
Is this something you fancy trying for me?
(As I don’t run openHabian for example, I’ll test it with DietPi machines I have)
1 Like
Good evening MDAR,
I was on vacation in July and I must have missed your message dated from 19 July…until tonight 
.
Meanwhile I reinstalled Openhab a few times because an Openhabian upgrade ruined everything. Pi was running hot and no rules where executed anymore. I ran your revisited zip (see last message) but still no Velbuslink connection via TCP/IP. All the rest(OH) is working fine again. I didn’t have a lot of time recently but I’m wondering if others experiencing the same problem?
It’s not an urgent one but if I can help you testing…let me know.
Kind regards and sorry for this dust covered reply!
Jona
1 Like
No problem.
I’ll start another thread, specially to address your issue, which will make it easier for others to find in the future should they come looking for openHABIAN issues.
Cool. I will keep an eye on it 
. Thanks for your help!!!
I have a NUC, i dit install it a few years ago, i don,t know which linux is on it but when i restart the NUC it is always ending with Homeassistant, i think its a runtime Linux.
I. am not at home yet, but when i am, can i connect a hdmi and keyboard to the NUC, and i think it have a command prompt.
As i don’t have a password and user (maybe root) of the Linux version i can not access my NUC from my Laptop (Putty) or better Mac with terminal.
If that fails i should re install a Home Assistant, then i should use a (NUC / linux) installation that most of the people use here. Does anybody know which installer to use?
I know i have now a (not container) version of HAOS
Good luck.
Without an SSH or Command line access to the core OS, you’ll not be able to install Velbus-tcp or VelServ.
If, it is a pure HomeAssistant image, I believe there is an SSH plugin that needs to be loaded.
However, that’s where my knowledge ends with HA.
Yes, there is a plugin: terminal or something like that, i have it, but i don’t have the password and user name of the linux.
If you don’t recall changing them, have you tried the default credentials?
Nope, i don’t know the original pw
I think the packages are changed the last Year.
I have the ha os the first of the 3 options Czoete on 95/110 so i also not have the option to ssh or command prompt
So i need a new install, Wich one? i have a lot of raspberries but the are using unsave memory cards, Green and Yellow do have better disks but do they have access to OS? which option to use?
I have bought a Signum, there are too many problems with usb and installation with Home Assistant.
Okay.
That’s probably the best option in this situation.
Unfortunately not. Apparently I am the first to buy a Signum, and it now appears that no hub can be connected, no Zigbee but also no Zwave stick or hub. And now it appears that this apparently still needs to be implemented. I have made inquiries in the forum here but also on various HomeAssistant groups, and apparently no one has experience with it. So it was put on the market without testing it first. In the meantime, 1300 euros later and… the old people at home are still without light, I have to come back to their house from work because the old (Homeassistant) system keeps switching off the screen and has to be restarted. Pulling cables is not allowed by the landlord, so Zwave or Zigbee has to be used at that location, the Velbus screens are much easier to operate, intuitive, but unfortunately after years (I have been working on it since 2019) there is still no good connection with wireless lighting. And indeed, I will have to look for another system next
I don’t have words to reply
Even the entities > 62 entities on Home Assistant like Alarm1 2 3… button 1 2 3 etc but when i want to pick one to test if the button is hit… No! the identity is disabled!! all 62? how to enable?
See picture: The identity is disabled, on Dutch: de identiteit is uitgeschakeld!
I just bought a HUE hub, it is connected on utp so no USB, and this is working. Too bad, only for lightning, there is no power measuring on on/off plugs, so there is no solution for this, as these plugs are Zigbee or Zwave, i don’t know of a Zwave hub that connects on UTP (network)
Hi @bonestaak ,
Thanks for sharing your experience. It’s clear that you’re trying to support a setup involving people in a property with strict installation limitations. That can definitely make things more challenging, especially when wireless functionality is a core requirement.
That said, I’d like to clarify a few important points for the benefit of others reading along, and to ensure everyone has accurate expectations:
Velbus and Signum – Scope and Expectations
- Velbus is, by design, a wired home automation system. While we fully understand the growing demand for wireless integrations, the system’s strength and reliability stem from its robust bus-based architecture. Wireless support is possible, but not part of the core product.
- The Signum is not a Zigbee or Z-Wave controller or hub. It doesn’t contain radios for wireless standards. It is a communication bridge between Velbus and third-party platforms (like Home Assistant, MQTT, Node-RED, etc.). If wireless connections are required, you’ll need additional hardware outside the Velbus product line.
- More than 1,000 Signum modules are currently running smoothly in real-world installations. When used within their intended purpose — as a secure and robust interface to Velbus — Signums have proven to be reliable and extremely stable.
Wireless Integration and Energy Monitoring
- If your goal is to connect Zigbee devices (e.g. wireless lights or switches), you’ll need a Zigbee-to-Ethernet gateway (like a Zigbee2MQTT bridge). This device must be on the same local network as Home Assistant to enable integration.
- Many users have already tested this successfully, combining Zigbee or Z-Wave networks with Velbus through Home Assistant. It’s a powerful solution, but some setup in Home Assistant is required — it’s not plug-and-play (yet).
- The USB port on the Signum is currently disabled. USB Zigbee or Z-Wave sticks won’t work for now. We are still investigating the potential security vulnerabilities of enabling this feature, as simply opening USB access could expose the system to unnecessary risk.Furthermore, placing a wireless stick inside an electrical cabinet is usually not ideal for signal quality or system stability. That’s why we recommend and endorse Ethernet-based wireless bridges instead, which can be placed in more optimal wireless locations.
- For kWh monitoring, Velbus supports Modbus TCP/IP meters, connected over Ethernet, or pulse output meters wired into a VMB7IN/8IN module (such as the VMB8IN-20).These are proven and accurate solutions, used in many long-term projects.
Final Thoughts
It might not be the cheap or zero-effort solution you’re hoping for, but it is a stable, proven platform built to last for decades. We prioritize reliability, security, and long-term support over short-term convenience — especially when it comes to core infrastructure like home automation.
If wireless and plug-and-play are your main requirements, Velbus might not be the right standalone system for your use case. But with a little help via Home Assistant or from an experienced integrator, it’s absolutely possible to create a hybrid system that combines Velbus reliability with the flexibility of wireless devices.
We’ve also noticed you’re struggling with some basic Home Assistant features, such as disabled entities. We strongly recommend taking a bit of time to explore and understand Home Assistant more in depth — this will help you move forward faster and avoid unnecessary frustration.
We’re always happy to assist and we welcome honest, constructive feedback like yours. It helps us improve and guide others more clearly.
2 Likes