Major changes in Capabilities for Classic and for the new


(Dave Gutheinz) #1

It appears that SmartThings has some major change in their capabilities reference that have not been advertised (or as usual, I was taking a nap).

  1. Segregation. We now have separate lists of “Classic” app and “New” app capabilities.

  2. Sunsetting. In the Classic, a lot of the previous “live” capabilities in the classic are now “dead” (i.e., bulbs, lights) or depreciated (i.e., music player). In the new capabilities, these capabilities no longer appear!!!

Not a real problem, but definitely a nice to know going forward.

Question: Will the classic capabilities have to be reconciled prior to going to the new app???

Dave


(Dan) #2

Very interesting. I especially like how “Button” and “Holdable Button” are both deprecated in Classic, and completely missing from New.


(JIm) #3

Since I don’t fully understand this stuff, forgive me if this is a dumb question.

I have written a couple smartapps for my own use. Where I wanted to know the current status of a switch or light I used device.currentswitch or device.currentstate.

Looking at the capabilities now I would just use device.switch???


(jkp) #4



(www.rboyapps.com - Make your home your butler!) #5

When you say change in capabilities are you referring to the new Samsung docs vs the classic ST docs?


(Dave Gutheinz) #6

Yes. The capabilities do not match between the two. Additionally, with it’s reappearance, the classic documentation has some previous Live capabilities now Dead or Depreciated. I think this impacts smart apps going forward (since they often detect devices based typically on capabilities). I do not know how a “dead” capability would impact a device handler with the capability listed.


(Dave Gutheinz) #7

Additionally, the depreciated capabilities on the classic documentation are NOT in the documentation for the new app (a week or so ago, the lists were the same). Capability polling and refresh may both be going away.


(www.rboyapps.com - Make your home your butler!) #8

Another piece of news: the Contact Address book will no longer be available after the migration to the new Samsung account (for those who had it with ST Classic, it won’t be migrated and there’s no way to re enable it).


(Jimmy) #9

Not quite true at present. I was migrated to a Samsung account and am still using my contacts, but I did have to set it up again. It’s available in the new app if the smart app supports it. I’m guessing it will totally disappear when the Groovy IDE is depreciated.


(Keith G) #10

Someone is asleep at the wheel. From the Classic App supported capabilities list:


(Jimmy) #11

Is everyone referring to the Groovy IDE as Classic App?


(Keith G) #12

The IDE isn’t mentioned, just the mobile app version:

There is still no official documentation on developer tools for hub-connected devices on the new IoT platform. So as far as I can tell, for now, we’re still exclusively working with Groovy smart apps and device handlers.


(www.rboyapps.com - Make your home your butler!) #13

Can you share a screenshot please?


(Jimmy) #14

ah, i see that now. not sure if I have any devices using deprecated capabilities to test with the new app.

here is the screen in your Door Lock Manager smart app using the new app



(www.rboyapps.com - Make your home your butler!) #15

Awesome thanks. Just to confirm, you’ve migrated your account from SmartThings to Samsung, is that correct?


(Dan) #16

Just going to leave this here…

Deprecated is normally used today for some feature of a computer language/platform which is still supported, but no longer recommended. It may not be supported at some time in the future, because it doesn’t fit well with the way the language/platform is being developed.

Depreciated, on the other hand, derives from Latin pretium=price. It’s used of things which have reduced in value (typically monetary value) over time.


(Jimmy) #17

yup, was in the Beta many moons ago. Wouldn’t be able to access the new app without a Samsung account.


(Dave Gutheinz) #18

Concur. To a programmer it means do not use for new code and when updating code, replace. It is just the extreme number of items being depreciated that smart apps may use (i.e., webcore, ActionTiles, and others.


(Dan) #19

Yet, you keep typing depreciated instead of deprecated? :wink:


#20

It looks like I’m not the only pedant who dies a little inside everyone I see these getting mixed up :smiley: