Hub Firmware Release Notes - 18.18


(Nick Stevens) #1

Starting on Wednesday, July 19th, we are going to begin rolling out Hub firmware version 18.18. Note that this is a rolling release, and you will be informed of your particular update time slot via email. Downtime for most Hubs will be less than 1 minute.

This update will provide the following improvements:

  • Faster boot times and local automations
  • Increased reliability and performance for Zigbee devices
  • Fix for problem with some Schlage Z-Wave locks not reporting lock status
  • Firmware updates for SmartThings sensors and outlets, Sengled Classic bulbs, Iris sensors and the Halo smoke alarm

EDIT 7-Aug-2017:
There are multiple release versions as we work out issues affecting certain user’s setups. Here’s a round-up of versions to hopefully help ease some confusion:

  • 18.21: Production users in UK/EU whose Hub was active as of July 19th
  • 18.20: Beta users
  • 17.14, 17.13, 17.12: All other production users, including all of NA, and new users on UK/EU

[RELEASE] Xiaomi Sensors and Button (beta)
Devices showing up as "This device is unavailable at the moment"
Please Help! Z-wave devices stop working after a few minutes
Iris v2 Contact Sensor eating batteries
FAQ: Iris Device Firmware Versions
#2

What are the specific zwave network repair issues that are being fixed?


(Michael Hess) #3

Will “Increased reliability and performance for Zigbee devices” fix our ge light drop out issue?


#4

I welcome any improvements, thanks.


(Jimmy) #5

whoa, so z-wave OTA updates are being implemented now? I don’t remember hearing that in the beta.


(Tom Manley) #6

I removed these items from the release notes in the first post. Z-Wave OTA isn’t supported and there were not actually any Z-Wave network repair issues fixed in this release. Sorry for the confusion.


(Tom Manley) #7

Depending on your zigbee network it may help. The somewhat technical explanation is we increased the number of end devices (typically battery powered devices) that can directly connect to the hub. Previously if you had more than 32 of these types of devices they would be forced to join through routers (typically mains powered devices like lights and outlets). If they joined through GE Link bulbs you’d be more likely to run into the firmware issues with the GE Link bulbs that causes them or devices connected through them to go offline.

Once you get the firmware update, you may want to try powering off all your GE Links for about 10 minutes to try to force any end devices that were joined through a GE Link to find a new way to join the network, ideally directly to the hub. After 10 minutes you can power the GE Links back on. I do this any time devices in the vicinity of my GE Links start acting up and it generally helps.


(Jimmy) #8

Any details on which devices besides Iris?


(Tom Manley) #9

Also Sengled Classic bulbs and the Halo/Halo+ smoke alarm


(Jason "The Enabler" as deemed so by @Smart) #10

I replaced all of my ge links with Philips hue… Haven’t had a problem since! :grin::thinking:


(Tom Manley) #11

Well sure, if you want to take the easy route :slight_smile:


(Robin) #12

Will this reduce the false triggers on the Multi Motion sensor?


(John C) #13

Faster boot times is pretty self-explanatory, but what logging improvements might we expect to see?

Thanks! :sunglasses:

EDIT: apparently none, as @nastevens removed mention of ‘logging’ from the original post. Darn!


(Bill S.) #14

Will this reduce the false triggers on the multi sensor?

I thought that was just an included feature they forgot to list on the box. :wink:


(Figgy) #15

Are any models of Samsung Smart Cameras being added? I have a model I purchased that does not work with Smartthings and I am thinking of bringing it back.


(DavidK) #16

@RobinWinbourne

False positives on multi-sensors?

I have the exact opposite problem! :slight_smile:

I am on the beta. Was anything changed in how acceleration is determined?

Basically I have a door that I wanted to monitor for movement and it worked flawlessly until last week.

It worked flawlessly for like 2 years.

When I manually test the door acceleration is shown in the event logs, but when the events happen, no acceleration is shown.

Other uses work flawlessly, i use it for doorbell notification and to monitor laundry done. In those cases it always notifies correctly and no false alarms. Thanks smartthings! For doorbell notification it might be more accurate to say there is never a false positive that I do not know about, what I mean is that if we are physically next to the door bell chime inside the house and I am jumping up and down with my 4 year old daughter, of course the multi-sensor will detect vibrations!


(Robin) #17

I’ve only ever use the multi Motion sensor for motion. I get almost daily motion events from my empty garage to the point where I’ve had to disable the routine.

Even if I put the dam thing in a shoebox it still somehow detects motion.

I can’t say much about the vibration sensor as I’ve never used it for that.


(Bobby) #18

Speaking of multi sensor oddities (contact). My bedroom door closes without even opening. #STghosts exist!


(Nick Stevens) #19

So those original release notes had a lot of problems. Communication with people is hard, that’s why I communicate with computers for a living (╯°□°)╯︵ ┻━┻)

┬─┬ ノ( ゜-゜ノ)

The notes have been edited to be actually representative of what people will see in this update. Sorry for the confusion.


#20

Does this firmware address the bug (that apparently has been acknowledged by SmartThings) of devices that just simply drop out and are shown as “inactive”?