Afternoon. Thank you for your prompt response. As requested I have the log file on USB stick, but of course I cannot upload files here. Please send DM and I shall respond ASAP. Thanks Ian
I have the same issue. I have sent the log file to the mail. It gets stuck on ‘Connecting to device‘ for multiple minutes and then I get an error 33-504
I am having the same issue, as I moved 3 years ago and tried to set up my hub weeks ago with the same issue. Please help, as I tried all the troubleshooting with no success.
May I also get instructions?
Could you please confirm if you have already followed the steps in the post below?
Yes Yes Yes… multiple times. This is the Smartthings Hub V3P01 that I purchased from Amazon in 2020. I even tried to update the firmware over cellular. There has to be an easier way.
don’t believe that is even possible because in the steps provided, you need to reset while the hub is connected by Ethernet to your network.
first question, does your Router allow you to block port 123 udp or block the domain ntp.org? have you reset the hub (where you see solid yellow on the hub led? once you add the hub to the app, remove the block.
Hello, I’m experiencing error 33-504 during the installation of my Aeotec SmartThings Hub via the SmartThings app.
The hub is connected through Ethernet, and the network is stable. I have already:
Restarted the hub and router
Confirmed internet connectivity is working properly
Retried the setup multiple times
Despite this, the error persists and prevents the setup from completing.
Could you please provide more details on what error 33-504 indicates and how to resolve it? Let me know if you need additional information (network configuration, firmware version, etc.).
Follow the troubleshooting guide in the following thread to update the security certificate on the hub. It can be found in this thread: Troubleshooting SmartThings Hub 2018 and Aeotec Hub
The 33-504 error means “No internet while home AP connected”
The actual error number indicates a problem connecting to the internet. However there is also a specific issue which has arisen with V3/Aeotec hubs that results in the same error number when attempting to install hubs.
The problem is that the hub firmware includes a root certificate for securing communication with the update servers and certain hubs manufactured before about two years ago included one that expired in March last year. This wasn’t an issue for hubs that received firmware updates before then, but plenty were either purchased and not used, or sat on shelves unsold. Beyond that the details are a little vague. We haven’t been told, for example, if the issue only applies to ‘new’ hubs or if any hub that was not updated over a certain period of time would be affected.
Anyway the bottom line is that during installation the affected hubs are attempting to connect to the update servers and the expired certificate is preventing this access, causing installation to be terminated. Those who bought their hubs as new may be able to get them replaced as they are recognised as defective, but others who don’t have that option may be able to workaround the issue. A workaround can be to prevent the hub connecting to a time server to learn the correct time, resulting in it treating the expired certificate as valid and so being able to update the firmware to a version without the problem. Hence all the talk about NTP.
To me it seems like a significant cockup that deserved more than the rather matter of fact acknowledgement that it received.
Same issue Error code is 33-504 Serial number.. 3011081879. my hub has not been used for a while. and I just moved and want to get it set up..
Follow the troubleshooting guide posted above in several posts.