VMBELO subaddresses not being populated using .things file #29
Description
Expected Behavior
The VMBELO modules are configured by OpenHAB as 33 channel input modules, with only one address to access the module on the bus.
The expected number of addresses for a complete VMBELO is infact 5:
1 for the module itself and the first 8 channels, 3 addresses for the next 24 channels and 1 address for the temperature controller.
Current Behavior
Only one address can be configured in OpenHAB, hence only the functionality of the first 8 channels works.
Possible Solution
Allow the user to enter different addresses for the different channel ranges
Environment
As I'm working solely with the .items and .things files a had to resort to the source code to determine the parameters which were required for the network bridge, oled panels, etc... I'm running the latest version of VelbusLink (10.2.4) and the latest firmware for the VMBELO modules (2012)
Note
I've added two images, one showing the configuration, and one showing the response given by the VMBELO module (Module type + Module subtype) on a scan request.
As I'm not using the scan function but instead use the .things file, I'm unaware if you actually process the subtype packet to collect the additional addresses during the scan.
