Hub Firmware Beta 0.28.x

Hey everyone!

We’re excited to announce the start of a new SmartThings Hub Firmware Beta. Version 0.28.x will begin rolling out in batches starting November 6th; we will send out an email when we start updating Hubs. We will be paying close attention to any issues encountered by users so your hub may not get updated right away. The hub will be offline for about a minute during the update. See below for more specific details about the update.

Version

  • 0.28.x

Hub Targets

  • Samsung SmartThings Hub 2015 (Hub V2)
  • Samsung SmartThings Hub 2018 (Hub V3)

Release Date

  • November 6th

Release Notes

Features

  • Stability and performance improvements

Fixes

  • Zigbee Secure Mode cannot be disabled on Hub V3
  • Updated LED behavior to differentiate when hub is in Wi-Fi setup mode (slow blinking yellow) and when hub is in “initial setup” mode (alternating red/green).
  • Sonos reliability updates when discovering grouped speakers.
  • Hue device health update to address frequent online/offline state changes.
  • Various minor fixes

NOTE

*Anyone who participated in the previous beta (0.27.x) is automatically signed up for this one.

If you’d like to participate in the beta, but haven’t taken the survey yet, you can Sign Up Here

If you’d like to opt out, you can also leave the program via the Account Settings menu item in Centercode.

7 Likes

what, no local rules API testing yet?! :stuck_out_tongue:

7 Likes

I do not know what you are talking about?! Do you have any screenshots to prove this API even exists? :sunglasses:

1 Like

why a screenshot when there’s a press release :slight_smile: https://news.samsung.com/global/infographic-get-smart-the-latest-in-what-smartthings-can-do-for-you?utm_source=mainkv&utm_medium=internal

1 Like

@BroderickCarlin Could this be causing an issue when pairing an Iris remote?

Nope, this issue does not affect initial join/pairing at all. Instead, this issue means that devices were not able to unsecure rejoin to a V3 hub

Hmm, ok. I’ll tinker with it more.

1 Like

Even better than a press release…

1 Like

@BarryA - I got an email saying I was not going to be part of the beta because my hub’s serial number was incorrect in centercode. I fixed it and would be happy to participate in this beta if at all possible.

2 Likes

@aruffell - Thanks for updating your s/n. You are good to go when the beta rolls out.

1 Like

@BarryA this still planned for today?

@Automated_House - Beta will be rolling out to hubs shortly

3 Likes

I just received it, everything fine so far

Got it too, and so far so good. Got the typical HUB_DISCONNECTED status on several devices, but those are going away as devices check in or get used.

1 Like

I got it. Not device disconnects at all. Also re-enable Device Heath option and so far no drop outs of battery devices :slight_smile: or the arrival sensor. That usually takes a couple of days to drop off though so I’ll reserve judgement on that one.

Like it didn’t even happen :slight_smile: No disconnects here either.

Did not even notice it was installed… meaning no issues at all.

1 Like

no issues yet.

automations working as normal…

will this beta version have anything to do with access tokens, I am trying to use one in Home Assistant but I keep getting an “unknown error”. I wouldn’t think it would be anything to do with this but just thought I would ask.

i’ve had a ST Arrival sensor off-line a couple days. Pulled the battery and re-installed and it came back online. This didn’t work on old firmware, so i’d say the insecure rejoin fix is good.

2 Likes