After changing form Version 4.3.0.202410201446 to the Marketplace binding, the Bridge (Account) is online and the Thing (Vehicle) stays unknown (Yellow).
result Trace with two BEV vehicles:
2025-01-03 08:50:57.242 [TRACE] [esme.internal.handler.AccountHandler] - IOException decoding message While parsing a protocol message, the input ended unexpectedly in the middle of a field. This could mean either that the input has been truncated or that an embedded message misreported its own length.
2025-01-03 08:51:09.184 [TRACE] [esme.internal.handler.AccountHandler] - IOException decoding message Protocol message contained an invalid tag (zero).
2025-01-03 08:51:21.171 [TRACE] [rcedesme.internal.server.MBWebsocket] - Websocket stop
2025-01-03 08:51:42.794 [TRACE] [rcedesme.internal.server.MBWebsocket] - Websocket start wss://websocket.emea-prod.mobilesdk.mercedes-benz.com/v2/ws
2025-01-03 08:51:42.993 [TRACE] [esme.internal.handler.AccountHandler] - MB Debug Message: Registering User with ciamID: xxxxxxxxxxxxx and App-UUID: xxxxxx-xxxx-xxxx-xxxx-xxxxxxxx
2025-01-03 08:51:42.997 [TRACE] [esme.internal.handler.AccountHandler] - MB Debug Message: app twin actor was initialized
2025-01-03 08:51:43.112 [TRACE] [esme.internal.handler.AccountHandler] - IOException decoding message Protocol message tag had invalid wire type.
2025-01-03 08:51:47.115 [TRACE] [esme.internal.handler.AccountHandler] - IOException decoding message Protocol message contained an invalid tag (zero).
2025-01-03 08:51:51.915 [TRACE] [esme.internal.handler.AccountHandler] - IOException decoding message Protocol message end-group tag did not match expected tag.
2025-01-03 08:51:57.676 [TRACE] [esme.internal.handler.AccountHandler] - IOException decoding message Protocol message end-group tag did not match expected tag.
2025-01-03 08:52:04.590 [TRACE] [esme.internal.handler.AccountHandler] - IOException decoding message Protocol message tag had invalid wire type.
2025-01-03 08:52:12.895 [TRACE] [esme.internal.handler.AccountHandler] - IOException decoding message Protocol message end-group tag did not match expected tag.
2025-01-03 08:52:22.853 [TRACE] [esme.internal.handler.AccountHandler] - IOException decoding message Protocol message contained an invalid tag (zero).
2025-01-03 08:52:34.801 [TRACE] [esme.internal.handler.AccountHandler] - IOException decoding message Protocol message had invalid UTF-8.
2025-01-03 08:52:42.818 [TRACE] [rcedesme.internal.server.MBWebsocket] - Websocket stop