Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Error/Bug
    4. Alexa2 Adapter startet nicht / Cookie wird nicht gespeichert

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    UNSOLVED Alexa2 Adapter startet nicht / Cookie wird nicht gespeichert

    This topic has been deleted. Only users with topic management privileges can see it.
    • Thomas Braun
      Thomas Braun Most Active last edited by Thomas Braun

      Systemdata Bitte Ausfüllen
      Hardwaresystem: Raspberry Pi 4
      Arbeitsspeicher: 4GB
      Festplattenart: SD-Karte
      Betriebssystem: Raspbian Buster
      Node-Version: 14.0.0
      Nodejs-Version: 14.0.0
      NPM-Version: 6.14.4
      Installationsart: Skript
      Image genutzt: Nein
      Ort/Name der Imagedatei: Link
      1 Reply Last reply Reply Quote 0
      • Thomas Braun
        Thomas Braun Most Active last edited by

        Wenn ich denn Adapter startet schmeißt er folgendes raus:

        2020-04-28 20:36:01.839  - info: host.raspberrypi instance system.adapter.alexa2.0 started with pid 3114
        2020-04-28 20:36:03.591  - info: alexa2.0 (3114) starting. Version 3.1.2 in /opt/iobroker/node_modules/iobroker.alexa2, node: v14.0.0, js-controller: 3.0.20
        2020-04-28 20:36:03.697  - info: alexa2.0 (3114) Proxy IP not set, use first network interface (192.168.178.50) instead
        2020-04-28 20:36:04.006  - error: alexa2.0 (3114) Error:
        2020-04-28 20:36:04.006  - error: alexa2.0 (3114) Error: You can try to get the cookie manually by opening http://192.168.178.50:34705/ with your browser.
        2020-04-28 20:37:33.674  - info: info.0 (931) Popup news was read...
        2020-04-28 20:47:08.613  - info: host.raspberrypi stopInstance system.adapter.alexa2.0 (force=false, process=true)
        2020-04-28 20:47:08.633  - info: host.raspberrypi stopInstance system.adapter.alexa2.0 send kill signal
        2020-04-28 20:47:08.635  - info: alexa2.0 (3114) Got terminate signal TERMINATE_YOURSELF
        2020-04-28 20:47:08.640  - info: alexa2.0 (3114) terminating
        2020-04-28 20:47:08.646  - info: alexa2.0 (3114) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
        2020-04-28 20:47:09.176  - info: host.raspberrypi instance system.adapter.alexa2.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
        2020-04-28 20:47:11.732  - info: host.raspberrypi instance system.adapter.alexa2.0 started with pid 3601
        2020-04-28 20:47:13.373  - info: alexa2.0 (3601) starting. Version 3.1.2 in /opt/iobroker/node_modules/iobroker.alexa2, node: v14.0.0, js-controller: 3.0.20
        2020-04-28 20:47:13.465  - info: alexa2.0 (3601) Proxy IP not set, use first network interface (192.168.178.50) instead
        2020-04-28 20:47:13.806  - error: alexa2.0 (3601) Error:
        2020-04-28 20:47:13.807  - error: alexa2.0 (3601) Error: You can try to get the cookie manually by opening http://192.168.178.50:43673/ with your browser.
        2020-04-28 20:47:41.094  - warn: alexa2.0 (3601) Exception: TypeError: Cannot read property 'end' of null
        2020-04-28 20:47:41.097  - error: alexa2.0 (3601) uncaught exception: Cannot read property 'end' of null
        2020-04-28 20:47:41.098  - error: alexa2.0 (3601) TypeError: Cannot read property 'end' of null
            at IncomingMessage.<anonymous> (/opt/iobroker/node_modules/alexa-cookie2/alexa-cookie.js:110:36)
            at IncomingMessage.emit (events.js:327:22)
            at IncomingMessage.EventEmitter.emit (domain.js:485:12)
            at endReadableNT (_stream_readable.js:1218:12)
            at processTicksAndRejections (internal/process/task_queues.js:84:21)
        2020-04-28 20:47:41.129  - info: alexa2.0 (3601) terminating
        2020-04-28 20:47:41.131  - info: alexa2.0 (3601) Terminated (NO_ERROR): Without reason
        2020-04-28 20:47:41.404  - error: host.raspberrypi Caught by controller[0]: (node:3601) [DEP0066] DeprecationWarning: OutgoingMessage.prototype._headers is deprecated
        2020-04-28 20:47:41.405  - error: host.raspberrypi Caught by controller[0]: (Use `node --trace-deprecation ...` to show where the warning was created)
        2020-04-28 20:47:41.405  - error: host.raspberrypi Caught by controller[1]: TypeError: Cannot read property 'end' of null
        2020-04-28 20:47:41.406  - error: host.raspberrypi Caught by controller[1]:     at IncomingMessage.<anonymous> (/opt/iobroker/node_modules/alexa-cookie2/alexa-cookie.js:110:36)
        2020-04-28 20:47:41.406  - error: host.raspberrypi Caught by controller[1]:     at IncomingMessage.emit (events.js:327:22)
        2020-04-28 20:47:41.406  - error: host.raspberrypi Caught by controller[1]:     at IncomingMessage.EventEmitter.emit (domain.js:485:12)
        2020-04-28 20:47:41.407  - error: host.raspberrypi Caught by controller[1]:     at endReadableNT (_stream_readable.js:1218:12)
        2020-04-28 20:47:41.407  - error: host.raspberrypi Caught by controller[1]:     at processTicksAndRejections (internal/process/task_queues.js:84:21)
        2020-04-28 20:47:41.407  - error: host.raspberrypi instance system.adapter.alexa2.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
        2020-04-28 20:47:41.408  - info: host.raspberrypi Restart adapter system.adapter.alexa2.0 because enabled
        

        Das cookie habe ich schon diverse Male neugeholt, das wird nicht gespeichert und der Adapter fragt immer wieder danach. Keine Ahnung was da schiefläuft.

        1 Reply Last reply Reply Quote 0
        • Thomas Braun
          Thomas Braun Most Active last edited by Thomas Braun

          Na sowas blödes...
          Habe auf node12 umgestellt, jetzt läuft es wieder.

          Ich bin aber felsenfest davon überzeugt, dass es auch unter 14 schon mal lief...

          1 Reply Last reply Reply Quote 0
          • apollon77
            apollon77 last edited by

            Die 3.2.0 vom Adapter sollte auch unter Nodejs 14 laufen

            Thomas Braun 1 Reply Last reply Reply Quote 0
            • Thomas Braun
              Thomas Braun Most Active @apollon77 last edited by

              @apollon77 Komischerweise läuft die 3.1.2 bei mir gerade auch mit node14.
              3.2.0 ist noch nicht im latest drin.

              apollon77 2 Replies Last reply Reply Quote 0
              • apollon77
                apollon77 @Thomas Braun last edited by

                @Thomas-Braun Der Fehler mit nodejs 14 tritt nur auf wenn DU kein Cookie hast und dich daher anmelden musst ... Wenn Du also eins Hast und er das nur "refresht" ist alles ok gewesen 🙂

                1 Reply Last reply Reply Quote 0
                • apollon77
                  apollon77 @Thomas Braun last edited by

                  @Thomas-Braun sagte in Alexa2 Adapter startet nicht / Cookie wird nicht gespeichert:

                  3.2.0 ist noch nicht im latest drin.

                  Jupp, > 2 Uhr 🙂

                  1 Reply Last reply Reply Quote 0
                  • First post
                    Last post

                  Support us

                  ioBroker
                  Community Adapters
                  Donate

                  666
                  Online

                  31.9k
                  Users

                  80.1k
                  Topics

                  1.3m
                  Posts

                  alexa 2 adapter
                  2
                  7
                  414
                  Loading More Posts
                  • Oldest to Newest
                  • Newest to Oldest
                  • Most Votes
                  Reply
                  • Reply as topic
                  Log in to reply
                  Community
                  Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                  The ioBroker Community 2014-2023
                  logo