Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. Alexa2.0 login nicht möglich

    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

    Alexa2.0 login nicht möglich

    This topic has been deleted. Only users with topic management privileges can see it.
    • S
      smarty15 last edited by

      @Thomas-Braun

      Ok danke dir Thomas
      Ich habe heute morgen noch ein altes Backup eingespielt aber der Alexa Adapter verbindet sich nicht.

      Gibt es eine Möglichkeit die Login Daten zu löschen, also das ich mich im Adapter neu mit den Benutzerdaten von Amazon Alexa anmelden kann?

      Ich las da noch was von Cookies und kam auch auf eine Anleitung aber ich bin der Englischen Sprache leider nicht so mächtig.

      sonst läuft alles auf dem IOBroker, bis auf den Alexa Adapter

      1 Reply Last reply Reply Quote 0
      • G
        Guppy82 last edited by

        Hallo,

        Hatte das selbe Problem!

        Habe jetzt auch eine Lösung! die bei mir geholfen hat.
        Den Adapter (Alexa2.0) deinstallieren. Dann den iobrocker Neustarten. und die Adapter neu installieren und anmelden.

        hoffe konnte helfen
        MFG
        Guppy

        1 Reply Last reply Reply Quote 0
        • S
          smarty15 last edited by

          @Guppy82

          Leider bracht das bei mir nichts.
          jetzt steht auch bei
          Verbunden mit alexa2 Falsch

          weiss langsam nicht mehr was machen 😞

          Ich habe das Gefühl das das Login nicht richtig gelöscht wird wenn ich den Adapter Deinstalliert.
          Aber ist nur eine Vermutung von mir, bin Anfänger hier.

          Würde es vielleicht etwas bringen auf eine frühere Node.js Version zurückzukehren?

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

            @smarty15 Was steht denn im Startlog des Adapters?
            Eine ältere Version von node dürfte nicht die Lösung sein.

            1 Reply Last reply Reply Quote 0
            • S
              smarty15 last edited by

              @Thomas-Braun

              Ich weiss nicht ob dies reicht um zu sehen wo das Problem liegt.
              Kann auch den ganzen Log von heute anhängen aber der ist sehr lang.

              2020-07-17 00:00:16.404  - info: host.raspberrypi instance system.adapter.alexa2.0 started with pid 20335
2020-07-17 00:00:17.103  - error: host.raspberrypi Caught by controller[0]: internal/modules/cjs/loader.js:969
2020-07-17 00:00:17.104  - error: host.raspberrypi Caught by controller[0]:   throw err;
2020-07-17 00:00:17.104  - error: host.raspberrypi Caught by controller[0]:   ^
2020-07-17 00:00:17.104  - error: host.raspberrypi Caught by controller[0]: Error: Cannot find module 'https-proxy-agent'
2020-07-17 00:00:17.104  - error: host.raspberrypi Caught by controller[0]: Require stack:
2020-07-17 00:00:17.104  - error: host.raspberrypi Caught by controller[0]: - /opt/iobroker/node_modules/virtual-device-sdk/lib/src/VirtualDevice.js
2020-07-17 00:00:17.104  - error: host.raspberrypi Caught by controller[0]: - /opt/iobroker/node_modules/virtual-device-sdk/lib/src/Index.js
2020-07-17 00:00:17.105  - error: host.raspberrypi Caught by controller[0]: - /opt/iobroker/node_modules/iobroker.alexa2/main.js
2020-07-17 00:00:17.105  - error: host.raspberrypi Caught by controller[0]:     at Function.Module._resolveFilename (internal/modules/cjs/loader.js:966:15)
2020-07-17 00:00:17.105  - error: host.raspberrypi Caught by controller[0]:     at Function.Module._load (internal/modules/cjs/loader.js:842:27)
2020-07-17 00:00:17.105  - error: host.raspberrypi Caught by controller[0]:     at Module.require (internal/modules/cjs/loader.js:1026:19)
2020-07-17 00:00:17.105  - error: host.raspberrypi Caught by controller[0]:     at require (internal/modules/cjs/helpers.js:72:18)
2020-07-17 00:00:17.105  - error: host.raspberrypi Caught by controller[0]:     at Object.<anonymous> (/opt/iobroker/node_modules/virtual-device-sdk/lib/src/VirtualDevice.js:41:23)
2020-07-17 00:00:17.119  - error: host.raspberrypi Caught by controller[0]:     at Module._compile (internal/modules/cjs/loader.js:1138:30)
2020-07-17 00:00:17.119  - error: host.raspberrypi Caught by controller[0]:     at Object.Module._extensions..js (internal/modules/cjs/loader.js:1158:10)
2020-07-17 00:00:17.119  - error: host.raspberrypi Caught by controller[0]:     at Module.load (internal/modules/cjs/loader.js:986:32)
2020-07-17 00:00:17.119  - error: host.raspberrypi Caught by controller[0]:     at Function.Module._load (internal/modules/cjs/loader.js:879:14)
2020-07-17 00:00:17.120  - error: host.raspberrypi Caught by controller[0]:     at Module.require (internal/modules/cjs/loader.js:1026:19) {
2020-07-17 00:00:17.120  - error: host.raspberrypi Caught by controller[0]:   code: 'MODULE_NOT_FOUND',
2020-07-17 00:00:17.120  - error: host.raspberrypi Caught by controller[0]:   requireStack: [
2020-07-17 00:00:17.120  - error: host.raspberrypi Caught by controller[0]:     '/opt/iobroker/node_modules/virtual-device-sdk/lib/src/VirtualDevice.js',
2020-07-17 00:00:17.120  - error: host.raspberrypi Caught by controller[0]:     '/opt/iobroker/node_modules/virtual-device-sdk/lib/src/Index.js',
2020-07-17 00:00:17.120  - error: host.raspberrypi Caught by controller[0]:     '/opt/iobroker/node_modules/iobroker.alexa2/main.js'
2020-07-17 00:00:17.121  - error: host.raspberrypi Caught by controller[0]:   ]
2020-07-17 00:00:17.121  - error: host.raspberrypi Caught by controller[0]: }
2020-07-17 00:00:17.122  - error: host.raspberrypi instance system.adapter.alexa2.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
2020-07-17 00:00:17.122  - info: host.raspberrypi Restart adapter system.adapter.alexa2.0 because enabled
2020-07-17 00:00:47.139  - info: host.raspberrypi instance system.adapter.alexa2.0 started with pid 20354
2020-07-17 00:00:47.734  - error: host.raspberrypi Caught by controller[0]: internal/modules/cjs/loader.js:969
2020-07-17 00:00:47.735  - error: host.raspberrypi Caught by controller[0]:   throw err;
2020-07-17 00:00:47.735  - error: host.raspberrypi Caught by controller[0]:   ^
2020-07-17 00:00:47.735  - error: host.raspberrypi Caught by controller[0]: Error: Cannot find module 'https-proxy-agent'
2020-07-17 00:00:47.735  - error: host.raspberrypi Caught by controller[0]: Require stack:
2020-07-17 00:00:47.735  - error: host.raspberrypi Caught by controller[0]: - /opt/iobroker/node_modules/virtual-device-sdk/lib/src/VirtualDevice.js
2020-07-17 00:00:47.735  - error: host.raspberrypi Caught by controller[0]: - /opt/iobroker/node_modules/virtual-device-sdk/lib/src/Index.js
2020-07-17 00:00:47.736  - error: host.raspberrypi Caught by controller[0]: - /opt/iobroker/node_modules/iobroker.alexa2/main.js
2020-07-17 00:00:47.736  - error: host.raspberrypi Caught by controller[0]:     at Function.Module._resolveFilename (internal/modules/cjs/loader.js:966:15)
2020-07-17 00:00:47.736  - error: host.raspberrypi Caught by controller[0]:     at Function.Module._load (internal/modules/cjs/loader.js:842:27)
2020-07-17 00:00:47.736  - error: host.raspberrypi Caught by controller[0]:     at Module.require (internal/modules/cjs/loader.js:1026:19)
2020-07-17 00:00:47.736  - error: host.raspberrypi Caught by controller[0]:     at require (internal/modules/cjs/helpers.js:72:18)
2020-07-17 00:00:47.736  - error: host.raspberrypi Caught by controller[0]:     at Object.<anonymous> (/opt/iobroker/node_modules/virtual-device-sdk/lib/src/VirtualDevice.js:41:23)
2020-07-17 00:00:47.736  - error: host.raspberrypi Caught by controller[0]:     at Module._compile (internal/modules/cjs/loader.js:1138:30)
2020-07-17 00:00:47.736  - error: host.raspberrypi Caught by controller[0]:     at Object.Module._extensions..js (internal/modules/cjs/loader.js:1158:10)
2020-07-17 00:00:47.737  - error: host.raspberrypi Caught by controller[0]:     at Module.load (internal/modules/cjs/loader.js:986:32)
2020-07-17 00:00:47.737  - error: host.raspberrypi Caught by controller[0]:     at Function.Module._load (internal/modules/cjs/loader.js:879:14)
2020-07-17 00:00:47.737  - error: host.raspberrypi Caught by controller[0]:     at Module.require (internal/modules/cjs/loader.js:1026:19) {
2020-07-17 00:00:47.737  - error: host.raspberrypi Caught by controller[0]:   code: 'MODULE_NOT_FOUND',
2020-07-17 00:00:47.737  - error: host.raspberrypi Caught by controller[0]:   requireStack: [
2020-07-17 00:00:47.737  - error: host.raspberrypi Caught by controller[0]:     '/opt/iobroker/node_modules/virtual-device-sdk/lib/src/VirtualDevice.js',
2020-07-17 00:00:47.737  - error: host.raspberrypi Caught by controller[0]:     '/opt/iobroker/node_modules/virtual-device-sdk/lib/src/Index.js',
2020-07-17 00:00:47.737  - error: host.raspberrypi Caught by controller[0]:     '/opt/iobroker/node_modules/iobroker.alexa2/main.js'
2020-07-17 00:00:47.738  - error: host.raspberrypi Caught by controller[0]:   ]
2020-07-17 00:00:47.738  - error: host.raspberrypi Caught by controller[0]: }
2020-07-17 00:00:47.738  - error: host.raspberrypi instance system.adapter.alexa2.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
2020-07-17 00:00:47.738  - info: host.raspberrypi Restart adapter system.adapter.alexa2.0 because enabled
2020-07-17 00:01:17.755  - info: host.raspberrypi instance system.adapter.alexa2.0 started with pid 20421
2020-07-17 00:01:18.382  - error: host.raspberrypi Caught by controller[0]: internal/modules/cjs/loader.js:969
2020-07-17 00:01:18.382  - error: host.raspberrypi Caught by controller[0]:   throw err;
2020-07-17 00:01:18.382  - error: host.raspberrypi Caught by controller[0]:   ^
2020-07-17 00:01:18.383  - error: host.raspberrypi Caught by controller[0]: Error: Cannot find module 'https-proxy-agent'
2020-07-17 00:01:18.383  - error: host.raspberrypi Caught by controller[0]: Require stack:
2020-07-17 00:01:18.383  - error: host.raspberrypi Caught by controller[0]: - /opt/iobroker/node_modules/virtual-device-sdk/lib/src/VirtualDevice.js
2020-07-17 00:01:18.383  - error: host.raspberrypi Caught by controller[0]: - /opt/iobroker/node_modules/virtual-device-sdk/lib/src/Index.js
2020-07-17 00:01:18.383  - error: host.raspberrypi Caught by controller[0]: - /opt/iobroker/node_modules/iobroker.alexa2/main.js
2020-07-17 00:01:18.383  - error: host.raspberrypi Caught by controller[0]:     at Function.Module._resolveFilename (internal/modules/cjs/loader.js:966:15)
2020-07-17 00:01:18.383  - error: host.raspberrypi Caught by controller[0]:     at Function.Module._load (internal/modules/cjs/loader.js:842:27)
2020-07-17 00:01:18.383  - error: host.raspberrypi Caught by controller[0]:     at Module.require (internal/modules/cjs/loader.js:1026:19)
2020-07-17 00:01:18.384  - error: host.raspberrypi Caught by controller[0]:     at require (internal/modules/cjs/helpers.js:72:18)
2020-07-17 00:01:18.384  - error: host.raspberrypi Caught by controller[0]:     at Object.<anonymous> (/opt/iobroker/node_modules/virtual-device-sdk/lib/src/VirtualDevice.js:41:23)
2020-07-17 00:01:18.384  - error: host.raspberrypi Caught by controller[0]:     at Module._compile (internal/modules/cjs/loader.js:1138:30)
2020-07-17 00:01:18.384  - error: host.raspberrypi Caught by controller[0]:     at Object.Module._extensions..js (internal/modules/cjs/loader.js:1158:10)
2020-07-17 00:01:18.384  - error: host.raspberrypi Caught by controller[0]:     at Module.load (internal/modules/cjs/loader.js:986:32)
2020-07-17 00:01:18.384  - error: host.raspberrypi Caught by controller[0]:     at Function.Module._load (internal/modules/cjs/loader.js:879:14)
2020-07-17 00:01:18.384  - error: host.raspberrypi Caught by controller[0]:     at Module.require (internal/modules/cjs/loader.js:1026:19) {
2020-07-17 00:01:18.384  - error: host.raspberrypi Caught by controller[0]:   code: 'MODULE_NOT_FOUND',
2020-07-17 00:01:18.385  - error: host.raspberrypi Caught by controller[0]:   requireStack: [
2020-07-17 00:01:18.385  - error: host.raspberrypi Caught by controller[0]:     '/opt/iobroker/node_modules/virtual-device-sdk/lib/src/VirtualDevice.js',
2020-07-17 00:01:18.385  - error: host.raspberrypi Caught by controller[0]:     '/opt/iobroker/node_modules/virtual-device-sdk/lib/src/Index.js',
2020-07-17 00:01:18.385  - error: host.raspberrypi Caught by controller[0]:     '/opt/iobroker/node_modules/iobroker.alexa2/main.js'
2020-07-17 00:01:18.385  - error: host.raspberrypi Caught by controller[0]:   ]
2020-07-17 00:01:18.385  - error: host.raspberrypi Caught by controller[0]: }
              Thomas Braun 1 Reply Last reply Reply Quote 0
              • Thomas Braun
                Thomas Braun Most Active @smarty15 last edited by

                @smarty15 sagte in Alexa2.0 login nicht möglich:
                Von Hand installiert schon probiert?

                npm i https-proxy-agent
                Eulo 1 Reply Last reply Reply Quote 0
                • S
                  smarty15 last edited by

                  @Thomas-Braun

                  Das habe ich noch nie gemacht so
                  Muss ich dazu den Code von dir einfach im Terminal eingeben?

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

                    @Thomas-Braun sagte in Alexa2.0 login nicht möglich:

                    @smarty15 sagte in Alexa2.0 login nicht möglich:
                    Von Hand installiert schon probiert?

                    npm i https-proxy-agent

                    habs versucht, bringt leider kein erfolg.

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

                      ich habe das problem das er mir immer anzeigt, das ich angeblich Falsche Login Daten eingegeben habe. Was aber absolut nicht sein kann! Mehrfach schon ausprobiert und getestet.

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

                        @Eulo Was liefert denn

                        cd /opt/iobroker
npm list https-proxy-agent
                        1 Reply Last reply Reply Quote 0
                        • S
                          smarty15 last edited by

                          @Thomas-Braun

                          Habe jetzt beides probiert
                          leider ohne Erfolg

                          Hier der Auszug aus dem Terminal

                          pi@raspberrypi:~ $ npm i https-proxy-agent
npm WARN saveError ENOENT: no such file or directory, open '/home/pi/package.json'
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN enoent ENOENT: no such file or directory, open '/home/pi/package.json'
npm WARN pi No description
npm WARN pi No repository field.
npm WARN pi No README data
npm WARN pi No license field.

+ https-proxy-agent@5.0.0
added 4 packages from 3 contributors and audited 4 packages in 1.083s
found 0 vulnerabilities

pi@raspberrypi:~ $ iobroker restart
pi@raspberrypi:~ $ node -v
v12.18.2
pi@raspberrypi:~ $ npm -v
6.14.5
pi@raspberrypi:~ $ cd /opt/iobroker
pi@raspberrypi:/opt/iobroker $ npm list https-proxy-agent
iobroker.inst@2.0.3 /opt/iobroker
├─┬ iobroker.alexa2@3.2.8
│ └─┬ @sentry/node@5.19.2
│   └── https-proxy-agent@5.0.0 
└─┬ iobroker.vis-weather@2.5.2
  └─┬ npm@6.14.4
    └─┬ npm-registry-fetch@4.0.3
      └─┬ make-fetch-happen@5.0.2
        └── https-proxy-agent@2.2.4 

pi@raspberrypi:/opt/iobroker $
                          Thomas Braun 1 Reply Last reply Reply Quote 0
                          • Thomas Braun
                            Thomas Braun Most Active @smarty15 last edited by

                            @smarty15
                            Komisch, bei mir liegt das Modul auch noch im js-controller drin:

                            pi@raspberrypi:/opt/iobroker $ npm list https-proxy-agent
iobroker.inst@2.0.3 /opt/iobroker
├─┬ iobroker.alexa2@3.2.8
│ └─┬ @sentry/node@5.19.2
│   └── https-proxy-agent@5.0.0
├─┬ iobroker.backitup@1.5.8
│ └─┬ google-auth-library@6.0.0
│   └─┬ gaxios@3.0.3
│     └── https-proxy-agent@5.0.0
├─┬ iobroker.js-controller@3.1.6
│ └─┬ @iobroker/plugin-sentry@1.1.4
│   └─┬ @sentry/node@5.17.0
│     └── https-proxy-agent@4.0.0
└─┬ iobroker.nuki-extended@2.2.6
  └─┬ npm@6.14.6
    └─┬ npm-registry-fetch@4.0.5
      └─┬ make-fetch-happen@5.0.2
        └── https-proxy-agent@2.2.4
                            1 Reply Last reply Reply Quote 0
                            • S
                              smarty15 last edited by

                              @Thomas-Braun

                              Also heisst dass das bei mir irgendwo ein Fehler ist?

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

                                @smarty15 Das kann ich nicht sagen. Aber der js-controller ist so zentral, das würde ich eigentlich bei jeder Installation dann dort erwarten.

                                iobroker version

                                bringt?

                                1 Reply Last reply Reply Quote 0
                                • S
                                  smarty15 last edited by

                                  @Thomas-Braun

                                  Ok

                                  Da bekomme ich das hier raus

                                  pi@raspberrypi:~ $ iobroker version
3.1.6
pi@raspberrypi:~ $
                                  Thomas Braun 1 Reply Last reply Reply Quote 0
                                  • Thomas Braun
                                    Thomas Braun Most Active @smarty15 last edited by

                                    @smarty15

                                    which nodejs && nodejs -v && which node && node -v && which npm && npm -v && apt policy nodejs
                                    1 Reply Last reply Reply Quote 0
                                    • S
                                      smarty15 last edited by

                                      @Thomas-Braun

                                      Soll ich das jetzt im Terminal eingeben?
                                      oder ist das dass was bei dir rauskommt wenn du iobroker Version eingibst?

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

                                        @smarty15
                                        Das so in deine Konsole kopieren.

                                        1 Reply Last reply Reply Quote 0
                                        • S
                                          smarty15 last edited by

                                          @Thomas-Braun

                                          ok dann erscheint das hier

                                          pi@raspberrypi:~ $ which nodejs && nodejs -v && which node && node -v && which npm && npm -v && apt policy nodejs
/usr/bin/nodejs
v12.18.2
/usr/local/bin/node
v12.18.2
/usr/local/bin/npm
6.14.5
nodejs:
  Installiert:           12.18.2-1nodesource1
  Installationskandidat: 12.18.2-1nodesource1
  Versionstabelle:
 *** 12.18.2-1nodesource1 100
        100 /var/lib/dpkg/status
     10.21.0-1nodesource1 500
        500 https://deb.nodesource.com/node_10.x buster/main armhf Packages
     10.21.0~dfsg-1~deb10u1+rpi1 500
        500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages
pi@raspberrypi:~ $
                                          Thomas Braun 1 Reply Last reply Reply Quote 0
                                          • Thomas Braun
                                            Thomas Braun Most Active @smarty15 last edited by

                                            @smarty15 Node nicht richtig installiert.

                                            Schau dich hier mal um:
                                            https://forum.iobroker.net/topic/35090/howto-nodejs-installation-und-upgrades-unter-debian/3

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

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate
                                            FAQ Cloud / IOT
                                            HowTo: Node.js-Update
                                            HowTo: Backup/Restore
                                            Downloads
                                            BLOG

                                            555
                                            Online

                                            31.9k
                                            Users

                                            80.1k
                                            Topics

                                            1.3m
                                            Posts

                                            alexa alexa 2 adapter alexa2 adapter login
                                            15
                                            90
                                            6323
                                            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