We’re excited to announce the start of a new SmartThings Hub Firmware Beta. Version 0.49.6 will begin rolling out in batches starting on Jul 25, 2023. 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. The hub will be offline for about a minute during the update. See below for more specific details about the update.
Version
0.49.6
Hub Target
Samsung SmartThings Hub 2015 (Hub v2)
Samsung SmartThings Hub 2018 (Hub v3)
Release Date
Release Date: Jul 25, 2023 → Jul 28, 2023
Help Us Help You
As part of our Beta program, it is important for our support team to investigate logs from Hubs running that are reporting errors. To provide our team access, please follow these instructions:
Added support for LAN drivers to optionally define search parameters to prevent running discovery (saving system resources) unless a device matching those terms is found. Drivers without search parameters defined will not see any change in behavior.
These parameters should start being used automatically for SmartThings official drivers.
Additional documentation and details forthcoming for usage by custom drivers.
Added support for Matter Bridge end devices
Some optimizations on Lua device table and datastore metatables to decrease memory usage
Fix error caused by use of manufacturer specific clusters in Matter drivers
Fix issue where drivers could drop bytes during partial receives on cosock TLS sockets
Updated network connection manager and enable internet connectivity checking
Drivers will now have a longer backoff after consecutive crashes (up to a max of 12 hours) unless the driver has more than 30s of uptime or is updated
NOTE
Anyone who participated in the previous beta 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
No Edge Driver update will be needed. We are enhancing and improving the onboarding experience of Matter Bridged end devices in the upcoming release, but the functionality post add will be the same regardless of the Mobile App release.
Great question. This particular change is Hub itself adding more validation and monitoring to see if it is connected to the Internet. The goal is to detect disruptions and disconnections faster than before.
Not at this time no. The driver will still be installed ahead of time, but storage is not usually the most constrained. This way the cpu/memory costs of running the driver will only be used if a matching device exists. It is possible we could wait to install the driver until a match is found, but that would add significant latency to the onboarding as download would be required ad-hoc.
Just got an email from the Hub Firmware Beta team about information in my account for Hub Firmware Beta didn’t make it past your validation process.
This happened before, and everything on my end is right. If I remember right, ST did something on your end to get this figured out, so can you do that again?
Btw, the email content needs to be updated so it doesn’t ask the customer to go to Graph and get hub detail anymore.
Hi @johnconstantelo,
Thank you for informing us of the out-of-date email instructions. I will correct those. I manually added you back to the beta tester group in Centercode and your hub should receive the update once the rollout begins. I will check to see what could be going wrong with your Centercode profile information that our validation system does not like.
The issue is really that the behaviour is different to the default Zigbee and Z-Wave drivers that magically appear when first needed so it immediately looks ‘wrong’ to many users and generates concern.
When hubs hit memory limits users are often advised to remove drivers without regard to whether they are being used or not so again having these drivers installed seems ‘wrong’. Storage v memory isn’t really front and centre when sitting in the end user chairs.
I have two Switchbot hub 2 that are running their Matter Bridge firmware. I was able to successfully add one of them to my V3 hub running 49.6, and I see all of the expected child devices from that hub. But i’m having issues getting the second hub 2 to add. Has anybody had luck adding 2 matter bridges from the same vendor?
