Skip to content
  • Home
  • Aktuell
  • Tags
  • 0 Ungelesen 0
  • Kategorien
  • Unreplied
  • Beliebt
  • GitHub
  • Docu
  • Hilfe
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Standard: (Kein Skin)
  • Kein Skin
Einklappen
ioBroker Logo

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. Error/Bug
  4. gelöst Adapter RPI2.0 nicht mehr drauf und sehr langam

NEWS

  • Monatsrückblick Januar/Februar 2026 ist online!
    BluefoxB
    Bluefox
    17
    1
    473

  • Jahresrückblick 2025 – unser neuer Blogbeitrag ist online! ✨
    BluefoxB
    Bluefox
    17
    1
    5.2k

  • Neuer Blogbeitrag: Monatsrückblick - Dezember 2025 🎄
    BluefoxB
    Bluefox
    13
    1
    1.4k

gelöst Adapter RPI2.0 nicht mehr drauf und sehr langam

Geplant Angeheftet Gesperrt Verschoben Error/Bug
21 Beiträge 4 Kommentatoren 763 Aufrufe 3 Watching
  • Älteste zuerst
  • Neuste zuerst
  • Meiste Stimmen
Antworten
  • In einem neuen Thema antworten
Anmelden zum Antworten
Dieses Thema wurde gelöscht. Nur Nutzer mit entsprechenden Rechten können es sehen.
  • ? Ein ehemaliger Benutzer
    Systemdata Bitte Ausfüllen
    Hardwaresystem: ;Pi3
    Arbeitsspeicher: 1GB
    Festplattenart: SD-Karte/SSD/HDD
    Betriebssystem: Ubuntu/Windows/Mac
    Node-Version: 14.18.3
    Nodejs-Version: 14.18.3
    NPM-Version: 6.14.15
    Installationsart: Skript/Manuell
    Image genutzt: Ja/Nein
    Ort/Name der Imagedatei: Link

    Laut Fehlermeldung ist GPIO is not initialized!

    bekam auch immer eine Fehlermeldung

    Error: GET-UNSUPPORTED for namespace meta.: Data=["meta.states.protocolVersion"]

    jetzt geht gar nicht mehr und deinstallieren des Adapters ging auch nicht
    Hoffe ihr könnt mir helfen.

    02-11 20:18:00.548  - info: host.iobroker instance system.adapter.luxtronik2.0 scheduled normal terminated and will be restarted on schedule.
    2022-02-11 20:18:00.550  - info: host.iobroker Restart adapter system.adapter.luxtronik2.0 because enabled
    2022-02-11 20:18:01.567  - info: host.iobroker instance system.adapter.luxtronik2.0 started with pid 23565
    2022-02-11 20:18:02.043  - info: luxtronik2.0 (23565) starting. Version 0.3.0 in /opt/iobroker/node_modules/iobroker.luxtronik2, node: v14.18.3, js-controller: 3.3.22
    2022-02-11 20:18:02.106  - info: luxtronik2.0 (23565) Connecting to ws://192.168.178.5:8214
    2022-02-11 20:18:02.539  - info: luxtronik2.0 (23565) Connecting to 192.168.178.5:8889
    2022-02-11 20:18:22.544  - error: luxtronik2.0 (23565) Didn't receive data from WebSocket after 3 retries, restarting adapter
    2022-02-11 20:18:22.555  - warn: luxtronik2.0 (23565) Restart initiated
    2022-02-11 20:18:22.560  - info: luxtronik2.0 (23565) terminating
    2022-02-11 20:18:22.561  - info: luxtronik2.0 (23565) Terminated (NO_ERROR): Without reason
    2022-02-11 20:18:23.093  - info: host.iobroker instance system.adapter.luxtronik2.0 terminated with code 0 (NO_ERROR)
    2022-02-11 20:18:23.095  - info: host.iobroker Restart adapter system.adapter.luxtronik2.0 because enabled
    2022-02-11 20:18:24.110  - info: host.iobroker instance system.adapter.luxtronik2.0 started with pid 23580
    2022-02-11 20:18:24.608  - info: luxtronik2.0 (23580) starting. Version 0.3.0 in /opt/iobroker/node_modules/iobroker.luxtronik2, node: v14.18.3, js-controller: 3.3.22
    2022-02-11 20:18:24.669  - info: luxtronik2.0 (23580) Connecting to ws://192.168.178.5:8214
    2022-02-11 20:18:24.901  - info: luxtronik2.0 (23580) Connecting to 192.168.178.5:8889
    2022-02-11 20:18:33.225  - info: javascript.0 (391) Stop script script.js.common.Klingel.Klingel_Taster
    2022-02-11 20:18:33.227  - info: javascript.0 (391) Start javascript script.js.common.Klingel.Klingel_Taster
    2022-02-11 20:18:33.229  - info: javascript.0 (391) script.js.common.Klingel.Klingel_Taster: registered 1 subscription and 0 schedules
    2022-02-11 20:18:44.904  - error: luxtronik2.0 (23580) Didn't receive data from WebSocket after 3 retries, restarting adapter
    2022-02-11 20:18:44.917  - warn: luxtronik2.0 (23580) Restart initiated
    2022-02-11 20:18:44.919  - info: luxtronik2.0 (23580) terminating
    2022-02-11 20:18:44.920  - info: luxtronik2.0 (23580) Terminated (NO_ERROR): Without reason
    2022-02-11 20:18:45.453  - info: host.iobroker instance system.adapter.luxtronik2.0 terminated with code 0 (NO_ERROR)
    2022-02-11 20:18:45.454  - info: host.iobroker Restart adapter system.adapter.luxtronik2.0 because enabled
    2022-02-11 20:18:46.472  - info: host.iobroker instance system.adapter.luxtronik2.0 started with pid 23595
    2022-02-11 20:18:47.059  - info: luxtronik2.0 (23595) starting. Version 0.3.0 in /opt/iobroker/node_modules/iobroker.luxtronik2, node: v14.18.3, js-controller: 3.3.22
    2022-02-11 20:18:47.128  - info: luxtronik2.0 (23595) Connecting to ws://192.168.178.5:8214
    2022-02-11 20:18:47.361  - info: luxtronik2.0 (23595) Connecting to 192.168.178.5:8889
    2022-02-11 20:18:55.189  - info: admin.1 (376) Unsubscribe from all states, except system's, because over 3 seconds the number of events is over 200 (in last second 0)
    2022-02-11 20:19:00.005  - info: luxtronik2.0 (23595) Scheduled restart.
    2022-02-11 20:19:00.263  - info: luxtronik2.0 (23595) terminating
    2022-02-11 20:19:00.264  - info: luxtronik2.0 (23595) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
    2022-02-11 20:19:01.981  - info: host.iobroker instance system.adapter.luxtronik2.0 scheduled normal terminated and will be restarted on schedule.
    2022-02-11 20:19:01.983  - info: host.iobroker Restart adapter system.adapter.luxtronik2.0 because enabled
    2022-02-11 20:19:04.176  - info: host.iobroker instance system.adapter.luxtronik2.0 started with pid 23610
    2022-02-11 20:19:39.797  - info: luxtronik2.0 (23610) starting. Version 0.3.0 in /opt/iobroker/node_modules/iobroker.luxtronik2, node: v14.18.3, js-controller: 3.3.22
    2022-02-11 20:19:43.114  - info: luxtronik2.0 (23610) Connecting to ws://192.168.178.5:8214
    2022-02-11 20:19:43.349  - info: judoisoft.0 (646) State value to set for "judoisoft.0.ServiceDays" has to be type "number" but received type "string" 
    2022-02-11 20:19:44.227  - info: judoisoft.0 (646) State value to set for "judoisoft.0.Maintenance" has to be type "number" but received type "string" 
    2022-02-11 20:19:56.106  - info: admin.1 (376) Subscribe on all states again
    2022-02-11 20:20:00.006  - info: luxtronik2.0 (23610) Scheduled restart.
    2022-02-11 20:20:01.507  - info: luxtronik2.0 (23610) terminating with timeout
    2022-02-11 20:20:01.507  - info: luxtronik2.0 (23610) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
    2022-02-11 20:20:01.777  - info: luxtronik2.0 (23610) terminating
    2022-02-11 20:20:01.928  - info: luxtronik2.0 (23610) terminating
    2022-02-11 20:20:04.302  - error: luxtronik2.0 (23610) 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().
    2022-02-11 20:20:04.302  - error: luxtronik2.0 (23610) unhandled promise rejection: DB closed
    2022-02-11 20:20:04.304  - error: luxtronik2.0 (23610) Error: DB closed
        at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:183:25)
        at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:150:20)
        at Object.onceWrapper (events.js:520:26)
        at Socket.emit (events.js:400:28)
        at Socket.emit (domain.js:475:12)
        at TCP.<anonymous> (net.js:686:12)
    2022-02-11 20:20:04.304  - error: luxtronik2.0 (23610) DB closed
    2022-02-11 20:20:06.975  - info: host.iobroker instance system.adapter.luxtronik2.0 scheduled normal terminated and will be restarted on schedule.
    2022-02-11 20:20:06.976  - info: host.iobroker Restart adapter system.adapter.luxtronik2.0 because enabled
    2022-02-11 20:20:13.009  - info: host.iobroker instance system.adapter.luxtronik2.0 started with pid 23625
    2022-02-11 20:20:17.590  - warn: luxtronik2.0 (23625) slow connection to states DB. Still waiting ...
    2022-02-11 20:21:08.824  - info: luxtronik2.0 (23625) starting. Version 0.3.0 in /opt/iobroker/node_modules/iobroker.luxtronik2, node: v14.18.3, js-controller: 3.3.22
    2022-02-11 20:21:14.944  - info: luxtronik2.0 (23625) Connecting to ws://192.168.178.5:8214
    2022-02-11 20:21:50.260  - info: admin.1 (376) Unsubscribe from all states, except system's, because over 3 seconds the number of events is over 200 (in last second 0)
    2022-02-11 20:22:00.005  - info: luxtronik2.0 (23625) Scheduled restart.
    2022-02-11 20:22:01.508  - info: luxtronik2.0 (23625) terminating with timeout
    2022-02-11 20:22:01.508  - info: luxtronik2.0 (23625) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
    2022-02-11 20:22:02.081  - info: luxtronik2.0 (23625) terminating
    2022-02-11 20:22:02.390  - info: luxtronik2.0 (23625) terminating
    2022-02-11 20:22:04.187  - error: luxtronik2.0 (23625) 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().
    2022-02-11 20:22:04.188  - error: luxtronik2.0 (23625) unhandled promise rejection: DB closed
    2022-02-11 20:22:04.191  - error: luxtronik2.0 (23625) Error: DB closed
        at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:183:25)
        at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:150:20)
        at Object.onceWrapper (events.js:520:26)
        at Socket.emit (events.js:400:28)
        at Socket.emit (domain.js:475:12)
        at TCP.<anonymous> (net.js:686:12)
    2022-02-11 20:22:04.191  - error: luxtronik2.0 (23625) DB closed
    2022-02-11 20:22:04.756  - warn: host.iobroker-Server Objects 192.168.178.11:36846 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets"]
    2022-02-11 20:22:05.326  - warn: host.iobroker-Server Objects 192.168.178.11:36846 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.protocolVersion"]
    2022-02-11 20:22:06.408  - warn: host.iobroker-Server Objects 192.168.178.11:36848 Error from InMemDB: Error: PSUBSCRIBE-UNSUPPORTED for namespace cfg.: Data=["meta.*"]
    2022-02-11 20:22:07.901  - info: host.iobroker instance system.adapter.luxtronik2.0 scheduled normal terminated and will be restarted on schedule.
    2022-02-11 20:22:07.902  - info: host.iobroker Restart adapter system.adapter.luxtronik2.0 because enabled
    2022-02-11 20:22:11.857  - warn: host.iobroker-Server States 192.168.178.11:47346 Error from InMemDB: Error: GET-UNSUPPORTED for namespace meta.: Data=["meta.states.protocolVersion"]
    2022-02-11 20:22:13.810  - info: host.iobroker instance system.adapter.luxtronik2.0 started with pid 23642
    2022-02-11 20:22:14.345  - warn: host.iobroker-Server States 192.168.178.11:47348 Error from InMemDB: Error: PSUBSCRIBE-UNSUPPORTED for namespace meta.: Data=["meta.*"]
    2022-02-11 20:22:18.325  - warn: luxtronik2.0 (23642) slow connection to states DB. Still waiting ...
    2022-02-11 20:22:45.513  - info: knx.0 (676) State value to set for "knx.0.1_Zentral_und_Sicherheit.1_Wetterstation.Datum_Uhrzeit" has to be type "number" but received type "object" 
    2022-02-11 20:22:51.181  - info: admin.1 (376) Subscribe on all states again
    2022-02-11 20:23:02.393  - info: luxtronik2.0 (23642) starting. Version 0.3.0 in /opt/iobroker/node_modules/iobroker.luxtronik2, node: v14.18.3, js-controller: 3.3.22
    2022-02-11 20:23:08.280  - info: luxtronik2.0 (23642) Connecting to ws://192.168.178.5:8214
    2022-02-11 20:24:00.005  - info: luxtronik2.0 (23642) Scheduled restart.
    2022-02-11 20:24:01.505  - info: luxtronik2.0 (23642) terminating with timeout
    2022-02-11 20:24:01.506  - info: luxtronik2.0 (23642) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
    2022-02-11 20:24:02.275  - info: luxtronik2.0 (23642) terminating
    2022-02-11 20:24:02.458  - info: luxtronik2.0 (23642) terminating
    2022-02-11 20:24:04.725  - error: luxtronik2.0 (23642) 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().
    2022-02-11 20:24:04.726  - error: luxtronik2.0 (23642) unhandled promise rejection: Connection is closed.
    2022-02-11 20:24:04.728  - error: luxtronik2.0 (23642) Error: Connection is closed.
        at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:183:25)
        at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:150:20)
        at Object.onceWrapper (events.js:520:26)
        at Socket.emit (events.js:400:28)
        at Socket.emit (domain.js:475:12)
        at TCP.<anonymous> (net.js:686:12)
    2022-02-11 20:24:04.728  - error: luxtronik2.0 (23642) Connection is closed.
    2022-02-11 20:24:08.775  - info: host.iobroker instance system.adapter.luxtronik2.0 scheduled normal terminated and will be restarted on schedule.
    2022-02-11 20:24:08.776  - info: host.iobroker Restart adapter system.adapter.luxtronik2.0 because enabled
    2022-02-11 20:24:16.082  - info: host.iobroker instance system.adapter.luxtronik2.0 started with pid 23659
    2022-02-11 20:24:21.500  - warn: luxtronik2.0 (23659) slow connection to states DB. Still waiting ...
    2022-02-11 20:24:52.895  - info: judoisoft.0 (646) State value to set for "judoisoft.0.ServiceDays" has to be type "number" but received type "string" 
    2022-02-11 20:24:54.612  - info: judoisoft.0 (646) State value to set for "judoisoft.0.Maintenance" has to be type "number" but received type "string" 
    2022-02-11 20:25:15.871  - info: luxtronik2.0 (23659) starting. Version 0.3.0 in /opt/iobroker/node_modules/iobroker.luxtronik2, node: v14.18.3, js-controller: 3.3.22
    2022-02-11 20:25:20.699  - info: luxtronik2.0 (23659) Connecting to ws://192.168.178.5:8214
    2022-02-11 20:25:52.285  - warn: host.iobroker-Server Objects 192.168.178.11:36858 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets"]
    2022-02-11 20:25:52.844  - warn: host.iobroker-Server Objects 192.168.178.11:36858 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.protocolVersion"]
    2022-02-11 20:25:53.597  - warn: host.iobroker-Server Objects 192.168.178.11:36860 Error from InMemDB: Error: PSUBSCRIBE-UNSUPPORTED for namespace cfg.: Data=["meta.*"]
    2022-02-11 20:25:58.463  - warn: host.iobroker-Server States 192.168.178.11:47358 Error from InMemDB: Error: GET-UNSUPPORTED for namespace meta.: Data=["meta.states.protocolVersion"]
    2022-02-11 20:26:00.004  - info: luxtronik2.0 (23659) Scheduled restart.
    2022-02-11 20:26:00.430  - warn: host.iobroker-Server States 192.168.178.11:47360 Error from InMemDB: Error: PSUBSCRIBE-UNSUPPORTED for namespace meta.: Data=["meta.*"]
    2022-02-11 20:26:01.505  - info: luxtronik2.0 (23659) terminating with timeout
    2022-02-11 20:26:01.506  - info: luxtronik2.0 (23659) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
    2022-02-11 20:26:02.172  - info: luxtronik2.0 (23659) terminating
    2022-02-11 20:26:02.340  - info: luxtronik2.0 (23659) terminating
    2022-02-11 20:26:04.218  - error: luxtronik2.0 (23659) 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().
    2022-02-11 20:26:04.218  - error: luxtronik2.0 (23659) unhandled promise rejection: Connection is closed.
    2022-02-11 20:26:04.220  - error: luxtronik2.0 (23659) Error: Connection is closed.
        at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:183:25)
        at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:150:20)
        at Object.onceWrapper (events.js:520:26)
        at Socket.emit (events.js:400:28)
        at Socket.emit (domain.js:475:12)
        at TCP.<anonymous> (net.js:686:12)
    2022-02-11 20:26:04.220  - error: luxtronik2.0 (23659) Connection is closed.
    2022-02-11 20:26:07.638  - info: host.iobroker instance system.adapter.luxtronik2.0 scheduled normal terminated and will be restarted on schedule.
    2022-02-11 20:26:07.638  - info: host.iobroker Restart adapter system.adapter.luxtronik2.0 because enabled
    2022-02-11 20:26:14.817  - info: host.iobroker instance system.adapter.luxtronik2.0 started with pid 23674
    2022-02-11 20:26:20.096  - warn: luxtronik2.0 (23674) slow connection to states DB. Still waiting ...
    2022-02-11 20:27:17.635  - info: luxtronik2.0 (23674) starting. Version 0.3.0 in /opt/iobroker/node_modules/iobroker.luxtronik2, node: v14.18.3, js-controller: 3.3.22
    2022-02-11 20:27:23.621  - info: luxtronik2.0 (23674) Connecting to ws://192.168.178.5:8214
    2022-02-11 20:28:00.007  - info: luxtronik2.0 (23674) Scheduled restart.
    2022-02-11 20:28:01.509  - info: luxtronik2.0 (23674) terminating with timeout
    2022-02-11 20:28:01.510  - info: luxtronik2.0 (23674) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
    2022-02-11 20:28:02.432  - info: luxtronik2.0 (23674) terminating
    2022-02-11 20:28:03.015  - info: luxtronik2.0 (23674) terminating
    2022-02-11 20:28:05.038  - error: luxtronik2.0 (23674) 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().
    2022-02-11 20:28:05.038  - error: luxtronik2.0 (23674) unhandled promise rejection: Connection is closed.
    2022-02-11 20:28:05.040  - error: luxtronik2.0 (23674) Error: Connection is closed.
        at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:183:25)
        at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:150:20)
        at Object.onceWrapper (events.js:520:26)
        at Socket.emit (events.js:400:28)
        at Socket.emit (domain.js:475:12)
        at TCP.<anonymous> (net.js:686:12)
    2022-02-11 20:28:05.041  - error: luxtronik2.0 (23674) Connection is closed.
    2022-02-11 20:28:09.824  - info: host.iobroker instance system.adapter.luxtronik2.0 scheduled normal terminated and will be restarted on schedule.
    2022-02-11 20:28:09.825  - info: host.iobroker Restart adapter system.adapter.luxtronik2.0 because enabled
    2022-02-11 20:28:17.679  - info: host.iobroker instance system.adapter.luxtronik2.0 started with pid 23694
    2022-02-11 20:28:23.231  - warn: luxtronik2.0 (23694) slow connection to states DB. Still waiting ...
    2022-02-11 20:29:19.425  - info: luxtronik2.0 (23694) starting. Version 0.3.0 in /opt/iobroker/node_modules/iobroker.luxtronik2, node: v14.18.3, js-controller: 3.3.22
    2022-02-11 20:29:24.152  - info: luxtronik2.0 (23694) Connecting to ws://192.168.178.5:8214
    2022-02-11 20:29:26.859  - warn: host.iobroker-Server Objects 192.168.178.11:36872 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets"]
    2022-02-11 20:29:27.206  - warn: host.iobroker-Server Objects 192.168.178.11:36872 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.protocolVersion"]
    2022-02-11 20:29:28.260  - warn: host.iobroker-Server Objects 192.168.178.11:36874 Error from InMemDB: Error: PSUBSCRIBE-UNSUPPORTED for namespace cfg.: Data=["meta.*"]
    2022-02-11 20:29:33.143  - warn: host.iobroker-Server States 192.168.178.11:47372 Error from InMemDB: Error: GET-UNSUPPORTED for namespace meta.: Data=["meta.states.protocolVersion"]
    2022-02-11 20:29:35.110  - warn: host.iobroker-Server States 192.168.178.11:47374 Error from InMemDB: Error: PSUBSCRIBE-UNSUPPORTED for namespace meta.: Data=["meta.*"]
    2022-02-11 20:30:00.007  - info: luxtronik2.0 (23694) Scheduled restart.
    2022-02-11 20:30:01.508  - info: luxtronik2.0 (23694) terminating with timeout
    2022-02-11 20:30:01.509  - info: luxtronik2.0 (23694) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
    2022-02-11 20:30:01.858  - info: luxtronik2.0 (23694) terminating
    2022-02-11 20:30:02.010  - info: luxtronik2.0 (23694) terminating
    2022-02-11 20:30:02.687  - info: host.iobroker instance system.adapter.dwd.0 started with pid 23709
    2022-02-11 20:30:04.109  - info: judoisoft.0 (646) State value to set for "judoisoft.0.ServiceDays" has to be type "number" but received type "string" 
    2022-02-11 20:30:04.143  - error: luxtronik2.0 (23694) 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().
    2022-02-11 20:30:04.144  - error: luxtronik2.0 (23694) unhandled promise rejection: DB closed
    2022-02-11 20:30:04.145  - error: luxtronik2.0 (23694) Error: DB closed
        at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:183:25)
        at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:150:20)
        at Object.onceWrapper (events.js:520:26)
        at Socket.emit (events.js:400:28)
        at Socket.emit (domain.js:475:12)
        at TCP.<anonymous> (net.js:686:12)
    2022-02-11 20:30:04.146  - error: luxtronik2.0 (23694) DB closed
    2022-02-11 20:30:05.147  - info: judoisoft.0 (646) State value to set for "judoisoft.0.Maintenance" has to be type "number" but received type "string" 
    2022-02-11 20:30:07.308  - warn: host.iobroker-Server Objects 192.168.178.11:36884 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets"]
    2022-02-11 20:30:07.969  - info: host.iobroker instance system.adapter.luxtronik2.0 scheduled normal terminated and will be restarted on schedule.
    2022-02-11 20:30:07.969  - info: host.iobroker Restart adapter system.adapter.luxtronik2.0 because enabled
    2022-02-11 20:30:08.012  - warn: dwd.0 (23709) slow connection to states DB. Still waiting ...
    2022-02-11 20:30:08.075  - warn: host.iobroker-Server Objects 192.168.178.11:36884 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.protocolVersion"]
    2022-02-11 20:30:09.003  - warn: host.iobroker-Server Objects 192.168.178.11:36886 Error from InMemDB: Error: PSUBSCRIBE-UNSUPPORTED for namespace cfg.: Data=["meta.*"]
    2022-02-11 20:30:14.877  - info: host.iobroker instance system.adapter.luxtronik2.0 started with pid 23768
    2022-02-11 20:30:14.877  - warn: host.iobroker-Server States 192.168.178.11:47384 Error from InMemDB: Error: GET-UNSUPPORTED for namespace meta.: Data=["meta.states.protocolVersion"]
    2022-02-11 20:30:16.948  - warn: host.iobroker-Server States 192.168.178.11:47386 Error from InMemDB: Error: PSUBSCRIBE-UNSUPPORTED for namespace meta.: Data=["meta.*"]
    2022-02-11 20:30:20.177  - warn: luxtronik2.0 (23768) slow connection to states DB. Still waiting ...
    2022-02-11 20:31:13.285  - info: luxtronik2.0 (23768) starting. Version 0.3.0 in /opt/iobroker/node_modules/iobroker.luxtronik2, node: v14.18.3, js-controller: 3.3.22
    2022-02-11 20:31:20.139  - info: luxtronik2.0 (23768) Connecting to ws://192.168.178.5:8214
    2022-02-11 20:31:29.510  - info: dwd.0 (23709) starting. Version 2.7.7 in /opt/iobroker/node_modules/iobroker.dwd, node: v14.18.3, js-controller: 3.3.22
    2022-02-11 20:32:00.006  - info: luxtronik2.0 (23768) Scheduled restart.
    2022-02-11 20:32:01.508  - info: luxtronik2.0 (23768) terminating with timeout
    2022-02-11 20:32:01.508  - info: luxtronik2.0 (23768) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
    2022-02-11 20:32:02.172  - info: luxtronik2.0 (23768) terminating
    2022-02-11 20:32:02.429  - info: luxtronik2.0 (23768) terminating
    2022-02-11 20:32:05.128  - error: luxtronik2.0 (23768) 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().
    2022-02-11 20:32:05.129  - error: luxtronik2.0 (23768) unhandled promise rejection: DB closed
    2022-02-11 20:32:05.131  - error: luxtronik2.0 (23768) Error: DB closed
        at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:183:25)
        at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:150:20)
        at Object.onceWrapper (events.js:520:26)
        at Socket.emit (events.js:400:28)
        at Socket.emit (domain.js:475:12)
        at TCP.<anonymous> (net.js:686:12)
    2022-02-11 20:32:05.131  - error: luxtronik2.0 (23768) DB closed
    2022-02-11 20:32:09.270  - info: host.iobroker instance system.adapter.luxtronik2.0 scheduled normal terminated and will be restarted on schedule.
    2022-02-11 20:32:09.272  - info: host.iobroker Restart adapter system.adapter.luxtronik2.0 because enabled
    2022-02-11 20:32:17.119  - info: host.iobroker instance system.adapter.luxtronik2.0 started with pid 23787
    2022-02-11 20:32:23.253  - warn: luxtronik2.0 (23787) slow connection to states DB. Still waiting ...
    2022-02-11 20:32:45.953  - info: knx.0 (676) State value to set for "knx.0.1_Zentral_und_Sicherheit.1_Wetterstation.Datum_Uhrzeit" has to be type "number" but received type "object" 
    2022-02-11 20:32:53.637  - warn: host.iobroker-Server Objects 192.168.178.11:35018 Error from InMemDB: Error: CONFIG-UNSUPPORTED for ["set","notify-keyspace-events","Exe"]
    2022-02-11 20:32:54.230  - warn: host.iobroker-Server Objects 192.168.178.11:35018 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets"]
    2022-02-11 20:32:54.822  - warn: host.iobroker-Server Objects 192.168.178.11:35018 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.protocolVersion"]
    2022-02-11 20:32:55.058  - warn: host.iobroker-Server Objects 192.168.178.11:35020 Error from InMemDB: Error: PSUBSCRIBE-UNSUPPORTED for namespace cfg.: Data=["meta.*"]
    2022-02-11 20:32:57.752  - warn: host.iobroker-Server Objects 192.168.178.11:35020 Error from InMemDB: Error: subscribe NOT SUPPORTED
    2022-02-11 20:32:59.641  - info: dwd.0 (23709) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
    2022-02-11 20:33:00.900  - warn: host.iobroker-Server States 192.168.178.11:56370 Error from InMemDB: Error: GET-UNSUPPORTED for namespace meta.: Data=["meta.states.protocolVersion"]
    2022-02-11 20:33:02.742  - warn: host.iobroker-Server States 192.168.178.11:56372 Error from InMemDB: Error: PSUBSCRIBE-UNSUPPORTED for namespace meta.: Data=["meta.*"]
    2022-02-11 20:33:03.458  - info: host.iobroker instance system.adapter.dwd.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
    2022-02-11 20:33:12.284  - info: luxtronik2.0 (23787) starting. Version 0.3.0 in /opt/iobroker/node_modules/iobroker.luxtronik2, node: v14.18.3, js-controller: 3.3.22
    2022-02-11 20:33:17.242  - info: luxtronik2.0 (23787) Connecting to ws://192.168.178.5:8214
    2022-02-11 20:33:24.818  - warn: host.iobroker-Server Objects 192.168.178.11:35026 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets"]
    2022-02-11 20:33:25.585  - warn: host.iobroker-Server Objects 192.168.178.11:35026 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.protocolVersion"]
    2022-02-11 20:33:26.351  - warn: host.iobroker-Server Objects 192.168.178.11:35028 Error from InMemDB: Error: PSUBSCRIBE-UNSUPPORTED for namespace cfg.: Data=["meta.*"]
    2022-02-11 20:33:27.701  - warn: host.iobroker-Server Objects 192.168.178.11:35032 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets"]
    2022-02-11 20:33:28.348  - warn: host.iobroker-Server Objects 192.168.178.11:35032 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.protocolVersion"]
    2022-02-11 20:33:28.799  - warn: host.iobroker-Server Objects 192.168.178.11:35034 Error from InMemDB: Error: PSUBSCRIBE-UNSUPPORTED for namespace cfg.: Data=["meta.*"]
    2022-02-11 20:33:31.349  - warn: host.iobroker-Server States 192.168.178.11:56386 Error from InMemDB: Error: GET-UNSUPPORTED for namespace meta.: Data=["meta.states.protocolVersion"]
    2022-02-11 20:33:33.245  - warn: host.iobroker-Server States 192.168.178.11:56388 Error from InMemDB: Error: PSUBSCRIBE-UNSUPPORTED for namespace meta.: Data=["meta.*"]
    2022-02-11 20:33:33.959  - warn: host.iobroker-Server States 192.168.178.11:56392 Error from InMemDB: Error: GET-UNSUPPORTED for namespace meta.: Data=["meta.states.protocolVersion"]
    2022-02-11 20:33:35.787  - warn: host.iobroker-Server States 192.168.178.11:56394 Error from InMemDB: Error: PSUBSCRIBE-UNSUPPORTED for namespace meta.: Data=["meta.*"]
    2022-02-11 20:34:00.006  - info: luxtronik2.0 (23787) Scheduled restart.
    2022-02-11 20:34:01.508  - info: luxtronik2.0 (23787) terminating with timeout
    2022-02-11 20:34:01.509  - info: luxtronik2.0 (23787) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
    2022-02-11 20:34:01.703  - info: luxtronik2.0 (23787) terminating
    2022-02-11 20:34:01.703  - info: luxtronik2.0 (23787) terminating
    2022-02-11 20:34:04.269  - error: luxtronik2.0 (23787) 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().
    2022-02-11 20:34:04.269  - error: luxtronik2.0 (23787) unhandled promise rejection: Connection is closed.
    2022-02-11 20:34:04.271  - error: luxtronik2.0 (23787) Error: Connection is closed.
        at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:183:25)
        at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:150:20)
        at Object.onceWrapper (events.js:520:26)
        at Socket.emit (events.js:400:28)
        at Socket.emit (domain.js:475:12)
        at TCP.<anonymous> (net.js:686:12)
    2022-02-11 20:34:04.271  - error: luxtronik2.0 (23787) Connection is closed.
    2022-02-11 20:34:07.066  - info: host.iobroker instance system.adapter.luxtronik2.0 scheduled normal terminated and will be restarted on schedule.
    2022-02-11 20:34:07.068  - info: host.iobroker Restart adapter system.adapter.luxtronik2.0 because enabled
    2022-02-11 20:34:12.497  - info: host.iobroker instance system.adapter.luxtronik2.0 started with pid 23804
    2022-02-11 20:34:17.372  - warn: luxtronik2.0 (23804) slow connection to states DB. Still waiting ...
    2022-02-11 20:34:34.815  - warn: host.iobroker-Server Objects 192.168.178.11:35050 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets"]
    2022-02-11 20:34:35.132  - warn: host.iobroker-Server Objects 192.168.178.11:35050 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.protocolVersion"]
    2022-02-11 20:34:35.910  - warn: host.iobroker-Server Objects 192.168.178.11:35052 Error from InMemDB: Error: PSUBSCRIBE-UNSUPPORTED for namespace cfg.: Data=["meta.*"]
    2022-02-11 20:34:38.788  - warn: host.iobroker-Server Objects 192.168.178.11:35056 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets"]
    2022-02-11 20:34:59.017  - info: luxtronik2.0 (23804) starting. Version 0.3.0 in /opt/iobroker/node_modules/iobroker.luxtronik2, node: v14.18.3, js-controller: 3.3.22
    2022-02-11 20:35:00.013  - info: luxtronik2.0 (23804) Scheduled restart.
    2022-02-11 20:35:01.515  - info: luxtronik2.0 (23804) terminating with timeout
    2022-02-11 20:35:01.516  - info: luxtronik2.0 (23804) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
    2022-02-11 20:35:01.765  - info: luxtronik2.0 (23804) terminating
    2022-02-11 20:35:01.928  - info: luxtronik2.0 (23804) terminating
    2022-02-11 20:35:03.660  - info: luxtronik2.0 (23804) Connecting to ws://192.168.178.5:8214
    2022-02-11 20:35:04.200  - error: luxtronik2.0 (23804) 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().
    2022-02-11 20:35:04.200  - error: luxtronik2.0 (23804) unhandled promise rejection: DB closed
    2022-02-11 20:35:04.201  - error: luxtronik2.0 (23804) Error: DB closed
        at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:183:25)
        at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:150:20)
        at Object.onceWrapper (events.js:520:26)
        at Socket.emit (events.js:400:28)
        at Socket.emit (domain.js:475:12)
        at TCP.<anonymous> (net.js:686:12)
    2022-02-11 20:35:04.202  - error: luxtronik2.0 (23804) DB closed
    2022-02-11 20:35:06.823  - info: host.iobroker instance system.adapter.luxtronik2.0 scheduled normal terminated and will be restarted on schedule.
    2022-02-11 20:35:06.824  - info: host.iobroker Restart adapter system.adapter.luxtronik2.0 because enabled
    2022-02-11 20:35:11.843  - info: host.iobroker instance system.adapter.luxtronik2.0 started with pid 23819
    2022-02-11 20:35:14.129  - info: judoisoft.0 (646) State value to set for "judoisoft.0.ServiceDays" has to be type "number" but received type "string" 
    2022-02-11 20:35:14.954  - info: judoisoft.0 (646) State value to set for "judoisoft.0.Maintenance" has to be type "number" but received type "string" 
    2022-02-11 20:35:16.184  - warn: luxtronik2.0 (23819) slow connection to states DB. Still waiting ...
    2022-02-11 20:35:53.101  - warn: host.iobroker-Server Objects 192.168.178.11:35074 Error from InMemDB: Error: CONFIG-UNSUPPORTED for ["set","notify-keyspace-events","Exe"]
    2022-02-11 20:35:53.732  - warn: host.iobroker-Server Objects 192.168.178.11:35074 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets"]
    2022-02-11 20:35:53.951  - warn: host.iobroker-Server Objects 192.168.178.11:35074 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.protocolVersion"]
    2022-02-11 20:35:54.589  - warn: host.iobroker-Server Objects 192.168.178.11:35076 Error from InMemDB: Error: PSUBSCRIBE-UNSUPPORTED for namespace cfg.: Data=["meta.*"]
    2022-02-11 20:35:55.490  - info: luxtronik2.0 (23819) starting. Version 0.3.0 in /opt/iobroker/node_modules/iobroker.luxtronik2, node: v14.18.3, js-controller: 3.3.22
    2022-02-11 20:35:56.371  - warn: host.iobroker-Server Objects 192.168.178.11:35076 Error from InMemDB: Error: subscribe NOT SUPPORTED
    2022-02-11 20:35:59.882  - info: luxtronik2.0 (23819) Connecting to ws://192.168.178.5:8214
    2022-02-11 20:36:00.007  - info: luxtronik2.0 (23819) Scheduled restart.
    2022-02-11 20:36:00.428  - warn: host.iobroker-Server States 192.168.178.11:56426 Error from InMemDB: Error: GET-UNSUPPORTED for namespace meta.: Data=["meta.states.protocolVersion"]
    2022-02-11 20:36:01.508  - info: luxtronik2.0 (23819) terminating with timeout
    2022-02-11 20:36:01.508  - info: luxtronik2.0 (23819) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
    2022-02-11 20:36:01.664  - info: luxtronik2.0 (23819) terminating
    2022-02-11 20:36:02.334  - warn: host.iobroker-Server States 192.168.178.11:56428 Error from InMemDB: Error: PSUBSCRIBE-UNSUPPORTED for namespace meta.: Data=["meta.*"]
    2022-02-11 20:36:02.364  - info: luxtronik2.0 (23819) terminating
    2022-02-11 20:36:04.367  - error: luxtronik2.0 (23819) 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().
    2022-02-11 20:36:04.368  - error: luxtronik2.0 (23819) unhandled promise rejection: DB closed
    2022-02-11 20:36:04.369  - error: luxtronik2.0 (23819) Error: DB closed
        at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:183:25)
        at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:150:20)
        at Object.onceWrapper (events.js:520:26)
        at Socket.emit (events.js:400:28)
        at Socket.emit (domain.js:475:12)
        at TCP.<anonymous> (net.js:686:12)
    2022-02-11 20:36:04.369  - error: luxtronik2.0 (23819) DB closed
    2022-02-11 20:36:08.713  - info: host.iobroker instance system.adapter.luxtronik2.0 scheduled normal terminated and will be restarted on schedule.
    2022-02-11 20:36:08.713  - info: host.iobroker Restart adapter system.adapter.luxtronik2.0 because enabled
    2022-02-11 20:36:09.649  - info: admin.1 (376) Unsubscribe from all states, except system's, because over 3 seconds the number of events is over 200 (in last second 0)
    2022-02-11 20:36:14.208  - info: host.iobroker instance system.adapter.luxtronik2.0 started with pid 23834
    2022-02-11 20:36:18.962  - warn: luxtronik2.0 (23834) slow connection to states DB. Still waiting ...
    2022-02-11 20:36:24.568  - warn: host.iobroker-Server Objects 192.168.178.11:35082 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets"]
    2022-02-11 20:36:25.203  - warn: host.iobroker-Server Objects 192.168.178.11:35082 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.protocolVersion"]
    2022-02-11 20:36:25.670  - warn: host.iobroker-Server Objects 192.168.178.11:35084 Error from InMemDB: Error: PSUBSCRIBE-UNSUPPORTED for namespace cfg.: Data=["meta.*"]
    2022-02-11 20:36:28.350  - warn: host.iobroker-Server Objects 192.168.178.11:35088 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets"]
    2022-02-11 20:36:29.179  - warn: host.iobroker-Server Objects 192.168.178.11:35088 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.protocolVersion"]
    2022-02-11 20:36:29.904  - warn: host.iobroker-Server Objects 192.168.178.11:35090 Error from InMemDB: Error: PSUBSCRIBE-UNSUPPORTED for namespace cfg.: Data=["meta.*"]
    2022-02-11 20:36:30.261  - warn: host.iobroker-Server Objects 192.168.178.11:35094 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets"]
    2022-02-11 20:36:30.957  - warn: host.iobroker-Server Objects 192.168.178.11:35094 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.protocolVersion"]
    2022-02-11 20:36:31.303  - warn: host.iobroker-Server Objects 192.168.178.11:35096 Error from InMemDB: Error: PSUBSCRIBE-UNSUPPORTED for namespace cfg.: Data=["meta.*"]
    2022-02-11 20:36:35.005  - warn: host.iobroker-Server States 192.168.178.11:56448 Error from InMemDB: Error: GET-UNSUPPORTED for namespace meta.: Data=["meta.states.protocolVersion"]
    2022-02-11 20:36:35.519  - warn: host.iobroker-Server States 192.168.178.11:56450 Error from InMemDB: Error: GET-UNSUPPORTED for namespace meta.: Data=["meta.states.protocolVersion"]
    2022-02-11 20:36:35.889  - warn: host.iobroker-Server Objects 192.168.178.11:35104 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets"]
    2022-02-11 20:36:36.428  - warn: host.iobroker-Server Objects 192.168.178.11:35104 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.protocolVersion"]
    2022-02-11 20:36:36.844  - warn: host.iobroker-Server States 192.168.178.11:56454 Error from InMemDB: Error: PSUBSCRIBE-UNSUPPORTED for namespace meta.: Data=["meta.*"]
    2022-02-11 20:36:36.997  - warn: host.iobroker-Server States 192.168.178.11:56458 Error from InMemDB: Error: PSUBSCRIBE-UNSUPPORTED for namespace meta.: Data=["meta.*"]
    2022-02-11 20:36:36.998  - warn: host.iobroker-Server Objects 192.168.178.11:35114 Error from InMemDB: Error: PSUBSCRIBE-UNSUPPORTED for namespace cfg.: Data=["meta.*"]
    2022-02-11 20:36:41.696  - warn: host.iobroker-Server States 192.168.178.11:56466 Error from InMemDB: Error: GET-UNSUPPORTED for namespace meta.: Data=["meta.states.protocolVersion"]
    2022-02-11 20:36:43.560  - warn: host.iobroker-Server States 192.168.178.11:56468 Error from InMemDB: Error: PSUBSCRIBE-UNSUPPORTED for namespace meta.: Data=["meta.*"]
    2022-02-11 20:36:45.520  - warn: host.iobroker-Server Objects 192.168.178.11:35124 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets"]
    2022-02-11 20:36:46.397  - warn: host.iobroker-Server Objects 192.168.178.11:35124 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.protocolVersion"]
    2022-02-11 20:36:47.089  - warn: host.iobroker-Server Objects 192.168.178.11:35126 Error from InMemDB: Error: PSUBSCRIBE-UNSUPPORTED for namespace cfg.: Data=["meta.*"]
    2022-02-11 20:36:49.133  - warn: host.iobroker-Server Objects 192.168.178.11:35130 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets"]
    2022-02-11 20:36:49.335  - warn: host.iobroker-Server Objects 192.168.178.11:35130 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.protocolVersion"]
    2022-02-11 20:36:50.146  - warn: host.iobroker-Server Objects 192.168.178.11:35132 Error from InMemDB: Error: PSUBSCRIBE-UNSUPPORTED for namespace cfg.: Data=["meta.*"]
    2022-02-11 20:36:50.361  - warn: host.iobroker-Server Objects 192.168.178.11:35136 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets"]
    2022-02-11 20:36:51.244  - warn: host.iobroker-Server Objects 192.168.178.11:35136 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.protocolVersion"]
    2022-02-11 20:36:51.845  - warn: host.iobroker-Server Objects 192.168.178.11:35140 Error from InMemDB: Error: PSUBSCRIBE-UNSUPPORTED for namespace cfg.: Data=["meta.*"]
    2022-02-11 20:36:52.132  - warn: host.iobroker-Server States 192.168.178.11:56486 Error from InMemDB: Error: GET-UNSUPPORTED for namespace meta.: Data=["meta.states.protocolVersion"]
    2022-02-11 20:36:54.117  - warn: host.iobroker-Server States 192.168.178.11:56492 Error from InMemDB: Error: PSUBSCRIBE-UNSUPPORTED for namespace meta.: Data=["meta.*"]
    2022-02-11 20:36:55.002  - warn: host.iobroker-Server States 192.168.178.11:56496 Error from InMemDB: Error: GET-UNSUPPORTED for namespace meta.: Data=["meta.states.protocolVersion"]
    2022-02-11 20:36:57.075  - warn: host.iobroker-Server States 192.168.178.11:56498 Error from InMemDB: Error: PSUBSCRIBE-UNSUPPORTED for namespace meta.: Data=["meta.*"]
    2022-02-11 20:36:57.284  - warn: host.iobroker-Server States 192.168.178.11:56502 Error from InMemDB: Error: GET-UNSUPPORTED for namespace meta.: Data=["meta.states.protocolVersion"]
    2022-02-11 20:36:59.158  - warn: host.iobroker-Server States 192.168.178.11:56504 Error from InMemDB: Error: PSUBSCRIBE-UNSUPPORTED for namespace meta.: Data=["meta.*"]
    2022-02-11 20:37:01.207  - info: luxtronik2.0 (23834) starting. Version 0.3.0 in /opt/iobroker/node_modules/iobroker.luxtronik2, node: v14.18.3, js-controller: 3.3.22
    2022-02-11 20:37:05.497  - info: luxtronik2.0 (23834) Connecting to ws://192.168.178.5:8214
    2022-02-11 20:37:10.571  - info: admin.1 (376) Subscribe on all states again
    2022-02-11 20:37:42.960  - warn: host.iobroker-Server Objects 192.168.178.11:35160 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets"]
    2022-02-11 20:37:43.072  - warn: host.iobroker-Server Objects 192.168.178.11:35160 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.protocolVersion"]
    2022-02-11 20:37:44.487  - warn: host.iobroker-Server Objects 192.168.178.11:35162 Error from InMemDB: Error: PSUBSCRIBE-UNSUPPORTED for namespace cfg.: Data=["meta.*"]
    2022-02-11 20:37:50.709  - warn: host.iobroker-Server States 192.168.178.11:56514 Error from InMemDB: Error: GET-UNSUPPORTED for namespace meta.: Data=["meta.states.protocolVersion"]
    2022-02-11 20:37:53.849  - warn: host.iobroker-Server States 192.168.178.11:56516 Error from InMemDB: Error: PSUBSCRIBE-UNSUPPORTED for namespace meta.: Data=["meta.*"]
    2022-02-11 20:38:00.004  - info: luxtronik2.0 (23834) Scheduled restart.
    2022-02-11 20:38:01.509  - info: luxtronik2.0 (23834) terminating with timeout
    2022-02-11 20:38:01.509  - info: luxtronik2.0 (23834) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
    2022-02-11 20:38:02.344  - info: luxtronik2.0 (23834) terminating
    2022-02-11 20:38:02.782  - info: luxtronik2.0 (23834) terminating
    2022-02-11 20:38:05.089  - error: luxtronik2.0 (23834) 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().
    2022-02-11 20:38:05.089  - error: luxtronik2.0 (23834) unhandled promise rejection: DB closed
    2022-02-11 20:38:05.090  - error: luxtronik2.0 (23834) Error: DB closed
        at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:183:25)
        at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:150:20)
        at Object.onceWrapper (events.js:520:26)
        at Socket.emit (events.js:400:28)
        at Socket.emit (domain.js:475:12)
        at TCP.<anonymous> (net.js:686:12)
    2022-02-11 20:38:05.091  - error: luxtronik2.0 (23834) DB closed
    2022-02-11 20:38:09.274  - info: host.iobroker instance system.adapter.luxtronik2.0 scheduled normal terminated and will be restarted on schedule.
    2022-02-11 20:38:09.275  - info: host.iobroker Restart adapter system.adapter.luxtronik2.0 because enabled
    2022-02-11 20:38:15.273  - info: host.iobroker instance system.adapter.luxtronik2.0 started with pid 23851
    2022-02-11 20:38:20.857  - warn: luxtronik2.0 (23851) slow connection to states DB. Still waiting ...
    2022-02-11 20:38:42.844  - info: host.iobroker stopInstance system.adapter.luxtronik2.0 (force=false, process=true)
    2022-02-11 20:38:44.304  - info: luxtronik2.0 (23851) Got terminate signal TERMINATE_YOURSELF
    2022-02-11 20:38:44.304  - info: luxtronik2.0 (23851) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
    2022-02-11 20:38:45.778  - info: host.iobroker stopInstance system.adapter.luxtronik2.0 send kill signal
    2022-02-11 20:38:47.050  - info: host.iobroker stopInstance system.adapter.luxtronik2.0 killing pid 23851
    2022-02-11 20:38:47.059  - info: luxtronik2.0 (23851) starting. Version 0.3.0 in /opt/iobroker/node_modules/iobroker.luxtronik2, node: v14.18.3, js-controller: 3.3.22
    2022-02-11 20:38:47.111  - warn: luxtronik2.0 (23851) get state error: Connection is closed.
    2022-02-11 20:38:47.111  - warn: luxtronik2.0 (23851) get state error: Connection is closed.
    2022-02-11 20:38:47.112  - warn: luxtronik2.0 (23851) get state error: Connection is closed.
    2022-02-11 20:38:47.112  - warn: luxtronik2.0 (23851) get state error: Connection is closed.
    2022-02-11 20:38:47.112  - warn: luxtronik2.0 (23851) get state error: Connection is closed.
    2022-02-11 20:38:47.112  - warn: luxtronik2.0 (23851) get state error: Connection is closed.
    2022-02-11 20:38:47.112  - warn: luxtronik2.0 (23851) get state error: Connection is closed.
    2022-02-11 20:38:47.112  - warn: luxtronik2.0 (23851) get state error: Connection is closed.
    2022-02-11 20:38:47.112  - warn: luxtronik2.0 (23851) get state error: Connection is closed.
    2022-02-11 20:38:47.114  - error: luxtronik2.0 (23851) Cannot find view "system" for search "folder" : Connection is closed.
    2022-02-11 20:38:47.115  - warn: luxtronik2.0 (23851) Could not perform strict object check of state luxtronik2.0.info.connection: Connection is closed.
    2022-02-11 20:38:47.115  - warn: luxtronik2.0 (23851) get state error: Connection is closed.
    2022-02-11 20:38:47.115  - error: luxtronik2.0 (23851) Cannot find view "system" for search "device" : Connection is closed.
    2022-02-11 20:38:47.117  - error: luxtronik2.0 (23851) Cannot find view "system" for search "channel" : Connection is closed.
    2022-02-11 20:38:47.117  - error: luxtronik2.0 (23851) Cannot find view "system" for search "state" : Connection is closed.
    2022-02-11 20:38:47.118  - warn: luxtronik2.0 (23851) get state error: Connection is closed.
    2022-02-11 20:38:47.118  - warn: luxtronik2.0 (23851) get state error: Connection is closed.
    2022-02-11 20:38:47.121  - info: luxtronik2.0 (23851) Connecting to ws://192.168.178.5:8214
    2022-02-11 20:38:47.122  - error: luxtronik2.0 (23851) 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().
    2022-02-11 20:38:47.123  - error: luxtronik2.0 (23851) unhandled promise rejection: Connection is closed.
    2022-02-11 20:38:47.123  - error: luxtronik2.0 (23851) Error: Connection is closed.
        at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:628:24)
        at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
        at ObjectsInRedisClient._getObject (/opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:2286:37)
        at Immediate.<anonymous> (/opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:2332:33)
        at processImmediate (internal/timers.js:466:21)
    2022-02-11 20:38:47.123  - error: luxtronik2.0 (23851) Connection is closed.
    2022-02-11 20:38:51.751  - info: host.iobroker instance system.adapter.luxtronik2.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
    2022-02-11 20:38:57.374  - info: host.iobroker instance system.adapter.luxtronik2.0 started with pid 23866
    2022-02-11 20:39:03.177  - warn: luxtronik2.0 (23866) slow connection to states DB. Still waiting ...
    2022-02-11 20:39:10.499  - warn: host.iobroker-Server Objects 192.168.178.11:35172 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets"]
    2022-02-11 20:39:10.499  - warn: host.iobroker-Server States 192.168.178.11:56522 Error from InMemDB: Error: GET-UNSUPPORTED for namespace meta.: Data=["meta.states.protocolVersion"]
    2022-02-11 20:39:10.701  - warn: host.iobroker-Server Objects 192.168.178.11:35172 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.protocolVersion"]
    2022-02-11 20:40:01.820  - info: luxtronik2.0 (23866) starting. Version 0.3.0 in /opt/iobroker/node_modules/iobroker.luxtronik2, node: v14.18.3, js-controller: 3.3.22
    2022-02-11 20:40:06.759  - info: luxtronik2.0 (23866) Connecting to ws://192.168.178.5:8214
    2022-02-11 20:40:22.755  - info: admin.1 (376) Unsubscribe from all states, except system's, because over 3 seconds the number of events is over 200 (in last second 0)
    2022-02-11 20:40:23.439  - info: judoisoft.0 (646) State value to set for "judoisoft.0.ServiceDays" has to be type "number" but received type "string" 
    2022-02-11 20:40:24.580  - info: judoisoft.0 (646) State value to set for "judoisoft.0.Maintenance" has to be type "number" but received type "string" 
    2022-02-11 20:40:31.100  - warn: host.iobroker-Server Objects 192.168.178.11:35178 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets"]
    2022-02-11 20:40:32.062  - warn: host.iobroker-Server Objects 192.168.178.11:35178 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.protocolVersion"]
    2022-02-11 20:40:32.889  - warn: host.iobroker-Server Objects 192.168.178.11:35180 Error from InMemDB: Error: PSUBSCRIBE-UNSUPPORTED for namespace cfg.: Data=["meta.*"]
    2022-02-11 20:40:38.131  - warn: host.iobroker-Server States 192.168.178.11:56532 Error from InMemDB: Error: GET-UNSUPPORTED for namespace meta.: Data=["meta.states.protocolVersion"]
    2022-02-11 20:40:40.160  - warn: host.iobroker-Server States 192.168.178.11:56534 Error from InMemDB: Error: PSUBSCRIBE-UNSUPPORTED for namespace meta.: Data=["meta.*"]
    2022-02-11 20:40:43.887  - warn: host.iobroker-Server Objects 192.168.178.11:35190 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets"]
    2022-02-11 20:40:44.187  - warn: host.iobroker-Server States 192.168.178.11:56540 Error from InMemDB: Error: GET-UNSUPPORTED for namespace meta.: Data=["meta.states.protocolVersion"]
    2022-02-11 20:40:44.780  - warn: host.iobroker-Server Objects 192.168.178.11:35190 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.protocolVersion"]
    2022-02-11 20:40:46.150  - warn: host.iobroker-Server States 192.168.178.11:56542 Error from InMemDB: Error: PSUBSCRIBE-UNSUPPORTED for namespace meta.: Data=["meta.*"]
    2022-02-11 20:41:00.004  - info: luxtronik2.0 (23866) Scheduled restart.
    2022-02-11 20:41:01.504  - info: luxtronik2.0 (23866) terminating with timeout
    2022-02-11 20:41:01.505  - info: luxtronik2.0 (23866) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
    2022-02-11 20:41:01.825  - info: luxtronik2.0 (23866) terminating
    2022-02-11 20:41:02.457  - info: luxtronik2.0 (23866) terminating
    2022-02-11 20:41:03.974  - error: luxtronik2.0 (23866) 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().
    2022-02-11 20:41:03.974  - error: luxtronik2.0 (23866) unhandled promise rejection: DB closed
    2022-02-11 20:41:03.976  - error: luxtronik2.0 (23866) Error: DB closed
        at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:183:25)
        at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:150:20)
        at Object.onceWrapper (events.js:520:26)
        at Socket.emit (events.js:400:28)
        at Socket.emit (domain.js:475:12)
        at TCP.<anonymous> (net.js:686:12)
    2022-02-11 20:41:03.976  - error: luxtronik2.0 (23866) DB closed
    2022-02-11 20:41:06.934  - info: host.iobroker instance system.adapter.luxtronik2.0 scheduled normal terminated and will be restarted on schedule.
    2022-02-11 20:41:06.935  - info: host.iobroker Restart adapter system.adapter.luxtronik2.0 because enabled
    2022-02-11 20:41:12.345  - info: host.iobroker instance system.adapter.luxtronik2.0 started with pid 23881
    2022-02-11 20:41:17.269  - warn: luxtronik2.0 (23881) slow connection to states DB. Still waiting ...
    2022-02-11 20:41:23.681  - info: admin.1 (376) Subscribe on all states again
    2022-02-11 20:41:57.787  - info: luxtronik2.0 (23881) starting. Version 0.3.0 in /opt/iobroker/node_modules/iobroker.luxtronik2, node: v14.18.3, js-controller: 3.3.22
    2022-02-11 20:42:00.004  - info: luxtronik2.0 (23881) Scheduled restart.
    2022-02-11 20:42:01.507  - info: luxtronik2.0 (23881) terminating with timeout
    2022-02-11 20:42:01.508  - info: luxtronik2.0 (23881) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
    2022-02-11 20:42:01.599  - info: luxtronik2.0 (23881) terminating
    2022-02-11 20:42:01.666  - info: luxtronik2.0 (23881) terminating
    2022-02-11 20:42:02.209  - info: luxtronik2.0 (23881) Connecting to ws://192.168.178.5:8214
    2022-02-11 20:42:03.536  - error: luxtronik2.0 (23881) 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().
    2022-02-11 20:42:03.536  - error: luxtronik2.0 (23881) unhandled promise rejection: DB closed
    2022-02-11 20:42:03.537  - error: luxtronik2.0 (23881) Error: DB closed
        at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:183:25)
        at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:150:20)
        at Object.onceWrapper (events.js:520:26)
        at Socket.emit (events.js:400:28)
        at Socket.emit (domain.js:475:12)
        at TCP.<anonymous> (net.js:686:12)
    2022-02-11 20:42:03.538  - error: luxtronik2.0 (23881) DB closed
    2022-02-11 20:42:06.380  - info: host.iobroker instance system.adapter.luxtronik2.0 scheduled normal terminated and will be restarted on schedule.
    2022-02-11 20:42:06.381  - info: host.iobroker Restart adapter system.adapter.luxtronik2.0 because enabled
    2022-02-11 20:42:11.991  - info: host.iobroker instance system.adapter.luxtronik2.0 started with pid 23896
    2022-02-11 20:42:17.076  - warn: luxtronik2.0 (23896) slow connection to states DB. Still waiting ...
    2022-02-11 20:42:46.083  - info: knx.0 (676) State value to set for "knx.0.1_Zentral_und_Sicherheit.1_Wetterstation.Datum_Uhrzeit" has to be type "number" but received type "object" 
    2022-02-11 20:43:03.957  - info: luxtronik2.0 (23896) starting. Version 0.3.0 in /opt/iobroker/node_modules/iobroker.luxtronik2, node: v14.18.3, js-controller: 3.3.22
    2022-02-11 20:43:08.091  - info: luxtronik2.0 (23896) Connecting to ws://192.168.178.5:8214
    2022-02-11 20:43:46.736  - warn: host.iobroker-Server Objects 192.168.178.11:35196 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets"]
    2022-02-11 20:43:46.737  - warn: host.iobroker-Server States 192.168.178.11:56546 Error from InMemDB: Error: GET-UNSUPPORTED for namespace meta.: Data=["meta.states.protocolVersion"]
    2022-02-11 20:43:47.838  - warn: host.iobroker-Server Objects 192.168.178.11:35196 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.protocolVersion"]
    2022-02-11 20:43:48.727  - warn: host.iobroker-Server States 192.168.178.11:56548 Error from InMemDB: Error: PSUBSCRIBE-UNSUPPORTED for namespace meta.: Data=["meta.*"]
    2022-02-11 20:44:00.004  - info: luxtronik2.0 (23896) Scheduled restart.
    2022-02-11 20:44:01.507  - info: luxtronik2.0 (23896) terminating with timeout
    2022-02-11 20:44:01.507  - info: luxtronik2.0 (23896) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
    2022-02-11 20:44:01.923  - info: luxtronik2.0 (23896) terminating
    2022-02-11 20:44:01.923  - info: luxtronik2.0 (23896) terminating
    2022-02-11 20:44:03.936  - error: luxtronik2.0 (23896) 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().
    2022-02-11 20:44:03.936  - error: luxtronik2.0 (23896) unhandled promise rejection: DB closed
    2022-02-11 20:44:03.938  - error: luxtronik2.0 (23896) Error: DB closed
        at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:183:25)
        at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:150:20)
        at Object.onceWrapper (events.js:520:26)
        at Socket.emit (events.js:400:28)
        at Socket.emit (domain.js:475:12)
        at TCP.<anonymous> (net.js:686:12)
    2022-02-11 20:44:03.938  - error: luxtronik2.0 (23896) DB closed
    2022-02-11 20:44:06.766  - info: host.iobroker instance system.adapter.luxtronik2.0 scheduled normal terminated and will be restarted on schedule.
    2022-02-11 20:44:06.766  - info: host.iobroker Restart adapter system.adapter.luxtronik2.0 because enabled
    2022-02-11 20:44:12.412  - info: host.iobroker instance system.adapter.luxtronik2.0 started with pid 23913
    2022-02-11 20:44:17.235  - warn: luxtronik2.0 (23913) slow connection to states DB. Still waiting ...
    2022-02-11 20:45:00.814  - info: luxtronik2.0 (23913) starting. Version 0.3.0 in /opt/iobroker/node_modules/iobroker.luxtronik2, node: v14.18.3, js-controller: 3.3.22
    2022-02-11 20:45:02.244  - info: host.iobroker instance system.adapter.dwd.0 started with pid 23928
    2022-02-11 20:45:05.063  - info: luxtronik2.0 (23913) Connecting to ws://192.168.178.5:8214
    2022-02-11 20:45:07.267  - warn: dwd.0 (23928) slow connection to states DB. Still waiting ...
    2022-02-11 20:45:32.850  - info: judoisoft.0 (646) State value to set for "judoisoft.0.ServiceDays" has to be type "number" but received type "string" 
    2022-02-11 20:45:33.791  - info: judoisoft.0 (646) State value to set for "judoisoft.0.Maintenance" has to be type "number" but received type "string" 
    2022-02-11 20:46:00.003  - info: luxtronik2.0 (23913) Scheduled restart.
    2022-02-11 20:46:01.506  - info: luxtronik2.0 (23913) terminating with timeout
    2022-02-11 20:46:01.507  - info: luxtronik2.0 (23913) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
    2022-02-11 20:46:01.720  - info: luxtronik2.0 (23913) terminating
    2022-02-11 20:46:01.734  - info: luxtronik2.0 (23913) terminating
    2022-02-11 20:46:03.785  - error: luxtronik2.0 (23913) 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().
    2022-02-11 20:46:03.785  - error: luxtronik2.0 (23913) unhandled promise rejection: DB closed
    2022-02-11 20:46:03.788  - error: luxtronik2.0 (23913) Error: DB closed
        at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:183:25)
        at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:150:20)
        at Object.onceWrapper (events.js:520:26)
        at Socket.emit (events.js:400:28)
        at Socket.emit (domain.js:475:12)
        at TCP.<anonymous> (net.js:686:12)
    2022-02-11 20:46:03.788  - error: luxtronik2.0 (23913) DB closed
    2022-02-11 20:46:06.623  - info: host.iobroker instance system.adapter.luxtronik2.0 scheduled normal terminated and will be restarted on schedule.
    2022-02-11 20:46:06.624  - info: host.iobroker Restart adapter system.adapter.luxtronik2.0 because enabled
    2022-02-11 20:46:07.598  - info: dwd.0 (23928) starting. Version 2.7.7 in /opt/iobroker/node_modules/iobroker.dwd, node: v14.18.3, js-controller: 3.3.22
    2022-02-11 20:46:12.043  - info: host.iobroker instance system.adapter.luxtronik2.0 started with pid 23943
    2022-02-11 20:46:17.189  - warn: luxtronik2.0 (23943) slow connection to states DB. Still waiting ...
    2022-02-11 20:47:04.458  - info: luxtronik2.0 (23943) starting. Version 0.3.0 in /opt/iobroker/node_modules/iobroker.luxtronik2, node: v14.18.3, js-controller: 3.3.22
    2022-02-11 20:47:08.899  - info: luxtronik2.0 (23943) Connecting to ws://192.168.178.5:8214
    2022-02-11 20:47:14.194  - warn: host.iobroker-Server Objects 192.168.178.11:35202 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets"]
    2022-02-11 20:47:14.195  - warn: host.iobroker-Server States 192.168.178.11:56552 Error from InMemDB: Error: GET-UNSUPPORTED for namespace meta.: Data=["meta.states.protocolVersion"]
    2022-02-11 20:47:15.289  - warn: host.iobroker-Server Objects 192.168.178.11:35202 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.protocolVersion"]
    2022-02-11 20:47:16.652  - warn: host.iobroker-Server States 192.168.178.11:56554 Error from InMemDB: Error: PSUBSCRIBE-UNSUPPORTED for namespace meta.: Data=["meta.*"]
    2022-02-11 20:47:19.642  - info: dwd.0 (23928) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
    2022-02-11 20:47:24.012  - info: host.iobroker instance system.adapter.dwd.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
    2022-02-11 20:48:00.004  - info: luxtronik2.0 (23943) Scheduled restart.
    2022-02-11 20:48:01.506  - info: luxtronik2.0 (23943) terminating with timeout
    2022-02-11 20:48:01.506  - info: luxtronik2.0 (23943) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
    2022-02-11 20:48:01.945  - info: luxtronik2.0 (23943) terminating
    2022-02-11 20:48:02.148  - info: luxtronik2.0 (23943) terminating
    2022-02-11 20:48:02.825  - warn: host.iobroker-Server Objects 192.168.178.11:35208 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets"]
    2022-02-11 20:48:03.500  - warn: host.iobroker-Server Objects 192.168.178.11:35208 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.protocolVersion"]
    2022-02-11 20:48:04.122  - warn: host.iobroker-Server Objects 192.168.178.11:35210 Error from InMemDB: Error: PSUBSCRIBE-UNSUPPORTED for namespace cfg.: Data=["meta.*"]
    2022-02-11 20:48:04.151  - error: luxtronik2.0 (23943) 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().
    2022-02-11 20:48:04.151  - error: luxtronik2.0 (23943) unhandled promise rejection: DB closed
    2022-02-11 20:48:04.153  - error: luxtronik2.0 (23943) Error: DB closed
        at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:183:25)
        at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:150:20)
        at Object.onceWrapper (events.js:520:26)
        at Socket.emit (events.js:400:28)
        at Socket.emit (domain.js:475:12)
        at TCP.<anonymous> (net.js:686:12)
    2022-02-11 20:48:04.153  - error: luxtronik2.0 (23943) DB closed
    2022-02-11 20:48:08.063  - info: host.iobroker instance system.adapter.luxtronik2.0 scheduled normal terminated and will be restarted on schedule.
    2022-02-11 20:48:08.064  - info: host.iobroker Restart adapter system.adapter.luxtronik2.0 because enabled
    2022-02-11 20:48:09.914  - warn: host.iobroker-Server States 192.168.178.11:56562 Error from InMemDB: Error: GET-UNSUPPORTED for namespace meta.: Data=["meta.states.protocolVersion"]
    2022-02-11 20:48:12.144  - warn: host.iobroker-Server States 192.168.178.11:56564 Error from InMemDB: Error: PSUBSCRIBE-UNSUPPORTED for namespace meta.: Data=["meta.*"]
    2022-02-11 20:48:14.145  - info: host.iobroker instance system.adapter.luxtronik2.0 started with pid 23960
    2022-02-11 20:48:18.588  - warn: host.iobroker-Server Objects 192.168.178.11:35220 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets"]
    2022-02-11 20:48:18.787  - warn: host.iobroker-Server Objects 192.168.178.11:35220 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.protocolVersion"]
    2022-02-11 20:48:19.756  - warn: luxtronik2.0 (23960) slow connection to states DB. Still waiting ...
    2022-02-11 20:48:20.243  - warn: host.iobroker-Server Objects 192.168.178.11:35222 Error from InMemDB: Error: PSUBSCRIBE-UNSUPPORTED for namespace cfg.: Data=["meta.*"]
    2022-02-11 20:48:25.741  - warn: host.iobroker-Server Objects 192.168.178.11:35226 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets"]
    2022-02-11 20:48:25.741  - warn: host.iobroker-Server States 192.168.178.11:56576 Error from InMemDB: Error: GET-UNSUPPORTED for namespace meta.: Data=["meta.states.protocolVersion"]
    2022-02-11 20:48:26.349  - warn: host.iobroker-Server Objects 192.168.178.11:35226 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.protocolVersion"]
    2022-02-11 20:48:27.147  - warn: host.iobroker-Server Objects 192.168.178.11:35230 Error from InMemDB: Error: PSUBSCRIBE-UNSUPPORTED for namespace cfg.: Data=["meta.*"]
    2022-02-11 20:48:27.780  - warn: host.iobroker-Server States 192.168.178.11:56582 Error from InMemDB: Error: PSUBSCRIBE-UNSUPPORTED for namespace meta.: Data=["meta.*"]
    2022-02-11 20:48:33.246  - warn: host.iobroker-Server States 192.168.178.11:56586 Error from InMemDB: Error: GET-UNSUPPORTED for namespace meta.: Data=["meta.states.protocolVersion"]
    2022-02-11 20:48:35.190  - warn: host.iobroker-Server States 192.168.178.11:56588 Error from InMemDB: Error: PSUBSCRIBE-UNSUPPORTED for namespace meta.: Data=["meta.*"]
    2022-02-11 20:49:09.953  - info: luxtronik2.0 (23960) starting. Version 0.3.0 in /opt/iobroker/node_modules/iobroker.luxtronik2, node: v14.18.3, js-controller: 3.3.22
    2022-02-11 20:49:15.092  - info: luxtronik2.0 (23960) Connecting to ws://192.168.178.5:8214
    2022-02-11 20:50:00.006  - info: luxtronik2.0 (23960) Scheduled restart.
    2022-02-11 20:50:01.507  - info: luxtronik2.0 (23960) terminating with timeout
    2022-02-11 20:50:01.508  - info: luxtronik2.0 (23960) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
    2022-02-11 20:50:02.290  - info: luxtronik2.0 (23960) terminating
    2022-02-11 20:50:02.292  - info: luxtronik2.0 (23960) terminating
    2022-02-11 20:50:04.482  - error: luxtronik2.0 (23960) 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().
    2022-02-11 20:50:04.482  - error: luxtronik2.0 (23960) unhandled promise rejection: DB closed
    2022-02-11 20:50:04.484  - error: luxtronik2.0 (23960) Error: DB closed
        at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:183:25)
        at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:150:20)
        at Object.onceWrapper (events.js:520:26)
        at Socket.emit (events.js:400:28)
        at Socket.emit (domain.js:475:12)
        at TCP.<anonymous> (net.js:686:12)
    2022-02-11 20:50:04.484  - error: luxtronik2.0 (23960) DB closed
    2022-02-11 20:50:08.480  - info: host.iobroker instance system.adapter.luxtronik2.0 scheduled normal terminated and will be restarted on schedule.
    2022-02-11 20:50:08.481  - info: host.iobroker Restart adapter system.adapter.luxtronik2.0 because enabled
    2022-02-11 20:50:16.261  - info: host.iobroker instance system.adapter.luxtronik2.0 started with pid 23975
    2022-02-11 20:50:22.013  - warn: luxtronik2.0 (23975) slow connection to states DB. Still waiting ...
    2022-02-11 20:50:41.359  - info: judoisoft.0 (646) State value to set for "judoisoft.0.ServiceDays" has to be type "number" but received type "string" 
    2022-02-11 20:50:43.167  - info: judoisoft.0 (646) State value to set for "judoisoft.0.Maintenance" has to be type "number" but received type "string" 
    2022-02-11 20:51:22.805  - info: luxtronik2.0 (23975) starting. Version 0.3.0 in /opt/iobroker/node_modules/iobroker.luxtronik2, node: v14.18.3, js-controller: 3.3.22
    2022-02-11 20:51:29.151  - info: luxtronik2.0 (23975) Connecting to ws://192.168.178.5:8214
    2022-02-11 20:52:00.004  - info: luxtronik2.0 (23975) Scheduled restart.
    2022-02-11 20:52:01.505  - info: luxtronik2.0 (23975) terminating with timeout
    2022-02-11 20:52:01.505  - info: luxtronik2.0 (23975) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
    2022-02-11 20:52:01.796  - info: luxtronik2.0 (23975) terminating
    2022-02-11 20:52:01.797  - info: luxtronik2.0 (23975) terminating
    2022-02-11 20:52:03.747  - error: luxtronik2.0 (23975) 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().
    2022-02-11 20:52:03.747  - error: luxtronik2.0 (23975) unhandled promise rejection: DB closed
    2022-02-11 20:52:03.749  - error: luxtronik2.0 (23975) Error: DB closed
        at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:183:25)
        at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:150:20)
        at Object.onceWrapper (events.js:520:26)
        at Socket.emit (events.js:400:28)
        at Socket.emit (domain.js:475:12)
        at TCP.<anonymous> (net.js:686:12)
    2022-02-11 20:52:03.749  - error: luxtronik2.0 (23975) DB closed
    2022-02-11 20:52:06.711  - info: host.iobroker instance system.adapter.luxtronik2.0 scheduled normal terminated and will be restarted on schedule.
    2022-02-11 20:52:06.713  - info: host.iobroker Restart adapter system.adapter.luxtronik2.0 because enabled
    2022-02-11 20:52:12.605  - info: host.iobroker instance system.adapter.luxtronik2.0 started with pid 23990
    2022-02-11 20:52:17.956  - warn: luxtronik2.0 (23990) slow connection to states DB. Still waiting ...
    2022-02-11 20:52:18.496  - warn: host.iobroker-Server Objects 192.168.178.11:35244 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets"]
    2022-02-11 20:52:18.986  - warn: host.iobroker-Server Objects 192.168.178.11:35244 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.protocolVersion"]
    2022-02-11 20:52:20.201  - warn: host.iobroker-Server Objects 192.168.178.11:35246 Error from InMemDB: Error: PSUBSCRIBE-UNSUPPORTED for namespace cfg.: Data=["meta.*"]
    2022-02-11 20:52:26.110  - warn: host.iobroker-Server States 192.168.178.11:56598 Error from InMemDB: Error: GET-UNSUPPORTED for namespace meta.: Data=["meta.states.protocolVersion"]
    2022-02-11 20:52:28.776  - warn: host.iobroker-Server States 192.168.178.11:56600 Error from InMemDB: Error: PSUBSCRIBE-UNSUPPORTED for namespace meta.: Data=["meta.*"]
    2022-02-11 20:52:45.931  - info: knx.0 (676) State value to set for "knx.0.1_Zentral_und_Sicherheit.1_Wetterstation.Datum_Uhrzeit" has to be type "number" but received type "object" 
    2022-02-11 20:53:09.713  - info: luxtronik2.0 (23990) starting. Version 0.3.0 in /opt/iobroker/node_modules/iobroker.luxtronik2, node: v14.18.3, js-controller: 3.3.22
    2022-02-11 20:53:15.187  - info: luxtronik2.0 (23990) Connecting to ws://192.168.178.5:8214
    2022-02-11 20:54:00.006  - info: luxtronik2.0 (23990) Scheduled restart.
    2022-02-11 20:54:01.508  - info: luxtronik2.0 (23990) terminating with timeout
    2022-02-11 20:54:01.508  - info: luxtronik2.0 (23990) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
    2022-02-11 20:54:02.259  - info: luxtronik2.0 (23990) terminating
    2022-02-11 20:54:02.259  - info: luxtronik2.0 (23990) terminating
    2022-02-11 20:54:04.535  - error: luxtronik2.0 (23990) 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().
    2022-02-11 20:54:04.535  - error: luxtronik2.0 (23990) unhandled promise rejection: DB closed
    2022-02-11 20:54:04.536  - error: luxtronik2.0 (23990) Error: DB closed
        at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:183:25)
        at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:150:20)
        at Object.onceWrapper (events.js:520:26)
        at Socket.emit (events.js:400:28)
        at Socket.emit (domain.js:475:12)
        at TCP.<anonymous> (net.js:686:12)
    2022-02-11 20:54:04.537  - error: luxtronik2.0 (23990) DB closed
    2022-02-11 20:54:08.887  - info: host.iobroker instance system.adapter.luxtronik2.0 scheduled normal terminated and will be restarted on schedule.
    2022-02-11 20:54:08.888  - info: host.iobroker Restart adapter system.adapter.luxtronik2.0 because enabled
    2022-02-11 20:54:16.568  - info: host.iobroker instance system.adapter.luxtronik2.0 started with pid 24007
    2022-02-11 20:54:22.319  - warn: luxtronik2.0 (24007) slow connection to states DB. Still waiting ...
    2022-02-11 20:55:18.038  - info: luxtronik2.0 (24007) starting. Version 0.3.0 in /opt/iobroker/node_modules/iobroker.luxtronik2, node: v14.18.3, js-controller: 3.3.22
    2022-02-11 20:55:22.623  - info: luxtronik2.0 (24007) Connecting to ws://192.168.178.5:8214
    2022-02-11 20:55:53.175  - info: judoisoft.0 (646) State value to set for "judoisoft.0.ServiceDays" has to be type "number" but received type "string" 
    2022-02-11 20:55:53.812  - info: judoisoft.0 (646) State value to set for "judoisoft.0.Maintenance" has to be type "number" but received type "string" 
    2022-02-11 20:56:00.004  - info: luxtronik2.0 (24007) Scheduled restart.
    2022-02-11 20:56:01.506  - info: luxtronik2.0 (24007) terminating with timeout
    2022-02-11 20:56:01.507  - info: luxtronik2.0 (24007) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
    2022-02-11 20:56:01.962  - info: luxtronik2.0 (24007) terminating
    2022-02-11 20:56:02.295  - info: luxtronik2.0 (24007) terminating
    2022-02-11 20:56:04.226  - error: luxtronik2.0 (24007) 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().
    2022-02-11 20:56:04.226  - error: luxtronik2.0 (24007) unhandled promise rejection: DB closed
    2022-02-11 20:56:04.228  - error: luxtronik2.0 (24007) Error: DB closed
        at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:183:25)
        at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:150:20)
        at Object.onceWrapper (events.js:520:26)
        at Socket.emit (events.js:400:28)
        at Socket.emit (domain.js:475:12)
        at TCP.<anonymous> (net.js:686:12)
    2022-02-11 20:56:04.228  - error: luxtronik2.0 (24007) DB closed
    2022-02-11 20:56:07.930  - info: host.iobroker instance system.adapter.luxtronik2.0 scheduled normal terminated and will be restarted on schedule.
    2022-02-11 20:56:07.931  - info: host.iobroker Restart adapter system.adapter.luxtronik2.0 because enabled
    2022-02-11 20:56:14.602  - info: host.iobroker instance system.adapter.luxtronik2.0 started with pid 24022
    2022-02-11 20:56:14.989  - warn: host.iobroker-Server Objects 192.168.178.11:35256 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets"]
    2022-02-11 20:56:15.930  - warn: host.iobroker-Server Objects 192.168.178.11:35256 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.protocolVersion"]
    2022-02-11 20:56:16.681  - warn: host.iobroker-Server Objects 192.168.178.11:35258 Error from InMemDB: Error: PSUBSCRIBE-UNSUPPORTED for namespace cfg.: Data=["meta.*"]
    2022-02-11 20:56:20.176  - warn: luxtronik2.0 (24022) slow connection to states DB. Still waiting ...
    2022-02-11 20:56:22.412  - warn: host.iobroker-Server States 192.168.178.11:56610 Error from InMemDB: Error: GET-UNSUPPORTED for namespace meta.: Data=["meta.states.protocolVersion"]
    2022-02-11 20:56:24.527  - warn: host.iobroker-Server States 192.168.178.11:56612 Error from InMemDB: Error: PSUBSCRIBE-UNSUPPORTED for namespace meta.: Data=["meta.*"]
    2022-02-11 20:57:08.724  - info: luxtronik2.0 (24022) starting. Version 0.3.0 in /opt/iobroker/node_modules/iobroker.luxtronik2, node: v14.18.3, js-controller: 3.3.22
    2022-02-11 20:57:14.842  - info: luxtronik2.0 (24022) Connecting to ws://192.168.178.5:8214
    
    wendy2702W Offline
    wendy2702W Offline
    wendy2702
    schrieb am zuletzt editiert von
    #2

    @marcel-drzal Ich verstehe dein Problem ehrlich gesagt gerade nicht.

    Kannst du das nochmal genauer beschreiben?

    Kann es auch sein das du das falsche Log gepostet hast?

    Bitte keine Fragen per PN, die gehören ins Forum!

    Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

    ? 1 Antwort Letzte Antwort
    0
    • wendy2702W wendy2702

      @marcel-drzal Ich verstehe dein Problem ehrlich gesagt gerade nicht.

      Kannst du das nochmal genauer beschreiben?

      Kann es auch sein das du das falsche Log gepostet hast?

      ? Offline
      ? Offline
      Ein ehemaliger Benutzer
      schrieb am zuletzt editiert von
      #3

      @wendy2702 Danke für die Rückantwort

      heute morgen geht das System etwas schneller wirder.

      Mein Problem ist folgende Fehlermeldungen, welche ich immer erhalte.
      Auf der 192.168.178.11 läuft mein Rasperry Pi 3 Slave, welcher das Log was ich gepostet hatte ausgiebt. (siehe am Ende vom Log)
      Die IP 192.168.178.16 ist neim Intel Nuc Proxmox wo der Iobroker Master drauf läuft.

      Was ist Data Meta?

      e47fe717-2f61-475a-a624-5c4b7d19a33f-grafik.png

      wendy2702W 1 Antwort Letzte Antwort
      0
      • ? Ein ehemaliger Benutzer

        @wendy2702 Danke für die Rückantwort

        heute morgen geht das System etwas schneller wirder.

        Mein Problem ist folgende Fehlermeldungen, welche ich immer erhalte.
        Auf der 192.168.178.11 läuft mein Rasperry Pi 3 Slave, welcher das Log was ich gepostet hatte ausgiebt. (siehe am Ende vom Log)
        Die IP 192.168.178.16 ist neim Intel Nuc Proxmox wo der Iobroker Master drauf läuft.

        Was ist Data Meta?

        e47fe717-2f61-475a-a624-5c4b7d19a33f-grafik.png

        wendy2702W Offline
        wendy2702W Offline
        wendy2702
        schrieb am zuletzt editiert von
        #4

        @marcel-drzal Muss mir erstmal einen Überblick über deine Installation verschaffen.

        Bitte in der Konsole vom Master und Slave einmal das ausführen und hier als Text in Code Tags posten.

        CodeTags.gif

        iob list instances
        iob update
        

        Bitte keine Fragen per PN, die gehören ins Forum!

        Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

        ? 1 Antwort Letzte Antwort
        0
        • wendy2702W wendy2702

          @marcel-drzal Muss mir erstmal einen Überblick über deine Installation verschaffen.

          Bitte in der Konsole vom Master und Slave einmal das ausführen und hier als Text in Code Tags posten.

          CodeTags.gif

          iob list instances
          iob update
          
          ? Offline
          ? Offline
          Ein ehemaliger Benutzer
          schrieb am zuletzt editiert von Ein ehemaliger Benutzer
          #5

          @wendy2702 Auf dem Master habe ich noch ein Problem mit dem Backup aber ist erst mal nebensächlich. HOffe ers du kannst mir helfen.

          Vom Master auf Proxmox LXC:

          root@iobroker:~# cd /opt/iobroker/
          root@iobroker:/opt/iobroker# iob list instances
          
          Server Cannot load /opt/iobroker/iobroker-data/objects.json: Database file /opt/iobroker/iobroker-data/objects.json does not exists.. We try last Backup!
          No connection to databases possible ...
          root@iobroker:/opt/iobroker#
          root@iobroker:/opt/iobroker# iob update
          No connection to databases possible ...
          root@iobroker:/opt/iobroker#
          

          vom Slave auf Raspi 3:

          pi@pi-Test:/opt/iobroker $ iob list instances
           Connection is closed.
          Uncaught Rejection: Error: States DB is not allowed to start in the current Multihost environment
              at Redis.<anonymous> (/opt/iobroker/node_modules/@iobroker/db-states-redis/lib/states/statesInRedisClient.js:579:23)
              at processTicksAndRejections (internal/process/task_queues.js:95:5)
           Unable to subscribe to expiry Keyspace events from Redis Server: Connection is closed.
           Unable to subscribe to evicted Keyspace events from Redis Server: Connection is closed.
           Unable to subscribe to meta namespace "meta." changes: Connection is closed.
          pi@pi-Test:/opt/iobroker $ iob update
          
          Uncaught Rejection: Error: Connection is closed.
              at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
              at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
              at Object.onceWrapper (events.js:520:26)
              at Socket.emit (events.js:400:28)
              at TCP.<anonymous> (net.js:686:12)
           Unable to subscribe to expiry Keyspace events from Redis Server: Connection is closed.
           Unable to subscribe to evicted Keyspace events from Redis Server: Connection is closed.
           Unable to subscribe to meta namespace "meta." changes: Connection is closed.
          pi@pi-Test:/opt/iobroker $
          pi@pi-Test:/opt/iobroker $
          
          
          wendy2702W 1 Antwort Letzte Antwort
          0
          • ? Ein ehemaliger Benutzer

            @wendy2702 Auf dem Master habe ich noch ein Problem mit dem Backup aber ist erst mal nebensächlich. HOffe ers du kannst mir helfen.

            Vom Master auf Proxmox LXC:

            root@iobroker:~# cd /opt/iobroker/
            root@iobroker:/opt/iobroker# iob list instances
            
            Server Cannot load /opt/iobroker/iobroker-data/objects.json: Database file /opt/iobroker/iobroker-data/objects.json does not exists.. We try last Backup!
            No connection to databases possible ...
            root@iobroker:/opt/iobroker#
            root@iobroker:/opt/iobroker# iob update
            No connection to databases possible ...
            root@iobroker:/opt/iobroker#
            

            vom Slave auf Raspi 3:

            pi@pi-Test:/opt/iobroker $ iob list instances
             Connection is closed.
            Uncaught Rejection: Error: States DB is not allowed to start in the current Multihost environment
                at Redis.<anonymous> (/opt/iobroker/node_modules/@iobroker/db-states-redis/lib/states/statesInRedisClient.js:579:23)
                at processTicksAndRejections (internal/process/task_queues.js:95:5)
             Unable to subscribe to expiry Keyspace events from Redis Server: Connection is closed.
             Unable to subscribe to evicted Keyspace events from Redis Server: Connection is closed.
             Unable to subscribe to meta namespace "meta." changes: Connection is closed.
            pi@pi-Test:/opt/iobroker $ iob update
            
            Uncaught Rejection: Error: Connection is closed.
                at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                at Object.onceWrapper (events.js:520:26)
                at Socket.emit (events.js:400:28)
                at TCP.<anonymous> (net.js:686:12)
             Unable to subscribe to expiry Keyspace events from Redis Server: Connection is closed.
             Unable to subscribe to evicted Keyspace events from Redis Server: Connection is closed.
             Unable to subscribe to meta namespace "meta." changes: Connection is closed.
            pi@pi-Test:/opt/iobroker $
            pi@pi-Test:/opt/iobroker $
            
            
            wendy2702W Offline
            wendy2702W Offline
            wendy2702
            schrieb am zuletzt editiert von
            #6

            @marcel-drzal sagte in Adapter RPI2.0 nicht mehr drauf und sehr langam geworden:

            Server Cannot load /opt/iobroker/iobroker-data/objects.json: Database file /opt/iobroker/iobroker-data/objects.json does not exists.. We try last Backup!

            Erstmal: NICHT als root user arbeiten. Wenn du keinen user hast lege einen an und nutze den.

            Läuft dein iobroker überhaupt?

            Auf dem Master/Slave

            iob status
            iob v
            

            Bitte keine Fragen per PN, die gehören ins Forum!

            Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

            ? 1 Antwort Letzte Antwort
            0
            • wendy2702W wendy2702

              @marcel-drzal sagte in Adapter RPI2.0 nicht mehr drauf und sehr langam geworden:

              Server Cannot load /opt/iobroker/iobroker-data/objects.json: Database file /opt/iobroker/iobroker-data/objects.json does not exists.. We try last Backup!

              Erstmal: NICHT als root user arbeiten. Wenn du keinen user hast lege einen an und nutze den.

              Läuft dein iobroker überhaupt?

              Auf dem Master/Slave

              iob status
              iob v
              
              ? Offline
              ? Offline
              Ein ehemaliger Benutzer
              schrieb am zuletzt editiert von Ein ehemaliger Benutzer
              #7

              @wendy2702

              danke für die Info. bin nun als User drin

              Liegt es an den Versionen? Wie kann ich das Ändern?
              Und was bedeutet Meta kann nicht aboniert werden?

              Beim Master 192.168.178.18

              marcel@iobroker:~$ iob status
              iobroker is running on this host.
              
              
              Objects type: file
              States  type: file
              marcel@iobroker:~$ iob v
              3.3.22
              marcel@iobroker:~$
              
              
              

              uns der Slave:

              192.168.178.11

              
              pi@pi-Test:/opt/iobroker $ iob status
               Unable to subscribe to meta namespace "meta." changes: Error PSUBSCRIBE-UNSUPPORTED for namespace meta.: Data=["meta.*"]
              iobroker is running on this host.
              
              At least one iobroker host is running.
              
              Objects type: jsonl
              States  type: jsonl
              pi@pi-Test:/opt/iobroker $ iob v
              4.0.8
              pi@pi-Test:/opt/iobroker $
              
              
              HomoranH 1 Antwort Letzte Antwort
              0
              • ? Ein ehemaliger Benutzer

                @wendy2702

                danke für die Info. bin nun als User drin

                Liegt es an den Versionen? Wie kann ich das Ändern?
                Und was bedeutet Meta kann nicht aboniert werden?

                Beim Master 192.168.178.18

                marcel@iobroker:~$ iob status
                iobroker is running on this host.
                
                
                Objects type: file
                States  type: file
                marcel@iobroker:~$ iob v
                3.3.22
                marcel@iobroker:~$
                
                
                

                uns der Slave:

                192.168.178.11

                
                pi@pi-Test:/opt/iobroker $ iob status
                 Unable to subscribe to meta namespace "meta." changes: Error PSUBSCRIBE-UNSUPPORTED for namespace meta.: Data=["meta.*"]
                iobroker is running on this host.
                
                At least one iobroker host is running.
                
                Objects type: jsonl
                States  type: jsonl
                pi@pi-Test:/opt/iobroker $ iob v
                4.0.8
                pi@pi-Test:/opt/iobroker $
                
                
                HomoranH Nicht stören
                HomoranH Nicht stören
                Homoran
                Global Moderator Administrators
                schrieb am zuletzt editiert von Homoran
                #8

                @marcel-drzal sagte in Adapter RPI2.0 nicht mehr drauf und sehr langam geworden:

                pi@pi-Test:/opt/iobroker $ iob v 4.0.8

                keinen Controller v4 mit v3 mischen
                Außerdem ist v4 noch Beta

                kein Support per PN! - Fragen im Forum stellen -
                Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
                Das Forum freut sich über eine Spende. Benutzt dazu den Spendenbutton im Header. Danke!
                der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -

                ? 1 Antwort Letzte Antwort
                0
                • wendy2702W Offline
                  wendy2702W Offline
                  wendy2702
                  schrieb am zuletzt editiert von
                  #9

                  wie @Homoran sagt. Erstmal auf beiden den JS Controller gleich machen.

                  Entweder beide JS3.3.22 oder beide 4.0.8

                  Dann können wir mal den rest vom System prüfen.

                  Bitte keine Fragen per PN, die gehören ins Forum!

                  Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

                  ? 2 Antworten Letzte Antwort
                  0
                  • HomoranH Homoran

                    @marcel-drzal sagte in Adapter RPI2.0 nicht mehr drauf und sehr langam geworden:

                    pi@pi-Test:/opt/iobroker $ iob v 4.0.8

                    keinen Controller v4 mit v3 mischen
                    Außerdem ist v4 noch Beta

                    ? Offline
                    ? Offline
                    Ein ehemaliger Benutzer
                    schrieb am zuletzt editiert von
                    #10

                    @homoran ok also den v4 auf v3 wieder änder

                    gibt es da ein Befehl?

                    HomoranH 1 Antwort Letzte Antwort
                    0
                    • ? Ein ehemaliger Benutzer

                      @homoran ok also den v4 auf v3 wieder änder

                      gibt es da ein Befehl?

                      HomoranH Nicht stören
                      HomoranH Nicht stören
                      Homoran
                      Global Moderator Administrators
                      schrieb am zuletzt editiert von
                      #11

                      @marcel-drzal sagte in Adapter RPI2.0 nicht mehr drauf und sehr langam geworden:

                      @homoran ok also den v4 auf v3 wieder änder

                      gibt es da ein Befehl?

                      Bin nicht sicher:
                      iobroker upgrade self@3.3.22

                      kein Support per PN! - Fragen im Forum stellen -
                      Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
                      Das Forum freut sich über eine Spende. Benutzt dazu den Spendenbutton im Header. Danke!
                      der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -

                      ? 1 Antwort Letzte Antwort
                      0
                      • wendy2702W wendy2702

                        wie @Homoran sagt. Erstmal auf beiden den JS Controller gleich machen.

                        Entweder beide JS3.3.22 oder beide 4.0.8

                        Dann können wir mal den rest vom System prüfen.

                        ? Offline
                        ? Offline
                        Ein ehemaliger Benutzer
                        schrieb am zuletzt editiert von
                        #12

                        @wendy2702 sagte in Adapter RPI2.0 nicht mehr drauf und sehr langam geworden:

                        JS3.3.22

                        Fehler beim Update aud 3.22

                        
                        pi@pi-Test:/opt/iobroker $ sudo iobroker update
                         Unable to subscribe to meta namespace "meta." changes: Error PSUBSCRIBE-UNSUPPORTED for namespace meta.: Data=["meta.*"]
                        Used repository: Stable (default)
                        Adapter    "admin"        : 5.2.3    , installed 5.1.25 [Updatable]
                        Adapter    "backitup"     : 2.2.3    , installed 2.2.3
                        Adapter    "discovery"    : 2.7.3    , installed 2.7.3
                        Controller "js-controller": 3.3.22   , installed 4.0.8
                        Adapter    "node-red"     : 2.4.1    , installed 2.4.1
                        Adapter    "rpi2"         : 1.3.1    , installed 1.3.1
                        pi@pi-Test:/opt/iobroker $
                        
                        
                        cd /opt/iobroker
                        sudo iobroker stop
                        sudo iobroker update
                        sudo iobroker upgrade self
                        sudo iobroker start
                        
                        Thomas BraunT 1 Antwort Letzte Antwort
                        0
                        • HomoranH Homoran

                          @marcel-drzal sagte in Adapter RPI2.0 nicht mehr drauf und sehr langam geworden:

                          @homoran ok also den v4 auf v3 wieder änder

                          gibt es da ein Befehl?

                          Bin nicht sicher:
                          iobroker upgrade self@3.3.22

                          ? Offline
                          ? Offline
                          Ein ehemaliger Benutzer
                          schrieb am zuletzt editiert von
                          #13

                          @homoran
                          geht auch nicht

                          immer die gleiche Fehlermeldung:

                          
                          pi@pi-Test:/opt/iobroker $  iobroker upgrade self@3.3.22
                           Unable to subscribe to meta namespace "meta." changes: Error PSUBSCRIBE-UNSUPPORTED for namespace meta.: Data=["meta.*"]
                          Adapter "self" is not in the repository and cannot be updated.
                          Cannot upgrade: Cannot read property 'controller' of undefined
                          
                          
                          1 Antwort Letzte Antwort
                          0
                          • ? Ein ehemaliger Benutzer

                            @wendy2702 sagte in Adapter RPI2.0 nicht mehr drauf und sehr langam geworden:

                            JS3.3.22

                            Fehler beim Update aud 3.22

                            
                            pi@pi-Test:/opt/iobroker $ sudo iobroker update
                             Unable to subscribe to meta namespace "meta." changes: Error PSUBSCRIBE-UNSUPPORTED for namespace meta.: Data=["meta.*"]
                            Used repository: Stable (default)
                            Adapter    "admin"        : 5.2.3    , installed 5.1.25 [Updatable]
                            Adapter    "backitup"     : 2.2.3    , installed 2.2.3
                            Adapter    "discovery"    : 2.7.3    , installed 2.7.3
                            Controller "js-controller": 3.3.22   , installed 4.0.8
                            Adapter    "node-red"     : 2.4.1    , installed 2.4.1
                            Adapter    "rpi2"         : 1.3.1    , installed 1.3.1
                            pi@pi-Test:/opt/iobroker $
                            
                            
                            cd /opt/iobroker
                            sudo iobroker stop
                            sudo iobroker update
                            sudo iobroker upgrade self
                            sudo iobroker start
                            
                            Thomas BraunT Online
                            Thomas BraunT Online
                            Thomas Braun
                            Most Active
                            schrieb am zuletzt editiert von
                            #14

                            @marcel-drzal

                            Wie kommst du auf die Idee mit sudo da herum zu frickeln? Das ist falsch.

                            Linux-Werkzeugkasten:
                            https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                            NodeJS Fixer Skript:
                            https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                            iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                            ? 1 Antwort Letzte Antwort
                            0
                            • wendy2702W wendy2702

                              wie @Homoran sagt. Erstmal auf beiden den JS Controller gleich machen.

                              Entweder beide JS3.3.22 oder beide 4.0.8

                              Dann können wir mal den rest vom System prüfen.

                              ? Offline
                              ? Offline
                              Ein ehemaliger Benutzer
                              schrieb am zuletzt editiert von
                              #15

                              @wendy2702

                              Keine Verbindung zur Datenbbank möglich

                              
                              pi@pi-Test:/opt/iobroker $  iobroker upgrade self@3.3.22
                               Unable to subscribe to meta namespace "meta." changes: Error PSUBSCRIBE-UNSUPPORTED for namespace meta.: Data=["meta.*"]
                              Adapter "self" is not in the repository and cannot be updated.
                              Cannot upgrade: Cannot read property 'controller' of undefined
                              pi@pi-Test:/opt/iobroker $ ^C
                              pi@pi-Test:/opt/iobroker $
                              pi@pi-Test:/opt/iobroker $
                              pi@pi-Test:/opt/iobroker $ iobroker stop
                              pi@pi-Test:/opt/iobroker $ iobroker update
                              No connection to databases possible ...
                              pi@pi-Test:/opt/iobroker $ iobroker upgrade self
                              No connection to databases possible ...
                              pi@pi-Test:/opt/iobroker $  iobroker upgrade self@3.3.22
                              No connection to databases possible ...
                              pi@pi-Test:/opt/iobroker $
                              
                              
                              Thomas BraunT wendy2702W 2 Antworten Letzte Antwort
                              0
                              • ? Ein ehemaliger Benutzer

                                @wendy2702

                                Keine Verbindung zur Datenbbank möglich

                                
                                pi@pi-Test:/opt/iobroker $  iobroker upgrade self@3.3.22
                                 Unable to subscribe to meta namespace "meta." changes: Error PSUBSCRIBE-UNSUPPORTED for namespace meta.: Data=["meta.*"]
                                Adapter "self" is not in the repository and cannot be updated.
                                Cannot upgrade: Cannot read property 'controller' of undefined
                                pi@pi-Test:/opt/iobroker $ ^C
                                pi@pi-Test:/opt/iobroker $
                                pi@pi-Test:/opt/iobroker $
                                pi@pi-Test:/opt/iobroker $ iobroker stop
                                pi@pi-Test:/opt/iobroker $ iobroker update
                                No connection to databases possible ...
                                pi@pi-Test:/opt/iobroker $ iobroker upgrade self
                                No connection to databases possible ...
                                pi@pi-Test:/opt/iobroker $  iobroker upgrade self@3.3.22
                                No connection to databases possible ...
                                pi@pi-Test:/opt/iobroker $
                                
                                
                                Thomas BraunT Online
                                Thomas BraunT Online
                                Thomas Braun
                                Most Active
                                schrieb am zuletzt editiert von Thomas Braun
                                #16

                                @marcel-drzal
                                Ist klar. Das Datenbankformat passt nicht mehr.
                                Musst mal schauen, ob man das neue jetzt vorab auf file umstellen kann.
                                Aber das ist ja eine schöne Aufgabe für einen Beta-Tester, der dann auch noch als root über das System rutscht.

                                Linux-Werkzeugkasten:
                                https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                                NodeJS Fixer Skript:
                                https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                                iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                                1 Antwort Letzte Antwort
                                0
                                • Thomas BraunT Thomas Braun

                                  @marcel-drzal

                                  Wie kommst du auf die Idee mit sudo da herum zu frickeln? Das ist falsch.

                                  ? Offline
                                  ? Offline
                                  Ein ehemaliger Benutzer
                                  schrieb am zuletzt editiert von
                                  #17

                                  @thomas-braun

                                  npm ist auch auf der falschen Version

                                  
                                  pi@pi-Test:/opt/iobroker $ npm -v
                                  8.4.1
                                  
                                  
                                  Thomas BraunT 1 Antwort Letzte Antwort
                                  0
                                  • ? Ein ehemaliger Benutzer

                                    @thomas-braun

                                    npm ist auch auf der falschen Version

                                    
                                    pi@pi-Test:/opt/iobroker $ npm -v
                                    8.4.1
                                    
                                    
                                    Thomas BraunT Online
                                    Thomas BraunT Online
                                    Thomas Braun
                                    Most Active
                                    schrieb am zuletzt editiert von
                                    #18

                                    @marcel-drzal

                                    War mir klar...

                                    Ganz ehrlich: Installier den Mist neu, log dich nicht als root ein, verwende kein sudo beim iobroker, verwende keine Beta-Software.

                                    Linux-Werkzeugkasten:
                                    https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                                    NodeJS Fixer Skript:
                                    https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                                    iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                                    1 Antwort Letzte Antwort
                                    0
                                    • ? Ein ehemaliger Benutzer

                                      @wendy2702

                                      Keine Verbindung zur Datenbbank möglich

                                      
                                      pi@pi-Test:/opt/iobroker $  iobroker upgrade self@3.3.22
                                       Unable to subscribe to meta namespace "meta." changes: Error PSUBSCRIBE-UNSUPPORTED for namespace meta.: Data=["meta.*"]
                                      Adapter "self" is not in the repository and cannot be updated.
                                      Cannot upgrade: Cannot read property 'controller' of undefined
                                      pi@pi-Test:/opt/iobroker $ ^C
                                      pi@pi-Test:/opt/iobroker $
                                      pi@pi-Test:/opt/iobroker $
                                      pi@pi-Test:/opt/iobroker $ iobroker stop
                                      pi@pi-Test:/opt/iobroker $ iobroker update
                                      No connection to databases possible ...
                                      pi@pi-Test:/opt/iobroker $ iobroker upgrade self
                                      No connection to databases possible ...
                                      pi@pi-Test:/opt/iobroker $  iobroker upgrade self@3.3.22
                                      No connection to databases possible ...
                                      pi@pi-Test:/opt/iobroker $
                                      
                                      
                                      wendy2702W Offline
                                      wendy2702W Offline
                                      wendy2702
                                      schrieb am zuletzt editiert von wendy2702
                                      #19

                                      @marcel-drzal mach im iobroker Verzeichnis das:

                                      npm install iobroker.js-controller@3.3.22
                                      

                                      Wenn das obere nicht funktioniert weiter damit:

                                      hiermit prüfen welches Repo aktiv ist:

                                      iob repo
                                      

                                      Wenn Stable aktiv dann:

                                      sudo -H -u iobroker npm install iobroker.js-controller 
                                      

                                      EDIT: OK das mit dem NPM hatte ich noch garnicht gelesen :-(

                                      Bitte keine Fragen per PN, die gehören ins Forum!

                                      Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

                                      ? 1 Antwort Letzte Antwort
                                      0
                                      • wendy2702W wendy2702

                                        @marcel-drzal mach im iobroker Verzeichnis das:

                                        npm install iobroker.js-controller@3.3.22
                                        

                                        Wenn das obere nicht funktioniert weiter damit:

                                        hiermit prüfen welches Repo aktiv ist:

                                        iob repo
                                        

                                        Wenn Stable aktiv dann:

                                        sudo -H -u iobroker npm install iobroker.js-controller 
                                        

                                        EDIT: OK das mit dem NPM hatte ich noch garnicht gelesen :-(

                                        ? Offline
                                        ? Offline
                                        Ein ehemaliger Benutzer
                                        schrieb am zuletzt editiert von
                                        #20

                                        @wendy2702 geht wieder alles. Adapter Laufen nun auf 3.3.22
                                        danke dir

                                        1 Antwort Letzte Antwort
                                        0
                                        • wendy2702W Offline
                                          wendy2702W Offline
                                          wendy2702
                                          schrieb am zuletzt editiert von
                                          #21

                                          @marcel-drzal Top!

                                          Bitte keine Fragen per PN, die gehören ins Forum!

                                          Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

                                          1 Antwort Letzte Antwort
                                          0
                                          Antworten
                                          • In einem neuen Thema antworten
                                          Anmelden zum Antworten
                                          • Älteste zuerst
                                          • Neuste zuerst
                                          • Meiste Stimmen


                                          Support us

                                          ioBroker
                                          Community Adapters
                                          Donate

                                          396

                                          Online

                                          32.7k

                                          Benutzer

                                          82.5k

                                          Themen

                                          1.3m

                                          Beiträge
                                          Community
                                          Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
                                          ioBroker Community 2014-2025
                                          logo
                                          • Anmelden

                                          • Du hast noch kein Konto? Registrieren

                                          • Anmelden oder registrieren, um zu suchen
                                          • Erster Beitrag
                                            Letzter Beitrag
                                          0
                                          • Home
                                          • Aktuell
                                          • Tags
                                          • Ungelesen 0
                                          • Kategorien
                                          • Unreplied
                                          • Beliebt
                                          • GitHub
                                          • Docu
                                          • Hilfe