Not quite true, it depends on the app/driver design. An example is Jason Bottjen's (@JasonJoel) excellent parent/child drivers for the GE/Jasco 26931 and 26933 Smart Motion switch and dimmer Z-Wave devices that have a motion sensor and switch or dimmer in the same unit. The parent/child version of the app creates an appropriate child device and motion sensor device so they can be separately operated. Makes Rules very clean and clear. I've used the parent/child versions for years, always operates perfectly, well coded.
He also provides integral drivers for the devices that allow the motion sensor and switch/dimmer to be controlled by operations on a single device. User's preference, mine is for the parent/child version.
But, again, it depends on the app/driver that is selected for the device. A parent/child version may not exist.
Unless I'm misunderstanding what you're saying...that's how the stock Parent/Child drivers work:
E.g., for a Minoston double-plug I have:
On/off for both plugs via parent device
On/off for either child plug individually
What I meant by above was that when you join a parent/child device to HE (double plugs, plug strips, the GE switch you mention, etc., you don't get an option to just join them as separate devices, they always join as parent/child devices. You can then control them together or separately as I note above.
I understood what you meant, but that’s true only if the only HE driver/app is a parent/child design. Some such devices have an integrated design that is not parent child. Jason Bottjen proves drivers of the parent/child app/driver design AND an integrated single driver that controls both the motion sensor AND the switch/dimmer as separate commands on the single, integrated, device. You choose the HE driver at pairing time, provided you have the user code for both types installed.
This is AMAZING!!! I have this exact switch and for this particular one, SmartThings doesn't allow you to separate the two. (In fact...it has stopped me from buying more) It annoys the crap out of me. I'm so happy to hear that HE does it better for this switch!!
Ok, so on a only slightly related note to the purpose of this thread;
I've gotten word that samsung should be releasing a hotfit for the flawed firmware that caused my system to basically go unusable over the past few weeks. Assuming that fix gets implemented soon and does actually fix it, my "rush" to transition to HE isn't quite as urgent. I 100% am still going to do it, but hopefully a little more relaxed timeline.
Curious if the C-8 Pro is expected to go on (more) sale on Black Friday/Cyber Monday? I'm happy to wait a few weeks to purchase it if it will go on more of a sale than it already is.
I've started my slow migration from ST to HE. So far, althoug a lot left to learn on HE, the features in HE blow away the lack of features in ST.
I'm running into a pickel.....I have a detached garage. I have a light switch in my house that I would use to open and close the garage door. Due to the distance between the two (and the fact that my house is stucco....aka RF blocking) I have a ST hub in the garage (on the same internet network as the house) that allows devices in the house to talk to those in the garage.
At the current moment, I'm only converting my house to HE, with a plan to swap the garage in the future. Until then, I would like to have the now HE light switch still able to open and close the ST Garage doors. I know this could be done via Sharp Tools, but pretty sure there are ways I can control my ST devices via HE. All the posts I've seen, however, are quite old and would love to know what the best solution to this issue is?
Just a heads up - once you’ve migrated all physical devices to HE, you can toss your ST hub and still use Hubithings to connect to any ST cloud devices - in my case for example, ring doorbell press and motion, brilliant wall controls, and a Mysa baseboard thermostat.
If you run into the same situation, Hubitat has Hubmesh, where you can directly share devices between Hubitat hubs.
You might pick up a cheap C5 or C7 on somewhere like Ebay, and use it for the garage devices. There are hubs on Ebay between $30-50 that would work fine for this purpose.
All automations and dashboards can then be integrated onto the main hub, and for the most part you won't know the difference.
that is my eventual plan.....until then I"m going to try to get Mira working
I did get it installed. I AM able to see my shared HE devices inside ST.
However, how do I share a device in ST so that I can see and use it in HE? That is what I'm trying to do. I need a switch in HE to control a device in ST.
edit: I think I am looking at this wrong. I'm guessing I share that light switch inside of HE with ST, and then in ST I creat a routine using the shared HE device.
You should not have to set up routines/automations to allow HE to see/control your ST device. I can see my Brilliant lighting loads in HE and control them directly. Similarly, my brilliant control can see the HE connected TV and control it directly (as a switch).
Did you install Hubi things on both the HE and ST?
Oh my....Im embarrased to even say how I messed this one up. In all my million browser tabs I had installed, I followed the directions for Mira install rather than HubiThings. Oops.
Took about 10 mins to setup and HubiThings is working great! I'm able to open the garage door via HE.
When I do this....this works via the cloud, right? Or is my HE hub communicating directly to my ST hub since they are on the same network?
I've not seen that community driver in action, good to know. Thanks for holding up class to explain to me again. 
