If you do, like I did, you will get an obnoxious pop-up window, which completely obscures the SmartThings dashboard, cannot be closed, and makes SmartThings Classic unusable.
And if, like me, migration to new Samsung SmartThings App is impossible because of region issues, you will end with $xx00 worth of SmartThings junk.
Once more, SmartThings has shown its very peculiar version of “upward compatibility”, except that this time it looks like the final end of the road.
Once more, SmartThings has shown its total disregard for early adopters (August 2014), those same adopters who enabled SmartThings to stay afloat up to now.
Disappointment is way too weak to describe my feelings towards this betrayal which annihilates literally MONTHS of work on SmartThings (I developed my own custom handler for a Fibaro Device initially unsupported by SmartThings) and makes $2000 worth of Things a gross pile of junk.
I apologize for posting this warning way too late for most people trapped in the same quagmire. Up to now, I thought my difficulties were a simple problem of migration, but after a dozen of exchanges with SmartThings support, I realized it was deliberate.
This is a dire warning not only for early adopters but also for all home automation fans : the so-called “standards” are not stable enough to ensure smooth upward compatibility, the cloud-based solutions give all the power to the cloud masters and big companies like Samsung (or Apple, or Google, or…) will always optimize their bottom line first, and treat “marginal” customers like collateral damage.
I suppose a talented US lawyer could see there an opportunity for a juicy class action suit, but although the same concept exists in Europe, the likeliness of winning and the local number of SmartThings customers is way too low.
Thanks anyway to all SmartThings community members which helped me with my set-up and which used my custom FGK-101 Handler, keeping it functional up to now. It was nice iterating with all of you across the Atlantic, sharing a common passion.