Velbus binding for OpenHAB

MDAR · December 4, 2019, 10:14pm

Hi

My apologies, I thought we posted about the VMB1TS being up and running in a development version that Cédric is working on.

You can access it by downloading and running this script.

sudo wget http://www.mdar.co.uk/dl/openhab2/update-velbus-jar-dev.sh

sudo sh update-velbus-jar-dev.sh

Just make sure you only have 1 binding running in openHAB2

By accessing the Karaf console and checking the bundle list

openhab-cli console
bundle:list | grep Velbus

I’ve got this binding running on a 2.4 version and a 2.5

Does that help you?

bouwkarolinemaarten · December 5, 2019, 12:49pm

Hi MDAR,

Thanks a lot for the clear instructions. I think the script/update was successful as I’m able to manually add the VMB1TS, unfortunately something is wrong at my setup, since after the works the blinds and meteo are not responding anymore / though relais/input modules are still reacting. I initially assumed a bus error but the windows velbuslink is still able to discover them all. The output of Karaf console can be found below (it looks indeed i’m running 2x the velbus binding). What the best troubleshooting action now? (remove the velbus binding from PaperUI and start again?)

A view on the current status of the Openhab Things:

MDAR · December 5, 2019, 12:55pm

HI

I suspected that might happen, which is why I said you check that you only have 1 bundle loaded.

The 2.4 version should vanish if you reboot, or you can remove it from the database (because the JAR file was deleted by the script) by simply starting the Karaf console and entering (in your specific case, other people will have a different number)

bundle:uninstall 219

“2.5.0.201908142035” is the development version, there are a few bugs in it, which I’m sure Cédric will address when he has time.

You may need to disable and re-enable the Velbus Network Bridge (or serial) bridge to force and update of all of your Velbus modules within openHAB2.

I find it easiest to do this in PaperUI, by clicking on the clock symbol (again after a pause of a few seconds)

bouwkarolinemaarten · December 5, 2019, 2:11pm

Hi,
Almost there … all modules working again after removing v2.4 and VMB1TS is now auto discovering/recognized in “inbox”, but for some reason not “online” yet (despite reboots, disabling serial bridge, reinstalling serial bridge)… sorry but still some hints required? Any minimum prerequirements with respect to firmware level ?
Thanks a lot

MDAR · December 5, 2019, 2:44pm

Now there’s a good question.

I’m sure it has been working, but now even mine is showing similar

With a very different build / firmware version and serial number than is shown in VelbusLink

I think this is something that @cedricb needs to work his magic on, we may have to wait patiently, as he is extremely busy.

MDAR · January 8, 2020, 12:00pm

@bouwkarolinemaarten

MDAR:

My apologies, I thought we posted about the VMB1TS being up and running in a development version that Cédric is working on.

You can access it by downloading and running this script.
sudo wget http://www.mdar.co.uk/dl/openhab2/update-velbus-jar-dev.sh

sudo sh update-velbus-jar-dev.sh
Just make sure you only have 1 binding running in openHAB2

By accessing the Karaf console and checking the bundle list
openhab-cli console
bundle:list | grep Velbus
I’ve got this binding running on a 2.4 version and a 2.5

Does that help you?

Hi

Cédric has worked his magic again and the VMB1TS appears to be working correctly now

Please stop openHAB2

Run the update-velbus-jar-dev.sh script

start openHAB2

double check in Karaf that there is only the latest version running

openhab-cli console

bundle:list | grep elbus

If you have any other bundle versions loaded, just remove them

 bundle:uninstall {NUMBER}

Please let us know how you get on

bouwkarolinemaarten · January 8, 2020, 10:40pm

Dear MDAR & Cedric,
Thank you very much for the successful development of the integration of the 1TS module
Initial tests are looking great, working like a charm.

Note to all: I purchased the velbus system back in 2009 (yes 11 years ago). Interesting to see all modules are still backwards compatible and even new developments are made for this older module.
That’s what I call a perfect service and I never regret my good decision to select Velbus.
I hope this convinces new buyers as well !

Kind Regards,
Maarten

Join · January 11, 2020, 8:16pm

Hi,
My vmb1ts thermostats are working in openhab, but since the update it looks I a have problems with the connection with velbuslink and openahab at the same time, I’m loosing modules or it takes very long time to detect them in velbuslink and in openhab. Is somebody have the same?

bouwkarolinemaarten · January 11, 2020, 10:50pm

Hi,

I don’t think this is related with the upgrade. If you are using Velserv to be able to use both VelbusLink and OpenHab, I think this is the issue (also others have similar issues). I’m using the direct (serial/COM) connection as I also experience desync status updates. (of course with limitation that I only use OpenHab)

@MDAR, I was trying to get your temperature widgets working, the original one VelbusThermostat.widget.json works partly (actual temperature doesn’t show), the updated version I can’t get to work out of the box (VelbusThermostatStreamlined.widget.json)
Do you have it working with you with the 1TS module?

Thx,
Maarten

Join · January 11, 2020, 11:17pm

The problem appeared since the vmb1ts are recognized.
Before it was working perfect with velserv, openhab and nodered on the same pi.
I tried a fresh setup this evening and everything worked till…I updated the binding…

MDAR · January 12, 2020, 8:30pm

Hi @Join

As you’re using the development version of Cédric’s binding, would you be kind enough to give your feedback on his GitHub site ?

https://github.com/cedricboon/openhab2-addons/issues

MDAR · January 12, 2020, 8:31pm

Hello Maarten,

You should be able to get the widget working, it’s normally not much more than an Item name issue.
Can you double check with the text file in the zip ?

I suspect your Current Temperature Item has either the wrong name, or it’s a Number:Temperature, rather than a basic Number.

(FYI, don’t forget that you can link multiple Items to a Thing channel, if you want to try different spellings etc)

Good luck,

Stuart

Join · January 12, 2020, 9:08pm

@bouwkarolinemaarten
Is the normal knob working with the the vmb1ts ?
My settings:

MDAR · January 13, 2020, 9:08am

Another thought

Have you checked that only 1 binding version is registered in Karaf?
(Sometimes, just deleting the jar file leaves an artifact in Karaf)

Try this command in the Karaf console

bundle:list | grep elbus

Then delete / uninstall older versions of the binding

(As per instructions earlier in this thread, comment No 189)

bouwkarolinemaarten · January 14, 2020, 6:50pm

Hi,
Sorry for the screenshots, but I don’t see the “knopinstellingen”
Also not 100% sure i’m using the latest VelbusThermostatStreamlined.widget.json (note, I also didn’t “load” the Widget_Ani.gif). I’m pretty sure i’m doing something wrong but I don’t see immediately what is incorrect. Currently I only see the background / ref right block in first screenshot
the original module is functioning fine except current temperature is not showing based on default item names.
Any ideas based on below screenshots? (note testing both versions)

Thanks a lot,
Maarten

MDAR · January 14, 2020, 10:00pm

Hi

This is a good example of why I don’t use text files.

What’s wrong with adding Items from PaperUI?

Can you paste your VMB1TS Thermostat items (in text) on here?

I’ll have a good look and see if I can work out what’s happening…

MDAR · January 15, 2020, 1:45pm

My humblest apologies, there was a big (repeated) typo in the Widget that meant the Mode temperatures weren’t shown.

I’ve also changed the Default version so that _Input_Temperature is used, rather than _CurrentTemperature

I’ve updated the Widgets and uploaded a replacement ZIP to my site.

http://www.mdar.co.uk/dl/forum_assets//VelbusThermostatStreamlined.widget.zip

There is also a folder of Screen grabs to show the construction of the Items in PaperUI.

Widget_Ani.gif is / was just an animation of the older screen grabs and is nothing to do with the Widget.

It might be quicker to directly edit the widget directly within HabPanel (“Manage widgets”), rather than try to remove them and import these new versions.

The advantage of editing the widget is two fold…

You’ll see how they are constructed
Your edits will be reflected directly into any used copies of the widget and work straight away.

For reference, here are snippets of code from each widget so you can see how the Item names are used and see the changes I’ve made.

StreamLined Item Names

  <div ng-init="
    OperatingMode= config.ThermostatThingName + '_ThermostatOperatingMode';
    ThermostatMode= config.ThermostatThingName + '_ThermostatMode';
    heat_relay= config.ThermostatThingName + '_HeatingRelay';
    cool_relay= config.ThermostatThingName + '_CoolingRelay';
    CurrentTemperature= config.ThermostatThingName + '_CurrentTemperature';
    CurrentTTemperature= config.ThermostatThingName + '_CurrentTargetTemperature';
    HATTemperature= config.ThermostatThingName + '_HeatingAntifrostTarget';
    HNTTemperature= config.ThermostatThingName + '_HeatingNightTarget';
    HDTTemperature= config.ThermostatThingName + '_HeatingDayTarget';
    HCTTemperature= config.ThermostatThingName + '_HeatingComfortTarget';
    CSTTemperature= config.ThermostatThingName + '_CoolingSafeTarget';
    CNTTemperature= config.ThermostatThingName + '_CoolingNightTarget';
    CDTTemperature= config.ThermostatThingName + '_CoolingDayTarget';
    CCTTemperature= config.ThermostatThingName + '_CoolingComfortTarget'
            "</div>

Default Names

 <div ng-init="
    OperatingMode= config.ThermostatThingName + '_Thermostat_OperatingMode';
    ThermostatMode= config.ThermostatThingName + '_Thermostat_Mode';
    heat_relay= config.ThermostatThingName + '_HeatingRelay';
    cool_relay= config.ThermostatThingName + '_CoolingRelay';
    CurrentTemperature= config.ThermostatThingName + '_Input_Temperature'; <!...........For clarify this has been changed from _CurrentTemperature to _Input_Temperature .......... >
    CurrentTTemperature= config.ThermostatThingName + '_Thermostat_CurrentTemperatureSetpoint';
    HATTemperature= config.ThermostatThingName + '_Thermostat_HeatingModeAntifrostTemperatureSetpoint';
    HNTTemperature= config.ThermostatThingName + '_Thermostat_HeatingModeNightTemperatureSetpoint';
    HDTTemperature= config.ThermostatThingName + '_Thermostat_HeatingModeDayTemperatureSetpoint';
    HCTTemperature= config.ThermostatThingName + '_Thermostat_HeatingModeComfortTemperatureSetpoint';
    CSTTemperature= config.ThermostatThingName + '_Thermostat_CoolingModeSafeTemperatureSetpoint';
    CNTTemperature= config.ThermostatThingName + '_Thermostat_CoolingModeNightTemperatureSetpoint';
    CDTTemperature= config.ThermostatThingName + '_Thermostat_CoolingModeDayTemperatureSetpoint';
    CCTTemperature= config.ThermostatThingName + '_Thermostat_CoolingModeComfortTemperatureSetpoint'
            "</div>

bouwkarolinemaarten · January 16, 2020, 10:16pm

Hi MDAR,
Working fine ! Thanks a lot again.

Still happy with my items file to manage the +500 variables (a bit challenging with the PAPER UI)
as example …

Number Bureau_CurrentTemperature {channel=“velbus:vmb1ts:003e088b:99:input#CH1”}
Number Bureau_CurrentTargetTemperature {channel=“velbus:vmb1ts:003e088b:99:thermostat#CURRENTTEMPERATURESETPOINT”}

Number Bureau_HeatingComfortTarget {channel=“velbus:vmb1ts:003e088b:99:thermostat#HEATINGMODECOMFORTTEMPERATURESETPOINT”}

Number Bureau_HeatingDayTarget {channel=“velbus:vmb1ts:003e088b:99:thermostat#HEATINGMODEDAYTEMPERATURESETPOINT”}

Number Bureau_HeatingNightTarget {channel=“velbus:vmb1ts:003e088b:99:thermostat#HEATINGMODENIGHTTEMPERATURESETPOINT”}

Number Bureau_HeatingAntifrostTarget {channel=“velbus:vmb1ts:003e088b:99:thermostat#HEATINGMODEANTIFROSTTEMPERATURESETPOINT”}

Number Bureau_CoolingComfortTarget {channel=“velbus:vmb1ts:003e088b:99:thermostat#COOLINGMODECOMFORTTEMPERATURESETPOINT”}

Number Bureau_CoolingDayTarget {channel=“velbus:vmb1ts:003e088b:99:thermostat#COOLINGMODEDAYTEMPERATURESETPOINT”}

Number Bureau_CoolingNightTarget {channel=“velbus:vmb1ts:003e088b:99:thermostat#COOLINGMODENIGHTTEMPERATURESETPOINT”}

Number Bureau_CoolingSafeTarget {channel=“velbus:vmb1ts:003e088b:99:thermostat#COOLINGMODESAFETEMPERATURESETPOINT”}

String Bureau_ThermostatOperatingMode {channel=“velbus:vmb1ts:003e088b:99:thermostat#OPERATINGMODE”}

String Bureau_ThermostatMode {channel=“velbus:vmb1ts:003e088b:99:thermostat#MODE”}

Switch Bureau_HeatingRelay {channel=“velbus:vmb4ry:F0_BU_VB_VSB_SerialBridge:11:CH3”}

Switch Bureau_CoolingRelay {channel=“opendaikin:ac_unit:192_168_0_212:power”}

Join · January 19, 2020, 12:18pm

Hi Mdar, can you tell me what I have to fill in the settings of the widget ?

or can you make a small manual ?
Thanks, Johan

MDAR · January 19, 2020, 4:11pm

Hi

Have you read the text file in that Zip ??

It all revolves around a naming convention with the required Items.

Just for information, I have edited the Widget, so please download it again and use the new version (without the Typos)

If you look closely at Marteen’s post above, you’ll see the pattern in the Items he is using.

Cheers,

Stuart