This integration is going to stop once Samsung or Aeotec (whoever is driving the car now) pull the plug on groovy. No idea when that's going to be though. Aeotec likely gets to decide that now. However, from your list of Z-Wave devices, I would just slowly make the transition. You didn't mention the age of your Z-Wave wall switches, but if they all support S2 security then it shouldn't be an issue. When you're prompted, just uncheck all the boxes and run them without security enabled. Devices that will only join with S0 can be a problem if you have too many. Locks of course will still join as S0, but that's not an issue since they're non-repeating end devices. But, if you have a Schlage lock, you might want to replace that. They are very problematic here. Most have either moved to another brand or switched to Zigbee locks. I have a Yale YRD256 Z-Wave lock and it works great, so it's primarily the Schlage that are a pain.
What other devices do you need to keep ST running for?
With all due respect, I have to disagree with "They are very problematic here" Some have had issues, but not all. I have 3 Schlage locks that I had no trouble moving from ST and they have been working fine for months - and I didn't even add any repeaters.
The better strategy, IMHO, is to see how it goes with pairing. If you have more than one Schlage, try moving one and see how it goes.
Over the last two years, more issues have been reported with Zwave Schlage locks than any other lock, including zwave+ Schlage locks. This led to Schlage locks being removed from the List of Compatible Devices.
Considering that Schlage zwave fw dates back to 2015, I think @SmartHomePrimer’s advice is sage.
Does it mean that every Schlage lock will be troublesome? Obviously, not. But the odds are not in favor of a trouble-free experience.
Did you exclude all your devices from smartthings first and then put each of them in pair mode individually to pair them with hubitat?
You need to exclude each device from smatrtthings, then put each device in inclusion mode then tell hubitat to find it.
Your post sounded like you are expecting hubitat to find all your devices at once and by itself. That’s not how it works.
By the way, unless I'm mistaken, with the latest update, you can purchase a small TP-LINK nano wifi adapter, and use it on the Hub with the right cable. This approach will allow you ton put the Hub anywhere (where there is power).
I personally haven't tried this approach, but apparently it works.
Relax guys. I wrote "you might want to replace", not DO IT!
They are off the compatible devices list for a second time. Yes, they are very problematic. That's not a guess.
By all means, I'm not suggesting you don't try anything you want to try. It's just advice.
Okay, couple things here. Move devices over slowly. Start from near the he hub with repeaters. Exclude device in st first, then exclude in HE, then pair repeaters near the he hub to build the mesh. I had to restart the hub after adding every 1-2 devices, don't know if that's the case with the newest hub firmware, but I had to or nothing else would pair.
I built my mesh slowly over a week or so. Once I got past 15 devices it seemed to settle down.
But getting started is painful due to the 700 series firmware.
I think OP latched onto that concept as a way to migrate based on his reading of the definitions of the standard from the owner of the standard, Silicon Labs. I get the impression that OP's functional use case is just to find the least painful route to transition from ST to HE - the best tools and techniques. I jumped on OP about the secondary controller route but unless one was quite familiar with this environment, it's not an illogical place to start or approach to take.
I did a transition similar to OP's last fall and it's been a much bigger project than I originally envisioned. Everything Zigbee came over just fine. But the Z-Wave stuff has been frustrating and time consuming. I suspect this is because I have some older and poorly implemented Z-Wave devices, but they weren't a problem on ST and they've caused a lot of grief in HE.
My advice after going through this is plan on replacing Z-Wave devices that cause problems. You'll know about them from the beginning because they'll be difficult to exclude from your ST mesh and difficult to include in HE. After you spend hours doing that they'll just continue to cause grief. I've had to replace probably 20% of my Z-Wave devices (none of my Zigbee). Battery powered sensors seem to be the worst, but I've had problems with several plug-in switches too. Before buying replacements, spend some time reading on this forum what people are having luck with.
Seeing how the ST platform is imploding, I'm glad I'm off of it. The Hubitat world feels less mature to me and has some rough edges, but it also feels much more open and malleable. And this active user community helps a lot. It's going to take more work and money than I expected, but I'm ending up with a home automation system I think I'll like more.
@dnickel: I don't think you understood my original post...I want to use the Hubitat hub as a secondary z-wave controller...exclusion is easy...simplest was for me is to just reset the z-wave device.
@marktheknife: The use case is not an edge one. As I stated in my original post, I simply do not want to migrate 54 Z-wave devices and 14 Zigbee devices from a working setup to (in my mind) an unproven platform...regardless of the people who like it
@Rxich: Thank you for your comment, but if you look at my original post, with 54 Z-wave devices in my network...I know how to build one up. My current network is very stable and functional...just not sure about the future of SmartThings (which is working just fine at the moment)
@erktrek: I totally understand this issue. Assuming I can get the Hubitat as a secondary Z-wave controller...the next step will be to look for a "z wave tweaker" which would let me set group 1 lifeline with both the primary Z-wave controller address and the Hubitat Z-wave address.
If I cannot find a "z wave tweaker", I would simply setup a polling routine using Rule Machine or WebCore (which I use now in SmartThings).
I would prefer to be able to set the lifeline as the response would be quicker.
I’m just going to rip the bandaid off. HE will NOT function as a secondary controller in the way you are describing, and no amount of talking about how you think it should work differently will change that fact. So your choices are, like it or not, either buy in to migrating the devices off of ST or go looking for another solution that won’t work the way you want it to either.
@thebearmay: The Hubitat documentation says otherwise: Hubitat Learn Mode. Now why would you publish this in your documentation when you don't support it? Why give me a "bandaid" and not let me use it? Why give me a radio dial in my car and not let me change the channel? Heck, even the "evil" SmartThings hub works as a secondary Z-wave controller.
@bcopeland: This has not been my experience. My Z-wave devices (all Z-Wave plus) accept up to 4 I think (GE/Jasco switches, Kwikset lock, etc.)
@ksgnow2010 - I migrated from Smartthings to hubitat. It took a long time over many many weekends to fully do it, but during the transfer I was able to keep everything working by using Hub Connect to link devices between ST & Hubitat.
I know from experience how long it takes to do it (I have nearly 150 devices and so so many rules). I also had devices that were installed into the house in a way that made them almost completely inaccessible and in some cases I nearly gave up trying to move them.
But... oh my god is it worth it. Forget about this idea of using hubitat as a secondary controller in ST - its a no go. Just go through the pain of moving... there is no shortcuts. On the other side is a hub that actually works, is super fast, and can connect with practically everything... just do it!
