We will begin rolling out Samsung SmartThings Hub firmware version 0.42.07 starting Monday, April 11.
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)
Aeotec Smart Home Hub
Release Date:11 April 2022~ 15 April 2022
Note that this release may be spread out over a week, so you may not see your Hub update the first day of the release period.
Release Notes
General
Better support for multi-endpoint Zigbee devices (Discovery increased from 4 to 16)
Other minor bug fixes and improvements
Edge Drivers
Edge Driver Enhancements for Development
Allow drivers to specify additional_zcl_profiles allowing Zigbee messages of unexpected profiles to be parsed as ZCL
Move driver call_with_delay and call_on_schedule to be handled on the non main st.Thread.
Update low level API to pass ipv4 hub address as a string
going from a maximum of four endpoints to 16 is better than not going to 16, but it is still ridiculously short of the Zigbee 3.0 specification, which allows for 240 endpoints per node.
You should know this. Itâs part of the Zigbee specification.
1.1
ZigBee Device Types
A device type is a software entity which defines the functionality of a ZigBee node. The device type defines a collection of clusters that make up this functionality. A cluster is therefore a basic building-block of device functionality. Some clusters are mandatory and some are optional. For example, the Thermostat device uses the Basic and Temperature Measurement clusters, and can also use one or more optional clusters.
A device is an instance of a device type.
A network node can support more than one device type. The application for a device type runs on a software entity called an endpoint and each node can have up to 240 endpoints, numbered from 1.
My Hub v3 was updated to this firmware and my motion activated lights started performing inconsistently. I have the automation set up through the Smart Lighting SmartApp, to turn on with motion, and delay a minute before turning off. Now, if more motion is detected during that one minute on time, it doesnât âresetâ that minute, and rather turns off the lights and keeps them off for a minute, even with more motion.
The issue is similar to the one that appeared a couple months ago where a hotfix was issued. It happens less frequently and consistently this time however. An we expect a fix for this?
Not sure if this should go here or the the Edge driver topic but I added an Ecosmart remote today and it is displaying all the button options again. The one paired before the update still shows correctly. Both are using Zigbee Button Groups driver by @lmullineux. The CLI shows no errors with joining and the buttons work as expected.
Edited: I get the same all button option results using the stock Zigbee Button driver.
Hopefully theyâll either add some of the Smart Lighting capabilities to Routines that is currently missing (i.e sunset/sunrise offset more than 60 minutes) or come up with an Edge equivalent of Smart Lighting.
Good morning. The update to the fw version 0.42.07 is (or will be) also available for Samsung Smartthings wifi hub model ET-WV523? The firmware currently installed in my hub is still the 000.038.00011. Many thanks
Giorgio
Thank you very much @mhatley !
Do you know if ST wifi and last update on Octuber (version 38.000011) allow the installation of edge drivers?
I tried installing edge drivers but it always appears an error message: âRequest failed with status code 400â. I donât know if it depends on the firmware that does not support edge drivers⊠any idea?
Still experiencing the issue where motion activated light set to stay on for one minute will turn off even when motion continues, and then will not turn back on for some time, seemingly when it detects motion again. Similar to the bug that was introduced with two updates ago and hotfixed a week later. Happens with regular routines and with the SmartLighting âappâ.
Can we expect a fix for this? Iâm convinced of turning off auto updates because new bugs have been introduced twice now for a very basic function. Pretty frustrating.
This is working as designed for routines. If you add an auto-off to the On action then its a pure timer. Doesnât take into account the conditions on the IF side. In routines what youâd probably want is another routine with IF no motion for X minutes THEN turn off light.
Regardless if it is set up as a routine or a SmartLighting app within SmartThings, it started behaving differently when this update was issued. Exactly how a previous update a couple months ago did the same thing, a bug was reported by many users, and Samsung issued a new fix for that very issue.
I have tried every possible combination of conditions and it simply doesnât behave as intended. It gets real wonky sometimes, for example the light will stay on indefinitely and new motion will trigger it to turn off.
Smart Lighting will eventually be phased out when support for groovy ends.
