I initially thought that but really found the old DTH setup was too slow. I originally migrated to Hubitat and HA but I find Hubitat slows down and regularly has to be reset.
I am actually fairly happy with the new edge drivers and have moved some stuff back to Smartthings that I had migrated away. I think these new Edge drivers gives Smartthings a new lease of life.
Smartthings is āvalue addā nothing more, nothing less.
Modern devices such as phones - have or are nearing a zenith of development, camera quality is very acceptable, phone speed is very acceptable, different sizes of phones are available so how do you keep selling your products ? By adding value add software on all of your products
If a few people get burned along the journey it is regrettable but unavoidable. Corporations need to sell products, no sell, no money, no Smartthings.
Smartthings has been a corporate addition since its purchase by Samsung, it is less hobyist and more mainstream, i have been known to grumble here and there about the UI which is poor in multiple areas but i understand the world we live in, more over i am very pleased to hear a new app is being developedā¦ lets hope it is an improvement, i may be alone on this but i look forward to the future and if i have to reset some devices i am sure i will manage.
Yeah I agree.
Iāve tried HA with some success but itās alot of work.
If ST doesnāt work in the new year then itās hubitat. Iād say the grass isnāt always greener though. One thing ST does very well is simple control and automations.
Iāll admit, Iām curious to see if SmartThings releases Matter support before the final Groovy shutdown, and if so, whether that makes any difference to customer satisfaction.
It should mean lots more inexpensive devices running locally to choose from, without requiring custom code. RGBW LED strips could be a good example. Or being able to bring in Aqara devices by adding their hub, again without needing custom code, adding to reliability.
Unfortunately, since Samsung has chosen to support only a one way integration with Matter (you can bring Matter certified devices into the ST app, but you canāt add the ST hub to other Matter certified controller apps), we wonāt get to take advantage of more available rules creators in the same way. 
But stillā¦it could be an interesting plus for the ecosystem as a whole. Again, though, it doesnāt help with zwave devices.
Has there been any discussion about what will happen with devices not successfully transitioned? Will they remain in the device list, but be non-functional and allow the user to try and apply an edge driver, or will they disappear? The former seems easier for us non-power users. The latter sounds like a huge amount of work.
The understanding is it will be given a designation as āThingā which keeps things the same as the present naming convention for items not immediately given a driver that matches
What attributesā¦ if any, āThingā will have i am not sure
For ZigBee and Z-Wave devices it is possible to create a fingerprint that will match any device. as far as I can tell, Zigbee devices will migrate as a āZigbee Thingā, which just has the refresh capability, and Z-Wave devices will migrate to the Z-Wave Switch driver using the switch-level profile which supports switch, switchLevel and refresh.
So is now the time to create more location modes while we still can? Iām assuming that when all the dust settles in December and January, we will not be able to create anymore.
At this point it probably will not hurt to have some spare location modes, I created some last week just in case.
Rebooting the hub is also one of my concerns, some have suggested adding a wifi outlet, but what if you need to travel 1200 miles to do that?
In 5 or 6 years i have rebooted deliberately maybe 3 times, we have had the occasional power cut over those years
A wifi plug is an option at distance if you are concerned though but dont forget they are less reliable after a wifi drop out than zigbee or zwave
Thatās disheartening to hear. Which ST hub are you using (I have the V2 and donāt consider it very good in this regard)?
I havenāt noticed any if these problems in the last year. The database getting full was the only one that really annoyed me as I did need to restart the hub occasionally and occasionally press an extra few buttons to repair at boot time. (Also surely with a mesh network the quality of the antenna doesnt matter much? They are regulated/recommended by Zwave so Im surprised there is much variation)
However the last 12 months I havenāt had to do anything and itās been absolutely rock solid. Updates are seamless, the features are so rich, and the community is building some awesome things whilst being very responsive. Touch wood, not a single hiccup.
The app is the one area of weakness but there are so many great alternatives that I have no regrets at all about hubitat. Happily recommend it to everybody now, even totally non-techy people if they are interested, as itās easy to learn.
Whats the process for creating device handlers in hubitat?
You can either copy and paste code (exactly like the Groovy web IDE here), or there is a search app (hubitat package manager) which will automatically install drivers that you find from search.
For actually writing them, itās also the same as ST used to be, but there wonāt be many things that havenāt been written already. Rule machine is the most advanced tool to do so many things without having to actually code.
I have 3 V2 hubs. When adding Hubitat C7 in the same locations, zwave and ZigBee signal levels were much lower. Especially zwave. The antenna mod mentioned over in the Hubitat forum has many rave reviews and makes the performance better than most.
It definitely matters. On C7 I had many devices that would not connect directly to the hub vs ST. After the antenna mod people on the forum say most devices now connect directly, no hops. And at 100kbps. I donāt think the zwave alliance tests relative antenna performance on any devices, it just has to communicate at a basic level.
I agree and as I did said there are many many pros for going with Hubitat. I was just saying itās not perfect and there were things I felt I lost coming from ST.
They can be created using the API. A POST to https://api.smartthings.com/locations/{{locationId}}/modes with body { "label" : "{{Name of new mode}}" } should do it.
Iām a little surprised they havenāt made it to the CLI yet, but I guess they have lots to do.
I just went into the IDE and made some for future use.
The first notice of a deadline for the death of Groovy pushed me to taking action on migrating to a new platform. After some research, I settled on Home Assistant. The migration of all my Z-wave and cloud connected devices took probably a few effort-days, and more importantly, my wife is perfectly happy with the new automation.
To your point about frustration, moving to HA after years of dealing with the vagaries of SmartThings was like opening up all the windows in a house that had been shut down for a year. The transparency of automation and operation was almost ā¦ breathtaking. Everything is in code you can see, everything (e.g., device and entity states) is inspectable through the local web UI, and everything is logged. Itās all running locally except for cloud integrations. The community is very active, and there are integrations and templates for darn near everything.
Even better, there is an actively-maintained integration with SmartThings, so you donāt have to migrate all devices at once. In my case, a few Zigbee lights are on Still on ST, and the integration works well enough that Iām in no rush to migrate them.
There is a downside: You have to be comfortable with using or at least reading the YAML language for many configurations. If youāve ever dealt with Groovy, YAML will be a snap.
I donāt want to hijack this thread to talk about HA, but feel free to DM me for more experiences.
I tried HA.
Itās brilliant. But it also has issues such as configuring external access which proved a bit of a nightmare when I had local devices connected via WiFi.
The process for creating routines is just not as easy and itās very much community based.
Lastly, I had to run a pc which took alot of juice and my old NUC couldnāt handle that plus anything else.
If Iām going to buy new hardware I think it would be hubitat.