mercedesme-connector causes errors after host/js-controller update

[schlaubstar]

Hi,

after the latest upgrade of the IoBroker host (js-controller & npm) in particular, the adapter does not start anymore throwing the following error messages:

mercedesme.0 | 2023-12-14 10:03:14.436 | error | Error: Failure: Invalid wire type: %s (at position %s) -- | -- | -- | -- mercedesme.0 | 2023-12-14 10:03:14.434 | error | Websocket parse error mercedesme.0 | 2023-12-14 10:03:08.983 | error | Error: Failure: Invalid wire type: %s (at position %s) mercedesme.0 | 2023-12-14 10:03:08.979 | error | Websocket parse error mercedesme.0 | 2023-12-14 10:03:03.752 | error | Error: Assertion failed mercedesme.0 | 2023-12-14 10:03:03.750 | error | Websocket parse error mercedesme.0 | 2023-12-14 10:02:58.566 | error | Error: Failure: Invalid wire type: %s (at position %s) mercedesme.0 | 2023-12-14 10:02:58.564 | error | Websocket parse error mercedesme.0 | 2023-12-14 10:02:53.370 | error | Error: Assertion failed mercedesme.0 | 2023-12-14 10:02:53.369 | error | Websocket parse error mercedesme.0 | 2023-12-14 10:02:53.154 | error | "" mercedesme.0 | 2023-12-14 10:02:53.153 | error | AxiosError: Request failed with status code 418

[TA2k]

which version you are using

[TA2k]

please try the GitHub version

[schlaubstar]

I was on 0.1.1 from the official repository and then upgraded to v0.1.3 from Github, but the errors posted above are already from the latest Github version !

` mercedesme.0	2023-12-14 11:35:24.773	info	Got terminate signal TERMINATE_YOURSELF
mercedesme.0	2023-12-14 11:35:23.793	error	Error: Failure: Invalid wire type: %s (at position %s)
mercedesme.0	2023-12-14 11:35:23.791	error	Websocket parse error
mercedesme.0	2023-12-14 11:35:23.729	debug	WebSocket connected
mercedesme.0	2023-12-14 11:35:23.595	debug	Connect to WebSocket
mercedesme.0	2023-12-14 11:35:22.183	debug	Websocket closed
mercedesme.0	2023-12-14 11:35:22.180	debug	1006
mercedesme.0	2023-12-14 11:35:18.590	error	Error: Assertion failed
mercedesme.0	2023-12-14 11:35:18.589	error	Websocket parse error
mercedesme.0	2023-12-14 11:35:18.533	debug	WebSocket connected
mercedesme.0	2023-12-14 11:35:18.403	debug	Connect to WebSocket
mercedesme.0	2023-12-14 11:35:18.400	info	Start Websocket Connection
mercedesme.0	2023-12-14 11:35:18.397	error	""
mercedesme.0	2023-12-14 11:35:18.396	error	AxiosError: Request failed with status code 418
mercedesme.0	2023-12-14 11:35:18.209	debug	start refresh interval
mercedesme.0	2023-12-14 11:35:18.208	debug	Login successful
mercedesme.0	2023-12-14 11:35:18.205	debug	setRefrehToken: xxxxxx
mercedesme.0	2023-12-14 11:35:18.201	debug	{"access_token":"eyJhbGxxxxxxxx","token_type":"Bearer","expires_in":7199}
mercedesme.0	2023-12-14 11:35:17.574	debug	refreshToken
mercedesme.0	2023-12-14 11:35:17.571	debug	Login
mercedesme.0	2023-12-14 11:35:16.945	info	starting. Version 0.1.3 (non-npm: TA2k/ioBroker.mercedesme) in /opt/iobroker/node_modules/iobroker.mercedesme, node: v18.17.1, js-controller: 5.0.17

`

[TA2k]

Please use 0.1.6

[schlaubstar]

Wherever this version magically came from: it works! Thank you very much and have a great holiday season ! Also a big "thank you" to @TA2k

[Wer-ner]

Had the same issue as schlaubstar since Dec 12. The Version 0.1.6 has fixed the problem. @TA2k, Thank you very much!

[duejo46]

I had the same issue since this morning (Dec 14th). V0.1.1 and V0.1.3 didn´t work. V0.1.6 fixed it. Thanks a lot!

[DerFloBBy]

Same for me. With v0.1.6 it works again. Thanks! When will it become official?

[GieGit]

and the same for me. The Version 0.1.6 has fixed the problem and it works again.

[aklickermann]

I had the same issue and installed 0.1.6 from github. But the adapter does not show up in „instances“. What have I done wrong?

edit: I additionally installed the Adapter via „add instance“ and now I can see, configure and use it. It is working perfectly again. Thank you!