Today I installed the new binding version 2.3.0 (93kb).
To read the temperature out of a “vmbpiro” its not possible yet. The “Error 500internal server error” is gone now and it is possible to view the channels. For the “vmbpiro” there is no temperature channel.
“1.Have you removed and restored the VMBPIR module? (So that it can be reprofiled)”
Perfect, now the temp channels are available and it works.
2.May I ask why you aren’t using PaperUI to create things and link to (auto generated) items? (Instead of using .items files)
There are more possibilities, you can create groups,…
I think it’s a little bug in velbuslink.
VMBGPOD, VMBGP4, VMBPIR and VMBGP2 all giving “input” instead of (things Paper UI)
“channel=velbus:vmbgp2:956cb640:91:input#CH9”
VMBGP4PIR is the only one that gives “glasspannel”
“channel=“velbus:vmbgp4pir:956cb640:7D:glasspannel#CH9”
if you want to use openhab with other third parties like google home or alexa, you need to declare the items on the files and rules too.
personnally i dont use paper ui or habpanel, everything is voice commands and rules…
it is faster as i have almost 70 channels…
Do you guys really have time for all this. I’ve been struggling for the past month to configure my installation but the more I add the more ideas come and the more time consuming is to make it smart. I would like something hey I see you have a new blind module do you want me to set up rules … yes… ok would you like a sunset wake up to be set … sound nice yes… What openhab needs is AI. Do you guys have something like that?
Hi guys, I’m pretty new to the whole OpenHAB story.
I’m a professional Velbus installer and offcourse have Velbus installed at my home.
Last week I installed OpenHAB on a RPi 2. Most of my Velbus installation works through openHAB (with Android phone and on Windows PC) but I’m not able to use a VMB1BL, not on openHAB, and not even in PAPER UI. I had to manually add it too, as it was not found while searching for modules.
Is it possible that the VMB1BL is not included in the binding? Or am I missing something?
Thanks a lot for the binding btw, I’m in love
edit:
my Velbus installation works through openHAB
not able to use a VMB1BL, not on openHAB
Oops, I can’t believe that actually slipped my mind.
I had read the entire post and immediately downloaded the newer release, but hadn’t found the time yet to install it.
I won’t be having time the first few days, but when I install it, I will surely post a reply to let you know if it works.
Hi all,
As a new Openhab user, but early adopter of Velbus, I’m very happy I made the right decision years ago. First of all, special thanks for the great works of @cedricb enabling Velbus on OpenHAB!
Stating the obvious, but this is a real “reinvention” for me, changing from an isolated home system to limitless possibilities (a bit overwhelming).
Thousands combinations/integrations are coming at the reach of Velbus users:
OpenHAB: 328 add-ons & 1547 things
IFTT Binding: ecosystem of over 600 world-class services
MQTT Binding: machine-to-machine (M2M)/"Internet of Things"
In order to make correct design decisions, I wonder what is on the further roadmap for Velbus binding. I’m currently running version released 2019 Feb 3rd on openhab2 (on raspberry 3/Openhabian). Can you please let me know if there are plans (or potential already night releases) supporting vmb4pd, vmb1ts, vmb1tc ? Possibly with estimated timers (weeks/months?)
All output modules (for me) working 100%: vmb1dm, vmb2bl, vmb4ry, vmb4ryno
Some input modules recognized as well: vmb8pd, vmb8pbu, vmbmeteo
Original target was to use Openhab as “input”, triggering relais, but it would be nice if we can link temperature state change or the push button input module to use Openhab as “output” trigger for 3th party integrations. Alternative I can sacrifice vmb8pd inputs or if anyone has another idea as workaround? (like capture state changes directly from the Velbus)
Dear MDAR,
100% right for thing types vmbgp1 , vmbgp2 , vmbgp4 , vmbgp4pir and vmbpiro have 8 trigger channels CH1 … CH8 and one temperature channel CH9 .
But I still have/use the “old” temperature sensors vmb1ts
I hope low effort to add this to the supported sensors (or potentially I can make openhab “think/fool” I have vmbgp1 instead of vmb1ts