mrbungle64 / ioBroker.ecovacs-deebot

Control your Ecovacs Deebot and yeedi vacuum cleaner with ioBroker

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Crash durch Authentiation Error?

aski71 opened this issue · comments

Is there an existing issue for this?

  • I have searched the existing issues and no issue is describing my issue

The problem

Adapter verabschiedet sich mit Uncaught Termination nach Authentication Error.

With which model does the problem occur?

Deebot X2 series

From which source you have installed the adapter?

GitHub

Version of the ioBroker adapter ("info.version")

1.4.15-alpha.4

Version of the ecovacs-deebot.js library ("info.library.version")

0.9.6-beta.2

Version of the JS controller

5.0.19

Version of Node.js

18.19.1

Operating system

Linux

Anything in the logs that might be useful?

Zeit

	
Nachricht


ecovacs-deebot.0
2024-02-29 18:01:07.925	info	Product name: DEEBOT X2

ecovacs-deebot.0
2024-02-29 18:01:07.924	info	Library version: 0.9.6-beta.2

ecovacs-deebot.0
2024-02-29 18:01:07.922	info	Instance for 'MoX2' successfully initialized

ecovacs-deebot.0
2024-02-29 18:01:07.508	info	Using Device[0]: {"did":"69b9ba3c-6726-48eb-ac7a-26a77ecb5741","name":"E0B617982E1FPGZW0892","class":"lf3bn4","resource":"HjhV","company":"eco-ng","bindTs":1708337914318,"service":{"jmq":"jmq-ngiot-eu.dc.ww.ecouser.net","mqs":"api-ngiot.dc-as.ww.ecouser.net"},"deviceName":"DEEBOT X2","icon":"https://portal-ww.ecouser.net/api/pim/file/get/64dec730215d4f35d90f069a","ota":true,"UILogicId":"x2_ww_h_x2omnih5","materialNo":"110-2228-0203","pid":"634e4c1408f47c801ae3706e","product_category":"DEEBOT","model":"X2_OMNI_INT","updateInfo":{"needUpdate":false,"changeLog":""},"nick":"MoX2","homeId":"65a12142a640d325456023a6","homeSort":1,"status":1,"btName":"ECOVACS-lf3bn4-0892","btMac":"40:80:E1:C1:1F:A3","otaUpgrade":{},"deviceNumber":0}

ecovacs-deebot.0
2024-02-29 18:01:07.507	info	Successfully connected to Ecovacs server. Found 1 device(s) ...

ecovacs-deebot.0
2024-02-29 18:01:06.606	info	starting. Version 1.4.15-alpha.4 (non-npm: mrbungle64/ioBroker.ecovacs-deebot) in /opt/iobroker/node_modules/iobroker.ecovacs-deebot, node: v18.19.1, js-controller: 5.0.19

ecovacs-deebot.0
2024-02-29 18:00:35.150	info	terminating

ecovacs-deebot.0
2024-02-29 18:00:34.647	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason

ecovacs-deebot.0
2024-02-29 18:00:34.646	info	terminating

ecovacs-deebot.0
2024-02-29 18:00:34.646	info	cleaned everything up...

ecovacs-deebot.0
2024-02-29 18:00:34.644	error	unhandled promise rejection: false

ecovacs-deebot.0
2024-02-29 18:00:34.644	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

ecovacs-deebot.0
2024-02-29 18:00:34.642	error	Received disconnect event from library: true

ecovacs-deebot.0
2024-02-29 18:00:34.641	error	Received disconnect event from library: true

ecovacs-deebot.0
2024-02-29 18:00:34.641	warn	RequestOAuthError: Authentication error

ecovacs-deebot.0
2024-02-29 18:00:33.631	error	Received disconnect event from library: true
Hier die Logs:

ecovacs-deebot.0
2024-02-29 18:00:33.631	info	cleaned everything up...

ecovacs-deebot.0
2024-02-29 18:00:33.630	error	Received disconnect event from library: true

ecovacs-deebot.0
2024-02-29 18:00:33.628	warn	RequestOAuthError: Authentication error

Additional information

No response

Which "other" models are you using?

No response

Ecovacs device class ("info.deviceClass")

No response

Communication protocol ("info.library.communicationProtocol")

None

Is the canvas module installed? ("info.library.canvasModuleIsInstalled")

None

@aski71

Den ersten "Authentication error" scheint der Adapter ja noch halbwegs gehandelt zu haben.

Kam der "RequestOAuthError: Authentication error" nur zu diesem Zeitpunkt oder jetzt schon öfter mal?
Falls ja, hatte das dann auch immer den "Terminated (UNCAUGHT_EXCEPTION): Without reason" zur Folge?

Habe das bisher nur einmal gesehen. Ich halte mal weiter ein Auge drauf.

Heute hatte ich das nach einer Ewigkeit zum erstenmal erneut:

` 2024-04-21 15:51:17.059 info Successfully connected to Ecovacs server. Found 1 device(s) ...

ecovacs-deebot.0
2024-04-21 15:51:16.053 info starting. Version 1.4.15 in /opt/iobroker/node_modules/iobroker.ecovacs-deebot, node: v18.19.1, js-controller: 5.0.19

ecovacs-deebot.0
2024-04-21 15:50:44.669 info terminating

ecovacs-deebot.0
2024-04-21 15:50:44.167 warn Terminated (UNCAUGHT_EXCEPTION): Without reason

ecovacs-deebot.0
2024-04-21 15:50:44.167 info terminating

ecovacs-deebot.0
2024-04-21 15:50:44.166 info cleaned everything up...

ecovacs-deebot.0
2024-04-21 15:50:44.164 error unhandled promise rejection: false

ecovacs-deebot.0
2024-04-21 15:50:44.164 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

ecovacs-deebot.0
2024-04-21 15:50:44.161 error Received disconnect event from library: true

ecovacs-deebot.0
2024-04-21 15:50:44.160 warn RequestOAuthError: Authentication error

ecovacs-deebot.0
2024-04-21 15:50:43.155 info cleaned everything up...

ecovacs-deebot.0
2024-04-21 15:50:43.154 error Received disconnect event from library: true

ecovacs-deebot.0
2024-04-21 15:50:43.145 warn RequestOAuthError: Authentication error`