Weihnachtsangebot 2025! 🎄

[Thomas Braun]

@vumer sagte in Spotify-Premium Adapter:

playlist error 503

Schaut nach irendwas auf dem Server aus. Wenn das ein html-Error Code sein sollte.

[Vumer]

@djmarc75 sagte in Spotify-Premium Adapter:

System aktuell ?

Jaa,
proxmox ist noch 6.4, sonst alles up to date

[Vumer]

@thomas-braun sagte in Spotify-Premium Adapter:

Schaut nach irendwas auf dem Server aus. Wenn das ein html-Error Code sein sollte.

steh auf dem Schlauch, was kann ich machen? Wo anfangen?
Fehler tritt aber nur mit dem Spotify Adapter auf

[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.

[Vumer]

@djmarc75 sagte in Spotify-Premium Adapter:

ja? zeig mal bitte.

[Vumer]

@djmarc75 sagte in Spotify-Premium Adapter:

seitens Spotify

ach so

Danke Euch :+1:

[Thomas Braun]

@vumer

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

[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

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

[DJMarc75]

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

[Vumer]

@djmarc75
Spotify Installierte Version: 1.2.2
Admin 6.2.23

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

[DJMarc75]

@vumer jo, Adapter sind aktuell...

erstmal:

sudo apt update

Ausgabe bitte komplett zeigen.

[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.

[DJMarc75]

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

[Vumer]

@djmarc75

[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

[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.

[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

[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

[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 :)

[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...