Closed MartiMan79 closed 7 months ago
Hmmm. Thats pretty difficult.
As you see here:
2023-12-26 11:41:34.357 - error: mielecloudservice.1 (493619) Error: Unable to authenticate user! Your credentials seem to be invalid. Please double check and fix them. 2023-12-26 11:41:34.359 - warn: mielecloudservice.1 (493619) Credentials used for login: 2023-12-26 11:41:34.359 - warn: mielecloudservice.1 (493619) options Miele_account: [xxx] 2023-12-26 11:41:34.359 - warn: mielecloudservice.1 (493619) options Miele_Password: [xxx] 2023-12-26 11:41:34.360 - warn: mielecloudservice.1 (493619) options Client_ID: [xxx] 2023-12-26 11:41:34.360 - warn: mielecloudservice.1 (493619) options Client_Secret: [xxx] 2023-12-26 11:41:34.360 - warn: mielecloudservice.1 (493619) options country: [nl-BE]
The Miele servers deny the login due to invalid credentials - thats the obvisious part. BUT ... on the other hand there are currently approx 2000 users running this adapter sucessfully. So the answer must be: It's an issue between your instance and Miele. The most common issue and the most possible I can currently think of (respecting what you wrote) might be that there could be a leading and/or trailing whitespace in one or more of your copy/pasted credentials - maybe you haven't checked for things like this. That's the reason why I log these data in brackets [] - to make whitespaces more visible. But there have been users in the past also facing issues like that - who solved it themself or in exchange with Miele. Currently there is no known issue with password encryption or the login procedure.
BTW: Do you use Server-Send-Events or simple polling?
Regarding your .1 instance: The config data gets overwritten every time you klick the save button - so it should be sufficient to fix the config of the .0 instance. This has been nessecary a few times in the past to solve changes within the password encryption.
So I requested new API credentials under the same application name and email address and I got exactly the same credentials as before. Also I uninstalled the adapter again and did a iob fix. Now it works, so I no idea what exactly fixed it but think the error was on Miele's server side...
Okay. I'm happy that it works for you now. But sad that we couldn't nail down the exact issue. I really don't know why issues like that happen every now and then.
Ran the adapter successfully in the past but deleted the instance only (adapter still installed) as not needed. Now I want Siri to inform me regarding time left for several appliances. Reinstalled adapter, created new instances (*.1 in case of old config data not being overwritten), registered a new API token and even updated my app credentials but no success. Before you ask, I checked, double checked and triple checked my credentials even while copy pasting... Miele website login works and Miele iOS app as well.
Version 6.5.4
CPU: 44,23 % RAM: 25 % Uptime: 0h Available: 5.0.17 Installed: 5.0.17 Events: ?15 / ?25 Platform: linux operating system: linux Architecture: arm64 CPUs: 4 Speed: 1800 MHz Model: Cortex-A72 RAM: 7.6 GB System uptime: 14 d. 21:12:21 Node.js: v18.19.0 time: 1703586333894 timeOffset: -60 NPM: 10.2.5 adapters count: 615 Disk size: 234.2 GB Disk free: 216.6 GB Active instances: 4 Path: /opt/iobroker/ Uptime: 00:00:48 alive: true _nodeCurrent: 18.19.0 _nodeNewest: 18.19.0 _nodeNewestNext: 18.19.0 _npmCurrent: 10.2.5 _npmNewest: 10.2.3 _npmNewestNext: 10.2.3
Thanks in advance and happy holidays!