a critical blocking issue during the initial setup of my newly purchased Homey Pro (2026). I am attempting to migrate from my Homey Pro (2023) using a Cloud Backup, but the device is completely unusable due to a firmware update freeze.
During the initial setup process (both via the mobile app and via usb.homey.app DFU mode), the firmware update initiates but gets permanently stuck at 0% or 1% and refuses to progress, even after waiting for hours.
Here are the troubleshooting steps I have already performed without success:
Tried setting up via the mobile app over both local Ethernet adapter and Wi-Fi.
Ensured the phone had all VPN and local network isolation disabled.
Performed a hard power cycle multiple times.
Attempted a manual firmware update using the WebUSB tool (usb.homey.app) in Chrome/Edge, which also hangs indefinitely at the very beginning of the download/flash process.
It appears the update servers are either unreachable, timing out, or throttling the connection for my device, leaving the new Homey Pro (2026) completely bricked in setup mode.
I’ve been using the same cables for years and tried to start the offline update on the same laptop that I’ve successfully used for this countless times before. The update doesn’t start on the old Homey either, neither online nor offline. What should I check on the router?
That was just a thought if you are using the WiFi connection. Sometimes the connection gets worse over time if a WiFi router has been operating for long periods w/o a restart.
Problem solved: Athom’s update servers are occasionally simply unable to handle the massive number of download requests. I managed to complete the update early this morning.
@Doekse Abe, if statement below is true (which I think it is), isn’t it a plan to expand the progress bar with a simple line showing something like: Unable to perform request, please try again later → It’s safe to abort this procedure now
or
when download progress stalls for x minutes, show the same message?
I think it isn’t. Homey uses Cloudflare CDN for updates, so it doesn’t work like a regular server. There is an origin server, which hosts the actual files. The URL is behind Cloudflare, so the Cloudflare servers in your region get the file from the origin server, and then cache those files so that it doesn’t have to get it again for a few minutes. All further update downloads will be served from the cache, so the download will be faster too.
There is also the OTA API. This runs on servers, but it runs together with all the other microservices (push notifications, remote access, Google Home/Alexa, the API, etc.) on a few servers. So these should then experience issues as well, which they don’t. Most modern cloud services have automatic scaling based on demand as well
