Appreciate that it has been covered so many times … just wonder why such a simple and obvious design error can’t be corrected … I can also kvetch about cloud first. I just came home to find there had been a power outage so all my Zigbee lights were burning brightly. But one consequence is that my Internet connection had flaked so I couldn’t do anything about it until the lights had come back.
Not all is ST’s fault since DHCP dependency is another problem thus breaking Wi-Fi.
tgauchat
(ActionTiles.com co-founder Terry @ActionTiles; GitHub: @cosmicpuppy)
22
The problem is that SmartThings has not declared it to be a “design error”, let alone an “obvious” one.
Read through that thread (or related one(s)) … the CEO himself, Alex Hawkinson, who – to be very clear – we appreciate keeping an eye on these Forums and chipping in some really helpful comments … said, QUOTE:
“On device tile labels, that’s been quite the debate internally over time.”
(i.e., In my opinion, tile label issue can’t be consider a “bug” or “design flaw” until the “debate” has been settled – and it’s been a couple years and counting, with no resolution in sight …).
The Cloud dependency has also been a concern of the Community from the very beginning of ST, but certainly that is a debatable issue and a fundamental architecture decision was made – AND this one has a resolution plan (SmartHub V2, releasing Q2 2015).