Velbus binding for OpenHAB


From your previous post I assumed the maximum dim value for the VMB1DM was 64:


Do you see the trigger-channels in openHAB?

Is there anything related to these channels in your log file?
velbus:vmb8pb:72ef5aea:C3:CH1 triggered RELEASED

(slider percentage / 100) * 64 and not (slider percentage / 64) * 100 ?

IT WORKS :smile: i put ON in state instead of PRESSED or released !


log file of dimmer when actionned to 100% : strange?

2018-05-28 21:11:43.077 [ome.event.ItemCommandEvent] - Item ‘Light_FF_Corridor_Ceiling’ received command 100
2018-05-28 21:11:43.113 [vent.ItemStateChangedEvent] - Light_FF_Corridor_Ceiling changed from 0 to 100
2018-05-28 21:11:43.144 [vent.ItemStateChangedEvent] - Light_FF_Corridor_Ceiling changed from 100 to 32
2018-05-28 21:11:43.151 [vent.ItemStateChangedEvent] - HALL changed from 0 to 32


Hi Ciceron,

Can you try this version:

The 64 in the logs is in hexadecimal, which is 100 in decimal.
So no conversion factor should be required…


I will
Thanks …


not working

Any choosen value is automatically forced to 32

2018-06-04 21:58:54.353 [ome.event.ItemCommandEvent] - Item ‘Light_FF_Corridor_Ceiling’ received command 88
2018-06-04 21:58:54.372 [vent.ItemStateChangedEvent] - Light_FF_Corridor_Ceiling changed from 32 to 88
2018-06-04 21:58:55.420 [vent.ItemStateChangedEvent] - Light_FF_Corridor_Ceiling changed from 88 to 32

2018-06-05 19:53:39.977 [vent.ItemStateChangedEvent] - velbus_vmb1dm_72ef5aea_19_CH1 changed from 32 to 0

2018-06-05 19:53:43.474 [ome.event.ItemCommandEvent] - Item ‘velbus_vmb1dm_72ef5aea_17_CH1’ received command 44

2018-06-05 19:53:43.486 [vent.ItemStateChangedEvent] - velbus_vmb1dm_72ef5aea_17_CH1 changed from 0 to 44

2018-06-05 19:53:43.525 [vent.ItemStateChangedEvent] - velbus_vmb1dm_72ef5aea_17_CH1 changed from 44 to 32

2018-06-05 19:53:46.316 [ome.event.ItemCommandEvent] - Item ‘velbus_vmb1dm_72ef5aea_17_CH1’ received command 100

2018-06-05 19:53:46.330 [vent.ItemStateChangedEvent] - velbus_vmb1dm_72ef5aea_17_CH1 changed from 32 to 100

2018-06-05 19:53:49.550 [ome.event.ItemCommandEvent] - Item ‘velbus_vmb1dm_72ef5aea_17_CH1’ received command 0

2018-06-05 19:53:49.568 [vent.ItemStateChangedEvent] - velbus_vmb1dm_72ef5aea_17_CH1 changed from 100 to 0

2018-06-05 19:53:49.591 [vent.ItemStateChangedEvent] - velbus_vmb1dm_72ef5aea_17_CH1 changed from 0 to 32

2018-06-05 19:53:51.602 [vent.ItemStateChangedEvent] - velbus_vmb1dm_72ef5aea_17_CH1 changed from 32 to 0

2018-06-05 19:53:58.012 [ome.event.ItemCommandEvent] - Item ‘velbus_vmb1dm_72ef5aea_18_CH1’ received command 63

2018-06-05 19:53:58.024 [vent.ItemStateChangedEvent] - velbus_vmb1dm_72ef5aea_18_CH1 changed from 0 to 63

2018-06-05 19:53:58.069 [vent.ItemStateChangedEvent] - velbus_vmb1dm_72ef5aea_18_CH1 changed from 63 to 32

2018-06-05 19:54:02.865 [ome.event.ItemCommandEvent] - Item ‘velbus_vmb1dm_72ef5aea_18_CH1’ received command 0

2018-06-05 19:54:02.876 [vent.ItemStateChangedEvent] - velbus_vmb1dm_72ef5aea_18_CH1 changed from 32 to 0

2018-06-05 19:54:02.915 [vent.ItemStateChangedEvent] - velbus_vmb1dm_72ef5aea_18_CH1 changed from 0 to 32

2018-06-05 19:54:04.919 [vent.ItemStateChangedEvent] - velbus_vmb1dm_72ef5aea_18_CH1 changed from 32 to 0


WHAT is this error?
how to fix it?

2018-06-06 20:18:37.943 [ERROR] [org.openhab.binding.velbus ] - FrameworkEvent ERROR - org.openhab.binding.velbus

org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.velbus [223]

Another singleton bundle selected: osgi.identity; type=“osgi.bundle”; version:Version=“”; osgi.identity=“org.openhab.binding.velbus”; singleton:=“true”

at org.eclipse.osgi.container.Module.start( [?:?]

at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel( [?:?]

at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel( [?:?]

at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel( [?:?]

at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent( [?:?]

at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent( [?:?]

at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent( [?:?]

at org.eclipse.osgi.framework.eventmgr.EventManager$ [?:?]


Hi Ciceron,

The error message seems to indicate a version conflict in the Velbus binding.
I think this might be caused by having multiple instances of the Velbus binding jars in your addons folder, or e.g. a builtin version of the Velbus binding (e.g. from the market place) and one in your addons folder.

For the percentage problem with the vmb1dm, could you try the following:

  • In VelbusLink, choose the “Logging” tab and select “New”
  • Send a packet with priority “High” to your vmb1dm address (15), with a data size of 5, and data bytes “07 01 64 FF FF”
  • The 64 should mean 100%, watch the result and check the response packets for the dimmer status
  • Try to replace the “64” by some other values, e.g. “32” for 50%, etc.
  • When you have a set of working packets, use the “Save” button to export the logs, this will be more readable than screenshots


I got the same error:


can you repost an older snapsg-hot to see if I’m not missing something?


ok, needed to add the following:

ssh openhab@localhost -p8101
feature:install openhab-transport-serial

the error is now gone and the snapshot loads :slight_smile:


Ok, played with it and for now I’ve got 3 remarks:

  • the detection of the modules isn’t working well, it stops after receiving 8 modules (got about 40 modules in the system)
  • There’s no feedback to the values when pressing a button in the system, for example, the dimmer values doesn’t follow the system values when using the hardware buttons.
  • Great work!!

I’ll do some more testing the next few days.

PS: I’m using your network binding, maybe that’s got something to do with reading the values back in? Will try later on directly with a comcontrol


(Edit: translated)
Hi Jeroen,

It seems like you found the “network bridge”?
The commands that are sent and received over the network bridge and over the serial bridge are the same, so I don’t see a reason why the values would’nt be read back in by the network bridge. However, I noticed such “packet drop” behavior once when multiple processes were using the same serial port at the same time.


Ok, I’ll try it an other way around. My velbus server is currently running on another pi. I’m going to put verserv locally to see if that does the trick, maybe a networkconfig problem.

I’ll keep you informed

edit translated too



I’m using both a TTYACM0 Bridge connection and a Network Bridge without seeing any missed packets


Same here. Works perfect even with the physical buttons I get feedback. which velbus servers are you using?


I’m only running Linux machines these days.

In Windows I exclusively used Golfy’s PB_Server, but in Linux I use Jeroen’s VelServ (& VelTimer if there isn’t a need for a UI, or I want a separate way of updating the Velbus time)


an uptdate:
gverbist: I’m using my own velserv (since I’m the writer of it :wink: )
further: the relays give me feedback, the dimmer (vmb1dm) not, so there lays the problem, not in the communication binding. Some investigation to do, probably looking in your code at the wrong values


Stuart, do you have an example of the thermostat function in an items/sitemap file?


Hi Geert

I only use the HabPanel, as I’m not comfortable with text files.

However, Tom has written a nice Thermostat widget for Velbus & HabPanel
I can ask if he’s happy to share it publicly


I am making some changes. This should not take to long. I’ll post the file here when it is finished


Here are my config files, I have some thermostats setup in BASIC-UI. Images included