Home Connect, region issues
See original GitHub issueThe problem
For the first, I’m from Russia. BOSCH leaved the market by the first days of war. Since then:
- It seems my Home Connect client account was deleted. I managed to create a new one with the same email address, but this time I choosed US region. It worked, my wash machine works again from the app.
- Developer account is… Shadow blocked? I don’t know how to describe it, but it’s fun. It always says my password is incorrect -> Recovery it -> Then I sign in with one-time link method, and then it works. But if I choose to log out, I can’t login with the new password and should repeat the trick. I also changed my region to the US, but it keeps happening.
- Integration stopped working, so I re-added it. Everything I get now is error
{
"error": "unauthorized_client",
"error_description": "client or redirection URI not authorized",
"state": ""
}
The interesting fact:
- Even if I change callback-url in Home Connect Developer, it remains the same (previous) in the b64 error state.
- If I create a new app to get a new client ID/secret pair and update it in the configuration.yaml, it also remains the same in the given URL
https://api.home-connect.com/security/oauth/authorize?response_type=code&client_id=[previous client_id which is already unpresent in configuration.yaml]
- Tried to change callback-url to external https / internal http, no luck with that.
So… That’s it. Is there any other users from Russia? Did anyone had this issue, and if so - how did you resolved it?
For the devs - I know it’s probably not the integration issue, but I think it should be somewhere in “Issues”. At last, we need a place to discuss it, and maybe find a way to bypass theese restrictions.
What version of Home Assistant Core has the issue?
2022.5.5
What was the last working version of Home Assistant Core?
2022.5.5
What type of installation are you running?
Home Assistant Container
Integration causing the issue
Home Connect
Link to integration documentation on our website
https://www.home-assistant.io/integrations/home_connect/
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
Issue Analytics
- State:
- Created a year ago
- Comments:7 (1 by maintainers)
Top Results From Across the Web
FAQ - Home Connect
If your new country cannot be found in the list, any further use of the Home Connect app is not supported by us...
Read more >Fixing the common connectivity errors - Home Connect
On occasion, error messages about connectivity issues can appear on your appliance. We will take a closer look at the four most common...
Read more >Home Connect Connection Guide
The Home Connect Connection Guide allows you to connect your smart home appliances quickly and easily. Find out about all required steps here....
Read more >Works with - Home Connect
Please note, availability of certain partners may depend on your region. ... Do you have any questions about Home Connect issues? In our...
Read more >Home Connect error codes
Ensure your appliance is connected to the right network (Note some appliances only work with 2.4 GHz and will not connect to 5...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’m running into the same problem (
"client or redirection URI not authorized"
) when setting up for the first time, although I’m in New Zealand. ~What exactly does the configuration yaml look like @Sleepy81 – I’d like to give it a try and see if it helps. Thank you.~UPDATE: Manually editing configuration.yaml fixed the problem for me too.
Hi @Drun555! You posted a token in your message, you should delete it as it should not be public. To solve your problem, you could try creating a new developer account.