Yes it seems the Replace button is gone.
I just did the transition, only had 4 automations. The transition completed ‘successfully’. But the new app automation points at presence sensors that don’t ‘exist’. Except they do, of course.
It is treating presence sensors as a general device and I had to manually repair each of the 4 automations the transition created.
As it sees it as a device instead of a presence sensor the ‘after x minutes’ options are no longer available. They are available to mobile presence.
It’s a mess! I had a very simple home to transition and it’s a 4/4 failure rate on automations.
@blake.arnold Can you give us updates on the fixes for these from 8 month ago?
Automations with a presence condition only seem to work half of the time if you are lucky too.
This is getting to be horrible and I’m about to just give up and switch. Support has been useless if they even get back to you.
I spent my morning writing an automation so that I can get a notification if I left my garage door open after it has been opened for 5 minutes. This used to be a default automation in the old app but was removed in the new app. Anyways, because the link support sent me I wrote it for the old app. Now that I want to move it to the new app I see that I have to get aws lambda or jump through hoops on my website? This is 1 step forward and 15 steps back.
Me too. Years of ups and downs and I’ve never so close to pulling the trigger on a Hubitat hub. Only thing holding me back is I’m already at my limit at dealing with home automation and re-pairing all of devices and automations in a new ecosystem is too much to contemplate.
This looks like it should work but again the point is these are steps back where there is another ecosystem to manage instead of just being able to do it natively in the app like you used to be able to do until dumbthings removed it.
I know I’ve given up. Stripped my ST hub down to be a basic Z-wave / Zigbee controller, letting other things handle the automations until my Hubitat gets here. Been here since the start, but this was the final straw. ST support has been garbage and takes way to long to get an agent who is capable to actually help with something more advanced then just uninstalling/reinstalling the app. This migration was a joke and should have never been pushed on us until it could handle everything we could already do.
I purchased a Hubitat C7 a few weeks ago and am in the process of migrating. I was a long term SmartThings user and really loved this system, but I’m sad to say I’ve lost faith in it, and in the direction the owners are taking it. Frankly, the first couple of days after I got the Hubitat I though I had made a mistake. It takes some getting used to! But now after several weeks I couldn’t be happier, and seeing and experiencing all of the latest ST outages and this complete mess of a migration, and knowing there are much bigger and messier migrations to come next year… I’m glad I’m out. I hope in a few years the growing pains are over and I can consider using whatever ST has morphed into sometime in the future. But for now I see only retrograde steps, upsets, outages, and frankly nothing that makes me feel excited. With Hubitat I see a team of enthusiasts, an exciting product, and a sense of direction. It feels fun again.
Thanks @DThompson10 your experience gives me hope that I’ve made the right decision.
I’m considering making the same move as I just can’t get any of my devices migrated to the new app. No idea how, no examples, templates or documentation that I understand (and I consider myself reasonably technical having written 6 different devices handlers!).
The biggest thing that’s pushing me is that every few days my LAN connected devices stop updating and all changes/updates are lost from this point onwards until I restart the ST hub. Totally lost about what is going on but my home is certainly not smart any more, just incredibly annoying!
Have you posted your questions here? Custom Capability and CLI Developer Preview
2 posts were merged into an existing topic: Alternative Hubs
Does anyone know how to create a virtual switch in the new app?
Apparently I need a dozen to get everything working again, and the ones I created with ‘Alexa virtual device Creator’ are not usable on the new app!
Then when I try to do it the old way in the soon to die IDE it says.
We’re sorry, but you are not authorized to perform the requested operation.
I know - I just don’t get why they can’t just add the information - it’s incredibly annoying not to have the ability to know why something happened (Yes, I know I can go to the IDE - but that’s not the point).
I figured this part out at least
I Had to use incognito mode on the web browser
Yep. And why this is necessary sometimes has never been explained. Just another frustration.
With all these changes I am trying to use Modes to help coordinate changes between STHM, new Automations , Webcore and ActionTiles
-changing mode names in new app does not update the modes for my location that show in the IDE. Also changing them in IDE didn’t update new app either. Neither seemed to update ActionTiles
-would be nice if the current Mode showed at the top of the new app home screen in the under-utilized empty space (between location name and temperature maybe???)