On Monday, December 4 between 10:00 AM EST and 9:00 PM EST, we will automatically update your SmartThings Hub v2 (both US and UK/EU models) to the latest firmware (version 0.19.19). Your Hub will briefly go offline as it reboots and applies the update; most customers will experience less than one minute of downtime. This update will provide the following improvements:
Fix frequent disconnects for users with an offline Hue bridge
Fix disconnect issues for some users with video cameras
Note that this firmware will not affect SmartThings v1 Hubs, Samsung Connect, Nvidia, or ADT panels.
It would be helpful if official announcements and email blasts included which controllers will be affected by any updates. Plus a note that “No other hub models will be updated at this time.” And a specific note as to whether the UK model is getting updated at the same time as the US V2 model as it is not called V2 in the UK.
Otherwise we get questions posted to the forum forever afterwards.
I’m aware of that model number, but my understanding is that just occurred because of the switch in manufacturers and while the case is somewhat different, the architecture was the same. It wasn’t a generational change like we got between the V1 hub and the V2 hub in the US. So they aren’t running separate firmware update paths.
I agree with Tezz, this update needs to fix the connectivity issue between YOUR hub and YOUR TV. The SmartThings connectivity is the whole reason I upgraded the tv I was purchasing. If I wanted non-compatibly I would have bought the LG tv for $500.00 less.
Unfortunately it’s not a problem I can fix The problems are not related to Hub v2 firmware, so today’s update won’t have any effect on Samsung TV issues. I did confirm that there is a team aware of the issue.
We’re trying to pin down specifics on this bug. If you are seeing it regularly, it would be hugely helpful if you clicked “Retrieve” under “Hub Logs” in the “Utilities” page of the IDE right after you see this happen. Then reach out to support and let them know the issue you’ve seen and that you triggered logs. This gives us something specific to look at. Thanks!