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)
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
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 !
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?
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?
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…
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)
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)
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.
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”}
Again special thx to MDAR & Cedric and all team for the great developments. Happy to share the current (end) result and topic of VB1TS
For the interested people, best to search for following keywords on OpenHAB
(dynamic icons in standard dummy widget, influx db and grafana)
If you are up for additional challenges, I still have something on my wishlist that we can maybe extend for all future/add hoc requests. Not sure if even possible or potentially it’s already available in some kind of debug/logging mode, but i’m looking for: "I/O module - full passthrough of all packets send/received through the Velbus Serial Bridge"
I’m not so familiar with serial communication protocols and running multiple applications on a same serial port is challenging as well, so would like to keep Cedric Velbus Serial Bridge on the Serial Port /dev/ttyACM0 (/dev/ttyACM0) dedicated.
Goal/purpose is something like the Logging (Pakketmonitor) from VelbusLink, not for troubleshooting purpose, but to capture or send very specific events from my Velbus setup.
A basic interpreter like address, protocol splitter might be helpful, but optional
I was thinking about a basic string variable that you guys overwrite on every incoming event (+post in openHAB 2 Log Viewer and same to “send” a custom build string from a customer “rule”.
(of course with a note: be careful what you send as we are now working directly on the bus communication)
Of course if this will bring down stability of any component (too much events), happy to skip this request as I’m also interested in the low priority packets.
Use cases what I have in mind:
Basic support for VMB4PD to capture CH1 -> CH8 PRESSED/LONG_PRESSED/RELEASED events
something similar as the inputchannel events:
2020-01-26 20:04:58.958 [vent.ChannelTriggeredEvent] - velbus:vmb8pbu:F0_BU_VB_VSB_SerialBridge:2B:input#CH1 triggered PRESSED
2020-01-26 20:04:59.784 [vent.ChannelTriggeredEvent] - velbus:vmb8pbu:F0_BU_VB_VSB_SerialBridge:2B:input#CH1 triggered LONG_PRESSED
2020-01-26 20:05:00.010 [vent.ChannelTriggeredEvent] - velbus:vmb8pbu:F0_BU_VB_VSB_SerialBridge:2B:input#CH1 triggered RELEASED
VMB1TC module is currently controlling the VMB1TS modules.
Next to the button events (ref above), it would be interesting if I can set some kind of holiday schedule through velbus. Like “overwrite” or “block/stop” the program during a period when the normal schedule is not valid (holidays). Note, I never got this to work properly with the module itself.
Alternatively I can also work with rules reacting on events to “force to NIGHT” during holiday, but this is a bit suboptimal.
2020-01-26 20:08:17.721 [vent.ItemStateChangedEvent] - F0_SA_VB_1TS94_ThermostatMode changed from COMFORT to SAFE
2020-01-26 20:08:17.731 [vent.ItemStateChangedEvent] - F0_SA_VB_1TS94_CurrentTargetTemperature changed from 24.0 to 5.0
2020-01-26 20:08:18.291 [vent.ItemStateChangedEvent] - F0_SA_VB_1TS94_ThermostatMode changed from SAFE to NIGHT
2020-01-26 20:08:18.294 [vent.ItemStateChangedEvent] - F0_SA_VB_1TS94_CurrentTargetTemperature changed from 5.0 to 15.0
2020-01-26 20:08:18.804 [vent.ItemStateChangedEvent] - F0_SA_VB_1TS94_ThermostatMode changed from NIGHT to DAY
2020-01-26 20:08:18.830 [vent.ItemStateChangedEvent] - F0_SA_VB_1TS94_CurrentTargetTemperature changed from 15.0 to 19.5