See the following warning messages within my openHAB log since a couple of days:
2026-08-29 13:12:16.940 [WARN ] [al.webservice.DefaultMieleWebservice] - Failed to fetch action state for device 000178021234: OTHER_HTTP_ERROR - HTTP error 404: Not Found
Cloud returned message: Optional[Device not found.]
Does anybody else also see such messages? Or is an issue with Miele server access known which limits the usage of the “Miele Cloud Binding”?
Using the Miele app on my iPhone, my washing machine as well as the tumble dryer are still operational.
device not found from the cloud usually means the token is fine but the appliance isnt attached to that account anymore, so the 400 in the api explorer tracks. hit /v1/devices with your token first, if the machine isnt in that list its nothing to do with openhab. if it is listed then the thing UID is stale, delete the miele thing and let it rediscover after the bridge re-auths. also grep the log for 401/403, once the refresh dies the binding just keeps spamming.
Thanks for this hints. But it seems that Miele has an API server issue. Its even actually not possible to grant a new API access or to pair an account. Everything i tried, is ending in “have actually a technical problem” or “server is unavailable”.
Get now different error messages than a couple of days ago:
2026-08-31 11:26:40.760 [WARN ] [al.webservice.DefaultMieleWebservice] - Cannot poll action state: Request execution failed.. Retrying...
2026-08-31 11:26:40.761 [WARN ] [rnal.auth.OpenHabOAuthTokenRefresher] - Token refreshing was requested but there is no token refresh listener registered!
2026-08-31 11:26:40.810 [WARN ] [al.webservice.DefaultMieleWebservice] - Failed to fetch action state for device 00011970xxxx: REQUEST_EXECUTION_FAILED - Request execution failed.
2026-08-31 11:26:40.850 [WARN ] [al.webservice.DefaultMieleWebservice] - Cannot poll action state: Request execution failed.. Retrying...
2026-08-31 11:26:40.851 [WARN ] [rnal.auth.OpenHabOAuthTokenRefresher] - Token refreshing was requested but there is no token refresh listener registered!
2026-08-31 11:26:40.889 [WARN ] [al.webservice.DefaultMieleWebservice] - Failed to fetch action state for device 00017802xxxx: REQUEST_EXECUTION_FAILED - Request execution failed.
After a restart of the Miele cloud binding, i get the following messages:
2026-08-31 12:15:52.674 [WARN ] [ebservice.UnavailableMieleWebservice] - Cannot re-emit device state for device '00011970xxxx': The Miele cloud service is not available.
2026-08-31 12:15:52.674 [WARN ] [ebservice.UnavailableMieleWebservice] - Cannot re-emit device state for device '00017802xxxx': The Miele cloud service is not available.
2026-08-31 12:15:52.681 [WARN ] [.internal.handler.MieleBridgeHandler] - Using legacy OAuth service handle, please re-authorize to migrate
2026-08-31 12:15:52.818 [WARN ] [ernal.webservice.sse.SseStreamParser] - SSE connection failed unexpectedly: org.eclipse.jetty.client.HttpResponseException: HTTP protocol violation: Authentication challenge without WWW-Authenticate header
2026-08-31 12:15:52.948 [ERROR] [oauth2client.internal.OAuthConnector] - grant type refresh_token to URL https://api.mcs3.miele.com/thirdparty/token failed with error code invalid_grant, description
I am actually not able to re-authorize my account. It always ends up in server error messages. Sent an email to the Miele developer account. They announced that the “old” authorization procedure will be discontinued in 2026. They are probably changing the procedure now?
Got openHAB running again using an “old” token which i generated for Home Assistant a couple of months ago. The token which i have used since many years in openHAB stopped working suddenly for unknown reason.
Actually a new token can’t be generated. Don’t know if this is a special effect related to my account or if this is currently not working in general. Forwarded the related error messages and windows to the Miele developers.
Unclear is also what the OAuth procedure should be. The new procedure for the future is described on the Miele developer portal as recommended way for new accounts but not yet functional. The existing OAuth legacy method should still work out (and my old token confirms this) but a new token can’t be generated using this authentication procedure. Quite a bit confusing…
