Hub Firmware Release Notes - 0.32.12

We will be rolling out Samsung SmartThings Hub firmware version 0.32.12 starting tomorrow. This release version (0.32.12) is a hotfix for version 0.32.10 and will include additional improvements for Sonos and Z-Wave device communication. 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: 21 October 2020 ~ 22 October 2020
Note that this release may be spread out over a few days, so you may not see your Hub update the first day of the release period.

Release Notes:


  • Sonos
    • Fixed an issue that could prevent Sonos devices from being discovered or controlled if they are part of a Sonos household containing a large (8+) number of speakers.
    • Fixed an issue where favorites for a Sonos device were not being displayed or updated correctly in the SmartThings app.
  • Z-Wave
    • Fixed an issue that could result in the Hub Z-Wave framework sending duplicate messages in a loop when force deleting devices.

what’s about location mode set/detect home/away that’s no longer working since pretty long time? even if features as get your location from this phone is enable and it’s create “placeholder” device (IDE) it still doesn’t work!!! :frowning:

well TBH - that feature has NOTHING to do with the hub, soooo. That’s App and Cloud only.

1 Like

if not hub, it’s apps or cloud issues! ok! but hope they work to release new apps version soon with this bug fix!

Location it’s one of the most important basic thing to know in automation like if i’m home or not! all further action depend on that…

I can manually turn on/off vswitch and run routines if device off then… but it’s still asking for manual input as turn off/on device…

Also i know we can do with work around like with life360 or other tricky stuff like layer of webcore piston or groovy apps but natively its basic things that SmartThings need to be able to accomplish at 99.9% accurate time!

I’m not saying you’re not right, I’m saying this thread is about the hub firmware. There is another thread about location and spamming the guys working on the hub doesn’t help either case… Thanks.


regarding pairing/inclusion z-wave with the new app ive noticed that its quite the hoops to jump thru (and then it might not even work) compared to say pairing/inclusion with ring alarms z-wave.

Mine’s been offline for a long time… is this normal?

1 Like

Mine too! Any way to fix it?

1 Like

Same here, it’s been down for close to 2 hours. So much for a brief outage.

Mine is a 1.1 hub, says it has firmware version 000.013.00013, so maybe this is an unrelated malfunction?

Indeed. Completely unrelated. …

Hard to believe it’s unrelated when you have at least three users all complaining about the same issue.

This update is only applied to v2 and v3 hubs, the v1.1 should not be affected.

1 Like

Hi, Hub has been offline since 22:00 GMT last night, now nearly 15:00 GMT and still down. That’s nearly 17 hours since update started, how long is this going to take? All our fire and security systems are inoperable.

This firmware does not apply to that device. So while he may very well be having issues they are not related to 32.12 deployment. In fact @josiahdj that 1.x hub wont ever be getting any firmware updates again. If it were mine I would consider upgrades. I won’t run devices that aren’t eligible for firmware updates from the manufacturer for security reasons.

1 Like

Hi Nathan, if it’s not related to the update, do you have any idea why this is happening or should all of us contact support?

I would suggest contact support but I did read on posts from users the resetting their router and reconnecting the hub fixed their issues.

Agree with @RBoy - Call or email support. As difficult as that can be they can’t fix what they don’t know about.

We (Users) often take it for granted that they (IT / Vendor / SaaS provider) know about the issues already. I’ve worked product support nearly my entire IT career - the number of times IT/Vendor hasn’t ‘fixed’ something simply because the users never reported it and therefore they didn’t know it was a problem as an issue would mortify you. …And if they DO know about the issue - reports let them know about the severity of an issue and help prioritize it. Don’t rely on the other guy to open the ticket.


I’d upgrade in a heartbeat if there was an easy way to migrate everything from one hub to the next.

1 Like

i cant even get a v3 hub to setup connect - something going on with the platform backend