JeroenVdb / homebridge-daikin-cloud

This Homebrige plugin connects to the Daikin Cloud and loads all your devices to be controled via Homebridge and Homekit.
https://www.npmjs.com/package/homebridge-daikin-cloud
Apache License 2.0
32 stars 10 forks source link

[Bug] Fields "data.profile.communicationLanguage, data.profile.countryResidence" are absent #51

Closed nepofigist closed 3 months ago

nepofigist commented 3 months ago

Describe The Bug: Plugin can't login to user account in Daikin Cloud.

To Reproduce:

  1. Install plugin.
  2. Enable it.

Expected behavior: Login should be successful.

Logs:

[3/8/2024, 2:19:53 PM] [homebridge-daikin-cloud] Failed to get cloud devices from Daikin Cloud: Failed to login to Daikin Cloud with ***@***.***: Login failed: Missing required fields for registration: data.profile.communicationLanguage, data.profile.countryResidence
[3/8/2024, 2:19:53 PM] [homebridge-daikin-cloud] 

Plugin Config:

{
    "username": "***@***.***",
    "password": "***",
    "showExtraFeatures": true,
    "platform": "DaikinCloud",
    "_bridge": {
        "username": "***",
        "port": 37437
    }
}

Daikin Environment:

Homebridge Environment:

jwillemsen commented 3 months ago

Looks daikin broke things, other integrations having the same issue, see for example https://github.com/rospogrigio/daikin_residential/issues/209

GeneralMotors003 commented 3 months ago

I had exactly the same problem and found a workaround: 1) Log in to the Daikin Onecta app (if already logged in, log out and log in again) 2) Enter new required information, which is now asked for 3) Restart Homebdrige, the login now runs without problems

aroy314 commented 3 months ago

I had exactly the same problem and found a workaround:

  1. Log in to the Daikin Onecta app (if already logged in, log out and log in again)
  2. Enter new required information, which is now asked for
  3. Restart Homebdrige, the login now runs without problems

Worked for me ! Thank you ! 😊 🙏

JeroenVdb commented 3 months ago

I think the workaround is sufficient for closing this bug. I added some extra explanation to the error message. I think we should focus on the new API that is coming and that is a much bigger challenge.