At initialization or reload the Velbus integration scans every module address followed by getting channel names (equivalent to VelbusLink scan). This causes extensive use of the canBus resulting in some delay in the modules response messages. Because the module scan sequence does not pause for results, the traffic and delay on de canBus increases significant with higher module numbers because multiple modules are trying to send theire response messages at the same time.
Because of the fixed module timeout module configurations are missed.
Suggestion solution: restart (module) timeout when any message received from scanned module and stop timeout when config load complete.
At initialization or reload the Velbus integration scans every module address followed by getting channel names (equivalent to VelbusLink scan). This causes extensive use of the canBus resulting in some delay in the modules response messages. Because the module scan sequence does not pause for results, the traffic and delay on de canBus increases significant with higher module numbers because multiple modules are trying to send theire response messages at the same time. Because of the fixed module timeout module configurations are missed.
Suggestion solution: restart (module) timeout when any message received from scanned module and stop timeout when config load complete.