Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Tester
    4. Test Adapter Plex v1.1.x

    NEWS

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    Test Adapter Plex v1.1.x

    This topic has been deleted. Only users with topic management privileges can see it.
    • T
      ticaki Developer @sigi234 last edited by

      @sigi234
      Ich weiß nicht wirklich was die grandpa Datenpunkte sind. ist das die Show bei einer Serie?

      sigi234 1 Reply Last reply Reply Quote 0
      • sigi234
        sigi234 Forum Testing Most Active @ticaki last edited by

        @ticaki sagte in Test Adapter Plex v1.1.x:

        @sigi234
        Ich weiß nicht wirklich was die grandpa Datenpunkte sind. ist das die Show bei einer Serie?

        Keine Ahnung, hat was mit Serie zu tun.

        T 2 Replies Last reply Reply Quote 0
        • T
          ticaki Developer @sigi234 last edited by ticaki

          @sigi234
          Hast du einen Begriff für Musik, Film, Photo - des Multimediainhalts? Inhalts? Werks? Kunstwerks? Ich kann mich nicht entscheiden. Elements... Ich favorisiere Elements oder Multimediainhalts. Hab mich für Multimediainhalt entschieden ok?

          sigi234 1 Reply Last reply Reply Quote 0
          • T
            ticaki Developer @sigi234 last edited by

            @sigi234
            Noch was, wenn du einen Datenpunkt hast der (no description) heißt ist der nicht definiert, da muß ich wissen was drin steht - der wird immer mit {'name': '(no description given)', 'role': 'state', 'type': 'string'} erzeugt.

            sigi234 2 Replies Last reply Reply Quote 0
            • sigi234
              sigi234 Forum Testing Most Active @ticaki last edited by

              @ticaki sagte in Test Adapter Plex v1.1.x:

              Hab mich für Multimediainhalt entschieden ok?

              👍

              1 Reply Last reply Reply Quote 0
              • sigi234
                sigi234 Forum Testing Most Active @ticaki last edited by sigi234

                @ticaki sagte in Test Adapter Plex v1.1.x:

                da muß ich wissen was drin steht

                WO? Im RAW

                T 1 Reply Last reply Reply Quote 0
                • sigi234
                  sigi234 Forum Testing Most Active @ticaki last edited by

                  @ticaki

                  Hallo, gibt es was Neues?

                  1 Reply Last reply Reply Quote 0
                  • T
                    ticaki Developer @sigi234 last edited by ticaki

                    @sigi234

                    Hab morgen Zeit. Ich muss wissen was im Datenfeld steht. Also in dem Fall von oben wird es wohl das Studio als string sein

                    sigi234 1 Reply Last reply Reply Quote 0
                    • sigi234
                      sigi234 Forum Testing Most Active @ticaki last edited by

                      @ticaki sagte in Test Adapter Plex v1.1.x:

                      Ich muss wissen was im Datenfeld steht.

                      Welchen DP?

                      T 1 Reply Last reply Reply Quote 0
                      • T
                        ticaki Developer @sigi234 last edited by

                        @sigi234

                        parentStudio - aber bei dem kann ich es mir Denken, das produzierende Studio des Albums/Staffel, Zeichenkette.

                        Die Datenpunkte zu Tautulli werden nicht angepasst, weil die jeder Nutzer selbst für sich definieren kann.

                        Morgen gibts ein neues Release, ist fast alles was gemeldet wurde behoben. Um deinen Fernseher können wir uns vielleicht am Sonntag kümmern.

                        sigi234 1 Reply Last reply Reply Quote 1
                        • sigi234
                          sigi234 Forum Testing Most Active @ticaki last edited by

                          @ticaki sagte in Test Adapter Plex v1.1.x:

                          parentStudio - aber bei dem kann ich es mir Denken, das produzierende Studio des Albums/Staffel, Zeichenkette.

                          Wert:

                          MCA Records
                          
                          {
                            "common": {
                              "name": "(no description given)",
                              "role": "state",
                              "type": "string",
                              "write": false
                            },
                            "type": "state",
                            "native": {},
                            "from": "system.adapter.plex.0",
                            "user": "system.user.admin",
                            "ts": 1694430224466,
                            "_id": "plex.0.events.Metadata.parentStudio",
                            "acl": {
                              "object": 1636,
                              "state": 1636,
                              "owner": "system.user.admin",
                              "ownerGroup": "system.group.administrator"
                            }
                          }
                          
                          1 Reply Last reply Reply Quote 0
                          • T
                            ticaki Developer last edited by ticaki

                            v.1.1.1 demnächst im latest

                            nur Fehlerbehebungen, kaum geändertes Verhalten.

                            Ich weiß noch nciht ob ich die Metadata.*.Media.url Datenpunkte lassen oder entfernen soll. Unter Music ist er definiert und ein Link auf den abgespielten Inhalt. Das gibts auch für alles andere. Drin lassen und definieren (dann ist es eine url) oder raus werfen?

                            liv-in-sky 1 Reply Last reply Reply Quote 0
                            • liv-in-sky
                              liv-in-sky @ticaki last edited by

                              @ticaki

                              hi- habe auf neuen js-controller upgedatet - bekomme nun das

                              host.iobroker59
                              	2023-09-16 20:13:41.032	warn	Do not restart adapter system.adapter.plex.0 because restart loop detected
                              host.iobroker59
                              	2023-09-16 20:13:41.032	error	instance system.adapter.plex.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
                              plex.0
                              	2023-09-16 20:13:40.355	error	400 - {"response":{"result":"error","message":"Invalid apikey","data":{}}}
                              plex.0
                              	2023-09-16 20:13:40.355	error	StatusCodeError: 400 - {"response":{"result":"error","message":"Invalid apikey","data":{}}} at new StatusCodeError (/opt/iobroker/node_modules/request-promise-core/lib/errors.js:32:15) at plumbing.callback (/opt/iobroker/node_modules/request-promise-core/lib/plumbing.js:104:33) at Request.RP$callback [as _callback] (/opt/iobroker/node_modules/request-promise-core/lib/plumbing.js:46:31) at self.callback (/opt/iobroker/node_modules/request/request.js:185:22) at Request.emit (node:events:514:28) at Request.<anonymous> (/opt/iobroker/node_modules/request/request.js:1154:10) at Request.emit (node:events:514:28) at IncomingMessage.<anonymous> (/opt/iobroker/node_modules/request/request.js:1076:12) at Object.onceWrapper (node:events:628:28) at IncomingMessage.emit (node:events:526:35) at endReadableNT (node:internal/streams/readable:1359:12) at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
                              plex.0
                              	2023-09-16 20:13:40.355	error	unhandled promise rejection: 400 - {"response":{"result":"error","message":"Invalid apikey","data":{}}}
                              plex.0
                              	2023-09-16 20:13:40.355	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().
                              plex.0
                              	2023-09-16 20:13:40.341	error	400 - {"response":{"result":"error","message":"Invalid apikey","data":{}}}
                              plex.0
                              	2023-09-16 20:13:40.341	error	StatusCodeError: 400 - {"response":{"result":"error","message":"Invalid apikey","data":{}}} at new StatusCodeError (/opt/iobroker/node_modules/request-promise-core/lib/errors.js:32:15) at plumbing.callback (/opt/iobroker/node_modules/request-promise-core/lib/plumbing.js:104:33) at Request.RP$callback [as _callback] (/opt/iobroker/node_modules/request-promise-core/lib/plumbing.js:46:31) at self.callback (/opt/iobroker/node_modules/request/request.js:185:22) at Request.emit (node:events:514:28) at Request.<anonymous> (/opt/iobroker/node_modules/request/request.js:1154:10) at Request.emit (node:events:514:28) at IncomingMessage.<anonymous> (/opt/iobroker/node_modules/request/request.js:1076:12) at Object.onceWrapper (node:events:628:28) at IncomingMessage.emit (node:events:526:35) at endReadableNT (node:internal/streams/readable:1359:12) at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
                              plex.0
                              	2023-09-16 20:13:40.340	error	unhandled promise rejection: 400 - {"response":{"result":"error","message":"Invalid apikey","data":{}}}
                              plex.0
                              	2023-09-16 20:13:40.340	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().
                              plex.0
                              	2023-09-16 20:13:40.311	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
                              plex.0
                              	2023-09-16 20:13:40.310	info	terminating
                              

                              den api key habe ich neu eingerichtet und es kam auch kein fehler

                              hast du eine ahnung, was da sein könnte

                              T 1 Reply Last reply Reply Quote 0
                              • T
                                ticaki Developer @liv-in-sky last edited by

                                @liv-in-sky
                                Noch nicht 🙂

                                Hab gerade einen neue Token abgerufen und es läuft bei mir. (dev-server) Kannst du das mal mit Debuglog wiederholen?

                                liv-in-sky 2 Replies Last reply Reply Quote 0
                                • liv-in-sky
                                  liv-in-sky @ticaki last edited by

                                  @ticaki

                                  hast du den neuen js-controller ?

                                  host.iobroker59
                                     2023-09-16 20:44:43.541	warn	Do not restart adapter system.adapter.plex.0 because restart loop detected
                                  host.iobroker59
                                     2023-09-16 20:44:43.540	error	instance system.adapter.plex.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
                                  plex.0
                                     2023-09-16 20:44:42.878	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
                                  plex.0
                                     2023-09-16 20:44:42.878	info	terminating
                                  plex.0
                                     2023-09-16 20:44:42.878	info	Plex Adapter stopped und unloaded.
                                  plex.0
                                     2023-09-16 20:44:42.877	error	400 - {"response":{"result":"error","message":"Invalid apikey","data":{}}}
                                  plex.0
                                     2023-09-16 20:44:42.877	error	StatusCodeError: 400 - {"response":{"result":"error","message":"Invalid apikey","data":{}}} at new StatusCodeError (/opt/iobroker/node_modules/request-promise-core/lib/errors.js:32:15) at plumbing.callback (/opt/iobroker/node_modules/request-promise-core/lib/plumbing.js:104:33) at Request.RP$callback [as _callback] (/opt/iobroker/node_modules/request-promise-core/lib/plumbing.js:46:31) at self.callback (/opt/iobroker/node_modules/request/request.js:185:22) at Request.emit (node:events:514:28) at Request.<anonymous> (/opt/iobroker/node_modules/request/request.js:1154:10) at Request.emit (node:events:514:28) at IncomingMessage.<anonymous> (/opt/iobroker/node_modules/request/request.js:1076:12) at Object.onceWrapper (node:events:628:28) at IncomingMessage.emit (node:events:526:35) at endReadableNT (node:internal/streams/readable:1359:12) at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
                                  plex.0
                                     2023-09-16 20:44:42.877	error	unhandled promise rejection: 400 - {"response":{"result":"error","message":"Invalid apikey","data":{}}}
                                  plex.0
                                     2023-09-16 20:44:42.877	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().
                                  plex.0
                                     2023-09-16 20:44:42.876	error	400 - {"response":{"result":"error","message":"Invalid apikey","data":{}}}
                                  plex.0
                                     2023-09-16 20:44:42.876	error	StatusCodeError: 400 - {"response":{"result":"error","message":"Invalid apikey","data":{}}} at new StatusCodeError (/opt/iobroker/node_modules/request-promise-core/lib/errors.js:32:15) at plumbing.callback (/opt/iobroker/node_modules/request-promise-core/lib/plumbing.js:104:33) at Request.RP$callback [as _callback] (/opt/iobroker/node_modules/request-promise-core/lib/plumbing.js:46:31) at self.callback (/opt/iobroker/node_modules/request/request.js:185:22) at Request.emit (node:events:514:28) at Request.<anonymous> (/opt/iobroker/node_modules/request/request.js:1154:10) at Request.emit (node:events:514:28) at IncomingMessage.<anonymous> (/opt/iobroker/node_modules/request/request.js:1076:12) at Object.onceWrapper (node:events:628:28) at IncomingMessage.emit (node:events:526:35) at endReadableNT (node:internal/streams/readable:1359:12) at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
                                  plex.0
                                     2023-09-16 20:44:42.876	error	unhandled promise rejection: 400 - {"response":{"result":"error","message":"Invalid apikey","data":{}}}
                                  plex.0
                                     2023-09-16 20:44:42.876	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().
                                  plex.0
                                     2023-09-16 20:44:42.876	error	400 - {"response":{"result":"error","message":"Invalid apikey","data":{}}}
                                  plex.0
                                     2023-09-16 20:44:42.876	error	StatusCodeError: 400 - {"response":{"result":"error","message":"Invalid apikey","data":{}}} at new StatusCodeError (/opt/iobroker/node_modules/request-promise-core/lib/errors.js:32:15) at plumbing.callback (/opt/iobroker/node_modules/request-promise-core/lib/plumbing.js:104:33) at Request.RP$callback [as _callback] (/opt/iobroker/node_modules/request-promise-core/lib/plumbing.js:46:31) at self.callback (/opt/iobroker/node_modules/request/request.js:185:22) at Request.emit (node:events:514:28) at Request.<anonymous> (/opt/iobroker/node_modules/request/request.js:1154:10) at Request.emit (node:events:514:28) at IncomingMessage.<anonymous> (/opt/iobroker/node_modules/request/request.js:1076:12) at Object.onceWrapper (node:events:628:28) at IncomingMessage.emit (node:events:526:35) at endReadableNT (node:internal/streams/readable:1359:12) at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
                                  plex.0
                                     2023-09-16 20:44:42.876	error	unhandled promise rejection: 400 - {"response":{"result":"error","message":"Invalid apikey","data":{}}}
                                  plex.0
                                     2023-09-16 20:44:42.876	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().
                                  plex.0
                                     2023-09-16 20:44:42.876	error	400 - {"response":{"result":"error","message":"Invalid apikey","data":{}}}
                                  plex.0
                                     2023-09-16 20:44:42.875	error	StatusCodeError: 400 - {"response":{"result":"error","message":"Invalid apikey","data":{}}} at new StatusCodeError (/opt/iobroker/node_modules/request-promise-core/lib/errors.js:32:15) at plumbing.callback (/opt/iobroker/node_modules/request-promise-core/lib/plumbing.js:104:33) at Request.RP$callback [as _callback] (/opt/iobroker/node_modules/request-promise-core/lib/plumbing.js:46:31) at self.callback (/opt/iobroker/node_modules/request/request.js:185:22) at Request.emit (node:events:514:28) at Request.<anonymous> (/opt/iobroker/node_modules/request/request.js:1154:10) at Request.emit (node:events:514:28) at IncomingMessage.<anonymous> (/opt/iobroker/node_modules/request/request.js:1076:12) at Object.onceWrapper (node:events:628:28) at IncomingMessage.emit (node:events:526:35) at endReadableNT (node:internal/streams/readable:1359:12) at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
                                  plex.0
                                     2023-09-16 20:44:42.875	error	unhandled promise rejection: 400 - {"response":{"result":"error","message":"Invalid apikey","data":{}}}
                                  plex.0
                                     2023-09-16 20:44:42.875	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().
                                  plex.0
                                     2023-09-16 20:44:42.875	error	400 - {"response":{"result":"error","message":"Invalid apikey","data":{}}}
                                  plex.0
                                     2023-09-16 20:44:42.875	error	StatusCodeError: 400 - {"response":{"result":"error","message":"Invalid apikey","data":{}}} at new StatusCodeError (/opt/iobroker/node_modules/request-promise-core/lib/errors.js:32:15) at plumbing.callback (/opt/iobroker/node_modules/request-promise-core/lib/plumbing.js:104:33) at Request.RP$callback [as _callback] (/opt/iobroker/node_modules/request-promise-core/lib/plumbing.js:46:31) at self.callback (/opt/iobroker/node_modules/request/request.js:185:22) at Request.emit (node:events:514:28) at Request.<anonymous> (/opt/iobroker/node_modules/request/request.js:1154:10) at Request.emit (node:events:514:28) at IncomingMessage.<anonymous> (/opt/iobroker/node_modules/request/request.js:1076:12) at Object.onceWrapper (node:events:628:28) at IncomingMessage.emit (node:events:526:35) at endReadableNT (node:internal/streams/readable:1359:12) at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
                                  plex.0
                                     2023-09-16 20:44:42.875	error	unhandled promise rejection: 400 - {"response":{"result":"error","message":"Invalid apikey","data":{}}}
                                  plex.0
                                     2023-09-16 20:44:42.874	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().
                                  plex.0
                                     2023-09-16 20:44:42.841	debug	Retrieved Settings from Plex.
                                  plex.0
                                     2023-09-16 20:44:42.824	debug	Retrieved Playlists from Plex.
                                  plex.0
                                     2023-09-16 20:44:42.811	debug	Retrieved Libraries from Plex.
                                  plex.0
                                     2023-09-16 20:44:42.791	debug	StatusCodeError: 400 - {"response":{"result":"error","message":"Invalid apikey","data":{}}}
                                  plex.0
                                     2023-09-16 20:44:42.791	debug	Could not retrieve Users from Tautulli!
                                  plex.0
                                     2023-09-16 20:44:42.777	debug	Start getting client details _playing.aftr-f7c8166be109b676-com-plexapp-android - timeline,playback,mirror,playqueues,provider-playback - 192.168.178.202 - 32500
                                  plex.0
                                     2023-09-16 20:44:42.775	debug	setClientData config object from player _playing.aftr-f7c8166be109b676-com-plexapp-android is {"name":"AFTR","host":"192.168.178.202","address":"192.168.178.202","port":32500,"machineIdentifier":"f7c8166be109b676-com-plexapp-android","version":"9.30.0.3604","protocol":"plex","product":"Plex for Android (TV)","deviceClass":"mobile","protocolVersion":"1","protocolCapabilities":"timeline,playback,mirror,playqueues,provider-playback"}
                                  plex.0
                                     2023-09-16 20:44:42.775	debug	Create player with prefix "_playing.aftr-f7c8166be109b676-com-plexapp-android", localAddress "192.168.178.202" and port "32500"
                                  plex.0
                                     2023-09-16 20:44:42.773	debug	Retrieved Players from Plex. JSON: {"MediaContainer":{"size":1,"Server":[{"name":"AFTR","host":"192.168.178.202","address":"192.168.178.202","port":32500,"machineIdentifier":"f7c8166be109b676-com-plexapp-android","version":"9.30.0.3604","protocol":"plex","product":"Plex for Android (TV)","deviceClass":"mobile","protocolVersion":"1","protocolCapabilities":"timeline,playback,mirror,playqueues,provider-playback"}]}}
                                  plex.0
                                     2023-09-16 20:44:42.770	debug	Retrieved Servers from Plex.
                                  plex.0
                                     2023-09-16 20:44:41.720	debug	Retrieved playing now from plex server: {"size":0}
                                  plex.0
                                     2023-09-16 20:44:41.513	info	Establishing insecure connection to Plex Media Server...
                                  plex.0
                                     2023-09-16 20:44:41.474	info	starting. Version 1.1.1 (non-npm: iobroker-community-adapters/ioBroker.plex#2ef8ff88552fecba6bd199dc30349b9e8c4359c1) in /opt/iobroker/node_modules/iobroker.plex, node: v18.17.1, js-controller: 5.0.12
                                  

                                  T 1 Reply Last reply Reply Quote 0
                                  • liv-in-sky
                                    liv-in-sky @ticaki last edited by

                                    @ticaki

                                    ok - habe mal alles mit tautulli rausgenommen - der adapter funktioniert jetzt

                                    das scheint mein problem zu sein - muss mich damit nochmal rihtig beschäftigen

                                    1 Reply Last reply Reply Quote 0
                                    • T
                                      ticaki Developer @liv-in-sky last edited by

                                      @liv-in-sky sagte in Test Adapter Plex v1.1.x:

                                      debug StatusCodeError: 400 - {"response":{"result":"error","message":"Invalid apikey","data":{}}} plex.0
                                      debug Could not retrieve Users from Tautulli!

                                      adapter.log.debug('Could not retrieve Users from Tautulli!');
                                      adapter.log.debug(err);
                                      

                                      Der Tautulli Api-key ist falsch. Dann trag ich den auch mal falsch ein und suche wo der absturz ist 🙂

                                      liv-in-sky 2 Replies Last reply Reply Quote 0
                                      • liv-in-sky
                                        liv-in-sky @ticaki last edited by

                                        @ticaki hatte ich eigentlich auch neu gemacht - ich versuch es nochmal

                                        1 Reply Last reply Reply Quote 0
                                        • liv-in-sky
                                          liv-in-sky @ticaki last edited by

                                          @ticaki

                                          habe es nochmal neu eingerichtet - jetzt ist eine verbindung da - das war irgendwie mein eingestellter mist ! sorry

                                          T 1 Reply Last reply Reply Quote 0
                                          • T
                                            ticaki Developer @liv-in-sky last edited by

                                            @liv-in-sky

                                            2023-09-16 21:17:42.017  - error: plex.0 (127081) Tautulli configuration data are incorrect. IP: http://192.168.179.16 Port:  Api-Key: sddsaafadsass Error: RequestError: Error: getaddrinfo ENOTFOUND http
                                            

                                            ab version 1.1.2

                                            Nix zu sorryien 😄 , das war ein Fehler(seit 4 Jahren), ein Adapter sollte niemals abstürzen.

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

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            469
                                            Online

                                            31.7k
                                            Users

                                            79.8k
                                            Topics

                                            1.3m
                                            Posts

                                            adapter plex tautulli
                                            7
                                            250
                                            23152
                                            Loading More Posts
                                            • Oldest to Newest
                                            • Newest to Oldest
                                            • Most Votes
                                            Reply
                                            • Reply as topic
                                            Log in to reply
                                            Community
                                            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                            The ioBroker Community 2014-2023
                                            logo