I´ve had troubles recovering my Homey. I could see packets exchanged to & from my Homey, but recovery procedure did not progress(halted) after “Connect to HomeySetup” & changing towards the “HomeySetup XXXX” wifi.
A support request at athom/homey is still pending. As they did not come back yet, i was eager to find out more myself…
Further investigation showed, Chrome CORS´s policy was blocking access towards Homey:
Access to XMLHttpRequest at ‘http://10.199.198.1/system’ from origin ‘http://setup.athom.com’ has been blocked by CORS policy: The request client is not a secure context and the resource is in more-private address space
Reading up, Chrome has changed its "private network access " policies (CORS-RFC1918: interaction local, private & public networks), enforcing https…However, the current Homey recovery still uses http…
Guess this issue must hit more people trying to recover Homey with a new Chrome (v94 and higher) instance…
My work around consisted of 2 parts:
- Run chrome browser without CORS
- Alter chrome flags: Set “Block insecure private network requests” to “disabled”
The full detailed solution including reference links is outlined in next posts (1st post within this community only allows upto 2 embedded links…I have more).
This worked for me:-)… Hope it works for you too:-)
Im not sure if step 1 is necessary…In trying to find a solution I started with step 1…