Awesome! Thank you! Super helpful.
I read on a different thread, when able, it is better to install without security (for things like light switches). Seemed backwards to me, but I'll trust y'all on that one. Do you personally concur with this approach @danabw ??
That was recommended in past years...when the 700 series Z-Wave came out it was a bit of a mess and leaving out S2 probably helped.
Nowadays the recommendation is that including w/S2 is fine, and may have improved results due to extra checking it does when commands are sent to S2 devices (blanking on the name...S2 supervision?).
For all my Z-Wave devices I've added recently I've added them w/S2.
I am wondering if this approach would make sense.
That would just make sure you get all your rules replicated and working before potentially breaking stuff.
Also make sure you get the typical needed apps like HPM and any other needed apps. SmartStart app on hubitat helps allot with storing that info on the hub as well.
You may want to look at replacing the non zwave Plus devices as those seem to be the most common cause of issues.
Also, Install all repeaters first, battery powered last.
I would assume devices included as long range could be installed at any time since they talk direct to hub.
Very interesting idea, nice thinking outside the box.
The new option to replace a device during pairing would work great here I think. Each time he pairs a device moved from the smartthings hub, he can choose the replace device option and replace the virtual hubithings device with the real device.
….The op needs to be aware that replace won’t work for parent/child devices using that method.
Does SmartThings have Parent/Child devices? I haven't used ST in so long, I don't remember.
I'm not sure whether any ST device handlers used parent/child to be honest. It might be that some devices migrated over will use a HE parent/child driver.
Just remember that doesn't work with child devices.
I'm not familiar with this termonalogy.....is this the same as Direct Association? If so, YES, ST does allow Direct Association. I have a few motion sensors DA'd to the applicable switch.
What an amazing idea. The fact I can transfer over rules is pretty cool. To be honest, I have a LOT of rules, but most all are super basic "turn lights on at sunset" type rules. I have a feeling that the hastle to transfer any rules over and then reconnect them is more work than just remaking the basic ones from scratch. Additionally, I probably need to do a little "spring cleaning" on my rules list as no doubt some are no longer used, or should be changed anyways. Most all of my more complex rules are run via Sharp Tools as there are a lot of rules I have run that the rule logic programming limitations of SmartThings prevented me to running the rule as I wanted....SharpTools was my solution there. As much as I love sharptools, from my initial research here on Hubitat, I have a feeling I may be able to ditch sharptools as it seems like I can do similar dashboards and complex rules in Hubitat that SmartThings wouldn't let me do.
This sends flashbacks to SmartThings 2 years ago when we could add apps like WebCore. Now SmartThings is so locked up, apps like that have gone to the wayside. I'm excited about the possibility of having apps again!
This open a new question; What are your "must have" apps???
Hubitat package manager, Device Activity Check, Owntracks & Watchtower are some of the community apps I use. I also have numerous other community apps but they pertain to specific devices like Bond, Govee, Kasa, Lightify, etc. I use many of the built-in apps and extensive use of Rule Machine for my complex rules. Good luck in the transition.
No,. This is an example of parent/child devices. The parent is the overall outlet unit. (This is a dual outlet outdoor plug) The children are the individual plugs.. The parent controls all or you can simply address the children individually.
Oh...yes. I have a few zooz zen 17 relay switches. Parent unit is the zen17. Then there are 2 "children" each for the individual relays. You can leave them grouped together or you can split them up. It is a bit clunky in SmartThings.
Much more elegant in HE and you can name the parent and children what ever you want.
HE doesn't allow you to choose how to add them to the hub, they will always add as parent/child....like the Minoston double-plug below. You can always control the children separately, but since they are child devices they don't work w/device swap:
A Hue hub is another common example of Parent/Child devices...you can add your Hue Hub to HE and it brings in all your Hue devices as children of the Hue Hub. Also ceiling fans using the Bond Bridge integration...fans come in under a parent "Bond" device, and each fan is a Fan and Light child under the Bond Bridge.
As noted, the Swap feature doesn't support child devices, so they won't be displayed in the list of available devices in the Swap process.
Should be the minority of your devices, unless you are using a Hue Hub w/lots of Hue bulbs.
Just to be clear.....all of this "Swap feature" is for transferring Rules/Automations only.....not swapping over the actual device. That must still be done the arduous manual way. Correct?
It's for devices, not apps/automations. It allows you to swap one device for another, so when you swap device A for device B, device A is automatically replaced by device B in all automations.
However, remembering that Swap Devices doesn't support child devices... @mavrrick58 - AFAIK HubiThings Replica devices are created as child devices on the HE hub, so using device swap won't be an option. Never mind... 
Gotcha.....for a moment I thought you were implying there was an easier way to transfer devices from ST to Hubitat other than the zwave exclusion then repair with Hubitat manual method.....because, that would be awesome if that existed!
Yes, that would be nice...but unfortuately we're still living in a the world of exclude/include. 
Download the Hubitat app
