[ST Edge] How to create child devices with edge?

[joshua_lyon (Josh, SharpTools.io Dashboard)]

I think we’re loosely saying the same thing.

Groovy DTHs originally only had the concept of Parent-Child devices. Components were a concept introduced with the next-gen platform (eg. next-gen C2C integrations circa 2017-2018). Following that, Groovy devices which were creating child devices could be enriched to add the isComponent: true flag when creating a child and it was also created as a component so it would display in the SmartThings (Samsung Connect) mobile app with a nice UI.

Of course, Edge Drivers follow all that much later and I guess it makes sense to assume Edge components would get translated backwards for use in Groovy, but I can also see how we’re coming to an end with Groovy and perhaps that translation layer needed to be updated for Edge devices and wasn’t.

Either way, MCD devices seem to work fine in the testing I’ve done with our next-gen integration in my local development instance. I ordered a few more devices which I believe have MCD Edge Drivers available and will test with those as well.

[milandjurovic71 (Milan)]

Selecting right switch is entertaining now.
I have added only 9 remotes out of 24, and this is what I have to deal with

[allmac (Alberto)]

Muchas gracias @Mariano_Colmenarejo !!

[Paul_Oliver (PCO)]

Sharptools’ new integration shows the individual switches of multi component devices. See below.

https://community.sharptools.io/t/beta-samsung-smartthings-next-gen-integration/9151/82?u=paul_oliver

[joshua_lyon (Josh, SharpTools.io Dashboard)]

Thanks for sharing, Paul. That particular link is to a beta thread, so most people won’t be able to see it, but I’m copying the content here (as it’s available for new SharpTools users using the next-gen connection):

@joshua_lyon

Support for Multi Component Devices is now available!

For example, if you have a dual outlet device or multi-button device, these may be implemented as multi component devices. To get your multi-component devices to show up, proceed through the authorization process starting from your SharpTools.io User Page.

Multi Component Devices are synced over to SharpTools as independent ‘Things’ with the component name in parentheses. Some devices may have a ‘main’ component that does things like monitor sensor values and act as a control for all components:

Whereas others might have the first element as the ‘main’ component and secondary elements as components:

[ToddBonzalez]

Just checking in on child/nested devices for third-party services. If I have a SST device with multiple switches, and I link to Google Home, GH only sees the parent/main switch. Is there something I need to do to expose the child switches to third parties?

[nayelyz (SmartThings Developer Support)]

@ToddBonzalez

Just checking in on child/nested devices for third-party services

Hi, @ToddBonzalez
So, as you mentioned “third-party services” I think you’re referring to a Cloud-Connected device which requires you to log in to the Manufacturer’s cloud to discover the device on the SmartThings side.
If so, I’m guessing this device is presented as a Multi-Component device, meaning there’s only one device instance that includes a section (component) for each switch.
In that case, there’s no way for you to expose them because they would need to be broken down into a device instance per switch which can be done only by the manufacturer (who developed the Cloud integration). In this thread, the discussion is about Hub-Connected devices and if yours falls into this category, you can create a custom driver for this purpose.