VMBGPOD modules not loaded after scan

[deweirdt]

Hi,

I've executed the scan.py on my pi (and on a x86 linux) and having both the same results. My VMBGPOD is not getting detected.

Initially I thought that the timings where the problem (since I'm having 53 modules) and my previous problem indicated that the timer in the scan.py is not sufficient.

Out of previous reports on this topic I saw also that the timer was increased from 180sec. to 320 sec. self.load_timeout = threading.Timer(320, timeout_expired).start()

These are the changes (only for testing that I've did)

• self.load_timeout = threading.Timer(3200, timeout_expired).start() -> Changed to 3200sec
• Exectued callback() in the def module_loaded(): since this one would only call the callback() when all modules are loaded
• Modified some loggings so that I see in the callback what modules are loaded.

If I understand correctly the flow of the python-velbus is that first a 'scan' is done and after this that all the 'scanned' modules are read.

• scan is taking avg. 10sec.
• Reading each modules is taking until the timeout (since the 4xVMBGPOD are never finished), but for reading the 49 modules it's taking avg. 10min

Can you support me in finding why the VMBGPOD are not read fully? Any hints?

scan.log

[deweirdt]

Update: Found back some info from the velserv. With VelbusLink I'm still able to find my 53 modules, but enabling this in on HA I'm having the same problem. Not all modules are found.

Any clue on this: 2021-04-02 17:01:18 WARNING (velbus-process-reader) [velbus] received unrecognized command 229 from module 15 (44) 2021-04-02 17:01:34 WARNING (velbus-process-reader) [velbus] received unrecognized command 229 from module 15 (44) 2021-04-02 17:01:41 WARNING (Thread-6) [velbus] Failed to completely load module Hal OLED at address 8 before timeout expired. 2021-04-02 17:01:41 WARNING (Thread-6) [velbus] Failed to completely load module Living OLED at address 9 before timeout expired. 2021-04-02 17:01:41 WARNING (Thread-6) [velbus] Failed to completely load module Slpk ouders at address 27 before timeout expired. 2021-04-02 17:01:41 WARNING (Thread-6) [velbus] Failed to completely load module Keuken OLED at address 41 before timeout expired. 2021-04-02 17:01:41 WARNING (Thread-6) [velbus] Failed to completely load module Teller A at address 99 before timeout expired. 2021-04-02 17:01:41 WARNING (Thread-6) [velbus] Failed to completely load module VMB4DC at address 116 before timeout expired. 2021-04-02 17:01:41 WARNING (velbus-process-reader) [velbus] received unrecognized command 241 from module 99 2021-04-02 17:01:41 WARNING (velbus-process-reader) [velbus] received unrecognized command 242 from module 99 2021-04-02 17:01:41 WARNING (velbus-process-reader) [velbus] received unrecognized command 240 from module 99

[thomasdelaet]

Hey,

I'm sorry but I have only a very basic setup myself with just some relays and input modules. I also did not add support for VMBGPOD myself. What I did with the modules that I have is to look up protocol documentation on Velbus website and from there try to understand what commands need to be send to load a module (load = fetch names of individual channels).

[brefra]

@deweirdt, I have a VMBGPOD which works ok. I guess the retrieval of the channel names preventing the loading of the VMBGPOD modules. Did you assign a name to all channels at the enabled pages? I didn't test it out but there might be an issue if they don't have a name assigned.

To troubleshoot it in more detail it helps if you could collect a debug log of the complete startup of the Velbus integration in HomeAssistant. You can do this by adding this to your configuration.yaml and reload the velbus integration (or restarting HA)

logger:
  default: warning
  logs:
    velbus: debug
    python-velbus: debug

[deweirdt]

Hi,

Finally got some time to turn it back on, PI is broken so had to install it on my Synology Not sure what you mean with name all channels (in HA or in VelbusLink)?

What I've noticed with this version is that I only get 21devices and 121 entities discovered by HA where I have 53 devices on my Velbus

VMB2PBN - VelbusLink: 20 - HA: 15 (missing address 20, 21, 24, 2C, 2F) VMB40C - VelbusLink: 4 - HA: None VM4RYNO - VelbusLink: 14 - HA: None VMB6PBN - VelbusLink: 7 - HA: 5 (missing address: 23, 27) VMBGPOD - VelbusLink: 4 - HA: 0 VMBPIRO - VelbusLink: 4 - HA: 3 (missing address: 2A)

Please find attached the log file from HA and the screenshots from VelbusLink (for reference)

Not really sure if I can provide more items, but I can try if you instruct me

homeassistant.log

[deweirdt]

Update: Found out that my HA did not have the latest version of python-velbus (I'm not sure how I can see the version embedded in HA), but I have seen that the commit https://github.com/thomasdelaet/python-velbus/commit/f951c930da4688543bdbdcd1fcbf3e0480430dcd was missing. Now I've manually updated the timeout and now I get the following result:

VMB2PBN - VelbusLink: 20 - HA: 20 VMB4DC - VelbusLink: 4 - HA: 4 VM4RYNO - VelbusLink: 14 - HA: 13 (missing address: 99) VMB6PBN - VelbusLink: 7 - HA: 7 VMBGPOD - VelbusLink: 4 - HA: 0 VMBPIRO - VelbusLink: 4 - HA: 4 (but name is called VMBIRO)

Log from latest restart (with higher timer) attached:

homeassistant.log