We’re excited to announce the start of a new SmartThings Hub Firmware Beta. Version 0.54.5 will begin rolling out in batches starting on 27-Aug-2024. 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.54.5
Hub Target
Samsung SmartThings Hub 2015 (Hub v2)
Samsung SmartThings Hub 2018 (Hub v3)
Aeotec Smart Home Hub
Release Date
Release Date:27-Aug-2024.
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:
Enhanced fingerprinting of Zigbee devices to accommodate long names and
atypical formatting in manufacturer metadata
Fixed an issue to allow for faster boot-up time after a power-up or firmware update.
Added Matter support for multi-command invoke requests. Drivers can make us of this feature for 1.3 devices that support it as reflected in MaxPathsPerInvoke attribute of BasicInformationCluster.
Added support for firmware update events related to Matter bridged devices. This should also display the software version in information section of bridged device card, if it is made available by the bridge.
Edge Drivers
Add handling for specific default handlers directly in the firmware and not in the Edge Driver for faster execution.
This feature will allow for significant latency reduction in the processing of specific (Initially Switch and SwitchLevel) Capabilities to specific protocol messages .
This feature will be enabled by default for the official SmartThings drivers (initially Zigbee Switch, Matter Switch, and Z-Wave Switch)
Support can be added by including a new optional parameter on default handler registration in community drivers (official documentation coming)
Currently, this is only supported for devices with a single endpoint
There will still be logs of the commands being sent via either method
** Logs for commands being handled in the driver look like: INFO Zigbee Switch <ZigbeeDevice: 77cf0ae2-23f1-4035-bf22-026414b6a03f [0xF508] (SmartThings Outlet 1)> received command: {"args":{},"capability":"switch","command":"off","component":"main","positional_args":{}}
** Logs for commands being handled with the native handler look like: INFO Zigbee Switch hub handled command: 77cf0ae2-23f1-4035-bf22-026414b6a03f:main:switch:off []
Significantly improved the method of communication between edge drivers and the hub software leading to a decrease in latency for all communication.
54.8 - Targeting Release 10-Sep-2024
Reverted a change, that should decrease the device online and offline behavior being reported for Z-Wave devices
Addressed a bug with large sized lan messages that caused messages to be being dropped.
NOTE
Anyone who participated in the previous beta is automatically signed up for this one, unless you have unenrolled.
If you’d like to participate in the beta, but haven’t taken the survey yet: Sign Up Here
If you’d like to opt-out, update your preferences via the Account Settings menu item in Centercode or reach out to a SmartThings team member to assist.
Got this update last night. Only reason I noticed is both my Zwave door locks fell offline. Came back on about an hour later. Though overnight I’ve seen them go offline and online a few more times.
RBoy
(www.rboyapps.com - Making SmartThings Easy!)
4
I’m seeing the same issue with zwave locks going offline and online regularly after this update.
Have serveral errors after the firmware is updated on 27Aug
Both devices with lan services are now not able to function and error message shown per below @Luis_Humberto_Medina , @nayelyz can you assist on this ?
Yes, i seem to notice my z-wave locks going offline more frequently. Also, my zigbee rgbw controllers are still losing connection.
RBoy
(www.rboyapps.com - Making SmartThings Easy!)
8
Sounds like there are some tweaks made to the device offline detection to make it more aggressive. I know that earlier it has been set that if even if one ping was missed the firmware would make it offline (which caused this issue). Maybe the algorithm needs to be made a little more relaxed for FLiRS devices which are susceptible to packet loss. @alissa.dornbos some feedback.
@RBoy@Jason_Silva@Tin_Hwee_Wang@jamesonrw, We have consulted your issues with the team, and we will let you know as soon as we have updates. Thank you for your patience.
An edge driver for my ratgdo garage door seems to be reporting as offline as well and that NEVER happened before this update. These notifications are getting a bit annoying, and my zigbee devices are also showing more and more offline and reconnecting slowly.
I did before the beta started but it says “Applicant” since then and when I click on My opportunities - “SmartThings Hub Firmware Beta” it’s just an empty white space.
Edit: Thanks to the staff for fixing it, it’s now running the 54.x beta
I’ve been out of town for a while and returned just after this update to find several battery zwave devices (buttons, motion sensors, contact sensors) that are showing offline in the app and return to online when activated. Also, I had to re-include multiple zgbee devices that were unreaponsive. Not sure if this was related to the update or coincidence.
RBoy
(www.rboyapps.com - Making SmartThings Easy!)
15
I’ve also seen battery operated devices go offline with this beta update. They keep flipping between online and offline.
We are aware of an issue affecting LAN-connected devices following the rollout of firmware version 0.54.5. Our team has identified the cause, and we are actively working on a fix, which we expect to include in the next beta release.
For users experiencing problems with non-LAN devices, we are also investigating a separate issue, though we do not yet have a confirmed timeline for the resolution of that particular problem.
We appreciate your patience and will provide updates here as soon as more information becomes available.
Hi @Luis_Humberto_Medina, I’m also seeing battery powered devices drop and then come back online. I’ve also noticed severe battery drain on some, namely ST branded buttons. I just replaced a battery in one of them a couple days ago with a new battery and this morning it’s already down to 5%.
Oddly enough, it looks like that particular button just received a firmware update. Are device firmware updates also going out, or are those dates on those attributes just the last time the firmware was checked and not updated?
RBoy
(www.rboyapps.com - Making SmartThings Easy!)
18
Just a note on battery life and firmware updates. In our testing I noticed that firmware updates are very battery intensive and it’s not uncommon for devices to burn through a battery while updating firmwares. For example the heat it buttons weren’t even able to complete a firmware update because it ran through a brand new battery and then some. We had to hook it up to a DC source to get it to complete the update.
All weekend I’ve had Zigbee devices go offline (on my v2 hub) and come back online by either using the device (switch or contact sensors) or pulling the battery out and putting it back in, or just waiting. I’ve also replaced the battery TWICE now in two days for my Smartthings/Aeotec button I mentioned in my post above. If I could, I’d send SmartThings an invoice for the cost of the batteries I’m chewing through…
This beta needs some attention. It’s on my v2 hub, but luckily not on my v3 hub. I have two hubs in my current location, and I have zero issues with my v3 hub. Nearly all of my 240+ devices are Zigbee across those two hubs, so when there’s an issue like this, it impacts me perhaps more than others.
Can you please provide us any updates since your post last Thursday?
I have a number of local VIRTUAL devices using my own driver. Those on my main hub (not running the beta) are working perfectly. Those on my beta hub are totally unresponsive and do not log anything at all.
I have Meross Matter switches configured onto both hubs. By that I mean each switch will appear as two devices, a main device controlled by the main hub, and a beta device controlled by the beta hub. They are the same physical hardware though, so should be in sync. Not any more they ain’t.
As far as the main device is concerned everything in the garden is rosy. It is in sync with the hardware. When I toggle the switch using the main device the beta hub sees an interaction response and the log shows an event being emitted. However the status of the beta device is NOT updated.
If I turn the switch on using the beta device the switch is turned on. The main device reflects the change as it should. The beta hub logs the command and the interaction response but does NOT show an event being emitted and the status of the beta device is not updated.
The obvious question is what happens if we make it simpler and just consider a Matter switch that is only on the beta hub? It seems to be pretty similar. The commands are carried out but the status doesn’t update.
Fortunately for me, all of my ‘production’ devices are on my main hub now with the exception of a Matter smart plug to power said hub.
@alissa.dornbos My hub was updated to firmware 54.5 and as a consequence I lost a lot of important functionality (Tasmota Edge Driver Integration no longer working). For this reason i opted out of beta several days ago thinking i would automatically revert back to the normal firmware. Unfortunately I’m still on 54.5. When can I expect to be running on the normal firmware? Is there a way to push or force said installation? Thank you for your time.
