Hub Firmware 0.40.X Beta

Hey everyone!

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

If you haven’t seen our recent announcement on announcing the beta release of SmartThings Edge - a new architecture for Hubs that use Device Drivers and Rules to execute Hub Connected devices with lower latency, higher reliability, and… local execution . Please check out that announcement here.


  • 0.40.x

Hub Target

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

Release Date

  • Release Date: 12 October 2021 ~ 15 October 2021
    Note that this release will be spread over the listed days, so you may not see your Hub update on the first day of the release period. We will post on this thread once all users should have received the update.

Release Notes

Edge Drivers

  • Add default Fallback and Error handlers for dispatchers
  • Add SHA1 Lua library
  • Add support for Zigbee Float types
  • Fix certain use cases of Zigbee bind requests using an incorrect endpoint in the payload


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

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

If you’d like to opt-out, update your preferences via the Account Settings menu item in Centercode


0.40.3 – Released on 12 October 2021
0.40.4 – Released on 15 October 2021 (Fixed regressions introduced in 0.40.3)

1 Like

Looks like this has arrived on my hub

The release of 0.40.3 Hub Firmware has been completed. Please do let us know if your Hub has not been updated.

But still nothing for SmartThings WiFi

My hub updated and the secure mode switched from off to on.

Can you DM me your Hub ID?

My beta hub had Secure mode on too, but I can’t swear it was off before. I just thought it was.

I kind of thought insecure rejoin was no longer an issue with Zigbee 3.0 though I’ve never been clear if that only applied if the clients were on 3.0 too.

I had disabled mine several weeks ago when I was experiencing an issue with a zigbee device. Plus, when I checked on the update earlier, I remember noticing secure mode was off so when I went back this afternoon, the color change of the enable button was obvious. :slight_smile:

I cannot turn off zigbee unsecure rejoin either. I have 3 hubs in the beta and they all have the problem. Using the IDE, selecting “Allow unsecure rejoin (most compatible)” has no effect.

1 Like

Can also confirm my zigbee secure mode went from off to on. Turning it back off in the ios mobile app seems to revert back to On.

1 Like

I also tried using ios app to turn of secure mode, but after a moment it switched back on again.

Happens with the Android app too. You can set it off but as soon as the page is refreshed it is back on again.

1 Like

Sounds a bit like the issue where reordering devices does not always stick. Something is not making its way to the cloud.

the same here

Looks like my hub updated but immediately after device activities stopped logging to my history in the iOS app.
All device events that occurred before the update are still in the history;
cloud based automations are still running and showing to be run in history;
but the activity of the cloud based devices are not showing up;
From manually watching it looks like the devices are triggering from the automations currently, but
seeing the device updates linked to those automations is still pretty important. My mini split with three heads has had issues before because in ST each head is considered an independent device, but they are all dependent on the same main compressor.

Update: looks like after a few hours the history of device activities started syncing again.

It’s urgent that you fix the insecure rejoin issue, it’s a major inconvenience. Please.

Regarding the Secure Mode set to On by default, we have found the root cause, and we will proceed with releasing a new firmware shortly this week. I will communicate more once the plans are solidified.

Thank you all for your feedback (We were just testing you guys to see if you were using the Beta firmware)


Did we pass? :joy:


Good to know, thanks!

We are targeting to release a new Hub firmware with fixes on Friday, Oct 15th. Thanks all.