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. ioBroker Allgemein
  4. js-controller 3.2 jetzt im Latest!

NEWS

  • UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?
    apollon77A
    apollon77
    48
    3
    8.5k

  • Monatsrückblick – September 2025
    BluefoxB
    Bluefox
    13
    1
    2.1k

  • Neues Video "KI im Smart Home" - ioBroker plus n8n
    BluefoxB
    Bluefox
    16
    1
    2.8k

js-controller 3.2 jetzt im Latest!

Geplant Angeheftet Gesperrt Verschoben ioBroker Allgemein
575 Beiträge 70 Kommentatoren 145.9k Aufrufe 57 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.
  • DutchmanD Dutchman

    @feuersturm said in js-controller 3.2 jetzt im Latest!:

    Gerade hat sich der COVID-19 live information Adapter ( Dutchman ) zu Wort gemeldet. Ist das ein Adapter oder ein js-controller Thema?

    Thanks fürs git issue kümmern mich drum

    P Offline
    P Offline
    PrinzEisenherz1
    schrieb am zuletzt editiert von
    #45

    Hab jetzt unter js-controller 3.2.7 schon das zweite mal folgenden fehler vom dwd-Adapter

    2021-01-18 00:00:14.153 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning.begin": Error: Connection is closed.
    2021-01-18 00:00:14.163 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning.end": Error: Connection is closed.
    2021-01-18 00:00:14.167 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning.severity": Error: Connection is closed.
    2021-01-18 00:00:14.168 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning.level": Error: Connection is closed.
    2021-01-18 00:00:14.169 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning.type": Error: Connection is closed.
    2021-01-18 00:00:14.170 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning.text": Error: Connection is closed.
    2021-01-18 00:00:14.171 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning.headline": Error: Connection is closed.
    2021-01-18 00:00:14.171 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning.description": Error: Connection is closed.
    2021-01-18 00:00:14.175 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning.object": Error: Connection is closed.
    2021-01-18 00:00:14.177 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning.map": Error: Connection is closed.
    2021-01-18 00:00:14.200 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning1.begin": Error: Connection is closed.
    2021-01-18 00:00:14.200 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning1.end": Error: Connection is closed.
    2021-01-18 00:00:14.201 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning1.severity": Error: Connection is closed.
    2021-01-18 00:00:14.201 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning1.level": Error: Connection is closed.
    2021-01-18 00:00:14.211 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning1.type": Error: Connection is closed.
    2021-01-18 00:00:14.212 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning1.text": Error: Connection is closed.
    2021-01-18 00:00:14.212 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning1.headline": Error: Connection is closed.
    2021-01-18 00:00:14.212 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning1.description": Error: Connection is closed.
    2021-01-18 00:00:14.213 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning1.object": Error: Connection is closed.
    2021-01-18 00:00:14.213 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning1.map": Error: Connection is closed.
    2021-01-18 00:00:14.214 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning2.begin": Error: Connection is closed.
    2021-01-18 00:00:14.214 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning2.end": Error: Connection is closed.
    2021-01-18 00:00:14.215 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning2.severity": Error: Connection is closed.
    2021-01-18 00:00:14.215 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning2.level": Error: Connection is closed.
    2021-01-18 00:00:14.215 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning2.type": Error: Connection is closed.
    2021-01-18 00:00:14.216 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning2.text": Error: Connection is closed.
    2021-01-18 00:00:14.216 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning2.headline": Error: Connection is closed.
    2021-01-18 00:00:14.216 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning2.description": Error: Connection is closed.
    2021-01-18 00:00:14.217 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning2.object": Error: Connection is closed.
    2021-01-18 00:00:14.217 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning2.map": Error: Connection is closed.
    2021-01-18 00:00:14.218 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.numberofwarnings: Error: Cannot check object existence of "dwd.0.numberofwarnings": Error: Connection is closed.
    2021-01-18 00:00:14.223 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning.begin: Error: Cannot check object existence of "dwd.0.warning.begin": Error: Connection is closed.
    2021-01-18 00:00:14.224 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning.end: Error: Cannot check object existence of "dwd.0.warning.end": Error: Connection is closed.
    2021-01-18 00:00:14.225 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning.severity: Error: Cannot check object existence of "dwd.0.warning.severity": Error: Connection is closed.
    2021-01-18 00:00:14.225 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning.level: Error: Cannot check object existence of "dwd.0.warning.level": Error: Connection is closed.
    2021-01-18 00:00:14.226 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning.type: Error: Cannot check object existence of "dwd.0.warning.type": Error: Connection is closed.
    2021-01-18 00:00:14.227 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning.text: Error: Cannot check object existence of "dwd.0.warning.text": Error: Connection is closed.
    2021-01-18 00:00:14.228 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning.headline: Error: Cannot check object existence of "dwd.0.warning.headline": Error: Connection is closed.
    2021-01-18 00:00:14.259 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning.description: Error: Cannot check object existence of "dwd.0.warning.description": Error: Connection is closed.
    2021-01-18 00:00:14.260 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning.object: Error: Cannot check object existence of "dwd.0.warning.object": Error: Connection is closed.
    2021-01-18 00:00:14.260 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning.map: Error: Cannot check object existence of "dwd.0.warning.map": Error: Connection is closed.
    2021-01-18 00:00:14.261 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning1.begin: Error: Cannot check object existence of "dwd.0.warning1.begin": Error: Connection is closed.
    2021-01-18 00:00:14.262 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning1.end: Error: Cannot check object existence of "dwd.0.warning1.end": Error: Connection is closed.
    2021-01-18 00:00:14.263 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning1.severity: Error: Cannot check object existence of "dwd.0.warning1.severity": Error: Connection is closed.
    2021-01-18 00:00:14.264 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning1.level: Error: Cannot check object existence of "dwd.0.warning1.level": Error: Connection is closed.
    2021-01-18 00:00:14.264 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning1.type: Error: Cannot check object existence of "dwd.0.warning1.type": Error: Connection is closed.
    2021-01-18 00:00:14.265 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning1.text: Error: Cannot check object existence of "dwd.0.warning1.text": Error: Connection is closed.
    2021-01-18 00:00:14.266 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning1.headline: Error: Cannot check object existence of "dwd.0.warning1.headline": Error: Connection is closed.
    2021-01-18 00:00:14.311 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning1.description: Error: Cannot check object existence of "dwd.0.warning1.description": Error: Connection is closed.
    2021-01-18 00:00:14.312 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning1.object: Error: Cannot check object existence of "dwd.0.warning1.object": Error: Connection is closed.
    2021-01-18 00:00:14.313 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning1.map: Error: Cannot check object existence of "dwd.0.warning1.map": Error: Connection is closed.
    2021-01-18 00:00:14.314 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning2.begin: Error: Cannot check object existence of "dwd.0.warning2.begin": Error: Connection is closed.
    2021-01-18 00:00:14.315 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning2.end: Error: Cannot check object existence of "dwd.0.warning2.end": Error: Connection is closed.
    2021-01-18 00:00:14.316 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning2.severity: Error: Cannot check object existence of "dwd.0.warning2.severity": Error: Connection is closed.
    2021-01-18 00:00:14.316 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning2.level: Error: Cannot check object existence of "dwd.0.warning2.level": Error: Connection is closed.
    2021-01-18 00:00:14.317 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning2.type: Error: Cannot check object existence of "dwd.0.warning2.type": Error: Connection is closed.
    2021-01-18 00:00:14.318 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning2.text: Error: Cannot check object existence of "dwd.0.warning2.text": Error: Connection is closed.
    2021-01-18 00:00:14.335 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning2.headline: Error: Cannot check object existence of "dwd.0.warning2.headline": Error: Connection is closed.
    2021-01-18 00:00:14.336 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning2.description: Error: Cannot check object existence of "dwd.0.warning2.description": Error: Connection is closed.
    2021-01-18 00:00:14.337 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning2.object: Error: Cannot check object existence of "dwd.0.warning2.object": Error: Connection is closed.
    2021-01-18 00:00:14.337 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning2.map: Error: Cannot check object existence of "dwd.0.warning2.map": Error: Connection is closed.
    2021-01-18 00:00:14.373 - error: dwd.0 (5122) 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().
    2021-01-18 00:00:14.374 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
    2021-01-18 00:00:14.444 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
    at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    2021-01-18 00:00:14.445 - error: dwd.0 (5122) Cannot read property 'setState' of null
    2021-01-18 00:00:14.474 - error: dwd.0 (5122) 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().
    2021-01-18 00:00:14.475 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
    2021-01-18 00:00:14.476 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
    at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    2021-01-18 00:00:14.477 - error: dwd.0 (5122) Cannot read property 'setState' of null
    2021-01-18 00:00:14.484 - error: dwd.0 (5122) 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().
    2021-01-18 00:00:14.486 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
    2021-01-18 00:00:14.487 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
    at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    2021-01-18 00:00:14.488 - error: dwd.0 (5122) Cannot read property 'setState' of null
    2021-01-18 00:00:14.494 - error: dwd.0 (5122) 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().
    2021-01-18 00:00:14.504 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
    2021-01-18 00:00:14.506 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
    at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    2021-01-18 00:00:14.506 - error: dwd.0 (5122) Cannot read property 'setState' of null
    2021-01-18 00:00:14.511 - error: dwd.0 (5122) 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().
    2021-01-18 00:00:14.513 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
    2021-01-18 00:00:14.515 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
    at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    2021-01-18 00:00:14.515 - error: dwd.0 (5122) Cannot read property 'setState' of null
    2021-01-18 00:00:14.520 - error: dwd.0 (5122) 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().
    2021-01-18 00:00:14.520 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
    2021-01-18 00:00:14.521 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
    at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    2021-01-18 00:00:14.522 - error: dwd.0 (5122) Cannot read property 'setState' of null
    2021-01-18 00:00:14.531 - error: dwd.0 (5122) 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().
    2021-01-18 00:00:14.532 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
    2021-01-18 00:00:14.544 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
    at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    2021-01-18 00:00:14.545 - error: dwd.0 (5122) Cannot read property 'setState' of null
    2021-01-18 00:00:14.555 - error: dwd.0 (5122) 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().
    2021-01-18 00:00:14.556 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
    2021-01-18 00:00:14.557 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
    at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    2021-01-18 00:00:14.558 - error: dwd.0 (5122) Cannot read property 'setState' of null
    2021-01-18 00:00:14.588 - error: dwd.0 (5122) 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().
    2021-01-18 00:00:14.590 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
    2021-01-18 00:00:14.591 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
    at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    2021-01-18 00:00:14.592 - error: dwd.0 (5122) Cannot read property 'setState' of null
    2021-01-18 00:00:14.606 - error: dwd.0 (5122) 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().
    2021-01-18 00:00:14.607 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
    2021-01-18 00:00:14.608 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
    at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    2021-01-18 00:00:14.609 - error: dwd.0 (5122) Cannot read property 'setState' of null
    2021-01-18 00:00:14.618 - error: dwd.0 (5122) 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().
    2021-01-18 00:00:14.619 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
    2021-01-18 00:00:14.622 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
    at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    2021-01-18 00:00:14.622 - error: dwd.0 (5122) Cannot read property 'setState' of null
    2021-01-18 00:00:14.628 - error: dwd.0 (5122) 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().
    2021-01-18 00:00:14.629 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
    2021-01-18 00:00:14.632 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
    at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    2021-01-18 00:00:14.633 - error: dwd.0 (5122) Cannot read property 'setState' of null
    2021-01-18 00:00:14.637 - error: dwd.0 (5122) 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().
    2021-01-18 00:00:14.640 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
    2021-01-18 00:00:14.642 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
    at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    2021-01-18 00:00:14.644 - error: dwd.0 (5122) Cannot read property 'setState' of null
    2021-01-18 00:00:14.664 - error: dwd.0 (5122) 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().
    2021-01-18 00:00:14.665 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
    2021-01-18 00:00:14.667 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
    at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    2021-01-18 00:00:14.670 - error: dwd.0 (5122) Cannot read property 'setState' of null
    2021-01-18 00:00:14.678 - error: dwd.0 (5122) 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().
    2021-01-18 00:00:14.679 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
    2021-01-18 00:00:14.681 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
    at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    2021-01-18 00:00:14.692 - error: dwd.0 (5122) Cannot read property 'setState' of null
    2021-01-18 00:00:14.699 - error: dwd.0 (5122) 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().
    2021-01-18 00:00:14.700 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
    2021-01-18 00:00:14.702 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
    at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    2021-01-18 00:00:14.703 - error: dwd.0 (5122) Cannot read property 'setState' of null
    2021-01-18 00:00:14.812 - error: dwd.0 (5122) 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().
    2021-01-18 00:00:14.812 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
    2021-01-18 00:00:14.814 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
    at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    2021-01-18 00:00:14.831 - error: dwd.0 (5122) Cannot read property 'setState' of null
    2021-01-18 00:00:14.836 - error: dwd.0 (5122) 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().
    2021-01-18 00:00:14.837 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
    2021-01-18 00:00:14.838 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
    at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    2021-01-18 00:00:14.839 - error: dwd.0 (5122) Cannot read property 'setState' of null
    2021-01-18 00:00:14.844 - error: dwd.0 (5122) 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().
    2021-01-18 00:00:14.845 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
    2021-01-18 00:00:14.846 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
    at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    2021-01-18 00:00:14.847 - error: dwd.0 (5122) Cannot read property 'setState' of null
    2021-01-18 00:00:14.852 - error: dwd.0 (5122) 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().
    2021-01-18 00:00:14.853 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
    2021-01-18 00:00:14.855 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
    at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    2021-01-18 00:00:14.856 - error: dwd.0 (5122) Cannot read property 'setState' of null
    2021-01-18 00:00:14.862 - error: dwd.0 (5122) 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().
    2021-01-18 00:00:14.863 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
    2021-01-18 00:00:14.864 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
    at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    2021-01-18 00:00:14.865 - error: dwd.0 (5122) Cannot read property 'setState' of null
    2021-01-18 00:00:14.870 - error: dwd.0 (5122) 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().
    2021-01-18 00:00:14.871 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
    2021-01-18 00:00:14.872 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
    at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    2021-01-18 00:00:14.873 - error: dwd.0 (5122) Cannot read property 'setState' of null
    2021-01-18 00:00:14.877 - error: dwd.0 (5122) 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().
    2021-01-18 00:00:14.878 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
    2021-01-18 00:00:14.879 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
    at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    2021-01-18 00:00:14.880 - error: dwd.0 (5122) Cannot read property 'setState' of null
    2021-01-18 00:00:14.893 - error: dwd.0 (5122) 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().
    2021-01-18 00:00:14.894 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
    2021-01-18 00:00:14.907 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
    at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    2021-01-18 00:00:14.908 - error: dwd.0 (5122) Cannot read property 'setState' of null
    2021-01-18 00:00:14.915 - error: dwd.0 (5122) 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().
    2021-01-18 00:00:14.916 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
    2021-01-18 00:00:14.917 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
    at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    2021-01-18 00:00:14.918 - error: dwd.0 (5122) Cannot read property 'setState' of null
    2021-01-18 00:00:14.929 - error: dwd.0 (5122) 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().
    2021-01-18 00:00:14.929 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
    2021-01-18 00:00:14.934 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
    at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    2021-01-18 00:00:14.935 - error: dwd.0 (5122) Cannot read property 'setState' of null
    2021-01-18 00:00:14.940 - error: dwd.0 (5122) 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().
    2021-01-18 00:00:14.940 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
    2021-01-18 00:00:14.942 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
    at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    2021-01-18 00:00:14.943 - error: dwd.0 (5122) Cannot read property 'setState' of null
    2021-01-18 00:00:14.952 - error: dwd.0 (5122) 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().
    2021-01-18 00:00:14.953 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
    2021-01-18 00:00:14.955 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
    at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    2021-01-18 00:00:14.955 - error: dwd.0 (5122) Cannot read property 'setState' of null
    2021-01-18 00:00:14.965 - error: dwd.0 (5122) 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().
    2021-01-18 00:00:14.971 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
    2021-01-18 00:00:14.972 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
    at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    2021-01-18 00:00:14.973 - error: dwd.0 (5122) Cannot read property 'setState' of null
    2021-01-18 00:00:14.994 - error: dwd.0 (5122) 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().
    2021-01-18 00:00:14.995 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
    2021-01-18 00:00:14.996 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
    at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    2021-01-18 00:00:14.997 - error: dwd.0 (5122) Cannot read property 'setState' of null
    2021-01-18 00:00:15.028 - error: dwd.0 (5122) 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().
    2021-01-18 00:00:15.029 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
    2021-01-18 00:00:15.030 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
    at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    2021-01-18 00:00:15.031 - error: dwd.0 (5122) Cannot read property 'setState' of null
    

    Woran liegts? controller oder Adapter?

    Intel-NUC mit ProxMox: ioBroker,SQL, logging Strom- Gas- u. Wasserzähler;10Zoll Tab im Flur für VIS; weiteres: Homematic CCU2, Homeduino, Kameras, selbstgebaute Wetterstation;

    apollon77A 1 Antwort Letzte Antwort
    0
    • P PrinzEisenherz1

      Hab jetzt unter js-controller 3.2.7 schon das zweite mal folgenden fehler vom dwd-Adapter

      2021-01-18 00:00:14.153 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning.begin": Error: Connection is closed.
      2021-01-18 00:00:14.163 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning.end": Error: Connection is closed.
      2021-01-18 00:00:14.167 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning.severity": Error: Connection is closed.
      2021-01-18 00:00:14.168 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning.level": Error: Connection is closed.
      2021-01-18 00:00:14.169 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning.type": Error: Connection is closed.
      2021-01-18 00:00:14.170 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning.text": Error: Connection is closed.
      2021-01-18 00:00:14.171 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning.headline": Error: Connection is closed.
      2021-01-18 00:00:14.171 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning.description": Error: Connection is closed.
      2021-01-18 00:00:14.175 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning.object": Error: Connection is closed.
      2021-01-18 00:00:14.177 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning.map": Error: Connection is closed.
      2021-01-18 00:00:14.200 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning1.begin": Error: Connection is closed.
      2021-01-18 00:00:14.200 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning1.end": Error: Connection is closed.
      2021-01-18 00:00:14.201 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning1.severity": Error: Connection is closed.
      2021-01-18 00:00:14.201 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning1.level": Error: Connection is closed.
      2021-01-18 00:00:14.211 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning1.type": Error: Connection is closed.
      2021-01-18 00:00:14.212 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning1.text": Error: Connection is closed.
      2021-01-18 00:00:14.212 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning1.headline": Error: Connection is closed.
      2021-01-18 00:00:14.212 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning1.description": Error: Connection is closed.
      2021-01-18 00:00:14.213 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning1.object": Error: Connection is closed.
      2021-01-18 00:00:14.213 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning1.map": Error: Connection is closed.
      2021-01-18 00:00:14.214 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning2.begin": Error: Connection is closed.
      2021-01-18 00:00:14.214 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning2.end": Error: Connection is closed.
      2021-01-18 00:00:14.215 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning2.severity": Error: Connection is closed.
      2021-01-18 00:00:14.215 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning2.level": Error: Connection is closed.
      2021-01-18 00:00:14.215 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning2.type": Error: Connection is closed.
      2021-01-18 00:00:14.216 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning2.text": Error: Connection is closed.
      2021-01-18 00:00:14.216 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning2.headline": Error: Connection is closed.
      2021-01-18 00:00:14.216 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning2.description": Error: Connection is closed.
      2021-01-18 00:00:14.217 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning2.object": Error: Connection is closed.
      2021-01-18 00:00:14.217 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning2.map": Error: Connection is closed.
      2021-01-18 00:00:14.218 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.numberofwarnings: Error: Cannot check object existence of "dwd.0.numberofwarnings": Error: Connection is closed.
      2021-01-18 00:00:14.223 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning.begin: Error: Cannot check object existence of "dwd.0.warning.begin": Error: Connection is closed.
      2021-01-18 00:00:14.224 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning.end: Error: Cannot check object existence of "dwd.0.warning.end": Error: Connection is closed.
      2021-01-18 00:00:14.225 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning.severity: Error: Cannot check object existence of "dwd.0.warning.severity": Error: Connection is closed.
      2021-01-18 00:00:14.225 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning.level: Error: Cannot check object existence of "dwd.0.warning.level": Error: Connection is closed.
      2021-01-18 00:00:14.226 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning.type: Error: Cannot check object existence of "dwd.0.warning.type": Error: Connection is closed.
      2021-01-18 00:00:14.227 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning.text: Error: Cannot check object existence of "dwd.0.warning.text": Error: Connection is closed.
      2021-01-18 00:00:14.228 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning.headline: Error: Cannot check object existence of "dwd.0.warning.headline": Error: Connection is closed.
      2021-01-18 00:00:14.259 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning.description: Error: Cannot check object existence of "dwd.0.warning.description": Error: Connection is closed.
      2021-01-18 00:00:14.260 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning.object: Error: Cannot check object existence of "dwd.0.warning.object": Error: Connection is closed.
      2021-01-18 00:00:14.260 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning.map: Error: Cannot check object existence of "dwd.0.warning.map": Error: Connection is closed.
      2021-01-18 00:00:14.261 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning1.begin: Error: Cannot check object existence of "dwd.0.warning1.begin": Error: Connection is closed.
      2021-01-18 00:00:14.262 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning1.end: Error: Cannot check object existence of "dwd.0.warning1.end": Error: Connection is closed.
      2021-01-18 00:00:14.263 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning1.severity: Error: Cannot check object existence of "dwd.0.warning1.severity": Error: Connection is closed.
      2021-01-18 00:00:14.264 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning1.level: Error: Cannot check object existence of "dwd.0.warning1.level": Error: Connection is closed.
      2021-01-18 00:00:14.264 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning1.type: Error: Cannot check object existence of "dwd.0.warning1.type": Error: Connection is closed.
      2021-01-18 00:00:14.265 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning1.text: Error: Cannot check object existence of "dwd.0.warning1.text": Error: Connection is closed.
      2021-01-18 00:00:14.266 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning1.headline: Error: Cannot check object existence of "dwd.0.warning1.headline": Error: Connection is closed.
      2021-01-18 00:00:14.311 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning1.description: Error: Cannot check object existence of "dwd.0.warning1.description": Error: Connection is closed.
      2021-01-18 00:00:14.312 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning1.object: Error: Cannot check object existence of "dwd.0.warning1.object": Error: Connection is closed.
      2021-01-18 00:00:14.313 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning1.map: Error: Cannot check object existence of "dwd.0.warning1.map": Error: Connection is closed.
      2021-01-18 00:00:14.314 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning2.begin: Error: Cannot check object existence of "dwd.0.warning2.begin": Error: Connection is closed.
      2021-01-18 00:00:14.315 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning2.end: Error: Cannot check object existence of "dwd.0.warning2.end": Error: Connection is closed.
      2021-01-18 00:00:14.316 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning2.severity: Error: Cannot check object existence of "dwd.0.warning2.severity": Error: Connection is closed.
      2021-01-18 00:00:14.316 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning2.level: Error: Cannot check object existence of "dwd.0.warning2.level": Error: Connection is closed.
      2021-01-18 00:00:14.317 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning2.type: Error: Cannot check object existence of "dwd.0.warning2.type": Error: Connection is closed.
      2021-01-18 00:00:14.318 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning2.text: Error: Cannot check object existence of "dwd.0.warning2.text": Error: Connection is closed.
      2021-01-18 00:00:14.335 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning2.headline: Error: Cannot check object existence of "dwd.0.warning2.headline": Error: Connection is closed.
      2021-01-18 00:00:14.336 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning2.description: Error: Cannot check object existence of "dwd.0.warning2.description": Error: Connection is closed.
      2021-01-18 00:00:14.337 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning2.object: Error: Cannot check object existence of "dwd.0.warning2.object": Error: Connection is closed.
      2021-01-18 00:00:14.337 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning2.map: Error: Cannot check object existence of "dwd.0.warning2.map": Error: Connection is closed.
      2021-01-18 00:00:14.373 - error: dwd.0 (5122) 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().
      2021-01-18 00:00:14.374 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
      2021-01-18 00:00:14.444 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
      at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
      at processTicksAndRejections (internal/process/task_queues.js:97:5)
      2021-01-18 00:00:14.445 - error: dwd.0 (5122) Cannot read property 'setState' of null
      2021-01-18 00:00:14.474 - error: dwd.0 (5122) 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().
      2021-01-18 00:00:14.475 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
      2021-01-18 00:00:14.476 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
      at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
      at processTicksAndRejections (internal/process/task_queues.js:97:5)
      2021-01-18 00:00:14.477 - error: dwd.0 (5122) Cannot read property 'setState' of null
      2021-01-18 00:00:14.484 - error: dwd.0 (5122) 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().
      2021-01-18 00:00:14.486 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
      2021-01-18 00:00:14.487 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
      at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
      at processTicksAndRejections (internal/process/task_queues.js:97:5)
      2021-01-18 00:00:14.488 - error: dwd.0 (5122) Cannot read property 'setState' of null
      2021-01-18 00:00:14.494 - error: dwd.0 (5122) 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().
      2021-01-18 00:00:14.504 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
      2021-01-18 00:00:14.506 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
      at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
      at processTicksAndRejections (internal/process/task_queues.js:97:5)
      2021-01-18 00:00:14.506 - error: dwd.0 (5122) Cannot read property 'setState' of null
      2021-01-18 00:00:14.511 - error: dwd.0 (5122) 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().
      2021-01-18 00:00:14.513 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
      2021-01-18 00:00:14.515 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
      at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
      at processTicksAndRejections (internal/process/task_queues.js:97:5)
      2021-01-18 00:00:14.515 - error: dwd.0 (5122) Cannot read property 'setState' of null
      2021-01-18 00:00:14.520 - error: dwd.0 (5122) 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().
      2021-01-18 00:00:14.520 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
      2021-01-18 00:00:14.521 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
      at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
      at processTicksAndRejections (internal/process/task_queues.js:97:5)
      2021-01-18 00:00:14.522 - error: dwd.0 (5122) Cannot read property 'setState' of null
      2021-01-18 00:00:14.531 - error: dwd.0 (5122) 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().
      2021-01-18 00:00:14.532 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
      2021-01-18 00:00:14.544 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
      at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
      at processTicksAndRejections (internal/process/task_queues.js:97:5)
      2021-01-18 00:00:14.545 - error: dwd.0 (5122) Cannot read property 'setState' of null
      2021-01-18 00:00:14.555 - error: dwd.0 (5122) 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().
      2021-01-18 00:00:14.556 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
      2021-01-18 00:00:14.557 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
      at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
      at processTicksAndRejections (internal/process/task_queues.js:97:5)
      2021-01-18 00:00:14.558 - error: dwd.0 (5122) Cannot read property 'setState' of null
      2021-01-18 00:00:14.588 - error: dwd.0 (5122) 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().
      2021-01-18 00:00:14.590 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
      2021-01-18 00:00:14.591 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
      at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
      at processTicksAndRejections (internal/process/task_queues.js:97:5)
      2021-01-18 00:00:14.592 - error: dwd.0 (5122) Cannot read property 'setState' of null
      2021-01-18 00:00:14.606 - error: dwd.0 (5122) 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().
      2021-01-18 00:00:14.607 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
      2021-01-18 00:00:14.608 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
      at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
      at processTicksAndRejections (internal/process/task_queues.js:97:5)
      2021-01-18 00:00:14.609 - error: dwd.0 (5122) Cannot read property 'setState' of null
      2021-01-18 00:00:14.618 - error: dwd.0 (5122) 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().
      2021-01-18 00:00:14.619 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
      2021-01-18 00:00:14.622 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
      at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
      at processTicksAndRejections (internal/process/task_queues.js:97:5)
      2021-01-18 00:00:14.622 - error: dwd.0 (5122) Cannot read property 'setState' of null
      2021-01-18 00:00:14.628 - error: dwd.0 (5122) 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().
      2021-01-18 00:00:14.629 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
      2021-01-18 00:00:14.632 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
      at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
      at processTicksAndRejections (internal/process/task_queues.js:97:5)
      2021-01-18 00:00:14.633 - error: dwd.0 (5122) Cannot read property 'setState' of null
      2021-01-18 00:00:14.637 - error: dwd.0 (5122) 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().
      2021-01-18 00:00:14.640 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
      2021-01-18 00:00:14.642 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
      at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
      at processTicksAndRejections (internal/process/task_queues.js:97:5)
      2021-01-18 00:00:14.644 - error: dwd.0 (5122) Cannot read property 'setState' of null
      2021-01-18 00:00:14.664 - error: dwd.0 (5122) 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().
      2021-01-18 00:00:14.665 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
      2021-01-18 00:00:14.667 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
      at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
      at processTicksAndRejections (internal/process/task_queues.js:97:5)
      2021-01-18 00:00:14.670 - error: dwd.0 (5122) Cannot read property 'setState' of null
      2021-01-18 00:00:14.678 - error: dwd.0 (5122) 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().
      2021-01-18 00:00:14.679 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
      2021-01-18 00:00:14.681 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
      at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
      at processTicksAndRejections (internal/process/task_queues.js:97:5)
      2021-01-18 00:00:14.692 - error: dwd.0 (5122) Cannot read property 'setState' of null
      2021-01-18 00:00:14.699 - error: dwd.0 (5122) 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().
      2021-01-18 00:00:14.700 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
      2021-01-18 00:00:14.702 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
      at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
      at processTicksAndRejections (internal/process/task_queues.js:97:5)
      2021-01-18 00:00:14.703 - error: dwd.0 (5122) Cannot read property 'setState' of null
      2021-01-18 00:00:14.812 - error: dwd.0 (5122) 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().
      2021-01-18 00:00:14.812 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
      2021-01-18 00:00:14.814 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
      at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
      at processTicksAndRejections (internal/process/task_queues.js:97:5)
      2021-01-18 00:00:14.831 - error: dwd.0 (5122) Cannot read property 'setState' of null
      2021-01-18 00:00:14.836 - error: dwd.0 (5122) 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().
      2021-01-18 00:00:14.837 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
      2021-01-18 00:00:14.838 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
      at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
      at processTicksAndRejections (internal/process/task_queues.js:97:5)
      2021-01-18 00:00:14.839 - error: dwd.0 (5122) Cannot read property 'setState' of null
      2021-01-18 00:00:14.844 - error: dwd.0 (5122) 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().
      2021-01-18 00:00:14.845 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
      2021-01-18 00:00:14.846 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
      at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
      at processTicksAndRejections (internal/process/task_queues.js:97:5)
      2021-01-18 00:00:14.847 - error: dwd.0 (5122) Cannot read property 'setState' of null
      2021-01-18 00:00:14.852 - error: dwd.0 (5122) 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().
      2021-01-18 00:00:14.853 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
      2021-01-18 00:00:14.855 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
      at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
      at processTicksAndRejections (internal/process/task_queues.js:97:5)
      2021-01-18 00:00:14.856 - error: dwd.0 (5122) Cannot read property 'setState' of null
      2021-01-18 00:00:14.862 - error: dwd.0 (5122) 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().
      2021-01-18 00:00:14.863 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
      2021-01-18 00:00:14.864 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
      at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
      at processTicksAndRejections (internal/process/task_queues.js:97:5)
      2021-01-18 00:00:14.865 - error: dwd.0 (5122) Cannot read property 'setState' of null
      2021-01-18 00:00:14.870 - error: dwd.0 (5122) 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().
      2021-01-18 00:00:14.871 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
      2021-01-18 00:00:14.872 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
      at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
      at processTicksAndRejections (internal/process/task_queues.js:97:5)
      2021-01-18 00:00:14.873 - error: dwd.0 (5122) Cannot read property 'setState' of null
      2021-01-18 00:00:14.877 - error: dwd.0 (5122) 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().
      2021-01-18 00:00:14.878 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
      2021-01-18 00:00:14.879 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
      at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
      at processTicksAndRejections (internal/process/task_queues.js:97:5)
      2021-01-18 00:00:14.880 - error: dwd.0 (5122) Cannot read property 'setState' of null
      2021-01-18 00:00:14.893 - error: dwd.0 (5122) 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().
      2021-01-18 00:00:14.894 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
      2021-01-18 00:00:14.907 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
      at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
      at processTicksAndRejections (internal/process/task_queues.js:97:5)
      2021-01-18 00:00:14.908 - error: dwd.0 (5122) Cannot read property 'setState' of null
      2021-01-18 00:00:14.915 - error: dwd.0 (5122) 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().
      2021-01-18 00:00:14.916 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
      2021-01-18 00:00:14.917 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
      at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
      at processTicksAndRejections (internal/process/task_queues.js:97:5)
      2021-01-18 00:00:14.918 - error: dwd.0 (5122) Cannot read property 'setState' of null
      2021-01-18 00:00:14.929 - error: dwd.0 (5122) 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().
      2021-01-18 00:00:14.929 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
      2021-01-18 00:00:14.934 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
      at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
      at processTicksAndRejections (internal/process/task_queues.js:97:5)
      2021-01-18 00:00:14.935 - error: dwd.0 (5122) Cannot read property 'setState' of null
      2021-01-18 00:00:14.940 - error: dwd.0 (5122) 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().
      2021-01-18 00:00:14.940 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
      2021-01-18 00:00:14.942 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
      at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
      at processTicksAndRejections (internal/process/task_queues.js:97:5)
      2021-01-18 00:00:14.943 - error: dwd.0 (5122) Cannot read property 'setState' of null
      2021-01-18 00:00:14.952 - error: dwd.0 (5122) 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().
      2021-01-18 00:00:14.953 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
      2021-01-18 00:00:14.955 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
      at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
      at processTicksAndRejections (internal/process/task_queues.js:97:5)
      2021-01-18 00:00:14.955 - error: dwd.0 (5122) Cannot read property 'setState' of null
      2021-01-18 00:00:14.965 - error: dwd.0 (5122) 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().
      2021-01-18 00:00:14.971 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
      2021-01-18 00:00:14.972 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
      at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
      at processTicksAndRejections (internal/process/task_queues.js:97:5)
      2021-01-18 00:00:14.973 - error: dwd.0 (5122) Cannot read property 'setState' of null
      2021-01-18 00:00:14.994 - error: dwd.0 (5122) 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().
      2021-01-18 00:00:14.995 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
      2021-01-18 00:00:14.996 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
      at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
      at processTicksAndRejections (internal/process/task_queues.js:97:5)
      2021-01-18 00:00:14.997 - error: dwd.0 (5122) Cannot read property 'setState' of null
      2021-01-18 00:00:15.028 - error: dwd.0 (5122) 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().
      2021-01-18 00:00:15.029 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
      2021-01-18 00:00:15.030 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
      at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
      at processTicksAndRejections (internal/process/task_queues.js:97:5)
      2021-01-18 00:00:15.031 - error: dwd.0 (5122) Cannot read property 'setState' of null
      

      Woran liegts? controller oder Adapter?

      apollon77A Offline
      apollon77A Offline
      apollon77
      schrieb am zuletzt editiert von
      #46

      @prinzeisenherz1 Bitte mal die dwd Github version versuchen. Besser? Habe da im Adapter etwas nachgearbeitet

      Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

      • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
      • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
      P FeuersturmF 2 Antworten Letzte Antwort
      0
      • apollon77A apollon77

        @prinzeisenherz1 Bitte mal die dwd Github version versuchen. Besser? Habe da im Adapter etwas nachgearbeitet

        P Offline
        P Offline
        PrinzEisenherz1
        schrieb am zuletzt editiert von
        #47

        @apollon77 probier ich später. Brauche jetzt n Bett. 🥱

        Intel-NUC mit ProxMox: ioBroker,SQL, logging Strom- Gas- u. Wasserzähler;10Zoll Tab im Flur für VIS; weiteres: Homematic CCU2, Homeduino, Kameras, selbstgebaute Wetterstation;

        JayRJ 1 Antwort Letzte Antwort
        0
        • P PrinzEisenherz1

          @apollon77 probier ich später. Brauche jetzt n Bett. 🥱

          JayRJ Offline
          JayRJ Offline
          JayR
          schrieb am zuletzt editiert von
          #48

          Ich bekomme folgenden Fehler angezeigt und iobroker startet nicht mehr.

          2021-01-18 07:14:34.463  - error: host.Collector Cannot read property 'storeNotifications' of undefined
          Cannot read property 'storeNotifications' of undefined
          TypeError: Cannot read property 'storeNotifications' of undefined
              at /opt/iobroker/node_modules/iobroker.js-controller/main.js:4264:29
              at stopInstances (/opt/iobroker/node_modules/iobroker.js-controller/main.js:4225:43)
              at stop (/opt/iobroker/node_modules/iobroker.js-controller/main.js:4262:5)
              at process.<anonymous> (/opt/iobroker/node_modules/iobroker.js-controller/main.js:4619:9)
              at process.emit (events.js:314:20)
          2021-01-18 07:14:34.468  - error: host.Collector uncaught exception: Cannot read property 'storeNotifications' of undefined
          2021-01-18 07:14:34.469  - error: host.Collector TypeError: Cannot read property 'storeNotifications' of undefined
              at /opt/iobroker/node_modules/iobroker.js-controller/main.js:4264:29
              at stopInstances (/opt/iobroker/node_modules/iobroker.js-controller/main.js:4225:43)
              at stop (/opt/iobroker/node_modules/iobroker.js-controller/main.js:4262:5)
              at process.<anonymous> (/opt/iobroker/node_modules/iobroker.js-controller/main.js:4619:9)
              at process.emit (events.js:314:20)
          2021-01-18 07:14:34.478  - error: host.Collector Cannot read property 'storeNotifications' of undefined
          /opt/iobroker/node_modules/iobroker.js-controller/main.js:4264
                  notificationHandler.storeNotifications();
                                      ^
          
          TypeError: Cannot read property 'storeNotifications' of undefined
              at /opt/iobroker/node_modules/iobroker.js-controller/main.js:4264:29
              at stopInstances (/opt/iobroker/node_modules/iobroker.js-controller/main.js:4225:43)
              at stop (/opt/iobroker/node_modules/iobroker.js-controller/main.js:4262:5)
              at process.exceptionHandler (/opt/iobroker/node_modules/iobroker.js-controller/main.js:4612:9)
              at process.emit (events.js:314:20)
              at process._fatalException (internal/process/execution.js:165:25)
          
          
          apollon77A 1 Antwort Letzte Antwort
          0
          • JayRJ JayR

            Ich bekomme folgenden Fehler angezeigt und iobroker startet nicht mehr.

            2021-01-18 07:14:34.463  - error: host.Collector Cannot read property 'storeNotifications' of undefined
            Cannot read property 'storeNotifications' of undefined
            TypeError: Cannot read property 'storeNotifications' of undefined
                at /opt/iobroker/node_modules/iobroker.js-controller/main.js:4264:29
                at stopInstances (/opt/iobroker/node_modules/iobroker.js-controller/main.js:4225:43)
                at stop (/opt/iobroker/node_modules/iobroker.js-controller/main.js:4262:5)
                at process.<anonymous> (/opt/iobroker/node_modules/iobroker.js-controller/main.js:4619:9)
                at process.emit (events.js:314:20)
            2021-01-18 07:14:34.468  - error: host.Collector uncaught exception: Cannot read property 'storeNotifications' of undefined
            2021-01-18 07:14:34.469  - error: host.Collector TypeError: Cannot read property 'storeNotifications' of undefined
                at /opt/iobroker/node_modules/iobroker.js-controller/main.js:4264:29
                at stopInstances (/opt/iobroker/node_modules/iobroker.js-controller/main.js:4225:43)
                at stop (/opt/iobroker/node_modules/iobroker.js-controller/main.js:4262:5)
                at process.<anonymous> (/opt/iobroker/node_modules/iobroker.js-controller/main.js:4619:9)
                at process.emit (events.js:314:20)
            2021-01-18 07:14:34.478  - error: host.Collector Cannot read property 'storeNotifications' of undefined
            /opt/iobroker/node_modules/iobroker.js-controller/main.js:4264
                    notificationHandler.storeNotifications();
                                        ^
            
            TypeError: Cannot read property 'storeNotifications' of undefined
                at /opt/iobroker/node_modules/iobroker.js-controller/main.js:4264:29
                at stopInstances (/opt/iobroker/node_modules/iobroker.js-controller/main.js:4225:43)
                at stop (/opt/iobroker/node_modules/iobroker.js-controller/main.js:4262:5)
                at process.exceptionHandler (/opt/iobroker/node_modules/iobroker.js-controller/main.js:4612:9)
                at process.emit (events.js:314:20)
                at process._fatalException (internal/process/execution.js:165:25)
            
            
            apollon77A Offline
            apollon77A Offline
            apollon77
            schrieb am zuletzt editiert von
            #49

            @jayr Interessant, da fliegt bei die scheinbar mega früh irgendeine exception. versuch bitte nochmal drüber zu installieren

            Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

            • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
            • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
            JayRJ 1 Antwort Letzte Antwort
            0
            • apollon77A apollon77

              @jayr Interessant, da fliegt bei die scheinbar mega früh irgendeine exception. versuch bitte nochmal drüber zu installieren

              JayRJ Offline
              JayRJ Offline
              JayR
              schrieb am zuletzt editiert von
              #50

              @apollon77 said in js-controller 3.2 jetzt im Latest!:

              @jayr Interessant, da fliegt bei die scheinbar mega früh irgendeine exception. versuch bitte nochmal drüber zu installieren

              Also es lief die Ganze Zeit ohne Probleme (Habe gestern morgen geupdated). Der Fehler ist heute morgen gekommen nachdem ich ein Adapter installiert hab.

              apollon77A Master67M 2 Antworten Letzte Antwort
              0
              • JayRJ JayR

                @apollon77 said in js-controller 3.2 jetzt im Latest!:

                @jayr Interessant, da fliegt bei die scheinbar mega früh irgendeine exception. versuch bitte nochmal drüber zu installieren

                Also es lief die Ganze Zeit ohne Probleme (Habe gestern morgen geupdated). Der Fehler ist heute morgen gekommen nachdem ich ein Adapter installiert hab.

                apollon77A Offline
                apollon77A Offline
                apollon77
                schrieb am zuletzt editiert von
                #51

                @jayr Ok, dann bitte mehr log ... das fehlt halt. Es kam also aus dem cli Kommando oder wie wann genau? oder ist der ganze COntroller gecraht?

                Aber hab schon nen Fix der mit der 3.2.8 heute abend vorauss kommt.

                Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

                • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
                • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
                JayRJ 1 Antwort Letzte Antwort
                0
                • JayRJ JayR

                  @apollon77 said in js-controller 3.2 jetzt im Latest!:

                  @jayr Interessant, da fliegt bei die scheinbar mega früh irgendeine exception. versuch bitte nochmal drüber zu installieren

                  Also es lief die Ganze Zeit ohne Probleme (Habe gestern morgen geupdated). Der Fehler ist heute morgen gekommen nachdem ich ein Adapter installiert hab.

                  Master67M Offline
                  Master67M Offline
                  Master67
                  schrieb am zuletzt editiert von
                  #52

                  Läuft bei mir nicht... bekomme X-Fehlermeldungen (leider konnte ich die nicht speichern, lade eine Sicherung und dann habe ich die Meldungen), nur soviel, die Vis ging noch ein Einlogen per IP und Port ging nicht mehr!

                  Gruß Master67

                  apollon77A 1 Antwort Letzte Antwort
                  0
                  • Master67M Master67

                    Läuft bei mir nicht... bekomme X-Fehlermeldungen (leider konnte ich die nicht speichern, lade eine Sicherung und dann habe ich die Meldungen), nur soviel, die Vis ging noch ein Einlogen per IP und Port ging nicht mehr!

                    apollon77A Offline
                    apollon77A Offline
                    apollon77
                    schrieb am zuletzt editiert von
                    #53

                    @master67 Jupp mehr Infos bitte. Bist der erste der solche Probleme hat :-))

                    Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

                    • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
                    • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
                    Master67M 2 Antworten Letzte Antwort
                    0
                    • apollon77A apollon77

                      @jayr Ok, dann bitte mehr log ... das fehlt halt. Es kam also aus dem cli Kommando oder wie wann genau? oder ist der ganze COntroller gecraht?

                      Aber hab schon nen Fix der mit der 3.2.8 heute abend vorauss kommt.

                      JayRJ Offline
                      JayRJ Offline
                      JayR
                      schrieb am zuletzt editiert von
                      #54

                      @apollon77 said in js-controller 3.2 jetzt im Latest!:

                      @jayr Ok, dann bitte mehr log ... das fehlt halt. Es kam also aus dem cli Kommando oder wie wann genau? oder ist der ganze COntroller gecraht?

                      Aber hab schon nen Fix der mit der 3.2.8 heute abend vorauss kommt.

                      Kam aus dem CLI Kommand. Mehr wurde nicht angezeigt. Welches Log brauchst du genau?

                      Der Controller lief noch bin nur nicht mehr auf de WebUi gekommen.

                      apollon77A 1 Antwort Letzte Antwort
                      0
                      • JayRJ JayR

                        @apollon77 said in js-controller 3.2 jetzt im Latest!:

                        @jayr Ok, dann bitte mehr log ... das fehlt halt. Es kam also aus dem cli Kommando oder wie wann genau? oder ist der ganze COntroller gecraht?

                        Aber hab schon nen Fix der mit der 3.2.8 heute abend vorauss kommt.

                        Kam aus dem CLI Kommand. Mehr wurde nicht angezeigt. Welches Log brauchst du genau?

                        Der Controller lief noch bin nur nicht mehr auf de WebUi gekommen.

                        apollon77A Offline
                        apollon77A Offline
                        apollon77
                        schrieb am zuletzt editiert von
                        #55

                        @jayr Restarte mal controller sodass wieder alles geht. und dann versuch später ob es mit der 3.2.8 noch passiert

                        Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

                        • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
                        • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
                        1 Antwort Letzte Antwort
                        0
                        • apollon77A apollon77

                          @master67 Jupp mehr Infos bitte. Bist der erste der solche Probleme hat :-))

                          Master67M Offline
                          Master67M Offline
                          Master67
                          schrieb am zuletzt editiert von
                          #56

                          @apollon77 sagte in js-controller 3.2 jetzt im Latest!:

                          @master67 Jupp mehr Infos bitte. Bist der erste der solche Probleme hat :-))

                          Mache ich wenn der ioBroker wieder läuft... spiele doch grade eine Sicherung ein ;-)

                          Gruß Master67

                          1 Antwort Letzte Antwort
                          0
                          • apollon77A apollon77

                            @master67 Jupp mehr Infos bitte. Bist der erste der solche Probleme hat :-))

                            Master67M Offline
                            Master67M Offline
                            Master67
                            schrieb am zuletzt editiert von
                            #57

                            @apollon77 so hier mal die Fehlermeldung die ich erhalte :-)

                            Update js-controller from @3.1.6 to @3.2.7
                            NPM version: 6.14.10
                            npm install iobroker.js-controller@3.2.7 --loglevel error --unsafe-perm --prefix "/opt/iobroker" (System call)
                            In file included from ../authenticate_pam.cc:23:
                            ../../nan/nan.h: In function 'void Nan::AsyncQueueWorker(Nan::AsyncWorker*)':
                            ../../nan/nan.h:2294:62: warning: cast between incompatible function types from 'void (*)(uv_work_t*)' {aka 'void (*)(uv_work_s*)'} to 'uv_after_work_cb' {aka 'void (*)(uv_work_s*, int)'} [-Wcast-function-type]
                             2294 |     , reinterpret_cast<uv_after_work_cb>(AsyncExecuteComplete)
                                  |                                                              ^
                            ../authenticate_pam.cc: In function 'void after_doing_auth(uv_work_t*, int)':
                            ../authenticate_pam.cc:107:87: warning: 'v8::Local<v8::Value> Nan::MakeCallback(v8::Local<v8::Object>, v8::Local<v8::Function>, int, v8::Local<v8::Value>*)' is deprecated [-Wdeprecated-declarations]
                              107 |   Nan::MakeCallback(Nan::GetCurrentContext()->Global(), Nan::New(m->callback), 1, args);
                                  |                                                                                       ^
                            In file included from ../authenticate_pam.cc:23:
                            ../../nan/nan.h:1026:46: note: declared here
                             1026 |   NAN_DEPRECATED inline v8::Local<v8::Value> MakeCallback(
                                  |                                              ^~~~~~~~~~~~
                            ../authenticate_pam.cc:107:87: warning: 'v8::Local<v8::Value> Nan::MakeCallback(v8::Local<v8::Object>, v8::Local<v8::Function>, int, v8::Local<v8::Value>*)' is deprecated [-Wdeprecated-declarations]
                              107 |   Nan::MakeCallback(Nan::GetCurrentContext()->Global(), Nan::New(m->callback), 1, args);
                                  |                                                                                       ^
                            In file included from ../authenticate_pam.cc:23:
                            ../../nan/nan.h:1026:46: note: declared here
                             1026 |   NAN_DEPRECATED inline v8::Local<v8::Value> MakeCallback(
                                  |                                              ^~~~~~~~~~~~
                            ../authenticate_pam.cc: In function 'Nan::NAN_METHOD_RETURN_TYPE Authenticate(Nan::NAN_METHOD_ARGS_TYPE)':
                            ../authenticate_pam.cc:147:83: warning: 'v8::Local<v8::Value> v8::Object::Get(v8::Local<v8::Value>)' is deprecated: Use maybe version [-Wdeprecated-declarations]
                              147 |   Local<Value> res = options->Get(Nan::New<String>("serviceName").ToLocalChecked());
                                  |                                                                                   ^
                            In file included from /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8-internal.h:14,
                                             from /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8.h:27,
                                             from /home/iobroker/.cache/node-gyp/12.20.1/include/node/node.h:67,
                                             from ../../nan/nan.h:56,
                                             from ../authenticate_pam.cc:23:
                            /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8.h:3553:51: note: declared here
                             3553 |   V8_DEPRECATED("Use maybe version", Local<Value> Get(Local<Value> key));
                                  |                                                   ^~~
                            /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8config.h:328:3: note: in definition of macro 'V8_DEPRECATED'
                              328 |   declarator __attribute__((deprecated(message)))
                                  |   ^~~~~~~~~~
                            ../authenticate_pam.cc:150:30: error: cannot convert 'char [128]' to 'v8::Isolate*'
                              150 |    serviceName->WriteUtf8(m->serviceName, sizeof(m->serviceName) - 1);
                                  |                           ~~~^~~~~~~~~~~
                                  |                              |
                                  |                              char [128]
                            In file included from /home/iobroker/.cache/node-gyp/12.20.1/include/node/node.h:67,
                                             from ../../nan/nan.h:56,
                                             from ../authenticate_pam.cc:23:
                            /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8.h:2878:26: note:   initializing argument 1 of 'int v8::String::WriteUtf8(v8::Isolate*, char*, int, int*, int) const'
                             2878 |   int WriteUtf8(Isolate* isolate, char* buffer, int length = -1,
                                  |                 ~~~~~~~~~^~~~~~~
                            ../authenticate_pam.cc:152:69: warning: 'v8::Local<v8::Value> v8::Object::Get(v8::Local<v8::Value>)' is deprecated: Use maybe version [-Wdeprecated-declarations]
                              152 |   res = options->Get(Nan::New<String>("remoteHost").ToLocalChecked());
                                  |                                                                     ^
                            In file included from /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8-internal.h:14,
                                             from /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8.h:27,
                                             from /home/iobroker/.cache/node-gyp/12.20.1/include/node/node.h:67,
                                             from ../../nan/nan.h:56,
                                             from ../authenticate_pam.cc:23:
                            /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8.h:3553:51: note: declared here
                             3553 |   V8_DEPRECATED("Use maybe version", Local<Value> Get(Local<Value> key));
                                  |                                                   ^~~
                            /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8config.h:328:3: note: in definition of macro 'V8_DEPRECATED'
                              328 |   declarator __attribute__((deprecated(message)))
                                  |   ^~~~~~~~~~
                            ../authenticate_pam.cc:155:29: error: cannot convert 'char [128]' to 'v8::Isolate*'
                              155 |    remoteHost->WriteUtf8(m->remoteHost, sizeof(m->remoteHost) - 1);
                                  |                          ~~~^~~~~~~~~~
                                  |                             |
                                  |                             char [128]
                            In file included from /home/iobroker/.cache/node-gyp/12.20.1/include/node/node.h:67,
                                             from ../../nan/nan.h:56,
                                             from ../authenticate_pam.cc:23:
                            /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8.h:2878:26: note:   initializing argument 1 of 'int v8::String::WriteUtf8(v8::Isolate*, char*, int, int*, int) const'
                             2878 |   int WriteUtf8(Isolate* isolate, char* buffer, int length = -1,
                                  |                 ~~~~~~~~~^~~~~~~
                            ../authenticate_pam.cc:160:25: error: cannot convert 'char [128]' to 'v8::Isolate*'
                              160 |  username->WriteUtf8(m->username, sizeof(m->username) - 1);
                                  |                      ~~~^~~~~~~~
                                  |                         |
                                  |                         char [128]
                            In file included from /home/iobroker/.cache/node-gyp/12.20.1/include/node/node.h:67,
                                             from ../../nan/nan.h:56,
                                             from ../authenticate_pam.cc:23:
                            /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8.h:2878:26: note:   initializing argument 1 of 'int v8::String::WriteUtf8(v8::Isolate*, char*, int, int*, int) const'
                             2878 |   int WriteUtf8(Isolate* isolate, char* buffer, int length = -1,
                                  |                 ~~~~~~~~~^~~~~~~
                            ../authenticate_pam.cc:161:25: error: cannot convert 'char [128]' to 'v8::Isolate*'
                              161 |  password->WriteUtf8(m->password, sizeof(m->password) - 1);
                                  |                      ~~~^~~~~~~~
                                  |                         |
                                  |                         char [128]
                            In file included from /home/iobroker/.cache/node-gyp/12.20.1/include/node/node.h:67,
                                             from ../../nan/nan.h:56,
                                             from ../authenticate_pam.cc:23:
                            /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8.h:2878:26: note:   initializing argument 1 of 'int v8::String::WriteUtf8(v8::Isolate*, char*, int, int*, int) const'
                             2878 |   int WriteUtf8(Isolate* isolate, char* buffer, int length = -1,
                                  |                 ~~~~~~~~~^~~~~~~
                            ../authenticate_pam.cc: At global scope:
                            ../authenticate_pam.cc:170:11: error: variable or field 'init' declared void
                              170 | void init(Handle<Object> exports) {
                                  |           ^~~~~~
                            ../authenticate_pam.cc:170:11: error: 'Handle' was not declared in this scope
                            ../authenticate_pam.cc:170:24: error: expected primary-expression before '>' token
                              170 | void init(Handle<Object> exports) {
                                  |                        ^
                            ../authenticate_pam.cc:170:26: error: 'exports' was not declared in this scope
                              170 | void init(Handle<Object> exports) {
                                  |                          ^~~~~~~
                            In file included from ../../nan/nan.h:56,
                                             from ../authenticate_pam.cc:23:
                            ../authenticate_pam.cc:175:31: error: 'init' was not declared in this scope; did you mean 'int'?
                              175 | NODE_MODULE(authenticate_pam, init);
                                  |                               ^~~~
                            /home/iobroker/.cache/node-gyp/12.20.1/include/node/node.h:737:36: note: in definition of macro 'NODE_MODULE_X'
                              737 |       (node::addon_register_func) (regfunc),                          \
                                  |                                    ^~~~~~~
                            ../authenticate_pam.cc:175:1: note: in expansion of macro 'NODE_MODULE'
                              175 | NODE_MODULE(authenticate_pam, init);
                                  | ^~~~~~~~~~~
                            make: *** [authenticate_pam.target.mk:111: Release/obj.target/authenticate_pam/authenticate_pam.o] Error 1
                            gyp ERR! build error 
                            gyp ERR! stack Error: `make` failed with exit code: 2
                            gyp ERR! stack     at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:194:23)
                            gyp ERR! stack     at ChildProcess.emit (events.js:314:20)
                            gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:276:12)
                            gyp ERR! System Linux 5.4.78-2-pve
                            gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
                            gyp ERR! cwd /opt/iobroker/node_modules/authenticate-pam
                            gyp ERR! node -v v12.20.1
                            gyp ERR! node-gyp -v v5.1.0
                            gyp ERR! not ok 
                            Starting node restart.js
                            

                            Gruß Master67

                            apollon77A 1 Antwort Letzte Antwort
                            0
                            • Master67M Master67

                              @apollon77 so hier mal die Fehlermeldung die ich erhalte :-)

                              Update js-controller from @3.1.6 to @3.2.7
                              NPM version: 6.14.10
                              npm install iobroker.js-controller@3.2.7 --loglevel error --unsafe-perm --prefix "/opt/iobroker" (System call)
                              In file included from ../authenticate_pam.cc:23:
                              ../../nan/nan.h: In function 'void Nan::AsyncQueueWorker(Nan::AsyncWorker*)':
                              ../../nan/nan.h:2294:62: warning: cast between incompatible function types from 'void (*)(uv_work_t*)' {aka 'void (*)(uv_work_s*)'} to 'uv_after_work_cb' {aka 'void (*)(uv_work_s*, int)'} [-Wcast-function-type]
                               2294 |     , reinterpret_cast<uv_after_work_cb>(AsyncExecuteComplete)
                                    |                                                              ^
                              ../authenticate_pam.cc: In function 'void after_doing_auth(uv_work_t*, int)':
                              ../authenticate_pam.cc:107:87: warning: 'v8::Local<v8::Value> Nan::MakeCallback(v8::Local<v8::Object>, v8::Local<v8::Function>, int, v8::Local<v8::Value>*)' is deprecated [-Wdeprecated-declarations]
                                107 |   Nan::MakeCallback(Nan::GetCurrentContext()->Global(), Nan::New(m->callback), 1, args);
                                    |                                                                                       ^
                              In file included from ../authenticate_pam.cc:23:
                              ../../nan/nan.h:1026:46: note: declared here
                               1026 |   NAN_DEPRECATED inline v8::Local<v8::Value> MakeCallback(
                                    |                                              ^~~~~~~~~~~~
                              ../authenticate_pam.cc:107:87: warning: 'v8::Local<v8::Value> Nan::MakeCallback(v8::Local<v8::Object>, v8::Local<v8::Function>, int, v8::Local<v8::Value>*)' is deprecated [-Wdeprecated-declarations]
                                107 |   Nan::MakeCallback(Nan::GetCurrentContext()->Global(), Nan::New(m->callback), 1, args);
                                    |                                                                                       ^
                              In file included from ../authenticate_pam.cc:23:
                              ../../nan/nan.h:1026:46: note: declared here
                               1026 |   NAN_DEPRECATED inline v8::Local<v8::Value> MakeCallback(
                                    |                                              ^~~~~~~~~~~~
                              ../authenticate_pam.cc: In function 'Nan::NAN_METHOD_RETURN_TYPE Authenticate(Nan::NAN_METHOD_ARGS_TYPE)':
                              ../authenticate_pam.cc:147:83: warning: 'v8::Local<v8::Value> v8::Object::Get(v8::Local<v8::Value>)' is deprecated: Use maybe version [-Wdeprecated-declarations]
                                147 |   Local<Value> res = options->Get(Nan::New<String>("serviceName").ToLocalChecked());
                                    |                                                                                   ^
                              In file included from /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8-internal.h:14,
                                               from /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8.h:27,
                                               from /home/iobroker/.cache/node-gyp/12.20.1/include/node/node.h:67,
                                               from ../../nan/nan.h:56,
                                               from ../authenticate_pam.cc:23:
                              /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8.h:3553:51: note: declared here
                               3553 |   V8_DEPRECATED("Use maybe version", Local<Value> Get(Local<Value> key));
                                    |                                                   ^~~
                              /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8config.h:328:3: note: in definition of macro 'V8_DEPRECATED'
                                328 |   declarator __attribute__((deprecated(message)))
                                    |   ^~~~~~~~~~
                              ../authenticate_pam.cc:150:30: error: cannot convert 'char [128]' to 'v8::Isolate*'
                                150 |    serviceName->WriteUtf8(m->serviceName, sizeof(m->serviceName) - 1);
                                    |                           ~~~^~~~~~~~~~~
                                    |                              |
                                    |                              char [128]
                              In file included from /home/iobroker/.cache/node-gyp/12.20.1/include/node/node.h:67,
                                               from ../../nan/nan.h:56,
                                               from ../authenticate_pam.cc:23:
                              /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8.h:2878:26: note:   initializing argument 1 of 'int v8::String::WriteUtf8(v8::Isolate*, char*, int, int*, int) const'
                               2878 |   int WriteUtf8(Isolate* isolate, char* buffer, int length = -1,
                                    |                 ~~~~~~~~~^~~~~~~
                              ../authenticate_pam.cc:152:69: warning: 'v8::Local<v8::Value> v8::Object::Get(v8::Local<v8::Value>)' is deprecated: Use maybe version [-Wdeprecated-declarations]
                                152 |   res = options->Get(Nan::New<String>("remoteHost").ToLocalChecked());
                                    |                                                                     ^
                              In file included from /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8-internal.h:14,
                                               from /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8.h:27,
                                               from /home/iobroker/.cache/node-gyp/12.20.1/include/node/node.h:67,
                                               from ../../nan/nan.h:56,
                                               from ../authenticate_pam.cc:23:
                              /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8.h:3553:51: note: declared here
                               3553 |   V8_DEPRECATED("Use maybe version", Local<Value> Get(Local<Value> key));
                                    |                                                   ^~~
                              /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8config.h:328:3: note: in definition of macro 'V8_DEPRECATED'
                                328 |   declarator __attribute__((deprecated(message)))
                                    |   ^~~~~~~~~~
                              ../authenticate_pam.cc:155:29: error: cannot convert 'char [128]' to 'v8::Isolate*'
                                155 |    remoteHost->WriteUtf8(m->remoteHost, sizeof(m->remoteHost) - 1);
                                    |                          ~~~^~~~~~~~~~
                                    |                             |
                                    |                             char [128]
                              In file included from /home/iobroker/.cache/node-gyp/12.20.1/include/node/node.h:67,
                                               from ../../nan/nan.h:56,
                                               from ../authenticate_pam.cc:23:
                              /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8.h:2878:26: note:   initializing argument 1 of 'int v8::String::WriteUtf8(v8::Isolate*, char*, int, int*, int) const'
                               2878 |   int WriteUtf8(Isolate* isolate, char* buffer, int length = -1,
                                    |                 ~~~~~~~~~^~~~~~~
                              ../authenticate_pam.cc:160:25: error: cannot convert 'char [128]' to 'v8::Isolate*'
                                160 |  username->WriteUtf8(m->username, sizeof(m->username) - 1);
                                    |                      ~~~^~~~~~~~
                                    |                         |
                                    |                         char [128]
                              In file included from /home/iobroker/.cache/node-gyp/12.20.1/include/node/node.h:67,
                                               from ../../nan/nan.h:56,
                                               from ../authenticate_pam.cc:23:
                              /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8.h:2878:26: note:   initializing argument 1 of 'int v8::String::WriteUtf8(v8::Isolate*, char*, int, int*, int) const'
                               2878 |   int WriteUtf8(Isolate* isolate, char* buffer, int length = -1,
                                    |                 ~~~~~~~~~^~~~~~~
                              ../authenticate_pam.cc:161:25: error: cannot convert 'char [128]' to 'v8::Isolate*'
                                161 |  password->WriteUtf8(m->password, sizeof(m->password) - 1);
                                    |                      ~~~^~~~~~~~
                                    |                         |
                                    |                         char [128]
                              In file included from /home/iobroker/.cache/node-gyp/12.20.1/include/node/node.h:67,
                                               from ../../nan/nan.h:56,
                                               from ../authenticate_pam.cc:23:
                              /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8.h:2878:26: note:   initializing argument 1 of 'int v8::String::WriteUtf8(v8::Isolate*, char*, int, int*, int) const'
                               2878 |   int WriteUtf8(Isolate* isolate, char* buffer, int length = -1,
                                    |                 ~~~~~~~~~^~~~~~~
                              ../authenticate_pam.cc: At global scope:
                              ../authenticate_pam.cc:170:11: error: variable or field 'init' declared void
                                170 | void init(Handle<Object> exports) {
                                    |           ^~~~~~
                              ../authenticate_pam.cc:170:11: error: 'Handle' was not declared in this scope
                              ../authenticate_pam.cc:170:24: error: expected primary-expression before '>' token
                                170 | void init(Handle<Object> exports) {
                                    |                        ^
                              ../authenticate_pam.cc:170:26: error: 'exports' was not declared in this scope
                                170 | void init(Handle<Object> exports) {
                                    |                          ^~~~~~~
                              In file included from ../../nan/nan.h:56,
                                               from ../authenticate_pam.cc:23:
                              ../authenticate_pam.cc:175:31: error: 'init' was not declared in this scope; did you mean 'int'?
                                175 | NODE_MODULE(authenticate_pam, init);
                                    |                               ^~~~
                              /home/iobroker/.cache/node-gyp/12.20.1/include/node/node.h:737:36: note: in definition of macro 'NODE_MODULE_X'
                                737 |       (node::addon_register_func) (regfunc),                          \
                                    |                                    ^~~~~~~
                              ../authenticate_pam.cc:175:1: note: in expansion of macro 'NODE_MODULE'
                                175 | NODE_MODULE(authenticate_pam, init);
                                    | ^~~~~~~~~~~
                              make: *** [authenticate_pam.target.mk:111: Release/obj.target/authenticate_pam/authenticate_pam.o] Error 1
                              gyp ERR! build error 
                              gyp ERR! stack Error: `make` failed with exit code: 2
                              gyp ERR! stack     at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:194:23)
                              gyp ERR! stack     at ChildProcess.emit (events.js:314:20)
                              gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:276:12)
                              gyp ERR! System Linux 5.4.78-2-pve
                              gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
                              gyp ERR! cwd /opt/iobroker/node_modules/authenticate-pam
                              gyp ERR! node -v v12.20.1
                              gyp ERR! node-gyp -v v5.1.0
                              gyp ERR! not ok 
                              Starting node restart.js
                              
                              apollon77A Offline
                              apollon77A Offline
                              apollon77
                              schrieb am zuletzt editiert von
                              #58

                              @master67 Das ist alles ok ... bzw wenn du gluck hast sind die nach einem "iobroker fix" weg.

                              Das sind faktisch nur warnungen von einem optionalen Paket

                              Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

                              • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
                              • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
                              Master67M 1 Antwort Letzte Antwort
                              0
                              • apollon77A apollon77

                                @master67 Das ist alles ok ... bzw wenn du gluck hast sind die nach einem "iobroker fix" weg.

                                Das sind faktisch nur warnungen von einem optionalen Paket

                                Master67M Offline
                                Master67M Offline
                                Master67
                                schrieb am zuletzt editiert von
                                #59

                                @apollon77 ... freut mich ja... aber ich kommen den noch nicht mehr auf den ioBroker drauf ;-)

                                Gruß Master67

                                Thomas BraunT apollon77A 2 Antworten Letzte Antwort
                                0
                                • Master67M Master67

                                  @apollon77 ... freut mich ja... aber ich kommen den noch nicht mehr auf den ioBroker drauf ;-)

                                  Thomas BraunT Online
                                  Thomas BraunT Online
                                  Thomas Braun
                                  Most Active
                                  schrieb am zuletzt editiert von Thomas Braun
                                  #60

                                  @master67
                                  Ist libpam0g-dev auf deinem System installiert?

                                  [Edit:] Das ist wieder so'n Container-Gesumsel, oder?

                                  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

                                  Master67M 1 Antwort Letzte Antwort
                                  0
                                  • Thomas BraunT Thomas Braun

                                    @master67
                                    Ist libpam0g-dev auf deinem System installiert?

                                    [Edit:] Das ist wieder so'n Container-Gesumsel, oder?

                                    Master67M Offline
                                    Master67M Offline
                                    Master67
                                    schrieb am zuletzt editiert von Master67
                                    #61

                                    @thomas-braun .... keine Ahnung!
                                    Da läuft nur der ioBroker unter Ubuntu 20.04.1

                                    Edit: japp Proxmox :-)

                                    Gruß Master67

                                    Thomas BraunT 1 Antwort Letzte Antwort
                                    0
                                    • Master67M Master67

                                      @thomas-braun .... keine Ahnung!
                                      Da läuft nur der ioBroker unter Ubuntu 20.04.1

                                      Edit: japp Proxmox :-)

                                      Thomas BraunT Online
                                      Thomas BraunT Online
                                      Thomas Braun
                                      Most Active
                                      schrieb am zuletzt editiert von
                                      #62

                                      @master67

                                      apt policy libpam0g-dev
                                      

                                      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

                                      Master67M 1 Antwort Letzte Antwort
                                      0
                                      • Thomas BraunT Thomas Braun

                                        @master67

                                        apt policy libpam0g-dev
                                        
                                        Master67M Offline
                                        Master67M Offline
                                        Master67
                                        schrieb am zuletzt editiert von
                                        #63

                                        @thomas-braun sagte in js-controller 3.2 jetzt im Latest!:

                                        apt policy libpam0g-dev

                                        Ja läuft....

                                        libpam0g-dev:
                                          Installed: 1.3.1-5ubuntu4.1
                                          Candidate: 1.3.1-5ubuntu4.1
                                          Version table:
                                         *** 1.3.1-5ubuntu4.1 500
                                                500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
                                                100 /var/lib/dpkg/status
                                             1.3.1-5ubuntu4 500
                                                500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
                                        

                                        Gruß Master67

                                        1 Antwort Letzte Antwort
                                        0
                                        • H Offline
                                          H Offline
                                          homecineplexx
                                          schrieb am zuletzt editiert von
                                          #64

                                          also mit dem js-controller 3.2.7 hab ich leuter Fehlermeldungen:

                                          2021-01-18 19:37:16.508  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]: TypeError: Cannot read property 'stateValue' of undefined
                                          2021-01-18 19:37:16.508  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at VirtualDevice.<anonymous> (script.js.VirtuelleDevices.ESP.watermeter:297:72)
                                          2021-01-18 19:37:16.509  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at runCallback (timers.js:706:11)
                                          2021-01-18 19:37:16.509  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at tryOnImmediate (timers.js:676:5)
                                          2021-01-18 19:37:16.509  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at processImmediate (timers.js:658:5)
                                          2021-01-18 19:37:16.509  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at process.topLevelDomainCallback (domain.js:126:23)
                                          2021-01-18 19:37:16.509  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]: TypeError: Cannot read property 'stateValue' of undefined
                                          2021-01-18 19:37:16.509  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at VirtualDevice.<anonymous> (script.js.VirtuelleDevices.ESP.watermeter:297:72)
                                          2021-01-18 19:37:16.509  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at runCallback (timers.js:706:11)
                                          2021-01-18 19:37:16.509  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at tryOnImmediate (timers.js:676:5)
                                          2021-01-18 19:37:16.510  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at processImmediate (timers.js:658:5)
                                          2021-01-18 19:37:16.510  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at process.topLevelDomainCallback (domain.js:126:23)
                                          2021-01-18 19:37:16.510  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]: TypeError: Cannot read property 'stateValue' of undefined
                                          2021-01-18 19:37:16.510  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at VirtualDevice.<anonymous> (script.js.VirtuelleDevices.ESP.watermeter:297:72)
                                          2021-01-18 19:37:16.510  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at runCallback (timers.js:706:11)
                                          2021-01-18 19:37:16.510  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at tryOnImmediate (timers.js:676:5)
                                          2021-01-18 19:37:16.510  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at processImmediate (timers.js:658:5)
                                          2021-01-18 19:37:16.510  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at process.topLevelDomainCallback (domain.js:126:23)
                                          2021-01-18 19:37:16.511  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]: TypeError: Cannot read property 'stateValue' of undefined
                                          2021-01-18 19:37:16.511  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at VirtualDevice.<anonymous> (script.js.VirtuelleDevices.ESP.watermeter:297:72)
                                          2021-01-18 19:37:16.511  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at runCallback (timers.js:706:11)
                                          2021-01-18 19:37:16.511  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at tryOnImmediate (timers.js:676:5)
                                          2021-01-18 19:37:16.511  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at processImmediate (timers.js:658:5)
                                          2021-01-18 19:37:16.511  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at process.topLevelDomainCallback (domain.js:126:23)
                                          

                                          hab auch schon geschaut, aber wonach bitte zählt der denn die Line 297? nicht so, wie sie im JavaScript ist denke ich.

                                          apollon77A 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
                                          FAQ Cloud / IOT
                                          HowTo: Node.js-Update
                                          HowTo: Backup/Restore
                                          Downloads
                                          BLOG

                                          718

                                          Online

                                          32.4k

                                          Benutzer

                                          81.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