Support for Velbus Home Automation

MarcDe · October 11, 2021, 3:00pm

I have removed the complete Velbus integration. Performed a reboot of the complete installation. Installing the Velbus integration in the UI. After scan, Velbus integration found 12 of the 22 devices. It is not usable at the moment.

	Line 96: File /usr/src/homeassistant/homeassistant/components/velbus/config_flow.py, line 61, in async_step_user
	Line 98: File /usr/src/homeassistant/homeassistant/components/velbus/config_flow.py, line 41, in _test_connection
	Line 100: File /usr/local/lib/python3.9/site-packages/velbusaio/controller.py, line 151, in connect
	Line 112: 2021-10-11 16:33:49 WARNING (MainThread) [homeassistant.components.switch] Setup of switch platform velbus is taking over 10 seconds.
	Line 113: 2021-10-11 16:33:49 WARNING (MainThread) [homeassistant.components.sensor] Setup of sensor platform velbus is taking over 10 seconds.
	Line 114: 2021-10-11 16:33:49 WARNING (MainThread) [homeassistant.components.binary_sensor] Setup of binary_sensor platform velbus is taking over 10 seconds.
	Line 115: 2021-10-11 16:33:49 WARNING (MainThread) [homeassistant.components.cover] Setup of cover platform velbus is taking over 10 seconds.
	Line 116: 2021-10-11 16:33:49 WARNING (MainThread) [homeassistant.components.climate] Setup of climate platform velbus is taking over 10 seconds.
	Line 117: 2021-10-11 16:33:49 WARNING (MainThread) [homeassistant.components.light] Setup of light platform velbus is taking over 10 seconds.
	Line 118: 2021-10-11 16:34:39 ERROR (MainThread) [homeassistant.components.switch] Setup of platform velbus is taking longer than 60 seconds. Startup will proceed without waiting any longer.
	Line 119: 2021-10-11 16:34:39 ERROR (MainThread) [homeassistant.components.sensor] Setup of platform velbus is taking longer than 60 seconds. Startup will proceed without waiting any longer.
	Line 120: 2021-10-11 16:34:39 ERROR (MainThread) [homeassistant.components.binary_sensor] Setup of platform velbus is taking longer than 60 seconds. Startup will proceed without waiting any longer.
	Line 121: 2021-10-11 16:34:39 ERROR (MainThread) [homeassistant.components.cover] Setup of platform velbus is taking longer than 60 seconds. Startup will proceed without waiting any longer.
	Line 122: 2021-10-11 16:34:39 ERROR (MainThread) [homeassistant.components.climate] Setup of platform velbus is taking longer than 60 seconds. Startup will proceed without waiting any longer.
	Line 123: 2021-10-11 16:34:39 ERROR (MainThread) [homeassistant.components.light] Setup of platform velbus is taking longer than 60 seconds. Startup will proceed without waiting any longer.
	Line 126: 2021-10-11 16:40:09 ERROR (MainThread) [velbus] Not all modules are loaded within a timeout of 600 seconds, continuing with the loaded modules

Bart_Coppens · October 11, 2021, 7:38pm

Did you clear the Velbuscache folder inbetween removing the integration and rebooting and adding it again? This helped my installation as well as it forced to read out all devices again. Before I did this I also didn’t get correct readouts of device and entities names that changed in the meantime.

MarcDe · October 11, 2021, 7:52pm

Folder was empty

Bart_Coppens · October 11, 2021, 7:56pm

Ok then i guess all eyes are on @Cereal2nd.

yvesfouquet4 · October 11, 2021, 9:23pm

i deleted the cache:

after reboot it took 10 minutes to build this cache:

i tested some of the switches and earlier mentioned issues remain

Schildknaap · October 12, 2021, 10:08am

Hey yvesfouquet4,
I’m new to Homeassistent and have the same issues with a new installation and Velbus.
Before i ended up here because i was looking in the direction of a installation issues since i"m new
I try the follow steps without any luck on my raspberry pi homeassitent installation
Install velbus integration
Connected rasberry directly to the usb , serial module
Installation looks good all modules are found but when using the toggles 2 or more times things get acting wierd. Toggle issues…
Delete velbus and reinstall
But use a tcp/ip connection instead off directly conntect with usb .
Same issues . Toggles not updating responding , …
I also see the error coming up in the log files with 60 sec timeout when using tcp/ip.

So don’t know if this helps you with your search for a solution but fresh installation same issues is the bottom line
Kind regards
Bert

Cereal2nd · October 12, 2021, 10:21am

we are working on a fix:

yvesfouquet4 · October 12, 2021, 11:42am

Hey Bert, thanks for confirming the issues and i was going to reply to just wait for cereal to come with a fix but he already replied

Cereal2nd · October 12, 2021, 12:36pm

if people that are having problems are willing to help test this out it would be great.

github.com

Cereal2nd/velbus-aio/blob/master/README.md#develop-installation

![Python checks](https://github.com/Cereal2nd/velbus-aio/actions/workflows/main.yml/badge.svg)
![CodeQL](https://github.com/Cereal2nd/velbus-aio/workflows/CodeQL/badge.svg)

# velbus-aio

Velbus Asyncio, a library to support the [Velbus](https://www.velbus.eu/) home automation system.

This Lib is a rewrite in python3 with asyncio of the [python-velbus](https://github.com/thomasdelaet/python-velbus/) module.
Part of the code from the above lib is reused.
Its also build on top of the [openHab velbus protocol description](https://github.com/StefCoene/moduleprotocol).

The latest version of the library is published as a python package on [pypi](https://pypi.org/project/velbus-aio/)

# Supported connections:

| Type          | Example                 | Description                                                                              |
| ------------- | ----------------------- | ---------------------------------------------------------------------------------------- |
| serial        | /dev/ttyACME0           | a serial device                                                                          |
| ip:port       | 192.168.1.9:1234        | An ip address + tcp port combination, used in combination with any velbus => tcp gateway |
| tls://ip:port | tls://192.168.1.9:12345 | A connection to [Signum](https://www.velbus.eu/products/view/?id=458140)                 |

This file has been truncated. show original

Schildknaap · October 12, 2021, 12:48pm

Hey Cereal2nd ,

I’m always willing to test it out .
But i’m very new in the world of Home Assistent it can take a while before i figure things out
And might need some help if i can’t wrap my head around it .

Greetz Bert

Geert_Verbist · October 12, 2021, 1:02pm

Does this also include the thermostat fix?

Cereal2nd · October 12, 2021, 1:15pm

no, that fix is not ready

Schildknaap · October 12, 2021, 3:49pm

Hey Cereal2nd ,

Ok some noob questions sorry.
Can you point me a little in the right direction on how to test the Fix ?
Where do i run the installation ,terminal in Homeassistent ?
If yes than i’m stuck on step 3 no phyton.

Thx

yvesfouquet4 · October 12, 2021, 3:52pm

Same issue like Bert, willing to help but my knowledge to do what you asked is limited

Cereal2nd · October 12, 2021, 6:06pm

drop me a pm with your email adress and we will setup a debug session out of this thread

MarcDe · October 13, 2021, 12:40pm

I like to help you also, but I need some explination how to install it on my Raspberry Pi 4.

MarcDe · October 18, 2021, 5:20pm

I installed the “develop-installation” and started “python examples/load_modules.py”, for now it seems that all my Velbus devices have been scanned without errors. When I activate switches it seems to be fine. The “VMB1TS - Temperature sensor” also updates the temperature.

MarcDe · October 18, 2021, 5:45pm

Error after 600 seconds:

i thought it worked

Cereal2nd · October 18, 2021, 6:04pm

Just below that error message is a list printed

These are all the discoverd modules. Check what modules are missing or what modules have loaded=false

And let me know

MarcDe · October 19, 2021, 2:56pm

Since there is no log file, I am sending you 4 screenshots, the first is a “VelbusLink” recording of my Velbus configuration, the others are the modules found or not. Do you also need the files in the .velbuscache directory? You know better than me how to interpret this.