Multi component zwave devices and hub associations

[JDRoberts]

@nayelyz

@philh30 has been researching this issue further and has identified the flaw in the stock driver that caused the missing button:

[ST EDGE] Edge Developer needed: MCOHome MH-S312 and MH-S314

MH-S314 (newer Z-wave Plus model) - 015F/3141/5102 The issue with this device was just a mismatch in the way the stock driver maps components to endpoints. The logic is that endpoint n maps to component switchn, and main maps to endpoint 1. So both main and switch1 map to endpoint 1, switch2 maps to endpoint 2, etc. The profile in use, switch-multicomponent-4 lacks a switch4 component, so events from endpoint 4 weren’t being mapped to a component. The fix to that was simply adding the missing component. Overall, the naming of profiles in the stock driver seem a bit inconsistent - while the switch-multicomponent-4 profile maxes out at switch3, the switch-5 profile goes up to switch5. One oddity that I see in the screenshots for this device is that the hub isn’t currently in the Lifeline …

Please pass this along to the team doing the stock drivers for multi component zwave devices.

Thanks!