Hub Firmware Beta 0.27.x

Hey everyone!

We’re excited to announce the start of a new SmartThings Hub Firmware Beta. Version 0.27.x will begin rolling out in batches starting August 12th; 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.


  • 0.27.x

Hub Targets

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

Release Date

  • August 12th

Release Notes


  • Stability and performance improvements


  • Fixed issue where, in rare conditions, many “Thing” devices could appear in a user’s account.
  • Fixed issue where some Zigbee bulbs would forget the dimmer level if they were turned off by setting their dimmer level to 0.
  • Various minor fixes


*Anyone who participated in the previous beta (0.26.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.


Any chance this fixes the issue with devices not being created while pairing if they have too many endpoints (e.g. 10 or more)?

Surprised these changes aren’t just another 26.X version number.

Have y’all removed the Beta 26 from Centercode?

I’m having some major zwave issues today and was going to submit a report.

Never Mind… I fixed it. My fault. lol

26.12 is public, not beta.


@BarryA is this still going out today?

1 Like

Hi all:

Unfortunately I was not able to get the beta out today due to a number of issues with Centercode. However the issues have been resolved so the beta (0.27.4) will be going out tomorrow, 8/13. My apologies.

I have gone through many beta signups that were stuck in a pending state. This can be for a number of reasons, but the most common is due to invalid hub information provided at signup. There was also a brief period of time over the last couple of months where the beta signup failed to transition to a screen requesting hub information.

If you received an email from us asking to verify hub information, or you experienced a beta signup process that may not have been complete, feel free to sign up for the beta again ( and send me a DM letting me know and I’ll make sure you’re on this next beta.


I think this is the third time i’ve filled out that survery :joy:

Centercode is giving me this error:

Hi Joe, the beta isn’t live yet but you are on the list. You will get the beta when it rolls out.

Got my update about 20 minutes ago

1 Like

@BarryA signed up multiple times… never got the invite… even updated my hub ID in centercode…


My hub is updated! Let the fun begin.

1 Like

Got it. Nothing obviously broken so far.

1 Like

@BatraD you are now in the beta and hub is on 0.27.4

At this point all beta user hubs should be updated. If your hub is not updated to the beta release, or have trouble accessing the beta project in Centercode, please send me a DM.

Thanks again for being beta testers!


So I should probably spend the afternoon reconnecting all the devices that the last general release knocked off and I haven’t been able to get reconnected for the past month. Good deal, it’s raining today anyway.

1 Like

hi Barry,

got the 27.004 code on my hub now… thanks for your help

1 Like

Hi @BarryA,

So far, this is the only odd event messages I’ve gotten that I haven’t seen in quite some time:

The outlets are Aeon Zwave G2 microcontrollers, and the fans are GE Zwave Plus devices.

Want me to submit a Centercode report?

Yes please submit a bug report on Centercode. Also please note in the report if the devices are controllable via the SmartThings App or automations.

1 Like

Will do. I’ve been monitoring and this is the only time I’ve seen this, and the devices work as expected with both apps and automations. I wasn’t home when these events took place, so it’s impossible to know if they didn’t work when the events happened. I suspect they were probably ok.

Before submitting the report I’m going to watch the event log closely now that I’m home, and if it happens again I’ll send it in right away.