Hey all,
Actually I’m trying to connect Openremote on Raspberry Pi3 with Velbus. Openremote server running on the Pi and can be connected by the UI on my Android Phone…However I’m struggeling with the connection between the Pi and the VMBRSUSB.
If I do see it right the Pi is connected to the VMBRSUSB by an USB cable but how do you need to set the connection right?
My Raspberry has a static IP address 192.168.1.195:8688. In the Open Remote designer I filled out following fields:
I filled out the Velbus.server ip (192.168.1.190) and the port (8445) a bit random. Is this allowed or should it be specific?
Do you need to specify which USB port on the PI should communicate with the VMBRSUSB or is this automatically done by connecting a cable to one of his ports? Or I’m I seeing this completely wrong?
I’ve been busy quite a while to setup and to install everything but I would be delighted if someone could help me a little bit further.
I’m very happy to help you get your OpenRemote controller up and running with your Velbus installation, but before I go into great detail, can I ask if you’re read the first two paragraphs of this how to guide? (And followed any links that take you eye)
There is mention of JVelbusD which is a Linux / Java USB to IP server.
All you need to do is get this, or any other Velbus to IP server running on your Raspberry Pi and point OpenRemote to the defined port.
For example
IP address - 127.0.0.1
Port - 6000 (if using JVelbusD)
You can search this forum for VelServ if you don’t get on with JVelbusD.
Alternatively, I’m told that you can issue a ‘cat’ command that will pass everything from a USB port to an assigned IP port.
It’s not the most robust way of going about it, but it might work.
You could also try searching the OpenRemote Google groups page, as I have previously answered similar questions.
First of all many thanks for your continuous and ever lasting effort to help all of us in this forum. You answered already so many questions…so again THANK YOU SO MUCH!!!
Ok now i got it ;). I’ve read already the Velbus documentation above many times and now I do understand what you mean by the JVelbusD USB to IP server. This was my missing link. I knew there have to be an interface out there between the Openremote and Velbus but I didn’t get the point. Until now.
I’m out for the WE but I will try it out next week and I give you an update on this matter.
Just a small question… The thee files below after unzipping the JVelbusD zipfile…I guess you put them in the OR-server folders (in my case on the Rasp PI but that will be similar like on other platforms I suppose…). Do you know the exact folder location? I’m trying to work very systematic because I’m not used to work in Linux.
There’s no hard rules as to where you put those three files, it’s the paths to start them and the exact file path to the Java library in the config file that are important.
By running JVelbusD (or something like it) you can simultaneously connect OpenRemote and VelbusLink to your installation via the IP port of your server machine
Which helps for programming / reprogramming or debugging
I’m trying to get grip on linux and what in the script but I’m certainly missing some things…First before trying other Java USB to IP servers, I will try to make the JVelbusD working…
What you told my in yr previous reply is that ‘the exact file path to the to the Java library in het CONFIG file that is important’. Do you mean the ‘jvelbusd.sh’ or the ‘jvelbusd.config’ file?
I didn’t change the content of the files yet because I’m a bit careful doing that…
My ‘jvelbusd.sh’ file contains but I’m not sure about the library path (last line) :
My ‘jvelbusd.config’ contains:
Is this the right way or is the path to my lib incorrect?
Thanks Stuart for your time. Have a great sunday!!
It looks like you are really close to getting it up and running.
You are at the really fiddly bit
However, if you follow these instructions to the letter, you should be able to get up and running quickly. (I get stuck in the details of the last few steps if I go through it fast)
The long folder location listed in your result must contain all of the RXTX files, which aren’t always copied correctly. (We are working on a totally different solution for all this, but there is much to do)
So, please ‘cp’ all of the rxtx files into the folder that is indicated by the java.ext.dirs= entry.
Then it’s just a matter of…
Editing the jvelbusd.config file to include the specific path to RXTX-comm.jar,
or remove all reference if it is located in a normal place, as defined by “java.ext.dirs=”
I think that should get you up and running, assuming you run it with the sudo command or on bootup using the RC.local method.
Please excuse the short answer, I’m accessing the site from my phone.
Yeah I getting closer. Will first try to run the JVelbusd module. It’s in my nature not to quit easily things when something is difficult … So I will let you know how it turns out.
because I’m not used to work in Linux.
