Module VMBGP4-2, VMBGP4PIR does not yet support sub modules

[bvedomotic]

The problem

When I refresh the Velbus Integration i receive the flowing errors in the configuration logs:
Logger: velbus
Source: /usr/local/lib/python3.8/site-packages/velbus/controller.py:311
First occurred: 4:09:17 PM (6 occurrences)
Last logged: 4:09:35 PM

Module VMBGP4PIR does not yet support sub modules
Module VMBGP4-2 does not yet support sub modules

For the modules of this type i also have the flowing error in the configuration logs:
Logger: velbus
Source: /usr/local/lib/python3.8/site-packages/velbus/controller.py:161
First occurred: 4:12:46 PM (4 occurrences)
Last logged: 4:12:46 PM

Failed to completely load module VMBGP4PIRK at address 8 before timeout expired.
Failed to completely load module VMBGP4 at address 176 before timeout expired.
Failed to completely load module VMBGP4PIRBad at address 177 before timeout expired.
Failed to completely load module VMBGP4PIR Living at address 191 before timeout expired.

The rest of the modules works fine only those 2 types are not working and not present in the devices.

Environment

• Home Assistant Core release with the issue:
  Version | 0.118.3
• Last working Home Assistant Core release (if known):
  Not working sinds begin testing.
• Operating environment (OS/Container/Supervised/Core):
  Installation Type | Home Assistant OS
• Integration causing this issue:
  Velbus
• Link to integration documentation on our website:
  https://www.home-assistant.io/integrations/velbus/

Problem-relevant configuration.yaml

It is the discovery that fails

Traceback/Error logs

Source: /usr/local/lib/python3.8/site-packages/velbus/controller.py:311
First occurred: 4:09:17 PM (6 occurrences)
Last logged: 4:09:35 PM

Module VMBGP4PIR does not yet support sub modules
Module VMBGP4-2 does not yet support sub modules

Logger: velbus
Source: /usr/local/lib/python3.8/site-packages/velbus/controller.py:161
First occurred: 4:12:46 PM (4 occurrences)
Last logged: 4:12:46 PM

Failed to completely load module VMBGP4PIRK at address 8 before timeout expired.
Failed to completely load module VMBGP4 at address 176 before timeout expired.
Failed to completely load module VMBGP4PIRBad at address 177 before timeout expired.
Failed to completely load module VMBGP4PIR Living at address 191 before timeout expired.

Additional information

[cereal2nd]

i think i have a fix for this, but i can not test this as i do not own these modules ...

[bvedomotic]

I wil test it on my system, wil this update (fix) apply automatically on home assistant os or have i to wait following release update?

[cereal2nd]

i can not commit this until we test this out, as i can break other parts of the system.

2 options:
1- i provide a difff and you test it on your local system
2- you provide me with some (temporary) access to your system over an ssh tunnel or something like thats and i debug on your system.

[bvedomotic]

I will try to setup a separate system that is connected on my velbus installation and inform you when it is accessible.

[AlbertHakvoort]

I've got the same issue @cereal2nd , I would like to try it

[ErikRat]

I have a similar problem.
Module VMBGP4-2 does not yet support sub modules
Failed to completely load module VMB4RYLD at address 100 before timeout expired
This has worked until Home Assistant version 0.113.3
I have 10 x VMB4RYLD.
Sometimes it loads one or two of these modules and gives the error message for the others.
All the modules with an address higher than the one that was loaded last will give this error.

[cereal2nd]

i'm currently working on a complete new implementation in homeassistent

not sure when i will be able to push it.
people who want to test can alreeady try it.
https://github.com/Cereal2nd/velbus-aio

VMBGP*-2 are not yet supported, althought it should be an easy fix (if i can login to someones installation with these active)

@ErikRat
that the modules are not loaded after some time is not normal, maybe some buss errors?
i have this running in an installation with about 80 modules and it works perfect.

[ErikRat]

@cereal2nd
My active installation runs on Home Assistant version 0.113.3, here it loads all modules without any problems. He will give the warning 'Module VMBGP4-2 does not yet support sub modules'.
But not the error message 'Failed to completely load module VMB4RYLD at address 100 before timeout expired'
I also get this warning in my logs
Logger: velbus
Source: /usr/local/lib/python3.8/site-packages/velbus/connections/serial.py:75
First occurred: January 16, 2021 15:28:46 (5 occurrences)
Last logged: 11:21:50
Stop executed
If I update my installation to a later version, the problems start.
Here is a list of all my modules:
10 x VMB4RYLD
1 x VMB4RYNOS
1 x VMB1RYNOS
1 x VMB1RY
1 x VMB4DC
1 x VMBGPO
1 x VMBGPOD
1 x VMBELO
6 x VMB8PBU
6 x VMBGP2

[cereal2nd]

the warning is normal in case the velbus connection is not stable. what you could try is to extend the timeout in the velbus module in the controller file there isa timer, increase this one

…

On Sun, Jan 17, 2021 at 1:46 PM ErikRat ***@***.***> wrote: @cereal2nd <https://github.com/Cereal2nd> My active installation runs on Home Assistant version 0.113.3, here it loads all modules without any problems. He will give the warning 'Module VMBGP4-2 does not yet support sub modules'. But not the error message 'Failed to completely load module VMB4RYLD at address 100 before timeout expired' I also get this warning in my logs Logger: velbus Source: /usr/local/lib/python3.8/site-packages/velbus/connections/serial.py:75 First occurred: January 16, 2021 15:28:46 (5 occurrences) Last logged: 11:21:50 If I update my installation to a later version, the problems start. Stop executed — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#69 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA4LF4NVCSB443SNBPDJGQTS2LL3VANCNFSM4UQSQYLQ> .

[ErikRat]

I have a separate test environment on a raspberry pi 4. Here I can perform any tests, it also has a connection with my velbus installation.
Where can I find this file where I can adjust the timer?
Can I access the file via the terminal in home assistant?
Or do I have to use the file editor in home assistant.

[cereal2nd]

the files depend on your installation type. how is it installed? - docker - virtualenv? - hass.io - system python - ....

…

On Sun, Jan 17, 2021 at 3:47 PM ErikRat ***@***.***> wrote: I have a separate test environment on a raspberry pi 4. Here I can perform any tests, it also has a connection with my velbus installation. Where can I find this file where I can adjust the timer? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#69 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA4LF4MBZC5ZFS3X6SFYVGLS2LZ6XANCNFSM4UQSQYLQ> .

[ErikRat]

In my test environment this is HA image
My active installation
Operating System
Ubuntu 20.04 LTS
Docker version
19.03.11

[ErikRat]

My concern is why does everything work in Home Assistant version 0.113.3 and not in a later version?
The only thing that has changed is the Home Assistant version.
Then it is Home Assistant that has broken something.

[KevChief]

I seem to have the same kind of error, but for modules VMBEL1 (failed to load address before timeout) and VMBEL4 (does not yet support sub modules)

[cereal2nd]

Previously before hass 0.115 we hardfailed in case a module was not loaded, since hass 0.115 we softail and do not continue with the error modules. If we increase the timer, then it should solve your problems.

…

On Mon, 18 Jan 2021, 00:46 KevChief, ***@***.***> wrote: I seem to have the same kind of error, but for modules VMBEL1 (failed to load address before timeout) and VMBEL4 (does not yet support sub modules) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#69 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA4LF4LQCVAXCQTW76E6GILS2NZFHANCNFSM4UQSQYLQ> .