Does persistent "Get Started" with SmartThings means it's broke?


(Mike) #1

I got a v2 ST hub and installed it a few days ago. I think I got interrupted in the middle of first starting up, but everything otherwise works okay, shrug.

However, I keep getting a home screen with a “Get Started” text balloon in the upper right (see below). I can’t click on it; it’s grayed out and clicking doesn’t do anything. It shows up about two seconds after loading the ST home screen, and there’s no way to get rid of it when on its home screen. (But only the home screen; it doesn’t appear on other screens.) Like this:

As you can see, there isn’t otherwise anything happening on my home screen. But is this normal? Shouldn’t my home screen be telling me status of things? Do I really have to drill deep into ST over and over to see what’s up? Not counting notifications - I am getting them, and in one sense, that’s the main thing. Still, any time I tap on a notification, it brings me to this home screen, which doesn’t tell me anything, and Getting Started persists.

This doesn’t seem normal. Will the Android app say “Getting Started” for everyone (all you) forever? And not give any other status info on the home screen, even when you get there by tapping a notification?

I can’t help but think the app got confused when I interrupted my initial ST setup.

This is on a Nexus 6P. I downloaded the app three days ago.

Thanks if you can help!

(Eric) #2

sounds like the kind of situation where I would go to Android\ Applications\ App-manager\ SmartThings\ clear-data\ clear cache. In hopes of not deleting the entire app to start over.

(Mike) #3

Thanks Eric, listen, can you confirm for me that the ST home screen should be doing more than that? So I know if I’m missing something.

It’s stuck on that one home-in-a-circle graphic, without showing any actual house status info. Should it be showing status info?

It seems awkward to have to drill down to “Things” to see what’s happening in my house all the time. (I am not interested in setting up Rooms per se.)

(Eric) #4

my suggestion to clear-data is just a guess.

My phone app home screen shows “smart home monitor” (SHM) with “live” status, which seems to be functioning as intended. I also have a couple legacy dashboards that a new user will not see. In practice the legacy dashboards are NOT adding useful information.

FYI IMO SHM will ALSO not add much convenient insight to what is happening in your house. When I look, I usually look at Things and Rooms. I prefer to not operate my house with the smart app. I am most satisfied with SmartThings when I do not have to manually intervene. Admittedly my expectations and dependence is low.

(Mike) #5

Thank you very much, Eric. I actually tried Wink before this and while it had a nicer home screen (showing status of everything) and some other nice points, I found Wink less flexible in the really important ways that matter to me. (Push notifications and developer and community involvement.)

When you say you prefer not to operate your house with the smart app, do you mean you have something else to operate it with, or are you just saying (as you did in your next sentence), you don’t really want to have to operate it at all.

I can definitely empathize. Although at this point right now I am just in new/learning/test mode, which is sure to be more intense and quite different from S.O.P. situation.

I might add, I am surprised to find how piecemeal and awkward all the DIY smart home systems seem to be, each in their own way. There’s no clear winner; it’s more like, choose your poison. But then I guess that all the hard work is really under the surface. And we really can’t forget that it’s a highly competitive marketplace (= little money for them to build cadillacs).

(Eric) #6

SmartTiles is a third-party dashboard that I use to view selected device status. There are a few commandable devices in it, that I avoid commanding. If you search you can find many references to SmartTiles.

my last comment is that you may have better results by avoiding time scheduled actions in ST. By using event-and-sensor-driven actions instead.