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. Spotify-Premium Adapter

NEWS

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

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

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

Spotify-Premium Adapter

Geplant Angeheftet Gesperrt Verschoben Error/Bug
29 Beiträge 3 Kommentatoren 2.5k Aufrufe 3 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.
  • DJMarc75D DJMarc75

    @vumer sagte in Spotify-Premium Adapter:

    proxmox ist noch 6.4

    kenn ich nicht

    @vumer sagte in Spotify-Premium Adapter:

    sonst alles up to date

    ja? zeig mal bitte.

    Und wie @Thomas-Braun geschrieben hat ist der Fehler 503 ein Serverproblem - seitens Spotify - da kann man nix ändern.

    Hab grad mal in meinen Logs geschaut und tatsächlich vor einigen Tagen auch diesen "Fehler" gehabt.
    Aber sowas ist mit egal weil es da keine Einschränkungen gibt in der Funktionalität - zumindest bei mir nicht.

    VumerV Offline
    VumerV Offline
    Vumer
    schrieb am zuletzt editiert von
    #8

    @djmarc75 sagte in Spotify-Premium Adapter:

    seitens Spotify

    ach so

    Danke Euch :+1:

    Thomas BraunT 1 Antwort Letzte Antwort
    0
    • VumerV Vumer

      @djmarc75 sagte in Spotify-Premium Adapter:

      seitens Spotify

      ach so

      Danke Euch :+1:

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

      @vumer

      https://www.seo-kueche.de/lexikon/503-fehler-code/

      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

      1 Antwort Letzte Antwort
      1
      • DJMarc75D DJMarc75

        @vumer sagte in Spotify-Premium Adapter:

        proxmox ist noch 6.4

        kenn ich nicht

        @vumer sagte in Spotify-Premium Adapter:

        sonst alles up to date

        ja? zeig mal bitte.

        Und wie @Thomas-Braun geschrieben hat ist der Fehler 503 ein Serverproblem - seitens Spotify - da kann man nix ändern.

        Hab grad mal in meinen Logs geschaut und tatsächlich vor einigen Tagen auch diesen "Fehler" gehabt.
        Aber sowas ist mit egal weil es da keine Einschränkungen gibt in der Funktionalität - zumindest bei mir nicht.

        VumerV Offline
        VumerV Offline
        Vumer
        schrieb am zuletzt editiert von Vumer
        #10

        @djmarc75 sagte in Spotify-Premium Adapter:

        Hab grad mal in meinen Logs geschaut und tatsächlich vor einigen Tagen auch diesen "Fehler" gehabt.
        Aber sowas ist mit egal weil es da keine Einschränkungen gibt in der Funktionalität - zumindest bei mir nicht.

        bei mir ist das leider anders
        324f42d7-baf6-4d1f-b7d8-9752d30f7490-grafik.png

        2022-11-18 16:42:06.390 - error: spotify-premium.0 (2113) 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().
        2022-11-18 16:42:06.393 - error: spotify-premium.0 (2113) unhandled promise rejection: undefined
        2022-11-18 16:42:06.393 - error: spotify-premium.0 (2113) undefined
        2022-11-18 16:42:07.235 - 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:
        2022-11-18 16:42:07.236 - error: host.iobroker Caught by controller[1]: no ids in trackListIds
        2022-11-18 16:42:07.236 - error: host.iobroker instance system.adapter.spotify-premium.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
        2022-11-18 16:42:07.236 - info: host.iobroker Restart adapter system.adapter.spotify-premium.0 because enabled
        2022-11-18 16:42:37.350 - info: host.iobroker instance system.adapter.spotify-premium.0 started with pid 29878
        2022-11-18 16:42:39.641 - error: spotify-premium.0 (29878) 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().
        2022-11-18 16:42:39.642 - error: spotify-premium.0 (29878) unhandled promise rejection: undefined
        2022-11-18 16:42:39.642 - error: spotify-premium.0 (29878) undefined
        2022-11-18 16:42:40.444 - 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:
        2022-11-18 16:42:40.444 - error: host.iobroker Caught by controller[0]: no ids in trackListIds
        2022-11-18 16:42:40.444 - error: host.iobroker instance system.adapter.spotify-premium.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
        2022-11-18 16:42:40.444 - info: host.iobroker Restart adapter system.adapter.spotify-premium.0 because enabled
        2022-11-18 16:43:10.553 - info: host.iobroker instance system.adapter.spotify-premium.0 started with pid 29990
        2022-11-18 16:43:36.237 - error: spotify-premium.0 (29990) could not execute command: 404
        2022-11-18 16:43:37.819 - error: spotify-premium.0 (29990) 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().
        2022-11-18 16:43:37.820 - error: spotify-premium.0 (29990) unhandled promise rejection: undefined
        2022-11-18 16:43:37.820 - error: spotify-premium.0 (29990) undefined
        2022-11-18 16:43:38.542 - 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:
        2022-11-18 16:43:38.543 - error: host.iobroker Caught by controller[1]: no ids in trackListIds
        2022-11-18 16:43:38.543 - error: host.iobroker instance system.adapter.spotify-premium.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
        2022-11-18 16:43:38.543 - info: host.iobroker Restart adapter system.adapter.spotify-premium.0 because enabled
        2022-11-18 16:43:38.543 - warn: host.iobroker Do not restart adapter system.adapter.spotify-premium.0 because restart loop detected
        2022-11-18 16:44:00.759 - info: host.iobroker instance system.adapter.spotify-premium.0 started with pid 30185
        2022-11-18 16:44:03.862 - error: spotify-premium.0 (30185) 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().
        2022-11-18 16:44:03.863 - error: spotify-premium.0 (30185) unhandled promise rejection: undefined
        2022-11-18 16:44:03.863 - error: spotify-premium.0 (30185) undefined
        2022-11-18 16:44:04.645 - 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:
        2022-11-18 16:44:04.645 - error: host.iobroker Caught by controller[0]: no ids in trackListIds
        2022-11-18 16:44:04.645 - error: host.iobroker instance system.adapter.spotify-premium.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
        2022-11-18 16:44:04.645 - info: host.iobroker Restart adapter system.adapter.spotify-premium.0 because enabled
        2022-11-18 16:44:15.477 - info: host.iobroker "system.adapter.spotify-premium.0" disabled
        2022-11-18 16:44:18.226 - info: host.iobroker "system.adapter.spotify-premium.0" enabled
        2022-11-18 16:44:18.453 - info: host.iobroker instance system.adapter.spotify-premium.0 started with pid 30254
        2022-11-18 16:44:21.306 - error: spotify-premium.0 (30254) 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().
        2022-11-18 16:44:21.307 - error: spotify-premium.0 (30254) unhandled promise rejection: undefined
        2022-11-18 16:44:21.308 - error: spotify-premium.0 (30254) undefined
        2022-11-18 16:44:22.036 - 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:
        2022-11-18 16:44:22.037 - error: host.iobroker Caught by controller[1]: no ids in trackListIds
        2022-11-18 16:44:22.037 - error: host.iobroker instance system.adapter.spotify-premium.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
        2022-11-18 16:44:22.037 - info: host.iobroker Restart adapter system.adapter.spotify-premium.0 because enabled
        2022-11-18 16:44:52.145 - info: host.iobroker instance system.adapter.spotify-premium.0 started with pid 30368
        2022-11-18 16:44:54.904 - error: spotify-premium.0 (30368) 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().
        2022-11-18 16:44:54.905 - error: spotify-premium.0 (30368) unhandled promise rejection: undefined
        2022-11-18 16:44:54.905 - error: spotify-premium.0 (30368) undefined
        2022-11-18 16:44:55.443 - info: host.iobroker stopInstance system.adapter.spotify-premium.0 (force=false, process=true)
        2022-11-18 16:44:55.571 - info: host.iobroker stopInstance system.adapter.spotify-premium.0 send kill signal
        2022-11-18 16:44:55.864 - 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:
        2022-11-18 16:44:55.864 - error: host.iobroker Caught by controller[1]: no ids in trackListIds
        2022-11-18 16:44:55.865 - info: host.iobroker instance system.adapter.spotify-premium.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
        2022-11-18 16:44:58.770 - info: host.iobroker instance system.adapter.spotify-premium.0 started with pid 30401
        2022-11-18 16:45:01.180 - error: spotify-premium.0 (30401) 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().
        2022-11-18 16:45:01.181 - error: spotify-premium.0 (30401) unhandled promise rejection: undefined
        2022-11-18 16:45:01.182 - error: spotify-premium.0 (30401) undefined
        2022-11-18 16:45:01.991 - 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:
        2022-11-18 16:45:01.991 - error: host.iobroker Caught by controller[0]: no ids in trackListIds
        2022-11-18 16:45:01.992 - error: host.iobroker instance system.adapter.spotify-premium.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
        2022-11-18 16:45:01.992 - info: host.iobroker Restart adapter system.adapter.spotify-premium.0 because enabled
        2022-11-18 16:45:01.992 - warn: host.iobroker Do not restart adapter system.adapter.spotify-premium.0 because restart loop detected
        
        DJMarc75D 1 Antwort Letzte Antwort
        0
        • VumerV Vumer

          @djmarc75 sagte in Spotify-Premium Adapter:

          Hab grad mal in meinen Logs geschaut und tatsächlich vor einigen Tagen auch diesen "Fehler" gehabt.
          Aber sowas ist mit egal weil es da keine Einschränkungen gibt in der Funktionalität - zumindest bei mir nicht.

          bei mir ist das leider anders
          324f42d7-baf6-4d1f-b7d8-9752d30f7490-grafik.png

          2022-11-18 16:42:06.390 - error: spotify-premium.0 (2113) 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().
          2022-11-18 16:42:06.393 - error: spotify-premium.0 (2113) unhandled promise rejection: undefined
          2022-11-18 16:42:06.393 - error: spotify-premium.0 (2113) undefined
          2022-11-18 16:42:07.235 - 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:
          2022-11-18 16:42:07.236 - error: host.iobroker Caught by controller[1]: no ids in trackListIds
          2022-11-18 16:42:07.236 - error: host.iobroker instance system.adapter.spotify-premium.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
          2022-11-18 16:42:07.236 - info: host.iobroker Restart adapter system.adapter.spotify-premium.0 because enabled
          2022-11-18 16:42:37.350 - info: host.iobroker instance system.adapter.spotify-premium.0 started with pid 29878
          2022-11-18 16:42:39.641 - error: spotify-premium.0 (29878) 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().
          2022-11-18 16:42:39.642 - error: spotify-premium.0 (29878) unhandled promise rejection: undefined
          2022-11-18 16:42:39.642 - error: spotify-premium.0 (29878) undefined
          2022-11-18 16:42:40.444 - 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:
          2022-11-18 16:42:40.444 - error: host.iobroker Caught by controller[0]: no ids in trackListIds
          2022-11-18 16:42:40.444 - error: host.iobroker instance system.adapter.spotify-premium.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
          2022-11-18 16:42:40.444 - info: host.iobroker Restart adapter system.adapter.spotify-premium.0 because enabled
          2022-11-18 16:43:10.553 - info: host.iobroker instance system.adapter.spotify-premium.0 started with pid 29990
          2022-11-18 16:43:36.237 - error: spotify-premium.0 (29990) could not execute command: 404
          2022-11-18 16:43:37.819 - error: spotify-premium.0 (29990) 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().
          2022-11-18 16:43:37.820 - error: spotify-premium.0 (29990) unhandled promise rejection: undefined
          2022-11-18 16:43:37.820 - error: spotify-premium.0 (29990) undefined
          2022-11-18 16:43:38.542 - 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:
          2022-11-18 16:43:38.543 - error: host.iobroker Caught by controller[1]: no ids in trackListIds
          2022-11-18 16:43:38.543 - error: host.iobroker instance system.adapter.spotify-premium.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
          2022-11-18 16:43:38.543 - info: host.iobroker Restart adapter system.adapter.spotify-premium.0 because enabled
          2022-11-18 16:43:38.543 - warn: host.iobroker Do not restart adapter system.adapter.spotify-premium.0 because restart loop detected
          2022-11-18 16:44:00.759 - info: host.iobroker instance system.adapter.spotify-premium.0 started with pid 30185
          2022-11-18 16:44:03.862 - error: spotify-premium.0 (30185) 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().
          2022-11-18 16:44:03.863 - error: spotify-premium.0 (30185) unhandled promise rejection: undefined
          2022-11-18 16:44:03.863 - error: spotify-premium.0 (30185) undefined
          2022-11-18 16:44:04.645 - 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:
          2022-11-18 16:44:04.645 - error: host.iobroker Caught by controller[0]: no ids in trackListIds
          2022-11-18 16:44:04.645 - error: host.iobroker instance system.adapter.spotify-premium.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
          2022-11-18 16:44:04.645 - info: host.iobroker Restart adapter system.adapter.spotify-premium.0 because enabled
          2022-11-18 16:44:15.477 - info: host.iobroker "system.adapter.spotify-premium.0" disabled
          2022-11-18 16:44:18.226 - info: host.iobroker "system.adapter.spotify-premium.0" enabled
          2022-11-18 16:44:18.453 - info: host.iobroker instance system.adapter.spotify-premium.0 started with pid 30254
          2022-11-18 16:44:21.306 - error: spotify-premium.0 (30254) 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().
          2022-11-18 16:44:21.307 - error: spotify-premium.0 (30254) unhandled promise rejection: undefined
          2022-11-18 16:44:21.308 - error: spotify-premium.0 (30254) undefined
          2022-11-18 16:44:22.036 - 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:
          2022-11-18 16:44:22.037 - error: host.iobroker Caught by controller[1]: no ids in trackListIds
          2022-11-18 16:44:22.037 - error: host.iobroker instance system.adapter.spotify-premium.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
          2022-11-18 16:44:22.037 - info: host.iobroker Restart adapter system.adapter.spotify-premium.0 because enabled
          2022-11-18 16:44:52.145 - info: host.iobroker instance system.adapter.spotify-premium.0 started with pid 30368
          2022-11-18 16:44:54.904 - error: spotify-premium.0 (30368) 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().
          2022-11-18 16:44:54.905 - error: spotify-premium.0 (30368) unhandled promise rejection: undefined
          2022-11-18 16:44:54.905 - error: spotify-premium.0 (30368) undefined
          2022-11-18 16:44:55.443 - info: host.iobroker stopInstance system.adapter.spotify-premium.0 (force=false, process=true)
          2022-11-18 16:44:55.571 - info: host.iobroker stopInstance system.adapter.spotify-premium.0 send kill signal
          2022-11-18 16:44:55.864 - 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:
          2022-11-18 16:44:55.864 - error: host.iobroker Caught by controller[1]: no ids in trackListIds
          2022-11-18 16:44:55.865 - info: host.iobroker instance system.adapter.spotify-premium.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
          2022-11-18 16:44:58.770 - info: host.iobroker instance system.adapter.spotify-premium.0 started with pid 30401
          2022-11-18 16:45:01.180 - error: spotify-premium.0 (30401) 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().
          2022-11-18 16:45:01.181 - error: spotify-premium.0 (30401) unhandled promise rejection: undefined
          2022-11-18 16:45:01.182 - error: spotify-premium.0 (30401) undefined
          2022-11-18 16:45:01.991 - 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:
          2022-11-18 16:45:01.991 - error: host.iobroker Caught by controller[0]: no ids in trackListIds
          2022-11-18 16:45:01.992 - error: host.iobroker instance system.adapter.spotify-premium.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
          2022-11-18 16:45:01.992 - info: host.iobroker Restart adapter system.adapter.spotify-premium.0 because enabled
          2022-11-18 16:45:01.992 - warn: host.iobroker Do not restart adapter system.adapter.spotify-premium.0 because restart loop detected
          
          DJMarc75D Offline
          DJMarc75D Offline
          DJMarc75
          schrieb am zuletzt editiert von
          #11

          @vumer Welche Version vom Adapter und auch sonst so: wie bist Du unterwegs ?

          Lehrling seit 1975 !!!
          Beitrag geholfen ? dann gerne ein upvote rechts unten im Beitrag klicken ;)
          https://forum.iobroker.net/topic/51555/hinweise-f%C3%BCr-gute-forenbeitr%C3%A4ge

          VumerV 1 Antwort Letzte Antwort
          0
          • DJMarc75D DJMarc75

            @vumer Welche Version vom Adapter und auch sonst so: wie bist Du unterwegs ?

            VumerV Offline
            VumerV Offline
            Vumer
            schrieb am zuletzt editiert von
            #12

            @djmarc75
            Spotify Installierte Version: 1.2.2
            Admin 6.2.23

            Gibt es ein Befehl für die Infos die de brauchst?

            DJMarc75D 1 Antwort Letzte Antwort
            0
            • VumerV Vumer

              @djmarc75
              Spotify Installierte Version: 1.2.2
              Admin 6.2.23

              Gibt es ein Befehl für die Infos die de brauchst?

              DJMarc75D Offline
              DJMarc75D Offline
              DJMarc75
              schrieb am zuletzt editiert von
              #13

              @vumer jo, Adapter sind aktuell...

              erstmal:

              sudo apt update
              

              Ausgabe bitte komplett zeigen.

              Lehrling seit 1975 !!!
              Beitrag geholfen ? dann gerne ein upvote rechts unten im Beitrag klicken ;)
              https://forum.iobroker.net/topic/51555/hinweise-f%C3%BCr-gute-forenbeitr%C3%A4ge

              VumerV 1 Antwort Letzte Antwort
              0
              • DJMarc75D DJMarc75

                @vumer jo, Adapter sind aktuell...

                erstmal:

                sudo apt update
                

                Ausgabe bitte komplett zeigen.

                VumerV Offline
                VumerV Offline
                Vumer
                schrieb am zuletzt editiert von
                #14

                @djmarc75 sagte in Spotify-Premium Adapter:

                sudo apt update

                OK:1 http://security.debian.org/debian-security bullseye-security InRelease
                OK:2 http://ftp.debian.org/debian bullseye InRelease                                                                              
                OK:3 http://ftp.debian.org/debian bullseye-updates InRelease                                                                      
                OK:4 https://deb.nodesource.com/node_16.x bullseye InRelease                                                                      
                OK:5 https://repos.influxdata.com/debian bullseye InRelease                                                                       
                Paketlisten werden gelesen… Fertig
                Abhängigkeitsbaum wird aufgebaut… Fertig
                Statusinformationen werden eingelesen… Fertig
                Alle Pakete sind aktuell.
                
                DJMarc75D 1 Antwort Letzte Antwort
                0
                • VumerV Vumer

                  @djmarc75 sagte in Spotify-Premium Adapter:

                  sudo apt update

                  OK:1 http://security.debian.org/debian-security bullseye-security InRelease
                  OK:2 http://ftp.debian.org/debian bullseye InRelease                                                                              
                  OK:3 http://ftp.debian.org/debian bullseye-updates InRelease                                                                      
                  OK:4 https://deb.nodesource.com/node_16.x bullseye InRelease                                                                      
                  OK:5 https://repos.influxdata.com/debian bullseye InRelease                                                                       
                  Paketlisten werden gelesen… Fertig
                  Abhängigkeitsbaum wird aufgebaut… Fertig
                  Statusinformationen werden eingelesen… Fertig
                  Alle Pakete sind aktuell.
                  
                  DJMarc75D Offline
                  DJMarc75D Offline
                  DJMarc75
                  schrieb am zuletzt editiert von
                  #15

                  @vumer ok, dann zeig mal die Einstellungen im SoptifyAdapter (unterhalb von Client-Secret)

                  Lehrling seit 1975 !!!
                  Beitrag geholfen ? dann gerne ein upvote rechts unten im Beitrag klicken ;)
                  https://forum.iobroker.net/topic/51555/hinweise-f%C3%BCr-gute-forenbeitr%C3%A4ge

                  VumerV 1 Antwort Letzte Antwort
                  0
                  • DJMarc75D DJMarc75

                    @vumer ok, dann zeig mal die Einstellungen im SoptifyAdapter (unterhalb von Client-Secret)

                    VumerV Offline
                    VumerV Offline
                    Vumer
                    schrieb am zuletzt editiert von
                    #16

                    @djmarc75
                    53e830c9-13a6-440f-bc72-731bd51b4836-grafik.png

                    1 Antwort Letzte Antwort
                    0
                    • VumerV Offline
                      VumerV Offline
                      Vumer
                      schrieb am zuletzt editiert von Vumer
                      #17

                      Jetzt geht gar nichts. Sobald ich den Adapter starte

                      host.iobroker 2022-11-18 17:12:20.917	warn	Do not restart adapter system.adapter.spotify-premium.0 because restart loop detected
                      host.iobroker 2022-11-18 17:12:20.916	error	instance system.adapter.spotify-premium.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
                      host.iobroker 2022-11-18 17:12:20.916	error	Caught by controller[1]: no ids in trackListIds
                      host.iobroker 2022-11-18 17:12:20.916	error	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:
                      spotify-premium.0 2022-11-18 17:12:20.237	error	undefined
                      spotify-premium.0 2022-11-18 17:12:20.236	error	unhandled promise rejection: undefined
                      spotify-premium.0 2022-11-18 17:12:20.235	error	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().
                      host.iobroker 2022-11-18 17:11:47.854	error	instance system.adapter.spotify-premium.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
                      host.iobroker 2022-11-18 17:11:47.854	error	Caught by controller[0]: no ids in trackListIds
                      host.iobroker 2022-11-18 17:11:47.854	error	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:
                      spotify-premium.0 2022-11-18 17:11:47.117	error	undefined
                      spotify-premium.0 2022-11-18 17:11:47.116	error	unhandled promise rejection: undefined
                      spotify-premium.0 2022-11-18 17:11:47.115	error	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().
                      host.iobroker 2022-11-18 17:11:14.439	error	instance system.adapter.spotify-premium.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
                      host.iobroker 2022-11-18 17:11:14.439	error	Caught by controller[1]: no ids in trackListIds
                      host.iobroker 2022-11-18 17:11:14.439	error	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:
                      spotify-premium.0 2022-11-18 17:11:13.755	error	undefined
                      spotify-premium.0 2022-11-18 17:11:13.754	error	unhandled promise rejection: undefined
                      spotify-premium.0 2022-11-18 17:11:13.753	error	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().
                      

                      und der Adapter geht in rot

                      DJMarc75D 1 Antwort Letzte Antwort
                      0
                      • VumerV Vumer

                        Jetzt geht gar nichts. Sobald ich den Adapter starte

                        host.iobroker 2022-11-18 17:12:20.917	warn	Do not restart adapter system.adapter.spotify-premium.0 because restart loop detected
                        host.iobroker 2022-11-18 17:12:20.916	error	instance system.adapter.spotify-premium.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
                        host.iobroker 2022-11-18 17:12:20.916	error	Caught by controller[1]: no ids in trackListIds
                        host.iobroker 2022-11-18 17:12:20.916	error	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:
                        spotify-premium.0 2022-11-18 17:12:20.237	error	undefined
                        spotify-premium.0 2022-11-18 17:12:20.236	error	unhandled promise rejection: undefined
                        spotify-premium.0 2022-11-18 17:12:20.235	error	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().
                        host.iobroker 2022-11-18 17:11:47.854	error	instance system.adapter.spotify-premium.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
                        host.iobroker 2022-11-18 17:11:47.854	error	Caught by controller[0]: no ids in trackListIds
                        host.iobroker 2022-11-18 17:11:47.854	error	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:
                        spotify-premium.0 2022-11-18 17:11:47.117	error	undefined
                        spotify-premium.0 2022-11-18 17:11:47.116	error	unhandled promise rejection: undefined
                        spotify-premium.0 2022-11-18 17:11:47.115	error	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().
                        host.iobroker 2022-11-18 17:11:14.439	error	instance system.adapter.spotify-premium.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
                        host.iobroker 2022-11-18 17:11:14.439	error	Caught by controller[1]: no ids in trackListIds
                        host.iobroker 2022-11-18 17:11:14.439	error	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:
                        spotify-premium.0 2022-11-18 17:11:13.755	error	undefined
                        spotify-premium.0 2022-11-18 17:11:13.754	error	unhandled promise rejection: undefined
                        spotify-premium.0 2022-11-18 17:11:13.753	error	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().
                        

                        und der Adapter geht in rot

                        DJMarc75D Offline
                        DJMarc75D Offline
                        DJMarc75
                        schrieb am zuletzt editiert von
                        #18

                        @vumer Dann zeig mal:

                        sudo ln -s /usr/bin/node /usr/bin/nodejs &> /dev/null
                        uname -m && test -f /opt/scripts/.docker_config/.thisisdocker && echo "Docker-Installation" || echo "Kein Docker" && type -P nodejs node npm && nodejs -v && node -v && npm -v && iob -v && whoami && groups && echo $XDG_SESSION_TYPE && echo $DESKTOP_SESSION && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs
                        

                        Inklusive Ein- und Ausgaben bitte.

                        Lehrling seit 1975 !!!
                        Beitrag geholfen ? dann gerne ein upvote rechts unten im Beitrag klicken ;)
                        https://forum.iobroker.net/topic/51555/hinweise-f%C3%BCr-gute-forenbeitr%C3%A4ge

                        VumerV 1 Antwort Letzte Antwort
                        0
                        • DJMarc75D DJMarc75

                          @vumer Dann zeig mal:

                          sudo ln -s /usr/bin/node /usr/bin/nodejs &> /dev/null
                          uname -m && test -f /opt/scripts/.docker_config/.thisisdocker && echo "Docker-Installation" || echo "Kein Docker" && type -P nodejs node npm && nodejs -v && node -v && npm -v && iob -v && whoami && groups && echo $XDG_SESSION_TYPE && echo $DESKTOP_SESSION && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs
                          

                          Inklusive Ein- und Ausgaben bitte.

                          VumerV Offline
                          VumerV Offline
                          Vumer
                          schrieb am zuletzt editiert von Vumer
                          #19

                          @djmarc75

                          @iobroker:~$ uname -m && test -f /opt/scripts/.docker_config/.thisisdocker && echo "Docker-Installation" || echo "Kein Docker" && type -P nodejs node npm && nodejs -v && node -v && npm -v && iob -v && whoami && groups && echo $XDG_SESSION_TYPE && echo $DESKTOP_SESSION && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs
                          x86_64
                          Kein Docker
                          /usr/bin/nodejs
                          /usr/bin/node
                          /usr/bin/npm
                          v16.18.1
                          v16.18.1
                          8.19.2
                          4.0.23
                          
                          
                          
                          /home/
                          OK:1 http://security.debian.org/debian-security bullseye-security InRelease
                          OK:2 http://ftp.debian.org/debian bullseye InRelease                                                                              
                          OK:3 http://ftp.debian.org/debian bullseye-updates InRelease                                                                      
                          OK:4 https://deb.nodesource.com/node_16.x bullseye InRelease                                                                      
                          OK:5 https://repos.influxdata.com/debian bullseye InRelease                                                                       
                          Paketlisten werden gelesen… Fertig
                          Abhängigkeitsbaum wird aufgebaut… Fertig
                          Statusinformationen werden eingelesen… Fertig
                          Alle Pakete sind aktuell.
                          nodejs:
                            Installiert:           16.18.1-deb-1nodesource1
                            Installationskandidat: 16.18.1-deb-1nodesource1
                            Versionstabelle:
                           *** 16.18.1-deb-1nodesource1 500
                                  500 https://deb.nodesource.com/node_16.x bullseye/main amd64 Packages
                                  100 /var/lib/dpkg/status
                               12.22.12~dfsg-1~deb11u1 500
                                  500 http://security.debian.org/debian-security bullseye-security/main amd64 Packages
                               12.22.5~dfsg-2~11u1 500
                                  500 http://ftp.debian.org/debian bullseye/main amd64 Packages
                          
                          DJMarc75D 1 Antwort Letzte Antwort
                          0
                          • VumerV Vumer

                            @djmarc75

                            @iobroker:~$ uname -m && test -f /opt/scripts/.docker_config/.thisisdocker && echo "Docker-Installation" || echo "Kein Docker" && type -P nodejs node npm && nodejs -v && node -v && npm -v && iob -v && whoami && groups && echo $XDG_SESSION_TYPE && echo $DESKTOP_SESSION && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs
                            x86_64
                            Kein Docker
                            /usr/bin/nodejs
                            /usr/bin/node
                            /usr/bin/npm
                            v16.18.1
                            v16.18.1
                            8.19.2
                            4.0.23
                            
                            
                            
                            /home/
                            OK:1 http://security.debian.org/debian-security bullseye-security InRelease
                            OK:2 http://ftp.debian.org/debian bullseye InRelease                                                                              
                            OK:3 http://ftp.debian.org/debian bullseye-updates InRelease                                                                      
                            OK:4 https://deb.nodesource.com/node_16.x bullseye InRelease                                                                      
                            OK:5 https://repos.influxdata.com/debian bullseye InRelease                                                                       
                            Paketlisten werden gelesen… Fertig
                            Abhängigkeitsbaum wird aufgebaut… Fertig
                            Statusinformationen werden eingelesen… Fertig
                            Alle Pakete sind aktuell.
                            nodejs:
                              Installiert:           16.18.1-deb-1nodesource1
                              Installationskandidat: 16.18.1-deb-1nodesource1
                              Versionstabelle:
                             *** 16.18.1-deb-1nodesource1 500
                                    500 https://deb.nodesource.com/node_16.x bullseye/main amd64 Packages
                                    100 /var/lib/dpkg/status
                                 12.22.12~dfsg-1~deb11u1 500
                                    500 http://security.debian.org/debian-security bullseye-security/main amd64 Packages
                                 12.22.5~dfsg-2~11u1 500
                                    500 http://ftp.debian.org/debian bullseye/main amd64 Packages
                            
                            DJMarc75D Offline
                            DJMarc75D Offline
                            DJMarc75
                            schrieb am zuletzt editiert von
                            #20

                            @vumer nix auffälliges ...

                            Ich würde den Adapter mal komplett deinstallieren und neu installieren, dann nochmal authentifizieren.
                            Ist mir grad sonst echt ein Rätsel - ich hatte das mal vor knapp nem Jahr aber da lags an der Version vom Adapter

                            Lehrling seit 1975 !!!
                            Beitrag geholfen ? dann gerne ein upvote rechts unten im Beitrag klicken ;)
                            https://forum.iobroker.net/topic/51555/hinweise-f%C3%BCr-gute-forenbeitr%C3%A4ge

                            VumerV 1 Antwort Letzte Antwort
                            0
                            • DJMarc75D DJMarc75

                              @vumer nix auffälliges ...

                              Ich würde den Adapter mal komplett deinstallieren und neu installieren, dann nochmal authentifizieren.
                              Ist mir grad sonst echt ein Rätsel - ich hatte das mal vor knapp nem Jahr aber da lags an der Version vom Adapter

                              VumerV Offline
                              VumerV Offline
                              Vumer
                              schrieb am zuletzt editiert von
                              #21

                              @djmarc75 sagte in Spotify-Premium Adapter:

                              Ich würde den Adapter mal komplett deinstallieren und neu installieren, dann nochmal authentifizieren.

                              hab ich, zur Zeit noch grün :)

                              DJMarc75D 1 Antwort Letzte Antwort
                              0
                              • VumerV Vumer

                                @djmarc75 sagte in Spotify-Premium Adapter:

                                Ich würde den Adapter mal komplett deinstallieren und neu installieren, dann nochmal authentifizieren.

                                hab ich, zur Zeit noch grün :)

                                DJMarc75D Offline
                                DJMarc75D Offline
                                DJMarc75
                                schrieb am zuletzt editiert von
                                #22

                                @vumer sagte in Spotify-Premium Adapter:

                                hab ich, zur Zeit noch grün

                                na dann drück ich Dir mal die Daumen dass das so bleibt... noch ein Tipp... Playlisten welche NICHT von Dir in Spotify angelegt wurden können auch große Probleme im Adapter machen...

                                Lehrling seit 1975 !!!
                                Beitrag geholfen ? dann gerne ein upvote rechts unten im Beitrag klicken ;)
                                https://forum.iobroker.net/topic/51555/hinweise-f%C3%BCr-gute-forenbeitr%C3%A4ge

                                VumerV 1 Antwort Letzte Antwort
                                1
                                • DJMarc75D DJMarc75

                                  @vumer sagte in Spotify-Premium Adapter:

                                  hab ich, zur Zeit noch grün

                                  na dann drück ich Dir mal die Daumen dass das so bleibt... noch ein Tipp... Playlisten welche NICHT von Dir in Spotify angelegt wurden können auch große Probleme im Adapter machen...

                                  VumerV Offline
                                  VumerV Offline
                                  Vumer
                                  schrieb am zuletzt editiert von
                                  #23

                                  @djmarc75
                                  Danke für den Tipp :+1: Ich hoffe das Alias keine probleme bereitet.

                                  DJMarc75D 1 Antwort Letzte Antwort
                                  0
                                  • VumerV Offline
                                    VumerV Offline
                                    Vumer
                                    schrieb am zuletzt editiert von Vumer
                                    #24

                                    Leider immer noch

                                    host.iobroker 2022-11-19 13:02:24.813	error	instance system.adapter.spotify-premium.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
                                    host.iobroker 2022-11-19 13:02:24.812	error	Caught by controller[8]: 503
                                    host.iobroker 2022-11-19 13:02:24.812	error	Caught by controller[7]: 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:
                                    host.iobroker 2022-11-19 13:02:24.812	error	Caught by controller[6]: at processTicksAndRejections (node:internal/process/task_queues:96:5)
                                    host.iobroker 2022-11-19 13:02:24.812	error	Caught by controller[6]: at runMicrotasks (<anonymous>)
                                    host.iobroker 2022-11-19 13:02:24.812	error	Caught by controller[6]: at /opt/iobroker/node_modules/iobroker.spotify-premium/main.js:973:21
                                    host.iobroker 2022-11-19 13:02:24.812	error	Caught by controller[6]: at createOrDefault (/opt/iobroker/node_modules/iobroker.spotify-premium/main.js:387:13)
                                    host.iobroker 2022-11-19 13:02:24.812	error	Caught by controller[6]: at loadOrDefault (/opt/iobroker/node_modules/iobroker.spotify-premium/main.js:373:13)
                                    host.iobroker 2022-11-19 13:02:24.812	error	Caught by controller[6]: at eval (eval at loadOrDefault (/opt/iobroker/node_modules/iobroker.spotify-premium/main.js:372:19), <anonymous>:3:12)
                                    host.iobroker 2022-11-19 13:02:24.812	error	Caught by controller[6]: TypeError: Cannot read properties of undefined (reading 'songs')
                                    host.iobroker 2022-11-19 13:02:24.812	error	Caught by controller[5]: at processTicksAndRejections (node:internal/process/task_queues:96:5)
                                    host.iobroker 2022-11-19 13:02:24.812	error	Caught by controller[5]: at runMicrotasks (<anonymous>)
                                    host.iobroker 2022-11-19 13:02:24.812	error	Caught by controller[5]: at /opt/iobroker/node_modules/iobroker.spotify-premium/main.js:970:21
                                    host.iobroker 2022-11-19 13:02:24.812	error	Caught by controller[5]: at createOrDefault (/opt/iobroker/node_modules/iobroker.spotify-premium/main.js:387:13)
                                    host.iobroker 2022-11-19 13:02:24.812	error	Caught by controller[5]: at loadOrDefault (/opt/iobroker/node_modules/iobroker.spotify-premium/main.js:373:13)
                                    host.iobroker 2022-11-19 13:02:24.812	error	Caught by controller[5]: at eval (eval at loadOrDefault (/opt/iobroker/node_modules/iobroker.spotify-premium/main.js:372:19), <anonymous>:3:12)
                                    host.iobroker 2022-11-19 13:02:24.812	error	Caught by controller[5]: TypeError: Cannot read properties of undefined (reading 'trackIds')
                                    host.iobroker 2022-11-19 13:02:24.812	error	Caught by controller[4]: at processTicksAndRejections (node:internal/process/task_queues:96:5)
                                    host.iobroker 2022-11-19 13:02:24.812	error	Caught by controller[4]: at runMicrotasks (<anonymous>)
                                    host.iobroker 2022-11-19 13:02:24.812	error	Caught by controller[4]: at /opt/iobroker/node_modules/iobroker.spotify-premium/main.js:967:21
                                    host.iobroker 2022-11-19 13:02:24.812	error	Caught by controller[4]: at createOrDefault (/opt/iobroker/node_modules/iobroker.spotify-premium/main.js:387:13)
                                    host.iobroker 2022-11-19 13:02:24.811	error	Caught by controller[4]: at loadOrDefault (/opt/iobroker/node_modules/iobroker.spotify-premium/main.js:373:13)
                                    host.iobroker 2022-11-19 13:02:24.811	error	Caught by controller[4]: at eval (eval at loadOrDefault (/opt/iobroker/node_modules/iobroker.spotify-premium/main.js:372:19), <anonymous>:3:12)
                                    host.iobroker 2022-11-19 13:02:24.811	error	Caught by controller[4]: TypeError: Cannot read properties of undefined (reading 'trackIdMap')
                                    host.iobroker 2022-11-19 13:02:24.811	error	Caught by controller[3]: at processTicksAndRejections (node:internal/process/task_queues:96:5)
                                    host.iobroker 2022-11-19 13:02:24.811	error	Caught by controller[3]: at runMicrotasks (<anonymous>)
                                    host.iobroker 2022-11-19 13:02:24.811	error	Caught by controller[3]: at /opt/iobroker/node_modules/iobroker.spotify-premium/main.js:964:21
                                    host.iobroker 2022-11-19 13:02:24.811	error	Caught by controller[3]: at createOrDefault (/opt/iobroker/node_modules/iobroker.spotify-premium/main.js:387:13)
                                    host.iobroker 2022-11-19 13:02:24.811	error	Caught by controller[3]: at loadOrDefault (/opt/iobroker/node_modules/iobroker.spotify-premium/main.js:373:13)
                                    host.iobroker 2022-11-19 13:02:24.811	error	Caught by controller[3]: at eval (eval at loadOrDefault (/opt/iobroker/node_modules/iobroker.spotify-premium/main.js:372:19), <anonymous>:3:12)
                                    host.iobroker 2022-11-19 13:02:24.811	error	Caught by controller[3]: TypeError: Cannot read properties of undefined (reading 'stateString')
                                    host.iobroker 2022-11-19 13:02:24.811	error	Caught by controller[2]: at processTicksAndRejections (node:internal/process/task_queues:96:5)
                                    host.iobroker 2022-11-19 13:02:24.811	error	Caught by controller[2]: at runMicrotasks (<anonymous>)
                                    host.iobroker 2022-11-19 13:02:24.811	error	Caught by controller[2]: at /opt/iobroker/node_modules/iobroker.spotify-premium/main.js:961:21
                                    host.iobroker 2022-11-19 13:02:24.811	error	Caught by controller[2]: at createOrDefault (/opt/iobroker/node_modules/iobroker.spotify-premium/main.js:387:13)
                                    host.iobroker 2022-11-19 13:02:24.811	error	Caught by controller[2]: at loadOrDefault (/opt/iobroker/node_modules/iobroker.spotify-premium/main.js:373:13)
                                    host.iobroker 2022-11-19 13:02:24.811	error	Caught by controller[2]: at eval (eval at loadOrDefault (/opt/iobroker/node_modules/iobroker.spotify-premium/main.js:372:19), <anonymous>:3:12)
                                    host.iobroker 2022-11-19 13:02:24.811	error	Caught by controller[2]: TypeError: Cannot read properties of undefined (reading 'listString')
                                    host.iobroker 2022-11-19 13:02:24.811	error	Caught by controller[2]: at processTicksAndRejections (node:internal/process/task_queues:96:5)
                                    host.iobroker 2022-11-19 13:02:24.811	error	Caught by controller[2]: at runMicrotasks (<anonymous>)
                                    host.iobroker 2022-11-19 13:02:24.811	error	Caught by controller[2]: at /opt/iobroker/node_modules/iobroker.spotify-premium/main.js:958:21
                                    host.iobroker 2022-11-19 13:02:24.811	error	Caught by controller[2]: at createOrDefault (/opt/iobroker/node_modules/iobroker.spotify-premium/main.js:387:13)
                                    host.iobroker 2022-11-19 13:02:24.810	error	Caught by controller[2]: at loadOrDefault (/opt/iobroker/node_modules/iobroker.spotify-premium/main.js:373:13)
                                    host.iobroker 2022-11-19 13:02:24.810	error	Caught by controller[2]: at eval (eval at loadOrDefault (/opt/iobroker/node_modules/iobroker.spotify-premium/main.js:372:19), <anonymous>:3:12)
                                    host.iobroker 2022-11-19 13:02:24.810	error	Caught by controller[2]: TypeError: Cannot read properties of undefined (reading 'listNumber')
                                    host.iobroker 2022-11-19 13:02:24.810	error	Caught by controller[1]: at processTicksAndRejections (node:internal/process/task_queues:96:5)
                                    host.iobroker 2022-11-19 13:02:24.810	error	Caught by controller[1]: at runMicrotasks (<anonymous>)
                                    host.iobroker 2022-11-19 13:02:24.810	error	Caught by controller[1]: at /opt/iobroker/node_modules/iobroker.spotify-premium/main.js:937:32
                                    host.iobroker 2022-11-19 13:02:24.810	error	Caught by controller[1]: at loadOrDefault (/opt/iobroker/node_modules/iobroker.spotify-premium/main.js:373:13)
                                    host.iobroker 2022-11-19 13:02:24.810	error	Caught by controller[1]: at eval (eval at loadOrDefault (/opt/iobroker/node_modules/iobroker.spotify-premium/main.js:372:19), <anonymous>:3:12)
                                    host.iobroker 2022-11-19 13:02:24.810	error	Caught by controller[1]: TypeError: Cannot read properties of undefined (reading 'stateString')
                                    spotify-premium.0 2022-11-19 13:02:24.099	error	undefined
                                    spotify-premium.0 2022-11-19 13:02:24.099	error	unhandled promise rejection: undefined
                                    spotify-premium.0 2022-11-19 13:02:24.095	error	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().
                                    

                                    gesteuert habe ich nur über die Android app oder direkt am Teufel Lautsprecher. Um 13:02, glaube ich, mit der FB vom Teufel

                                    1 Antwort Letzte Antwort
                                    0
                                    • VumerV Vumer

                                      @djmarc75
                                      Danke für den Tipp :+1: Ich hoffe das Alias keine probleme bereitet.

                                      DJMarc75D Offline
                                      DJMarc75D Offline
                                      DJMarc75
                                      schrieb am zuletzt editiert von
                                      #25

                                      @vumer sagte in Spotify-Premium Adapter:

                                      das Alias keine probleme bereitet

                                      eben erst gelesen und da stellt sich mir die Frage welche DPs als Aliase angelegt sind?

                                      @vumer sagte in Spotify-Premium Adapter:

                                      gesteuert habe ich nur über die Android app oder direkt am Teufel Lautsprecher

                                      ok, Ja, wenn ich mit externen APPs steuere dann hab ich "hinundwieder" auch ähnliche Meldungen.
                                      Aber schau mal hier https://github.com/iobroker-community-adapters/ioBroker.spotify-premium/issues/143

                                      Könnte ähnlich bis gleich sein.

                                      Ich bin da mal ehrlich und sage Dir dass ich den Adapter eigentlich nur noch wenn mal was im Forum steht aktiv nutze.
                                      Steuerung mache ich eh per Alexa oder eben mit externen APPS

                                      Lehrling seit 1975 !!!
                                      Beitrag geholfen ? dann gerne ein upvote rechts unten im Beitrag klicken ;)
                                      https://forum.iobroker.net/topic/51555/hinweise-f%C3%BCr-gute-forenbeitr%C3%A4ge

                                      VumerV 1 Antwort Letzte Antwort
                                      1
                                      • DJMarc75D DJMarc75

                                        @vumer sagte in Spotify-Premium Adapter:

                                        das Alias keine probleme bereitet

                                        eben erst gelesen und da stellt sich mir die Frage welche DPs als Aliase angelegt sind?

                                        @vumer sagte in Spotify-Premium Adapter:

                                        gesteuert habe ich nur über die Android app oder direkt am Teufel Lautsprecher

                                        ok, Ja, wenn ich mit externen APPs steuere dann hab ich "hinundwieder" auch ähnliche Meldungen.
                                        Aber schau mal hier https://github.com/iobroker-community-adapters/ioBroker.spotify-premium/issues/143

                                        Könnte ähnlich bis gleich sein.

                                        Ich bin da mal ehrlich und sage Dir dass ich den Adapter eigentlich nur noch wenn mal was im Forum steht aktiv nutze.
                                        Steuerung mache ich eh per Alexa oder eben mit externen APPS

                                        VumerV Offline
                                        VumerV Offline
                                        Vumer
                                        schrieb am zuletzt editiert von
                                        #26

                                        @djmarc75 sagte in Spotify-Premium Adapter:

                                        eben erst gelesen und da stellt sich mir die Frage welche DPs als Aliase angelegt sind?

                                        In der Tabelle N12.
                                        Es gibt leider keinen Adapter für Teufel Raumfeld. Unter die Direktwahltasten kann man nur einen direkten Titel aus einer Playlist hinterlegen. Die Playlist wir durchgespielt, startet aber mit dem gleichen Titel und nicht immer ist shuffle aktiv. Und dass wenn meine Frau kocht, und die Kartofel nicht die richtige sind, und ... ;)

                                        DJMarc75D 1 Antwort Letzte Antwort
                                        0
                                        • VumerV Vumer

                                          @djmarc75 sagte in Spotify-Premium Adapter:

                                          eben erst gelesen und da stellt sich mir die Frage welche DPs als Aliase angelegt sind?

                                          In der Tabelle N12.
                                          Es gibt leider keinen Adapter für Teufel Raumfeld. Unter die Direktwahltasten kann man nur einen direkten Titel aus einer Playlist hinterlegen. Die Playlist wir durchgespielt, startet aber mit dem gleichen Titel und nicht immer ist shuffle aktiv. Und dass wenn meine Frau kocht, und die Kartofel nicht die richtige sind, und ... ;)

                                          DJMarc75D Offline
                                          DJMarc75D Offline
                                          DJMarc75
                                          schrieb am zuletzt editiert von
                                          #27

                                          @vumer Jetzt würfelst Du aber grad so einiges durcheinander:
                                          Lovelace, Teufel, Spotify, Kartoffeln, usw :grin:
                                          Bei Lovelace und Teufel bin ich eh raus - kenn ich nicht.
                                          Ob daher vll die Adaptercrashes ihren Ursprung haben ?

                                          Lehrling seit 1975 !!!
                                          Beitrag geholfen ? dann gerne ein upvote rechts unten im Beitrag klicken ;)
                                          https://forum.iobroker.net/topic/51555/hinweise-f%C3%BCr-gute-forenbeitr%C3%A4ge

                                          VumerV 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

                                          739

                                          Online

                                          32.4k

                                          Benutzer

                                          81.6k

                                          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