Samsung SmartThings Hub 2015 (Hub v2) Model Hub Firmware Release Notes - 0.59.9

[SmartThings]

We will begin rolling out Samsung SmartThings Hub firmware version 0.59.9 starting on January 12, 2026. This will be a phased rollout, so that we can keep a close eye on any issues that arise, so your hub may not be updated immediately. 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)

Release Period

• January 12, 2026 - January 16, 2026
  • Platforms to be updated:
    • Samsung SmartThings Hub 2015 (Hub v2)

Note that this release will be spread out over the course of a one week per release period, so you may not see your Hub update on the first day of the release period. This release period is an estimate, so the rate of hubs updated and final completion date may vary slightly within the timeframe. Please check the status page for more up to date information on this release.

Release Notes

General

• Upgraded to Matter 1.5 SDK
• Added support for Matter Cameras with the following features:
  • Live Streaming, Snapshot and Video Clip Recording, Zone Management, Live Talkback, Pan-Tilt-Zoom
  • Requires latest SmartThings App Version 1.8.41.x (Android) or 1.7.41.x (iOS)
• When merging a Hub’s Thread network into a 3rd party network, handle unexpected data in the Thread network settings that might have previously prevented the merge from succeeding.

Edge Drivers

Significant Memory optimizations

In sum these changes represent cutting the memory used by running drivers on the system in half. In practice this means all hubs upon receiving the firmware should be able to support double the number of drivers and devices. The exact gains will somewhat depend on the devices and drivers being used.

These changes should be fully backwards compatible and automatically apply to all existing drivers. Some, like the new method for subdriver loading, will require driver changes to fully utilize the new savings, but the existing methods will continue to work, they just wont see the same benefits.

• Add lazy_load_subdriver_v2 option that allows for a different subdriver structure to further limit memory usage of subdrivers
• Split some commonly required files up (e.g. st.utils) so that only the functions being used are in memory so some previous functionality may be in new files
• Remove device event state cache from lua. Instead if get_latest_state is called the value will be loaded from the hub, and after that point will continue to cache events generated from the driver, but only for values that have been requested via get_latest_state
• Additional structural changes to optimize memory footprint.

Other Driver Changes

• On startup enforce parent devices being sent the init lifecycle event before children allowing children that depend on parent information to not have to handle cases where the parent is not yet present.
• Extend the latency improvements for default handlers to Zigbee Light Link (ZLL) devices

Deprecation Notice

• For Zigbee devices, the monitored_attribute feature is being deprecated. There are other systems in place for tracking when we last heard from a device and updating the attributes, so duplicating that effort in the driver was both memory and cpu expensive but unnecessary. For now a warning will be added to documentation and on calling functions related to monitored_attributes and the release where these will be fully removed hasn’t been decided yet, but developers should remove usage when they next update their drivers.