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

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

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. Error/Bug
  4. iot und Alexa Adapter starten nicht mehr

NEWS

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

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

  • Weihnachtsangebot 2025! 🎄
    BluefoxB
    Bluefox
    25
    1
    2.4k

iot und Alexa Adapter starten nicht mehr

Geplant Angeheftet Gesperrt Verschoben Error/Bug
1 Beiträge 1 Kommentatoren 233 Aufrufe 1 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.
  • L Offline
    L Offline
    lxs
    schrieb am zuletzt editiert von
    #1
    Systemdata Bitte Ausfüllen
    Hardwaresystem: intel, Docker
    Arbeitsspeicher: 16GB
    Festplattenart: SSD
    Betriebssystem: Ubuntu
    Node-Version: 16.19.1
    Nodejs-Version: 16.19.1
    NPM-Version: 8.19.3
    Installationsart: Docker Container
    Image genutzt: Ja
    Ort/Name der Imagedatei: https://hub.docker.com/r/buanet/iobroker

    Hallo,

    Seit wenigen Tagen starten sowohl der iot als auch der Alexa Adapter bei mir nicht mehr. Ich hatte keine bewusste Änderung davor. Angefangen hat es mit dem Alexa Adapter, seit einem system-Reboot startet nun der iot Adapter mit einer sehr ähnlichen Fehlermeldung nicht mehr....

    Hier die Info vom Alexa Adapter:

    2023-05-14 19:27:20.270  - info: host.iobroker Restart adapter system.adapter.alexa2.0 because enabled
    2023-05-14 19:27:50.399  - info: host.iobroker instance system.adapter.alexa2.0 started with pid 32235
    2023-05-14 19:27:52.969  - info: alexa2.0 (32235) starting. Version 3.23.2 in /opt/iobroker/node_modules/iobroker.alexa2, node: v16.19.1, js-controller: 4.0.24
    2023-05-14 19:27:53.019  - info: alexa2.0 (32235) Starting Alexa2 adapter ... it can take several minutes to initialize all data. Please be patient! A done message is logged.
    2023-05-14 19:27:53.021  - error: alexa2.0 (32235) Adapter seems to have issues and crashed three times in a row. Disabling!! Please start again and check logs.
    2023-05-14 19:27:53.063  - error: alexa2.0 (32235) 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().
    2023-05-14 19:27:53.064  - error: alexa2.0 (32235) unhandled promise rejection: Cannot read properties of null (reading '_id')
    2023-05-14 19:27:53.069  - error: alexa2.0 (32235) TypeError: Cannot read properties of null (reading '_id')
        at /opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:3422:42
        at Array.map (<anonymous>)
        at ObjectsInRedisClient._applyViewFunc (/opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:3414:39)
        at processTicksAndRejections (node:internal/process/task_queues:96:5)
    2023-05-14 19:27:53.069  - error: alexa2.0 (32235) Cannot read properties of null (reading '_id')
    2023-05-14 19:27:53.089  - info: alexa2.0 (32235) terminating
    2023-05-14 19:27:53.091  - warn: alexa2.0 (32235) Terminated (UNCAUGHT_EXCEPTION): Without reason
    2023-05-14 19:27:53.770  - error: host.iobroker Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
    2023-05-14 19:27:53.771  - error: host.iobroker Caught by controller[1]: TypeError: Cannot read properties of null (reading '_id')
    2023-05-14 19:27:53.771  - error: host.iobroker Caught by controller[1]:     at /opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:3422:42
    2023-05-14 19:27:53.771  - error: host.iobroker Caught by controller[1]:     at Array.map (<anonymous>)
    2023-05-14 19:27:53.771  - error: host.iobroker Caught by controller[1]:     at ObjectsInRedisClient._applyViewFunc (/opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:3414:39)
    2023-05-14 19:27:53.771  - error: host.iobroker Caught by controller[1]:     at processTicksAndRejections (node:internal/process/task_queues:96:5)
    2023-05-14 19:27:53.772  - error: host.iobroker instance system.adapter.alexa2.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
    2023-05-14 19:27:53.772  - info: host.iobroker Restart adapter system.adapter.alexa2.0 because enabled
    2023-05-14 19:27:53.772  - warn: host.iobroker Do not restart adapter system.adapter.alexa2.0 because restart loop detected
    

    Und hier der iot-Adapter (leicht gekürzt, da sehr viele Geräte aufgezählt wurden):

    2023-05-14 19:43:31.489  - info: host.iobroker instance system.adapter.iot.0 started with pid 33043
    2023-05-14 19:43:32.450  - debug: iot.0 (33043) Redis Objects: Use Redis connection: iob_redis:6379
    2023-05-14 19:43:32.477  - debug: iot.0 (33043) Objects client ready ... initialize now
    2023-05-14 19:43:32.478  - debug: iot.0 (33043) Objects create System PubSub Client
    2023-05-14 19:43:32.479  - debug: iot.0 (33043) Objects create User PubSub Client
    2023-05-14 19:43:33.299  - debug: iot.0 (33043) Objects client initialize lua scripts
    2023-05-14 19:43:33.303  - debug: iot.0 (33043) Objects connected to redis: iob_redis:6379
    2023-05-14 19:43:33.319  - debug: iot.0 (33043) Redis States: Use Redis connection: iob_redis:6379
    2023-05-14 19:43:33.325  - debug: iot.0 (33043) States create System PubSub Client
    2023-05-14 19:43:33.326  - debug: iot.0 (33043) States create User PubSub Client
    2023-05-14 19:43:33.333  - debug: iot.0 (33043) States connected to redis: iob_redis:6379
    2023-05-14 19:43:33.567  - debug: iot.0 (33043) Plugin sentry Initialize Plugin (enabled=true)
    2023-05-14 19:43:33.843  - info: iot.0 (33043) starting. Version 1.14.5 in /opt/iobroker/node_modules/iobroker.iot, node: v16.19.1, js-controller: 4.0.24
    2023-05-14 19:43:33.914  - info: iot.0 (33043) Connecting with a18wym7vjdl22g.iot.eu-west-1.amazonaws.com
    2023-05-14 19:43:34.322  - info: iot.0 (33043) Connection changed: connect
    2023-05-14 19:43:39.911  - debug: iot.0 (33043) [ALEXA] Name "Licht Treppenhaus Status.STATE" cannot be written and will be ignored
    ...
    2023-05-14 19:43:40.572  - debug: iot.0 (33043) [ALEXA] Name "Steckdosen Esszimmer Status.STATE" cannot be written and will be ignored
    2023-05-14 19:43:40.579  - debug: iot.0 (33043) [ALEXA] Created ALEXA device: Wohnzimmer Steckdosen ["turnOn","turnOff"]
    ...
    2023-05-14 19:43:40.588  - debug: iot.0 (33043) [ALEXA] Created ALEXA device: Arbeitszimmer EG Rollo ["setPercentage","incrementPercentage","decrementPercentage","turnOn","turnOff"]
    2023-05-14 19:43:40.588  - debug: iot.0 (33043) [ALEXA] Created ALEXA device: Arbeitszimmer EG Licht ["setPercentage","incrementPercentage","decrementPercentage","turnOn","turnOff"]
    2023-05-14 19:43:41.186  - error: iot.0 (33043) 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().
    2023-05-14 19:43:41.187  - error: iot.0 (33043) unhandled promise rejection: Cannot read properties of null (reading '_id')
    2023-05-14 19:43:41.244  - error: iot.0 (33043) TypeError: Cannot read properties of null (reading '_id')
        at /opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:3422:42
        at Array.map (<anonymous>)
        at ObjectsInRedisClient._applyViewFunc (/opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:3414:39)
        at runMicrotasks (<anonymous>)
        at processTicksAndRejections (node:internal/process/task_queues:96:5)
    2023-05-14 19:43:41.244  - error: iot.0 (33043) Cannot read properties of null (reading '_id')
    2023-05-14 19:43:41.260  - info: iot.0 (33043) terminating
    2023-05-14 19:43:41.261  - debug: iot.0 (33043) Plugin sentry destroyed
    2023-05-14 19:43:41.261  - warn: iot.0 (33043) Terminated (UNCAUGHT_EXCEPTION): Without reason
    2023-05-14 19:43:41.311  - info: iot.0 (33043) Connection changed: disconnect
    2023-05-14 19:43:41.312  - info: iot.0 (33043) Connection lost
    2023-05-14 19:43:41.959  - error: host.iobroker Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
    2023-05-14 19:43:41.959  - error: host.iobroker Caught by controller[1]: TypeError: Cannot read properties of null (reading '_id')
    2023-05-14 19:43:41.960  - error: host.iobroker Caught by controller[1]:     at /opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:3422:42
    2023-05-14 19:43:41.960  - error: host.iobroker Caught by controller[1]:     at Array.map (<anonymous>)
    2023-05-14 19:43:41.960  - error: host.iobroker Caught by controller[1]:     at ObjectsInRedisClient._applyViewFunc (/opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:3414:39)
    2023-05-14 19:43:41.960  - error: host.iobroker Caught by controller[1]:     at runMicrotasks (<anonymous>)
    2023-05-14 19:43:41.960  - error: host.iobroker Caught by controller[1]:     at processTicksAndRejections (node:internal/process/task_queues:96:5)
    2023-05-14 19:43:41.960  - error: host.iobroker instance system.adapter.iot.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
    2023-05-14 19:43:41.961  - info: host.iobroker Restart adapter system.adapter.iot.0 because enabled
    

    Hat jemand eine Idee woran es liegen könnte oder was ich machen könnte?

    Eine kleine Besonderheit vielleicht: der Biobroker läuft als Docker-Container. objects und states sind beide in redis (ebenfalls ein container).

    Danke für jede Hilfe!

    Alexander

    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

    728

    Online

    32.6k

    Benutzer

    82.3k

    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