Jahresrückblick 2025 – unser neuer Blogbeitrag ist online! ✨

[Meister Mopper]

@puls200

Ja, es fehlen noch mehr Infos. Was hast Du da für ein System laufen: Hardware, Betriebssystem, JS-Controller, Node.js, NPM.

Und das vielleicht entscheidende Kriterium: Welche Version des Chromecast-Adapters nutzt Du?

[crunchip]

@meister-mopper und Netzwerk

@meister-mopper sagte in Chromecast Adapter: Konfiguration:

Welche Version des Chromecast-Adapters nutzt Du

@puls200 sagte in Chromecast Adapter: Konfiguration:

Chromecast-Adapter (v2.3.1

[puls200]

Hardware: Raspberry Pi 4
CPUs: 4
Geschwindigkeit: 1500 MHz
Modell: ARMv7 Processor rev 3 (v7l)
RAM: 3.75 GB
Node.js: v16.18.1
NPM: 8.19.2
js-controller: 4.0.23
Chromecast-Adapter: v2.3.1
NetzwerK: Unifi Security Gateway + Access Points 2,4/5GHz

[crunchip]

@puls200 sagte in Chromecast Adapter: Konfiguration:

Unter Devices finde ich keinen meiner Google Lautsprecher. Warum wird dort nichts gelistet

und dein Netzwerk?

[puls200]

@crunchip Im WLAN finde ich natürlich alle Lautsprecher. Die funktionieren ja auch. Der SayIt-Adapter funktioniert auch über die Google Minis. Die Vielzahl an Fehler und Warnungen nerven sehr...

[Meister Mopper]

@puls200
In der Instanzkonfiguration stehen die Geräte bei mir auch nicht. Wenn sie in den Objekten auftauchen und sogar funktionieren ist doch alles gut?!

[puls200]

@meister-mopper Jein, jedes Mal, wenn ich einen ioBroker-Check mache, nerven die täglichen 200x Warnungen von Chromecast. Warnungen sind nicht schlimm, aber man kann sie beheben. Oder sind es nur "Warn-Infos", da diese gemeldeten Probleme erst mit zukünftigen Chromecast-Versionen behoben werden können? Wenn ja, warum kategorisiert man diese nicht als Info?

[crunchip]

@puls200 sagte in Chromecast Adapter: Konfiguration:

sind es nur "Warn-Infos

ja, wen Gerät xy nicht erreichbar ist
stell die Logstufe im Adapter auf error

[puls200]

@crunchip Diese Logik ist schon klar, aber WARUM sind die Geräte STÄNDIG nicht erreichbar?

[crunchip]

@puls200 sagte in Chromecast Adapter: Konfiguration:

Geräte STÄNDIG nicht erreichbar

das kann ich dir nicht sagen

[Mike77]

@puls200 said in Chromecast Adapter: Konfiguration:

@crunchip Diese Logik ist schon klar, aber WARUM sind die Geräte STÄNDIG nicht erreichbar?

Geht mir aber genauso.

Aber nicht so oft.... Das Gerät, das ständig Fehlermeldungen erzeugt hat ist mein Nvidia Shield, den hab ich mittlerweile auf Enabled "false" gestellt, weil über den geb ich sowieso nix wieder.

chromecast.0
2022-11-29 07:15:03.753	warn	Oben - Client error: Error: connect ECONNREFUSED 192.168.178.227:32106 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)

chromecast.0
2022-11-29 07:15:03.747	warn	Überall - Client error: Error: connect ECONNREFUSED 192.168.178.227:32197 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)

chromecast.0
2022-11-29 07:15:01.740	warn	Oben - Client error: Error: connect ECONNREFUSED 192.168.178.227:32106 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)

chromecast.0
2022-11-29 07:15:01.738	warn	Überall - Client error: Error: connect ECONNREFUSED 192.168.178.227:32197 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)

chromecast.0
2022-11-29 07:15:00.733	warn	Oben - Client error: Error: connect ECONNREFUSED 192.168.178.227:32106 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)

chromecast.0
2022-11-29 07:15:00.731	warn	Überall - Client error: Error: connect ECONNREFUSED 192.168.178.227:32197 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)

chromecast.0
2022-11-29 07:15:00.657	warn	Oben - Client error: Error: connect ECONNREFUSED 192.168.178.227:32106 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)

chromecast.0
2022-11-29 07:15:00.642	warn	Überall - Client error: Error: connect ECONNREFUSED 192.168.178.227:32197 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)

Hardware: Raspberry Pi 400
CPUs: 4
Geschwindigkeit: 600 MHz
Modell: ARMv7 Processor rev 3 (v7l)
RAM: 3.7 GB
System-Betriebszeit: 18:29:05
Node.js: v16.18.1
NPM: 8.19.2
js-controller: 6.1.4
Chromecast-Adapter: v3.0.3
Netzwerk: FritzBox 6591 <---Lan----> Fritzbox 7590

Mike

[PhoenixCR]

Mir auch :male-detective:

Gibt es hier Neuigkeiten?
Oder nur der Umstellung auf 3?

2022-12-29 18:13:46.252  - info: chromecast.0 (15756) Unload triggered
2022-12-29 18:13:46.253  - info: chromecast.0 (15756) Destroying chromecast scanner
2022-12-29 18:13:46.258  - info: chromecast.0 (15756) Küche - Detached player
2022-12-29 18:13:46.259  - info: chromecast.0 (15756) Küche - Detached player
2022-12-29 18:13:46.261  - info: chromecast.0 (15756) Küche - client disconnected
2022-12-29 18:13:46.262  - info: chromecast.0 (15756) Unload completed sucesfully
2022-12-29 18:13:46.262  - info: chromecast.0 (15756) terminating
2022-12-29 18:13:46.263  - warn: chromecast.0 (15756) Terminated (UNCAUGHT_EXCEPTION): Without reason
2022-12-29 18:13:46.341  - info: chromecast.0 (15756) Küche - Connected client
2022-12-29 18:13:46.356  - error: chromecast.0 (15756) uncaught exception: Cannot read properties of undefined (reading 'getVolume')
2022-12-29 18:13:46.358  - error: chromecast.0 (15756) TypeError: Cannot read properties of undefined (reading 'getVolume')
    at ChromecastDevice._updateClientStatus (/opt/iobroker/node_modules/iobroker.chromecast/lib/chromecastDevice.js:622:80)
    at MediaPlayer.emit (node:events:513:28)
    at PersistentClient.emit (node:events:525:35)
    at PersistentClient._updateStatus (/opt/iobroker/node_modules/castv2-player/lib/persistentClient.js:338:12)
    at /opt/iobroker/node_modules/castv2-player/lib/persistentClient.js:266:20
    at /opt/iobroker/node_modules/castv2-client/lib/controllers/receiver.js:31:5
    at fn.onmessage (/opt/iobroker/node_modules/castv2-client/lib/controllers/request-response.js:27:7)
    at fn.emit (node:events:525:35)
    at Channel.onmessage (/opt/iobroker/node_modules/castv2-client/lib/controllers/controller.js:16:10)
    at Channel.emit (node:events:513:28)
2022-12-29 18:13:46.359  - error: chromecast.0 (15756) Cannot read properties of undefined (reading 'getVolume')
2022-12-29 18:13:46.929  - error: host.homeautomationcretu instance system.adapter.chromecast.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2022-12-29 18:13:46.931  - info: host.homeautomationcretu Restart adapter system.adapter.chromecast.0 because enabled
2022-12-29 18:14:03.754  - info: sayit.0 (13148) saying: Trockner aus
2022-12-29 18:14:03.759  - info: sayit.0 (13148) Set "chromecast.0.Küche.player.announcement to {"url":"http://192.168.1.200:8082/state/sayit.0.tts.mp3","volume":70}
2022-12-29 18:14:16.989  - info: host.homeautomationcretu instance system.adapter.chromecast.0 started with pid 16822
2022-12-29 18:14:18.854  - info: chromecast.0 (16822) starting. Version 2.3.1 in /opt/iobroker/node_modules/iobroker.chromecast, node: v16.19.0, js-controller: 4.0.23
2022-12-29 18:14:19.175  - warn: chromecast.0 (16822) Object chromecast.0.Küche.player.state is invalid: Default value has to be type "number" but received type "string"
2022-12-29 18:14:19.176  - warn: chromecast.0 (16822) This object will not be created in future versions. Please report this to the developer.
2022-12-29 18:14:19.179  - warn: chromecast.0 (16822) Object chromecast.0.Küche.playlist.list is invalid: Default value has to be stringified but received type "object"
2022-12-29 18:14:19.181  - warn: chromecast.0 (16822) This object will not be created in future versions. Please report this to the developer.
2022-12-29 18:14:19.182  - warn: chromecast.0 (16822) Object chromecast.0.Küche.playlist.currentItemId is invalid: Default value has to be type "number" but received type "object"
2022-12-29 18:14:19.183  - warn: chromecast.0 (16822) This object will not be created in future versions. Please report this to the developer.
2022-12-29 18:14:19.184  - warn: chromecast.0 (16822) Object chromecast.0.Küche.player.repeatMode is invalid: Default value has to be type "number" but received type "string"
2022-12-29 18:14:19.185  - warn: chromecast.0 (16822) This object will not be created in future versions. Please report this to the developer.
2022-12-29 18:14:19.187  - warn: chromecast.0 (16822) Object chromecast.0.Küche.player.shuffleMode is invalid: Default value has to be type "boolean" but received type "string"
2022-12-29 18:14:19.188  - warn: chromecast.0 (16822) This object will not be created in future versions. Please report this to the developer.
2022-12-29 18:14:19.356  - info: chromecast.0 (16822) State value to set for "chromecast.0.Küche.port" has to be type "string" but received type "number" 
2022-12-29 18:14:19.403  - info: chromecast.0 (16822) Küche - Connected client
2022-12-29 18:14:19.420  - info: chromecast.0 (16822) Küche - Connected client
2022-12-29 18:14:19.468  - info: chromecast.0 (16822) Küche - Try to join player
2022-12-29 18:14:19.471  - info: chromecast.0 (16822) Küche - Connected player
2022-12-29 18:14:19.473  - info: chromecast.0 (16822) Küche - Player joint
2022-12-29 18:14:19.496  - info: chromecast.0 (16822) Küche - Try to join player
2022-12-29 18:14:19.498  - info: chromecast.0 (16822) Küche - Connected player
2022-12-29 18:14:19.499  - info: chromecast.0 (16822) Küche - Player joint
2022-12-29 18:14:19.565  - info: chromecast.0 (16822) Küche - getStatus

Hardware: Raspberry Pi 400
CPUs: 4
Geschwindigkeit: 1800 MHz
Modell: ARMv7 Processor rev 3 (v7l)
RAM: 7.7 GB
Node.js: v16.19.1
NPM: 8.19.3
js-controller: 6.1.4
Chromecast-Adapter: v2.3.1

Danke!

[Troya]

Selbige Warnungen nerven auch mich...einmal die has to be type:

...
chromecast.02023-01-10 18:06:57.046	warn	Object chromecast.0.Unten.playlist.currentItemId is invalid: Default value has to be type "number" but received type "object"
chromecast.02023-01-10 18:06:57.044	warn	This object will not be created in future versions. Please report this to the developer.
chromecast.02023-01-10 18:06:57.043	warn	Object chromecast.0.Unten.playlist.list is invalid: Default value has to be stringified but received type "object"
chromecast.02023-01-10 18:06:57.042	warn	This object will not be created in future versions. Please report this to the developer.
chromecast.02023-01-10 18:06:57.040	warn	Object chromecast.0.Unten.player.state is invalid: Default value has to be type "number" but received type "string"
chromecast.02023-01-10 18:06:57.022	warn	This object will not be created in future versions. Please report this to the developer.
chromecast.02023-01-10 18:06:57.020	warn	Object chromecast.0.Wohnzimmer.player.shuffleMode is invalid: Default value has to be type "boolean" but received type "string"
chromecast.02023-01-10 18:06:57.018	warn	This object will not be created in future versions. Please report this to the developer.
chromecast.02023-01-10 18:06:57.017	warn	Object chromecast.0.Wohnzimmer.player.repeatMode is invalid: Default value has to be type "number" but received type "string"
chromecast.02023-01-10 18:06:57.017	warn	This object will not be created in future versions. Please report this to the developer.
chromecast.02023-01-10 18:06:57.014	warn	Object chromecast.0.Wohnzimmer.playlist.currentItemId is invalid: Default value has to be type "number" but received type "object"
...

Und dann noch die has no existing object:

...
chromecast.02023-01-10 18:06:58.052	warn	State "chromecast.0.Wohnzimmer_Max.status.connected" has no existing object, this might lead to an error in future versions
chromecast.02023-01-10 18:06:58.051	warn	State "chromecast.0.Wohnzimmer_Max.port" has no existing object, this might lead to an error in future versions
chromecast.02023-01-10 18:06:58.050	warn	State "chromecast.0.Wohnzimmer_Max.address" has no existing object, this might lead to an error in future versions
...

Sind bei jeweils bummelig 50x im Log

mein System

Plattform docker
Betriebssystem linux
Architektur x64
CPUs 2
Geschwindigkeit 2001 MHz
Modell Intel(R) Celeron(R) CPU J3355 @ 2.00GHz
RAM 9.58 GB
Node.js v14.18.3 (Es gibt eine neuere Version: v14.21.2 - Empfohlene Version v16.19.0)