We’re excited to announce the start of a new SmartThings Hub Firmware Beta. Version 0.30.x will begin rolling out in batches starting April 21st; we will send out an email when we start updating Hubs. We will be paying close attention to any issues encountered by users so your hub may not get updated right away. The hub will be offline for about a minute during the update. See below for more specific details about the update.
Version
0.30.x
Hub Targets
Samsung SmartThings Hub 2015 (Hub V2)
Samsung SmartThings Hub 2018 (Hub V3)
Release Date
April 21st
Release Notes
Features
Several system updates for stability and security improvements
Improved reliability and responsiveness of Sonos device discovery
Increased the number of Zigbee devices whose metrics and routes can be tracked
Added more Zigbee device metrics
NOTE
* Anyone who participated in the previous beta (0.29.x) is automatically signed up for this one.
If you’d like to participate in the beta, but haven’t taken the survey yet, you can Sign Up Here
If you’d like to opt out, you can also leave the program via the Account Settings menu item in Centercode
6 Likes
RBoy
(www.rboyapps.com - Making SmartThings Easy!)
2
Does it fix the bug with the FE599 association while pairing which was introduced with auto encapsulation architecture causing notifications/status updates from the lock not to be received by the hub?
The Schlage FE599 and Yale T1L/YRD-120 locks do not support secure encapsulation for the association command class as shown in the links below. This is what leads to the issue you are reporting.
The 0.30.x firmware does not have a “fix” for that. It does have a change which makes it easier for support to workaround the issue for individual devices. Users impacted by this should contact support for assistance.
RBoy
(www.rboyapps.com - Making SmartThings Easy!)
6
Thanks Brad, glad to know it on the radar. Unfortunately, these aren’t the only devices impacted by the auto encapsulation issue. I was hoping that there was something in the works to let the DTH’s set a flag or specify if the command being sent didn’t need secure encapsulation.
I also understand from Kianoosh that it may be possible to handle this in the hub firmware as a special condition for these locks.
Just noticed these metrics. Are these the new additions or even more goodies are on their way? I am so happy we are finally getting more tools to troubleshoot zwave and zigbee mesh network issues on our own!
Those have been there for a while, and no need to blank out the zigbee ID in my opinion. I’m looking forward to more! I’m still on v29.8 and just got the email saying I’m being updated today.
Maybe but I don’t know. I’m on 30.3 now and it looks the same as what Alex posted above, and I didn’t capture a previous view (should have thought of that sooner) I wonder if adding a new Zigbee device adds anything new.
I did see the increased number of Zigbee devices!
EDIT: Yup, I see the new metric in Alex’s second post above compared to the first one prior to 30.3. Good catch @aruffell
Before this update there was a limit of 200 Zigbee devices that were supported for their new metrics features, but I have a whole lot more than that. I just checked a few devices that I knew didn’t have those metrics and path info, and now they do.
Any chance of Z-Wave devices getting more metrics like Zigbee
My Zigbee routes all make sense but my Z-wave routes make no sense at all
I purchased two Aeotec range extender 6’s over a year ago to be placed next to my doors to improve my yale conexis l1 locks. It didnt really improve the locks which sometimes report still being unlocked when their not, But ST is saying that the locks are travelling to a device nowhere near the lock. I believe zwave can travel by different routes but was wondering if the route that ST is reporting is important or not. Maybe @RBoy might be able to recommend something to do. I noticed my range extenders are running 1.02 and there is a update to 1.05 so might update them tomorrow.
@posborne, @BarryA@tpmanley - This update went well. Usually the Zigbee mesh suffers some issues when the update happens, but haven’t noticed anything this time. Actually my wife hasn’t noticed anything, which means it went really well.
Only one thing to note, an IKEA motion sensors, what had gone HUB DISCONNECTED state a few days ago, but still sends motion events still stayed on HUB DISCONNECTED state. Would be possible to fix this issue? - I am going to reboot the Hub to clear it, but it is still annoying that the device reports normally, but shows HUB DISCONNECTED.
I went to login to center code today and clicked on the beta firmware link and was forwarded to a page to submit an application to apply to the beta program. I filled out the form but now I am told I have to wait for my application to be reviewed so I am unable to access the beta section to review or submit bugs for 30.x.
