# Multi component zwave devices and hub associations

**URL:** <https://community.smartthings.com/t/multi-component-zwave-devices-and-hub-associations/246430>\
**Category:** Support\
**Created:** [August 20, 2022, 4:02pm UTC](https://community.smartthings.com/t/multi-component-zwave-devices-and-hub-associations/246430 "2022-08-20T16:02:56Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![JDRoberts](https://yyz2.discourse-cdn.com/smartthings/user_avatar/community.smartthings.com/jdroberts/32/56577_2.png) [@JDRoberts](https://community.smartthings.com/u/JDRoberts)\
**Post date:** [August 20, 2022, 4:02pm UTC](https://community.smartthings.com/t/multi-component-zwave-devices-and-hub-associations/246430/1 "2022-08-20T16:02:56Z")

</div>

@nayelyz

This issue is supertechnical and needs to be given to a zwave engineer who understands zwave multichannel association. But I have seen it reported for several different devices now, so it definitely needs a fix.

When a multiendpoint zwave device (typically a multi button light switch) uses association to communicate with the hub, the hub’s device ID needs to be added to each association group used by the device, or the button presses for that device will not get sent to the hub.

There have been several devices using the stock drivers where users report the last button doesn’t work. Meaning its button presses aren’t being sent to the hub. Here’s one recent example with a stock edge driver. Buttons 1-3 work, button 4 doesn’t.

[[ST EDGE] Edge Developer needed: MCOHome MH-S312 and MH-S314 - #2 by philh30](https://community.smartthings.com/t/st-edge-edge-developer-needed-mcohome-mh-s312-and-mh-s314/246164/2)

![image](https://global.discourse-cdn.com/smartthings/original/3X/6/f/6f43d753a68c6dfa41efd279c49b018368f533cf.jpeg)

And here’s the user manual for the device.

> **[340724\_mh\_s314\_eu.pdf](https://storage.ua.prom.st/340724_mh_s314_eu.pdf)**

This should be an easy fix for someone who is familiar with the zwave side.

Thanks!

---

<div class="post-metadata">

**Author:** ![JDRoberts](https://yyz2.discourse-cdn.com/smartthings/user_avatar/community.smartthings.com/jdroberts/32/56577_2.png) [@JDRoberts](https://community.smartthings.com/u/JDRoberts)\
**Post date:** [August 21, 2022, 4:27pm UTC](https://community.smartthings.com/t/multi-component-zwave-devices-and-hub-associations/246430/2 "2022-08-21T16:27:37Z")

</div>

@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](https://community.smartthings.com/t/st-edge-edge-developer-needed-mcohome-mh-s312-and-mh-s314/246164/18):
>
> 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 A…

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

Thanks!

---

<div class="post-metadata">

**Author:** ![nayelyz](https://avatars.discourse-cdn.com/v4/letter/n/59ef9b/32.png) [@nayelyz](https://community.smartthings.com/u/nayelyz)\
**Post date:** [August 22, 2022, 11:59pm UTC](https://community.smartthings.com/t/multi-component-zwave-devices-and-hub-associations/246430/3 "2022-08-22T23:59:39Z")

</div>

Sorry for the delay, @JDRoberts. I’ll report this to the internal team.

Thanks, @philh30 for debugging this issue and both for bringing this to our attention 😃
