Authorisation issue

[tlustopro]

Hi, sorry to bother you. I have got issue with authorisation to Home Connect API. Home bridge generate me the URL, where i log in a grant permissions - no problem. Home connect page displays me the success message.
But i have got a error in the home bridge log as you can see below.

What i validate:

1. I copied right client ID
2. I have got same email on singleKeyID and Home Connect dev account
3. I have got right setup for app based on documentation of this repo

[14/03/2023, 14:44:17] [HomeConnect] Retrying client authentication in 60 seconds
[14/03/2023, 14:45:17] [HomeConnect] Requesting Home Connect authorisation using the Device Flow
[14/03/2023, 14:45:27] [HomeConnect] Home Connect API error: Connect Timeout Error
[14/03/2023, 14:45:27] [HomeConnect] Retrying client authentication in 60 seconds
[14/03/2023, 14:46:27] [HomeConnect] Requesting Home Connect authorisation using the Device Flow
[14/03/2023, 14:46:33] [HomeConnect] Home Connect authorisation required. Please visit:
[14/03/2023, 14:46:33] [HomeConnect]     https://api.home-connect.com/security/oauth/device_verify?user_code=SR6D-QB7A
[14/03/2023, 14:46:36] [HomeConnect] Configuration schema file updated: /var/lib/homebridge/.homebridge-homeconnect-v1.schema.json
[14/03/2023, 14:46:53] [HomeConnect] Home Connect API error: Connect Timeout Error
[14/03/2023, 14:46:53] [HomeConnect] Retrying client authentication in 60 seconds

My config file, which i set up using home bridge GUI:

{
    "platform": "HomeConnect",
    "clientid": "$clientId"
}

Any idea how to solve this, please? 🙏

[thoukydides]

The Connect Timeout Error means that the plugin was unable to connect to the Home Connect API server's Access Code Endpoint. Since the Device Authorization Request worked (to obtain the authorisation URL shown in the log file), and both requests use the same Amazon AWS gateway, this is almost certainly an internal problem within the Home Connect cloud services.

It will probably be fixed by the Home Connect team, so I suggest just trying again later.

[tlustopro]

Thank you! Do you know about some "status" page for Home Connect cloud services?

[thoukydides]

There was a status page on the Home Connect web site (https://www.home-connect.com/global/help-support/system-status) for a short period, but it always indicated that everything was OK even when it obviously wasn't. Hence, it wasn't actually of any use.

I operate my own unofficial status page at https://homeconnect.thouky.co.uk but that only checks the main API. It does not check anything relating to authorisation - both because that is difficult to automate (especially for problems like this where some parts of the authorization flow are working), and because the rate limits are very strict.

You could always try contacting the Home Connect Developer team at https://developer.home-connect.com/support/contact

[tlustopro]

Still same issue, it looks like there is no issue on Home Connect side. Can i provide you somehow more detailed log? Is it possible that my provider does block this specific request?
Also, this is my first plugin installed on new home bridge server. Maybe i need to do some initial settings of HB?

Log with debugger turned on:

[14/03/2023, 22:14:53] Homebridge v1.6.0 (HAP v0.11.0) (Homebridge C93C) is running on port 51214.
[14/03/2023, 22:15:35] [HomeConnect] Home Connect request #1: Headers Timeout Error +45849ms 
[14/03/2023, 22:15:35] [HomeConnect] Home Connect API error: Headers Timeout Error
[14/03/2023, 22:15:35] [HomeConnect] Retrying client authentication in 60 seconds
[14/03/2023, 22:16:35] [HomeConnect] Requesting Home Connect authorisation using the Device Flow
[14/03/2023, 22:16:35] [HomeConnect] Home Connect request #2: POST https://api.home-connect.com/security/oauth/device_authorization
[14/03/2023, 22:16:40] [HomeConnect] Home Connect request #2: OK +5520ms 
[14/03/2023, 22:16:40] [HomeConnect] Home Connect authorisation required. Please visit:
[14/03/2023, 22:16:40] [HomeConnect]     https://api.home-connect.com/security/oauth/device_verify?user_code=DZ4R-JSD2
[14/03/2023, 22:16:40] [HomeConnect] Waiting for completion of Home Connect authorisation (poll every 5 seconds, device code 71ae1b90-528a-422b-a934-7445b8ef110b expires after 600 seconds)...
[14/03/2023, 22:16:40] [HomeConnect] Scheduling configuration schema write
[14/03/2023, 22:16:43] [HomeConnect] Configuration schema file updated: /var/lib/homebridge/.homebridge-homeconnect-v1.schema.json
[14/03/2023, 22:16:43] [HomeConnect] Scheduled configuration schema write complete
[14/03/2023, 22:16:45] [HomeConnect] Home Connect request #3: POST https://api.home-connect.com/security/oauth/token
[14/03/2023, 22:16:46] [HomeConnect] Home Connect request #3: Authorisation pending +407ms 
[14/03/2023, 22:16:51] [HomeConnect] Home Connect request #4: POST https://api.home-connect.com/security/oauth/token
[14/03/2023, 22:17:01] [HomeConnect] Home Connect request #4: Connect Timeout Error +10064ms 
[14/03/2023, 22:17:01] [HomeConnect] Home Connect API error: Connect Timeout Error
[14/03/2023, 22:17:01] [HomeConnect] Retrying client authentication in 60 seconds
[14/03/2023, 22:18:01] [HomeConnect] Requesting Home Connect authorisation using the Device Flow
[14/03/2023, 22:18:01] [HomeConnect] Home Connect request #5: POST https://api.home-connect.com/security/oauth/device_authorization
[14/03/2023, 22:18:01] [HomeConnect] Home Connect request #5: OK +382ms 
[14/03/2023, 22:18:01] [HomeConnect] Home Connect authorisation required. Please visit:
[14/03/2023, 22:18:01] [HomeConnect]     https://api.home-connect.com/security/oauth/device_verify?user_code=3WMV-YA1G
[14/03/2023, 22:18:01] [HomeConnect] Waiting for completion of Home Connect authorisation (poll every 5 seconds, device code df90f572-447c-48f5-a1a3-41cd4193a110 expires after 600 seconds)...
[14/03/2023, 22:18:01] [HomeConnect] Scheduling configuration schema write
[14/03/2023, 22:18:04] [HomeConnect] Configuration schema file updated: /var/lib/homebridge/.homebridge-homeconnect-v1.schema.json
[14/03/2023, 22:18:04] [HomeConnect] Scheduled configuration schema write complete
[14/03/2023, 22:18:06] [HomeConnect] Home Connect request #6: POST https://api.home-connect.com/security/oauth/token
[14/03/2023, 22:18:16] [HomeConnect] Home Connect request #6: Connect Timeout Error +10059ms 
[14/03/2023, 22:18:16] [HomeConnect] Home Connect API error: Connect Timeout Error
[14/03/2023, 22:18:16] [HomeConnect] Retrying client authentication in 60 seconds

Could i call request using Postman or other software to verify if it works when i call it separately?

[thoukydides]

I have just tried it on my system, and it all works fine.

It could be an issue with the setup of your DNS resolution:
https://undici.nodejs.org/#/?id=network-address-family-autoselection.

However, it is strange that POST https://api.home-connect.com/security/oauth/device_authorization works reliably, but POST https://api.home-connect.com/security/oauth/token fails with UND_ERR_CONNECT_TIMEOUT. That strongly suggests that the issue is on the Home Connect server side, since both requests connect to the same host using the same options. It is only the server side that will care about the different paths.

If you want to try it yourself using a different client then you can find the documentation for these two requests at https://api-docs.home-connect.com/authorization?#device-flow.

There's a link to running the API in Postman at https://api-docs.home-connect.com/general. I haven't tried it myself, so don't know whether it supports the Device Flow authorisation or (like the Swagger client) only Authorisation Code Grant Flow.

You could also try the (unreleased) head of tree code for this plugin. The Home Connect API handling has been rewritten from scratch, so it uses slightly different options which might affect the behaviour. There are also new debug configuration options to log the full API requests and responses... although that feature won't be helpful when the HTTPS connect itself is failing.

[tlustopro]

Okay, I finally figured it out. The problem was in DNS. I changed the DNS on raspberry in the dhcpcd.conf file and it starts working. 🎉 Thanks for the help on how to fix it!