Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adapter in restart loop #678

Closed
1 task done
ponG86 opened this issue Apr 28, 2024 · 1 comment
Closed
1 task done

Adapter in restart loop #678

ponG86 opened this issue Apr 28, 2024 · 1 comment
Labels
Potential bug Potential bug Verification Verification

Comments

@ponG86
Copy link

ponG86 commented Apr 28, 2024

Is there an existing issue for this?

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

The problem

Since a few days, iobroker notifies me that the deebot adapter is not startet, as a restart loop was detected. The loop is always caused by the same sequence of errors in the logfile.
The error occurs in the context of "getWaterInfo". Behavior is not impacted by using or not using the waterbox.

I attached a logfile. Sorry for the format, git won't let me attach the html provided by iobroker frontend.
log.txt

Thanks for the adapter and your effort!

With which model does the problem occur?

Deebot N8 series

From which source you have installed the adapter?

Stable (default)

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

1.4.15

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

0.9.6-beta.3

Version of the JS controller

4.0.24

Version of Node.js

18.20.2

Operating system

Linux

Anything in the logs that might be useful?

Look for waterboxinfo

Additional information

No response

Which "other" models are you using?

none

Ecovacs device class ("info.deviceClass")

7zya6u

Communication protocol ("info.library.communicationProtocol")

MQTT

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

yes (true)

@ponG86 ponG86 added Potential bug Potential bug Verification Verification labels Apr 28, 2024
@mrbungle64
Copy link
Owner

@ponG86

The problem is caused by running with JS Controller version 4.0.x
See also #671

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Potential bug Potential bug Verification Verification
Projects
None yet
Development

No branches or pull requests

2 participants