I hadn’t tried that before your suggestion, but I just did: I set the location in Homey to the US, tested it, and then switched it back to Germany. Unfortunately, I’m still getting the exact same error.
FYI When you wanted to copy the signal: most 433MHz garage/gate remotes can’t be used with Homey, because they use so called rolling code, to prevent it from copying (by unwanted ‘guests’).
Thanks for pointing that out! I actually have a Tesla in the garage where I had HomeLink installed afterwards. With that setup, the Tesla successfully cloned my remote key — and since then the garage door reliably opens and closes automatically when I approach or leave.
Because this has been working fine for months, I don’t think my garage door uses rolling code. That’s why I’m quite sure my issue is not the remote type, but rather Homey blocking 433 MHz due to the “country: US” restriction.
It looks during Homey activation, the IP address of the request is used to look up the country of origin. Since IP databases change all the time (and are notoriously unreliable anyway) it doesn’t surprise me that Starlink IP addresses aren’t being identified properly.
Why it’s not possible to override this by setting the proper location manually, I don’t know, only Athom will be able to say.
Can you open Homey Developer Tools , log in and check for any US reference? And not sure if Homeys sold in the US have 433 MHz blocked altogether. Might your Homey possibly be a non EU one?
No, it’s handled in software: the RF manager checks if the country is blacklisted (US, CA, KR) and if so, emits the error message. And the country seems to only be determined at activation time (so first time you power on Homey and set it up).