So there is a chance, that this behaviour is not triggered by my installation of OH?
I think so, as you did not change anything in your installation and it suddenly stopped working.
If it is on Miele’s side, is there any chance to get a clue on the changes they probably made? And therefore if you can make a new binding version…?
I doubt that this is a problem with the binding. Could you check the cloud status of your devices?
As an explanation: The binding does not connect directly to your devices, it only connects to the Miele Cloud and relies on the information provided from there. The cloud reports a connectivity status for each device that the binding maps to the thing status in openHAB. So if the cloud reports a device as not connected then this will cause the thing status to be set to not connected, too.
yes, that was exactly my understanding of how it works (or should…).
Therefore I checked in the meanwhile the device through the Miele app and et voilá: device shown as “not connected”. Playing a little bit “back and forth” in the app shows sooner or later an error warning from the app “Miele server reports error 500.”.
I filed a report directly out of the app for support on this. Maybe they will give me call back to solve the problem (their problem).
Today (2024/22/03) MIELE responded to my file and sent me an email, informing me that they fixed the(ir) problem:
Thank you for your inquiry.
Our colleagues in the department informed us that the behavior of the Miele app you described was fixed yesterday with the help of a hotfix.
You should now be able to reconnect your freezer as usual. It may be necessary for you to log out of the Miele app in advance and then log in again with your user account.
You will find the option to log out via the “Profile” tab under “Profile Settings”.
If you observe any further irregularities, please contact us again.
THANK YOU MIELE!
And of course thanks to you both, Björn & Levin, for stepping in here!
I noticed that I’m unable to start the dishwasher since around 2025-03-28.
Other values like state or remaining program time is working so the device seems to be online.
Is anyone else experiencing this? It looks like an issue on Miele side.
Error log stated the following:
2025-03-30 19:39:57.993 [WARN ] [al.webservice.DefaultMieleWebservice] - Failed to perform PUT request: HTTP error 500: Internal Server Error
Cloud returned message: Optional[GENERIC_BUSINESS_ERROR - INTERNAL_SERVER_ERROR]. Retrying...
2025-03-30 19:39:58.237 [WARN ] [handler.DishwasherDeviceThingHandler] - Failed to perform 'START' operation for device '000106275417'.
org.openhab.binding.mielecloud.internal.webservice.exception.MieleWebserviceException: Unable to perform operation. Operation failed 2 times.
at org.openhab.binding.mielecloud.internal.webservice.retry.NTimesRetryStrategy.performRetryableOperation(NTimesRetryStrategy.java:65) ~[?:?]
at org.openhab.binding.mielecloud.internal.webservice.retry.RetryStrategyCombiner.performRetryableOperation(RetryStrategyCombiner.java:44) ~[?:?]
at org.openhab.binding.mielecloud.internal.webservice.retry.RetryStrategy.performRetryableOperation(RetryStrategy.java:54) ~[?:?]
at org.openhab.binding.mielecloud.internal.webservice.DefaultMieleWebservice.putActions(DefaultMieleWebservice.java:338) ~[?:?]
at org.openhab.binding.mielecloud.internal.webservice.DefaultMieleWebservice.putProcessAction(DefaultMieleWebservice.java:214) ~[?:?]
at org.openhab.binding.mielecloud.internal.handler.AbstractMieleThingHandler.lambda$1(AbstractMieleThingHandler.java:181) ~[?:?]
at org.openhab.binding.mielecloud.internal.handler.AbstractMieleThingHandler.lambda$9(AbstractMieleThingHandler.java:203) ~[?:?]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539) [?:?]
at java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) [?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) [?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) [?:?]
at java.lang.Thread.run(Thread.java:840) [?:?]
Caused by: org.openhab.binding.mielecloud.internal.webservice.exception.MieleWebserviceTransientException: HTTP error 500: Internal Server Error
Cloud returned message: Optional[GENERIC_BUSINESS_ERROR - INTERNAL_SERVER_ERROR]
at org.openhab.binding.mielecloud.internal.webservice.HttpUtil.checkHttpSuccess(HttpUtil.java:66) ~[?:?]
at org.openhab.binding.mielecloud.internal.webservice.DefaultMieleWebservice.lambda$8(DefaultMieleWebservice.java:347) ~[?:?]
at org.openhab.binding.mielecloud.internal.webservice.retry.RetryStrategy$1.get(RetryStrategy.java:57) ~[?:?]
at org.openhab.binding.mielecloud.internal.webservice.retry.RetryStrategy$1.get(RetryStrategy.java:1) ~[?:?]
at org.openhab.binding.mielecloud.internal.webservice.retry.AuthorizationFailedRetryStrategy.performRetryableOperation(AuthorizationFailedRetryStrategy.java:67) ~[?:?]
at org.openhab.binding.mielecloud.internal.webservice.retry.RetryStrategyCombiner.lambda$0(RetryStrategyCombiner.java:44) ~[?:?]
at org.openhab.binding.mielecloud.internal.webservice.retry.NTimesRetryStrategy.performRetryableOperation(NTimesRetryStrategy.java:54) ~[?:?]
... 12 more
I have the exact same error message. The dishwasher is new and my integration in openhab is new, so it was never working on my side. Glad to hear, that I’m not the only one with this problem. I wrote a mail to miele developer support. Maybe it could help if you also report this, so it increase priority a bit…
EDIT: Maybe I should add that this problem also occurs when using the swagger api site on miele.com. So I don’t think it is a problem specific to the binding.
As far as I know this is not possible because of restrictions on Miele side, at least for the dishwasher.
You have to choose the program on the appliance and choose smart start.
Otherwise you can use the Miele App to choose and start a program. I’m not sure if you can choose smart start in the Miele App.
thanks for confirmation. What works is to set the appliance to “Remote Start” and select a program via the Miele@Home app. Once that’s done, I can start the program via Miele@Home app or openHAB (e.g. after reaching a certain threshold in regards to solar yield).
Hi,
I have an issue from time to time. I have a dishwasher and registered via the documentation and it works well. After weeks it stopps working, thing and bridge go “red” in OH. On /mielecloud the bridge is offline.
The only solution to get it back online: create a new account and do all configuration over again. Is there another way to get it back online? Do I oversee something?
Hi @parachutesj, this sounds like an issue with the access token refresh to me. When it happens the next time, before re-creating the things follow these instructions and message me on the result.
For all who get new generation of devices like my W2 washing machine nova edition (WQ1200/WQ100-12 CH), they seem not to be supported yet
The developper site is stating the following:
Important - New generation washer/dryers and new generation vacuum cleaners. Endpoints for the new generations are not yet available and will be released in the fall of 2025.
Hallo,
i have the same issue in multiple times.
I have to renew the account every time.
The result of the check according to your linked documentation:
it seems like the OAuth token refresh with the Miele 3rd Party API fails. Please check the following:
What is the exact thing state of the bridge?
Are there any logs provided about failed token refreshes? Most relevant is a log entry saying “Failed to refresh OAuth token” and the attached exception info.
Some of the relevant logs are only shown on DEBUG level, so please increase the log level to DEBUG for the mielecloud binding and then restart it. A token refresh attempt should take place automatically.
Today I’m experiencing the same issue.
In GUI I have the following Error:
Logfile Entry:
2025-05-19 07:30:04.825 [ERROR] [oauth2client.internal.OAuthConnector] - grant type refresh_token to URL https://api.mcs3.miele.com/thirdparty/token failed with error code invalid_grant, description