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

  1. Thread is an interesting addition since only Nest uses it
  2. no battery backup
  3. Connecting via wifi will make a lot of people happy.
2 Likes
  1. Only 5GHz WiFi
  2. WiFi not mentioned on the Quick Start Guide
  3. The bottom is purple!

Here’s another possible useful link (well… it may eventually be useful…):

https://wikidevi.com/wiki/Samsung_SmartThings_Hub_v3_(STH-ETH-300)

1 Like

image

2 Likes

Sign me up for one! :slight_smile:

2 Likes

There are two completely separate Threads at this point.

“Nest Thread” remains proprietary to google/nest.

However, about 3 years ago Nest donated rights to an open source version, now called just Thread and managed by the thread group, of which Samsung was a founding member.

https://www.threadgroup.org

https://www.threadgroup.org/thread-group#OurMembers

So far only chips have been certified, but there are about a dozen different ones, including from ARM, NXP, and SiLabs.

Same frequency as nest thread (but then, so is zigbee), but a different protocol.

Eero and Legrand are supposed to both have projects in the pipeline:

https://www.threadgroup.org/news-events/press-releases/ID/177/Thread-Group-Sees-Strong-Adoption-for-Networking-Protocol-Across-IoT-Ecosystem

None of this means a SmartThings hub will actually end up using thread for anything, but it’s a separate initiative than the nest communication protocol. :sunglasses:

3 Likes

It looks blue on my screen.

But they can change the color without needing to recertify so who knows…

1 Like

I wonder if the molded in logo will also change? That’s the old logo vs the current multi circles logo

2 Likes

My guess would be yes. FCC certification typically comes before marketing gets their hands on it. They can change the case as long as it’s RF equivalent.

4 Likes

So it appears they have solved the issue of WiFi and Zigbee interference …

EDIT: Nevermind, looks like it’s 5GHz only.

Looks like some new devices incoming, too. FCC approval April 12th. All appear to be zigbee.
Leak Sensor

Motion sensor

Multi sensor

I wonder if there will be a migration tool? Ha ha

10 Likes

Almost missed the button

Found this image of the migration tool being tested.

image

11 Likes

I’ve heard rumors that support may have access to such a tool on a limited basis (V2 → V2 only). I’ve heard further rumors that such a tool is being expanded to work on additional hub versions and will be made available to customers. Naturally I can neither confirm nor deny any such rumors and if such a tool were real, I would expect it “in a few weeks”.

21 Likes

Sounded like we will get this when v3 is out. :joy:

I’ve been waiting for such a tool…(v1 to v3?), the tool might have a picture of me :wink:

4 Likes

If the information on wkidevi.com is correct, can anyone explain why the STH-ETH-300 has less Ram 128 vs 512, and a slower cpu 500mhz vs 1ghz, than the STH_ETH_250?

From what I’ve read the STH_ETH_250 and STH_ETH_200 (my device) are almost identical V2 hubs by different manufacturers.

1 Like

Hmmm… That would appear to indicate that Samsung is trying to cut costs, and is doubling down on the Cloud, versus true local processing.

I upgraded from a v1 hub to a v2 hub on the promise of local processing which has NEVER materialized for user created drivers and apps. Fool me once, shame on you…fool me twice - NOT GONNA HAPPEN! I am loving my Hubitat Elevation hub! :grin:

1 Like

Samsung isn’t “doubling down”, they are betting their entire kitty on the SmartThings Cloud.

I’m not sure why folks think there’s much ambiguity here: The SmartThings portion of the SDC conference was 80% about the new SmartThings Cloud, 15% about the new App and development environment, and only 5% on Hubs (including ADT, Nvidia Shield, Connect WiFi, fridge, etc.).

SmartThings is a cloud based platform - always was and always will be, just like Amazon Alexa which has sold tens of millions of units.

6 Likes