Should I wait for v3 hub? (STH-ETH-300)

[Roguetech (John Roguetech)]

@Zach_Varberg

I mean, this is a lose lose situation for Nick or I to reply to in any meaningful way. We get yelled at for promising things that aren’t delivered yet, we get yelled at for not sharing enough information. Nick and I are embedded software engineers, we aren’t C level executives. We can’t guarantee anything. For the first time in a long time we are actually releasing new locally running functionality and instead of people saying “hey maybe they are working towards expanded local execution support” the response is “local execution is dead”. I think our release notes speak for themselves, but you can draw your own conclusions.

The issue isn’t whether or not there’s more local processing, or whether everything ever promised is delivered (within a decade). Frankly, the issue is that we never know wtf we’re going to get at all, such as Bluetooth. Samsung has managed both a lack of vision and customer service, and it seems to trickle down from the top. SmartThings should be the core of everything Samsung does, and leveraged to challenge Amazon and Google in automation. Instead of pushing their brand, Samsung “updates” tv’s to STOP working with ST, aren’t fixed in years, despite literally begging for a class-action lawsuit, never mind customer support on par with Comcast. Then releases a $300 electronic lock that’s not even “smart”. Hell, Samsung pushes an email telling us to get ready for an update that’s so incomplete, no one can say when we’re going to be left without which features (aside from cloud services for 3rd party apps… we know WebCore is going away or become a private subscription model… to rival Samsung’s products). If Samsung had their crap together, we’d not need to speculate about whether Samsung staff have any clue about what will happen tomorrow. We’d could at least be certain of incremental improvement.