I don’t know exactly what is planned, but I presume the idea is to deal with the problems caused by allowing device handlers to define their own custom attributes and commands with no formal definition. Sure the attributes are pretty well defined in terms of possible values, but the commands only have a name with no indication of the parameters they can take, and both could be completely differently defined somewhere else.
It is not that webCoRE has any greater access to these things. It is just that as a third party product it can use de facto standards (like arrived() and departed() as commands for simulated presence), and it is in a better position to ask the user what the parameters are for the other custom commands the device says it supports.
On top of that there is the issue of the UI to be used for the commands and attributes. The Classic app could have a custom one defined in each device handler, the ‘new’ app is pretty much hosed as there is nothing for it to work with.
If we take the simulated presence example, what is really needed is to be able to define e.g. ‘Simulated Presence Sensor’ as a capability with the commands arrived() and departed(), and whatever is required so the mobile app can display a couple of buttons to explicitly set presence, all without having to ask the user what is going on.
Custom Capabilities is an important one for me to fully transition. For example, light bulbs that have a color loop mode or blink mode. We need a way to turn those on and off in the new app. Recently, anything that uses “standard” capabilities seem to work fine in the new app.
Keep in mind that we’ll also need to monitor and use those custom capabilities in the rules engine before we can get rid of third party apps like webcore.
Way to go Samsung to ruin a good thing. I am one of those advanced users that has many custom device handlers and smart apps, from this community and my own, and none of them work in the new SmartThings app…not to mention its the most poorly organzied UI I have ever used. Ugh.
There will be time to make sure that custom capabilties and devices are supported before you need to migrate. Only a tiny fraction of users are even given the suggestion to move now. We are taking all feedback into consideration.
what are you going to do with customers who CANNOT migrate to the new app because the app has problems (verified by samsung support) and the user cannot even log in, let alone start any sort of migration process?
I’m new to ST and of course downloaded the App, but when I tried to download the App on my tablet it only let’s me have the classic one, I do like the classic one but I’m I going to lose this and then can not use my tablet, if I do anything a the classic is it going to just go? Should I stick to timers and things on the new app, Thanks
I kept getting emails that 10/14 was final day to migrate. Well I did it most of my devices are OFFLINE now after I used them once on new app. Deleted downloaded classic same thing. Deleted and retried now devices are just off line on both classic and new app. I’m stuck.