# Solid Blue Lights on Hub V2

[1dermutt]

I have a hub V2 which has worked flawlessly for 4 years. Last week I was adding 2 new devices (1) a z-wave wall outlet and (1) a zigbee switch. The pairing of the zigbee switch did not go correctly and I was having trouble getting it to pair to the hub correctly. To try to help the hub forget the zigbee device, I removed power/batteries from the hub for several minutes and then tried to bring the smart network back up. But, when the hub rebooted it came back to 3 solid blue lights and anything I have tried, it always comes back to 3 solid blue lights. I know this means the hub can’t authenticate with the Samsung cloud. Here is what I have tried to fix the issue:

1. power cycle the hub
2. power cycle the router
3. power cycle the cable modem
4. change the ethernet cable
5. Performed soft reboot of the hub
6. make sure the two new devices I tried installing have all power removed (tripped the actual circuit breaker) and repeat the above 5 steps.
7. ensure the hub is talking to the router. I can ping the hub on my network.
8. I have given the hub traffic priority at the router

I have 90+ devices tied into this integration. I would like to avoid performing a factory reset. Are there any thoughts on what to try to resolve this?

[jkp]

Try powering it off, remove the batteries, switch the Ethernet cable, power it back up without the batteries.

[1dermutt]

Yeah, I have tried those multiple times.

[DaWeav]

Have you tried changing the DNS servers that your DHCP server (router) gives out and then power on the Hub so it gets the new DNS settings to see what happens? If not, then try using Google’s DNS servers (8.8.8.8/8.8.4.4).

[1dermutt]

I followed your suggestion and set my router’s DNS settings to point to google’s (8.8.8.8 and 8.8.4.4), cycled the power on the hub and still 3 solid blue lights.

Is there a way for Smartthings to see if authentication requests are coming from my hub to their servers and are being rejected?

[Paul_Oliver (PCO)]

I bought a used v2 Hub as a spare.

I reset it twice and added it to my SmartThings account twice with out any issues.

It shows up in the both Mobile App and the AWA with Firmware 49.09.

I has a solid Blue light.

AWA says it has no ZigBee or Z-Wave support. No MAC or IP addresses are shown.

If I disconnect and reconnect the ethernet cable if flashed blue for a short time then goes back to solid blue.

If I disconnect and reconnect power I get a red light, then flashing blue, then solid blue

Switched ethernet cables and there was no changes.

@nayelyz @jkp

[nayelyz (SmartThings Developer Support)]

Hi, @Paul_Oliver
Can you open support access to your account, please?

1. Confirm the email account registered in the forum is the same one you use for SmartThings. If not, please share it with me over DM
2. Enable support access to your account:

1. Go to the SmartThings Web (my.smartthings.com)
2. Log in to your Samsung Account
3. Select Menu (⋮) and choose Settings
4. Toggle on Account Data Access
5. Select the time period and confirm - In this step, please select “Until turned off”, once the team finishes, we’ll let you know so you can disable it again.

See more information about this access here: https://support.smartthings.com/hc/en-us/articles/36170233944852-Enabling-Account-Data-Access-for-Support

[Paul_Oliver (PCO)]

Email is the same as the forum

Support access enabled until I manually turn it off

Hub is called Spare

[nayelyz (SmartThings Developer Support)]

Hi, @Paul_Oliver
I checked your hub and this case sounds similar to this one:

V2 hub issues

Hi, @gvpopov So, the engineering team mentioned that we need your help to follow the instructions here to disable the NTP port on the source side: Troubleshooting SmartThings Hub 2018 and Aeotec Hub This should help to update your hub, please let us know if you have any issues. Just as a heads-up. If you don’t see any option to do this on your router, you might have to connect the hub to another one from a friend/family member.

This hub had version 40, blue LED and Zigbee/Z-Wave radios displayed as “not supported”, so, after checking the hub logs, the engineering team suggested following the NTP port blocking workaround to help this hub update, and it worked.
Can you please follow the steps as well? I added the post on troubleshooting here as well:

Troubleshooting SmartThings Hub 2018 and Aeotec Hub

Use this guide for troubleshooting help with onboarding your Hub. We also include Hub replacement information if necessary. Overview When encountering the 33-504 error while claiming a SmartThings Hub 2018 (IM6001-V3P) or an Aeotec SmartThings Hub, the following root causes may apply: Your hub cannot access the internet over Ethernet or Wi-Fi connections Hubs manufactured before April 2024 may not have received firmware updates after production. If a Hub has not been claimed by March 2, 2025, it may not have been updated before purchase or activation. The following steps could be attempted to claim your hub successfully. Verify Internet Connectivity: Please verify the following: Your hub can connect to the internet If claiming over Ethernet, the LAN is internet-connected If claimin…

[Paul_Oliver (PCO)]

Thanks. I am currently away for a few days. I will give it a try when I get back.

[Paul_Oliver (PCO)]

Thanks for your help.

With your guidance and help from ChatGPT on how to change the setting on my Fios G3100 router I was able to get my used v2 hub installed and the firmware updated to 59.09. It took many tries before I got it right. The hub is functional, I can add community drivers and I was able to add a ZigBee device.

Thanks again