NEWS
js-controller Lucy (v7.0.0) Alpha Test
-
Produktiv läuft nicht , zurück mit Proxmox Backup.
tobias@iobroker:/opt/iobroker$ npm i iobroker.js-controller@next --omit=dev added 7 packages, and changed 17 packages in 11s 307 packages are looking for funding run `npm fund` for details tobias@iobroker:/opt/iobroker$ iob start tobias@iobroker:/opt/iobroker$ iob logs --watch2024-09-26 17:13:52.080 - error: admin.0 (578389) 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(). 2024-09-26 17:13:52.080 - error: admin.0 (578389) unhandled promise rejection: callback is not a function 2024-09-26 17:13:52.081 - error: admin.0 (578389) TypeError: callback is not a function at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-09-26 17:13:52.082 - error: admin.0 (578389) callback is not a function 2024-09-26 17:13:52.588 - warn: admin.0 (578389) Terminated (UNCAUGHT_EXCEPTION): Without reason 2024-09-26 17:13:53.115 - error: host.iobroker Caught by controller[0]: 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(). The promise rejected with the reason: 2024-09-26 17:13:53.115 - error: host.iobroker Caught by controller[1]: TypeError: callback is not a function 2024-09-26 17:13:53.115 - error: host.iobroker Caught by controller[1]: at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-09-26 17:13:53.115 - error: host.iobroker instance system.adapter.admin.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2024-09-26 17:13:53.116 - info: host.iobroker Restart adapter system.adapter.admin.0 because enabled 2024-09-26 17:13:55.354 - info: host.iobroker instance system.adapter.email.0 in version "1.3.1" started with pid 578404 2024-09-26 17:13:55.856 - error: email.0 (578404) 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(). 2024-09-26 17:13:55.857 - error: email.0 (578404) unhandled promise rejection: callback is not a function 2024-09-26 17:13:55.858 - error: email.0 (578404) TypeError: callback is not a function at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:454:9) 2024-09-26 17:13:55.859 - error: email.0 (578404) callback is not a function 2024-09-26 17:13:56.366 - warn: email.0 (578404) Terminated (UNCAUGHT_EXCEPTION): Without reason 2024-09-26 17:13:56.890 - error: host.iobroker Caught by controller[0]: 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(). The promise rejected with the reason: 2024-09-26 17:13:56.891 - error: host.iobroker Caught by controller[1]: TypeError: callback is not a function 2024-09-26 17:13:56.891 - error: host.iobroker Caught by controller[1]: at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-09-26 17:13:56.891 - error: host.iobroker Caught by controller[1]: at runNextTicks (node:internal/process/task_queues:60:5) 2024-09-26 17:13:56.891 - error: host.iobroker Caught by controller[1]: at processImmediate (node:internal/timers:454:9) 2024-09-26 17:13:56.891 - error: host.iobroker instance system.adapter.email.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2024-09-26 17:13:56.891 - info: host.iobroker Restart adapter system.adapter.email.0 because enabled 2024-09-26 17:13:59.363 - info: host.iobroker instance system.adapter.influxdb.0 in version "4.0.2" started with pid 578419 2024-09-26 17:13:59.955 - error: influxdb.0 (578419) Unhandled promise rejection. This error originated either by throwing inside of an async function without a ca tch block, or by rejecting a promise which was not handled with .catch(). 2024-09-26 17:13:59.955 - error: influxdb.0 (578419) unhandled promise rejection: callback is not a function 2024-09-26 17:13:59.956 - error: influxdb.0 (578419) TypeError: callback is not a function at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-09-26 17:13:59.957 - error: influxdb.0 (578419) callback is not a function 2024-09-26 17:14:00.007 - info: influxdb.0 (578419) starting. Version 4.0.2 in /opt/iobroker/node_modules/iobroker.influxdb, node: v20.17.0, js-controller: 7.0.0-a lpha.0-20240926-91f9b082f 2024-09-26 17:14:00.964 - warn: influxdb.0 (578419) Terminated (UNCAUGHT_EXCEPTION): Without reason 2024-09-26 17:14:01.488 - error: host.iobroker Caught by controller[0]: 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(). The promise rejected with the reason: 2024-09-26 17:14:01.488 - error: host.iobroker Caught by controller[1]: TypeError: callback is not a function 2024-09-26 17:14:01.489 - error: host.iobroker Caught by controller[1]: at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-09-26 17:14:01.489 - error: host.iobroker instance system.adapter.influxdb.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2024-09-26 17:14:01.489 - info: host.iobroker Restart adapter system.adapter.influxdb.0 because enabled 2024-09-26 17:14:03.363 - info: host.iobroker instance system.adapter.javascript.0 in version "8.8.3" started with pid 578434 2024-09-26 17:14:07.387 - info: host.iobroker instance system.adapter.pushover.0 in version "4.1.0" started with pid 578450 2024-09-26 17:14:07.931 - error: pushover.0 (578450) Unhandled promise rejection. This error originated either by throwing inside of an async function without a ca tch block, or by rejecting a promise which was not handled with .catch(). 2024-09-26 17:14:07.932 - error: pushover.0 (578450) unhandled promise rejection: callback is not a function 2024-09-26 17:14:07.933 - error: pushover.0 (578450) TypeError: callback is not a function at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:454:9) 2024-09-26 17:14:07.933 - error: pushover.0 (578450) callback is not a function 2024-09-26 17:14:08.442 - warn: pushover.0 (578450) Terminated (UNCAUGHT_EXCEPTION): Without reason 2024-09-26 17:14:08.964 - error: host.iobroker Caught by controller[0]: 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(). The promise rejected with the reason: 2024-09-26 17:14:08.965 - error: host.iobroker Caught by controller[1]: TypeError: callback is not a function 2024-09-26 17:14:08.965 - error: host.iobroker Caught by controller[1]: at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-09-26 17:14:08.965 - error: host.iobroker Caught by controller[1]: at runNextTicks (node:internal/process/task_queues:60:5) 2024-09-26 17:14:08.965 - error: host.iobroker Caught by controller[1]: at processImmediate (node:internal/timers:454:9) 2024-09-26 17:14:08.965 - error: host.iobroker instance system.adapter.pushover.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2024-09-26 17:14:08.965 - info: host.iobroker Restart adapter system.adapter.pushover.0 because enabled 2024-09-26 17:14:11.361 - info: host.iobroker instance system.adapter.pushover.1 in version "4.1.0" started with pid 578465 2024-09-26 17:14:11.852 - error: pushover.1 (578465) Unhandled promise rejection. This error originated either by throwing inside of an async function without a ca tch block, or by rejecting a promise which was not handled with .catch(). 2024-09-26 17:14:11.852 - error: pushover.1 (578465) unhandled promise rejection: callback is not a function 2024-09-26 17:14:11.854 - error: pushover.1 (578465) TypeError: callback is not a function at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:454:9) 2024-09-26 17:14:11.854 - error: pushover.1 (578465) callback is not a function 2024-09-26 17:14:12.361 - warn: pushover.1 (578465) Terminated (UNCAUGHT_EXCEPTION): Without reason 2024-09-26 17:14:12.884 - error: host.iobroker Caught by controller[0]: 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(). The promise rejected with the reason: 2024-09-26 17:14:12.884 - error: host.iobroker Caught by controller[1]: TypeError: callback is not a function 2024-09-26 17:14:12.884 - error: host.iobroker Caught by controller[1]: at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-09-26 17:14:12.885 - error: host.iobroker Caught by controller[1]: at runNextTicks (node:internal/process/task_queues:60:5) 2024-09-26 17:14:12.885 - error: host.iobroker Caught by controller[1]: at processImmediate (node:internal/timers:454:9) 2024-09-26 17:14:12.885 - error: host.iobroker instance system.adapter.pushover.1 terminated with code 6 (UNCAUGHT_EXCEPTION) 2024-09-26 17:14:12.885 - info: host.iobroker Restart adapter system.adapter.pushover.1 because enabled 2024-09-26 17:14:15.366 - info: host.iobroker instance system.adapter.pushover.2 in version "4.1.0" started with pid 578480 2024-09-26 17:14:15.865 - error: pushover.2 (578480) Unhandled promise rejection. This error originated either by throwing inside of an async function without a ca tch block, or by rejecting a promise which was not handled with .catch(). 2024-09-26 17:14:15.865 - error: pushover.2 (578480) unhandled promise rejection: callback is not a function 2024-09-26 17:14:15.867 - error: pushover.2 (578480) TypeError: callback is not a function at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:454:9) 2024-09-26 17:14:15.867 - error: pushover.2 (578480) callback is not a function 2024-09-26 17:14:15.921 - info: pushover.2 (578480) starting. Version 4.1.0 in /opt/iobroker/node_modules/iobroker.pushover, node: v20.17.0, js-controller: 7.0.0-a lpha.0-20240926-91f9b082f 2024-09-26 17:14:16.374 - info: pushover.2 (578480) terminating 2024-09-26 17:14:16.375 - warn: pushover.2 (578480) Terminated (UNCAUGHT_EXCEPTION): Without reason 2024-09-26 17:14:16.897 - error: host.iobroker Caught by controller[0]: 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(). The promise rejected with the reason: 2024-09-26 17:14:16.898 - error: host.iobroker Caught by controller[1]: TypeError: callback is not a function 2024-09-26 17:14:16.898 - error: host.iobroker Caught by controller[1]: at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-09-26 17:14:16.898 - error: host.iobroker Caught by controller[1]: at runNextTicks (node:internal/process/task_queues:60:5) 2024-09-26 17:14:16.898 - error: host.iobroker Caught by controller[1]: at processImmediate (node:internal/timers:454:9) 2024-09-26 17:14:16.898 - error: host.iobroker instance system.adapter.pushover.2 terminated with code 6 (UNCAUGHT_EXCEPTION) 2024-09-26 17:14:16.898 - info: host.iobroker Restart adapter system.adapter.pushover.2 because enabled 2024-09-26 17:14:19.362 - info: host.iobroker instance system.adapter.telegram.0 in version "3.9.0" started with pid 578495 2024-09-26 17:14:19.988 - error: telegram.0 (578495) Unhandled promise rejection. This error originated either by throwing inside of an async function without a ca tch block, or by rejecting a promise which was not handled with .catch(). 2024-09-26 17:14:19.989 - error: telegram.0 (578495) unhandled promise rejection: callback is not a function 2024-09-26 17:14:19.990 - error: telegram.0 (578495) TypeError: callback is not a function at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:454:9) 2024-09-26 17:14:19.990 - error: telegram.0 (578495) callback is not a function 2024-09-26 17:14:20.498 - warn: telegram.0 (578495) Terminated (UNCAUGHT_EXCEPTION): Without reason 2024-09-26 17:14:21.021 - error: host.iobroker Caught by controller[0]: 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(). The promise rejected with the reason: 2024-09-26 17:14:21.022 - error: host.iobroker Caught by controller[1]: TypeError: callback is not a function 2024-09-26 17:14:21.022 - error: host.iobroker Caught by controller[1]: at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-09-26 17:14:21.022 - error: host.iobroker Caught by controller[1]: at runNextTicks (node:internal/process/task_queues:60:5) 2024-09-26 17:14:21.022 - error: host.iobroker Caught by controller[1]: at processImmediate (node:internal/timers:454:9) 2024-09-26 17:14:21.022 - error: host.iobroker instance system.adapter.telegram.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2024-09-26 17:14:21.022 - info: host.iobroker Restart adapter system.adapter.telegram.0 because enabled 2024-09-26 17:14:22.132 - info: host.iobroker instance system.adapter.telegram.0 in version "3.9.0" started with pid 578510 2024-09-26 17:14:22.824 - error: telegram.0 (578510) Unhandled promise rejection. This error originated either by throwing inside of an async function without a ca tch block, or by rejecting a promise which was not handled with .catch(). 2024-09-26 17:14:22.825 - error: telegram.0 (578510) unhandled promise rejection: callback is not a function 2024-09-26 17:14:22.826 - error: telegram.0 (578510) TypeError: callback is not a function at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-09-26 17:14:22.826 - error: telegram.0 (578510) callback is not a function 2024-09-26 17:14:23.226 - info: host.iobroker instance system.adapter.admin.0 in version "7.1.5" started with pid 578540 2024-09-26 17:14:23.334 - warn: telegram.0 (578510) Terminated (UNCAUGHT_EXCEPTION): Without reason 2024-09-26 17:14:23.356 - info: host.iobroker instance system.adapter.telegram.1 in version "3.9.0" started with pid 578547 2024-09-26 17:14:23.875 - error: host.iobroker Caught by controller[0]: 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(). The promise rejected with the reason: 2024-09-26 17:14:23.876 - error: host.iobroker Caught by controller[1]: TypeError: callback is not a function 2024-09-26 17:14:23.876 - error: host.iobroker Caught by controller[1]: at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-09-26 17:14:23.876 - error: host.iobroker instance system.adapter.telegram.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2024-09-26 17:14:23.876 - info: host.iobroker Restart adapter system.adapter.telegram.0 because enabled 2024-09-26 17:14:24.064 - error: admin.0 (578540) 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(). 2024-09-26 17:14:24.065 - error: admin.0 (578540) unhandled promise rejection: callback is not a function 2024-09-26 17:14:24.066 - error: admin.0 (578540) TypeError: callback is not a function at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-09-26 17:14:24.066 - error: admin.0 (578540) callback is not a function 2024-09-26 17:14:24.119 - error: telegram.1 (578547) Unhandled promise rejection. This error originated either by throwing inside of an async function without a ca tch block, or by rejecting a promise which was not handled with .catch(). 2024-09-26 17:14:24.120 - error: telegram.1 (578547) unhandled promise rejection: callback is not a function 2024-09-26 17:14:24.121 - error: telegram.1 (578547) TypeError: callback is not a function at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-09-26 17:14:24.121 - error: telegram.1 (578547) callback is not a function 2024-09-26 17:14:24.573 - warn: admin.0 (578540) Terminated (UNCAUGHT_EXCEPTION): Without reason 2024-09-26 17:14:24.628 - warn: telegram.1 (578547) Terminated (UNCAUGHT_EXCEPTION): Without reason 2024-09-26 17:14:24.988 - info: host.iobroker instance system.adapter.telegram.0 in version "3.9.0" started with pid 578600 2024-09-26 17:14:25.098 - error: host.iobroker Caught by controller[0]: 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(). The promise rejected with the reason: 2024-09-26 17:14:25.098 - error: host.iobroker Caught by controller[0]: TypeError: callback is not a function 2024-09-26 17:14:25.098 - error: host.iobroker Caught by controller[0]: at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-09-26 17:14:25.098 - error: host.iobroker instance system.adapter.admin.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2024-09-26 17:14:25.098 - info: host.iobroker Restart adapter system.adapter.admin.0 because enabled 2024-09-26 17:14:25.161 - error: host.iobroker Caught by controller[0]: 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(). The promise rejected with the reason: 2024-09-26 17:14:25.161 - error: host.iobroker Caught by controller[1]: TypeError: callback is not a function 2024-09-26 17:14:25.161 - error: host.iobroker Caught by controller[1]: at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-09-26 17:14:25.161 - error: host.iobroker instance system.adapter.telegram.1 terminated with code 6 (UNCAUGHT_EXCEPTION) 2024-09-26 17:14:25.161 - info: host.iobroker Restart adapter system.adapter.telegram.1 because enabled 2024-09-26 17:14:25.654 - error: telegram.0 (578600) Unhandled promise rejection. This error originated either by throwing inside of an async function without a ca tch block, or by rejecting a promise which was not handled with .catch(). 2024-09-26 17:14:25.654 - error: telegram.0 (578600) unhandled promise rejection: callback is not a function 2024-09-26 17:14:25.656 - error: telegram.0 (578600) TypeError: callback is not a function at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:454:9) 2024-09-26 17:14:25.656 - error: telegram.0 (578600) callback is not a function 2024-09-26 17:14:26.162 - warn: telegram.0 (578600) Terminated (UNCAUGHT_EXCEPTION): Without reason 2024-09-26 17:14:26.265 - info: host.iobroker instance system.adapter.telegram.1 in version "3.9.0" started with pid 578615 2024-09-26 17:14:26.692 - error: host.iobroker Caught by controller[0]: 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(). The promise rejected with the reason: 2024-09-26 17:14:26.693 - error: host.iobroker Caught by controller[1]: TypeError: callback is not a function 2024-09-26 17:14:26.693 - error: host.iobroker Caught by controller[1]: at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-09-26 17:14:26.693 - error: host.iobroker Caught by controller[1]: at runNextTicks (node:internal/process/task_queues:60:5) 2024-09-26 17:14:26.693 - error: host.iobroker Caught by controller[1]: at processImmediate (node:internal/timers:454:9) 2024-09-26 17:14:26.693 - error: host.iobroker instance system.adapter.telegram.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2024-09-26 17:14:26.693 - info: host.iobroker Restart adapter system.adapter.telegram.0 because enabled 2024-09-26 17:14:26.693 - warn: host.iobroker Do not restart adapter system.adapter.telegram.0 because restart loop detected 2024-09-26 17:14:26.926 - error: telegram.1 (578615) Unhandled promise rejection. This error originated either by throwing inside of an async function without a ca tch block, or by rejecting a promise which was not handled with .catch(). 2024-09-26 17:14:26.926 - error: telegram.1 (578615) unhandled promise rejection: callback is not a function 2024-09-26 17:14:26.927 - error: telegram.1 (578615) TypeError: callback is not a function at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:454:9) 2024-09-26 17:14:26.928 - error: telegram.1 (578615) callback is not a function 2024-09-26 17:14:27.084 - info: host.iobroker instance system.adapter.email.0 in version "1.3.1" started with pid 578644 2024-09-26 17:14:27.352 - info: host.iobroker instance system.adapter.telegram.2 in version "3.9.0" started with pid 578652 2024-09-26 17:14:27.436 - warn: telegram.1 (578615) Terminated (UNCAUGHT_EXCEPTION): Without reason 2024-09-26 17:14:27.635 - error: email.0 (578644) 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(). 2024-09-26 17:14:27.636 - error: email.0 (578644) unhandled promise rejection: callback is not a function 2024-09-26 17:14:27.638 - error: email.0 (578644) TypeError: callback is not a function at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:454:9) 2024-09-26 17:14:27.638 - error: email.0 (578644) callback is not a function 2024-09-26 17:14:27.970 - error: host.iobroker Caught by controller[0]: 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(). The promise rejected with the reason: 2024-09-26 17:14:27.970 - error: host.iobroker Caught by controller[0]: TypeError: callback is not a function 2024-09-26 17:14:27.970 - error: host.iobroker Caught by controller[0]: at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-09-26 17:14:27.970 - error: host.iobroker Caught by controller[0]: at runNextTicks (node:internal/process/task_queues:60:5) 2024-09-26 17:14:27.970 - error: host.iobroker Caught by controller[0]: at processImmediate (node:internal/timers:454:9) 2024-09-26 17:14:27.970 - error: host.iobroker instance system.adapter.telegram.1 terminated with code 6 (UNCAUGHT_EXCEPTION) 2024-09-26 17:14:27.970 - info: host.iobroker Restart adapter system.adapter.telegram.1 because enabled 2024-09-26 17:14:28.078 - error: telegram.2 (578652) Unhandled promise rejection. This error originated either by throwing inside of an async function without a ca tch block, or by rejecting a promise which was not handled with .catch(). 2024-09-26 17:14:28.079 - error: telegram.2 (578652) unhandled promise rejection: callback is not a function 2024-09-26 17:14:28.080 - error: telegram.2 (578652) TypeError: callback is not a function at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:454:9) 2024-09-26 17:14:28.080 - error: telegram.2 (578652) callback is not a function 2024-09-26 17:14:28.147 - warn: email.0 (578644) Terminated (UNCAUGHT_EXCEPTION): Without reason 2024-09-26 17:14:28.161 - info: telegram.2 (578652) starting. Version 3.9.0 in /opt/iobroker/node_modules/iobroker.telegram, node: v20.17.0, js-controller: 7.0.0-a lpha.0-20240926-91f9b082f 2024-09-26 17:14:28.588 - info: telegram.2 (578652) terminating 2024-09-26 17:14:28.589 - warn: telegram.2 (578652) Terminated (UNCAUGHT_EXCEPTION): Without reason 2024-09-26 17:14:28.669 - error: host.iobroker Caught by controller[0]: 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(). The promise rejected with the reason: 2024-09-26 17:14:28.669 - error: host.iobroker Caught by controller[1]: TypeError: callback is not a function 2024-09-26 17:14:28.669 - error: host.iobroker Caught by controller[1]: at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-09-26 17:14:28.670 - error: host.iobroker Caught by controller[1]: at runNextTicks (node:internal/process/task_queues:60:5) 2024-09-26 17:14:28.670 - error: host.iobroker Caught by controller[1]: at processImmediate (node:internal/timers:454:9) 2024-09-26 17:14:28.670 - error: host.iobroker instance system.adapter.email.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2024-09-26 17:14:28.670 - info: host.iobroker Restart adapter system.adapter.email.0 because enabled 2024-09-26 17:14:29.077 - info: host.iobroker instance system.adapter.telegram.1 in version "3.9.0" started with pid 578689 2024-09-26 17:14:29.113 - error: host.iobroker Caught by controller[0]: 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(). The promise rejected with the reason: 2024-09-26 17:14:29.113 - error: host.iobroker Caught by controller[1]: TypeError: callback is not a function 2024-09-26 17:14:29.113 - error: host.iobroker Caught by controller[1]: at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-09-26 17:14:29.113 - error: host.iobroker Caught by controller[1]: at runNextTicks (node:internal/process/task_queues:60:5) 2024-09-26 17:14:29.113 - error: host.iobroker Caught by controller[1]: at processImmediate (node:internal/timers:454:9) 2024-09-26 17:14:29.113 - error: host.iobroker instance system.adapter.telegram.2 terminated with code 6 (UNCAUGHT_EXCEPTION) 2024-09-26 17:14:29.113 - info: host.iobroker Restart adapter system.adapter.telegram.2 because enabled 2024-09-26 17:14:29.737 - error: telegram.1 (578689) Unhandled promise rejection. This error originated either by throwing inside of an async function without a ca tch block, or by rejecting a promise which was not handled with .catch(). 2024-09-26 17:14:29.738 - error: telegram.1 (578689) unhandled promise rejection: callback is not a function 2024-09-26 17:14:29.740 - error: telegram.1 (578689) TypeError: callback is not a function at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:454:9) 2024-09-26 17:14:29.740 - error: telegram.1 (578689) callback is not a function 2024-09-26 17:14:30.224 - info: host.iobroker instance system.adapter.telegram.2 in version "3.9.0" started with pid 578704 2024-09-26 17:14:30.248 - warn: telegram.1 (578689) Terminated (UNCAUGHT_EXCEPTION): Without reason 2024-09-26 17:14:30.776 - error: host.iobroker Caught by controller[0]: 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(). The promise rejected with the reason: 2024-09-26 17:14:30.776 - error: host.iobroker Caught by controller[1]: TypeError: callback is not a function 2024-09-26 17:14:30.776 - error: host.iobroker Caught by controller[1]: at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-09-26 17:14:30.776 - error: host.iobroker Caught by controller[1]: at runNextTicks (node:internal/process/task_queues:60:5) 2024-09-26 17:14:30.776 - error: host.iobroker Caught by controller[1]: at processImmediate (node:internal/timers:454:9) 2024-09-26 17:14:30.776 - error: host.iobroker instance system.adapter.telegram.1 terminated with code 6 (UNCAUGHT_EXCEPTION) 2024-09-26 17:14:30.777 - info: host.iobroker Restart adapter system.adapter.telegram.1 because enabled 2024-09-26 17:14:30.777 - warn: host.iobroker Do not restart adapter system.adapter.telegram.1 because restart loop detected 2024-09-26 17:14:30.854 - error: telegram.2 (578704) Unhandled promise rejection. This error originated either by throwing inside of an async function without a ca tch block, or by rejecting a promise which was not handled with .catch(). 2024-09-26 17:14:30.854 - error: telegram.2 (578704) unhandled promise rejection: callback is not a function 2024-09-26 17:14:30.856 - error: telegram.2 (578704) TypeError: callback is not a function at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:454:9) 2024-09-26 17:14:30.856 - error: telegram.2 (578704) callback is not a function 2024-09-26 17:14:30.922 - info: telegram.2 (578704) starting. Version 3.9.0 in /opt/iobroker/node_modules/iobroker.telegram, node: v20.17.0, js-controller: 7.0.0-a lpha.0-20240926-91f9b082f 2024-09-26 17:14:31.361 - info: host.iobroker instance system.adapter.alexa2.0 in version "3.26.5" started with pid 578719 2024-09-26 17:14:31.363 - info: telegram.2 (578704) terminating 2024-09-26 17:14:31.365 - warn: telegram.2 (578704) Terminated (UNCAUGHT_EXCEPTION): Without reason 2024-09-26 17:14:31.607 - info: host.iobroker instance system.adapter.influxdb.0 in version "4.0.2" started with pid 578726 2024-09-26 17:14:31.902 - error: host.iobroker Caught by controller[0]: 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(). The promise rejected with the reason: 2024-09-26 17:14:31.903 - error: host.iobroker Caught by controller[1]: TypeError: callback is not a function 2024-09-26 17:14:31.903 - error: host.iobroker Caught by controller[1]: at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-09-26 17:14:31.903 - error: host.iobroker Caught by controller[1]: at runNextTicks (node:internal/process/task_queues:60:5) 2024-09-26 17:14:31.903 - error: host.iobroker Caught by controller[1]: at processImmediate (node:internal/timers:454:9) 2024-09-26 17:14:31.903 - error: host.iobroker instance system.adapter.telegram.2 terminated with code 6 (UNCAUGHT_EXCEPTION) 2024-09-26 17:14:31.904 - info: host.iobroker Restart adapter system.adapter.telegram.2 because enabled 2024-09-26 17:14:31.969 - error: alexa2.0 (578719) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catc h block, or by rejecting a promise which was not handled with .catch(). 2024-09-26 17:14:31.970 - error: alexa2.0 (578719) unhandled promise rejection: callback is not a function 2024-09-26 17:14:31.971 - error: alexa2.0 (578719) TypeError: callback is not a function at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-09-26 17:14:31.971 - error: alexa2.0 (578719) callback is not a function 2024-09-26 17:14:32.221 - error: influxdb.0 (578726) Unhandled promise rejection. This error originated either by throwing inside of an async function without a ca tch block, or by rejecting a promise which was not handled with .catch(). 2024-09-26 17:14:32.222 - error: influxdb.0 (578726) unhandled promise rejection: callback is not a function 2024-09-26 17:14:32.224 - error: influxdb.0 (578726) TypeError: callback is not a function at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:454:9) 2024-09-26 17:14:32.224 - error: influxdb.0 (578726) callback is not a function 2024-09-26 17:14:32.281 - info: influxdb.0 (578726) starting. Version 4.0.2 in /opt/iobroker/node_modules/iobroker.influxdb, node: v20.17.0, js-controller: 7.0.0-a lpha.0-20240926-91f9b082f 2024-09-26 17:14:32.479 - warn: alexa2.0 (578719) Terminated (UNCAUGHT_EXCEPTION): Without reason 2024-09-26 17:14:33.009 - error: host.iobroker Caught by controller[0]: 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(). The promise rejected with the reason: 2024-09-26 17:14:33.009 - error: host.iobroker Caught by controller[0]: TypeError: callback is not a function 2024-09-26 17:14:33.009 - error: host.iobroker Caught by controller[0]: at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-09-26 17:14:33.009 - error: host.iobroker instance system.adapter.alexa2.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2024-09-26 17:14:33.009 - info: host.iobroker Restart adapter system.adapter.alexa2.0 because enabled 2024-09-26 17:14:33.013 - info: host.iobroker instance system.adapter.telegram.2 in version "3.9.0" started with pid 578749 2024-09-26 17:14:33.231 - warn: influxdb.0 (578726) Terminated (UNCAUGHT_EXCEPTION): Without reason 2024-09-26 17:14:33.670 - error: telegram.2 (578749) Unhandled promise rejection. This error originated either by throwing inside of an async function without a ca tch block, or by rejecting a promise which was not handled with .catch(). 2024-09-26 17:14:33.670 - error: telegram.2 (578749) unhandled promise rejection: callback is not a function 2024-09-26 17:14:33.672 - error: telegram.2 (578749) TypeError: callback is not a function at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:454:9) 2024-09-26 17:14:33.672 - error: telegram.2 (578749) callback is not a function 2024-09-26 17:14:33.732 - info: telegram.2 (578749) starting. Version 3.9.0 in /opt/iobroker/node_modules/iobroker.telegram, node: v20.17.0, js-controller: 7.0.0-a lpha.0-20240926-91f9b082f 2024-09-26 17:14:33.764 - error: host.iobroker Caught by controller[0]: 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(). The promise rejected with the reason: 2024-09-26 17:14:33.764 - error: host.iobroker Caught by controller[1]: TypeError: callback is not a function 2024-09-26 17:14:33.764 - error: host.iobroker Caught by controller[1]: at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-09-26 17:14:33.764 - error: host.iobroker Caught by controller[1]: at runNextTicks (node:internal/process/task_queues:60:5) 2024-09-26 17:14:33.764 - error: host.iobroker Caught by controller[1]: at processImmediate (node:internal/timers:454:9) 2024-09-26 17:14:33.764 - error: host.iobroker instance system.adapter.influxdb.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2024-09-26 17:14:33.764 - info: host.iobroker Restart adapter system.adapter.influxdb.0 because enabled 2024-09-26 17:14:34.179 - info: telegram.2 (578749) terminating 2024-09-26 17:14:34.180 - warn: telegram.2 (578749) Terminated (UNCAUGHT_EXCEPTION): Without reason 2024-09-26 17:14:34.704 - error: host.iobroker Caught by controller[0]: 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(). The promise rejected with the reason: 2024-09-26 17:14:34.704 - error: host.iobroker Caught by controller[1]: TypeError: callback is not a function 2024-09-26 17:14:34.704 - error: host.iobroker Caught by controller[1]: at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-09-26 17:14:34.704 - error: host.iobroker Caught by controller[1]: at runNextTicks (node:internal/process/task_queues:60:5) 2024-09-26 17:14:34.704 - error: host.iobroker Caught by controller[1]: at processImmediate (node:internal/timers:454:9) 2024-09-26 17:14:34.705 - error: host.iobroker instance system.adapter.telegram.2 terminated with code 6 (UNCAUGHT_EXCEPTION) 2024-09-26 17:14:34.705 - info: host.iobroker Restart adapter system.adapter.telegram.2 because enabled 2024-09-26 17:14:34.705 - warn: host.iobroker Do not restart adapter system.adapter.telegram.2 because restart loop detected 2024-09-26 17:14:35.358 - info: host.iobroker instance system.adapter.backitup.0 in version "3.0.25" started with pid 578764 2024-09-26 17:14:35.858 - error: backitup.0 (578764) Unhandled promise rejection. This error originated either by throwing inside of an async function without a ca tch block, or by rejecting a promise which was not handled with .catch(). 2024-09-26 17:14:35.858 - error: backitup.0 (578764) unhandled promise rejection: callback is not a function 2024-09-26 17:14:35.860 - error: backitup.0 (578764) TypeError: callback is not a function at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:454:9) 2024-09-26 17:14:35.860 - error: backitup.0 (578764) callback is not a function 2024-09-26 17:14:35.921 - info: backitup.0 (578764) starting. Version 3.0.25 in /opt/iobroker/node_modules/iobroker.backitup, node: v20.17.0, js-controller: 7.0.0- alpha.0-20240926-91f9b082f 2024-09-26 17:14:36.368 - info: backitup.0 (578764) terminating 2024-09-26 17:14:36.369 - warn: backitup.0 (578764) Terminated (UNCAUGHT_EXCEPTION): Without reason 2024-09-26 17:14:36.892 - error: host.iobroker Caught by controller[0]: 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(). The promise rejected with the reason: 2024-09-26 17:14:36.892 - error: host.iobroker Caught by controller[1]: TypeError: callback is not a function 2024-09-26 17:14:36.892 - error: host.iobroker Caught by controller[1]: at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-09-26 17:14:36.892 - error: host.iobroker Caught by controller[1]: at runNextTicks (node:internal/process/task_queues:60:5) 2024-09-26 17:14:36.892 - error: host.iobroker Caught by controller[1]: at processImmediate (node:internal/timers:454:9) 2024-09-26 17:14:36.892 - error: host.iobroker instance system.adapter.backitup.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2024-09-26 17:14:36.892 - info: host.iobroker Restart adapter system.adapter.backitup.0 because enabled 2024-09-26 17:14:39.089 - info: host.iobroker instance system.adapter.pushover.0 in version "4.1.0" started with pid 578779 2024-09-26 17:14:39.392 - info: host.iobroker instance system.adapter.chromecast.0 in version "3.4.1" started with pid 578790 2024-09-26 17:14:39.632 - error: pushover.0 (578779) Unhandled promise rejection. This error originated either by throwing inside of an async function without a ca tch block, or by rejecting a promise which was not handled with .catch(). 2024-09-26 17:14:39.633 - error: pushover.0 (578779) unhandled promise rejection: callback is not a function 2024-09-26 17:14:39.634 - error: pushover.0 (578779) TypeError: callback is not a function at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-09-26 17:14:39.634 - error: pushover.0 (578779) callback is not a function 2024-09-26 17:14:39.969 - error: chromecast.0 (578790) 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(). 2024-09-26 17:14:39.970 - error: chromecast.0 (578790) unhandled promise rejection: callback is not a function 2024-09-26 17:14:39.972 - error: chromecast.0 (578790) TypeError: callback is not a function at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:454:9) 2024-09-26 17:14:39.972 - error: chromecast.0 (578790) callback is not a function 2024-09-26 17:14:40.141 - warn: pushover.0 (578779) Terminated (UNCAUGHT_EXCEPTION): Without reason 2024-09-26 17:14:40.664 - error: host.iobroker Caught by controller[0]: 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(). The promise rejected with the reason: 2024-09-26 17:14:40.664 - error: host.iobroker Caught by controller[0]: TypeError: callback is not a function 2024-09-26 17:14:40.664 - error: host.iobroker Caught by controller[0]: at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-09-26 17:14:40.664 - error: host.iobroker instance system.adapter.pushover.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2024-09-26 17:14:40.664 - info: host.iobroker Restart adapter system.adapter.pushover.0 because enabled 2024-09-26 17:14:41.004 - error: host.iobroker Caught by controller[0]: 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(). The promise rejected with the reason: 2024-09-26 17:14:41.004 - error: host.iobroker Caught by controller[1]: TypeError: callback is not a function 2024-09-26 17:14:41.004 - error: host.iobroker Caught by controller[1]: at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-09-26 17:14:41.004 - error: host.iobroker Caught by controller[1]: at runNextTicks (node:internal/process/task_queues:60:5) 2024-09-26 17:14:41.005 - error: host.iobroker Caught by controller[1]: at processImmediate (node:internal/timers:454:9) 2024-09-26 17:14:41.005 - error: host.iobroker instance system.adapter.chromecast.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2024-09-26 17:14:41.005 - info: host.iobroker Restart adapter system.adapter.chromecast.0 because enabled 2024-09-26 17:14:42.995 - info: host.iobroker instance system.adapter.pushover.1 in version "4.1.0" started with pid 578809 2024-09-26 17:14:43.363 - info: host.iobroker instance system.adapter.cloud.0 in version "5.0.1" started with pid 578820 2024-09-26 17:14:43.524 - error: pushover.1 (578809) 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(). 2024-09-26 17:14:43.525 - error: pushover.1 (578809) unhandled promise rejection: callback is not a function 2024-09-26 17:14:43.528 - error: pushover.1 (578809) TypeError: callback is not a function at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:454:9) 2024-09-26 17:14:43.528 - error: pushover.1 (578809) callback is not a function 2024-09-26 17:14:43.895 - error: cloud.0 (578820) 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(). 2024-09-26 17:14:43.896 - error: cloud.0 (578820) unhandled promise rejection: callback is not a function 2024-09-26 17:14:43.897 - error: cloud.0 (578820) TypeError: callback is not a function at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:454:9) 2024-09-26 17:14:43.897 - error: cloud.0 (578820) callback is not a function 2024-09-26 17:14:43.949 - info: cloud.0 (578820) starting. Version 5.0.1 in /opt/iobroker/node_modules/iobroker.cloud, node: v20.17.0, js-controller: 7.0.0-alpha.0-20240926-91f9b082f 2024-09-26 17:14:44.037 - warn: pushover.1 (578809) Terminated (UNCAUGHT_EXCEPTION): Without reason 2024-09-26 17:14:44.404 - info: cloud.0 (578820) terminating 2024-09-26 17:14:44.405 - warn: cloud.0 (578820) Terminated (UNCAUGHT_EXCEPTION): Without reason 2024-09-26 17:14:44.562 - error: host.iobroker Caught by controller[0]: 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(). The promise rejected with the reason: 2024-09-26 17:14:44.562 - error: host.iobroker Caught by controller[1]: TypeError: callback is not a function 2024-09-26 17:14:44.562 - error: host.iobroker Caught by controller[1]: at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-09-26 17:14:44.562 - error: host.iobroker Caught by controller[1]: at runNextTicks (node:internal/process/task_queues:60:5) 2024-09-26 17:14:44.562 - error: host.iobroker Caught by controller[1]: at processImmediate (node:internal/timers:454:9) 2024-09-26 17:14:44.562 - error: host.iobroker instance system.adapter.pushover.1 terminated with code 6 (UNCAUGHT_EXCEPTION) 2024-09-26 17:14:44.563 - info: host.iobroker Restart adapter system.adapter.pushover.1 because enabled 2024-09-26 17:14:44.929 - error: host.iobroker Caught by controller[0]: 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(). The promise rejected with the reason: 2024-09-26 17:14:44.929 - error: host.iobroker Caught by controller[1]: TypeError: callback is not a function 2024-09-26 17:14:44.929 - error: host.iobroker Caught by controller[1]: at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-09-26 17:14:44.929 - error: host.iobroker Caught by controller[1]: at runNextTicks (node:internal/process/task_queues:60:5) 2024-09-26 17:14:44.929 - error: host.iobroker Caught by controller[1]: at processImmediate (node:internal/timers:454:9) 2024-09-26 17:14:44.929 - error: host.iobroker instance system.adapter.cloud.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2024-09-26 17:14:44.929 - info: host.iobroker Restart adapter system.adapter.cloud.0 because enabled 2024-09-26 17:14:47.024 - info: host.iobroker instance system.adapter.pushover.2 in version "4.1.0" started with pid 578839 2024-09-26 17:14:47.384 - info: host.iobroker instance system.adapter.device-watcher.0 in version "2.12.1" started with pid 578850 2024-09-26 17:14:47.561 - error: pushover.2 (578839) 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(). 2024-09-26 17:14:47.562 - error: pushover.2 (578839) unhandled promise rejection: callback is not a function 2024-09-26 17:14:47.565 - error: pushover.2 (578839) TypeError: callback is not a function at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:454:9) 2024-09-26 17:14:47.565 - error: pushover.2 (578839) callback is not a function 2024-09-26 17:14:47.621 - info: pushover.2 (578839) starting. Version 4.1.0 in /opt/iobroker/node_modules/iobroker.pushover, node: v20.17.0, js-controller: 7.0.0-alpha.0-20240926-91f9b082f 2024-09-26 17:14:47.924 - error: device-watcher.0 (578850) 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(). 2024-09-26 17:14:47.925 - error: device-watcher.0 (578850) unhandled promise rejection: callback is not a function 2024-09-26 17:14:47.926 - error: device-watcher.0 (578850) TypeError: callback is not a function at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-09-26 17:14:47.927 - error: device-watcher.0 (578850) callback is not a function 2024-09-26 17:14:47.988 - info: device-watcher.0 (578850) starting. Version 2.12.1 in /opt/iobroker/node_modules/iobroker.device-watcher, node: v20.17.0, js-controller: 7.0.0-alpha.0-20240926-91f9b082f 2024-09-26 17:14:48.073 - info: pushover.2 (578839) terminating 2024-09-26 17:14:48.074 - warn: pushover.2 (578839) Terminated (UNCAUGHT_EXCEPTION): Without reason 2024-09-26 17:14:48.434 - info: device-watcher.0 (578850) terminating 2024-09-26 17:14:48.435 - warn: device-watcher.0 (578850) Terminated (UNCAUGHT_EXCEPTION): Without reason 2024-09-26 17:14:48.597 - error: host.iobroker Caught by controller[0]: 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(). The promise rejected with the reason: 2024-09-26 17:14:48.597 - error: host.iobroker Caught by controller[1]: TypeError: callback is not a function 2024-09-26 17:14:48.597 - error: host.iobroker Caught by controller[1]: at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-09-26 17:14:48.597 - error: host.iobroker Caught by controller[1]: at runNextTicks (node:internal/process/task_queues:60:5) 2024-09-26 17:14:48.597 - error: host.iobroker Caught by controller[1]: at processImmediate (node:internal/timers:454:9) 2024-09-26 17:14:48.597 - error: host.iobroker instance system.adapter.pushover.2 terminated with code 6 (UNCAUGHT_EXCEPTION) 2024-09-26 17:14:48.597 - info: host.iobroker Restart adapter system.adapter.pushover.2 because enabled 2024-09-26 17:14:48.957 - error: host.iobroker Caught by controller[0]: 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(). The promise rejected with the reason: 2024-09-26 17:14:48.957 - error: host.iobroker Caught by controller[1]: TypeError: callback is not a function 2024-09-26 17:14:48.957 - error: host.iobroker Caught by controller[1]: at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-09-26 17:14:48.957 - error: host.iobroker instance system.adapter.device-watcher.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2024-09-26 17:14:48.957 - info: host.iobroker Restart adapter system.adapter.device-watcher.0 because enabled 2024-09-26 17:14:51.381 - info: host.iobroker instance scheduled system.adapter.ical.0 0,30 * * * * 2024-09-26 17:14:51.386 - info: host.iobroker instance system.adapter.ical.0 in version "1.15.0" started with pid 578869 2024-09-26 17:14:51.923 - error: ical.0 (578869) 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(). 2024-09-26 17:14:51.924 - error: ical.0 (578869) unhandled promise rejection: callback is not a function 2024-09-26 17:14:51.926 - error: ical.0 (578869) TypeError: callback is not a function at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:454:9) 2024-09-26 17:14:51.926 - error: ical.0 (578869) callback is not a function 2024-09-26 17:14:52.959 - error: host.iobroker instance system.adapter.ical.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2024-09-26 17:14:55.213 - info: host.iobroker instance system.adapter.admin.0 in version "7.1.5" started with pid 578884 2024-09-26 17:14:55.375 - info: host.iobroker instance scheduled system.adapter.ical.1 0,30 * * * * 2024-09-26 17:14:55.380 - info: host.iobroker instance system.adapter.ical.1 in version "1.15.0" started with pid 578891 2024-09-26 17:14:55.934 - error: admin.0 (578884) 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(). 2024-09-26 17:14:55.935 - error: admin.0 (578884) unhandled promise rejection: callback is not a function 2024-09-26 17:14:55.936 - error: admin.0 (578884) TypeError: callback is not a function at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:454:9) 2024-09-26 17:14:55.936 - error: admin.0 (578884) callback is not a function 2024-09-26 17:14:55.989 - error: ical.1 (578891) 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(). 2024-09-26 17:14:55.990 - error: ical.1 (578891) unhandled promise rejection: callback is not a function 2024-09-26 17:14:55.992 - error: ical.1 (578891) TypeError: callback is not a function at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:454:9) 2024-09-26 17:14:55.993 - error: ical.1 (578891) callback is not a function 2024-09-26 17:14:56.446 - warn: admin.0 (578884) Terminated (UNCAUGHT_EXCEPTION): Without reason 2024-09-26 17:14:56.970 - error: host.iobroker Caught by controller[0]: 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(). The promise rejected with the reason: 2024-09-26 17:14:56.970 - error: host.iobroker Caught by controller[1]: TypeError: callback is not a function 2024-09-26 17:14:56.970 - error: host.iobroker Caught by controller[1]: at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-09-26 17:14:56.970 - error: host.iobroker Caught by controller[1]: at runNextTicks (node:internal/process/task_queues:60:5) 2024-09-26 17:14:56.970 - error: host.iobroker Caught by controller[1]: at processImmediate (node:internal/timers:454:9) 2024-09-26 17:14:56.970 - error: host.iobroker instance system.adapter.admin.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2024-09-26 17:14:56.970 - info: host.iobroker Restart adapter system.adapter.admin.0 because enabled 2024-09-26 17:14:56.970 - warn: host.iobroker Do not restart adapter system.adapter.admin.0 because restart loop detected 2024-09-26 17:14:57.028 - error: host.iobroker instance system.adapter.ical.1 terminated with code 6 (UNCAUGHT_EXCEPTION) 2024-09-26 17:14:58.779 - info: host.iobroker instance system.adapter.email.0 in version "1.3.1" started with pid 578914 2024-09-26 17:14:59.269 - error: email.0 (578914) 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(). 2024-09-26 17:14:59.270 - error: email.0 (578914) unhandled promise rejection: callback is not a function 2024-09-26 17:14:59.271 - error: email.0 (578914) TypeError: callback is not a function at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:454:9) 2024-09-26 17:14:59.272 - error: email.0 (578914) callback is not a function 2024-09-26 17:14:59.381 - info: host.iobroker instance system.adapter.mqtt.0 in version "6.1.2" started with pid 578929 2024-09-26 17:14:59.778 - warn: email.0 (578914) Terminated (UNCAUGHT_EXCEPTION): Without reason 2024-09-26 17:14:59.899 - error: mqtt.0 (578929) 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(). 2024-09-26 17:14:59.899 - error: mqtt.0 (578929) unhandled promise rejection: callback is not a function 2024-09-26 17:14:59.901 - error: mqtt.0 (578929) TypeError: callback is not a function at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:454:9) 2024-09-26 17:14:59.901 - error: mqtt.0 (578929) callback is not a function 2024-09-26 17:15:00.302 - error: host.iobroker Caught by controller[0]: 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(). The promise rejected with the reason: 2024-09-26 17:15:00.302 - error: host.iobroker Caught by controller[0]: TypeError: callback is not a function 2024-09-26 17:15:00.302 - error: host.iobroker Caught by controller[0]: at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-09-26 17:15:00.302 - error: host.iobroker Caught by controller[0]: at runNextTicks (node:internal/process/task_queues:60:5) 2024-09-26 17:15:00.302 - error: host.iobroker Caught by controller[0]: at processImmediate (node:internal/timers:454:9) 2024-09-26 17:15:00.302 - error: host.iobroker instance system.adapter.email.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2024-09-26 17:15:00.302 - info: host.iobroker Restart adapter system.adapter.email.0 because enabled 2024-09-26 17:15:00.302 - warn: host.iobroker Do not restart adapter system.adapter.email.0 because restart loop detected 2024-09-26 17:15:00.409 - warn: mqtt.0 (578929) Terminated (UNCAUGHT_EXCEPTION): Without reason 2024-09-26 17:15:00.931 - error: host.iobroker Caught by controller[0]: 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(). The promise rejected with the reason: 2024-09-26 17:15:00.932 - error: host.iobroker Caught by controller[1]: TypeError: callback is not a function 2024-09-26 17:15:00.932 - error: host.iobroker Caught by controller[1]: at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-09-26 17:15:00.932 - error: host.iobroker Caught by controller[1]: at runNextTicks (node:internal/process/task_queues:60:5) 2024-09-26 17:15:00.932 - error: host.iobroker Caught by controller[1]: at processImmediate (node:internal/timers:454:9) 2024-09-26 17:15:00.932 - error: host.iobroker instance system.adapter.mqtt.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2024-09-26 17:15:00.932 - info: host.iobroker Restart adapter system.adapter.mqtt.0 because enabled 2024-09-26 17:15:03.120 - info: host.iobroker instance system.adapter.alexa2.0 in version "3.26.5" started with pid 578946 2024-09-26 17:15:03.386 - info: host.iobroker instance system.adapter.netatmo.0 in version "3.1.0" started with pid 578953 2024-09-26 17:15:03.657 - error: alexa2.0 (578946) 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(). 2024-09-26 17:15:03.658 - error: alexa2.0 (578946) unhandled promise rejection: callback is not a function 2024-09-26 17:15:03.660 - error: alexa2.0 (578946) TypeError: callback is not a function at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:454:9) 2024-09-26 17:15:03.660 - error: alexa2.0 (578946) callback is not a function 2024-09-26 17:15:03.888 - info: host.iobroker instance system.adapter.influxdb.0 in version "4.0.2" started with pid 578972 2024-09-26 17:15:04.051 - error: netatmo.0 (578953) 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(). 2024-09-26 17:15:04.052 - error: netatmo.0 (578953) unhandled promise rejection: callback is not a function 2024-09-26 17:15:04.054 - error: netatmo.0 (578953) TypeError: callback is not a function at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:454:9) 2024-09-26 17:15:04.054 - error: netatmo.0 (578953) callback is not a function 2024-09-26 17:15:04.166 - warn: alexa2.0 (578946) Terminated (UNCAUGHT_EXCEPTION): Without reason 2024-09-26 17:15:04.473 - error: influxdb.0 (578972) 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(). 2024-09-26 17:15:04.474 - error: influxdb.0 (578972) unhandled promise rejection: callback is not a function 2024-09-26 17:15:04.476 - error: influxdb.0 (578972) TypeError: callback is not a function at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:454:9) 2024-09-26 17:15:04.476 - error: influxdb.0 (578972) callback is not a function 2024-09-26 17:15:04.526 - info: influxdb.0 (578972) starting. Version 4.0.2 in /opt/iobroker/node_modules/iobroker.influxdb, node: v20.17.0, js-controller: 7.0.0-alpha.0-20240926-91f9b082f 2024-09-26 17:15:04.563 - warn: netatmo.0 (578953) Terminated (UNCAUGHT_EXCEPTION): Without reason 2024-09-26 17:15:04.691 - error: host.iobroker Caught by controller[0]: 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(). The promise rejected with the reason: 2024-09-26 17:15:04.692 - error: host.iobroker Caught by controller[1]: TypeError: callback is not a function 2024-09-26 17:15:04.692 - error: host.iobroker Caught by controller[1]: at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-09-26 17:15:04.692 - error: host.iobroker Caught by controller[1]: at runNextTicks (node:internal/process/task_queues:60:5) 2024-09-26 17:15:04.692 - error: host.iobroker Caught by controller[1]: at processImmediate (node:internal/timers:454:9) 2024-09-26 17:15:04.692 - error: host.iobroker instance system.adapter.alexa2.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2024-09-26 17:15:04.692 - info: host.iobroker Restart adapter system.adapter.alexa2.0 because enabled 2024-09-26 17:15:05.086 - error: host.iobroker Caught by controller[0]: 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(). The promise rejected with the reason: 2024-09-26 17:15:05.086 - error: host.iobroker Caught by controller[1]: TypeError: callback is not a function 2024-09-26 17:15:05.086 - error: host.iobroker Caught by controller[1]: at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-09-26 17:15:05.086 - error: host.iobroker Caught by controller[1]: at runNextTicks (node:internal/process/task_queues:60:5) 2024-09-26 17:15:05.086 - error: host.iobroker Caught by controller[1]: at processImmediate (node:internal/timers:454:9) 2024-09-26 17:15:05.086 - error: host.iobroker instance system.adapter.netatmo.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2024-09-26 17:15:05.086 - info: host.iobroker Restart adapter system.adapter.netatmo.0 because enabled 2024-09-26 17:15:05.483 - warn: influxdb.0 (578972) Terminated (UNCAUGHT_EXCEPTION): Without reason 2024-09-26 17:15:06.006 - error: host.iobroker Caught by controller[0]: 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(). The promise rejected with the reason: 2024-09-26 17:15:06.007 - error: host.iobroker Caught by controller[1]: TypeError: callback is not a function 2024-09-26 17:15:06.007 - error: host.iobroker Caught by controller[1]: at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-09-26 17:15:06.007 - error: host.iobroker Caught by controller[1]: at runNextTicks (node:internal/process/task_queues:60:5) 2024-09-26 17:15:06.007 - error: host.iobroker Caught by controller[1]: at processImmediate (node:internal/timers:454:9) 2024-09-26 17:15:06.007 - error: host.iobroker instance system.adapter.influxdb.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2024-09-26 17:15:06.007 - info: host.iobroker Restart adapter system.adapter.influxdb.0 because enabled 2024-09-26 17:15:06.007 - warn: host.iobroker Do not restart adapter system.adapter.influxdb.0 because restart loop detected 2024-09-26 17:15:07.023 - info: host.iobroker instance system.adapter.backitup.0 in version "3.0.25" started with pid 578991 2024-09-26 17:15:07.400 - info: host.iobroker instance system.adapter.notification-manager.0 in version "1.2.1" started with pid 579002 2024-09-26 17:15:07.572 - error: backitup.0 (578991) 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(). 2024-09-26 17:15:07.573 - error: backitup.0 (578991) unhandled promise rejection: callback is not a function 2024-09-26 17:15:07.574 - error: backitup.0 (578991) TypeError: callback is not a function at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:454:9) 2024-09-26 17:15:07.574 - error: backitup.0 (578991) callback is not a function 2024-09-26 17:15:07.642 - info: backitup.0 (578991) starting. Version 3.0.25 in /opt/iobroker/node_modules/iobroker.backitup, node: v20.17.0, js-controller: 7.0.0-alpha.0-20240926-91f9b082f 2024-09-26 17:15:07.831 - info: notification-manager.0 (579002) starting. Version 1.2.1 in /opt/iobroker/node_modules/iobroker.notification-manager, node: v20.17.0, js-controller: 7.0.0-alpha.0-20240926-91f9b082f 2024-09-26 17:15:07.839 - info: notification-manager.0 (579002) Starting notification manager ... 2024-09-26 17:15:07.850 - info: notification-manager.0 (579002) Send notification "system.restartLoop" to "telegram.0" 2024-09-26 17:15:08.082 - info: backitup.0 (578991) terminating 2024-09-26 17:15:08.083 - warn: backitup.0 (578991) Terminated (UNCAUGHT_EXCEPTION): Without reason 2024-09-26 17:15:08.606 - error: host.iobroker Caught by controller[0]: 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(). The promise rejected with the reason: 2024-09-26 17:15:08.607 - error: host.iobroker Caught by controller[1]: TypeError: callback is not a function 2024-09-26 17:15:08.607 - error: host.iobroker Caught by controller[1]: at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-09-26 17:15:08.607 - error: host.iobroker Caught by controller[1]: at runNextTicks (node:internal/process/task_queues:60:5) 2024-09-26 17:15:08.607 - error: host.iobroker Caught by controller[1]: at processImmediate (node:internal/timers:454:9) 2024-09-26 17:15:08.607 - error: host.iobroker instance system.adapter.backitup.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2024-09-26 17:15:08.607 - info: host.iobroker Restart adapter system.adapter.backitup.0 because enabled 2024-09-26 17:15:10.776 - info: host.iobroker instance system.adapter.pushover.0 in version "4.1.0" started with pid 579021 2024-09-26 17:15:11.128 - info: host.iobroker instance system.adapter.chromecast.0 in version "3.4.1" started with pid 579032 2024-09-26 17:15:11.378 - error: pushover.0 (579021) 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(). 2024-09-26 17:15:11.379 - error: pushover.0 (579021) unhandled promise rejection: callback is not a function 2024-09-26 17:15:11.381 - error: pushover.0 (579021) TypeError: callback is not a function at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:454:9) 2024-09-26 17:15:11.381 - error: pushover.0 (579021) callback is not a function 2024-09-26 17:15:11.400 - info: notification-manager.0 (579002) Send notification "system.restartLoop" to "telegram.0" 2024-09-26 17:15:11.414 - info: host.iobroker instance system.adapter.nuki.0 in version "2.0.0" started with pid 579039 2024-09-26 17:15:11.683 - error: chromecast.0 (579032) 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(). 2024-09-26 17:15:11.688 - info: notification-manager.0 (579002) Send notification "system.restartLoop" to "telegram.0" 2024-09-26 17:15:11.684 - error: chromecast.0 (579032) unhandled promise rejection: callback is not a function 2024-09-26 17:15:11.685 - error: chromecast.0 (579032) TypeError: callback is not a function at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:454:9) 2024-09-26 17:15:11.685 - error: chromecast.0 (579032) callback is not a function 2024-09-26 17:15:11.892 - warn: pushover.0 (579021) Terminated (UNCAUGHT_EXCEPTION): Without reason 2024-09-26 17:15:11.996 - info: nuki.0 (579039) starting. Version 2.0.0 in /opt/iobroker/node_modules/iobroker.nuki, node: v20.17.0, js-controller: 7.0.0-alpha.0-20240926-91f9b082f 2024-09-26 17:15:12.416 - error: host.iobroker Caught by controller[0]: 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(). The promise rejected with the reason: 2024-09-26 17:15:12.416 - error: host.iobroker Caught by controller[0]: TypeError: callback is not a function 2024-09-26 17:15:12.416 - error: host.iobroker Caught by controller[0]: at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-09-26 17:15:12.416 - error: host.iobroker Caught by controller[0]: at runNextTicks (node:internal/process/task_queues:60:5) 2024-09-26 17:15:12.416 - error: host.iobroker Caught by controller[0]: at processImmediate (node:internal/timers:454:9) 2024-09-26 17:15:12.416 - error: host.iobroker instance system.adapter.pushover.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2024-09-26 17:15:12.417 - info: host.iobroker Restart adapter system.adapter.pushover.0 because enabled 2024-09-26 17:15:12.417 - warn: host.iobroker Do not restart adapter system.adapter.pushover.0 because restart loop detected 2024-09-26 17:15:12.420 - info: notification-manager.0 (579002) Send notification "system.restartLoop" to "telegram.0" 2024-09-26 17:15:12.717 - error: host.iobroker Caught by controller[0]: 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(). The promise rejected with the reason: 2024-09-26 17:15:12.717 - error: host.iobroker Caught by controller[1]: TypeError: callback is not a function 2024-09-26 17:15:12.717 - error: host.iobroker Caught by controller[1]: at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-09-26 17:15:12.717 - error: host.iobroker Caught by controller[1]: at runNextTicks (node:internal/process/task_queues:60:5) 2024-09-26 17:15:12.717 - error: host.iobroker Caught by controller[1]: at processImmediate (node:internal/timers:454:9) 2024-09-26 17:15:12.717 - error: host.iobroker instance system.adapter.chromecast.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2024-09-26 17:15:12.717 - info: host.iobroker Restart adapter system.adapter.chromecast.0 because enabled 2024-09-26 17:15:12.853 - error: notification-manager.0 (579002) Error appeared while sending notification "system.restartLoop" to "telegram.0": Timeout exceeded 2024-09-26 17:15:12.854 - error: notification-manager.0 (579002) Instance telegram.0 could not handle the notification for "system.restartLoop"@shadowhunter23 Könntest du da mal die Ausgabe zeigen von
npm ls @iobroker/plugin-sentryund
npm ls @iobroker/plugin-basejeweils im Verzeichnis
/opt/iobrokerausgeführtDer Fehler deutet stark daraufhin, dass da eine alte Version von
@iobroker/plugin-basegenutzt wird. Eventuell hat ein Paket diese inkorrekterweise als Dependency konfiguriert was dazu führt das eine falsche Version herangezogen wird.Hier könnt ihr mich unterstützen.
-
@shadowhunter23 Könntest du da mal die Ausgabe zeigen von
npm ls @iobroker/plugin-sentryund
npm ls @iobroker/plugin-basejeweils im Verzeichnis
/opt/iobrokerausgeführtDer Fehler deutet stark daraufhin, dass da eine alte Version von
@iobroker/plugin-basegenutzt wird. Eventuell hat ein Paket diese inkorrekterweise als Dependency konfiguriert was dazu führt das eine falsche Version herangezogen wird.tobias@iobroker:~$ cd /opt/iobroker/ tobias@iobroker:/opt/iobroker$ npm ls @iobroker/plugin-sentry iobroker.inst@3.0.0 /opt/iobroker +-- iobroker.js-controller@6.0.11 | +-- @iobroker/js-controller-adapter@6.0.11 | | `-- @iobroker/plugin-sentry@1.2.1 deduped | `-- @iobroker/plugin-sentry@1.2.1 `-- iobroker.wireguard@1.6.4 `-- @iobroker/plugin-sentry@1.2.1 deduped tobias@iobroker:/opt/iobroker$ npm ls @iobroker/plugin-base iobroker.inst@3.0.0 /opt/iobroker `-- iobroker.js-controller@6.0.11 +-- @iobroker/js-controller-adapter@6.0.11 | `-- @iobroker/plugin-base@1.2.1 deduped +-- @iobroker/plugin-base@1.2.1 `-- @iobroker/plugin-sentry@1.2.1 `-- @iobroker/plugin-base@1.2.1 deduped tobias@iobroker:/opt/iobroker$ -
@shadowhunter23 Könntest du da mal die Ausgabe zeigen von
npm ls @iobroker/plugin-sentryund
npm ls @iobroker/plugin-basejeweils im Verzeichnis
/opt/iobrokerausgeführtDer Fehler deutet stark daraufhin, dass da eine alte Version von
@iobroker/plugin-basegenutzt wird. Eventuell hat ein Paket diese inkorrekterweise als Dependency konfiguriert was dazu führt das eine falsche Version herangezogen wird.@foxriver76 Danke, der wireguard Adapter scheint der Übeltäter zu sein. Ich probiere das schnell zu fixen!
-
@shadowhunter23 Könntest du da mal die Ausgabe zeigen von
npm ls @iobroker/plugin-sentryund
npm ls @iobroker/plugin-basejeweils im Verzeichnis
/opt/iobrokerausgeführtDer Fehler deutet stark daraufhin, dass da eine alte Version von
@iobroker/plugin-basegenutzt wird. Eventuell hat ein Paket diese inkorrekterweise als Dependency konfiguriert was dazu führt das eine falsche Version herangezogen wird.Hier soweit kein Aufflälligkeiten, System rennt:
===================== ZUSAMMENFASSUNG ===================== v.2024-09-16 Static hostname: chet Icon name: computer Operating System: Debian GNU/Linux trixie/sid Kernel: Linux 6.6.47+rpt-rpi-v8 Architecture: arm64 Installation: native Kernel: aarch64 Userland: 64 bit Timezone: Europe/Berlin (CEST, +0200) User-ID: 1000 Display-Server: false Boot Target: multi-user.target Offene OS-Updates: 0 Offene iob updates: 0 Nodejs-Installation: /usr/bin/nodejs v22.9.0 /usr/bin/node v22.9.0 /usr/bin/npm 10.8.3 /usr/bin/npx 10.8.3 /usr/bin/corepack 0.29.3 Empfohlene Versionen sind zurzeit nodejs 20.17.0 und npm 10.8.2 nodeJS ist korrekt installiert MEMORY: total used free shared buff/cache available Mem: 8.2G 2.9G 1.2G 876K 4.2G 5.2G Swap: 2.4G 0B 2.4G Total: 10G 2.9G 3.6G Active iob-Instances: 38 Upgrade policy: none ioBroker Core: js-controller 7.0.0-alpha.0-20240926-91f9b082f admin 7.1.5 ioBroker Status: iobroker is running on this host. Objects type: jsonl States type: jsonl Status admin and web instance: + system.adapter.admin.0 : admin : chet - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.web.0 : web : chet - enabled, port: 8082, bind: 0.0.0.0, run as: admin Objects: 11221 States: 8962 Size of iob-Database: 28M /opt/iobroker/iobroker-data/objects.jsonl 4.9M /opt/iobroker/iobroker-data/states.jsonl Das Betriebssystem mit dem Codenamen 'trixie' ist eine Testversion! Es sollte nur zu Testzwecken eingesetzt werden! =================== ENDE DER ZUSAMMENFASSUNG ==================== -
@foxriver76 Danke, der wireguard Adapter scheint der Übeltäter zu sein. Ich probiere das schnell zu fixen!
@foxriver76
Kein Stress, ich hab keine Eile! -
Wenn ich Node-Red öffnen möchte, erscheint die falsche URL im Browser.
httpundefined://192.168.2.230:1880/Gruß
Peterfido
Proxmox auf Intel NUC12WSHi5
ioBroker: Debian (VM)
CCU: Debmatic (VM)
Influx: Debian (VM)
Grafana: Debian (VM)
eBus: Debian (VM)
Zigbee: Debian (VM) mit zigbee2mqtt -
Wenn ich Node-Red öffnen möchte, erscheint die falsche URL im Browser.
httpundefined://192.168.2.230:1880/@peterfido sicher dass das mit Controller 6 nicht so war? Ich denke das ist eher Admin oder Adapter
Hier könnt ihr mich unterstützen.
-
@foxriver76 Ich habe für den Test 7.0.0.0 eine neue VM erstellt. Im Produktivsystem passt der rot eingekreiste Link,
-
@peterfido sicher dass das mit Controller 6 nicht so war? Ich denke das ist eher Admin oder Adapter
@foxriver76
Ich habe noch ein Testsystem (6.0.11), welches ich für das Proxmox-Speicher-Problem angelegt habe. Da habe ich mal eben Node-Red installiert und der Fehler tritt auch da auf.Also wohl ein Problem von Node-Red. Ich habe mal ein Issue geöffnet.
-
@peterfido sicher dass das mit Controller 6 nicht so war? Ich denke das ist eher Admin oder Adapter
@foxriver76 sagte in js-controller Lucy (v7.0.0) Alpha Test:
sicher dass das mit Controller 6 nicht so war?
Hat nichts mit Controller zu tun. Gibt es schon länger.
-
Aktuelle Test Version 7.0.0 Veröffentlichungsdatum 26.09.2024 Hallo ioBroker-Community,
Erst Ende Mai ging es in den Alpha Test für den js-controller 6 und da steht auch schon die Version 7 in den Startlöchern.
Wir haben uns für einen verkürzten Release-Zyklus entschieden, was auch heißt, dass es weniger Features in dieser Version gibt allerdings dadurch auch weniger Zeit für den Alpha und Beta Test gebraucht werden sollte.Somit möchte ich euch heute den js-controller 7.0 für einen ersten Alpha-test zur Verfügung stellen. Dieser Post enthält alle wichtigen Infos.
:grey_exclamation: Node.js Versions-Anforderungen
Die unterstützten Node.js Versionen sind weiterhin: 18.x, 20.x und voraussichtlich 22.x. Die empfohlene Node.js Version für ioBroker ist Stand heute 20.x.
Bitte beachtet weiterhin bei Node.js Updates die Anleitung im Forum unter https://forum.iobroker.net/topic/64032/update-nodejs-best-practise-supported-14-16-und-18 !:exclamation: Informationen zur Version
Hier möchte ich euch als erstes einen Einblick in die für euch relevanten neuen Features geben.
:star2: Feature Spotlight
:new: Dynamic Notifications
Diese Version bringt vorallem ein neues Feature: Dynamic Notifications, dies ermöglicht es Entwicklern Benachrichtigungen zu generieren mit welchen Adapter interagieren können. Als erstes steht der Admin Adapter hier im Rampenlicht, welcher es nun ermöglicht, dass ihr als Anwender mit Benachrichtigungen interagieren könnt, z. B. benachrichtigt euch der Ping Adapter mit diesem Feature über neue Geräte in eurem Netzwerk. Direkt im Notification Dialog habt ihr nun die Möglichkeit die neu gefundenen Geräte mit dem Ping Adapter zu überwachen. Wir hoffen damit die Nutzererfahrung weiterhin zu verbessern und hoffen das weitere Adapter folgen.
Für die Entwickler unter euch, verweise ich zur Implementierung dieses Features in eurem Adapter aktuell auf den Ping Adapter welcher dieses Feature nutzt. Das Feature basiert auf JSON Config und benötigt somit keine umfangreiche Erfahrung im Frontend. Eine Dokumentation im Admin Adapter wird folgen welche ich hier ergänzen werde.
:new: Docker Notifications
Um bei den Notifications zu bleiben, gibt es nun für Nutzer des offiziellen ioBroker Docker Containers eine Benachrichtigung sobald eine neue Version auf Docker Hub zur Verfügung steht. Somit verpasst ihr keinen Release mehr und haltet euer System bequem aktuell!
:new: Neue Backup-Technologie
Weiterhin haben wir die interne Backup Mechanik komplett überarbeitet. Statt das gesamte Backup File auf ein mal einzulesen nutzt das Backup nun JSONL, was ihr bereits von der Standard Datenbank kennt. Somit ist die Erstellung und Wiederherstellung von Backups großer Installationen kein Problem mehr. Und mit groß meinen wir, dass das Konzept beliebig skaliert - in der Theorie sind selbst Backups mit mehreren Millionen Objekten kein Problem!
Um dies zu erreichen haben wir die interne Mechanik so optimiert, dass diese inkompatibel mit alten js-controller Versionen ist. Umgekehrt haben wir eine Möglichkeit geschaffen, dass ältere Backups mit der neuen Controller Version wiederhergestellt werden können.
:information_source: Weitere Informationen
Detailliertere Informationen zu allen Änderungen und Features findet Ihr weiter unten und im Changelog. Ich hoffe auch diesmal auf Eure tatkräftige Unterstützung, sodass der Latest-Release dann genau so reibungslos verläuft wie bei den letzten Versionen.
Für die aktive Mitarbeit an dieser Version des js-controller bedanke mich diesmal wieder besonders bei Apollon77 und Bluefox!
Darüber hinaus ist der js-controller 7.0 generell kompatibel mit allen bestehenden ioBroker-Systemen. Ein Update von der Version 6.0.x ist problemlos möglich.
Ansonsten empfehlen wir ein schrittweises Update auf die 7.0 (3.3.x -> 4.0 -> 5.0 -> 6.0).:floppy_disk: Installation
:one: VOR der Installation
Wie bei jedem Test dieser Art: Bitte macht ein Backup!
iobroker backupbzw kopieren desiobroker-dataVerzeichnisses reichen an sich aus. Bitte nicht das node_modules Verzeichnis einfach kopieren, da sonst symbolische Links kaputt gehen können, was zu größeren Problemen danach führt.
Eine alte 6.0.x-Version des js-controller kann im Notfall einfach wieder pernpm install iobroker.js-controller@version --omit=dev("version" durch die gewünschte Versionsnummer ersetzen) installiert werden und sollte alles wieder herstellen (Letzter Stable Stand ist die 6.0.11):two: Nötige Adapter-Aktualisierungen
Am besten VOR dem js-controller Update alle verfügbaren Adapter-Updates prüfen und alle Updates installieren, die im Changelog auf Optimierungen oder Anpassungen für den js-controller 7.0 oder höher hinweisen.
Mit den stable Versionen der jeweiligen Adapter sollten keine Probleme auftreten, falls doch bitte hier melden.:three: Achtung: MASTER/SLAVE-Systeme Reihenfolgen beachten!
Bei einem Multi-Host-System, welches auf js-controller 6.0.x läuft, ist es beim Update auf Version 7.0 empfohlen, zuerst das Master-System zu aktualisieren. Der Master muss dann wieder gestartet werden. Die Slaves werden danach aktualisiert!
Bei Updates von Master/Slave-Systemen mit js-controller 4.x oder früher Bitte die jeweiligen Update Threads der empfohlenen Zwischenversionen prüfen.
:four: Windows
Wir empfehlen euch den Weg über den Installer zu nutzen. Hierzu im Expertenmodus das Häkchen bei "Nutze Alpha-Repo (@next)" setzen und das Update durchführen.
Im Zweifel kann das Update manuell via npm installiert werden. Hierzu im ioBroker-Verzeichnis nach stoppen des ioBroker den Befehlnpm i iobroker.js-controller@next --omit=devausführen.:four: Linux
- ioBroker stoppen (iobroker stop)
- Prüfen das keine Prozesse (Adapter, Backups) mehr laufen (
ps auxww|grep iound auchps auxww|grep backup). Es passiert manchmal das trotz dem Stoppen noch Zombies zurückbleiben cd /opt/iobroker- Das Update erfolgt via
npm i iobroker.js-controller@next --omit=dev - ioBroker starten (
iobroker start)
:five: Bei Fehlern:
Wenn bei der Installation Fehler wegen fehlender Zugriffsrechte auftreten, am besten den Installation-Fixer (
iobroker fixwer schon einen js-controller 2.x oder höher hat, alternativ weiterhin manuell viacurl -sL https://iobroker.net/fix.sh | bash -) nutzen und die Installation wiederholen.
Falls es auch danach noch Fehler gibt, bitte die Installation erneut mittelssudo -H -u iobroker npm install iobroker.js-controller@next --omit=devversuchen. Bitte berichtet solche Fälle hier im Thread.:six: NACH der Installation
Wenn alles klappt merkt Ihr ausser der höheren Versionsnummer in der Host-Ansicht im Admin keinen Unterschied. Alles funktioniert weiterhin wie vorher. Alle Adapterinstanzen starten und funktionieren. Wenn das so ist hat alles geklappt.
Falls im Log Warn-Meldungen auftauchen mit dem Hinweis diese an den Entwickler zu senden, dann bitte schauen welcher Adapter es ist und entsprechend dort Issues bitte anlegen!
Was hat sich geändert, was besonders ansehen/beachten?Speziell die Entwickler sollten sich das Dynamic Notifications Feature anschauen.
Hier für Interessierte als Spoiler eine Zusammenfassung des Changelogs :newspaper::
Generell ist zu testen, ob alles noch so funktioniert wie vorher auch. Das ist das Wichtigste!
Wie Fehler melden?Wer sich unsicher ist, ob ein Fehler vorliegt, sollte am besten hier im Thread das Problem beschreiben. So können wir alle versuchen, das Problem nachzuvollziehen und ggf. einzugrenzen.
Bitte checkt auch die "Known issues Liste" (zweiter Post) mit den Dingen die aktuell während der Alpha bekannt sind und bis zum Releasen noch angepasst werden.
Sobald ein Fehler auftritt der in einer Fehlermeldung oder einen Crash mit Fehlerdetails im Log oder auf Kommandozeile endet, dann dazu am besten direkt ein GitHub-Issue im js-controller Projekt öffnen und zusätzlich hier im Thread posten. Je detaillierter die Angaben im Issue sind (genaue Fehlermeldungen/Logs, Infos zur OS- und Node.js-Umgebung sowie genaue Schritte zur Reproduktion des Problems), umso schneller können wir Fehler einkreisen und beheben.
Bitte postet auch die Ausgabe von
iob diagmit rein.Wir wünschen allen viel Spaß beim Testen und vielen Dank für Eure Unterstützung!
Moritz
Läuft bei mir ebenfalls - ohne Probleme
-
Aktuelle Test Version 7.0.0 Veröffentlichungsdatum 26.09.2024 Hallo ioBroker-Community,
Erst Ende Mai ging es in den Alpha Test für den js-controller 6 und da steht auch schon die Version 7 in den Startlöchern.
Wir haben uns für einen verkürzten Release-Zyklus entschieden, was auch heißt, dass es weniger Features in dieser Version gibt allerdings dadurch auch weniger Zeit für den Alpha und Beta Test gebraucht werden sollte.Somit möchte ich euch heute den js-controller 7.0 für einen ersten Alpha-test zur Verfügung stellen. Dieser Post enthält alle wichtigen Infos.
:grey_exclamation: Node.js Versions-Anforderungen
Die unterstützten Node.js Versionen sind weiterhin: 18.x, 20.x und voraussichtlich 22.x. Die empfohlene Node.js Version für ioBroker ist Stand heute 20.x.
Bitte beachtet weiterhin bei Node.js Updates die Anleitung im Forum unter https://forum.iobroker.net/topic/64032/update-nodejs-best-practise-supported-14-16-und-18 !:exclamation: Informationen zur Version
Hier möchte ich euch als erstes einen Einblick in die für euch relevanten neuen Features geben.
:star2: Feature Spotlight
:new: Dynamic Notifications
Diese Version bringt vorallem ein neues Feature: Dynamic Notifications, dies ermöglicht es Entwicklern Benachrichtigungen zu generieren mit welchen Adapter interagieren können. Als erstes steht der Admin Adapter hier im Rampenlicht, welcher es nun ermöglicht, dass ihr als Anwender mit Benachrichtigungen interagieren könnt, z. B. benachrichtigt euch der Ping Adapter mit diesem Feature über neue Geräte in eurem Netzwerk. Direkt im Notification Dialog habt ihr nun die Möglichkeit die neu gefundenen Geräte mit dem Ping Adapter zu überwachen. Wir hoffen damit die Nutzererfahrung weiterhin zu verbessern und hoffen das weitere Adapter folgen.
Für die Entwickler unter euch, verweise ich zur Implementierung dieses Features in eurem Adapter aktuell auf den Ping Adapter welcher dieses Feature nutzt. Das Feature basiert auf JSON Config und benötigt somit keine umfangreiche Erfahrung im Frontend. Eine Dokumentation im Admin Adapter wird folgen welche ich hier ergänzen werde.
:new: Docker Notifications
Um bei den Notifications zu bleiben, gibt es nun für Nutzer des offiziellen ioBroker Docker Containers eine Benachrichtigung sobald eine neue Version auf Docker Hub zur Verfügung steht. Somit verpasst ihr keinen Release mehr und haltet euer System bequem aktuell!
:new: Neue Backup-Technologie
Weiterhin haben wir die interne Backup Mechanik komplett überarbeitet. Statt das gesamte Backup File auf ein mal einzulesen nutzt das Backup nun JSONL, was ihr bereits von der Standard Datenbank kennt. Somit ist die Erstellung und Wiederherstellung von Backups großer Installationen kein Problem mehr. Und mit groß meinen wir, dass das Konzept beliebig skaliert - in der Theorie sind selbst Backups mit mehreren Millionen Objekten kein Problem!
Um dies zu erreichen haben wir die interne Mechanik so optimiert, dass diese inkompatibel mit alten js-controller Versionen ist. Umgekehrt haben wir eine Möglichkeit geschaffen, dass ältere Backups mit der neuen Controller Version wiederhergestellt werden können.
:information_source: Weitere Informationen
Detailliertere Informationen zu allen Änderungen und Features findet Ihr weiter unten und im Changelog. Ich hoffe auch diesmal auf Eure tatkräftige Unterstützung, sodass der Latest-Release dann genau so reibungslos verläuft wie bei den letzten Versionen.
Für die aktive Mitarbeit an dieser Version des js-controller bedanke mich diesmal wieder besonders bei Apollon77 und Bluefox!
Darüber hinaus ist der js-controller 7.0 generell kompatibel mit allen bestehenden ioBroker-Systemen. Ein Update von der Version 6.0.x ist problemlos möglich.
Ansonsten empfehlen wir ein schrittweises Update auf die 7.0 (3.3.x -> 4.0 -> 5.0 -> 6.0).:floppy_disk: Installation
:one: VOR der Installation
Wie bei jedem Test dieser Art: Bitte macht ein Backup!
iobroker backupbzw kopieren desiobroker-dataVerzeichnisses reichen an sich aus. Bitte nicht das node_modules Verzeichnis einfach kopieren, da sonst symbolische Links kaputt gehen können, was zu größeren Problemen danach führt.
Eine alte 6.0.x-Version des js-controller kann im Notfall einfach wieder pernpm install iobroker.js-controller@version --omit=dev("version" durch die gewünschte Versionsnummer ersetzen) installiert werden und sollte alles wieder herstellen (Letzter Stable Stand ist die 6.0.11):two: Nötige Adapter-Aktualisierungen
Am besten VOR dem js-controller Update alle verfügbaren Adapter-Updates prüfen und alle Updates installieren, die im Changelog auf Optimierungen oder Anpassungen für den js-controller 7.0 oder höher hinweisen.
Mit den stable Versionen der jeweiligen Adapter sollten keine Probleme auftreten, falls doch bitte hier melden.:three: Achtung: MASTER/SLAVE-Systeme Reihenfolgen beachten!
Bei einem Multi-Host-System, welches auf js-controller 6.0.x läuft, ist es beim Update auf Version 7.0 empfohlen, zuerst das Master-System zu aktualisieren. Der Master muss dann wieder gestartet werden. Die Slaves werden danach aktualisiert!
Bei Updates von Master/Slave-Systemen mit js-controller 4.x oder früher Bitte die jeweiligen Update Threads der empfohlenen Zwischenversionen prüfen.
:four: Windows
Wir empfehlen euch den Weg über den Installer zu nutzen. Hierzu im Expertenmodus das Häkchen bei "Nutze Alpha-Repo (@next)" setzen und das Update durchführen.
Im Zweifel kann das Update manuell via npm installiert werden. Hierzu im ioBroker-Verzeichnis nach stoppen des ioBroker den Befehlnpm i iobroker.js-controller@next --omit=devausführen.:four: Linux
- ioBroker stoppen (iobroker stop)
- Prüfen das keine Prozesse (Adapter, Backups) mehr laufen (
ps auxww|grep iound auchps auxww|grep backup). Es passiert manchmal das trotz dem Stoppen noch Zombies zurückbleiben cd /opt/iobroker- Das Update erfolgt via
npm i iobroker.js-controller@next --omit=dev - ioBroker starten (
iobroker start)
:five: Bei Fehlern:
Wenn bei der Installation Fehler wegen fehlender Zugriffsrechte auftreten, am besten den Installation-Fixer (
iobroker fixwer schon einen js-controller 2.x oder höher hat, alternativ weiterhin manuell viacurl -sL https://iobroker.net/fix.sh | bash -) nutzen und die Installation wiederholen.
Falls es auch danach noch Fehler gibt, bitte die Installation erneut mittelssudo -H -u iobroker npm install iobroker.js-controller@next --omit=devversuchen. Bitte berichtet solche Fälle hier im Thread.:six: NACH der Installation
Wenn alles klappt merkt Ihr ausser der höheren Versionsnummer in der Host-Ansicht im Admin keinen Unterschied. Alles funktioniert weiterhin wie vorher. Alle Adapterinstanzen starten und funktionieren. Wenn das so ist hat alles geklappt.
Falls im Log Warn-Meldungen auftauchen mit dem Hinweis diese an den Entwickler zu senden, dann bitte schauen welcher Adapter es ist und entsprechend dort Issues bitte anlegen!
Was hat sich geändert, was besonders ansehen/beachten?Speziell die Entwickler sollten sich das Dynamic Notifications Feature anschauen.
Hier für Interessierte als Spoiler eine Zusammenfassung des Changelogs :newspaper::
Generell ist zu testen, ob alles noch so funktioniert wie vorher auch. Das ist das Wichtigste!
Wie Fehler melden?Wer sich unsicher ist, ob ein Fehler vorliegt, sollte am besten hier im Thread das Problem beschreiben. So können wir alle versuchen, das Problem nachzuvollziehen und ggf. einzugrenzen.
Bitte checkt auch die "Known issues Liste" (zweiter Post) mit den Dingen die aktuell während der Alpha bekannt sind und bis zum Releasen noch angepasst werden.
Sobald ein Fehler auftritt der in einer Fehlermeldung oder einen Crash mit Fehlerdetails im Log oder auf Kommandozeile endet, dann dazu am besten direkt ein GitHub-Issue im js-controller Projekt öffnen und zusätzlich hier im Thread posten. Je detaillierter die Angaben im Issue sind (genaue Fehlermeldungen/Logs, Infos zur OS- und Node.js-Umgebung sowie genaue Schritte zur Reproduktion des Problems), umso schneller können wir Fehler einkreisen und beheben.
Bitte postet auch die Ausgabe von
iob diagmit rein.Wir wünschen allen viel Spaß beim Testen und vielen Dank für Eure Unterstützung!
Moritz
@foxriver76 Upgrade von js-controller 6 auf 7 lief auf meinem Testsystem ohne Probleme :clap:
iob diag vom aktualisierten Testsystem
-
Guten Morgen, bisher keine Auffälligkeiten auf dem Testsystem. Installation lief unauffällig durch.
Grüße und ein schönes Wochenende!
-
@sigi234 said in js-controller Lucy (v7.0.0) Alpha Test:
Hallo, also der Windows Installer installiert diese Version nicht?
Doch, natürlich. Im Expertenmodus das Häkchen bei "Nutze Alpha-Repo (@next)" setzen und es wird aktuell Version 7.0.0-alpha.0-20240926-91f9b082f angeboten. Warum fragst du?
@gaspode sagte in js-controller Lucy (v7.0.0) Alpha Test:
Im Expertenmodus das Häkchen bei "Nutze Alpha-Repo (@next)" setzen
ich lese immer Häkchen, kann aber keines finden. Installer Version 3.3.0, gerade runtergeladen. Auch ein Expertenmodus wird da nicht angeboten.
iobroker läuft unter Docker auf QNAP TS-451+
SkriptRecovery: https://forum.iobroker.net/post/930558 -
@gaspode sagte in js-controller Lucy (v7.0.0) Alpha Test:
Im Expertenmodus das Häkchen bei "Nutze Alpha-Repo (@next)" setzen
ich lese immer Häkchen, kann aber keines finden. Installer Version 3.3.0, gerade runtergeladen. Auch ein Expertenmodus wird da nicht angeboten.
@fastfoot sagte in js-controller Lucy (v7.0.0) Alpha Test:
@gaspode sagte in js-controller Lucy (v7.0.0) Alpha Test:
Im Expertenmodus das Häkchen bei "Nutze Alpha-Repo (@next)" setzen
ich lese immer Häkchen, kann aber keines finden. Installer Version 3.3.0, gerade runtergeladen. Auch ein Expertenmodus wird da nicht angeboten.
Hast du ihn auch aktiviert? Soweit ich noch weiß auf das Logo doppelt klicken.
-
@fastfoot sagte in js-controller Lucy (v7.0.0) Alpha Test:
@gaspode sagte in js-controller Lucy (v7.0.0) Alpha Test:
Im Expertenmodus das Häkchen bei "Nutze Alpha-Repo (@next)" setzen
ich lese immer Häkchen, kann aber keines finden. Installer Version 3.3.0, gerade runtergeladen. Auch ein Expertenmodus wird da nicht angeboten.
Hast du ihn auch aktiviert? Soweit ich noch weiß auf das Logo doppelt klicken.
@sigi234 sagte in js-controller Lucy (v7.0.0) Alpha Test:
Hast du ihn auch aktiviert? Soweit ich noch weiß auf das Logo doppelt klicken.
Hatte ich natürlich nicht, habe einfach den Installer runtergeladen und ausgeführt. Doku, falls vorhanden, wo? Ist also nicht benutzerfreundlich bzw. wenn man Expertendinge machen will kann man ja auch fragen. Ist echt gut versteckt, aber Danke, hattest Recht und jetzt gibts auch den Haken mit dem Alphamodus :-)
iobroker läuft unter Docker auf QNAP TS-451+
SkriptRecovery: https://forum.iobroker.net/post/930558 -
Kaum hat man den Haken gefunden und aktiviert, schon hat man den neuesten Controller und auch die Daten vom vorherigen System wurden alle übernommen. Wollte schon immer mal den neuen Installer probieren, ist wirklich klasse. Das vorige System hatte ich noch mit npx installiert
-
@sigi234 sagte in js-controller Lucy (v7.0.0) Alpha Test:
Hast du ihn auch aktiviert? Soweit ich noch weiß auf das Logo doppelt klicken.
Hatte ich natürlich nicht, habe einfach den Installer runtergeladen und ausgeführt. Doku, falls vorhanden, wo? Ist also nicht benutzerfreundlich bzw. wenn man Expertendinge machen will kann man ja auch fragen. Ist echt gut versteckt, aber Danke, hattest Recht und jetzt gibts auch den Haken mit dem Alphamodus :-)
@fastfoot sagte in js-controller Lucy (v7.0.0) Alpha Test:
@sigi234 sagte in js-controller Lucy (v7.0.0) Alpha Test:
Hast du ihn auch aktiviert? Soweit ich noch weiß auf das Logo doppelt klicken.
Hatte ich natürlich nicht, habe einfach den Installer runtergeladen und ausgeführt. Doku, falls vorhanden, wo? Ist also nicht benutzerfreundlich bzw. wenn man Expertendinge machen will kann man ja auch fragen. Ist echt gut versteckt, aber Danke, hattest Recht und jetzt gibts auch den Haken mit dem Alphamodus :-)
https://github.com/ioBroker/ioBroker.build/blob/master/Windows-Installer.md
Sollte man in der Doku erwähnen.
Bitte benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
Immer Daten sichern! -
@fastfoot sagte in js-controller Lucy (v7.0.0) Alpha Test:
@sigi234 sagte in js-controller Lucy (v7.0.0) Alpha Test:
Hast du ihn auch aktiviert? Soweit ich noch weiß auf das Logo doppelt klicken.
Hatte ich natürlich nicht, habe einfach den Installer runtergeladen und ausgeführt. Doku, falls vorhanden, wo? Ist also nicht benutzerfreundlich bzw. wenn man Expertendinge machen will kann man ja auch fragen. Ist echt gut versteckt, aber Danke, hattest Recht und jetzt gibts auch den Haken mit dem Alphamodus :-)
https://github.com/ioBroker/ioBroker.build/blob/master/Windows-Installer.md
Sollte man in der Doku erwähnen.
@sigi234 said in js-controller Lucy (v7.0.0) Alpha Test:
Sollte man in der Doku erwähnen.
Ja, allerdings war das ja ursprünglich als verstecktes Feature gedacht. Da wir jetzt offen dazu aufrufen, den Installer für Alpha-Versionen zu nutzen, sollte das wohl besser auch in die Doku. :D
Ich kümmere mich drum.Edit: https://github.com/ioBroker/ioBroker.docs/pull/550
@fastfoot said in js-controller Lucy (v7.0.0) Alpha Test:
Kaum hat man den Haken gefunden und aktiviert, schon hat man den neuesten Controller und auch die Daten vom vorherigen System wurden alle übernommen. Wollte schon immer mal den neuen Installer probieren, ist wirklich klasse. Das vorige System hatte ich noch mit npx installiert
Danke für das Feedback, freut mich, dass alles geklappt hat.
-
@peterfido sicher dass das mit Controller 6 nicht so war? Ich denke das ist eher Admin oder Adapter
Ein Scan alle im repository gelisteten Adapter hat ergeben, dass folgende Adapter potenziell inkompatibel sein können und auf Grund der (an sich internen) Änderungen am Plug In System Störungen auslösen können:
- wegen dependency auf @iobroker/sentry-plugin:
ioBroker.dysonairpurifier
ioBroker.mielecloudservice
ioBroker.robonect
ioBroker.resol
ioBroker.wireguard- wegen expliziter dependency auf iobroker.js-controller:
ioBroker.hausbus_de
- wegen expliziter dependency auf dev-server (*)
ioBroker.sonnen-charger
ioBroker.vis-map(*) die falsche dependency zu dev-server wird wahrscheinlich keine Probleme bereiten außer dass unnötiger Code installiert wird.
Support us
786
Online32.4k
Benutzer81.5k
Themen1.3m
Beiträge