[ST Edge] Issues with multi-component devices and third-party integrations

Hi @nayelyz @posborne

I have installed all available edge drivers from smartthings and I see a big problem with the way how multi gang switches like “Qubino 2 relay switch”, “Neo coolcam double switch” are being handled by “z-wave switch” edge driver. Instead creating separate child device for each gang in a switch, they all are being put in one device using sub components.

In this format it is not possible to use/call separate gangs neither in Google Home nor in webcore as they are being recognized as one device only.

Keep in mind that even official “Qubino 2 relay switch” groovy DTH provided by smartthings have also created separate child devices, so such a change is not backward compatible at all even with DTH which smartthings have provided before.

Is there any plan to change the way how multi gang switches are going to be handled by edge drivers or do you suggest any workaround for that to overcome it ?

I tried creating “simulated switch” along with two automations to synchronize the changes on the child component (representing the second gang) with it, and reverse, but this didn’t work as it ended up in a loop.


Yes, in the non-Groovy integrations such as ST Schema or Edge drivers, components are not presented as separate devices.
However, I’ll share your question with the engineering team to see if they can provide any feedback and I’ll share it here with you.

Thank you for bringing this up.


Great than you.

I’ve always been a bit surprised that a comparatively recent integration like the Google Home one only handles the ‘main’ component. It seems rather lazy.

I don’t have webCoRE installed any more but I never used to have any problems using components, whether from legacy or current integrations. They were always available for authorisation as if they were child devices.

To me the apps are at fault for not handling components more effectively.

1 Like

Smartthings needs to present multi component devices in a way that allows voice assistants to independently control each switch of a two gang or three gang switch.

There are lots of examples of these devices.

Zooz zen30 fan/light switch (zwave)


Aeotec Nano dimmer, which allows separate functions for S1 and S2.(Zwave)


Tuya Smart Zigbee 3.0 2 gang switch

(this is the one with an integration in the smartthings app, again, separate functions for S1 and S2)

And lots of others. Like the recently added Heltun Quinto, which has 5 outputs, not just multiple inputs.

These are multi endpoint devices. There are multiple different ways of implementing that, but they are part of the standard protocol for both Z wave and Zigbee. And smartThings should be able to handle them, both in its own automations and in exposure to voice assistants and Ifttt.

Submitted with respect.


Has anything promised that Edge drivers would be backwards compatible with the all the abilities present in existing DTHs?

Of course not, but that is the purpose of this forum so the smartthings team can hear our feedback from testing edge beta drivers and provide changes or workarounds if needed, as this is still work in progress.

And I strongly believe that handling of multi gang switches by smart speakers is a must, as for sure a lot of users use such things and a lot of companies sell them.

So @nayelyz if possible talk to engineers please and let us know if any workaround could be provided.


You’re right, Edge drivers are a work in progress, the team is constantly working on improving their functionality.

I already created the report for the engineering team, once I get more information, I’ll share it with you.


Hello, I hope the developers are able to address this. For my Aeotec Nano Dual Switch (ZW132-C), with a DTH, I had 2 separate virtual devices to control 2 physically independent loads. With the Z-Wave Switch Edge driver (stock and 3rd party), I now see 1 virtual device with 2 sub switches: Main and Switch 1.

The two physical toggle switches continue to control the independent loads.

From the app, the power button on the tile controls both loads.
Inside the device, “Main” controls both loads, “Switch 1” controls 1 of the loads. There is no way of controlling the second load virtually. (So a virtual switch won’t work either).

Even if this did work, it’s not a good UX compared to the DTH, where independent loads showed separately (from the same physical module). If I had to create virtual switches as workarounds, I’d need to have 6: 2 to handle the physical toggle switch changing the virtual switch status, 2 to control the virtual switches being switched on and 2 for off (yes, I know I could use on/off).

Please, please revert this behaviour or at least give the choice of having a child device.

I have reverted back to DTH for this device, but hope the developers see fit to tweak this before DTH is finally sunset.

Thanks :slight_smile:


Can you try this version of the Z-Wave Switch Mc to see if you can control channel 1 with main and channel 2 with Switch1 from the app?

│ Name        │ Z-Wave Switch Mc                     │
│ Version     │ 2022-03-15T16:23:17.548625           │
1 Like

I am having the similar issues as @lewisburgess with z-wave dual switches using both stock z-wave switch driver and z-wave switch mc driver with Minoston Z-Wave Plug Outlet Dual On/Off Switch Outlet (MP20Z). I have no control of the second outlet using either driver.

Issues with Z-wave switch driver

With this latest version either?

I will try once it updates and it and report back. I still have verson 2022-03-11

1 Like

I still dont have this version available.

I published it again, just in case.

If you have the CLI in use you can install it immediately with the command
smartthings edge:drivers:install

1 Like

This now works to control both loads with the Minoston Z-Wave Plug Outlet Dual On/Off Switch Outlet (MP20Z).

I am fine with this version but wanted to note that the switches don’t control the expected outlets.
Main controls the Right (secondary) outlet and Switch 1 controls the Left (main) outlet. Thank you for fixing this!


This is improved on the Fibaro Double Switch

Main controls 1 load and Switch 1 controls the other from within the app.

But, there is an issue in the app changing state when either toggle switches change state. Looking at the logs, the hub is not seeing a state change and therefore, the app state is not changing. I have occasionally seen a button “pushed” but rarely.

Secondly, I use an IKEA button (with an Edge driver) to control some bulbs and both of these devices in a routine. There is a very significant delay in the Fibaro Double Switch switches changing state. The bulbs fire straight away. In a different room, with a Fibaro Dimmer and several bulbs, the states change straight away.

I haven’t tried removing the device and re-adding it. It’s the only Fibaro Double Switch I have. The Single Switch seems to be the same as before (you know I have a case open with ST about this). The Dimmers all work as usual. I removed my Aeotec Double Switch entirely as I have no use for it elsewhere in the house so I can’t try this (as you know, I was having big trouble with this).

I’ll send you some logs in a PM.

Thanks :slight_smile:

I didn’t change anything for the fibaro double switch. It Use the stock driver code.

I have one with the driver and it updates the toggle states change in the app correctly and without delay.

Oh, well it has improved - so something’s changed!

What would you like me to test?

I thought you had a problem with the double switch aoetec, but it seems that you no longer use it