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.
    • 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
                    • T
                      ticaki Developer last edited by

                      v1.1.2 ist auf dem Weg

                      sigi234 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:

                        v1.1.2 ist auf dem Weg

                        plex.0
                        2023-09-17 11:49:11.876	warn	Object of state "plex.0.events.Player" is missing the required property "common.type"
                        

                        RAW:

                        {
                          "common": {
                            "name": "Player Information",
                            "write": false
                          },
                          "type": "channel",
                          "native": {},
                          "from": "system.adapter.plex.0",
                          "user": "system.user.admin",
                          "ts": 1694428241214,
                          "_id": "plex.0.events.Player",
                          "acl": {
                            "object": 1636,
                            "owner": "system.user.admin",
                            "ownerGroup": "system.group.administrator"
                          }
                        }
                        

                        Screenshot (296).png

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

                          @sigi234
                          Hm dachte nur ich hätte diese Warnung... ok muß mal schauen wo das nun wieder her kommt.

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

                            @sigi234
                            Lösche mal die Ordner unter event, oder event gleich ganz. Das gehört da nicht mehr hin.

                            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
                              Lösche mal die Ordner unter event, oder event gleich ganz. Das gehört da nicht mehr hin.

                              Läuft einwandfrei.👍

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

                                Die Version 1.1.3 ist auf dem Weg ins stable, wenn keine Fehler gefunden werden.
                                ca. 1 Woche

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

                                  @ticaki

                                  könntest du mir evtl helfen - was besagt diese fehlermeldung?

                                  
                                  plex.0
                                  2023-11-04 19:04:26.125	warn	catch() 122: {"message":"connect ECONNREFUSED 192.168.178.202:32500","name":"Error","stack":"Error: connect ECONNREFUSED 192.168.178.202:32500\n at AxiosError.from (/opt/iobroker/node_modules/iobroker.plex/node_modules/axios/dist/node/axios.cjs:837:14)\n at RedirectableRequest.handleRequestError (/opt/iobroker/node_modules/iobroker.plex/node_modules/axios/dist/node/axios.cjs:3016:25)\n at RedirectableRequest.emit (node:events:526:35)\n at eventHandlers.<computed> (/opt/iobroker/node_modules/follow-redirects/index.js:14:24)\n at ClientRequest.emit (node:events:514:28)\n at Socket.socketErrorListener (node:_http_client:501:9)\n at Socket.emit (node:events:514:28)\n at emitErrorNT (node:internal/streams/destroy:151:8)\n at emitErrorCloseNT (node:internal/streams/destroy:116:3)\n at process.processTicksAndRejections (node:internal/process/task_queues:82:21)","config":{"transitional":{"silentJSONParsing":true,"forcedJSONParsing":true,"clarifyTimeoutError":false},"adapter":["xhr","http"],"transformRequest":[null],"transformResponse":[null],"timeout":700,"xsrfCookieName":"XSRF-TOKEN","xsrfHeaderName":"X-XSRF-TOKEN","maxContentLength":-1,"maxBodyLength":-1,"env":{},"headers":{"Accept":"application/json, text/plain, */*","X-Plex-Token":"MB-e_x5Gu1AnqxTxHrGQ","X-Plex-Target-Client-Identifier":"f7c8166be109b676-com-plexapp-android","X-Plex-Client-Identifier":"5cc42810-6dc0-44b1-8c70-747152d4f7f9","X-Plex-Device-Name":"AFTR","User-Agent":"axios/1.5.1","Accept-Encoding":"gzip, compress, deflate, br"},"method":"get","url":"http://192.168.178.202:32500/player/timeline/poll?wait=0&commandID=251"},"code":"ECONNREFUSED","status":null}
                                  

                                  die 202 ist der firetv cube - die meldung kommt eine zeit lang, dann verschwindet sie
                                  in welche richtung wird da was refused ?

                                  T 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:

                                    catch() 122

                                    Wenn du von den States nichts logs, lösche mal den Unterzweig zu diesem Player und starte den Adapter neu. Irgendwer hat mir doch erzählt das man das firetv nicht kontrollieren kann.

                                    Und schaue mal was du du hier für eine Antwort bekommst:

                                    http://192.168.178.202:32500/player/timeline/poll?wait=0&commandID=251"
                                    
                                    liv-in-sky 1 Reply Last reply Reply Quote 0
                                    • liv-in-sky
                                      liv-in-sky @ticaki last edited by

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

                                      http://192.168.178.202:32500/player/timeline/poll?wait=0&commandID=251"

                                      da kommt keine verbindung möglich

                                      das löschn der dp und dann der start des adapters bringt keine fehler im moment

                                      ich muss aber mal morgen nochmal nachsehen, den das ganze kommt, wenn ich die server (plex,tautulli) und den tv( mit fire cube) alle gleichzeitig einschalte - evtl muss ich da eine rehenfolge beachten - geht gerade nicht 😞

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

                                        @liv-in-sky

                                        Erstmal der Fehler ist egal, wird abgefangen und behandelt nervt nur im log. Aber durch das löschen der States ist entweder die ip oder der port verschwunden(weiß net mehr was es genau war) und damit weiß der Adapter das der Player das nicht unterstützt und versuchts erst garnicht.

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

                                          @ticaki

                                          schau mal - ist wieder da - ic schalt mal das log der instanz auf "error" 🙂

                                             catch() 122: {"message":"connect ECONNREFUSED 192.168.178.202:32500","name":"Error","stack":"Error: connect ECONNREFUSED 192.168.178.202:32500\n at AxiosError.from (/opt/iobroker/node_modules/iobroker.plex/node_modules/axios/dist/node/axios.cjs:837:14)\n at RedirectableRequest.handleRequestError (/opt/iobroker/node_modules/iobroker.plex/node_modules/axios/dist/node/axios.cjs:3016:25)\n at RedirectableRequest.emit (node:events:526:35)\n at eventHandlers.<computed> (/opt/iobroker/node_modules/follow-redirects/index.js:14:24)\n at ClientRequest.emit (node:events:514:28)\n at Socket.socketErrorListener (node:_http_client:501:9)\n at Socket.emit (node:events:514:28)\n at emitErrorNT (node:internal/streams/destroy:151:8)\n at emitErrorCloseNT (node:internal/streams/destroy:116:3)\n at process.processTicksAndRejections (node:internal/process/task_queues:82:21)","config":{"transitional":{"silentJSONParsing":true,"forcedJSONParsing":true,"clarifyTimeoutError":false},"adapter":["xhr","http"],"transformRequest":[null],"transformResponse":[null],"timeout":700,"xsrfCookieName":"XSRF-TOKEN","xsrfHeaderName":"X-XSRF-TOKEN","maxContentLength":-1,"maxBodyLength":-1,"env":{},"headers":{"Accept":"application/json, text/plain, */*","X-Plex-Token":"MB-e_x5Gu1AnqxTxHrGQ","X-Plex-Target-Client-Identifier":"f7c8166be109b676-com-plexapp-android","X-Plex-Client-Identifier":"5cc42810-6dc0-44b1-8c70-747152d4f7f9","X-Plex-Device-Name":"AFTR","User-Agent":"axios/1.5.1","Accept-Encoding":"gzip, compress, deflate, br"},"method":"get","url":"http://192.168.178.202:32500/player/timeline/poll?wait=0&commandID=128"},"code":"ECONNREFUSED","status":null}
                                          

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

                                            @liv-in-sky
                                            a) gib mir mal die Daten dieses Gerätes damit mal sehen kann ob ich infos finde 192.168.178.202
                                            b) ich hab ne Version auf Github hochgeladen, wo die Meldung ins debug geschrieben wird.

                                            liv-in-sky 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            893
                                            Online

                                            31.7k
                                            Users

                                            79.7k
                                            Topics

                                            1.3m
                                            Posts

                                            adapter plex tautulli
                                            7
                                            250
                                            23081
                                            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