I need to find someone that has a router that can allow the rules but I have bought 3 x devices with three different issues and don’t know which one to tackle.
Device 1. Everytime it updates gets stuck at 99%. Blue light, but is shown connected in the smart things app which is a good sign.
Device 2. Got to 99% installation and stopped. Now has Permanent Purple Light and can not be found on network and every time I hard reset it can’t go past the purple light so seems dead.
Device 3. Has the 33-504 error. I don’t have access to a router to disable UDP port 123 (NTP).
If you go to the Advanced Web App do either of hub 1 or 2 get listed in the hub section. If they do, does the firmware version show and what version are they on?
Any your mobile device is in the same 2.4 ghz WiFi network and subnet that your hubs are connected to?
If the firmware version is not appearing then most likely it did not get the needed firmware. You may want to reach out to Support or opt for the hub replace option depending on where you purchased the hubs.
Why should I buy a $300 router just to be able to get this device to work and then it’s not evenb guaranteed to work.
I don’t know what to do. It seems like staff don’t contact or even care to help.
@kriminal very well-put - why should we, the consumer, have to go through all this hassle to make something work that should be working out of the box? Samsung has it backwards.
I’ve initiated a return with the place I bought it from for a full refund, and set up the open-source Home Assistant instead. If you have an always-on PC or NAS I’d recommend investigating that route; you could add a zigbee dongle for less than half the price of ST v3 hub, and it was surprisingly not as hard to set up as I thought it would be.
It’s really the only way to fix this issue. Out of the box the hub thinks that the current date/time is the date the firmware was made and that the certificate is valid. As soon as it receives the real date, the certificate is invalid, because it’s expired.
Does your router or your ISP offer any domain name based filtering for blocking access to sites? If so you could perhaps try blocking access to pool.ntp.org temporarily rather than the NTP port. That assumes the hub doesn’t try other time servers.
Thanks guys, I managed to get this to work by using my friends router to block UDP port 123.
For people that have an issue there are two scenarios:
You may get the 33-504, and not get to the part where it downloads the firmware
You may see it downloading the update and install to 99% but it’s not actually doing anything. You will see downloading 40MB (or something close to that)
When It actually worked for me the downloading updates was 119MB. That is when I realised it was working and it finished 100% installation.
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.
If you can’t disable it on your Router, do you have any friends or neighbors who can disable it on their network and you can connect it on their network to get the valid certificate and firmware update so you can add it?
This is completely ridiculous… I have the same problem registering my hub… and I know that buying another one is not the solution because i will suffer the same problem as other users who have already shared their experience. My router does not allow me to block port 123 correctly. The support from Aeotec and SmartThings, which I have already contacted, do not admit the problem at its source. Few users avoid the problem. They manage to do so because their router allows them to modify the required settings or because they have computer knowledge that allows them to overcome the bug. I do not think it is right that they continue to sell a product that only works for some without a warning indicating that this product only works as advertised for some… Now for guidance… Wouldn’t it be much simpler to change the security modifications they made at the source and allow all hubs to register normally as was the case in the past??? Please, someone, correct me if I am wrong…
I don’t think there is anything they can do now. They should recall the devices, fixed them, then released them back into the market. I bought three devices and wasted hours trying to figure out the issue.
It’s strange it took them so long to announce there was an issue.
If you can’t block UDP port 123, unfortunately there is nothing else you can do to install the firmware.
