Sorry about the Typo, I’ll correct that right now.
Although I have used that script on loads of machines and it hasn’t failed, so I’ll look closely
(I can’t find the typo, did you cut and paste the command line, or type it in?)
(are you not going to use VelServ and a Velbus Network bridge, so that you can connect VelbusLink whenever you wish?)
I would strongly recommend NOT creating Things in Text files, but instead allow PaperUI to create them from the Inbox. (Over write the Bridge ID with something of your choosing, so that you can move everything to a new machine / setup easily)
Another reason being that it is far too easy to make a mistake with a Thing file and when you get to adding glass panels there are WAY too many channels, so you’ll be fighting syntax errors for hours and hours.
Then… should the binding get updated and add new functionality, it is very easy to delete the Thing in PaperUI and add it again. (you might only need to tweak the Item files to suit, which is super easy in NotePad++)
(if the Velbus device doesn’t appear in the Inbox, then there is something else wrong)
Then you can create all the Items you need in Text files and add the Alexa / Google metadata as you need.
I’ve even create a template Items file, along with some useful HabPanel widgets. (The thermostat widget was created by @tomvancutsem)
They are all in this ZIP - openhab_items_template.zip
There is a VelbusBridge.thing in the zip
It looks like this, just comment out what you don’t need
// Please note that I have not tested the USB port access bridges in this file.
//
// The Bridge (internal) name is also the same for each, so that they can be interachanged without having to edit other files (*.items and *.rules for example)
// Network bridge, for use with TCP servers like Velserv, Velbus_PB_Server or the upcoming Velbus TCP gateway. Running on the same machine
Bridge velbus:networkbridge:VelbusNetworkBridge "Velbus Network Bridge - Loopback" @ "Loft" [ address="127.0.0.1", port=6000 ]
// Network bridge, for use with TCP servers like Velserv, Velbus_PB_Server or the upcoming Velbus TCP gateway, running on a different machine on your LAN
// Bridge velbus:networkbridge:VelbusNetworkBridge "Velbus Network Bridge - at 192.168.0.100" @ "Control" [ address="192.168.0.100", port=6000 ]
// USB bridge for use on Linux with symlink ttyACM0
// Bridge velbus:bridge:VelbusBridge "Velbus USB / RS232 Bridge - ttyACM0" @ "Control" [ port="/dev/ttyACM0" ]
// USB bridge for use with Windows, using Com5
// Bridge velbus:bridge:VelbusBridge "Velbus USB / RS232 Bridge - Com5" @ "Control" [ port="com5" ]
)
