Good luck, you won't be disappointed The two biggest improvements for me after migrating....first, no outages, whether internet connection related or platform outage related. Second, the response speed is incredible. No more issues being halfway down the hallway (or even all the way through) before lights turn on, etc. I never would have dreamed in ST about being able to issue 10 consecutive commands with 1 second delay between each and have them execute with any degree of accuracy.
Being able to pick and choose which updates are applied and when has been awesome too...no more forced upgrades and associated down time. I read the update and bug fix lists with each update that comes out. If nothing applies to me, I don't update. If something does apply, I pick a time when everything it quiet at home to perform the update so it doesn't mess with anything. Having restorable backups is a nice feeling too in case something doesn't go well for whatever reason. Every thread I read about platform updates over on that other forum reinforces that I made the right decision to switch.
Backups have been mentioned and it would be good to point out that backups here on a Hubitat hub is two parts. There's a page under Settings where you can find backups. Every reboot causes a backup to be made, and every time you download a backup, it creates one. But be aware that this is a backup of the SQL DB -- not of the firmware version. There is no backup for that because it's not unique to you. The Hub stores a couple of copies of the firmware and you can "rewind" to a previous version. Those are separate, individual processes. Since ST has never offered a backup, understanding that you'll want to download backups, even if the hub has several, is going to help a lot at Restore time.
The Hub checks the DB at boot, and if it finds a critical error, it automatically uses an older instance of the DB. You'll notice.. rebooting takes a LOT longer when that's occurring. DON'T reboot quicker than 15-20 mins or you'll corrupt the DB again, it will boot slow, you reboot, corrupting the 3rd DB, and pretty soon, none of the DB on the hub are good. That's when you'll find that the backup you downloaded and saved gets you working again.
OMGOSH! 400 things! That's a lot! I can't imagine you'd take it slowly. it's just going to take a long time to port 400 things over to HE. So it's more of a situation where you're just sick of doing it for a while. I agree with @SmartHomePrimer. Take this time to evaluate your setup and phase out older stuff. I think it'll be hard to take it slowly when you realize how blazing fast your HE automations are running compared to what is still on smartthings. Be aware that harmony is still relying on smartthings, but there is an integration in the forums. Also, be prepared to rethink sensor locations as there's no latency with this system. (At least not with mine). I had to move sensors inside of the rooms they were automating because the automations react immediately when they're triggered, so I didn't need a motion sensor to see me from 20 feet away so that it turned on a light by the time I arrived in the room. No one has mentioned support. It's phenomenal. It's rare that you'll have to wait long for an answer. Usually there is someone in the community to help, and a lot of knowledgeable users to fill in when a developer or HE staffer isn't around. Doesn't happen very often. Long story short, I think you'll be happy with HE. Welcome to Hubitat, and be careful of that rabbit hole. It's rather deep.
In retrospect, un-pairing (excluding) the Z-Wave devices from SmartThings was my greatest challenge. If you have a Minimote (or can borrow one) it can make life easier. Also, the general exclude from the SmartThings main menu seemed to work when working from the device screen did not.
I also don't have as much devices as you do but I still thought the whole process of migrating from ST to HE was going to be hard. I took someone's advice and did it room by room. Basically moving stuff that was too integrated with other stuff in the house. I also moved Webcore Pistons as I went but soon realized that my HE hub was crawling. I started to look at RM but I couldn't wrap my head around how it worked. However, I knew that I had to move away from WC if I wanted success. I started with little rules in RM and really started to get the hang of how it works. Really easy, just don't over think it with RM. I just have two WC pistons that I need to keep right now and I still have my iphone's as presence sensors in ST which I use Hub Link to pass the presence to HE. Like other users, the big difference is the speed at which things happen. The lights go on instantly when motion is detected. With ST, I would be down the stairs and in the room(in the dark) before the lights would turn on. So frustrating!
Im a bit late getting my hub going due to a flakey Schlage Touch Screen Deadbolt lock. ST support finally responded on some of the issues I've been reporting and uncovered that this particular lock was flooding the Z-Wave network with bogus messages. Had to spend time last night replacing and reprogramming it.
I saw that in my research. I use neither so I'm not too concerned.
About 2 months ago I migrated to a SmartThings v3 hub after a Z-Wave failure on my v2 hub. I took the time to replace all of my Gen1 Jasco Z-Wave (200 series chipset) switches and dimmers with Z-Wave plus devices. I also replaced some problematic devices as well. I intend to replace any other devices that have issues during this migration as well.
I wrote an advanced DTH for the Z-Wave repeater for SmartThings which includes diagnostics. I'm looking forward to porting it to Hubitat in the coming days. I have 47 of these things so its critical these work flawlessly.
I'm certainly willing to entertain any volunteers for the endeavor! Your advise is sound. I actually have a sizeable pool of spare devices right now, thanks to holiday sales, so I'm currently working on test pairings with the HE hub. I'm also running trials ofg pairing them with ST then unpairing, and pairing with HE, to get an idea of how each device will respond, and which ones need a battery pull or full reset. Its very time consuming, but will save a big headache in the end.
Great advice. I was planning to do just that! Thanks.
Thanks all for the welcome. I look forward to getting the system up and running over the coming weeks!
A question that I forgot to ask earlier. What are folks using for a GUI? I interact with the ST UI more than I would probably like to. I miss the ability to group devices by room. It makes it much simpler to manager.
I know I can build Dashboards, but thats a ton of work with 400 devices! How are others managing large mnumbers of devices?
The answer depends on your Design. For you, Home Automation means a specific something. You have 400 devices so you probably expect a lot of automation to just take care of itself. Door or Motion causes light(s). Humidity causes fan(s). Water level causes water refil in the Pool, etc.
However, many people design Home Automation around activities they or the family are already doing. Turn on a switch, push a button, tap a wall mounted tablet, etc. And have those actions do more than happened in their "dumb house".
I'm in the first group.. my family has never been exposed to the man-behind-the-curtain of either ST or Hubitat. We have buttons stuck to the headboards of our beds to control the lighting and fans within. There's only one person that even knows where the Hub is located.. me, and I use a browser, as intended. Yes, I have created Dashboards, but don't use them much, thus choosing a more customizable one such as SharpTools or HousePanel exceeds my time vs interest calculation.
Therefore, for me, there's nothing to miss. I hated SmartThings Mobile App because it exposed all the admin functions to every user. Hubitat distinctly differentiates Admin (the browser interface) and User (Dashboard), and that's a big important feature, to me.
If you have v5.3 of SmartTiles you can get that working on HE. I edited the code to be an exception dashboard that shows me doors open, lights on, locks unlocked, etc since that is usually what I care most about.
I really want a local-only solution. I've been using ActionTiles for about a year as the interface in which most people in the house interact with StartThings. Myself I use the SmartThings app daily. It's a vital tool for managing such a large system. I'm struggling with a viable replacement that doesn't require a ton of work to get started.
The built-in Dashboard would be an otherwise decent choice, if the it were were customizable. I'd be perfectly happy to even design my own tile templates. As it stands, it's too rigid and inflexible right now. Sharptools looks interesting but I'm on a "crusade" against using cloud services for vital parts of the system.
I hate the ST mobile app, but it's a necessary evil for such a large system. Whether I'm turning off devices that failed to respond to automation, manually turning on lights just because, or checking some of the advanced telemetry I collect from custom DTH's for UPS's, Raspberry PI's, Windows servers, even Iris Smart Plugs Z-Wave radios. Those are all DTH's that have a UI that is not supported in HE, which I need to find a solution for. Having customizable tiles in Dashboard would be a huge help.
I'm considering this. I may also enable the MakerAPI and just create my own at some point too.
Don't get me wrong, I am really enjoying working with Hubitat. I've already moved over 50+ devices which were cloud-connected as well as my Hue lighting. From an automation perspective, I'll be able to achieve everything I'm doing now plus a lot more. From a user-interaction perspective, I'm struggling to achieve a reasonable WAF.
One of my biggest issues is the lack of the power attribute on switch tiles. I've got over 50 SmartPlugs total and use the power usage readings now and then to confirm things are working properly. I now have to define 2x tiles for those devices.
You can layer tiles on top of tiles. So those are image tiles with switch tiles stacked on top. Then changed the switch tile template to be transparent when on and opaque when off.
You add image tiles like any other tile, except there's no need to pick a device, just the image template. Then you paste in the URL of your image. The tricky part is finding (or modifying and rehosting) an image that fits the size of the tile you want. Until we get the ability to choose fill/stretch type options, the image gets resized every time the tile size changes. It's also a PITA to layer the tiles, you have to create them in the right order since there's no way to "send to back"....the newer tile always goes on top. So lots of planning and/or rework, but still doable.
Quick update... I've hit the halfway point with 205 of 408 devices migrated off of ST onto HE. I've focused exclusively on Zigbee devices at this point except Iris plugs and for 3 GE in-wall devices for testing. Most devices have paired without any issue. The exception is that some of my oldest Iris contact sensors put up a good fight but everything else has been fairly easy.
The two biggest improvements for me after migrating....first, no outages, whether internet connection related or platform outage related. Second, the response speed is incredible. No more issues being halfway down the hallway (or even all the way through) before lights turn on, etc. I never would have dreamed in ST about being able to issue 10 consecutive commands with 1 second delay between each and have them execute with any degree of accuracy.
Your advise is sound. I actually have a sizeable pool of spare devices right now, thanks to holiday sales, so I'm currently working on test pairings with the HE hub. I'm also running trials ofg pairing them with ST then unpairing, and pairing with HE, to get an idea of how each device will respond, and which ones need a battery pull or full reset. Its very time consuming, but will save a big headache in the end.
