GithubHelp home page GithubHelp logo

iobroker.botvac's People

Contributors

apollon77 avatar arensman avatar dependabot[bot] avatar germanbluefox avatar klein0r avatar mcm1957 avatar petervoronov avatar pmant avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar

iobroker.botvac's Issues

Problems with log-in since few days

Since few days, my adapter log shows:

botvac.0 | 2020-09-27 17:50:33.728 | warn | (757) login failed

did anyone knows what toDo? He sends this status every 15 minutes.. And the Bot is not working via script
Logindata is correct, Neato is functioning via mobileapp perfectly.
Please help.

Thanks

Compatibility check and testing for Node.js 14 and 16

Dear Adapter develop,

Node.js 14 is now available for a year and Node.js 16 was release just some days ago and will become LTS by October 2021. We plan to update the ioBroker Node.js recommendation (currently 12.x) to 14.x later this year.

Please check your adapter with Node.js 14 especially, and ideally also directly with Node.js 16

Please add both versions to the adapter testing which is executed on commits.

If your adapter requires a certain minimum version of Node.js please set the 'engine' setting in package.json accordingly! Please also do this if the adapter is not able to work in certain Node.js versions, so that ioBroker can prevent users from installing te adapter if not compatible!

On questions please talk to us at ioBroker/ioBroker.js-controller#1138

Please close the issue after you checked it.

Thank you very much for your support!

[Feature] Zonen Reinigung

In der doku von Node-Botvac habe ich gesehen das es Funktionen für die Zonenreinigung gibt.
z.B.
robot.getPersistentMaps([callback])
Returns the persistent maps of the robot

callback - function(error, schedule)
error null if no error occurred
maps Maps[] - array of maps

ich habe leider keine Ahnung von der Adapter Programmierung deshalb meine Frage ob es möglich wäre diese Funktionen noch in dieses Adapter zu integrieren damit man dann D7 über Vis zu den jeweiligen Räumen zu schicken ohne den Umweg über die Neato App zugehen

schöne Grüße
Enrico

Please check ioBroker.botvac with js-controller 2.0

Hi,

the new js-controller 2.0 will come into latest repository in the next days and we want to make sure that all adapters are working well. We already did a 2 weeks Beta test and so some adapter were aleady checked and some needed slight adjustments.

You can find more information in ioBroker/ioBroker.js-controller#482 and in the ioBroker Forum. If you have more technical questions please write in the referenced issue or in the Developer thread please. General questions are best in the genral thread.

Please update your systems to js-controller 2.0 and check your adapter.

Please close this issue once you have checked your adapter or received successfull reports from users.

Thank you very much for your support. Please contact us in the other Threads or Forum on any question.

RESTART LOOP DETECTED

Hello,

i am actually facing the Same Problem like in Issue number #14 .

I hope you can help me.
System is a RASPI 4 with ioBroker.
Node.js v12.22.1
NPM 6.14.12
JS-Controller 3.2.16

host 2021-10-09 14:38:01.061 warn Do not restart adapter system.adapter.botvac.0 because restart loop detected
host 2021-10-09 14:38:01.060 info Restart adapter system.adapter.botvac.0 because enabled
host 2021-10-09 14:38:01.060 error instance system.adapter.botvac.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
botvac.0 2021-10-09 14:38:00.436 warn Terminated (UNCAUGHT_EXCEPTION): Without reason
botvac.0 2021-10-09 14:38:00.435 info terminating
botvac.0 2021-10-09 14:38:00.416 error Cannot read property 'isCharging' of undefined
botvac.0 2021-10-09 14:38:00.415 error TypeError: Cannot read property 'isCharging' of undefined at Robot. (/opt/iobroker/node_modules/node-botvac/lib/robot.js:40:50) at /opt/iobroker/node_modules/node-botvac/lib/robot.js:320:17 at Request._callback (/opt/iobroker/node_modules/node-botvac/lib/api.js:42:45) at Request.self.callback (/opt/iobroker/node_modules/request/request.js:185:22) at Request.emit (events.js:314:20) at Request. (/opt/iobroker/node_modules/request/request.js:1154:10) at Request.emit (events.js:314:20) at IncomingMessage. (/opt/iobroker/node_modules/request/request.js:1076:12) at Object.onceWrapper (events.js:420:28) at IncomingMessage.emit (events.js:326:22)
botvac.0 2021-10-09 14:38:00.413 error uncaught exception: Cannot read property 'isCharging' of undefined
botvac.0 2021-10-09 14:37:59.616 info devices found: 1
botvac.0 2021-10-09 14:37:58.459 info starting. Version 1.0.0 in /opt/iobroker/node_modules/iobroker.botvac, node: v12.22.1, js-controller: 3.2.16
host 2021-10-09 14:37:56.162 info instance system.adapter.botvac.0 started with pid 31108

I hope you can help me.

Greetings

Update stable version in repo from 2.0.1 to 2.0.2

Think about update stable version to 2.0.2

Version: stable=2.0.1 (109 days old) => latest=2.0.2 (15 days old)
Installs: stable=256 (53.11%), latest=32 (6.64%), total=482

Click to use developer portal
Click to edit

Note: This is an automatically generated message and not personally authored by bluefox!

Installation issues of the adapter

Hello,

I have an issues with installation of the adapter with npm version.
Following error meassage was displayed at iobroker:

ERROR: Process exited with code 25
$ iobroker url https://github.com/iobroker-community-adapters/ioBroker.botvac#200-alpha1-2023-09-15 --host BRIX03 --debug
install iobroker-community-adapters/ioBroker.botvac#34f4a07e0ed92c9895c57c686a15ecf2596baa4a
NPM version: 9.8.1
Installing iobroker-community-adapters/ioBroker.botvac#34f4a07e0ed92c9895c57c686a15ecf2596baa4a... (System call)
npm ERR! code ENOENT
npm ERR! syscall spawn git npm ERR! path git
npm ERR! errno -4058
npm ERR! enoent An unknown git error occurred npm ERR! enoent This is related to npm not being able to find a file. npm ERR! enoent
npm ERR! A complete log of this run can be found in: C:\Windows\system32\config\systemprofile\AppData\Local\npm-cache_logs\2023-11-04T14_11_16_935Z-debug-0.log
npm ERR! code ENOENTnpm ERR! syscall spawn gitnpm ERR! path gitnpm ERR! errno -4058npm ERR! enoent An unknown git error occurrednpm ERR! enoent This is related to npm not being able to find a file.npm ERR! enoent npm ERR! A complete log of this run can be found in: C:\Windows\system32\config\systemprofile\AppData\Local\npm-cache_logs\2023-11-04T14_11_16_935Z-debug-0.log
host.BRIX03 Cannot install iobroker-community-adapters/ioBroker.botvac#34f4a07e0ed92c9895c57c686a15ecf2596baa4a: 4294963238

ERROR: Process exited with code 25

What can be the problem? With old version on another systems it works.
THX!

Adapter plötzlich im restart-loop

Hallo,

plötzlich heute morgen hat der Adapter Fehler geworfen und ist in den Restart loop gekommen und ist dann vom js-controller deaktiviert worden. Anbei die Info-Log aus dieser Zeit.
Was möglicherweise der Auslöser sein könnte ist, dass einer der Roboter nicht erreichbar ist. Steht in einem andern Haus und dort dürfte gerade das Internet nicht funktionieren. Aber kann das den Adapter niederreissen?

edit: Nachdem der Roboter wieder im Netz war ließ sich der Adapter wieder problemlos starten.

2023-09-19 08:01:00.705 - warn: botvac.0 (57835) could not update robot Turnverein Oben
2023-09-19 08:01:00.709 - warn: botvac.0 (57835) Read-only state "botvac.0.Turnverein Oben.status.reachable" has been written without ack-flag with value "true"
2023-09-19 08:01:00.755 - warn: botvac.0 (57835) Read-only state "botvac.0.Turnverein Oben.status.reachable" has been written without ack-flag with value "true"
2023-09-19 08:02:14.587 - warn: botvac.0 (57835) could not update robot Turnverein Oben
2023-09-19 08:02:16.367 - info: botvac.0 (57835) devices found: 3
2023-09-19 08:02:16.395 - warn: botvac.0 (57835) Device"Turnverein Oben" with id: Turnverein Oben is not exists in cloud any more!
2023-09-19 08:02:16.635 - warn: botvac.0 (57835) Device"Erdgeschoss" with id: Erdgeschoss is not exists in cloud any more!
2023-09-19 08:02:16.636 - warn: botvac.0 (57835) Device"Turnverein Oben" with id: Turnverein Oben is not exists in cloud any more!
2023-09-19 08:02:16.969 - warn: botvac.0 (57835) Device"Erdgeschoss" with id: Erdgeschoss is not exists in cloud any more!
2023-09-19 08:02:16.969 - warn: botvac.0 (57835) Device"Keller" with id: Keller is not exists in cloud any more!
2023-09-19 08:02:16.969 - warn: botvac.0 (57835) Device"Turnverein Oben" with id: Turnverein Oben is not exists in cloud any more!
2023-09-19 08:02:17.201 - error: botvac.0 (57835) uncaught exception: Cannot read properties of undefined (reading 'getState')
2023-09-19 08:02:17.202 - error: botvac.0 (57835) TypeError: Cannot read properties of undefined (reading 'getState')
at updateRobot (/opt/iobroker/node_modules/iobroker.botvac/main.js:476:11)
at update (/opt/iobroker/node_modules/iobroker.botvac/main.js:467:9)
at Immediate. (/opt/iobroker/node_modules/iobroker.botvac/main.js:456:25)
at process.processImmediate (node:internal/timers:478:21)
2023-09-19 08:02:17.203 - error: botvac.0 (57835) Cannot read properties of undefined (reading 'getState')
2023-09-19 08:02:17.224 - info: botvac.0 (57835) terminating
2023-09-19 08:02:17.225 - warn: botvac.0 (57835) Terminated (UNCAUGHT_EXCEPTION): Without reason
2023-09-19 08:02:17.729 - info: botvac.0 (57835) terminating
2023-09-19 08:02:17.844 - error: host.VM-Slave instance system.adapter.botvac.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2023-09-19 08:02:49.398 - info: botvac.0 (78675) starting. Version 2.0.0-alpha.1 (non-npm: iobroker-community-adapters/ioBroker.botvac#48bc291c4416ec4a5393cecf340ec39162a7138c) in /opt/iobroker/node_modules/iobroker.botvac, node: v18.17.1, js-controller: 5.0.12
2023-09-19 08:02:51.991 - warn: botvac.0 (78675) could not update robot Turnverein Oben
2023-09-19 08:02:54.176 - info: botvac.0 (78675) devices found: 3
2023-09-19 08:02:54.209 - warn: botvac.0 (78675) Device"Turnverein Oben" with id: Turnverein Oben is not exists in cloud any more!
2023-09-19 08:02:54.558 - warn: botvac.0 (78675) Device"Erdgeschoss" with id: Erdgeschoss is not exists in cloud any more!
2023-09-19 08:02:54.559 - warn: botvac.0 (78675) Device"Turnverein Oben" with id: Turnverein Oben is not exists in cloud any more!
2023-09-19 08:02:54.826 - warn: botvac.0 (78675) Device"Erdgeschoss" with id: Erdgeschoss is not exists in cloud any more!
2023-09-19 08:02:54.826 - warn: botvac.0 (78675) Device"Keller" with id: Keller is not exists in cloud any more!
2023-09-19 08:02:54.827 - warn: botvac.0 (78675) Device"Turnverein Oben" with id: Turnverein Oben is not exists in cloud any more!
2023-09-19 08:02:55.079 - error: botvac.0 (78675) uncaught exception: Cannot read properties of undefined (reading 'getState')
2023-09-19 08:02:55.080 - error: botvac.0 (78675) TypeError: Cannot read properties of undefined (reading 'getState')
at updateRobot (/opt/iobroker/node_modules/iobroker.botvac/main.js:476:11)
at update (/opt/iobroker/node_modules/iobroker.botvac/main.js:467:9)
at Immediate. (/opt/iobroker/node_modules/iobroker.botvac/main.js:456:25)
at process.processImmediate (node:internal/timers:478:21)
2023-09-19 08:02:55.081 - error: botvac.0 (78675) Cannot read properties of undefined (reading 'getState')
2023-09-19 08:02:55.109 - info: botvac.0 (78675) terminating
2023-09-19 08:02:55.110 - warn: botvac.0 (78675) Terminated (UNCAUGHT_EXCEPTION): Without reason
2023-09-19 08:02:55.611 - info: botvac.0 (78675) terminating
2023-09-19 08:02:55.735 - error: host.VM-Slave instance system.adapter.botvac.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2023-09-19 08:03:27.330 - info: botvac.0 (78704) starting. Version 2.0.0-alpha.1 (non-npm: iobroker-community-adapters/ioBroker.botvac#48bc291c4416ec4a5393cecf340ec39162a7138c) in /opt/iobroker/node_modules/iobroker.botvac, node: v18.17.1, js-controller: 5.0.12
2023-09-19 08:03:29.998 - warn: botvac.0 (78704) could not update robot Turnverein Oben
2023-09-19 08:03:32.148 - info: botvac.0 (78704) devices found: 3
2023-09-19 08:03:32.179 - warn: botvac.0 (78704) Device"Turnverein Oben" with id: Turnverein Oben is not exists in cloud any more!
2023-09-19 08:03:32.490 - warn: botvac.0 (78704) Device"Erdgeschoss" with id: Erdgeschoss is not exists in cloud any more!
2023-09-19 08:03:32.491 - warn: botvac.0 (78704) Device"Turnverein Oben" with id: Turnverein Oben is not exists in cloud any more!
2023-09-19 08:03:32.800 - warn: botvac.0 (78704) Device"Erdgeschoss" with id: Erdgeschoss is not exists in cloud any more!
2023-09-19 08:03:32.801 - warn: botvac.0 (78704) Device"Keller" with id: Keller is not exists in cloud any more!
2023-09-19 08:03:32.801 - warn: botvac.0 (78704) Device"Turnverein Oben" with id: Turnverein Oben is not exists in cloud any more!
2023-09-19 08:03:33.006 - error: botvac.0 (78704) uncaught exception: Cannot read properties of undefined (reading 'getState')
2023-09-19 08:03:33.007 - error: botvac.0 (78704) TypeError: Cannot read properties of undefined (reading 'getState')
at updateRobot (/opt/iobroker/node_modules/iobroker.botvac/main.js:476:11)
at update (/opt/iobroker/node_modules/iobroker.botvac/main.js:467:9)
at Immediate. (/opt/iobroker/node_modules/iobroker.botvac/main.js:456:25)
at process.processImmediate (node:internal/timers:478:21)
2023-09-19 08:03:33.008 - error: botvac.0 (78704) Cannot read properties of undefined (reading 'getState')
2023-09-19 08:03:33.037 - info: botvac.0 (78704) terminating
2023-09-19 08:03:33.039 - warn: botvac.0 (78704) Terminated (UNCAUGHT_EXCEPTION): Without reason
2023-09-19 08:03:33.540 - info: botvac.0 (78704) terminating
2023-09-19 08:03:33.677 - error: host.VM-Slave instance system.adapter.botvac.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2023-09-19 08:03:33.678 - warn: host.VM-Slave Do not restart adapter system.adapter.botvac.0 because restart loop detected

Update stable version in repo from 1.0.0 to 2.0.1

Think about update stable version to 2.0.1

Version: stable=1.0.0 (2150 days old) => latest=2.0.1 (15 days old)
Installs: stable=467 (89.12%), latest=36 (6.87%), total=524

Click to use developer portal
Click to edit

Note: This is an automatically generated message and not personally authored by bluefox!

mit Botvac D3 reachable Status probleme

Moin,
Ich habe mit Botvac D3 reachable Status probleme. wenn der Botvac nicht erreichbar ist (AUS)
schaltet der reachable Status nicht auf "false" um.

ich hab darauf hin in der Zeile 659 der Datei main.js das " , true " entfernt und jetzt schaltet der reachable Status auf "false" um.

einstellungen-07 02 2018_02_24_33

Think about to fix the issues found by adapter checker

I am an automatic service that looks for possible errors in ioBroker and creates an issue for it. The link below leads directly to the test:

https://adapter-check.iobroker.in/?q=https://raw.githubusercontent.com/iobroker-community-adapters/ioBroker.botvac

I noticed that in the io-package under “restartAdapters” only vis is available. If your widget also runs with vis2, you might want to add vis2 to the list too.

Thanks,
your automatic adapter checker.

js-controller 5 not supported

After installing Node.js v18.16.1, the adapter doesn't start anymore.
Error message below:

host.iobroker 2023-07-18 17:53:43.453 info Rebuild for adapter system.adapter.botvac.0 not successful in 3 tries. Adapter will not be restarted again. Please execute "npm install --production" in adapter directory manually.
host.iobroker 2023-07-18 17:53:43.453 error instance system.adapter.botvac.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
host.iobroker 2023-07-18 17:53:43.453 error Caught by controller[0]: Node.js v18.16.1
host.iobroker 2023-07-18 17:53:43.453 error Caught by controller[0]: }
host.iobroker 2023-07-18 17:53:43.453 error Caught by controller[0]: ]
host.iobroker 2023-07-18 17:53:43.453 error Caught by controller[0]: '/opt/iobroker/node_modules/iobroker.botvac/main.js'
host.iobroker 2023-07-18 17:53:43.453 error Caught by controller[0]: '/opt/iobroker/node_modules/iobroker.botvac/lib/utils.js',
host.iobroker 2023-07-18 17:53:43.453 error Caught by controller[0]: requireStack: [
host.iobroker 2023-07-18 17:53:43.452 error Caught by controller[0]: code: 'MODULE_NOT_FOUND',
host.iobroker 2023-07-18 17:53:43.452 error Caught by controller[0]: at Module.require (node:internal/modules/cjs/loader:1143:19) {
host.iobroker 2023-07-18 17:53:43.452 error Caught by controller[0]: at Module._load (node:internal/modules/cjs/loader:960:12)
host.iobroker 2023-07-18 17:53:43.452 error Caught by controller[0]: at Module.load (node:internal/modules/cjs/loader:1119:32)
host.iobroker 2023-07-18 17:53:43.452 error Caught by controller[0]: at Module._extensions..js (node:internal/modules/cjs/loader:1310:10)
host.iobroker 2023-07-18 17:53:43.452 error Caught by controller[0]: at Module._compile (node:internal/modules/cjs/loader:1256:14)
host.iobroker 2023-07-18 17:53:43.452 error Caught by controller[0]: at Object. (/opt/iobroker/node_modules/iobroker.botvac/lib/utils.js:46:25)
host.iobroker 2023-07-18 17:53:43.452 error Caught by controller[0]: at require (node:internal/modules/cjs/helpers:110:18)
host.iobroker 2023-07-18 17:53:43.452 error Caught by controller[0]: at Module.require (node:internal/modules/cjs/loader:1143:19)
host.iobroker 2023-07-18 17:53:43.452 error Caught by controller[0]: at Module._load (node:internal/modules/cjs/loader:922:27)
host.iobroker 2023-07-18 17:53:43.452 error Caught by controller[0]: at Module._resolveFilename (node:internal/modules/cjs/loader:1077:15)
host.iobroker 2023-07-18 17:53:43.451 error Caught by controller[0]: - /opt/iobroker/node_modules/iobroker.botvac/main.js
host.iobroker 2023-07-18 17:53:43.451 error Caught by controller[0]: - /opt/iobroker/node_modules/iobroker.botvac/lib/utils.js
host.iobroker 2023-07-18 17:53:43.451 error Caught by controller[0]: Require stack:
host.iobroker 2023-07-18 17:53:43.451 error Caught by controller[0]: Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js'
host.iobroker 2023-07-18 17:53:43.451 error Caught by controller[0]: ^
host.iobroker 2023-07-18 17:53:43.451 error Caught by controller[0]: throw err;
host.iobroker 2023-07-18 17:53:43.450 error Caught by controller[0]: node:internal/modules/cjs/loader:1080

Finalize migration to community adapters

  • fix issues reported by aadpter checker
  • add github testing and release
  • update testing to node 16/18/20
  • add dependabot
  • adapt repository links
  • check wether an maintainer is available

Compatibility check to js-controller 4.0

Dear Adapter developer,

with js-controller 4.0 object definitions are now also checked that min/max in only provided for number/mixed objects and that the type of the default value matches to the object type.

If something is not correct this is logged as 'warning' or 'info' log.

Please also make sure to update to the lastest @iobroker/testing dependency 2.5.4 or to accept the PR from Apollon77 for legacy testing!

Please spent some time to verify your adapter by ideally starting with a fresh instance and do some actions and verify the log. If you see a warn or info log there from these checks please adjust the adapter and fix the relevant cases.

For questions please refer to ioBroker/ioBroker.js-controller#1749

Please close the issue after you checked it.

Thank you very much for your support to get the best experience for the growing numbers of ioBroker users!

Please add your adapter to ioBroker.discovery

I am an automatic service from ioBroker that searches adapters and makes suggestions.

I noticed that your adapter is not integrated in the ioBroker.discovery. Using the Discovery adapter, ioBroker can automatically find devices or suggest services to the user for installation. If possible I would live to see your adapter added there.

Some adapters have already been added and you can use them as blueprints. See: https://github.com/ioBroker/ioBroker.discovery You need to fork this project and then create a PR for your adapter to be added.

Basically the plugins can do HTTP calls, UDP discovery, MDNS, UPNP and will iterate over all devices found by IP scan and check local serial ports. If you want you can also add new discovery methods but please try to do that with at least dependencies as possible.

Then create one file under lib/adapters for your adapter to implement the detection and proposal of an instance to the user.

On questions, the other developers will support in the forum or via GitHub issues too.

If no detection is possible, simply close this issue and I won't bother you again. ;-)

Thanks,
your automatic adapter checker.

P.S.: There is a community in Github, which supports the maintenance and further development of adapters. There you will find many experienced developers who are always ready to assist anyone. New developers are always welcome there. For more informations visit: https://github.com/iobroker-community-adapters/info

Please correct npm maintainers configuration.

ioBroker adapter checker for npm access

Access right check for adapter botvac returned the following issue:

Bluefox was not found in the collaborators on NPM!.
Please execute in adapter directory: "npm owner add bluefox iobroker.botvac"

Current maintainers are
pmant [email protected]

Please fix the above error as soon as possible.
All adapters listed at ioBroker repositories must have 'bluefox' added as maintainer.

Future version updates at the repositories will be suspended until this problem is fixed.

Adapter terminates with error since 2020-08-30 23:08

A few days ago the botvac adapter stopped working.

It gives me the following error messages:
2020-08-30 23:08:28.123 - error: botvac.0 (4535) uncaught exception: Cannot read property 'isCharging' of undefined 2020-08-30 23:08:28.126 - error: botvac.0 (4535) TypeError: Cannot read property 'isCharging' of undefined at Robot. (/opt/iobroker/node_modules/node-botvac/lib/robot.js:40:50) at /opt/iobroker/node_modules/node-botvac/lib/robot.js:320:17 at Request._callback (/opt/iobroker/node_modules/node-botvac/lib/api.js:42:45) at Request.self.callback (/opt/iobroker/node_modules/request/request.js:185:22) at Request.emit (events.js:198:13) at Request. (/opt/iobroker/node_modules/request/request.js:1161:10) at Request.emit (events.js:198:13) at IncomingMessage. (/opt/iobroker/node_modules/request/request.js:1083:12) at Object.onceWrapper (events.js:286:20) at IncomingMessage.emit (events.js:203:15) 2020-08-30 23:08:28.135 - info: botvac.0 (4535) terminating 2020-08-30 23:08:28.138 - info: botvac.0 (4535) Terminated (NO_ERROR): Without reason 2020-08-30 23:09:01.328 - info: botvac.0 (23622) starting. Version 1.0.0 in /opt/iobroker/node_modules/iobroker.botvac, node: v10.20.1, js-controller: 3.0.20 2020-08-30 23:09:03.793 - info: botvac.0 (23622) devices found: 3 2020-08-30 23:09:08.050 - error: botvac.0 (23622) uncaught exception: Cannot read property 'isCharging' of undefined 2020-08-30 23:09:08.052 - error: botvac.0 (23622) TypeError: Cannot read property 'isCharging' of undefined at Robot. (/opt/iobroker/node_modules/node-botvac/lib/robot.js:40:50) at /opt/iobroker/node_modules/node-botvac/lib/robot.js:320:17 at Request._callback (/opt/iobroker/node_modules/node-botvac/lib/api.js:42:45) at Request.self.callback (/opt/iobroker/node_modules/request/request.js:185:22) at Request.emit (events.js:198:13) at Request. (/opt/iobroker/node_modules/request/request.js:1161:10) at Request.emit (events.js:198:13) at IncomingMessage. (/opt/iobroker/node_modules/request/request.js:1083:12) at Object.onceWrapper (events.js:286:20) at IncomingMessage.emit (events.js:203:15) 2020-08-30 23:09:08.063 - info: botvac.0 (23622) terminating

They were preceded by sporadic warnings in this style:

2020-08-30 18:57:36.403 - warn: botvac.0 (4535) could not update robot Neato

Unfortunately the adapter is now unusable.

meaning of 'state' value

Hi,

I have been using this adapter for a while and love it. It allows one to control botvac via alexa, mqtt, scripts... it is awesome!

Right now I am trying to integrate the status output in a graphical dashboard... can anybody please tell me what the state values mean? I assume that 1 means charging at station, because that's what it shows at the moment (and it is fully charged and at its station).

However, does anybody have a full overview of what other digits there are and what those mean? Thanks in advance for your help 👍

Neato Botvac Connected D3 Staubsauger Roboter

Hallo!

Ich bin gerade auf diesen iobroker Adapter gestoßen.
Ich denke das ist das was ich suche!

Funktioniert dieser auch mit dem Neato Botvac Connected D3 Staubsauger Roboter?

Hat jemand bereits Erfahrungen gemacht?
Ich wäre für jedes Feedback sehr dankbar bevor ich über 300EUR aus dem Fenster werfe.

Danke euch :)
LG,
Dark!

Think about to fix the issues found by adapter checker

I am an automatic service that looks for possible errors in ioBroker and creates an issue for it. The link below leads directly to the test:

https://adapter-check.iobroker.in/?q=https://raw.githubusercontent.com/iobroker-community-adapters/ioBroker.botvac

  • [E114] No adapter are allowed in the repo without admin support (set "common.noConfig = true" and "common.adminUI.config = none" if adapter has no configuration)

I have also found warnings that may be fixed if possible.

  • [W171] "common.title" is deprecated in io-package.json
  • [W113] Adapter should support compact mode
  • [W156] Adapter should support admin 5 UI (jsonConfig) if you do not use a React based UI

I noticed that in the io-package under “restartAdapters” only vis is available. If your widget also runs with vis-2, you might want to add “vis-2” to the list too.

Thanks,
your automatic adapter checker.

Compatibility check to js-controller 3.3 and Admin5 React UI

Dear Adapter developer,

with js-controller 3.2 and js-controller 3.3 some additional checks were added to make sure that created objects match to the specifications and also written state values match to the object definition.

If something is not correct this is logged as 'warning' or 'info' log.

Please take the time to verify your adapter by ideally starting with a fresh instance and do some actions and verify the log. If you see a warn log there from these checks please adjust the adapter and fix the relevant cases.

For questions please refer to ioBroker/ioBroker.js-controller#1301

Additionally we are preparing Admin 5 which will have a completely rewritten UI. Please install Admin 5, activate that new UI and verify that the configuration of you adapter works as expected also there.

More informations on Admin 5 can be found in Forum https://forum.iobroker.net/topic/44282/test-adapter-admin-5-0-x-alpha-der-neuen-ui

Please close the issue after you checked it.

Thank you very much for your support!

second Neato Botvac does not show up properly

Hi!
I have 2 Neatos, but only one shows up properly in ioBroker.
The other one does not have the subfolders and all the triggers. There is only an empty state with the name of the robot.
Any idea?
Thomas

Update stable version in repo from 2.0.2 to 2.2.0

Think about update stable version to 2.2.0

Version: stable=2.0.2 (121 days old) => latest=2.2.0 (18 days old)
Installs: stable=220 (49.33%), latest=23 (5.16%), total=446

Click to use developer portal
Click to edit

Do not close this issue manually as a new issue will be created if condition for update still exists.

Please drop a comment if any reason exists which blocks updating to version 2.2.0 at this time.

Note: This is an automatically generated message and not personally authored by bluefox!
@mcm1957 for evidence

Cannot read property 'isCharging' of undefined

Restart loop detected:

Since last week i get this error, the Adapther did not start anymore, and idea ?

botvac.0 2021-12-25 15:01:15.246 warn Terminated (UNCAUGHT_EXCEPTION): Without reason
botvac.0 2021-12-25 15:01:15.246 info terminating
botvac.0 2021-12-25 15:01:15.243 error Cannot read property 'isCharging' of undefined
botvac.0 2021-12-25 15:01:15.243 error TypeError: Cannot read property 'isCharging' of undefined at Robot. (/opt/iobroker/node_modules/node-botvac/lib/robot.js:40:50) at /opt/iobroker/node_modules/node-botvac/lib/robot.js:320:17 at Request._callback (/opt/iobroker/node_modules/node-botvac/lib/api.js:42:45) at Request.self.callback (/opt/iobroker/node_modules/request/request.js:185:22) at Request.emit (events.js:314:20) at Request. (/opt/iobroker/node_modules/request/request.js:1154:10) at Request.emit (events.js:314:20) at IncomingMessage. (/opt/iobroker/node_modules/request/request.js:1076:12) at Object.onceWrapper (events.js:420:28) at IncomingMessage.emit (events.js:326:22)
botvac.0 2021-12-25 15:01:15.242 error uncaught exception: Cannot read property 'isCharging' of undefined

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.