After Receive hub V2, I decide to say good bye to smartthings

[tgauchat (ActionTiles.com co-founder Terry @ActionTiles; GitHub: @cosmicpuppy)]

@cgrotal

but ST can let user save all the logic and setup for the hub. let user just delete devices and add devices, and all the apps come back to the new hub.

Sure could…

Migration to V2 - Hurdles and Best Practices

There’s no reason that the back-end data couldn’t be 100% cloned from 1 Hub recordset to the new one. – All that is needed is to create a temporary set of Device Records, if foreign key constraints can be temporarily disabled during the account’s migration. I’m 100% serious: Given full access to the SmartThings device Cloud database for a single account… Very rough pseudo code / sketch: Lock the account and database for migration mode, limiting what functions may be performed; disable foreign key constraints. Add a friendly alternate candidate primary key – heck, use the Label Attribute (e.g., make the user ensure all the Things have a unique name by using the existing Properties/Rename function in the UI). Add a temporary column to mark “devices set for replacement”. Remove the devi…