I have no idea what that is and it’s dang sure not the “main” problem…
The Robot Cleaner Cleaning Mode capability can display on the device details page without an explicit VID. I tested it this morning, out of curiosity.
The VID seems to be more about explicit control of which widgets feature on the device details page in which order, and of the icon, action and status used on the tile. I rather assumed that the VIDs have been manually or semi-automatically created but that aspect of things really isn’t clear yet.
The VID Selector tool raises as many questions as it answers because there is no context for it.
1 Like
I just picked a device handler I had, which was just implementing a virtual button, and added capability 'Robot Cleaner Cleaning Mode' to the metadata. As is usual with device handlers for the new app, I then initialised the attribute for it using a sendEvent( name: 'robotCleanerCleaningMode', value: 'auto' ) in the installed() method and updated the device.
The device details screen then showed a widget with a number of black on grey text buttons on it, which I assumed were the various modes.
I do sometimes think the new app makes it up as it goes along though.
1 Like
Thanks for the laugh this morning! 
3 Likes
The Vid Selector tool exists to help get older groovy implementations onto the new app. Something like a robot vac would go through our developer portal as a C2C integration and it’s UI would be generated there based on capabilities. The main pain point the VID selector is there to solve is the one for developers of hub connected devices. There is no alternative for groovy dth’s when it comes to hub/lan connected.
3 Likes
The forward-thinking approach would be to use the developer workspace.
Mine too man. Delete it reinstall and it works for a few then out again. Smh.
@Brad_ST Can everyone use the new developer workspace? Or is it only for companies approved by ST?
@Alyc100 is it possible to do something like the above for Neato in the new app?
Definitely will look into it
1 Like
Your car is people? Soylent Car is people!
9 Likes
Wait, am I seeing that right? No more workaround for location mode? Yay!
1 Like
Your eyes do not deceive you!
2 Likes
It’s rolling out on Android right now. Another example:
5 Likes
I’ve been looking forward to these changes for a long time, as have many others. Thanks for sharing this info.
3 Likes
Any update on when Scenes will be properly integrated with Webcore, Actiontiles, etc?
That’s up to them to implement, but will probably require them to re-write their application to work with the new API.
https://smartthings.developer.samsung.com/docs/api-ref/st-api.html#operation/executeScene
1 Like
Double yay! 
4 Likes
You should keep in mind that building an unspported integration on top of an unoffial Roomba API could, and most likely will, break at anytime. I would encourage you to take a second look at the developer workspace and building this out as a C2C integration given that you already need to run a server locally. All of your code could exist in javscript without the need for groovy. Even saying that, expect things to constantly break when building on top of unsupported features. The currently capabilies are probably not going to change before going live, but they could so keep that in mind too.
1 Like