You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Mercedes Me Account does show "Websocket Exception: Reason: {0}" and is kind of stuck in this state. The logs show the real issue [rcedesme.interna l.server.MBWebsocket] - onError Failed to upgrade to websocket: Unexpected HTTP Response Status Co de: 412 Precondition Failed
There is no way to reset the Account. Two weeks ago the refresh if the token failed and i had to delete Account from openhab and recreate it, now again.
Expected Behavior
The placeholder inside the log should be resolved. And there should be a way to reset the Account, e.g. like the Zigbee Binding does, this a switch hidden in advance settings of the thing.
Current Behavior
Possible Solution
See above
Steps to Reproduce (for Bugs)
Context
Your Environment
Version used: openHAB 4.3.2
Release Build
Environment name and version (e.g. Chrome 76, Java 8, Node.js 12.9, ...):
Operating System and version (desktop or mobile, Windows 10, Raspbian Buster, ...):
The text was updated successfully, but these errors were encountered:
The Mercedes Me Account does show "Websocket Exception: Reason: {0}" and is kind of stuck in this state. The logs show the real issue
[rcedesme.interna l.server.MBWebsocket] - onError Failed to upgrade to websocket: Unexpected HTTP Response Status Co de: 412 Precondition Failed
There is no way to reset the Account. Two weeks ago the refresh if the token failed and i had to delete Account from openhab and recreate it, now again.
Expected Behavior
The placeholder inside the log should be resolved. And there should be a way to reset the Account, e.g. like the Zigbee Binding does, this a switch hidden in advance settings of the thing.
Current Behavior
Possible Solution
See above
Steps to Reproduce (for Bugs)
Context
Your Environment
Release Build
The text was updated successfully, but these errors were encountered: