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.