Not sure that’s necessarily true.
How much would it cost them in development hours?
How many users have avoided upgrading for this reason? Certainly there are plenty around here (myself included) but this community of power users isn’t very representative of the entire ST user base, in terms of number of connected devices and complexity of automations.
I think you’re looking at this backwards. The average user not being a power user and being told they have to start fro scratch if they upgrade may be the reason they don’t upgrade. If I put in SmartThings just to do doors and some lights (easy stuff) and then a new one came out with more features (i.e v1 → v2) but I was told I’d have to set up everything from scratch I’m probably not going to bother unless those extra features are really worth it. If I was told you just plug in the new hub, go into the app, discover it, and it would move everything well then I’d be a lot more likely to upgrade.
Sure that’s entirely possible too.
Other threads have mentioned the number of devices the “average” user has but I can’t seem to find that at the moment. But IIRC it’s on the order of about 12 or something.
Personally I wouldn’t hesitate to start over from scratch if I had only 12 (give or take a few) devices.
But maybe the non-power user is unwilling to tolerate anything other than plug-and-play when it comes to upgrading, that definitely could be the case.
All I really meant was i don’t think it’s a slam dunk by any means that developing a migration tool is financially the right move. One would hope they put some thought into this, disappointing as the decision was.
A very synical…
I still dont folllow why this is differnt. the way it was explained to me is that my hub didnt have enough memory to upgrade due to the way the firmware handled memory… You were fixing this with newer firmwares… If that is the case you should be able to upgrade via cable or whatever just like you did johns hub? If not are you saying that there is actually a hardware fault in the hub if so this is the first I am hearing of that.
“Not enough memory” is not quite right. To make an analogy to a desktop computer, your Hub’s “hard drive” has “crashed”. Except that in the case of the storage for the Hub (a type of storage call eMMC), when it fails, it is still possible to read from the memory, but not possible to write to the memory. Once in this state, there’s no way to recover, so we replace it.
These types of failures are rare but possible. The dirty secret of math is that you can have something that happens only 0.01% of the time, but multiplied over large numbers of devices there will be failures. So for example, you can have an eMMC that is 99.99% reliable, but that still means that there will likely be 10 failures per 100,000 devices.
On the migration tool - engineering 100% wants to do it and absolutely wants it. I’ll leave you to infer where decisions against it are being made.
Guess it’s time for me to update my 3 star App Store review that previously focused on the lack of entry/exit delays and keypad support in SHM!
Thats what i did…
Yes, please do! I received an email response from ST Marketing (I think!) within 24-hours of a less-than-stellar review I posted on the App Store. Public embarrassment is something that will cause some folks to wake up and take notice. Sad it has to be that way…
Marketing drives Product Management, which drives product specs/schedules, in my experience. Engineering is held to the product specs & schedules — once a company transitions from startup to maturity. For better or worse! 