Hub V2 stuck on firmware 035.004

Devices & Integrations
1

I have a legacy v2 Hub (STH-ETH-200) trapped on version 035.004

  • It has not been online for a couple

its not updating, apparently due to the expired security certificate bug; I am unable to block time server on 123, as my Sagemcom ISP modem does not support outbound port filtering.

Understand that its possible to push a fix to the device

2

not possible on pushing a fix - not sure where users are seeing this as an option as of late. ST puts the burden on the user to resolve the expired security certificate. One recommendation is to use a family or friend’s home network that may have the ability to block ports.

Here is the guide for troubleshooting: Troubleshooting SmartThings Hub 2018 and Aeotec Hub

You need to reach out to Support directly as ST Staff have not been on the forum for three weeks at this point to check if it is an expired security certificate. I couldn’t tell from your description, how long it has been online. if firmware 35, it can take awhile as it needs to install each version from 35 to to the most recent firmware. in the ST app, tap on Menu and select Contact us:

if in US:

if outside US:

  • go to https://www.samsung.com
  • scroll to bottom of screen
  • tap on Support Home in the Support section
  • look for Apps and Services and tap on it
  • tap on SmartThings
  • scroll down to see contact methods available
  • someone mentioned Whatapps worked best for them
3

I’ve never been clear over what happens to firmware with a factory reset, but 35.4 is from February 2021.

Do you have a particular reason to believe that it is the security token issue? The V2 hub pretty much connects itself to the backend servers and the mobile app side of the process is more about claiming it to your account. I’ve seen various old firmware numbers displayed during hub installations even when it turns out the network wasn’t even plugged in and there couldn’t have been any communication. I think they were simply to frighten me.

Although I’ve had firmware pushed to a hub in the past I’ve not heard of it being an option to fix the security token issue, though you are by no means the first to mention it here. Whitelisting is another thing that has been confidently requested more than once but is a complete mystery to the community. Then again we don’t often (ever?) get to hear if and how hub installation issues are resolved.

Unfortunately the development support team who were helping handle the issue via this forum haven’t been seen for a few weeks so you may have to take the customer support approach. It would appear @jkp has covered that as I’ve no idea how to do it any more, though NOT having the Samsung Members app installed on a phone has helped in the past.