Now I’m trying to get velserv running (I used Velbus binding connecting to Velser but it’s similar to this thread).
I get following error when trying to enable velserv.service:
Failed to enable unit: File velserv.service: Bad message
When checking the status I get this:
● velserv.service
Loaded: error (Reason: Bad message)
Active: inactive (dead)
Jan 04 12:34:31 openHABianPi systemd[1]: [/etc/systemd/system/velserv.service:9] Invalid section header
I got the number 3809, which (I suppose) means that it’s running.
Then I just started “cleaning up” the velserv.service, meaning I put everything on a new line when I felt it should
So I guess it works now, I can connect with Velbuslink over TCP/IP, so that’s great.
Just to be sure, I’m gonna reboot the RPi again, and test if I can connect with Velbuslink
You actually thanked the author for referencing to your website…
But I honestly have to say, his explanation was more understandable than yours
I’m pretty sure the problem lies with me, since I know sh*t about linux coding.
I just wanted to let you guys know that I have disabled the Velserv service, as it interfered with the status-updates in Habpanel. Statuses weren’t shown correct when I pushed a button, temperatures were N/A.
So I disabled the service, and stopped it. Now, whenever I need it, I just start the service, and then stop it again after I have used it.
Still very happy that I don’t have to use a USB-cable anymore to change something with Velbuslink.
Are you still trying to use a Velbus Serial Bridge in openHAB2?
Or have you created a Velbus Network Bridge in openHAB2 and pointed it to VelServ?
FYI
I haven’t used a direct USB connection (serial bridge) in openHAB2 since Cédric added the Network Bridge.
It’s easy enough to swap your Velbus Things over to a new bridge in openHAB2.
Just set up the new Velbus Network Bridge in paperUI. Using the correct IP and port (don’t use localhost, its better to use 127.0.0.1 on the same machine)
Edit each Thing so that it uses the Network Bridge.
Delete the Serial Bridge once you’ve migrated all the Velbus Things.
You might need to restart openHAB2 (after starting the VelServ service) just so that openHAB2 can re-initialise each Thing)
Are you still trying to use a Velbus Serial Bridge in openHAB2?
I am…
I have now installed the Velbus Network Bridge in paper UI. Not sure how to point it to Velserv. I use 127.0.0.1, and port is 8080 (which is the standard openhab port I think).
–>*EDIT: should be port 6000 I suppose, gonna change that and let you know.
–>*EDIT2: nope, 6000 gives an error, 8080 says it works.
Updating each Thing to use the network bridge as we speak. I get a “thing updated” notification, but in the list of Things, everything looks the same. I’m gonna update each thing, then start the velserv service, and reboot the RPi, hoping everything works, and then I’ll delete the serial bridge.
The port to point the Velbus network bridge to is whichever port VelServ is outputting to. (My service file tells VelServ to use port 6000, but the default port for VelServ is 3788)
Until you remove the serial bridge in openHAB2 and start VelServ, it won’t work
(I’ve got no idea why pointing it to port 8080 suggests that it’s working, as port 8080 is the html server)
(Hence suggesting that you complete the changes, then reboot before deciding if it’s working)
Delete the serial bridge before rebooting, as you’ll never know if the serial bridge locks the USB interface before VelServ gets a chance to connect.
I changed the network binding port setting tot 3788, I get a reply “offline, communication error”
When I change it to 6000, the binding is online. (Velserv is running)
I did remove the serial bridge before rebooting…
When I look at the settings of any of my things, it shows the new network binding, but in the overview with all the things, they still show the old serial binding.
The 10370302 is the serial binding (which is deleted before reboot)
That’s what I was trying to explain, while changing the settings for each thing to the network bridge, in the settings it changed, I even got a notification that settings were saved, but in the overview nothing changed…
I can even still switch every output in Habpanel (which uses the outputs with the serial binding)
I thought that number was just a (random) unique ID for each Thing. I never noticed that it was the ID for the bridge (that was in play when the Thing was first created).
The thing is, Habpanel is working fine on my phone, but on my laptop it doesn’t. Status updates aren’t correct, it’s like I need to push a button again to have it updated.
Same goes with basic UI, which I recently started playing around in. I had a few thinks working, but now they don’t work anymore. Maybe that has something to do with the new network bridge.
I’ll search on that another time. Since it’s Sunday, maybe I should spend some attention to my girlfriend now