Hub Firmware Release Notes - 27.6

9/9 UPDATE

We are going to release a hotfix on Tuesday, September 10th for SmartThings Hub 2015 (v2) and 2018 (v3). Firmware version 27.8 will include improvements for some LAN icommunication issues and connectivity fixes for multi-endpoint devices.


We’re excited to announce the release of Samsung SmartThings Hub firmware version 0.27.6. Once downloaded, your Hub will briefly go offline as it reboots and applies the update; most customers will experience less than one minute of downtime. We will update the status page when the release is complete.

Hub Target:

  • Samsung SmartThings Hub 2015 (Hub v2)
  • Samsung SmartThings Hub 2018 (Hub v3)

Release Date: 26 August 2019 ~ 27 August 2019

Release Notes:

  • Zigbee bulbs can now remember the previous level if they were turned off by setting the dimmer level to zero
  • Firmware updates for various Zigbee devices including SmartThings Smart Plug (UK) and Aurora lights
  • Minor Z-Wave improvements for recovering communication with devices
  • General stability and performance improvements
6 Likes

I was given to understand that this also fixes an issue related to z-wave devices with a large number of endpoints not showing up after pairing.

The Smartthings WiFi hub is considered a V3 version? Thanks

no. it is a separate hub type on different firmware schedule.

3 Likes

You know…it would be nice if we were actually told what Zigbee devices would be getting firmware updates. Sorry but “various Zigbee devices” just doesn’t cut it.

2 Likes

This has a little more detail

2 Likes

What’s different between 27.5 and 27.6?

The following are the updates made available in this release:

  • Aurora Fixed White MPro update to 0x00000012
  • Aurora Fixed White Strip AOne update to 0x0000000A
  • Aurora Tunable White Strip AOne update to 0x0000000D
  • Aurora Rotary Dimmer update to 0x00000014
  • Aurora RGB Tunable White Strip update to 0x0000000C
  • Aurora AOne update to 0x11280002
  • Aurora ZBT Color Temperature update to 0x11396500
  • Aurora MPro Smart Tuneable LED update to 0x00000011
  • SmartThings SmartPlug (UK) update to 0x21186230
7 Likes

Only difference between 27.5 and 27.6 is the inclusion of a firmware update to SmartThings SmartPlug (UK) bringing it to 0x21186230

4 Likes

Thank you.

Yes that is correct

3 Likes

What does that firmware update bring UK users? Wish I could avoid it as my SmartPlugs have worked faultlessly for 2 years (“if it ain’t broke don’t fix it”).

This post was flagged by the community and is temporarily hidden.

It may be an update for the new UK plug, not prior models. @BroderickCarlin can you clarify which model UK plugs are getting the firmware update?

1 Like

Could you please clarify what you mean by “Zigbee bulbs can now remember the previous level if they were turned off by setting the dimmer level to zero”? Specifically, does this mean if a bulb is on and turned off (i.e. by a power outage) then when power is restored to the bulb (after a power outage or by a wall switch for instance) then the bulb will return to its previous state? This would be a huge improvement and eliminate the need for the canary bulb work around I currently use (which isn’t totally reliable). I have all Cree bulbs would this new feature apply to them too? Thank you!

1 Like

The update is for the new UK plug, not prior models :slight_smile:

2 Likes

This addresses a very specific use case that would cause some Zigbee bulbs to appear non-functional. The use case that is being addressed here is:

  1. Start with a Zigbee dimmable bulb turned on
  2. Through some means set the bulb to 0%
  3. At this point the bulb would appear turned off and would report as being turned off in the app.
  4. Through any means turn the bulb back on (voice assistant, automation, app, etc).
  5. Because the bulbs last level was 0% the bulb will turn back on to 0% or 1%. This results in it appearing that the bulb didn’t actually turn back on and just causes a world of confusion/frustration. The fix in the 27.X release causes the bulb, in this case, to turn back on to what ever the bulbs level was all the way back when we started at #1 :smile:

The use case you mention with the canary bulb is not something that would be addressed by this change.

5 Likes

@BroderickCarlin, @Kianoosh_Karami, @SmartThings

It appears that a change was made in 27.6 that has broken the proper receipt and processing of unsolicited LAN messages to port 39500 on the ST v2 Hub (only hub I have to test with!) This has broken both ST_Anything and OmniThing from being able to send status updates through the ST Hub to the ST Cloud to be processed by custom DTHs. These projects both utilize the MAC address of the sending microcontroller as the DNI of the ST Device. Communications from ST to the microcontroller still works fine.

Please advise if this change was intentional or not…and if there is a way to fix it.

Thank you!

6 Likes

There seems to be an issue with the update breaking several SmartApps.

This is impacting one of my projects. This change was not in the release notes, nor was it described in the beta. Can someone in ST engineering look into this? What was the reason for this change, and how can an application be modified or the firmware fixed?

3 Likes

Hi There,

I have a V2 Hub updated to 000.027.00006

Currently all my Zigbee devices seem to be down/Offline. Is there an outage? or is it related to the firmware update? I have tried rebooting the hub with no change. Thanks

Regards
Ravindran

© 2019 SmartThings, Inc. All Rights Reserved. Terms of Use | Privacy Policy

SmartThings; SmartApps®; Physical Graph; Hello, Home; and Hello, Smart Home are all trademarks of the SmartThings, Inc.