It may always take you there, but that would only be if you have an account on the first shard. People with newer accounts will find that that URL does not work for them.
When SmartThings went for sale in the UK, they added the first of what will be many “shards” to split the SmartThings Cloud workload into multiple, somewhat independent, clusters of servers.
SmartThings automatically replicates a lot of stuff between the shards when they deploy updates and so on, but if you are doing development and you Publish “For Me”, then you need to be sure to be logged into the correct shard, or your self-published SmartApp or custom Device Type Handler will not work. You won’t find it in the mobile App!
Eventually you may not need to know your shard. Eventually, SmartThings may make this process automatic and when you self-publish, it will go to the “right” shard without intervention.
Update:
The URL: https://account.smartthings.com should take you to your correc…
As far as the “ghost location,” that sounds like somebody who is using their Samsung ID (instead of their smartthings ID) for the first time. See the following:
The issues
The following are some issues experienced by users after migrating from a SmartThings account to Samsung account or by users who have previously added Samsung Appliances and TVs to the Samsung app/account before they had migrated their SmartThings account. Note: Samsung can implement this migration without you realizing it. They don’t send a notification before or after the actual migration event.
Devices are missing in the Classic app.
Hub/Devices are missing in the Classic app and you are prompted for the Welcome Code to add the hub.
Devices do not appear when you login to the SmartThings (Samsung Connect) app (STSC).
Two duplicate locations in IDE and unable to delete the empty one.
Hub and most devices are in one Home Location and Samsung Appliances and TVs are in another…
2 Likes