Support for Velbus Home Automation


#1

Hi,

Would it be possible to add support for the Velbus Home Automation system in Home Assistant?
The protocol sheets are available on their site and integration in your product would surely mean a great addition for myself and other users.

http://www.velbus.eu/domotica

Thank you,

Tom


#2

I am also curious if it would be possible to get Home Assistant to work with Velbus.

I found some information on sending data to the Velbus (a CAN-Bus like implementation) via JAVA, but while I am skilled enough to do everything I need to with Home Assistant, I have no clue how to translate the Java stuff to something usable in Home Assistant…
There is a download of the Library (Jvelbus) here and on the same page under “Wiki” there is some basic info…

Perhaps it is easy to “port” this stuff,…


#3

I’ve created a python-velbus library a while ago https://pypi.python.org/pypi/python-velbus/1.0 and would be interested in integrating velbus in home assistant. Care to collaborate?


#4

I have no Velbus system of my own, one of my friends has it installed though.
I was reading this and I thought that it could make integrating your previous work with Home Assistant easier.

I have no idea if it would be feasible, but perhaps it would be possible to add MQTT, it would allow Home Assistant, and with that also many others to read/interact with Velbus.


#5

In the mean time, Velbus support is integrated in latest version ;-).


#6

Hello Thomas, I am experiencing an issue with component Velbus during inital installation of Home Assistant. I followed the instructions on page https://home-assistant.io/components/velbus/ and updated the configuration.yaml file accordingly. Hassio returns following error after reboot:

2017-08-27 16:25:48 ERROR (SyncWorker_7) [velbus] Could not open serial port, no messages are read or written to the bus
2017-08-27 16:25:48 ERROR (MainThread) [homeassistant.setup] Error during setup of component velbus
Traceback (most recent call last):
File “/usr/lib/python3.6/site-packages/serial/serialposix.py”, line 244, in op en
self.fd = os.open(self.portstr, os.O_RDWR | os.O_NOCTTY | os.O_NONBLOCK)
FileNotFoundError: [Errno 2] No such file or directory: '/dev/ttyUSB00

Are you sure the device is called /dev/ttyUSB00 ??? Shouldn’t it be /dev/ttyACM00 ???
What will happen once this is fixed? Will the Hassio automatically detect all devices on the velbus? Or do I have to configure all of it manually?

I am running velbus components since 2008. Most of them are the older modules (first generation) such as VMB4RY, VMB4PD, VMB1BL, VMB2BL, VMB6IN, VMB8PB and a few more recent ones such as VMBGP4PIRW, VMBDME, VMB4RYNO.

Thank you,
GiGi


#7

Hello Thomas, I have the module VMB1USB in my velbus topology at home. When changing the configuration.yaml with the following (see last lines here below):

Text to speech

tts:

  • platform: google

group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml

velbus:
port: '/dev/ttyACM0’
core-ssh:~#

I did a reboot and still get the error. Here is the export of the command dmesg

0.243468] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.498335] hw perfevents: enabled with armv7_cortex_a7 PMU driver, 7 counters available
[ 0.499687] futex hash table entries: 1024 (order: 4, 65536 bytes)
[ 0.512815] VFS: Disk quotas dquot_6.6.0
[ 0.513117] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 0.515013] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 0.515496] FS-Cache: Netfs ‘nfs’ registered for caching
[ 0.516361] NFS: Registering the id_resolver key type
[ 0.516401] Key type id_resolver registered
[ 0.516410] Key type id_legacy registered
[ 0.518099] aufs 4.4-20170703
[ 0.519490] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
[ 0.519606] io scheduler noop registered
[ 0.519622] io scheduler deadline registered
[ 0.519669] io scheduler cfq registered (default)
[ 0.522188] BCM2708FB: allocated DMA memory fdc10000
[ 0.522214] BCM2708FB: allocated DMA channel 0 @ f3007000
[ 0.527331] Console: switching to colour frame buffer device 82x26
[ 0.604570] bcm2835-rng 3f104000.rng: hwrng registered
[ 0.604686] vc-cma: Videocore CMA driver
[ 0.604695] vc-cma: vc_cma_base = 0x00000000
[ 0.604704] vc-cma: vc_cma_size = 0x00000000 (0 MiB)
[ 0.604712] vc-cma: vc_cma_initial = 0x00000000 (0 MiB)
[ 0.604921] vc-mem: phys_addr:0x00000000 mem_base=0x3ea00000 mem_size:0x3f000000(1008 MiB)
[ 0.619404] brd: module loaded
[ 0.628020] loop: module loaded
[ 0.628894] vchiq: vchiq_init_state: slot_zero = 0xbdc80000, is_master = 0
[ 0.630271] Loading iSCSI transport class v2.0-870.
[ 0.630820] tun: Universal TUN/TAP device driver, 1.6
[ 0.630830] tun: © 1999-2004 Max Krasnyansky [email protected]
[ 0.631127] usbcore: registered new interface driver smsc95xx
[ 0.631179] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
[ 0.831457] Core Release: 2.80a
[ 0.831469] Setting default values for core params
[ 0.831498] Finished setting default values for core params
[ 1.031825] Using Buffer DMA mode
[ 1.031835] Periodic Transfer Interrupt Enhancement - disabled
[ 1.031843] Multiprocessor Interrupt Enhancement - disabled
[ 1.031852] OTG VER PARAM: 0, OTG VER FLAG: 0
[ 1.031866] Dedicated Tx FIFOs mode
[ 1.032152] WARN::dwc_otg_hcd_init:1047: FIQ DMA bounce buffers: virt = 0xbdc04000 dma = 0xfdc04000 len=9024
[ 1.032181] FIQ FSM acceleration enabled for :
[ 1.032181] Non-periodic Split Transactions
[ 1.032181] Periodic Split Transactions
[ 1.032181] High-Speed Isochronous Endpoints
[ 1.032181] Interrupt/Control Split Transaction hack enabled
[ 1.032203] dwc_otg: Microframe scheduler enabled
[ 1.032244] WARN::hcd_init_fiq:415: FIQ on core 1 at 0x804804d0
[ 1.032257] WARN::hcd_init_fiq:416: FIQ ASM at 0x80480830 length 36
[ 1.032271] WARN::hcd_init_fiq:441: MPHI regs_base at 0xbe87e000
[ 1.032328] dwc_otg 3f980000.usb: DWC OTG Controller
[ 1.032363] dwc_otg 3f980000.usb: new USB bus registered, assigned bus number 1
[ 1.032397] dwc_otg 3f980000.usb: irq 62, io mem 0x00000000
[ 1.032448] Init: Port Power? op_state=1
[ 1.032455] Init: Power Port (0)
[ 1.032653] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 1.032668] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.032680] usb usb1: Product: DWC OTG Controller
[ 1.032692] usb usb1: Manufacturer: Linux 4.4.50 dwc_otg_hcd
[ 1.032703] usb usb1: SerialNumber: 3f980000.usb
[ 1.033385] hub 1-0:1.0: USB hub found
[ 1.033434] hub 1-0:1.0: 1 port detected
[ 1.034003] dwc_otg: FIQ enabled
[ 1.034012] dwc_otg: NAK holdoff enabled
[ 1.034020] dwc_otg: FIQ split-transaction FSM enabled
[ 1.034049] Module dwc_common_port init
[ 1.034295] usbcore: registered new interface driver usb-storage
[ 1.034515] mousedev: PS/2 mouse device common for all mice
[ 1.035180] bcm2835-cpufreq: min=600000 max=1200000
[ 1.040228] sdhci: Secure Digital Host Controller Interface driver
[ 1.040233] sdhci: Copyright© Pierre Ossman
[ 1.040385] sdhost: log_buf @ bdc07000 (fdc07000)
[ 1.093813] mmc0: sdhost-bcm2835 loaded - DMA enabled (>1)
[ 1.095844] mmc-bcm2835 3f300000.mmc: mmc_debug:0 mmc_debug2:0
[ 1.095850] mmc-bcm2835 3f300000.mmc: DMA channel allocated
[ 1.153857] sdhci-pltfm: SDHCI platform and OF driver helper
[ 1.154053] ledtrig-cpu: registered to indicate activity on CPUs
[ 1.154115] hidraw: raw HID events driver © Jiri Kosina
[ 1.154206] usbcore: registered new interface driver usbhid
[ 1.154210] usbhid: USB HID core driver
[ 1.154404] nf_conntrack version 0.5.0 (15500 buckets, 62000 max)
[ 1.155222] ip_tables: © 2000-2006 Netfilter Core Team
[ 1.155313] Initializing XFRM netlink socket
[ 1.156010] NET: Registered protocol family 10
[ 1.156636] NET: Registered protocol family 17
[ 1.156669] bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this.
[ 1.156726] Key type dns_resolver registered
[ 1.156956] Registering SWP/SWPB emulation handler
[ 1.157389] registered taskstats version 1
[ 1.157487] vc-sm: Videocore shared memory driver
[ 1.157494] [vc_sm_connected_init]: start
[ 1.157618] vc_vchi_sm_init: failed to open VCHI service (-1)
[ 1.157624] [vc_sm_connected_init]: failed to initialize shared memory service
[ 1.157629] [vc_sm_connected_init]: end - returning -1
[ 1.158783] 3f201000.uart: ttyAMA0 at MMIO 0x3f201000 (irq = 87, base_baud = 0) is a PL011 rev2
[ 1.158998] of_cfs_init
[ 1.159043] of_cfs_init: OK
[ 1.159376] Warning: unable to open an initial console.
[ 1.161889] Freeing unused kernel memory: 3528K (808c4000 - 80c36000)
[ 1.193679] mmc0: host does not support reading read-only switch, assuming write-enable
[ 1.197275] mmc0: new high speed SDHC card at address e624
[ 1.198282] mmcblk0: mmc0:e624 SS16G 14.8 GiB
[ 1.205048] mmcblk0: p1 p2 p3 p4 < p5 p6 >
[ 1.223270] mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
[ 1.223953] Indeed it is in host mode hprt0 = 00021501
[ 1.224829] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[ 1.226352] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[ 1.229118] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
[ 1.321945] mmc1: new high speed SDIO card at address 0001
[ 1.403899] usb 1-1: new high-speed USB device number 2 using dwc_otg
[ 1.404076] Indeed it is in host mode hprt0 = 00001101
[ 1.604293] usb 1-1: New USB device found, idVendor=0424, idProduct=9514
[ 1.604314] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1.605232] hub 1-1:1.0: USB hub found
[ 1.605336] hub 1-1:1.0: 5 ports detected
[ 1.657076] udevd[328]: starting version 230
[ 1.659712] random: udevd: uninitialized urandom read (16 bytes read, 47 bits of entropy available)
[ 1.660198] random: udevd: uninitialized urandom read (16 bytes read, 47 bits of entropy available)
[ 1.660357] random: udevd: uninitialized urandom read (16 bytes read, 47 bits of entropy available)
[ 1.660506] random: udevd: uninitialized urandom read (16 bytes read, 47 bits of entropy available)
[ 1.665887] random: udevadm: uninitialized urandom read (16 bytes read, 48 bits of entropy available)
[ 1.666163] random: udevadm: uninitialized urandom read (16 bytes read, 48 bits of entropy available)
[ 1.666283] random: udevadm: uninitialized urandom read (16 bytes read, 48 bits of entropy available)
[ 1.666701] random: udevadm: uninitialized urandom read (16 bytes read, 48 bits of entropy available)
[ 1.667110] random: udevadm: uninitialized urandom read (16 bytes read, 48 bits of entropy available)
[ 1.667536] random: udevadm: uninitialized urandom read (16 bytes read, 48 bits of entropy available)
[ 1.883889] usb 1-1.1: new high-speed USB device number 3 using dwc_otg
[ 1.984120] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00
[ 1.984141] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1.987206] smsc95xx v1.0.4
[ 2.047662] smsc95xx 1-1.1:1.0 eth0: register ‘smsc95xx’ at usb-3f980000.usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:5e:a3:c7
[ 2.725239] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[ 2.780776] EXT4-fs (mmcblk0p5): recovery complete
[ 2.782186] EXT4-fs (mmcblk0p5): mounted filesystem with ordered data mode. Opts: (null)
[ 3.063853] usb 1-1.5: new full-speed USB device number 4 using dwc_otg
[ 3.116427] systemd[1]: System time before build time, advancing clock.
[ 3.158445] systemd[1]: systemd 230 running in system mode. (-PAM -AUDIT -SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP -LIBCRYPTSETUP -GCRYPT +GNUTLS +ACL +XZ -LZ4 -SECCOMP +BLKID -ELFUTILS +KMOD -IDN)
[ 3.158963] systemd[1]: Detected architecture arm.
[ 3.163657] systemd[1]: Set hostname to .
[ 3.169652] usb 1-1.5: New USB device found, idVendor=10cf, idProduct=0b1b
[ 3.169670] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 3.169683] usb 1-1.5: Product: VMB1USB Velbus USB interface
[ 3.169695] usb 1-1.5: Manufacturer: Velleman Projects
[ 3.510180] systemd[1]: brcm43438.service: Cannot add dependency job, ignoring: Unit brcm43438.service is masked.
[ 3.514581] systemd[1]: Listening on udev Kernel Socket.
[ 3.530770] systemd[1]: Listening on udev Control Socket.
[ 3.531007] systemd[1]: Listening on Syslog Socket.
[ 3.531113] systemd[1]: Reached target Login Prompts.
[ 3.531376] systemd[1]: Listening on Journal Socket.
[ 3.531747] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[ 3.533469] systemd[1]: Created slice User and Session Slice.
[ 3.533664] systemd[1]: Listening on Journal Socket (/dev/log).
[ 3.533763] systemd[1]: Reached target Swap.
[ 3.534113] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
[ 3.534216] systemd[1]: Reached target Remote File Systems.
[ 3.534848] systemd[1]: Created slice System Slice.
[ 3.564160] systemd[1]: Mounting Temporary Directory…
[ 3.567191] systemd[1]: Mounting POSIX Message Queue File System…
[ 3.582371] systemd[1]: Starting Journal Service…
[ 3.582606] systemd[1]: Reached target Slices.
[ 3.586174] systemd[1]: Starting Setup Virtual Console…
[ 3.589573] systemd[1]: Mounting Configuration File System…
[ 3.594484] systemd[1]: Mounting Debug File System…
[ 3.600715] systemd[1]: Starting Apply Kernel Variables…
[ 3.608160] systemd[1]: Starting Remount Root and Kernel File Systems…
[ 3.616923] systemd[1]: Starting Create list of required static device nodes for the current kernel…
[ 3.635875] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[ 3.635995] systemd[1]: Mounted Configuration File System.
[ 3.636252] systemd[1]: Mounted Debug File System.
[ 3.636469] systemd[1]: Mounted POSIX Message Queue File System.
[ 3.636650] systemd[1]: Mounted Temporary Directory.
[ 3.659806] systemd[1]: Started Setup Virtual Console.
[ 3.661234] systemd[1]: Started Apply Kernel Variables.
[ 3.662200] systemd[1]: Started Remount Root and Kernel File Systems.
[ 3.663151] systemd[1]: Started Create list of required static device nodes for the current kernel.
[ 3.675460] systemd[1]: Starting udev Coldplug all Devices…
[ 3.682060] systemd[1]: Starting Create Static Device Nodes in /dev…
[ 3.700315] systemd[1]: Started Journal Service.
[ 4.245004] bcm2835-wdt 3f100000.watchdog: Broadcom BCM2835 watchdog timer
[ 4.284937] bcm2708_i2c 3f804000.i2c: BSC1 Controller at 0x3f804000 (irq 83) (baudrate 100000)
[ 4.320522] gpiomem-bcm2835 3f200000.gpiomem: Initialised: Registers at 0x3f200000
[ 4.680708] cdc_acm 1-1.5:1.0: ttyACM0: USB ACM device
[ 4.681677] usbcore: registered new interface driver cdc_acm
[ 4.681693] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[ 4.971860] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 5.021064] usbcore: registered new interface driver brcmfmac
[ 5.146509] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Aug 29 2016 20:48:16 version 7.45.41.26 (r640327) FWID 01-4527cfab
[ 5.165338] cfg80211: World regulatory domain updated:
[ 5.165361] cfg80211: DFS Master region: unset
[ 5.165370] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[ 5.165385] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[ 5.165399] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz, 92000 KHz AUTO), (N/A, 2000 mBm), (N/A)
[ 5.165411] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
[ 5.165424] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
[ 5.165438] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
[ 5.165451] cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
[ 5.165462] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
[ 5.165474] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
[ 5.167555] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code
[ 8.016427] random: nonblocking pool is initialized
[ 8.388975] i2c /dev entries driver
[ 8.408918] brcmfmac: power management disabled
[ 9.694374] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 9.756144] smsc95xx 1-1.1:1.0 eth0: hardware isn’t capable of remote wakeup
[ 9.756526] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 9.784055] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 9.823192] brcmfmac: brcmf_add_if: ERROR: netdev:wlan0 already exists
[ 9.823218] brcmfmac: brcmf_add_if: ignore IF event
[ 9.829259] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 9.829300] brcmfmac: power management disabled
[ 10.350699] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 10.350723] brcmfmac: power management disabled
[ 10.642210] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 11.278967] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 11.279943] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[ 11.682242] EXT4-fs (mmcblk0p6): mounted filesystem with ordered data mode. Opts: (null)
[ 15.368930] aufs au_opts_verify:1606:dockerd[804]: dirperm1 breaks the protection by the permission bits on the lower branch
[ 15.652119] Bridge firewalling registered
[ 16.071017] IPv6: ADDRCONF(NETDEV_UP): docker0: link is not ready
[ 16.264218] IPv6: ADDRCONF(NETDEV_UP): hassio: link is not ready
[ 20.095809] device vethff05f30 entered promiscuous mode
[ 20.096263] IPv6: ADDRCONF(NETDEV_UP): vethff05f30: link is not ready
[ 20.205729] device veth28e1f8d entered promiscuous mode
[ 20.206620] IPv6: ADDRCONF(NETDEV_UP): veth28e1f8d: link is not ready
[ 20.206645] hassio: port 1(veth28e1f8d) entered forwarding state
[ 20.206723] hassio: port 1(veth28e1f8d) entered forwarding state
[ 20.210712] hassio: port 1(veth28e1f8d) entered disabled state
[ 21.085620] eth0: renamed from veth4b3f362
[ 21.125320] IPv6: ADDRCONF(NETDEV_CHANGE): vethff05f30: link becomes ready
[ 21.125426] docker0: port 1(vethff05f30) entered forwarding state
[ 21.125486] docker0: port 1(vethff05f30) entered forwarding state
[ 21.125638] IPv6: ADDRCONF(NETDEV_CHANGE): docker0: link becomes ready
[ 21.486683] eth1: renamed from vethba26889
[ 21.526353] IPv6: ADDRCONF(NETDEV_CHANGE): veth28e1f8d: link becomes ready
[ 21.526494] hassio: port 1(veth28e1f8d) entered forwarding state
[ 21.526586] hassio: port 1(veth28e1f8d) entered forwarding state
[ 21.526920] IPv6: ADDRCONF(NETDEV_CHANGE): hassio: link becomes ready
[ 32.773999] device vethf466cab entered promiscuous mode
[ 32.775500] IPv6: ADDRCONF(NETDEV_UP): vethf466cab: link is not ready
[ 34.145693] eth0: renamed from veth57d1a0f
[ 34.185769] IPv6: ADDRCONF(NETDEV_CHANGE): vethf466cab: link becomes ready
[ 34.185916] hassio: port 2(vethf466cab) entered forwarding state
[ 34.186004] hassio: port 2(vethf466cab) entered forwarding state
[ 36.143826] docker0: port 1(vethff05f30) entered forwarding state
[ 36.543823] hassio: port 1(veth28e1f8d) entered forwarding state
[ 40.042983] udevd[9]: starting version 3.2.2
[ 40.059756] udevd[9]: starting eudev-3.2.2
[ 49.223866] hassio: port 2(vethf466cab) entered forwarding state
[ 352.550558] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 352.550612] brcmfmac: power management disabled
core-ssh:~#

Kind regards,
Geert


#8

Hah, I didn’t notice, and I had not had my coffee yet. Thx for the reply. Passing it on to my friend to give it a try!


#9

Hello, do you or Thomas have any update? Regards, Geert


#10

Wow. Just wow Thomas!

Thanks for your hard work. I’ve just made the switch back to Home Assistant all thanks to your effort.
Finally I can use my Velbus modules which make up an important part of my automated home.

Lights seem to work perfectly, but I’m having some trouble with other modules/functions.
My blinds (VMB2BLE/VMB1BL) don’t seem to work, I’ve tried multiple options (switch, binary_sensor and cover). However for the cover I cannot find the corresponding information page (seems like the link is incorrect) so perhaps I just did not use it correctly.

I certainly want to help you however I can if you like to further develop this. Seems to me there is still a lot of potential. I’ll look into your code and see if I can grasp it, but I’m not as fluent as I would like to be.

In any case. Thanks for all the stuff you already made happen and hopefully we can’t improve it further in this community.

Kind regards,

Tom


#11

Hi gents, are dimmers supported?


#12

Does anyone have this up and running? Can’t get it to work. When I use a light switch. It seems it doesnt read the state


#13

Hi Geert,

My lights on relays VMB4RYNO and VMB4RYLD work as expected.
I don’t have any dimmers so can’t help you there.

Tom


#14

Would there we someone able to integrate Velbus at the fullest?


#15

With the latest release of python velbus we added support for some new message formats.
I have some dev code ready that support temperature sensors, and the counters (vmb7in) as a sensor in HA.
The next step will be to implement shutters and dimmers.

With the new version we can also connect to velbus over a socket connection, this makes it possible to connect HA and velbuslink or other tools to the same velbus install.


#16

Cool. I am willing to test if needed. What would be cool is to have thermostat support available.

currently I use a velserv ip to usb gateway.


#17

Geert here i also use the velserv.

What exact module do you want to see implented?
I’m currently working on the vmbgpod modules.


#18

cool. I have the glass panels . OLED 4 switch. The single panel. VMBDMI and the relays. The PIR sensor is also available but I don’t think much integration is needed on that device.


#20

Hi all,
Can anyone tell me how to configure velbus in hassio 0.77.3?

The Velbus component as previously defined (https://www.home-assistant.io/components/velbus/), doesn’t work anymore.
I just have the following line:
velbus:
port: ‘/dev/ttyACM0’

I read in earlier release notes that just the component should be added, after which the modules would be discovered.

I could revert back to 0.69, but I would very much like to make use of the latest integrations (PIR, temperature).

Can anyone please show me what I’m missing here? The documentation of the component doesn’t seem to be valid anymore.
TIA


#21

There is very poor support for velbus. Dont bother. Check openhab is you need velbus. I have been trying to get support for velbus but no one seem te be interested