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. Tester
  4. Test Adapter zoneminder v0.3.x

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.6k

Test Adapter zoneminder v0.3.x

Geplant Angeheftet Gesperrt Verschoben Tester
zonemindermotioncamera
206 Beiträge 23 Kommentatoren 32.8k Aufrufe 26 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.
  • D djsirius

    @Meistertr zoneminder.png

    MeistertrM Offline
    MeistertrM Offline
    Meistertr
    Developer
    schrieb am zuletzt editiert von
    #128

    @djsirius debuglog vom start wäre interessant

    D 1 Antwort Letzte Antwort
    0
    • MeistertrM Meistertr

      @djsirius debuglog vom start wäre interessant

      D Offline
      D Offline
      djsirius
      schrieb am zuletzt editiert von
      #129

      @Meistertr Habe ich dir per Chat zukommen lassen.

      Gruß

      djsirius

      1 Antwort Letzte Antwort
      0
      • MeistertrM Offline
        MeistertrM Offline
        Meistertr
        Developer
        schrieb am zuletzt editiert von
        #130

        so in der 0.3.2 sollten nun alle loginprobleme gelößt sein..

        1 Antwort Letzte Antwort
        0
        • MeistertrM Offline
          MeistertrM Offline
          Meistertr
          Developer
          schrieb am zuletzt editiert von
          #131

          so also die login probleme sehe ich nun mit der 0.3.2 als erledigt an und wende mich nun wieder dem ausweiten der Funktionen zu.

          M 1 Antwort Letzte Antwort
          0
          • MeistertrM Meistertr

            so also die login probleme sehe ich nun mit der 0.3.2 als erledigt an und wende mich nun wieder dem ausweiten der Funktionen zu.

            M Offline
            M Offline
            mikiline
            schrieb am zuletzt editiert von mikiline
            #132

            @Meistertr
            Vielen Dank funktioniert. Top!

            ZMEvent kommen leider auch keine Daten.
            zmevent.PNG
            Einzig, nach einer bestimmten Zeit verliert er die Verbindung und nach neustart des Adapters geht es wieder....

            host.nuc-ubuntu	2019-11-04 05:44:23.025	error	Caught by controller[6]: at process._tickCallback (internal/process/next_tick.js:63:19)
            host.nuc-ubuntu	2019-11-04 05:44:23.025	error	Caught by controller[6]: at endReadableNT (_stream_readable.js:1145:12)
            host.nuc-ubuntu	2019-11-04 05:44:23.025	error	Caught by controller[6]: at IncomingMessage.emit (events.js:203:15)
            host.nuc-ubuntu	2019-11-04 05:44:23.025	error	Caught by controller[6]: at Object.onceWrapper (events.js:286:20)
            host.nuc-ubuntu	2019-11-04 05:44:23.025	error	Caught by controller[6]: at IncomingMessage.<anonymous> (/opt/iobroker/node_modules/request/request.js:1083:12)
            host.nuc-ubuntu	2019-11-04 05:44:23.025	error	Caught by controller[6]: at Request.emit (events.js:198:13)
            host.nuc-ubuntu	2019-11-04 05:44:23.025	error	Caught by controller[6]: at Request.<anonymous> (/opt/iobroker/node_modules/request/request.js:1161:10)
            host.nuc-ubuntu	2019-11-04 05:44:23.025	error	Caught by controller[6]: at Request.emit (events.js:198:13)
            host.nuc-ubuntu	2019-11-04 05:44:23.025	error	Caught by controller[6]: at Request.self.callback (/opt/iobroker/node_modules/request/request.js:185:22)
            host.nuc-ubuntu	2019-11-04 05:44:23.025	error	Caught by controller[6]: at Request.RP$callback [as _callback] (/opt/iobroker/node_modules/request-promise-core/lib/plumbing.js:46:31)
            host.nuc-ubuntu	2019-11-04 05:44:23.025	error	Caught by controller[6]: at Request.plumbing.callback (/opt/iobroker/node_modules/request-promise-core/lib/plumbing.js:104:33)
            host.nuc-ubuntu	2019-11-04 05:44:23.025	error	Caught by controller[6]: at new StatusCodeError (/opt/iobroker/node_modules/request-promise-core/lib/errors.js:32:15)
            host.nuc-ubuntu	2019-11-04 05:44:23.025	error	Caught by controller[6]: Unhandled rejection StatusCodeError: 401 - "{\"success\":false,\"data\":{\"name\":\"Expired token\",\"message\":\"Expired token\",\"url\":\"\\/zm\\/api\\/monitors.json?token=
            host.nuc-ubuntu	2019-11-04 05:44:23.025	error	Caught by controller[5]: at process._tickCallback (internal/process/next_tick.js:63:19)
            host.nuc-ubuntu	2019-11-04 05:44:23.025	error	Caught by controller[5]: at endReadableNT (_stream_readable.js:1145:12)
            host.nuc-ubuntu	2019-11-04 05:44:23.025	error	Caught by controller[5]: at IncomingMessage.emit (events.js:203:15)
            host.nuc-ubuntu	2019-11-04 05:44:23.025	error	Caught by controller[5]: at Object.onceWrapper (events.js:286:20)
            host.nuc-ubuntu	2019-11-04 05:44:23.025	error	Caught by controller[5]: at IncomingMessage.<anonymous> (/opt/iobroker/node_modules/request/request.js:1083:12)
            host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[5]: at Request.emit (events.js:198:13)
            host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[5]: at Request.<anonymous> (/opt/iobroker/node_modules/request/request.js:1161:10)
            host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[5]: at Request.emit (events.js:198:13)
            host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[5]: at Request.self.callback (/opt/iobroker/node_modules/request/request.js:185:22)
            host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[5]: at Request.RP$callback [as _callback] (/opt/iobroker/node_modules/request-promise-core/lib/plumbing.js:46:31)
            host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[5]: at Request.plumbing.callback (/opt/iobroker/node_modules/request-promise-core/lib/plumbing.js:104:33)
            host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[5]: at new StatusCodeError (/opt/iobroker/node_modules/request-promise-core/lib/errors.js:32:15)
            host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[5]: Unhandled rejection StatusCodeError: 401 - "{\"success\":false,\"data\":{\"name\":\"Expired token\",\"message\":\"Expired token\",\"url\":\"\\/zm\\/api\\/monitors.json?token=
            host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[4]: at process._tickCallback (internal/process/next_tick.js:63:19)
            host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[4]: at endReadableNT (_stream_readable.js:1145:12)
            host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[4]: at IncomingMessage.emit (events.js:203:15)
            host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[4]: at Object.onceWrapper (events.js:286:20)
            host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[4]: at IncomingMessage.<anonymous> (/opt/iobroker/node_modules/request/request.js:1083:12)
            host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[4]: at Request.emit (events.js:198:13)
            host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[4]: at Request.<anonymous> (/opt/iobroker/node_modules/request/request.js:1161:10)
            host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[4]: at Request.emit (events.js:198:13)
            host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[4]: at Request.self.callback (/opt/iobroker/node_modules/request/request.js:185:22)
            host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[4]: at Request.RP$callback [as _callback] (/opt/iobroker/node_modules/request-promise-core/lib/plumbing.js:46:31)
            host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[4]: at Request.plumbing.callback (/opt/iobroker/node_modules/request-promise-core/lib/plumbing.js:104:33)
            host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[4]: at new StatusCodeError (/opt/iobroker/node_modules/request-promise-core/lib/errors.js:32:15)
            host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[4]: Unhandled rejection StatusCodeError: 401 - "{\"success\":false,\"data\":{\"name\":\"Expired token\",\"message\":\"Expired token\",\"url\":\"\\/zm\\/api\\/monitors.json?token=
            host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[3]: at process._tickCallback (internal/process/next_tick.js:63:19)
            host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[3]: at endReadableNT (_stream_readable.js:1145:12)
            host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[3]: at IncomingMessage.emit (events.js:203:15)
            host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[3]: at Object.onceWrapper (events.js:286:20)
            host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[3]: at IncomingMessage.<anonymous> (/opt/iobroker/node_modules/request/request.js:1083:12)
            host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[3]: at Request.emit (events.js:198:13)
            host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[3]: at Request.<anonymous> (/opt/iobroker/node_modules/request/request.js:1161:10)
            host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[3]: at Request.emit (events.js:198:13)
            host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[3]: at Request.self.callback (/opt/iobroker/node_modules/request/request.js:185:22)
            host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[3]: at Request.RP$callback [as _callback] (/opt/iobroker/node_modules/request-promise-core/lib/plumbing.js:46:31)
            host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[3]: at Request.plumbing.callback (/opt/iobroker/node_modules/request-promise-core/lib/plumbing.js:104:33)
            host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[3]: at new StatusCodeError (/opt/iobroker/node_modules/request-promise-core/lib/errors.js:32:15)
            host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[3]: Unhandled rejection StatusCodeError: 401 - "{\"success\":false,\"data\":{\"name\":\"Expired token\",\"message\":\"Expired token\",\"url\":\"\\/zm\\/api\\/monitors.json?token=
            host.nuc-ubuntu	2019-11-04 05:44:23.023	error	Caught by controller[2]: at process._tickCallback (internal/process/next_tick.js:63:19)
            host.nuc-ubuntu	2019-11-04 05:44:23.023	error	Caught by controller[2]: at endReadableNT (_stream_readable.js:1145:12)
            host.nuc-ubuntu	2019-11-04 05:44:23.023	error	Caught by controller[2]: at IncomingMessage.emit (events.js:203:15)
            host.nuc-ubuntu	2019-11-04 05:44:23.023	error	Caught by controller[2]: at Object.onceWrapper (events.js:286:20)
            host.nuc-ubuntu	2019-11-04 05:44:23.023	error	Caught by controller[2]: at IncomingMessage.<anonymous> (/opt/iobroker/node_modules/request/request.js:1083:12)
            host.nuc-ubuntu	2019-11-04 05:44:23.023	error	Caught by controller[2]: at Request.emit (events.js:198:13)
            host.nuc-ubuntu	2019-11-04 05:44:23.023	error	Caught by controller[2]: at Request.<anonymous> (/opt/iobroker/node_modules/request/request.js:1161:10)
            host.nuc-ubuntu	2019-11-04 05:44:23.023	error	Caught by controller[2]: at Request.emit (events.js:198:13)
            host.nuc-ubuntu	2019-11-04 05:44:23.023	error	Caught by controller[2]: at Request.self.callback (/opt/iobroker/node_modules/request/request.js:185:22)
            host.nuc-ubuntu	2019-11-04 05:44:23.023	error	Caught by controller[2]: at Request.RP$callback [as _callback] (/opt/iobroker/node_modules/request-promise-core/lib/plumbing.js:46:31)
            host.nuc-ubuntu	2019-11-04 05:44:23.023	error	Caught by controller[2]: at Request.plumbing.callback (/opt/iobroker/node_modules/request-promise-core/lib/plumbing.js:104:33)
            host.nuc-ubuntu	2019-11-04 05:44:23.023	error	Caught by controller[2]: at new StatusCodeError (/opt/iobroker/node_modules/request-promise-core/lib/errors.js:32:15)
            host.nuc-ubuntu	2019-11-04 05:44:23.023	error	Caught by controller[2]: Unhandled rejection StatusCodeError: 401 - "{\"success\":false,\"data\":{\"name\":\"Expired token\",\"message\":\"Expired token\",\"url\":\"\\/zm\\/api\\/monitors.json?token=
            host.nuc-ubuntu	2019-11-04 05:44:23.023	error	Caught by controller[1]: at process._tickCallback (internal/process/next_tick.js:63:19)
            host.nuc-ubuntu	2019-11-04 05:44:23.023	error	Caught by controller[1]: at endReadableNT (_stream_readable.js:1145:12)
            host.nuc-ubuntu	2019-11-04 05:44:23.023	error	Caught by controller[1]: at IncomingMessage.emit (events.js:203:15)
            host.nuc-ubuntu	2019-11-04 05:44:23.023	error	Caught by controller[1]: at Object.onceWrapper (events.js:286:20)
            host.nuc-ubuntu	2019-11-04 05:44:23.023	error	Caught by controller[1]: at IncomingMessage.<anonymous> (/opt/iobroker/node_modules/request/request.js:1083:12)
            host.nuc-ubuntu	2019-11-04 05:44:23.023	error	Caught by controller[1]: at Request.emit (events.js:198:13)
            host.nuc-ubuntu	2019-11-04 05:44:23.023	error	Caught by controller[1]: at Request.<anonymous> (/opt/iobroker/node_modules/request/request.js:1161:10)
            host.nuc-ubuntu	2019-11-04 05:44:23.023	error	Caught by controller[1]: at Request.emit (events.js:198:13)
            host.nuc-ubuntu	2019-11-04 05:44:23.023	error	Caught by controller[1]: at Request.self.callback (/opt/iobroker/node_modules/request/request.js:185:22)
            host.nuc-ubuntu	2019-11-04 05:44:23.023	error	Caught by controller[1]: at Request.RP$callback [as _callback] (/opt/iobroker/node_modules/request-promise-core/lib/plumbing.js:46:31)
            host.nuc-ubuntu	2019-11-04 05:44:23.023	error	Caught by controller[1]: at Request.plumbing.callback (/opt/iobroker/node_modules/request-promise-core/lib/plumbing.js:104:33)
            host.nuc-ubuntu	2019-11-04 05:44:23.023	error	Caught by controller[1]: at new StatusCodeError (/opt/iobroker/node_modules/request-promise-core/lib/errors.js:32:15)
            host.nuc-ubuntu	2019-11-04 05:44:23.022	error	Caught by controller[1]: Unhandled rejection StatusCodeError: 401 - "{\"success\":false,\"data\":{\"name\":\"Expired token\",\"message\":\"Expired token\",\"url\":\"\\/zm\\/api\\/monitors.json?token=
            
            MeistertrM 1 Antwort Letzte Antwort
            0
            • M mikiline

              @Meistertr
              Vielen Dank funktioniert. Top!

              ZMEvent kommen leider auch keine Daten.
              zmevent.PNG
              Einzig, nach einer bestimmten Zeit verliert er die Verbindung und nach neustart des Adapters geht es wieder....

              host.nuc-ubuntu	2019-11-04 05:44:23.025	error	Caught by controller[6]: at process._tickCallback (internal/process/next_tick.js:63:19)
              host.nuc-ubuntu	2019-11-04 05:44:23.025	error	Caught by controller[6]: at endReadableNT (_stream_readable.js:1145:12)
              host.nuc-ubuntu	2019-11-04 05:44:23.025	error	Caught by controller[6]: at IncomingMessage.emit (events.js:203:15)
              host.nuc-ubuntu	2019-11-04 05:44:23.025	error	Caught by controller[6]: at Object.onceWrapper (events.js:286:20)
              host.nuc-ubuntu	2019-11-04 05:44:23.025	error	Caught by controller[6]: at IncomingMessage.<anonymous> (/opt/iobroker/node_modules/request/request.js:1083:12)
              host.nuc-ubuntu	2019-11-04 05:44:23.025	error	Caught by controller[6]: at Request.emit (events.js:198:13)
              host.nuc-ubuntu	2019-11-04 05:44:23.025	error	Caught by controller[6]: at Request.<anonymous> (/opt/iobroker/node_modules/request/request.js:1161:10)
              host.nuc-ubuntu	2019-11-04 05:44:23.025	error	Caught by controller[6]: at Request.emit (events.js:198:13)
              host.nuc-ubuntu	2019-11-04 05:44:23.025	error	Caught by controller[6]: at Request.self.callback (/opt/iobroker/node_modules/request/request.js:185:22)
              host.nuc-ubuntu	2019-11-04 05:44:23.025	error	Caught by controller[6]: at Request.RP$callback [as _callback] (/opt/iobroker/node_modules/request-promise-core/lib/plumbing.js:46:31)
              host.nuc-ubuntu	2019-11-04 05:44:23.025	error	Caught by controller[6]: at Request.plumbing.callback (/opt/iobroker/node_modules/request-promise-core/lib/plumbing.js:104:33)
              host.nuc-ubuntu	2019-11-04 05:44:23.025	error	Caught by controller[6]: at new StatusCodeError (/opt/iobroker/node_modules/request-promise-core/lib/errors.js:32:15)
              host.nuc-ubuntu	2019-11-04 05:44:23.025	error	Caught by controller[6]: Unhandled rejection StatusCodeError: 401 - "{\"success\":false,\"data\":{\"name\":\"Expired token\",\"message\":\"Expired token\",\"url\":\"\\/zm\\/api\\/monitors.json?token=
              host.nuc-ubuntu	2019-11-04 05:44:23.025	error	Caught by controller[5]: at process._tickCallback (internal/process/next_tick.js:63:19)
              host.nuc-ubuntu	2019-11-04 05:44:23.025	error	Caught by controller[5]: at endReadableNT (_stream_readable.js:1145:12)
              host.nuc-ubuntu	2019-11-04 05:44:23.025	error	Caught by controller[5]: at IncomingMessage.emit (events.js:203:15)
              host.nuc-ubuntu	2019-11-04 05:44:23.025	error	Caught by controller[5]: at Object.onceWrapper (events.js:286:20)
              host.nuc-ubuntu	2019-11-04 05:44:23.025	error	Caught by controller[5]: at IncomingMessage.<anonymous> (/opt/iobroker/node_modules/request/request.js:1083:12)
              host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[5]: at Request.emit (events.js:198:13)
              host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[5]: at Request.<anonymous> (/opt/iobroker/node_modules/request/request.js:1161:10)
              host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[5]: at Request.emit (events.js:198:13)
              host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[5]: at Request.self.callback (/opt/iobroker/node_modules/request/request.js:185:22)
              host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[5]: at Request.RP$callback [as _callback] (/opt/iobroker/node_modules/request-promise-core/lib/plumbing.js:46:31)
              host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[5]: at Request.plumbing.callback (/opt/iobroker/node_modules/request-promise-core/lib/plumbing.js:104:33)
              host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[5]: at new StatusCodeError (/opt/iobroker/node_modules/request-promise-core/lib/errors.js:32:15)
              host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[5]: Unhandled rejection StatusCodeError: 401 - "{\"success\":false,\"data\":{\"name\":\"Expired token\",\"message\":\"Expired token\",\"url\":\"\\/zm\\/api\\/monitors.json?token=
              host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[4]: at process._tickCallback (internal/process/next_tick.js:63:19)
              host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[4]: at endReadableNT (_stream_readable.js:1145:12)
              host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[4]: at IncomingMessage.emit (events.js:203:15)
              host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[4]: at Object.onceWrapper (events.js:286:20)
              host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[4]: at IncomingMessage.<anonymous> (/opt/iobroker/node_modules/request/request.js:1083:12)
              host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[4]: at Request.emit (events.js:198:13)
              host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[4]: at Request.<anonymous> (/opt/iobroker/node_modules/request/request.js:1161:10)
              host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[4]: at Request.emit (events.js:198:13)
              host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[4]: at Request.self.callback (/opt/iobroker/node_modules/request/request.js:185:22)
              host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[4]: at Request.RP$callback [as _callback] (/opt/iobroker/node_modules/request-promise-core/lib/plumbing.js:46:31)
              host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[4]: at Request.plumbing.callback (/opt/iobroker/node_modules/request-promise-core/lib/plumbing.js:104:33)
              host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[4]: at new StatusCodeError (/opt/iobroker/node_modules/request-promise-core/lib/errors.js:32:15)
              host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[4]: Unhandled rejection StatusCodeError: 401 - "{\"success\":false,\"data\":{\"name\":\"Expired token\",\"message\":\"Expired token\",\"url\":\"\\/zm\\/api\\/monitors.json?token=
              host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[3]: at process._tickCallback (internal/process/next_tick.js:63:19)
              host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[3]: at endReadableNT (_stream_readable.js:1145:12)
              host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[3]: at IncomingMessage.emit (events.js:203:15)
              host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[3]: at Object.onceWrapper (events.js:286:20)
              host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[3]: at IncomingMessage.<anonymous> (/opt/iobroker/node_modules/request/request.js:1083:12)
              host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[3]: at Request.emit (events.js:198:13)
              host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[3]: at Request.<anonymous> (/opt/iobroker/node_modules/request/request.js:1161:10)
              host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[3]: at Request.emit (events.js:198:13)
              host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[3]: at Request.self.callback (/opt/iobroker/node_modules/request/request.js:185:22)
              host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[3]: at Request.RP$callback [as _callback] (/opt/iobroker/node_modules/request-promise-core/lib/plumbing.js:46:31)
              host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[3]: at Request.plumbing.callback (/opt/iobroker/node_modules/request-promise-core/lib/plumbing.js:104:33)
              host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[3]: at new StatusCodeError (/opt/iobroker/node_modules/request-promise-core/lib/errors.js:32:15)
              host.nuc-ubuntu	2019-11-04 05:44:23.024	error	Caught by controller[3]: Unhandled rejection StatusCodeError: 401 - "{\"success\":false,\"data\":{\"name\":\"Expired token\",\"message\":\"Expired token\",\"url\":\"\\/zm\\/api\\/monitors.json?token=
              host.nuc-ubuntu	2019-11-04 05:44:23.023	error	Caught by controller[2]: at process._tickCallback (internal/process/next_tick.js:63:19)
              host.nuc-ubuntu	2019-11-04 05:44:23.023	error	Caught by controller[2]: at endReadableNT (_stream_readable.js:1145:12)
              host.nuc-ubuntu	2019-11-04 05:44:23.023	error	Caught by controller[2]: at IncomingMessage.emit (events.js:203:15)
              host.nuc-ubuntu	2019-11-04 05:44:23.023	error	Caught by controller[2]: at Object.onceWrapper (events.js:286:20)
              host.nuc-ubuntu	2019-11-04 05:44:23.023	error	Caught by controller[2]: at IncomingMessage.<anonymous> (/opt/iobroker/node_modules/request/request.js:1083:12)
              host.nuc-ubuntu	2019-11-04 05:44:23.023	error	Caught by controller[2]: at Request.emit (events.js:198:13)
              host.nuc-ubuntu	2019-11-04 05:44:23.023	error	Caught by controller[2]: at Request.<anonymous> (/opt/iobroker/node_modules/request/request.js:1161:10)
              host.nuc-ubuntu	2019-11-04 05:44:23.023	error	Caught by controller[2]: at Request.emit (events.js:198:13)
              host.nuc-ubuntu	2019-11-04 05:44:23.023	error	Caught by controller[2]: at Request.self.callback (/opt/iobroker/node_modules/request/request.js:185:22)
              host.nuc-ubuntu	2019-11-04 05:44:23.023	error	Caught by controller[2]: at Request.RP$callback [as _callback] (/opt/iobroker/node_modules/request-promise-core/lib/plumbing.js:46:31)
              host.nuc-ubuntu	2019-11-04 05:44:23.023	error	Caught by controller[2]: at Request.plumbing.callback (/opt/iobroker/node_modules/request-promise-core/lib/plumbing.js:104:33)
              host.nuc-ubuntu	2019-11-04 05:44:23.023	error	Caught by controller[2]: at new StatusCodeError (/opt/iobroker/node_modules/request-promise-core/lib/errors.js:32:15)
              host.nuc-ubuntu	2019-11-04 05:44:23.023	error	Caught by controller[2]: Unhandled rejection StatusCodeError: 401 - "{\"success\":false,\"data\":{\"name\":\"Expired token\",\"message\":\"Expired token\",\"url\":\"\\/zm\\/api\\/monitors.json?token=
              host.nuc-ubuntu	2019-11-04 05:44:23.023	error	Caught by controller[1]: at process._tickCallback (internal/process/next_tick.js:63:19)
              host.nuc-ubuntu	2019-11-04 05:44:23.023	error	Caught by controller[1]: at endReadableNT (_stream_readable.js:1145:12)
              host.nuc-ubuntu	2019-11-04 05:44:23.023	error	Caught by controller[1]: at IncomingMessage.emit (events.js:203:15)
              host.nuc-ubuntu	2019-11-04 05:44:23.023	error	Caught by controller[1]: at Object.onceWrapper (events.js:286:20)
              host.nuc-ubuntu	2019-11-04 05:44:23.023	error	Caught by controller[1]: at IncomingMessage.<anonymous> (/opt/iobroker/node_modules/request/request.js:1083:12)
              host.nuc-ubuntu	2019-11-04 05:44:23.023	error	Caught by controller[1]: at Request.emit (events.js:198:13)
              host.nuc-ubuntu	2019-11-04 05:44:23.023	error	Caught by controller[1]: at Request.<anonymous> (/opt/iobroker/node_modules/request/request.js:1161:10)
              host.nuc-ubuntu	2019-11-04 05:44:23.023	error	Caught by controller[1]: at Request.emit (events.js:198:13)
              host.nuc-ubuntu	2019-11-04 05:44:23.023	error	Caught by controller[1]: at Request.self.callback (/opt/iobroker/node_modules/request/request.js:185:22)
              host.nuc-ubuntu	2019-11-04 05:44:23.023	error	Caught by controller[1]: at Request.RP$callback [as _callback] (/opt/iobroker/node_modules/request-promise-core/lib/plumbing.js:46:31)
              host.nuc-ubuntu	2019-11-04 05:44:23.023	error	Caught by controller[1]: at Request.plumbing.callback (/opt/iobroker/node_modules/request-promise-core/lib/plumbing.js:104:33)
              host.nuc-ubuntu	2019-11-04 05:44:23.023	error	Caught by controller[1]: at new StatusCodeError (/opt/iobroker/node_modules/request-promise-core/lib/errors.js:32:15)
              host.nuc-ubuntu	2019-11-04 05:44:23.022	error	Caught by controller[1]: Unhandled rejection StatusCodeError: 401 - "{\"success\":false,\"data\":{\"name\":\"Expired token\",\"message\":\"Expired token\",\"url\":\"\\/zm\\/api\\/monitors.json?token=
              
              MeistertrM Offline
              MeistertrM Offline
              Meistertr
              Developer
              schrieb am zuletzt editiert von
              #133

              @mikilinefinde mal anhand des logs heraus, nach welcher zeit er die Verbindung verliert, sollze eigentlich nicht sein, da er alle 10 minuten den token wechseln sollte... und schau mal im debug log nach dem start ob dort messages mit WEBSOCKET sind.

              M 1 Antwort Letzte Antwort
              0
              • MeistertrM Meistertr

                @mikilinefinde mal anhand des logs heraus, nach welcher zeit er die Verbindung verliert, sollze eigentlich nicht sein, da er alle 10 minuten den token wechseln sollte... und schau mal im debug log nach dem start ob dort messages mit WEBSOCKET sind.

                M Offline
                M Offline
                mikiline
                schrieb am zuletzt editiert von
                #134

                @Meistertr
                Ja, es gibt auch Websocketmeldungen

                zoneminder.0	2019-11-04 14:36:43.793	error	(2506) WEBSOCKET: Error: Error: connect ETIMEDOUT
                

                Hier mal Start bis zum Ende

                2019-11-04 05:44:25.510 - info: host.nuc-ubuntu instance system.adapter.zoneminder.0 started with pid 2506
                
                2019-11-04 05:52:57.233 - error: zoneminder.0 (2506) WEBSOCKET: Error: Error: connect ETIMEDOUT
                
                2019-11-04 06:44:27.416 - warn: zoneminder.0 (2506) No monitors found, please configure monitors in your zoneminder!
                

                und zwischendurch sind noch paar Websocket Error Meldungen

                MeistertrM 1 Antwort Letzte Antwort
                0
                • M mikiline

                  @Meistertr
                  Ja, es gibt auch Websocketmeldungen

                  zoneminder.0	2019-11-04 14:36:43.793	error	(2506) WEBSOCKET: Error: Error: connect ETIMEDOUT
                  

                  Hier mal Start bis zum Ende

                  2019-11-04 05:44:25.510 - info: host.nuc-ubuntu instance system.adapter.zoneminder.0 started with pid 2506
                  
                  2019-11-04 05:52:57.233 - error: zoneminder.0 (2506) WEBSOCKET: Error: Error: connect ETIMEDOUT
                  
                  2019-11-04 06:44:27.416 - warn: zoneminder.0 (2506) No monitors found, please configure monitors in your zoneminder!
                  

                  und zwischendurch sind noch paar Websocket Error Meldungen

                  MeistertrM Offline
                  MeistertrM Offline
                  Meistertr
                  Developer
                  schrieb am zuletzt editiert von
                  #135

                  @mikiline hast du einen anderen Port als 9000?

                  M 1 Antwort Letzte Antwort
                  0
                  • MeistertrM Meistertr

                    @mikiline hast du einen anderen Port als 9000?

                    M Offline
                    M Offline
                    mikiline
                    schrieb am zuletzt editiert von
                    #136

                    @Meistertr
                    eigentlich nicht. Hab da alles beim Standard gelassen
                    zmeventnotification.ini hat 9000 drinnen

                    1 Antwort Letzte Antwort
                    0
                    • MeistertrM Offline
                      MeistertrM Offline
                      Meistertr
                      Developer
                      schrieb am zuletzt editiert von
                      #137

                      So habe den Login noch einmal komplett überarbeitet meine ersten tests liefen soweit gut mit der api 2 hatte ich den ganzen tag Verbindung. zum event Problem kann ich noch nichts sagen. Er meldet einen Timeout, das bedeutet er kann die Gegenseite nicht erreichen. Kannst du nochmal nach websocket suchen und schauen ob der Host richtig ist (im debug log)

                      M 1 Antwort Letzte Antwort
                      0
                      • MeistertrM Meistertr

                        So habe den Login noch einmal komplett überarbeitet meine ersten tests liefen soweit gut mit der api 2 hatte ich den ganzen tag Verbindung. zum event Problem kann ich noch nichts sagen. Er meldet einen Timeout, das bedeutet er kann die Gegenseite nicht erreichen. Kannst du nochmal nach websocket suchen und schauen ob der Host richtig ist (im debug log)

                        M Offline
                        M Offline
                        mikiline
                        schrieb am zuletzt editiert von
                        #138

                        @Meistertr
                        also login geht. aber nach einer bestimmten zeit kommt wieder der fehler. ich denke es liegt auch daran das der token automatisch erneuert wird.

                        die ws fehlermeldung habe ich auch noch

                        MeistertrM 1 Antwort Letzte Antwort
                        0
                        • E Offline
                          E Offline
                          ErazorVIP
                          schrieb am zuletzt editiert von ErazorVIP
                          #139

                          Hallo,

                          ich bekomme den Adapter leider nicht ans laufen.

                          Caught	2019-11-07 18:18:41.284	error	by controller[1]: at process._tickCallback (internal/process/next_tick.js:63:19)
                          Caught	2019-11-07 18:18:41.284	error	by controller[1]: at endReadableNT (_stream_readable.js:1145:12)
                          Caught	2019-11-07 18:18:41.284	error	by controller[1]: at IncomingMessage.emit (events.js:203:15)
                          Caught	2019-11-07 18:18:41.284	error	by controller[1]: at Object.onceWrapper (events.js:286:20)
                          Caught	2019-11-07 18:18:41.284	error	by controller[1]: at IncomingMessage.<anonymous> (/opt/iobroker/node_modules/iobroker.zoneminder/node_modules/request/request.js:1083:12)
                          Caught	2019-11-07 18:18:41.284	error	by controller[1]: at Request.emit (events.js:198:13)
                          Caught	2019-11-07 18:18:41.284	error	by controller[1]: at Request.<anonymous> (/opt/iobroker/node_modules/iobroker.zoneminder/node_modules/request/request.js:1161:10)
                          Caught	2019-11-07 18:18:41.284	error	by controller[1]: at Request.emit (events.js:198:13)
                          Caught	2019-11-07 18:18:41.284	error	by controller[1]: at Request.self.callback (/opt/iobroker/node_modules/iobroker.zoneminder/node_modules/request/request.js:185:22)
                          Caught	2019-11-07 18:18:41.284	error	by controller[1]: at Request.RP$callback [as _callback] (/opt/iobroker/node_modules/iobroker.zoneminder/node_modules/request-promise-core/lib/plumbing.js:46:31)
                          Caught	2019-11-07 18:18:41.283	error	by controller[1]: at Request.plumbing.callback (/opt/iobroker/node_modules/iobroker.zoneminder/node_modules/request-promise-core/lib/plumbing.js:104:33)
                          Caught	2019-11-07 18:18:41.283	error	by controller[1]: at new StatusCodeError (/opt/iobroker/node_modules/iobroker.zoneminder/node_modules/request-promise-core/lib/errors.js:32:15)
                          Caught	2019-11-07 18:18:41.283	error	by controller[1]: Unhandled rejection StatusCodeError: 401 - "\n{\"success\":false,\"data\":{\"name\":\"User not found\",\"message\":\"User not found\",\"url\":\"\\/zm\\/api\\/host\\/login.json\",\"e
                          Caught	2019-11-07 18:18:41.283	error	by controller[0]: at process._tickCallback (internal/process/next_tick.js:63:19)
                          Caught	2019-11-07 18:18:41.283	error	by controller[0]: at endReadableNT (_stream_readable.js:1145:12)
                          Caught	2019-11-07 18:18:41.283	error	by controller[0]: at IncomingMessage.emit (events.js:203:15)
                          Caught	2019-11-07 18:18:41.283	error	by controller[0]: at Object.onceWrapper (events.js:286:20)
                          Caught	2019-11-07 18:18:41.283	error	by controller[0]: at IncomingMessage.<anonymous> (/opt/iobroker/node_modules/iobroker.zoneminder/node_modules/request/request.js:1083:12)
                          Caught	2019-11-07 18:18:41.283	error	by controller[0]: at Request.emit (events.js:198:13)
                          Caught	2019-11-07 18:18:41.283	error	by controller[0]: at Request.<anonymous> (/opt/iobroker/node_modules/iobroker.zoneminder/node_modules/request/request.js:1161:10)
                          Caught	2019-11-07 18:18:41.283	error	by controller[0]: at Request.emit (events.js:198:13)
                          Caught	2019-11-07 18:18:41.283	error	by controller[0]: at Request.self.callback (/opt/iobroker/node_modules/iobroker.zoneminder/node_modules/request/request.js:185:22)
                          Caught	2019-11-07 18:18:41.283	error	by controller[0]: at Request.RP$callback [as _callback] (/opt/iobroker/node_modules/iobroker.zoneminder/node_modules/request-promise-core/lib/plumbing.js:46:31)
                          Caught	2019-11-07 18:18:41.282	error	by controller[0]: at Request.plumbing.callback (/opt/iobroker/node_modules/iobroker.zoneminder/node_modules/request-promise-core/lib/plumbing.js:104:33)
                          Caught	2019-11-07 18:18:41.282	error	by controller[0]: at new StatusCodeError (/opt/iobroker/node_modules/iobroker.zoneminder/node_modules/request-promise-core/lib/errors.js:32:15)
                          Caught	2019-11-07 18:18:41.282	error	by controller[0]: Unhandled rejection StatusCodeError: 401 - "\n{\"success\":false,\"data\":{\"name\":\"User not found\",\"message\":\"User not found\",\"url\":\"\\/zm\\/api\\/host\\/login.json\",\"e
                          zoneminder.0	2019-11-07 18:18:41.170	info	cleaned everything up...
                          
                          zoneminder.0	2019-11-07 18:19:40.810	error	Cant connect!!
                          

                          Benutername: admin
                          Passwort: admin

                          AUTH_HASH_IPS den Haken habe ich auch raus.

                          Leider bleibt der Adapter "gelb" und verbindet sich nicht.

                          Zoneminderversion : v1.30.4

                          Was kann ich noch probieren?

                          MeistertrM E 2 Antworten Letzte Antwort
                          0
                          • MeistertrM Meistertr

                            @Berchemer da hast du recht, das will ich auch noch einbauen , hier muss dann aber jede sekunde der wert aller monitore abgefragt werden. was etwas unwirtschaftlich ist. daher ist die lösung über zmevent besser.

                            B Offline
                            B Offline
                            Berchemer
                            schrieb am zuletzt editiert von
                            #140

                            @Meistertr
                            Alter...
                            Habe mir grade mal die Doku zur Installationsanweisung von Event Server angeschaut :face_with_rolling_eyes:
                            Gibt es da auch etwas in Deutsch??? :grinning:

                            MeistertrM 1 Antwort Letzte Antwort
                            0
                            • B Berchemer

                              @Meistertr
                              Alter...
                              Habe mir grade mal die Doku zur Installationsanweisung von Event Server angeschaut :face_with_rolling_eyes:
                              Gibt es da auch etwas in Deutsch??? :grinning:

                              MeistertrM Offline
                              MeistertrM Offline
                              Meistertr
                              Developer
                              schrieb am zuletzt editiert von
                              #141

                              @Berchemer es sieht schwerer aus als es ist, wenn ich das grobe fertig habe wollte ich es mal dokumentieren..

                              1 Antwort Letzte Antwort
                              0
                              • M mikiline

                                @Meistertr
                                also login geht. aber nach einer bestimmten zeit kommt wieder der fehler. ich denke es liegt auch daran das der token automatisch erneuert wird.

                                die ws fehlermeldung habe ich auch noch

                                MeistertrM Offline
                                MeistertrM Offline
                                Meistertr
                                Developer
                                schrieb am zuletzt editiert von
                                #142

                                @mikiline do von git sollte nun gehen, hatte noch einen Fehler drin.Bitte nochmal testen

                                M 2 Antworten Letzte Antwort
                                0
                                • E ErazorVIP

                                  Hallo,

                                  ich bekomme den Adapter leider nicht ans laufen.

                                  Caught	2019-11-07 18:18:41.284	error	by controller[1]: at process._tickCallback (internal/process/next_tick.js:63:19)
                                  Caught	2019-11-07 18:18:41.284	error	by controller[1]: at endReadableNT (_stream_readable.js:1145:12)
                                  Caught	2019-11-07 18:18:41.284	error	by controller[1]: at IncomingMessage.emit (events.js:203:15)
                                  Caught	2019-11-07 18:18:41.284	error	by controller[1]: at Object.onceWrapper (events.js:286:20)
                                  Caught	2019-11-07 18:18:41.284	error	by controller[1]: at IncomingMessage.<anonymous> (/opt/iobroker/node_modules/iobroker.zoneminder/node_modules/request/request.js:1083:12)
                                  Caught	2019-11-07 18:18:41.284	error	by controller[1]: at Request.emit (events.js:198:13)
                                  Caught	2019-11-07 18:18:41.284	error	by controller[1]: at Request.<anonymous> (/opt/iobroker/node_modules/iobroker.zoneminder/node_modules/request/request.js:1161:10)
                                  Caught	2019-11-07 18:18:41.284	error	by controller[1]: at Request.emit (events.js:198:13)
                                  Caught	2019-11-07 18:18:41.284	error	by controller[1]: at Request.self.callback (/opt/iobroker/node_modules/iobroker.zoneminder/node_modules/request/request.js:185:22)
                                  Caught	2019-11-07 18:18:41.284	error	by controller[1]: at Request.RP$callback [as _callback] (/opt/iobroker/node_modules/iobroker.zoneminder/node_modules/request-promise-core/lib/plumbing.js:46:31)
                                  Caught	2019-11-07 18:18:41.283	error	by controller[1]: at Request.plumbing.callback (/opt/iobroker/node_modules/iobroker.zoneminder/node_modules/request-promise-core/lib/plumbing.js:104:33)
                                  Caught	2019-11-07 18:18:41.283	error	by controller[1]: at new StatusCodeError (/opt/iobroker/node_modules/iobroker.zoneminder/node_modules/request-promise-core/lib/errors.js:32:15)
                                  Caught	2019-11-07 18:18:41.283	error	by controller[1]: Unhandled rejection StatusCodeError: 401 - "\n{\"success\":false,\"data\":{\"name\":\"User not found\",\"message\":\"User not found\",\"url\":\"\\/zm\\/api\\/host\\/login.json\",\"e
                                  Caught	2019-11-07 18:18:41.283	error	by controller[0]: at process._tickCallback (internal/process/next_tick.js:63:19)
                                  Caught	2019-11-07 18:18:41.283	error	by controller[0]: at endReadableNT (_stream_readable.js:1145:12)
                                  Caught	2019-11-07 18:18:41.283	error	by controller[0]: at IncomingMessage.emit (events.js:203:15)
                                  Caught	2019-11-07 18:18:41.283	error	by controller[0]: at Object.onceWrapper (events.js:286:20)
                                  Caught	2019-11-07 18:18:41.283	error	by controller[0]: at IncomingMessage.<anonymous> (/opt/iobroker/node_modules/iobroker.zoneminder/node_modules/request/request.js:1083:12)
                                  Caught	2019-11-07 18:18:41.283	error	by controller[0]: at Request.emit (events.js:198:13)
                                  Caught	2019-11-07 18:18:41.283	error	by controller[0]: at Request.<anonymous> (/opt/iobroker/node_modules/iobroker.zoneminder/node_modules/request/request.js:1161:10)
                                  Caught	2019-11-07 18:18:41.283	error	by controller[0]: at Request.emit (events.js:198:13)
                                  Caught	2019-11-07 18:18:41.283	error	by controller[0]: at Request.self.callback (/opt/iobroker/node_modules/iobroker.zoneminder/node_modules/request/request.js:185:22)
                                  Caught	2019-11-07 18:18:41.283	error	by controller[0]: at Request.RP$callback [as _callback] (/opt/iobroker/node_modules/iobroker.zoneminder/node_modules/request-promise-core/lib/plumbing.js:46:31)
                                  Caught	2019-11-07 18:18:41.282	error	by controller[0]: at Request.plumbing.callback (/opt/iobroker/node_modules/iobroker.zoneminder/node_modules/request-promise-core/lib/plumbing.js:104:33)
                                  Caught	2019-11-07 18:18:41.282	error	by controller[0]: at new StatusCodeError (/opt/iobroker/node_modules/iobroker.zoneminder/node_modules/request-promise-core/lib/errors.js:32:15)
                                  Caught	2019-11-07 18:18:41.282	error	by controller[0]: Unhandled rejection StatusCodeError: 401 - "\n{\"success\":false,\"data\":{\"name\":\"User not found\",\"message\":\"User not found\",\"url\":\"\\/zm\\/api\\/host\\/login.json\",\"e
                                  zoneminder.0	2019-11-07 18:18:41.170	info	cleaned everything up...
                                  
                                  zoneminder.0	2019-11-07 18:19:40.810	error	Cant connect!!
                                  

                                  Benutername: admin
                                  Passwort: admin

                                  AUTH_HASH_IPS den Haken habe ich auch raus.

                                  Leider bleibt der Adapter "gelb" und verbindet sich nicht.

                                  Zoneminderversion : v1.30.4

                                  Was kann ich noch probieren?

                                  MeistertrM Offline
                                  MeistertrM Offline
                                  Meistertr
                                  Developer
                                  schrieb am zuletzt editiert von
                                  #143

                                  @ErazorVIP ich bräuchte einen etwas längeren Logauszug. (debug)

                                  E 1 Antwort Letzte Antwort
                                  0
                                  • MeistertrM Meistertr

                                    @mikiline do von git sollte nun gehen, hatte noch einen Fehler drin.Bitte nochmal testen

                                    M Offline
                                    M Offline
                                    mikiline
                                    schrieb am zuletzt editiert von
                                    #144

                                    @Meistertr
                                    Läuft :-) Danke

                                    1 Antwort Letzte Antwort
                                    0
                                    • XsevX Offline
                                      XsevX Offline
                                      Xsev
                                      schrieb am zuletzt editiert von
                                      #145

                                      Wie ist das eigenltich mit dem Zertifikat bei dem Event Server, soweit ich das verstanden habe wohl Pflicht, dieses zu installieren?
                                      Das immo der Grund, der mich davon abhält, weiter zu machen. Ich hab derzeit alles ohne irgendwelcher Zertifikate (die dann wieder irgendwann ablaufen und wieder erneuert werden wollen) und möchte das auch so belassen. Ich route nichts ins Inet und mein Zeug ist alles nur lokal erreichbar.

                                      Ist der Eventserver auch ohne Zertifiakt nutzbar?

                                      XsevX 1 Antwort Letzte Antwort
                                      0
                                      • MeistertrM Meistertr

                                        @mikiline do von git sollte nun gehen, hatte noch einen Fehler drin.Bitte nochmal testen

                                        M Offline
                                        M Offline
                                        mikiline
                                        schrieb am zuletzt editiert von mikiline
                                        #146

                                        @Meistertr
                                        eine frage noch.

                                        die video url mit dem token, da läuft es nicht flüssig in vis. immer wieder unterbrüche bis hin zu keinem bild.
                                        verwende ich die normale url zum mit username und passwort dann läuft es stabil und flüssig

                                        weisst du evtl woran das liegen könnte?

                                        edit:
                                        wenn man das objekt "zoneminder.1.cam_5.monitor.camUrl" als url verwendet unterbricht das video jedesmal bei aktualisierung des datenpunktes. wenn ich den geräreintervall in der adapterkonfig höher setze, wird auch das video länger flüssig angezeigt
                                        kann man da evtl. die aktualisierung des datenpunktes nur durchführen wenn sich der token ändert?

                                        oder einfach den geräteintervall hochsetzen (was ich nun gemacht habe).....geht auch.

                                        1 Antwort Letzte Antwort
                                        0
                                        • M Offline
                                          M Offline
                                          mikiline
                                          schrieb am zuletzt editiert von
                                          #147

                                          wie bindest du eigentlich das Video ein das du im datenpunkt zoneminder.0.cam_1.zmEvent.VideoUrl hast ?

                                          MeistertrM 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

                                          689

                                          Online

                                          32.5k

                                          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