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).
Segregation. We now have separate lists of “Classic” app and “New” app capabilities.
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???
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???
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.
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.
1 Like
RBoy
(www.rboyapps.com - Making SmartThings Easy!)
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).
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.
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.
1 Like
RBoy
(www.rboyapps.com - Making SmartThings Easy!)
13
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.
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.
