UPDATE We will release a firmware update to version 26.12 on Monday, July 15 for the Samsung SmartThings Hub 2018 and 2018 models to address issues with Hue connectivity, Z-Wave firmware updates, and a few other minor bugs.
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.
We’re excited to announce the release of Samsung SmartThings Hub firmware version 0.26.9. 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: 27 June 2019 ~ 28 June 2019
Release Notes:
Improvements to pairing process for some Zigbee devices that experienced rare delays or failures
Improved reliability and speed of Philips Hue device discovery
Fixed problems changing color or color temperature on certain model of Zigbee light bulbs
Fixed setting of color on Ikea TRÅDFRI lights connected to the Hue bridge
Any idea when all your users with the ADT SmartThings hub will get an update? They are still stuck on version 20.x and would probably appreciate many of those improvements as well…
Any idea when the Leviton 300W ZWave dimmer will be supported properly? Smartthings shows it as on when it is off, but is able to turn in on, off and dim it, but status says it is on when it is off.
HA-Bridge Hue emulator integration stopped working yesterday after update. All Hue devices appear OFFLINE. Rebooted everything still not working. Hue control is working independently but not through SmartThings integration.
We’re aware of this. The firwmare update included changes to provide better local support for portions of device health for individual hue bulbs using status endpoints. This works by using the /api/<username>/lights/<id> endpoint’s reachable attribute. We suspect that HA-Bridge is providing an incomplete emulation of the bridge leading the the bulbs attached to the HA-Bridge showing up as offline.
While we did not intentionally break HA-Bridge the fix here should probably occur within HA-Bridge by fixing the emulation.
This firmware has broken Samsung Washer and Dryer integration on Hub v2. After the updated there are no status updates in the IDE therefore my automations have stopped working. Status works in the new phone app as expected.
Something changed for the worse with Hue integration. Stock everything possible. No custom DTH’s no custom code/apps. Just SmartLighting and stock DTH’s all around. Popcorn is back. Maybe even worse as it seems the fade up (theater effect) is now longer too, didnt know ST had any control over that if not then I’ll blame Hue. But up until this firmware everything was ‘ok enough’. It still popcorn’d with hue bulbs on hue bridge, but it was acceptably fast. Now we are back to 2017 levels of slow turn on.
I wonder if anyone that QA’s this code has a ‘moderately’ large setup. My bedroom I have 3 lamps, that turn on with motion, all hue bulbs on hue bridge using smartlighting. I walk in, and theres easily half second between each bulb turning on. 2015-2016 it was nearly instantaneous for all 3. 2017 it was again .5 sec between bulbs. 2018 was reasonable and maybe .25 seconds between bulbs. This slowness is more evident in my kitchen. I have 5 can lights with hue br30 color bulbs. So its like 2.5 seconds or more for all 5 to turn on, add in 2 cree’s that i have connected to hue because when connected to ST they suck so bad… its like I’m halfway across the kitchen before all the lights are on.
So yes, something with 100% stock, as ST would lead you to believe the best setup, Hue integration has changed for the worse…regressing about a year in terms of functionality. Yes, the lights work they do turn on. But overall time of execution is not acceptable. QA needs to have like at minimum 5 bulbs on hue before they can say ‘all good on my end’… and just functioning isnt acceptable. Actual speed of execution should be fast. All this was working GREAT soon after the Hue dth was moved to work locally. I’ve had a great HA system up until this bug returning… So annoying
Correlation does not mean causation. There are many other pieces to the smartthings environment that could have been changed around the same time as the hub firmware that would break things (cloud changes, device handler changes, UI changes, etc)
