Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Cloud Dienste
    4. Alexa Geräte nicht sichtbar

    NEWS

    • [erledigt] 15. 05. Wartungsarbeiten am ioBroker Forum

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    Alexa Geräte nicht sichtbar

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

      Hallo,

      bin noch ein Newbie und habe folgendes Problem:

      Kriege im Reiter "Objekte" den Ordner Alexa angezeigt aber keine Geräte sondern nur den Ordner History?

      Habe in Instanzen die Email + Passwort eingegeben sowie manuell den Cookie. Siehe Bilder, es werden aber wie gesagt keine Echos angezeigt.

      Was habe ich verkehrt gemacht oder muss ich noch irgendwelche Einstellungen machen??

      Hoffe auf baldige Antwort.
      7416_cookie1.jpg

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

        Hi,

        den Effekt hatte ich auch schon, nimm einfach den Cookie mal raus, den brauchst du nicht, wenn du Email und Passwort einträgst.

        Dann den Adapter nochmal neu starten und ein paar Minuten warten, bei mir hat er dann so nach und nach alle Echos gefunden.

        1 Reply Last reply Reply Quote 0
        • H
          helfi9999 last edited by

          Hi,

          er schreibt dann aber folgendes " no csrf found. Check configuration of email/password or cookie"

          1 Reply Last reply Reply Quote 0
          • H
            helfi9999 last edited by

            und das bei neustart:

            host.ioBroker-RasPi 2018-05-21 18:06:03.912 error instance system.adapter.alexa.0 terminated with code 0 (OK)

            host.ioBroker-RasPi 2018-05-21 18:06:03.911 error Caught by controller[0]: at process._tickCallback (internal/process/next_tick.js:180:9)

            host.ioBroker-RasPi 2018-05-21 18:06:03.911 error Caught by controller[0]: at _combinedTickCallback (internal/process/next_tick.js:138:11)

            host.ioBroker-RasPi 2018-05-21 18:06:03.910 error Caught by controller[0]: at emitErrorNT (internal/streams/destroy.js:64:8)

            host.ioBroker-RasPi 2018-05-21 18:06:03.910 error Caught by controller[0]: at TLSSocket.emit (events.js:211:7)

            host.ioBroker-RasPi 2018-05-21 18:06:03.909 error Caught by controller[0]: at emitOne (events.js:116:13)

            host.ioBroker-RasPi 2018-05-21 18:06:03.909 error Caught by controller[0]: at TLSSocket.socketErrorListener (_http_client.js:387:9)

            host.ioBroker-RasPi 2018-05-21 18:06:03.908 error Caught by controller[0]: at ClientRequest.emit (events.js:211:7)

            host.ioBroker-RasPi 2018-05-21 18:06:03.908 error Caught by controller[0]: at emitOne (events.js:116:13)

            host.ioBroker-RasPi 2018-05-21 18:06:03.907 error Caught by controller[0]: at ClientRequest. <anonymous>(/opt/iobroker/node_modules/alexa-cookie/alexa-cookie.js:54:20)

            host.ioBroker-RasPi 2018-05-21 18:06:03.907 error Caught by controller[0]: at /opt/iobroker/node_modules/alexa-cookie/alexa-cookie.js:127:35

            host.ioBroker-RasPi 2018-05-21 18:06:03.905 error Caught by controller[0]: TypeError: Cannot read property 'req' of null

            alexa.0 2018-05-21 18:06:03.866 error TypeError: Cannot read property 'req' of null at /opt/iobroker/node_modules/alexa-cookie/alexa-cookie.js:127:35 at ClientRequest. <anonymous>(/opt/iobroker/node_modules/alexa-cookie/alexa-cook

            alexa.0 2018-05-21 18:06:03.864 error uncaught exception: Cannot read property 'req' of null</anonymous></anonymous>

            1 Reply Last reply Reply Quote 0
            • H
              helfi9999 last edited by

              Habe eben ein Backup gemacht und folgendes kam raus 1. Geräte alle sichtbar und dann passierte folgendes:

              alexa.0 2018-05-21 18:25:36.151 info Delete channel alexa.0.echo-devices.SMG900F9D873EDF79B95A57_Commands

              alexa.0 2018-05-21 18:25:36.150 info Delete channel alexa.0.echo-devices.SMG900F9D873EDF79B95A57_States

              alexa.0 2018-05-21 18:25:36.150 info Delete channel alexa.0.echo-devices.971931d63b464947b3825a251e67733f_Commands

              alexa.0 2018-05-21 18:25:36.149 info Delete channel alexa.0.echo-devices.971931d63b464947b3825a251e67733f_States

              alexa.0 2018-05-21 18:25:36.149 info Delete channel alexa.0.echo-devices.4e7b9e92362e4ba0850066a89a913818_Commands

              alexa.0 2018-05-21 18:25:36.148 info Delete channel alexa.0.echo-devices.4e7b9e92362e4ba0850066a89a913818_States

              alexa.0 2018-05-21 18:25:36.148 info Delete channel alexa.0.echo-devices.G090LF1175040KJB_Commands

              alexa.0 2018-05-21 18:25:36.148 info Delete channel alexa.0.echo-devices.G090LF1175040KJB_Bluetooth_B8:6C:E8:42:FB:A8

              alexa.0 2018-05-21 18:25:36.147 info Delete channel alexa.0.echo-devices.G090LF1175040KJB_Bluetooth_78:00:9E:73:63:C3

              alexa.0 2018-05-21 18:25:36.147 info Delete channel alexa.0.echo-devices.G090LF1175040KJB_States

              alexa.0 2018-05-21 18:25:36.146 info Delete channel alexa.0.echo-devices.G2A0P3077407031K_Commands

              alexa.0 2018-05-21 18:25:36.146 info Delete channel alexa.0.echo-devices.G2A0P3077407031K_States

              alexa.0 2018-05-21 18:25:36.145 info Delete channel alexa.0.echo-devices.G070L80773871QTN_Commands

              alexa.0 2018-05-21 18:25:36.144 info Delete channel alexa.0.echo-devices.G070L80773871QTN_States

              alexa.0 2018-05-21 18:25:36.095 info Delete channel alexa.0.echo-devices_SMG900F9D873EDF79B95A57_Commands

              alexa.0 2018-05-21 18:25:36.077 info Delete channel alexa.0.echo-devices_SMG900F9D873EDF79B95A57_States

              alexa.0 2018-05-21 18:25:36.046 info Delete channel alexa.0.echo-devices_971931d63b464947b3825a251e67733f_Commands

              alexa.0 2018-05-21 18:25:36.031 info Delete channel alexa.0.echo-devices_971931d63b464947b3825a251e67733f_States

              alexa.0 2018-05-21 18:25:36.015 info Delete channel alexa.0.echo-devices_4e7b9e92362e4ba0850066a89a913818_Commands

              alexa.0 2018-05-21 18:25:36.001 info Delete channel alexa.0.echo-devices_4e7b9e92362e4ba0850066a89a913818_States

              alexa.0 2018-05-21 18:25:35.984 info Delete channel alexa.0.echo-devices_G090LF1175040KJB_Commands

              alexa.0 2018-05-21 18:25:35.964 info Delete channel alexa.0.echo-devices_G090LF1175040KJB_Bluetooth_B8:6C:E8:42:FB:A8

              alexa.0 2018-05-21 18:25:35.949 info Delete channel alexa.0.echo-devices_G090LF1175040KJB_Bluetooth_78:00:9E:73:63:C3

              alexa.0 2018-05-21 18:25:35.933 info Delete channel alexa.0.echo-devices_G090LF1175040KJB_States

              alexa.0 2018-05-21 18:25:35.917 info Delete channel alexa.0.echo-devices_G2A0P3077407031K_Commands

              alexa.0 2018-05-21 18:25:35.901 info Delete channel alexa.0.echo-devices_G2A0P3077407031K_States

              alexa.0 2018-05-21 18:25:35.884 info Delete channel alexa.0.echo-devices_G070L80773871QTN_Commands

              alexa.0 2018-05-21 18:25:35.870 info Delete channel alexa.0.echo-devices_G070L80773871QTN_States

              alexa.0 2018-05-21 18:25:34.194 info starting. Version 0.0.36 in /opt/iobroker/node_modules/iobroker.alexa, node: v8.11.1

              alexa.0 2018-05-21 18:25:34.039 info States connected to redis: 127.0.0.1:6379

              1 Reply Last reply Reply Quote 0
              • J
                Jun last edited by

                Ist bei mir genauso, ich bin auch schon zurück auf Version 0.33 geht auch nicht mehr. Lösche ich bei Version 0.36 das manuell angelegte Cookie raus, kommt auch die Meldung "no csrf found. Check configuration of email/password or cookie" Anmeldedaten sind auch richtig eingetragen. Geräte werden bei mir auch keine angezeigt.

                1 Reply Last reply Reply Quote 0
                • G
                  g.pitzer last edited by

                  gibt es schon eine Lösung, ich habe das gleiche Problem..

                  Thomas Braun 1 Reply Last reply Reply Quote 0
                  • Thomas Braun
                    Thomas Braun Most Active @g.pitzer last edited by

                    @g-pitzer Bestimmt nicht. Der Thread ist 2Jahre alt.

                    1 Reply Last reply Reply Quote 0
                    • G
                      g.pitzer last edited by

                      Hallo,
                      Anscheinend gibt es wieder das Problem, ich habe jetzt auch einen aktuellen Thread gefunden.
                      lg

                      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

                      669
                      Online

                      31.6k
                      Users

                      79.5k
                      Topics

                      1.3m
                      Posts

                      5
                      9
                      1012
                      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