Support for Velbus Home Automation

BTC · September 16, 2018, 8:11am

Hi Thomas!
Yes, I checked the list of USB devices with the VMBUSB connected and without, and the ACM0 pops up when connected. It worked before (0.6x) and starting from 0.7x it doesn’t. There has to be some cause.

Thanks a lot for the info! I will take a look how to add velserv to hassio.

Cereal2nd · October 1, 2018, 3:32am

i just tried and it works here.

make sure the HA user has access to the device, on debian you need to add the HA user to the dialout group to make this work.

a quick test to see if this is your problem try:
chmod 777 /dev/ttyACM0

AlbertHakvoort · October 16, 2018, 6:49pm

Hey,

I’ve added velbus to the config, but nothing is (auto) added.

2018-10-16 20:46:01 INFO (velbus-process-reader) [velbus] New message: {“name”: “SensorTemperatureMessage”

When looking into the log I do see velbus messages…

Some extra config needed? The manual is a little bit…empty

Cereal2nd · October 17, 2018, 5:46am

the only thing i have is a port and alll my devices show up …
of course make sure you activate the switch and sensor domain in HA.

Do you see any moduleTypeRequest messages in the HA log?

AlbertHakvoort · October 17, 2018, 6:24am

2018-10-17 08:23:48 INFO (velbus-connection-writer) [velbus] Sending message on USB bus: {"name": "ModuleTypeRequestMessage", "priority": 251, "address": 238, "rtr": true}
2018-10-17 08:23:48 INFO (velbus-connection-writer) [velbus] Sending message on USB bus: {"name": "ModuleTypeRequestMessage", "priority": 251, "address": 239, "rtr": true}
2018-10-17 08:23:48 INFO (velbus-connection-writer) [velbus] Sending message on USB bus: {"name": "ModuleTypeRequestMessage", "priority": 251, "address": 240, "rtr": true}
2018-10-17 08:23:48 INFO (velbus-connection-writer) [velbus] Sending message on USB bus: {"name": "ModuleTypeRequestMessage", "priority": 251, "address": 241, "rtr": true}
2018-10-17 08:23:48 INFO (velbus-connection-writer) [velbus] Sending message on USB bus: {"name": "ModuleTypeRequestMessage", "priority": 251, "address": 242, "rtr": true}
2018-10-17 08:23:48 INFO (velbus-connection-writer) [velbus] Sending message on USB bus: {"name": "ModuleTypeRequestMessage", "priority": 251, "address": 243, "rtr": true}
2018-10-17 08:23:48 INFO (velbus-connection-writer) [velbus] Sending message on USB bus: {"name": "ModuleTypeRequestMessage", "priority": 251, "address": 244, "rtr": true}
2018-10-17 08:23:48 INFO (velbus-connection-writer) [velbus] Sending message on USB bus: {"name": "ModuleTypeRequestMessage", "priority": 251, "address": 245, "rtr": true}
2018-10-17 08:23:48 INFO (velbus-connection-writer) [velbus] Sending message on USB bus: {"name": "ModuleTypeRequestMessage", "priority": 251, "address": 246, "rtr": true}
2018-10-17 08:23:48 INFO (velbus-connection-writer) [velbus] Sending message on USB bus: {"name": "ModuleTypeRequestMessage", "priority": 251, "address": 247, "rtr": true}
2018-10-17 08:23:48 INFO (velbus-connection-writer) [velbus] Sending message on USB bus: {"name": "ModuleTypeRequestMessage", "priority": 251, "address": 248, "rtr": true}
2018-10-17 08:23:48 INFO (velbus-connection-writer) [velbus] Sending message on USB bus: {"name": "ModuleTypeRequestMessage", "priority": 251, "address": 249, "rtr": true}
2018-10-17 08:23:48 INFO (velbus-connection-writer) [velbus] Sending message on USB bus: {"name": "ModuleTypeRequestMessage", "priority": 251, "address": 250, "rtr": true}
2018-10-17 08:23:48 INFO (velbus-connection-writer) [velbus] Sending message on USB bus: {"name": "ModuleTypeRequestMessage", "priority": 251, "address": 251, "rtr": true}
2018-10-17 08:23:48 INFO (velbus-connection-writer) [velbus] Sending message on USB bus: {"name": "ModuleTypeRequestMessage", "priority": 251, "address": 252, "rtr": true}
2018-10-17 08:23:49 INFO (velbus-connection-writer) [velbus] Sending message on USB bus: {"name": "ModuleTypeRequestMessage", "priority": 251, "address": 253, "rtr": true}
2018-10-17 08:23:49 INFO (velbus-connection-writer) [velbus] Sending message on USB bus: {"name": "ModuleTypeRequestMessage", "priority": 251, "address": 254, "rtr": true}
2018-10-17 08:23:49 INFO (velbus-connection-writer) [velbus] Sending message on USB bus: {"name": "ModuleTypeRequestMessage", "priority": 251, "address": 255, "rtr": true}
2018-10-17 08:23:52 INFO (velbus-connection-writer) [root] Scan finished
    
    2018-10-17 08:20:19 INFO (velbus-process-reader) [velbus] Processing message b'\x0f\xfb!\x08\xf1\x01\xff\xff\xff\xff\xff\xff\xe1\x04'
    2018-10-17 08:20:19 INFO (velbus-process-reader) [velbus] New message: {"name": "ChannelNamePart2Message", "priority": 251, "address": 33, "rtr": false}
    2018-10-17 08:20:19 INFO (velbus-process-reader) [velbus] Processing message b'\x0f\xfb!\x06\xf2\x01\xff\xff\xff\xff\xe0\x04'
    2018-10-17 08:20:19 INFO (velbus-process-reader) [velbus] New message: {"name": "ChannelNamePart3Message", "priority": 251, "address": 33, "rtr": false}
    2018-10-17 08:20:19 INFO (velbus-process-reader) [velbus] Processing message b'\x0f\xfb!\x08\xf0\x02Tafel \xcf\x04'
    2018-10-17 08:20:19 INFO (velbus-process-reader) [velbus] New message: {"name": "ChannelNamePart1Message", "priority": 251, "address": 33, "rtr": false}
    2018-10-17 08:20:19 INFO (velbus-process-reader) [velbus] Processing message b'\x0f\xfb!\x08\xf1\x02lamp\xff\xff2\x04'
    2018-10-17 08:20:19 INFO (velbus-process-reader) [velbus] New message: {"name": "ChannelNamePart2Message", "priority": 251, "address": 33, "rtr": false}
    2018-10-17 08:20:19 INFO (velbus-process-reader) [velbus] Processing message b'\x0f\xfb!\x06\xf2\x02\xff\xff\xff\xff\xdf\x04'
    2018-10-17 08:20:19 INFO (velbus-process-reader) [velbus] New message: {"name": "ChannelNamePart3Message", "priority": 251, "address": 33, "rtr": false}
    2018-10-17 08:20:19 INFO (velbus-process-reader) [velbus] Processing message b'\x0f\xfb!\x08\xf0\x04Relaisy\x04'
    2018-10-17 08:20:19 INFO (velbus-process-reader) [velbus] New message: {"name": "ChannelNamePart1Message", "priority": 251, "address": 33, "rtr": false}
    2018-10-17 08:20:19 INFO (velbus-process-reader) [velbus] Processing message b'\x0f\xfb!\x08\xf1\x04 3\xff\xff\xff\xff\x89\x04'
    2018-10-17 08:20:19 INFO (velbus-process-reader) [velbus] New message: {"name": "ChannelNamePart2Message", "priority": 251, "address": 33, "rtr": false}
    2018-10-17 08:20:19 INFO (velbus-process-reader) [velbus] Processing message b'\x0f\xfb!\x06\xf2\x04\xff\xff\xff\xff\xdd\x04'
    2018-10-17 08:20:19 INFO (velbus-process-reader) [velbus] New message: {"name": "ChannelNamePart3Message", "priority": 251, "address": 33, "rtr": false}
    2018-10-17 08:20:19 INFO (velbus-process-reader) [velbus] Processing message b'\x0f\xfb!\x08\xf0\x08Zoldere\x04'
    2018-10-17 08:20:19 INFO (velbus-process-reader) [velbus] New message: {"name": "ChannelNamePart1Message", "priority": 251, "address": 33, "rtr": false}
    2018-10-17 08:20:19 INFO (velbus-process-reader) [velbus] Processing message b'\x0f\xfb!\x08\xf1\x08 overl\x8c\x04'
    2018-10-17 08:20:19 INFO (velbus-process-reader) [velbus] New message: {"name": "ChannelNamePart2Message", "priority": 251, "address": 33, "rtr": false}
    2018-10-17 08:20:19 INFO (velbus-process-reader) [velbus] Processing message b'\x0f\xfb!\x06\xf2\x08oop\xff\x88\x04'
    2018-10-17 08:20:19 INFO (velbus-process-reader) [velbus] New message: {"name": "ChannelNamePart3Message", "priority": 251, "address": 33, "rtr": false}
    2018-10-17 08:20:19 INFO (velbus-process-reader) [velbus] Processing message b'\x0f\xfb!\x08\xf0\x10VirtueN\x04'
    2018-10-17 08:20:19 INFO (velbus-process-reader) [velbus] New message: {"name": "ChannelNamePart1Message", "priority": 251, "address": 33, "rtr": false}
    2018-10-17 08:20:19 INFO (velbus-process-reader) [velbus] Processing message b'\x0f\xfb!\x08\xf1\x10el rel\x98\x04'
    2018-10-17 08:20:19 INFO (velbus-process-reader) [velbus] New message: {"name": "ChannelNamePart2Message", "priority": 251, "address": 33, "rtr": false}
    2018-10-17 08:20:19 INFO (velbus-process-reader) [velbus] Processing message b'\x0f\xfb!\x06\xf2\x10ais\xff\x91\x04'
    2018-10-17 08:20:19 INFO (velbus-process-reader) [velbus] New message: {"name": "ChannelNamePart3Message", "priority": 251, "address": 33, "rtr": false}
    2018-10-17 08:20:30 INFO (velbus-process-reader) [velbus] Processing message b'\x0f\xf8 \x02\x01\x01\xd5\x04'

(Home Assistant 0.80.1 with python-velbus 2.0.20)

AlbertHakvoort · October 17, 2018, 6:56am

My config is :

velbus:
port: 172.30.30.21:3788

sensor:

platform: velbus

switch:

platform: velbus

binary_sensor:

platform: velbus

AlbertHakvoort · October 18, 2018, 8:20pm

Tried a fresh install, but no luck either… Any Idea?

DRACO · February 7, 2019, 12:19pm

Good morning @Cereal2nd, when will this last version of Velbus be integrated on Hassio? I have the version 0.86.4 of Hassio and some VMB2BL modules, that are not detected in this version of Hassio because it is still version 2.0.11. When will we get version 2.0.22? Is there any way we can install it on Hassio, I mean, to update to version 2.0.11?
Thank you so much.
Best regards

Cereal2nd · February 8, 2019, 12:25pm

i have no idea what i should do to upgrade it in hass.io, i’m not a fan of hass,io and not using it

DRACO · February 9, 2019, 1:29pm

Thanks for your answer, it seems I’ll have to go back to Hassbian. Best regards

BTC · February 11, 2019, 12:35am

Dear Draco,
Home assistant is becoming more attractive by the day. Do you think manually updating some files from the 2.0.22 version could solve it? I’m also not seeing VMB2BLs in my installation…
Regards,
Ward

DRACO · February 12, 2019, 10:32pm

Dear Ward,
I’m sorry for my late reply.
That’s exactly what I want to try. I’ve already placed the folder Velbus inside the folder costum_components. However, I get an error and it tells me to check configurations at Velbus Home assistant: ```
velbus:
port: “/dev/ttyACM0”

Without the Velbus folder, it works but the module VMB2BLs doesn’t. My question is: is anyone going to make these modules available in a more recent version of the Hassio? That is to say, is anyone going to place the 2.0.22 version on Hassio?
Best regards
Draco

BTC · February 17, 2019, 8:48am

Hi Draco,

There is hope I have a second raspberry pi running Openhabian, and that one is seeing everything in my installation:

It is based off the same Python library, so we should be able to add support.
However!

I connect my HomeAssistant P to the system using the same VMB1USB, but the entities are not appearing anymore!
Would you be prepared to join an online meeting to check this out? Maybe you see where I made a mistake (I really can’t find any myself…)

BR

Ward

DRACO · February 17, 2019, 11:45am

Hi,
I’m trying to reach the man who is responsible for integrating Velbus with Home Assistant. I’ll come back to you when I have news on this.

Best regards,
Draco

BTC · February 17, 2019, 12:42pm

Hi DRACO,
I guess you mean Thomas Delaet?
I also contacted him but he didn’t answer yet.

Any chance you can take a look at my system to see how I can get to the same level as you? (Seeing modules except the ones you mention).

Best regards

Cereal2nd · February 17, 2019, 2:06pm

we have seen the exact same problem as you describe in other installations.
but i can not reproduce this here at home, so its hard to fix the problem in that case.

BTC · February 17, 2019, 4:25pm

Hi!
Thank you for your reply!
I have two systems side by side, Openhabian and Hassio.
I can do some debugging/investigation per your instruction, I can also give you access remotely via PM
Best regards
Ward

DRACO · February 17, 2019, 10:41pm

Good evening, BTC, it’s not Thomas Delaet, it’s one of the people who is doing the integration of Velbus with Hassio.

I’m going to try to help you by explaining my own Home Assistant Hassio and how it’s working with my Velbus modules (with the exception of VMB2L, of course).

I bought a VMB1USB: https://www.velbus.eu/products/view?id=365968 This module is linked to one of my Velbus modules and to a USB door of my Raspberry Pi 3B+ where I have my Home Assistant.
On the configuration menu I have the following code:

#Connetion to Velbus by USB at Raspberry Pi 
velbus:
  port: "/dev/ttyACM0"

Then reboot Home Assistant. Sometimes the sensors do not appear. If it happens, just reboot again they will eventually appear.

Then you just have to configure your way at customize.yaml

Best regards,

BTC · February 18, 2019, 8:47am

Dear DRACO,
My config is identical.
Which version of Hassio are you on?
I will downgrade to that one if it’s not the latest one.
Best regards,
Ward

DRACO · February 18, 2019, 11:09pm

Good evening Ward, my version is the last hassio 0.87.1
I think that in de next version 0.88 we are going to have the blinds will be available.
Best regards,
Draco