Just got a push message to my iPhone telling me to try the new App

Yeah I can see how it can be misinterpreted, I read it the way they apparently intended. It is not the best wording.

No, the current app is ST Classic.

Yea I know that. When they are referring to a “new” app, are they referring to the current state of the Samsung Connect version as being new? Or will they be updating that app so it doesn’t look horrid.

Samsung connect app —> (new) SmartThings app.

(Old) SmartThings app —> SmartThings classic.

@jody.albritton: “The current IDE, community apps, etc will be around for a while until we have a truly better replacement for them. This community is important to us and we are listening to you.”

Questions:

  1. What is “awhile”?
  2. The new ‘classic’ app is crashing in many instances with a variety of custom device handlers (such as Bravia). Will we be forced to update to the new classic app? Or will version 2.13.0 (1431) continue to function for awhile as-is?

What do you mean by “new classic app”? There is only one classic app. The new app, also called samsung connect, is the one that should not be used till you’re told to do so.

What version is the ‘classic’ app?

It’s newer than the ‘classic’ app I’m running. Presumably if there is a ‘new’ app that is different than the ‘classic’ app, and the ‘classic’ app is an update of an existing app, then the older version is also ‘classic’??

:grin:

I’m not using either the new Samsung app, or the ‘classic’ app that is now on the App Store.

Ya they just relabeled it Glen.

The old ST app that we have all been using is now just simply called SmartThings Classic.

Current version is 2.15.1

Maybe that’s why it’s not working . Update your app. :smiley:
There are only 2 apps…SmartThings = SmartThings Classic and NEW SmartThings = Samsung Connect.

Maybe you mean to say new VERSION instead of new app?

Current version, by multiple accounts, is working less well than the version I’m on.

I just wanna be sure that, this being the case, I’m not gonna be forced to 2.15.1 when my 2.13.0 seems to work better.

What? Who says the current version isn’t working better?

Yep, I hear ya. But the functionality issues this last month have mostly been from the cloud itself, not so much the app. The app functions exactly the same way.

And you know how they do things. It’s possible that they change things so that backwards compatibility breaks your 2.13 :smile:

If your stable it’s all good, but I dont think you have any worries with updating the app. I would be more worried about firmware at this point.

I see posts from folks who updated to ‘classic’ saying stuff like their app is crashing when they try to access a device. Such as denon.

Mine is not crashing in that situation.
By definition, an app that is not crashing is working better than one that is crashing.

Can you link to one of those posts? I just did a search and cannot see anything.

I apologize, it’s not the Bravia but the Denon. Will edit my previous post.

Look at the posts from thedude101 and dpdurst

If you are working, I would just leave it alone until it does break. Keep Auto updates off. And definitely leave the new app alone as well. Don’t install, don’t update, don’t run it.

They aren’t adding much to current/Classic app anymore as they ramp up to complete the new one, whenever that might be.

That’s about the new app…Samsung Connect. Not everyone else is going by your naming convention, that’s why I tried to correct you.

Then perhaps you should have read what I posted, and noted that I was making a distinction between the new Samsung app, the new classic app (which is what I called it when you presumed to correct me), and older versions of the app befor presuming to ‘correct’ me. I referenced “New classic” as a different entity than the “new app”. Thought that was crystal-clear, but apparently not… tell ya what. Tell me exactly how you believe I should reference the three entities, and i’ll Do it so as to avoid confusing everyone.

New Samsung app = ???
Classic app = ???
Un-updated ST app = ???

Anyway, this is all reminding me of the whole Coca Cola fiasco a couple decades ago.
New coke came out.
That had market problems, so they re-released ‘classic’ coke.
If you had an old can of coke with neither label on it, what exactly was it?

Coke, v 2.13.0?? :grin:

1 Like