# Velbus TCP connection with openHABIAN **URL:** \ **Category:** For developers\ **Created:** [October 1, 2024, 10:51am UTC](https://forum.velbus.eu/t/velbus-tcp-connection-with-openhabian/17544 "2024-10-01T10:51:03Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![MDAR](https://forum.velbus.eu/user_avatar/forum.velbus.eu/mdar/32/4215_2.png) [@MDAR](https://forum.velbus.eu/u/MDAR)\ **Post date:** [October 1, 2024, 10:51am UTC](https://forum.velbus.eu/t/velbus-tcp-connection-with-openhabian/17544/1 "2024-10-01T10:51:03Z")
@jvelbus Following on from your posts in these threads, regarding the connection between an openHABIAN OS install, Velbus Network bridge and the official Velbus SNAP TCP gateway package > [@TPC/IP connection Velserv - Velbuslink not working](https://forum.velbus.eu/t/tpc-ip-connection-velserv-velbuslink-not-working/17488/15): > > Good evening, > Sorry for my late reaction. Indeed there is no by-id only by-path. > [@How-To : Install and Run VelServ - a Velbus TCP Gateway](https://forum.velbus.eu/t/how-to-install-and-run-velserv-a-velbus-tcp-gateway/15422/103): > > 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? For the record, I don’t use or have ever used the openHABIAN OS method, nor in fact have I spent more than a few hours fighting with a Raspberry Pi. I’m hoping that @PrzemoF and @cereal can chip in and shine some light on what is going on in your setup. Purely for reference, this PDF outlines the basic workflow, where we are refering to the link between the Velbus hardware and various software solutions. > **[Workflow-Velbus-openHAB-VelbusTCP-Node-RED-HomeAssistant-Control4-QLCplus-ArtNet.pdf](https://www.velbus.co.uk/dl/drawings/Workflow-Velbus-openHAB-VelbusTCP-Node-RED-HomeAssistant-Control4-QLCplus-ArtNet.pdf)** > > 4.33 MB So first, let’s set some baselines. - You’ve got openHAB up and running and as far as you can see, everything in openHAB is working fine. - You’ve got a USB connection between some version of a Velbus USB module and your PI - You’ve installed **Either** VelServ _or_ velbus-tcp After that, my gut feeling is one of two issues. Either the configuration of VelServ / Velbus-TCP is wrong or The configuration of the Velbus Network Bridge is wrong. Can we focus on the Velbus hardware side first and work back from there? ??? Exactly which Velbus USB module are you using? VMB1USB VMBRSUSB VMBUSB-20 ---
**Author:** ![PrzemoF](https://forum.velbus.eu/user_avatar/forum.velbus.eu/przemof/32/4758_2.png) [@PrzemoF](https://forum.velbus.eu/u/PrzemoF)\ **Post date:** [October 1, 2024, 11:37am UTC](https://forum.velbus.eu/t/velbus-tcp-connection-with-openhabian/17544/2 "2024-10-01T11:37:31Z")
Also provide the debug info as it the main topic, dmesg, lsusb, systemctl status velserv Hey, it’s linux - in 99% of the cases the info is in the logs, we just need to find and understand it. Reference: [Installing OpenHAB – Velbus binding – Core Dump](https://firszt.eu/velbus/installing-openhab-velbus-binding/) ---
**Author:** ![MDAR](https://forum.velbus.eu/user_avatar/forum.velbus.eu/mdar/32/4215_2.png) [@MDAR](https://forum.velbus.eu/u/MDAR)\ **Post date:** [October 1, 2024, 11:41am UTC](https://forum.velbus.eu/t/velbus-tcp-connection-with-openhabian/17544/3 "2024-10-01T11:41:51Z")
> [@PrzemoF](#): > > provide the debug info as it the main topic, dmesg, lsusb, systemctl status velserv 😄 let’s stick to first principles to start with. What & how is plugged in. We can probably fix it from just that information 😉 ---
**Author:** ![jvelbus](https://forum.velbus.eu/letter_avatar_proxy/v4/letter/j/34f0e0/32.png) [@jvelbus](https://forum.velbus.eu/u/jvelbus)\ **Post date:** [October 7, 2024, 8:52am UTC](https://forum.velbus.eu/t/velbus-tcp-connection-with-openhabian/17544/4 "2024-10-07T08:52:36Z")
Hi all, I’m currently not at home till the end of the week. I’ll get back somewhere in the WE. Thanks in advance!!!