NEWS
Neato Botvac adapter - further development
-
Hi
Currently I'm trying to make some updates for the adapter.
First step - it is editable schedule for the robot.
Currently it available not for all robots, but, if somebody is ready to be a tester - I can continue.
My D5 has a limited schedule functionality - only to set the time and day.
For modes and boundaries - it's more or less ready, but I can't test...Next steps - it will be a maps and other things ...
My PR with schedule is accepted by maintainer of the adapter ...So - if you have such devices and ready to test - you are welcomed.
-
@petervoronov Hi, I have a D7 and would like to help. What should I do?
-
@masgo Hi
Excuse me for long silent.You can try to install dev version of adapter
cd /opt/iobroker/ iobroker url https://github.com/PeterVoronov/ioBroker.botvac/tree/dev-1.0.4-1
And check, what is new object's is created in channel schedule under the your robot device.
Please share the result.
Additionally you can try to edit startTime and mode.
I'm not sure about BoundaryId's now.To revert it back:
cd /opt/iobroker/ iobroker upgrade iobroker.botvac@1.0.0
And agree on downgrade.
-
Hey Peter,
i tried to install your developer version of the botvac because in Version 1.0.0. i have the problembotvac.0 2021-05-23 06:54:16.262 warn (7527) could not update robot Nono botvac.0 2021-05-23 06:54:15.832 info (7527) devices found: 1
Next step i´ve installed the developer version 1.0.4-1 from above and now i have another problem.
botvac.0 2021-05-23 06:54:54.876 warn (31575) Device"Nono" with id: Nono is not exists in cloud any more! botvac.0 2021-05-23 06:54:54.804 warn (31575) can not create appropriate objects! Err = "something wrong with devices: {}"
I tried also to delete the adapter in ioBroker and i reinstall the Botvac D5 conneceted also in the Neato app. Both didn´t help.
Can you help me how can i fix this problem, at least in one of the versions?
-
Пользователь @bourton88 написал в Neato Botvac adapter - further development:
Hey Peter,
i tried to install your developer version of the botvac because in Version 1.0.0. i have the problembotvac.0 2021-05-23 06:54:16.262 warn (7527) could not update robot Nono botvac.0 2021-05-23 06:54:15.832 info (7527) devices found: 1
Next step i´ve installed the developer version 1.0.4-1 from above and now i have another problem.
botvac.0 2021-05-23 06:54:54.876 warn (31575) Device"Nono" with id: Nono is not exists in cloud any more! botvac.0 2021-05-23 06:54:54.804 warn (31575) can not create appropriate objects! Err = "something wrong with devices: {}"
I tried also to delete the adapter in ioBroker and i reinstall the Botvac D5 conneceted also in the Neato app. Both didn´t help.
Can you help me how can i fix this problem, at least in one of the versions?
Hi.
It's strange, but I sometime faced with similar behavior.
Please try stop the adapter, then do not use mobile app for some period of time, and after that try to start the adapter.
If it is not help - will add some debugs ... may be it will help -
@petervoronov
Ohh thats cool. Thanks!!I stopped the Adapter just for an hour and it works
I have another assumption because unfortunately i changed two things. I stopped the adapter AND i recognized that the clock-time from the running ioBroker instance was not set to the correct time. So i changed that as well.
Maybe there is an Sync-Problem with the Neato-Server when the time doesn´t fit?
-
Пользователь @bourton88 написал в Neato Botvac adapter - further development:
@petervoronov
Ohh thats cool. Thanks!!I stopped the Adapter just for an hour and it works
I have another assumption because unfortunately i changed two things. I stopped the adapter AND i recognized that the clock-time from the running ioBroker instance was not set to the correct time. So i changed that as well.
Maybe there is an Sync-Problem with the Neato-Server when the time doesn´t fit?
It the code for connection I not saw the time-sync recs or functions...
But by my understanding, it is some limitation on the cloud for the connections in the same time from one account... -
@petervoronov
After a long time a had the same issue as before (see post from 23. Mai 2021, 10:11)This time i checked your recommendation first but it doesn´t help. Then i checked the clock-time at my Server again and it doesn´t fit with the current time. So i changed the Server time back to the current time and it works well.
There must be a dependency to the time-sync.
-
-
@thomas-braun
My Server is a QNAP-NAS. So i just correct the time in the settings. -
@PeterVoronov
Hey Peter,
login is again (?) not working. I found this thread and installed dev-1.0.4-1, but log says "botvac.1 2023-07-15 11:51:19.359 warn login failed"
As such, no objects have been discovered/installed.I recognize that there are several neato-plugins for several utilities (Smarthome), which seemed to have the same problem and needed some update work. So I suppose Neato changed their login procedure slightly.
Could you provide another update please? I have absolutely no competence in JS or PHP or any programming language...
Many thanks,
Daniel -
Hi @danielmayer .
Unfortunately my botvac broke a few years ago ... Currently I can't check the plugin.
At least - it can't find any robots, as it not logged in the Neato system.
That's why currently I have no possibility to help ....But I have no any issues with login of plugin...
Only "no robots" message ... -
@petervoronov
Hi Peter,the plugin was working fine for quite some time, but after I updated to the latest Node.js 18... it stopped working.
Reinstalling doesn't work either, I'm getting following error:
Any idea how to get it working again? It seems the adapter is no longer compatible...
Thanks,
Thomas*host.iobroker 2023-08-31 08:54:49.650 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-08-31 08:54:49.650 error instance system.adapter.botvac.0 terminated with code 1 (JS_CONTROLLER_STOPPED) host.iobroker 2023-08-31 08:54:49.650 error Caught by controller[0]: Node.js v18.17.1 host.iobroker 2023-08-31 08:54:49.650 error Caught by controller[0]: } host.iobroker 2023-08-31 08:54:49.650 error Caught by controller[0]: ] host.iobroker 2023-08-31 08:54:49.650 error Caught by controller[0]: '/opt/iobroker/node_modules/iobroker.botvac/main.js' host.iobroker 2023-08-31 08:54:49.650 error Caught by controller[0]: '/opt/iobroker/node_modules/iobroker.botvac/lib/utils.js', host.iobroker 2023-08-31 08:54:49.650 error Caught by controller[0]: requireStack: [ host.iobroker 2023-08-31 08:54:49.649 error Caught by controller[0]: code: 'MODULE_NOT_FOUND', host.iobroker 2023-08-31 08:54:49.649 error Caught by controller[0]: at Module.require (node:internal/modules/cjs/loader:1143:19) { host.iobroker 2023-08-31 08:54:49.649 error Caught by controller[0]: at Module._load (node:internal/modules/cjs/loader:960:12) host.iobroker 2023-08-31 08:54:49.649 error Caught by controller[0]: at Module.load (node:internal/modules/cjs/loader:1119:32) host.iobroker 2023-08-31 08:54:49.649 error Caught by controller[0]: at Module._extensions..js (node:internal/modules/cjs/loader:1310:10) host.iobroker 2023-08-31 08:54:49.649 error Caught by controller[0]: at Module._compile (node:internal/modules/cjs/loader:1256:14) host.iobroker 2023-08-31 08:54:49.649 error Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.botvac/lib/utils.js:46:25) host.iobroker 2023-08-31 08:54:49.649 error Caught by controller[0]: at require (node:internal/modules/cjs/helpers:121:18) host.iobroker 2023-08-31 08:54:49.649 error Caught by controller[0]: at Module.require (node:internal/modules/cjs/loader:1143:19) host.iobroker 2023-08-31 08:54:49.648 error Caught by controller[0]: at Module._load (node:internal/modules/cjs/loader:922:27) host.iobroker 2023-08-31 08:54:49.648 error Caught by controller[0]: at Module._resolveFilename (node:internal/modules/cjs/loader:1077:15) host.iobroker 2023-08-31 08:54:49.648 error Caught by controller[0]: - /opt/iobroker/node_modules/iobroker.botvac/main.js host.iobroker 2023-08-31 08:54:49.648 error Caught by controller[0]: - /opt/iobroker/node_modules/iobroker.botvac/lib/utils.js host.iobroker 2023-08-31 08:54:49.648 error Caught by controller[0]: Require stack: host.iobroker 2023-08-31 08:54:49.648 error Caught by controller[0]: Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js' host.iobroker 2023-08-31 08:54:49.648 error Caught by controller[0]: ^ host.iobroker 2023-08-31 08:54:49.648 error Caught by controller[0]: throw err; host.iobroker 2023-08-31 08:54:49.647 error Caught by controller[0]: node:internal/modules/cjs/loader:1080 host.iobroker 2023-08-31 08:54:49.444 info instance system.adapter.botvac.0 started with pid 22369 host.iobroker 2023-08-31 08:54:49.370 info iobroker npm-rebuild: exit 0 host.iobroker 2023-08-31 08:54:48.355 info iobroker npm-rebuild: rebuilt dependencies successfullyRebuilding native modules done*
-
@csp
I have the same version of node - 18.17.1.
As I have no more botvac devices, I can only check the starting adapter and login to the api.
For me it's working. But when I made migration to node 18th, I wiped the node_modules directory fully.
I will not recommend to follow my way, as it required some additional understanding and manual work.
You can try at least to follow the recommendations from error log - execute "npm install --production" in adapter directory manually. -
@petervoronov I tried that already. It is a bit difficult, as I'm running it on Synology server in docker.
It did run through though, but not worked at the end.
Any idea on how to wipe the adapter fully? (Not all of course, just this one)
Happy to follow instructions.
Thomas -
@csp I just did it again, no success.
So I deinstalled the adapter and manually deleted the module folder.
Reboot ioBroker.
Reinstall bot vac adapter -> OK
Putting credentials in and restart... -> same issue. ioBroker tries 3 times to rebuild and fails...host.iobroker 2023-09-01 09:37:08.038 info iobroker npm-rebuild: Rebuilding native modules ... host.iobroker 2023-09-01 09:37:06.088 info iobroker rebuild host.iobroker 2023-09-01 09:37:06.088 warn adapter "botvac" seems to be installed for a different version of Node.js. Trying to rebuild it... 1 attempt host.iobroker 2023-09-01 09:37:06.087 info system.adapter.botvac.0 will be rebuilt host.iobroker 2023-09-01 09:37:06.087 info Adapter system.adapter.botvac.0 needs rebuild and will be restarted afterwards. host.iobroker 2023-09-01 09:37:06.086 error instance system.adapter.botvac.0 terminated with code 1 (JS_CONTROLLER_STOPPED) host.iobroker 2023-09-01 09:37:06.086 error Caught by controller[0]: Node.js v18.17.1 host.iobroker 2023-09-01 09:37:06.086 error Caught by controller[0]: } host.iobroker 2023-09-01 09:37:06.086 error Caught by controller[0]: ] host.iobroker 2023-09-01 09:37:06.086 error Caught by controller[0]: '/opt/iobroker/node_modules/iobroker.botvac/main.js' host.iobroker 2023-09-01 09:37:06.086 error Caught by controller[0]: '/opt/iobroker/node_modules/iobroker.botvac/lib/utils.js', host.iobroker 2023-09-01 09:37:06.086 error Caught by controller[0]: requireStack: [ host.iobroker 2023-09-01 09:37:06.085 error Caught by controller[0]: code: 'MODULE_NOT_FOUND', host.iobroker 2023-09-01 09:37:06.085 error Caught by controller[0]: at Module.require (node:internal/modules/cjs/loader:1143:19) { host.iobroker 2023-09-01 09:37:06.085 error Caught by controller[0]: at Module._load (node:internal/modules/cjs/loader:960:12) host.iobroker 2023-09-01 09:37:06.085 error Caught by controller[0]: at Module.load (node:internal/modules/cjs/loader:1119:32) host.iobroker 2023-09-01 09:37:06.085 error Caught by controller[0]: at Module._extensions..js (node:internal/modules/cjs/loader:1310:10) host.iobroker 2023-09-01 09:37:06.085 error Caught by controller[0]: at Module._compile (node:internal/modules/cjs/loader:1256:14) host.iobroker 2023-09-01 09:37:06.085 error Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.botvac/lib/utils.js:46:25) host.iobroker 2023-09-01 09:37:06.079 error Caught by controller[0]: at require (node:internal/modules/cjs/helpers:121:18) host.iobroker 2023-09-01 09:37:06.079 error Caught by controller[0]: at Module.require (node:internal/modules/cjs/loader:1143:19) host.iobroker 2023-09-01 09:37:06.079 error Caught by controller[0]: at Module._load (node:internal/modules/cjs/loader:922:27) host.iobroker 2023-09-01 09:37:06.079 error Caught by controller[0]: at Module._resolveFilename (node:internal/modules/cjs/loader:1077:15) host.iobroker 2023-09-01 09:37:06.079 error Caught by controller[0]: - /opt/iobroker/node_modules/iobroker.botvac/main.js host.iobroker 2023-09-01 09:37:06.079 error Caught by controller[0]: - /opt/iobroker/node_modules/iobroker.botvac/lib/utils.js host.iobroker 2023-09-01 09:37:06.079 error Caught by controller[0]: Require stack: host.iobroker 2023-09-01 09:37:06.079 error Caught by controller[0]: Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js' host.iobroker 2023-09-01 09:37:06.079 error Caught by controller[0]: ^ host.iobroker 2023-09-01 09:37:06.078 error Caught by controller[0]: throw err; host.iobroker 2023-09-01 09:37:06.078 error Caught by controller[0]: node:internal/modules/cjs/loader:1080 host.iobroker 2023-09-01 09:37:02.812 info instance system.adapter.botvac.0 started with pid 912 host.iobroker 2023-09-01 09:36:57.818 info iobroker exit 0 host.iobroker 2023-09-01 09:36:56.009 info iobroker host.iobroker object system.adapter.botvac.0 created host.iobroker 2023-09-01 09:36:54.323 info iobroker host.iobroker object system.adapter.botvac.0.logLevel created host.iobroker 2023-09-01 09:36:53.946 info iobroker host.iobroker object system.adapter.botvac.0.sigKill created host.iobroker 2023-09-01 09:36:53.779 info iobroker host.iobroker object system.adapter.botvac.0.eventLoopLag created host.iobroker 2023-09-01 09:36:53.594 info iobroker host.iobroker object system.adapter.botvac.0.outputCount created host.iobroker 2023-09-01 09:36:53.420 info iobroker host.iobroker object system.adapter.botvac.0.inputCount created host.iobroker 2023-09-01 09:36:53.287 info iobroker host.iobroker object system.adapter.botvac.0.uptime created host.iobroker 2023-09-01 09:36:53.061 info iobroker host.iobroker object system.adapter.botvac.0.memRss created host.iobroker 2023-09-01 09:36:52.850 info iobroker host.iobroker object system.adapter.botvac.0.memHeapTotal created host.iobroker 2023-09-01 09:36:52.603 info iobroker host.iobroker object system.adapter.botvac.0.memHeapUsed created host.iobroker 2023-09-01 09:36:51.671 info iobroker host.iobroker object system.adapter.botvac.0.cputime created host.iobroker 2023-09-01 09:36:48.434 info iobroker host.iobroker object system.adapter.botvac.0.cpu created host.iobroker 2023-09-01 09:36:48.027 info iobroker host.iobroker object system.adapter.botvac.0.compactMode created host.iobroker 2023-09-01 09:36:47.669 info iobroker host.iobroker object system.adapter.botvac.0.connected created host.iobroker 2023-09-01 09:36:47.477 info iobroker host.iobroker object system.adapter.botvac.0.alive created host.iobroker 2023-09-01 09:36:47.342 info iobroker host.iobroker create instance botvac host.iobroker 2023-09-01 09:36:46.191 info iobroker host.iobroker object system.adapter.botvac created/updated
-
I just did a crosscheck on my setup.
The adapter installs without issues here.
Check your setup, especially the nodejs install.iob diag
may be helpfull.
-
@thomas-braun Installation works fine on my end as well. But as soon as I want to log in, it doesn't work.
What do I need to do exactly? Can you help? -
@csp
No, I don't own that device, I just checked the adapter installation. -
@thomas-braun but maybe how I can check nodejs with iob diag?