When I attempt to configure the new version 2.0.2, I get an error message:
CannotRetrieveData: Cannot find account owner customer ID
Am I doing something wrong? It prompts for email/password/authenticator code. I’ve tried from the android and windows clients.
UPDATE: I see there is an issue posted on github, so I am not alone with this problem.
Similar here: I am not able to configure the new version 2.0.2, too.
Error message in my case is “CannotRetrieveData: Request failed: Service Unavailable”
my homey 2023 updated the app to .0.2 with no issues, and log in no probs,
my homey 2018 wont update to the latest.
This is due to app been switched to the Python SDK.
Apps made with Python SDK will not run on pre 2023 Homeys.
Noticed this wasn’t working
Version is 2.0.2
When I select Configure I get “CannotAuthenticate: MFA OTP code not found on login page”
What is wrong?
Am I just being daft? As soon as Homey restarts, none of the Echos are accessible anymore. I have to enter new 2FA codes several times just to get a connection again.
The old app was better.
Common error message: “CannotAuthenticate: MFA OTP code not found on the login page”
Homey early26, App 2.0.2
Reconnecting takes up to a minute after a restart. Also version 2.0.2 does give up to fast on loading the device list, which is why you see this error. Test version 2.0.3 does retry internally, but this can feel like it’s doing nothing/being stuck, still trying to see if I can optimize the process.
Making sure I’m correct here. The 2.0.3 does get further but has a note that sms or email authentication codes will not work and the only option is the authenticator app. In searching for the app in Google Play there seems to be a few options. Could you please clarify which app is correct?
I suffered a major crash, unable to restore a backup and am setting up from scratch.
After installing 2.0.2, it would connect after multiple tries but never find devices.
I installed 2.0.3. It still took 2 attempts to connect to Amazon but after connection found all devices on the first attempt. Thank you.
Microsoft Authentication, Google Authenticator, Apple Passwords, etc. really any of them will do..
Just published a new test version 2.0.4 that fixed sign-in failing with “Cannot find account owner customer ID” (affected accounts that had signed in several times).
If you previously couldn’t sign in, update and try again.
Runs almost reliably so far.
Unfortunately, ‘Execute Routine’ does not work when the Alexa Routine works with scenes…
This is my first time trying this method so I may be screwing up but I installed Google Authenticator and put in the credentials to include the 6 digit pass code. “give this to the developer” 535e2a78-9b88-4788-9b1f-afc8e0ec854a is the code spit out by the error reporting. KeyError: ‘openid.oa2.authorization_code’ is what I see. Does the Authenticator need to be specifically linked to Amazon somehow first?
If you try to login in a browser to amazon, are you able to use the code and it works?
Procedurally, I enter username then password then get a QR code which I scan with the authenticator which then asks for a pin which once entered completes the sign in. If I just use a passkey and type in the current 6 digit passkey on the authenticator it faults out and wants to send a text passkey to my phone.
getting this on login (2.0.4)
CannotConnect: Connection error during GET on Homey SHS
Just wanted to say thanks for this app, @staeff.
I migrated over from the older Alexa app after months of it dropping authentication every 24–48 hours and needing a manual re-link — a problem that never really got fixed there. Your app has been a completely different experience. The whole migration went smoothly in a single session: signed in with the authenticator code, paired all my Echoes and speaker groups on the first attempt, and rebuilt my flow cards without issue. Announcements (Say Message) and voice commands (Tell Command) are both working exactly as I need.
For a useful data point: US account, Homey Pro 2026, test version 2.0.4. I’ll report back after a week or so on whether the session holds — but the fact that it’s built on a long-lived refresh token instead of the old cookie/proxy approach already makes me optimistic.
Really appreciate how responsive you’ve been on this thread and how quickly you’ve been shipping fixes. Thanks again for building it.
