Hi Bert,
This is probably because your are not running the latest snapshot version of openHAB. The binding is already using functionalities that are not yet present in the current openHAB stable build. To use the binding now, you will have to switch your openHAB version to the latest dev snapshot as described here: How To: Switch installed version (stable build to latest dev snapshot) - openhabian.
THANK YOU for finally making it possible to use the velbus system with a proper software!
1 Like
Hi,
I got 2 first-gen vmb4pd modules. Although the vmb8pb was found using the Velbus Binding search, my vmb4pd’s are not found. Any idea on how to fix this?
Can I add them manually using my things file? Any idea how?
tx!
Gert
Hi Cedric,
I finally found some time to pick this up again. Started from a clean new install in my RPI and switched to OH 2.4.0 snapshot (#1408), this brings Velbus binding 2.4.0 snapshot.
Also installed Velserv in the PI.
Velbus bridge shows ONLINE now in the Paper UI Things screen but when I start a search in the Inbox on the Velbus binding, no modules are detected.
Any suggestions to get this working ?
I believe the VMB1TS (temperature sensor) module is not supported? Is it? Plans to integrated also this module in the binding?
Hi
There is a bleeding edge jar file version of the Velbus binding that you can install.
First you will have to fully remove the downloadable version within PaperUI.
All the instructions are here, on the Velbus forum, along with a link to the very latest openHAB2 Velbus binding.
Good luck,
Stuart
FYI
A similar question was asked on this forum, here :-
Thanks for this information.
I managed to change the .jar file. Everything seems still to be working as before, and in the PaperUI scanning the Velbus binding discovered me 1 extra thing, a VMB1BL module. Showing me I did it right I believe.
The 4 different VMB1TS (https://www.velbus.eu/products/view/?id=366816) in my system are not discovered.
Are these modules supported by this version of the binding?
It certainly looks like you’ve done everything perfectly.
I could have sworn that the VMB1TS has been added.
The functionality of a VMB1TS is the same as the Thermostats within the glass panels, so if we’re really lucky, Cédric will be able to work some magic on the binding.
(I do know that he is extremely busy, so it might take him some time)
Cheers,
Stuart
is the velbus intergration via the JAR now compatible with the release 2.4 release or do we need to install the Milestone verison? Using the network bridge etc
Now there’s an excellent question.
I can give it a try on a spare machine, while I ask Cédric.
You can’t do any harm by trying 
Tried it, Still need to install the snapshot version
Hi
Cédric says that it should work 
I was putting a system together for someone a few days ago and realised that I needed to add the V1 Serial binding before the Velbus binding appeared.
If you use the Karaf console with bundle:list you’ll see if the Velbus binding is “installed” or “active”
bundle:list -s |grep elbus
Without the serial binding, Velbus was showing as “installed”, but when I tried to activate it, it threw a dependency error.
Adding the serial binding got it working without any further fuss.
Does that help at all?
got the same thing, So I moved to 2.5M1
The velbus binding does not work in the new release even not when you add the feature:serial …
That’s strange.
I’m running 2.5M1 and the binding is working perfectly.
Did you load the serial binding from the Karaf console or the PaperUI?
bundle:list show the Velbus binding as active
Hey @Geert_Verbist 
Did adding the V1 serial binding from within PaperUI solve the problem?
Cédric says…
I defined a dependency on the serial binding, so when installing the binding from the official distribution I expect the serial binding to be installed automatically. However, using a jar file to install the latest version of the binding might bypass this dependency check. Once the VMBELx en VMB4AN modules are integrated I should make some time to merge all changes of the 12 months back to the official branch
Hi Ben
There is a development version of the Velbus binding available which has experimental support for the VMB1TS.
Would you like to to try it and give some feedback?
You’ll need to completely remove all traces of the current binding (obviously not your Things and Items etc), including double checking in the Karaf console
openhab-cli console
bundle:list -s | grep elbus
bundle:uninstall {number of existing Velbus binding}
Then simply run this script to pull down the development binding.
wget http://www.mdar.co.uk/dl/openhab2/update-velbus-jar-dev.sh
sh update-velbus-jar-dev.sh
If you’re using PaperUI, you might have to temporarily delete a Velbus Thing and add it again so that new functionality can be profiled.
(Items will (should) be automatically re-connected with the Thing)
Hello,
Are the (relative new) edge lit glass switches also added? The VMBEL4 I purchased some and am I now discovering these are not supported?
Help would be appreciated!
Greetings matthijs
Hi
I’ve been working on some widgets for use primarily with the Velbus hardware, but there’s no reason why they couldn’t be used with other hardware.
I’ve created two versions of the Widget, one that uses the default names that are created in PaperUI when Items are added to Things, and one that requires Items to be named according to the Widget requirements.
My thoughts are that either will work, but just depend on how people want to work.
They are both in this zip file - http://www.mdar.co.uk/dl/forum_assets//VelbusThermostatStreamlined.widget.zip
These are the notes that are in the zip file, to help with naming conventions
All elements are taken from the Room name with following suffixes
Where Items are Numbers only, not Number:Temperature (or strings and switches)
IE, Room name = Lounge
Current Temperature = Lounge_CurrentTemperature
Current Target Temperature = Lounge_CurrentTargetTemperature
Operating Mode = Lounge_ThermostatOperatingMode
Current Mode = Lounge_ThermostatMode
Heating Relay = Lounge_HeatingRelay
Cooling Relay = Lounge_CoolingRelay
Heating Mode Antifrost target = Lounge_HeatingAntifrostTarget
Heating Mode Night target = Lounge_HeatingNightTarget
Heating Mode Day target = Lounge_HeatingDayTarget
Heating Mode Comfort target = Lounge_HeatingComfortTarget
Cooling Mode Antifreeze target = Lounge_CoolingSafeTarget
Cooling Mode Night target = Lounge_CoolingNightTarget
Cooling Mode Day target = Lounge_CoolingDayTarget
Cooling Mode Comfort target = Lounge_CoolingComfortTargetNotes for Streamlined Thermostat with Velbus Default Names, where Items are Numbers only, not Number:Temperature (or strings and switches)
Heating Relay = Lounge_HeatingRelay
Cooling Relay = Lounge_CoolingRelayCurrent Temperature = Lounge_CurrentTemperature Watch out for this one, as default would be Lounge_Input_Lounge
Current Target Temperature = Lounge_Thermostat_CurrentTemperatureSetpoint
Operating Mode = Lounge_Thermostat_OperatingMode
Current Mode = Lounge_Thermostat_Mode
Heating Mode Antifrost target = Lounge_Thermostat_HeatingModeAntifrostTemperatureSetpoint
Heating Mode Night target = Lounge_Thermostat_HeatingModeNightTemperatureSetpoint
Heating Mode Day target = Lounge_Thermostat_HeatingModeDayTemperatureSetpoint
Heating Mode Comfort target = Lounge_Thermostat_HeatingModeComfortTemperatureSetpoint
Cooling Mode Antifreeze target = Lounge_Thermostat_CoolingModeSafeTemperatureSetpoint
Cooling Mode Night target = Lounge_Thermostat_CoolingModeNightTemperatureSetpoint
Cooling Mode Day target = Lounge_Thermostat_CoolingModeDayTemperatureSetpoint
Cooling Mode Comfort target = Lounge_Thermostat_CoolingModeComfortTemperatureSetpoint
A widget for the Alarm Times can be found here, but you will need to add the rules that restrict the hours and minutes
Hi
The developement version of the Velbus binding has limited support for the Edge Lit panels, if you want to give it a try, please follow these instructions
This new version addresses an issue with the VMB1TS too, can you give it a try and confirm that it is working correctly please.
(I have 1 x VMB1TS on my test rig which seems to be fine)
Hello everyone
I’ve finally taken the time to get my head around how text based Item files work, because we’ve got a fun installation in the pipeline and I think it will save some time.
However, there is a small issue.
I think I have added the Alexa and Google assistant metadata correctly, but I don’t have any Alexa devices so can’t test it.
If anyone is feeling adventurous and generous, would you mind trying to create an Items file from the template in this ZIP file
Then letting me / us know if it plays nicely with Alexa?
I’ve included 4 updated widgets and a couple of rules in the zip for completeness. (as well as some example Items files that I’m trying in my own home)
Thanks in advance for your help.
Best wishes,
Stuart
