Hi @Alexhp11
Even though your V2 Hub has firmware from 2016, it might still be able to update, but some very old hubs cannot complete the update and end up being obsolete. We recommend trying to force the firmware update with these steps.
For these hubs, blocking NTP traffic can allow the hub to connect to the hub firmware update server. This does require administrator access to your router and the ability to set Access Control Rules. The following steps outline how users with the necessary permissions and equipment access can proceed:
Locate the steps provided by your home network router manufacturer to access the Router Settings / Admin Interface.
In your Router settings, navigate to Access Control Rules and create a rule to disable UDP port 123 (NTP). (What is NTP Wiki). Please be sure to set only the source port as 123 and do not specify a destination port.
Factory reset the SmartThings/Aeotec Hub.
Go through the standard onboarding/hub claim process outlined in the hub documentation provided with the device.
If you still have trouble claiming, please collect hub logs as outlined in the Troubleshooting section below before rebooting.
Once the hub has successfully onboarded, remove the Access Control Rule created to block UDP Port 123. At this time, the hub should have updated its firmware to the latest supported version.
** If blocking the NTP port is not functional, another option some users have had success with, is blocking URLs for your specific region within the Access Control or Parental Controls. Here is a guide to find your NTP server for your specific region.
After reading more on the forums, it looks like the NTP blocking issue mainly affects the V3 hubs. But in my case, Iāve got a 2015 V2 Hub that I kept brand new as a backup in case my main one died.
My main V2 hub (running since 2016) is still going strong, no issues.
The spare V2 hub (never used until now) wonāt connect to the cloud at all.
So the question is: Is there any hack, workaround, or recovery method to bring this unused V2 hub online? Or should I just accept itās a paperweight now?
Would really appreciate any insights from the communityāsurely I canāt be the only one with a ābrand new old stockā V2 hub stuck in limbo.
Iāve recovered three v2 hubs with the below procedure:
If you are able to factory reset it, remove the batteries, and Unplug Ethernet and leave it unplugged. Perform the factory reset (press and hold reset button while plugging in power, keep holding until flashing yellow LED goes yellow solid, then release the reset button)
Let the hub reboot and go through the motions and LED cycle allowing to boot and stay up for about 5 minutes (continue to keep Ethernet unplugged). Youāll see the led cycle red to magenta to flashing blue, etc.
after 5 minutes on flashing blue, power cycle the hub one more time by unplugging the hub and then plugging it back in (again, keep Ethernet unplugged) and allow the hub to boot.
then let it sit for 5 minutes without Ethernet. The LED will either be a flashing blue or solid blue at this point but after 5 minutes, now plug in Ethernet.
within about 1-2 minutes after finally plugging in Ethernet , you should see the LED go green and then it should pretty quickly go magenta to indicate it is download the firmwareā¦ donāt touch the hub at this point, just let it cook as it will do this cycle one more time before it finally gets upgraded to 57.x.
Let me share a little SmartThings history. ST stopped producing the V2 hubs in late 2017/early 2018. In mid 2018, SmartThings released a firmware that changed the servers that hubs connect to when they boot up. After a period of time, they decommissioned the old servers. If there were any new/unused hubs at the time the old servers shut down that had not received that firmware then they would not be able to reach the new servers. There is no way to fix if that is the situation.
try the ntp option (there have been v2 affected that were not connected for a period of time) and gather logs for staff to investigate your case in case the story I shared does not apply to you.
I understand about there being new servers and the history you shared, but I would have thought that a company as large as Samsung would have the resources to redirect a firmware update request from the old server to an active one that could still serve the necessary update. Especially since the V2 hub is still being developed for and supported, it feels like there should be a pathway to bring unused units online rather than leaving them permanently stranded.
i have now tried all the methods i can find around the web and the hub still shows no firmware version.
I have a post here on where I have recovered multiple V2 hubs: ensure you follow it exactly step by step.
the most important aspect is ensuring that you power it up WITHOUT Ethernet connected while doing the reset. Follow that process and the specified wait times.
Your post was the one I was referring to. I followed it to the letter twice. Yes, I even used a timer to track the time. Yes, I powered it up without Ethernet. You wrote it very clearly (thank you) and it wasnāt hard to follow.
The only thing I have not tried to blocking port 123 udp because I need to figure out how to do with that my new router.
To me, there may be something else wrong with my unit. Why is the LED solid blue = hub is claimed and connected to the network, but has no internet or server connection, but shows as connected in the SmartThings app? It properly connects to my thermostat and I can see it when off local Wi-Fi, so it has internet connection, right? I was also previously able to add Edge drivers, although now I get an error if I try.
You will need to figure out how to block poer 123 udp or if you have a friend or family member who can let you perform this on their network. If your hub has been sitting idle before March of this year, then you are experiencing the expired security certificate which will prevent your hub from updating to the latest firmware.
Is the Thermostat a linked service (cloud to cloud) which doesnāt require a hub?
I donāt believe firmware 38 was able to handle Edge drivers. But I canāt remember.
Are you successfully getting the solid yellow and flashing yellow LED? That reset process once completed and communicating to the cloud will successfully release the hub from any prior account.
I finally had some time to sit down and try this. My router is one of those that canāt block ports but I blocked NTP urls through parental controls. I tried resetting the hub per Itatiās instructions above, but donāt see the device trying to access any NTP servers. It only tries to access api.smartthings.com.
Iām going to leave it overnight and see if it tries to update after sitting for a while.
Oh, maybe thatās why? I did add it to SmartThings but itās a Nest thermostat so Iād guess itās a linked service.
Yes 20+ seconds of flashing yellow, then solid yellow. Iāve been able to add it and remove it from my account several times, during troubleshooting of edge drivers. The only difference from your instructions Iāve noticed is that the LED always cycles magenta first, then red, before flashing blue. I havenāt seen red before magenta, even though thatās also what the official documentation says,
Thanks for the reminder but my router canāt block ports. I only blocked NTP servers for the hub specifically. Itās still stuck on version 36 so Iāll try sending in my logs next.
I have three older hubs and they all are similar to yours. Somewhere in this thread is the actual explanation. Server changes were made and if your hub was not online then it missed a critical upgrade and has no way to reach the new servers. Technically those old ip addresses could be resurrected but Samsung doesnāt seem to have incentive to do that. I see quite a few on this thread in the same situation. Bottom line is that itās now a paperweight.
Is there any hack, workaround, or recovery method to bring this unused V2 hub online?
. After the final step, it just stays solid blue.