mine also back up, as are the echo’s.
Then you and I are almost certainly on different shards. The shard that my account is on filled up in 2015.![]()
Most North American {SmartThings} accounts added before September 2015 will be on NA01. Most of the ones added in 2016 will be on NA02. UK accounts should be on EU01.
My hub seems to be back online but my Ecobee devices are not. Had to run the offline diagnostic on each one before they came back. Only go back offline a minute later. They are all showing in the linked services. Anyone else having this issue?
I am getting notices that ecobee is not connected. Shows as connected in linked services, but devices are offline.
Another post just popped up on, perhaps, the same issue…
Yep, my Ecobee just went offline and I got the disconnected notification in ST.
Thanks for the info.
I don’t think it was ever sufficiently communicated at the time that any user could create a Location on any shard via the IDE, and indeed if you were publishing device handlers and apps the intention was you did so on every shard you wanted to cover. I first joined SmartThings around 2018. At the time publishing had largely fallen by the wayside, if the account.smartthings.com address existed it certainly wasn’t well documented, and new users were being pointed at the ‘new app’ which wasn’t actually available on any device that I had. I probably created my account via the web and ended up with a UK account with my default Location on NA01. A second UK account I created later had its default account created on NA04 and later new Locations it created were on NA01. Only later still did my UK accounts actually start reliably creating their Locations on EU01.
I don’t really know how significant the shards are these days, though there are certainly some regional issues. For example, the Chameleon ‘Smart Meter’ couldn’t be installed into a Location on the NA01 shard, which prompted me to completely reinstall. I also have a server that usually picks up api.smartthings.com from Dublin, Ireland in the UK/EU region. However occasionally it picks it up from North Virginia instead. That stops the /schema endpoint being populated. It is still possible to see which shard your Location is on via the Client API.
That’s me taking the thread miles off topic though.