Skip to content
  • Recent
  • Tags
  • 0 Unread 0
  • Categories
  • Unreplied
  • Popular
  • 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
  • Default (No Skin)
  • No Skin
Collapse
Logo
  1. ioBroker Community Home
  2. Deutsch
  3. ioBroker Allgemein
  4. js-controller 3.0/3.1 jetzt im Latest!

NEWS

  • Wartung am 15.11. – Forum ab 22:00 Uhr nicht erreichbar
    BluefoxB
    Bluefox
    11
    2
    207
  • UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?
    apollon77A
    apollon77
    48
    3
    7.9k
  • Monatsrückblick – September 2025
    BluefoxB
    Bluefox
    13
    1
    1.7k

js-controller 3.0/3.1 jetzt im Latest!

js-controller 3.0/3.1 jetzt im Latest!

Scheduled Pinned Locked Moved ioBroker Allgemein
js-controller
1.3k Posts 127 Posters 493.9k Views 89 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • apollon77A apollon77

    Hey All,

    nachdem die 3.0.20 nun ein paar Tage bereits im Einsatz ist und über 3000 Installationen aufweist sind wir fast soweit das es ins Stable gehen kann. Wir haben noch ein paar Fixes gesammelt und vor allem die Aktivierung des Sentry Fehler-Reportings noch etwas deutlicher bei der Erstinstallation eines 3.xer js-controllers hervorgehoben.

    Es kam noch ein kleineres Feature dazu und daher haben wir (auch weil wir schon bei 3.0.20 waren) für als Vorbereitung für den Stable Release das ganze zur 3.1 gemacht 🙂

    Changelog:

    3.1.2 (2020-05-09) Release Francesca

    • (foxriver76) catch error on alias ids with empty objects
    • (Apollon77) make sure promise rejections without error are not crashing the controller
    • (bluefox) Add Controller messages to allow read and write controller base settings (iobroker.json); introduce adapter feature flag CONTROLLER_READWRITE_BASE_SETTINGS
    • (Apollon77) handle edge case where hostName is not a string when sending messages (Sentry IOBROKER-ADMIN-B)
    • (Apollon77) handle case where letsencrypt directory can not be created (Sentry IOBROKER-ADMIN-C/IOBROKER-WEB-B)
    • (bluefox) add IDs to some log messages
    • (foxriver76) fix some logging in objects lib
    • (Apollon77) make sure to catch error when reading log directory (Sentry IOBROKER-JS-CONTROLLER-1F)
    • (foxriver76) Make decrypt and encrypt methods available in adapter object for developers. System secret is read automatically soonly the value is passed to the function
    • (AlCalzone) Add adapter exit code 13 (ADAPTER_REQUESTED_REBUILD) to also allow to tell js-controller to rebuild this adapter.
    • (Apollon77) change logging for invalid readFile actions to debug because ca be triggered also by other cases then planned ones. Update objects lib
    • (Apollon77) make sure command on cmdExec is a string (Sentry IOBROKER-JS-CONTROLLER-1H)
    • (Apollon77) Check more cases for existence of variables before accessing them (Sentry IOBROKER-JS-CONTROLLER-E)
    • (Apollon77) Add a node.js version check and output special error message if node.js version is not satisfied
    • (AlCalzone) Add missing parameter digest to crypto calls
    • (AlCalzone) further code optimizatons
    • (AlCalzone) Allow reverse lookup of exit codes (exit code -> error name)
    • (Apollon77) make sure Objects/States backup files are deleted correctly according to backup settings
    • (foxriver76) Make sure default state value is only set if state is not existing also in setObject
    • (foxriver76) check that alias is of type state when adding subscribing pattern
    • (Apollon77) Make sure error are checked correctly (Sentry IOBROKER-JS-CONTROLLER-1N)
    • (Apollon77) Inform about sentry activation if not configured on "iobroker setup first"
    • (bluefox) implement maintenance mode for adapter methods
    • (bluefox) store for binary states the binary flag in objects
    • (Apollon77) update Plugin system
    • (Apollon77) update Sentry plugin to respect all options to disable reporting including new disableDataReporting flag ( will be integrated into Admin later)
    • (AlCalzone) Add Plugin CLI commands to enable/disable plugins

    Die Version sollte in de nächsten Stunden im Latest Repository auftauchen. Wenn alles klappt werden wir ab morgen über den Info Adapter eine Info Meldung für alle Latest Nutzer einblenden die auf die neue Version hinweist und im Laufe der nächsten Woche geht der Controller 3.1 ins Stable.

    Viel Spass damit.

    Ingo

    sigi234S Online
    sigi234S Online
    sigi234
    Forum Testing Most Active
    wrote on last edited by
    #865

    @apollon77

    Läuft, alle Adapter Grün, vorläufig keine Meldungen im Log.

    Screenshot (2433).png

    Bitte benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
    Immer Daten sichern!

    1 Reply Last reply
    1
    • Holger76H Offline
      Holger76H Offline
      Holger76
      wrote on last edited by Holger76
      #866

      bei mir leider nicht. Es streikt der Unifi - Adapter, bleibt gelb (0.5, aber auch ein downgrade auf den vorigen läuft nicht) Meldung im LOG :

      (3030) Error: api.err.Invalid

      Ansonsten streikt auch der Discovergy Adapter, bleibt rot. (Login-Daten stimmen, nochmal kontrolliert, ging ja vorher auch)

      LOG:

      2020-05-10 00:02:01.030 - info: discovergy.0 (3267) starting. Version 0.5.4 in /opt/iobroker/node_modules/iobroker.discovergy, node: v12.16.3, js-controller: 3.1.2
2020-05-10 00:02:01.044 - info: discovergy.0 (3267) Discovergy Adapter startet, trying to discover meters associated with your account
2020-05-10 00:02:01.209 - error: discovergy.0 (3267) Connection_Failed at meter indication run, check your credentials !
2020-05-10 00:02:01.211 - 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().
2020-05-10 00:02:01.211 - error: discovergy.0 (3267) unhandled promise rejection: 401 - "401 Unauthorized: Invalid email or password supplied in the HTTP Authorization header"
2020-05-10 00:02:01.214 - error: discovergy.0 (3267) StatusCodeError: 401 - "401 Unauthorized: Invalid email or password supplied in the HTTP Authorization header"
at new StatusCodeError (/opt/iobroker/node_modules/request-promise-core/lib/errors.js:32:15)
at Request.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 Request.self.callback (/opt/iobroker/node_modules/request/request.js:185:22)
at Request.emit (events.js:310:20)
at Request.EventEmitter.emit (domain.js:482:12)
at Request. (/opt/iobroker/node_modules/request/request.js:1154:10)
at Request.emit (events.js:310:20)
at Request.EventEmitter.emit (domain.js:482:12)
at IncomingMessage. (/opt/iobroker/node_modules/request/request.js:1076:12)
2020-05-10 00:02:01.214 - info: discovergy.0 (3267) cleaned everything up...
2020-05-10 00:02:01.266 - info: discovergy.0 (3267) terminating
2020-05-10 00:02:01.267 - info: discovergy.0 (3267) Terminated (NO_ERROR): Without reason
2020-05-10 00:02:01.789 - error: host.ioBroker Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
2020-05-10 00:02:01.790 - error: host.ioBroker Caught by controller[1]: StatusCodeError: 401 - "401 Unauthorized: Invalid email or password supplied in the HTTP Authorization header"
2020-05-10 00:02:01.790 - error: host.ioBroker Caught by controller[1]: at new StatusCodeError (/opt/iobroker/node_modules/request-promise-core/lib/errors.js:32:15)
2020-05-10 00:02:01.790 - error: host.ioBroker Caught by controller[1]: at Request.plumbing.callback (/opt/iobroker/node_modules/request-promise-core/lib/plumbing.js:104:33)
2020-05-10 00:02:01.790 - error: host.ioBroker Caught by controller[1]: at Request.RP$callback [as _callback] (/opt/iobroker/node_modules/request-promise-core/lib/plumbing.js:46:31)
2020-05-10 00:02:01.791 - error: host.ioBroker Caught by controller[1]: at Request.self.callback (/opt/iobroker/node_modules/request/request.js:185:22)
2020-05-10 00:02:01.791 - error: host.ioBroker Caught by controller[1]: at Request.emit (events.js:310:20)
2020-05-10 00:02:01.791 - error: host.ioBroker Caught by controller[1]: at Request.EventEmitter.emit (domain.js:482:12)
2020-05-10 00:02:01.791 - error: host.ioBroker Caught by controller[1]: at Request. (/opt/iobroker/node_modules/request/request.js:1154:10)
2020-05-10 00:02:01.791 - error: host.ioBroker Caught by controller[1]: at Request.emit (events.js:310:20)
2020-05-10 00:02:01.791 - error: host.ioBroker Caught by controller[1]: at Request.EventEmitter.emit (domain.js:482:12)
2020-05-10 00:02:01.792 - error: host.ioBroker Caught by controller[1]: at IncomingMessage. (/opt/iobroker/node_modules/request/request.js:1076:12)
2020-05-10 00:02:01.792 - info: host.ioBroker instance system.adapter.discovergy.0 terminated with code 0 (NO_ERROR)
2020-05-10 00:02:01.792 - info: host.ioBroker Restart adapter system.adapter.discovergy.0 because enabled

      Alle Adapter sind latest.
      Debian 10, NodeJS12

      NUC8I5BEH (32GB,1TB-SSD) -> Proxmox VM [ioBroker.Pro auf Debian]+[InfluxDB/Grafana]+[AdGuard]+[ Rasp.matic] + [Conbee3] +[Graylog]+[Octopi]
      NUC6CAYH (16GB) [Proxmox Backup Server]+[OMV]

      apollon77A 2 Replies Last reply
      0
      • Holger76H Holger76

        bei mir leider nicht. Es streikt der Unifi - Adapter, bleibt gelb (0.5, aber auch ein downgrade auf den vorigen läuft nicht) Meldung im LOG :

        (3030) Error: api.err.Invalid

        Ansonsten streikt auch der Discovergy Adapter, bleibt rot. (Login-Daten stimmen, nochmal kontrolliert, ging ja vorher auch)

        LOG:

        2020-05-10 00:02:01.030 - info: discovergy.0 (3267) starting. Version 0.5.4 in /opt/iobroker/node_modules/iobroker.discovergy, node: v12.16.3, js-controller: 3.1.2
2020-05-10 00:02:01.044 - info: discovergy.0 (3267) Discovergy Adapter startet, trying to discover meters associated with your account
2020-05-10 00:02:01.209 - error: discovergy.0 (3267) Connection_Failed at meter indication run, check your credentials !
2020-05-10 00:02:01.211 - 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().
2020-05-10 00:02:01.211 - error: discovergy.0 (3267) unhandled promise rejection: 401 - "401 Unauthorized: Invalid email or password supplied in the HTTP Authorization header"
2020-05-10 00:02:01.214 - error: discovergy.0 (3267) StatusCodeError: 401 - "401 Unauthorized: Invalid email or password supplied in the HTTP Authorization header"
at new StatusCodeError (/opt/iobroker/node_modules/request-promise-core/lib/errors.js:32:15)
at Request.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 Request.self.callback (/opt/iobroker/node_modules/request/request.js:185:22)
at Request.emit (events.js:310:20)
at Request.EventEmitter.emit (domain.js:482:12)
at Request. (/opt/iobroker/node_modules/request/request.js:1154:10)
at Request.emit (events.js:310:20)
at Request.EventEmitter.emit (domain.js:482:12)
at IncomingMessage. (/opt/iobroker/node_modules/request/request.js:1076:12)
2020-05-10 00:02:01.214 - info: discovergy.0 (3267) cleaned everything up...
2020-05-10 00:02:01.266 - info: discovergy.0 (3267) terminating
2020-05-10 00:02:01.267 - info: discovergy.0 (3267) Terminated (NO_ERROR): Without reason
2020-05-10 00:02:01.789 - error: host.ioBroker Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
2020-05-10 00:02:01.790 - error: host.ioBroker Caught by controller[1]: StatusCodeError: 401 - "401 Unauthorized: Invalid email or password supplied in the HTTP Authorization header"
2020-05-10 00:02:01.790 - error: host.ioBroker Caught by controller[1]: at new StatusCodeError (/opt/iobroker/node_modules/request-promise-core/lib/errors.js:32:15)
2020-05-10 00:02:01.790 - error: host.ioBroker Caught by controller[1]: at Request.plumbing.callback (/opt/iobroker/node_modules/request-promise-core/lib/plumbing.js:104:33)
2020-05-10 00:02:01.790 - error: host.ioBroker Caught by controller[1]: at Request.RP$callback [as _callback] (/opt/iobroker/node_modules/request-promise-core/lib/plumbing.js:46:31)
2020-05-10 00:02:01.791 - error: host.ioBroker Caught by controller[1]: at Request.self.callback (/opt/iobroker/node_modules/request/request.js:185:22)
2020-05-10 00:02:01.791 - error: host.ioBroker Caught by controller[1]: at Request.emit (events.js:310:20)
2020-05-10 00:02:01.791 - error: host.ioBroker Caught by controller[1]: at Request.EventEmitter.emit (domain.js:482:12)
2020-05-10 00:02:01.791 - error: host.ioBroker Caught by controller[1]: at Request. (/opt/iobroker/node_modules/request/request.js:1154:10)
2020-05-10 00:02:01.791 - error: host.ioBroker Caught by controller[1]: at Request.emit (events.js:310:20)
2020-05-10 00:02:01.791 - error: host.ioBroker Caught by controller[1]: at Request.EventEmitter.emit (domain.js:482:12)
2020-05-10 00:02:01.792 - error: host.ioBroker Caught by controller[1]: at IncomingMessage. (/opt/iobroker/node_modules/request/request.js:1076:12)
2020-05-10 00:02:01.792 - info: host.ioBroker instance system.adapter.discovergy.0 terminated with code 0 (NO_ERROR)
2020-05-10 00:02:01.792 - info: host.ioBroker Restart adapter system.adapter.discovergy.0 because enabled

        Alle Adapter sind latest.
        Debian 10, NodeJS12

        apollon77A Offline
        apollon77A Offline
        apollon77
        wrote on last edited by
        #867

        @Holger76 dann bitte die Fehler bei beiden Adaptern melden, haben beide nichts direkt mit dem Controller zu tun. Am besten in den einschlägigen Forum Threads bzw als GitHub-Issue

        Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

        • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
        • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
        1 Reply Last reply
        0
        • Holger76H Holger76

          bei mir leider nicht. Es streikt der Unifi - Adapter, bleibt gelb (0.5, aber auch ein downgrade auf den vorigen läuft nicht) Meldung im LOG :

          (3030) Error: api.err.Invalid

          Ansonsten streikt auch der Discovergy Adapter, bleibt rot. (Login-Daten stimmen, nochmal kontrolliert, ging ja vorher auch)

          LOG:

          2020-05-10 00:02:01.030 - info: discovergy.0 (3267) starting. Version 0.5.4 in /opt/iobroker/node_modules/iobroker.discovergy, node: v12.16.3, js-controller: 3.1.2
2020-05-10 00:02:01.044 - info: discovergy.0 (3267) Discovergy Adapter startet, trying to discover meters associated with your account
2020-05-10 00:02:01.209 - error: discovergy.0 (3267) Connection_Failed at meter indication run, check your credentials !
2020-05-10 00:02:01.211 - 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().
2020-05-10 00:02:01.211 - error: discovergy.0 (3267) unhandled promise rejection: 401 - "401 Unauthorized: Invalid email or password supplied in the HTTP Authorization header"
2020-05-10 00:02:01.214 - error: discovergy.0 (3267) StatusCodeError: 401 - "401 Unauthorized: Invalid email or password supplied in the HTTP Authorization header"
at new StatusCodeError (/opt/iobroker/node_modules/request-promise-core/lib/errors.js:32:15)
at Request.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 Request.self.callback (/opt/iobroker/node_modules/request/request.js:185:22)
at Request.emit (events.js:310:20)
at Request.EventEmitter.emit (domain.js:482:12)
at Request. (/opt/iobroker/node_modules/request/request.js:1154:10)
at Request.emit (events.js:310:20)
at Request.EventEmitter.emit (domain.js:482:12)
at IncomingMessage. (/opt/iobroker/node_modules/request/request.js:1076:12)
2020-05-10 00:02:01.214 - info: discovergy.0 (3267) cleaned everything up...
2020-05-10 00:02:01.266 - info: discovergy.0 (3267) terminating
2020-05-10 00:02:01.267 - info: discovergy.0 (3267) Terminated (NO_ERROR): Without reason
2020-05-10 00:02:01.789 - error: host.ioBroker Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
2020-05-10 00:02:01.790 - error: host.ioBroker Caught by controller[1]: StatusCodeError: 401 - "401 Unauthorized: Invalid email or password supplied in the HTTP Authorization header"
2020-05-10 00:02:01.790 - error: host.ioBroker Caught by controller[1]: at new StatusCodeError (/opt/iobroker/node_modules/request-promise-core/lib/errors.js:32:15)
2020-05-10 00:02:01.790 - error: host.ioBroker Caught by controller[1]: at Request.plumbing.callback (/opt/iobroker/node_modules/request-promise-core/lib/plumbing.js:104:33)
2020-05-10 00:02:01.790 - error: host.ioBroker Caught by controller[1]: at Request.RP$callback [as _callback] (/opt/iobroker/node_modules/request-promise-core/lib/plumbing.js:46:31)
2020-05-10 00:02:01.791 - error: host.ioBroker Caught by controller[1]: at Request.self.callback (/opt/iobroker/node_modules/request/request.js:185:22)
2020-05-10 00:02:01.791 - error: host.ioBroker Caught by controller[1]: at Request.emit (events.js:310:20)
2020-05-10 00:02:01.791 - error: host.ioBroker Caught by controller[1]: at Request.EventEmitter.emit (domain.js:482:12)
2020-05-10 00:02:01.791 - error: host.ioBroker Caught by controller[1]: at Request. (/opt/iobroker/node_modules/request/request.js:1154:10)
2020-05-10 00:02:01.791 - error: host.ioBroker Caught by controller[1]: at Request.emit (events.js:310:20)
2020-05-10 00:02:01.791 - error: host.ioBroker Caught by controller[1]: at Request.EventEmitter.emit (domain.js:482:12)
2020-05-10 00:02:01.792 - error: host.ioBroker Caught by controller[1]: at IncomingMessage. (/opt/iobroker/node_modules/request/request.js:1076:12)
2020-05-10 00:02:01.792 - info: host.ioBroker instance system.adapter.discovergy.0 terminated with code 0 (NO_ERROR)
2020-05-10 00:02:01.792 - info: host.ioBroker Restart adapter system.adapter.discovergy.0 because enabled

          Alle Adapter sind latest.
          Debian 10, NodeJS12

          apollon77A Offline
          apollon77A Offline
          apollon77
          wrote on last edited by
          #868

          @Holger76 Versuch mal im Admin die Passwörter neu zu einzugeben bei den beiden Adaptern.

          Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

          • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
          • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
          Holger76H 1 Reply Last reply
          0
          • apollon77A apollon77

            @Holger76 Versuch mal im Admin die Passwörter neu zu einzugeben bei den beiden Adaptern.

            Holger76H Offline
            Holger76H Offline
            Holger76
            wrote on last edited by
            #869

            @apollon77 hatte ich natürlich schon getestet, bevor ich sowas hier melde 😉

            ok ich meld mich bei den Adaptern direkt...

            NUC8I5BEH (32GB,1TB-SSD) -> Proxmox VM [ioBroker.Pro auf Debian]+[InfluxDB/Grafana]+[AdGuard]+[ Rasp.matic] + [Conbee3] +[Graylog]+[Octopi]
            NUC6CAYH (16GB) [Proxmox Backup Server]+[OMV]

            apollon77A 1 Reply Last reply
            0
            • Holger76H Holger76

              @apollon77 hatte ich natürlich schon getestet, bevor ich sowas hier melde 😉

              ok ich meld mich bei den Adaptern direkt...

              apollon77A Offline
              apollon77A Offline
              apollon77
              wrote on last edited by
              #870

              @Holger76 Ich habe gerade die 3.1.3 released die deine Probleme beheben sollte. Habe mich entschieden nach Check das ganze im js-controller zu fixen. Es lag daran das die Passwörter falsch entschlüsselt wurden. Bitte checke mal die 3.1.3 sobald Sie für dich da ist

              Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

              • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
              • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
              S Holger76H 2 Replies Last reply
              0
              • M Offline
                M Offline
                Marty56
                wrote on last edited by
                #871

                Version 3.1.3. zeigt bei mir keine Fehler. Super Arbeit!

                HW:NUC (16 GB Ram)
                OS: Debian Bullseye, Promox V7, node v16.x npm 8.19.3

                1 Reply Last reply
                0
                • apollon77A apollon77

                  @Holger76 Ich habe gerade die 3.1.3 released die deine Probleme beheben sollte. Habe mich entschieden nach Check das ganze im js-controller zu fixen. Es lag daran das die Passwörter falsch entschlüsselt wurden. Bitte checke mal die 3.1.3 sobald Sie für dich da ist

                  S Offline
                  S Offline
                  skokarl
                  wrote on last edited by skokarl
                  #872

                  @apollon77
                  Moin,
                  ich habe jetzt gerade das Gefühl, dass der Sonos Adapter das JS-Controller Update nicht vertragen hat.
                  Fehler im Log kamen direkt nach dem Update auf 3.13

                  Ist aber für mich kein Problem, entsorge den jetzt sowieso, sollte nur als Info für Dich sein.

                  sonos.0	2020-05-10 06:20:01.791	error	at processTicksAndRejections (internal/process/task_queues.js:97:5)
sonos.0	2020-05-10 06:20:01.791	error	at /opt/iobroker/node_modules/standard-as-callback/built/index.js:19:49
sonos.0	2020-05-10 06:20:01.791	error	at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:11:23)
sonos.0	2020-05-10 06:20:01.791	error	at /opt/iobroker/node_modules/iobroker.objects-redis/index.js:1:93234
sonos.0	2020-05-10 06:20:01.791	error	at /opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:5012:26
sonos.0	2020-05-10 06:20:01.791	error	at checkState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4904:68)
sonos.0	2020-05-10 06:20:01.791	error	(30381) TypeError: Cannot read property 'state' of undefined
sonos.0	2020-05-10 06:20:01.790	error	(30381) uncaught exception: Cannot read property 'state' of undefined
sonos.0	2020-05-10 06:20:01.771	error	(30381) unknown user "undefined"

                  IOBroker mit Proxmox auf Celeron Nuc mit 16 GB und Debian11, Sonos API, Echo Show 15 als Wandtablet, Homematic IP, HUE, Sonos, Echos, DS718+ als Backup

                  MichMeinM apollon77A 3 Replies Last reply
                  0
                  • S skokarl

                    @apollon77
                    Moin,
                    ich habe jetzt gerade das Gefühl, dass der Sonos Adapter das JS-Controller Update nicht vertragen hat.
                    Fehler im Log kamen direkt nach dem Update auf 3.13

                    Ist aber für mich kein Problem, entsorge den jetzt sowieso, sollte nur als Info für Dich sein.

                    sonos.0	2020-05-10 06:20:01.791	error	at processTicksAndRejections (internal/process/task_queues.js:97:5)
sonos.0	2020-05-10 06:20:01.791	error	at /opt/iobroker/node_modules/standard-as-callback/built/index.js:19:49
sonos.0	2020-05-10 06:20:01.791	error	at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:11:23)
sonos.0	2020-05-10 06:20:01.791	error	at /opt/iobroker/node_modules/iobroker.objects-redis/index.js:1:93234
sonos.0	2020-05-10 06:20:01.791	error	at /opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:5012:26
sonos.0	2020-05-10 06:20:01.791	error	at checkState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4904:68)
sonos.0	2020-05-10 06:20:01.791	error	(30381) TypeError: Cannot read property 'state' of undefined
sonos.0	2020-05-10 06:20:01.790	error	(30381) uncaught exception: Cannot read property 'state' of undefined
sonos.0	2020-05-10 06:20:01.771	error	(30381) unknown user "undefined"
                    MichMeinM Online
                    MichMeinM Online
                    MichMein
                    wrote on last edited by MichMein
                    #873

                    Hi,

                    Ich habe anscheinend das gleiche Problem wie @skokarl mit dem Sonos Adapter 😞 nach Update auf 3.1.3

                    
host.raspberrypi	2020-05-10 06:50:57.059	info	Restart adapter system.adapter.sonos.0 because enabled
host.raspberrypi	2020-05-10 06:50:57.058	info	instance system.adapter.sonos.0 terminated with code 0 (NO_ERROR)
sonos.0	2020-05-10 06:50:56.855	error	(16270) TypeError: Cannot read property 'state' of undefined at checkState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4904:68) at /opt/iobroker/node_modules/iobroker.js-
sonos.0	2020-05-10 06:50:56.854	error	(16270) uncaught exception: Cannot read property 'state' of undefined
sonos.0	2020-05-10 06:50:56.831	error	(16270) unknown user "undefined"
sonos.0	2020-05-10 06:50:56.401	error	(16270) TypeError: Cannot read property 'state' of undefined at checkState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4904:68) at /opt/iobroker/node_modules/iobroker.js-
sonos.0	2020-05-10 06:50:56.400	error	(16270) uncaught exception: Cannot read property 'state' of undefined
sonos.0	2020-05-10 06:50:56.357	info	(16270) Terminated (NO_ERROR): Without reason
sonos.0	2020-05-10 06:50:56.356	info	(16270) terminating
sonos.0	2020-05-10 06:50:56.350	error	(16270) unknown user "undefined"
sonos.0	2020-05-10 06:50:56.275	info	(16270) terminating
sonos.0	2020-05-10 06:50:56.272	error	(16270) TypeError: Cannot read property 'state' of undefined at checkState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4904:68) at /opt/iobroker/node_modules/iobroker.js-
sonos.0	2020-05-10 06:50:56.269	error	(16270) uncaught exception: Cannot read property 'state' of undefined
sonos.0	2020-05-10 06:50:56.256	error	(16270) unknown user "undefined"
sonos.0	2020-05-10 06:50:55.620	info	(16270) starting. Version 2.0.1 in /opt/iobroker/node_modules/iobroker.sonos, node: v12.16.3, js-controller: 3.1.3
host.raspberrypi	2020-05-10 06:50:54.368	info	instance system.adapter.sonos.0 started with pid 16270
host.raspberrypi	2020-05-10 06:50:24.346	info	Restart adapter system.adapter.sonos.0 because enabled
host.raspberrypi	2020-05-10 06:50:24.345	info	instance system.adapter.sonos.0 terminated with code 0 (NO_ERROR)
sonos.0	2020-05-10 06:50:23.819	info	(15535) Terminated (NO_ERROR): Without reason
sonos.0	2020-05-10 06:50:23.817	info	(15535) terminating
sonos.0	2020-05-10 06:50:23.777	error	(15535) TypeError: Cannot read property 'state' of undefined at checkState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4904:68) at /opt/iobroker/node_modules/iobroker.js-
sonos.0	2020-05-10 06:50:23.776	error	(15535) uncaught exception: Cannot read property 'state' of undefined
sonos.0	2020-05-10 06:50:23.775	error	(15535) TypeError: Cannot read property 'state' of undefined at checkState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4904:68) at /opt/iobroker/node_modules/iobroker.js-
sonos.0	2020-05-10 06:50:23.775	error	(15535) uncaught exception: Cannot read property 'state' of undefined
sonos.0	2020-05-10 06:50:23.744	error	(15535) unknown user "undefined"
sonos.0	2020-05-10 06:50:23.726	info	(15535) terminating
sonos.0	2020-05-10 06:50:23.723	error	(15535) TypeError: Cannot read property 'state' of undefined at checkState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4904:68) at /opt/iobroker/node_modules/iobroker.js-
sonos.0	2020-05-10 06:50:23.720	error	(15535) uncaught exception: Cannot read property 'state' of undefined
sonos.0	2020-05-10 06:50:23.717	error	(15535) unknown user "undefined"
sonos.0	2020-05-10 06:50:23.683	error	(15535) unknown user "undefined"
sonos.0	2020-05-10 06:50:22.987	info	(15535) starting. Version 2.0.1 in /opt/iobroker/node_modules/iobroker.sonos, node: v12.16.3, js-controller: 3.1.3
host.raspberrypi	2020-05-10 06:50:21.520	info	instance system.adapter.sonos.0 started with pid 15535
host.raspberrypi	2020-05-10 06:49:51.453	info	Restart adapter system.adapter.sonos.0 because enabled
host.raspberrypi	2020-05-10 06:49:51.452	info	instance system.adapter.sonos.0 terminated with code 0 (NO_ERROR)
sonos.0	2020-05-10 06:49:51.251	error	at processTicksAndRejections (internal/process/task_queues.js:97:5)
sonos.0	2020-05-10 06:49:51.251	error	at /opt/iobroker/node_modules/standard-as-callback/built/index.js:19:49
sonos.0	2020-05-10 06:49:51.251	error	at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:11:23)
sonos.0	2020-05-10 06:49:51.251	error	at /opt/iobroker/node_modules/iobroker.objects-redis/index.js:1:93234
sonos.0	2020-05-10 06:49:51.251	error	at /opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:5012:26
sonos.0	2020-05-10 06:49:51.251	error	at checkState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4904:68)
sonos.0	2020-05-10 06:49:51.251	error	(14829) TypeError: Cannot read property 'state' of undefined
sonos.0	2020-05-10 06:49:51.250	error	(14829) uncaught exception: Cannot read property 'state' of undefined
sonos.0	2020-05-10 06:49:51.228	error	(14829) unknown user "undefined"
sonos.0	2020-05-10 06:49:50.987	error	at processTicksAndRejections (internal/process/task_queues.js:97:5)
sonos.0	2020-05-10 06:49:50.987	error	at /opt/iobroker/node_modules/standard-as-callback/built/index.js:19:49
sonos.0	2020-05-10 06:49:50.987	error	at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:11:23)
sonos.0	2020-05-10 06:49:50.987	error	at /opt/iobroker/node_modules/iobroker.objects-redis/index.js:1:93234
sonos.0	2020-05-10 06:49:50.987	error	at /opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:5012:26
sonos.0	2020-05-10 06:49:50.987	error	at checkState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4904:68)
sonos.0	2020-05-10 06:49:50.987	error	(14829) TypeError: Cannot read property 'state' of undefined
sonos.0	2020-05-10 06:49:50.986	error	(14829) uncaught exception: Cannot read property 'state' of undefined
sonos.0	2020-05-10 06:49:50.936	info	(14829) Terminated (NO_ERROR): Without reason
sonos.0	2020-05-10 06:49:50.935	info	(14829) terminating
sonos.0	2020-05-10 06:49:50.924	error	(14829) unknown user "undefined"
sonos.0	2020-05-10 06:49:50.858	info	(14829) terminating
sonos.0	2020-05-10 06:49:50.856	error	at processTicksAndRejections (internal/process/task_queues.js:97:5)
sonos.0	2020-05-10 06:49:50.856	error	at /opt/iobroker/node_modules/standard-as-callback/built/index.js:19:49
sonos.0	2020-05-10 06:49:50.856	error	at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:11:23)
sonos.0	2020-05-10 06:49:50.856	error	at /opt/iobroker/node_modules/iobroker.objects-redis/index.js:1:93234
sonos.0	2020-05-10 06:49:50.856	error	at /opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:5012:26
sonos.0	2020-05-10 06:49:50.856	error	at checkState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4904:68)
sonos.0	2020-05-10 06:49:50.856	error	(14829) TypeError: Cannot read property 'state' of undefined
sonos.0	2020-05-10 06:49:50.852	error	(14829) uncaught exception: Cannot read property 'state' of undefined
sonos.0	2020-05-10 06:49:50.839	error	(14829) unknown user "undefined"

                    EDIT: Das kam nach dem abschalten des Adapters dazu,

                    host.raspberrypi	2020-05-10 06:51:28.854	info	Do not restart adapter system.adapter.sonos.0 because disabled or deleted
host.raspberrypi	2020-05-10 06:51:28.853	error	instance system.adapter.sonos.0 terminated with code 3 (NO_ADAPTER_CONFIG_FOUND)
sonos.0	2020-05-10 06:51:28.315	warn	(16988) Terminated (NO_ADAPTER_CONFIG_FOUND): Without reason
sonos.0	2020-05-10 06:51:28.303	error	(16988) adapter disabled
host.raspberrypi	2020-05-10 06:51:12.560	info	"system.adapter.sonos.0" disabled

                    Gruß Michael
                    Sofern Beiträge hilfreich für Dich sind, nutze das Voting unten rechts.

                    S 1 Reply Last reply
                    0
                    • MichMeinM MichMein

                      Hi,

                      Ich habe anscheinend das gleiche Problem wie @skokarl mit dem Sonos Adapter 😞 nach Update auf 3.1.3

                      
host.raspberrypi	2020-05-10 06:50:57.059	info	Restart adapter system.adapter.sonos.0 because enabled
host.raspberrypi	2020-05-10 06:50:57.058	info	instance system.adapter.sonos.0 terminated with code 0 (NO_ERROR)
sonos.0	2020-05-10 06:50:56.855	error	(16270) TypeError: Cannot read property 'state' of undefined at checkState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4904:68) at /opt/iobroker/node_modules/iobroker.js-
sonos.0	2020-05-10 06:50:56.854	error	(16270) uncaught exception: Cannot read property 'state' of undefined
sonos.0	2020-05-10 06:50:56.831	error	(16270) unknown user "undefined"
sonos.0	2020-05-10 06:50:56.401	error	(16270) TypeError: Cannot read property 'state' of undefined at checkState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4904:68) at /opt/iobroker/node_modules/iobroker.js-
sonos.0	2020-05-10 06:50:56.400	error	(16270) uncaught exception: Cannot read property 'state' of undefined
sonos.0	2020-05-10 06:50:56.357	info	(16270) Terminated (NO_ERROR): Without reason
sonos.0	2020-05-10 06:50:56.356	info	(16270) terminating
sonos.0	2020-05-10 06:50:56.350	error	(16270) unknown user "undefined"
sonos.0	2020-05-10 06:50:56.275	info	(16270) terminating
sonos.0	2020-05-10 06:50:56.272	error	(16270) TypeError: Cannot read property 'state' of undefined at checkState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4904:68) at /opt/iobroker/node_modules/iobroker.js-
sonos.0	2020-05-10 06:50:56.269	error	(16270) uncaught exception: Cannot read property 'state' of undefined
sonos.0	2020-05-10 06:50:56.256	error	(16270) unknown user "undefined"
sonos.0	2020-05-10 06:50:55.620	info	(16270) starting. Version 2.0.1 in /opt/iobroker/node_modules/iobroker.sonos, node: v12.16.3, js-controller: 3.1.3
host.raspberrypi	2020-05-10 06:50:54.368	info	instance system.adapter.sonos.0 started with pid 16270
host.raspberrypi	2020-05-10 06:50:24.346	info	Restart adapter system.adapter.sonos.0 because enabled
host.raspberrypi	2020-05-10 06:50:24.345	info	instance system.adapter.sonos.0 terminated with code 0 (NO_ERROR)
sonos.0	2020-05-10 06:50:23.819	info	(15535) Terminated (NO_ERROR): Without reason
sonos.0	2020-05-10 06:50:23.817	info	(15535) terminating
sonos.0	2020-05-10 06:50:23.777	error	(15535) TypeError: Cannot read property 'state' of undefined at checkState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4904:68) at /opt/iobroker/node_modules/iobroker.js-
sonos.0	2020-05-10 06:50:23.776	error	(15535) uncaught exception: Cannot read property 'state' of undefined
sonos.0	2020-05-10 06:50:23.775	error	(15535) TypeError: Cannot read property 'state' of undefined at checkState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4904:68) at /opt/iobroker/node_modules/iobroker.js-
sonos.0	2020-05-10 06:50:23.775	error	(15535) uncaught exception: Cannot read property 'state' of undefined
sonos.0	2020-05-10 06:50:23.744	error	(15535) unknown user "undefined"
sonos.0	2020-05-10 06:50:23.726	info	(15535) terminating
sonos.0	2020-05-10 06:50:23.723	error	(15535) TypeError: Cannot read property 'state' of undefined at checkState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4904:68) at /opt/iobroker/node_modules/iobroker.js-
sonos.0	2020-05-10 06:50:23.720	error	(15535) uncaught exception: Cannot read property 'state' of undefined
sonos.0	2020-05-10 06:50:23.717	error	(15535) unknown user "undefined"
sonos.0	2020-05-10 06:50:23.683	error	(15535) unknown user "undefined"
sonos.0	2020-05-10 06:50:22.987	info	(15535) starting. Version 2.0.1 in /opt/iobroker/node_modules/iobroker.sonos, node: v12.16.3, js-controller: 3.1.3
host.raspberrypi	2020-05-10 06:50:21.520	info	instance system.adapter.sonos.0 started with pid 15535
host.raspberrypi	2020-05-10 06:49:51.453	info	Restart adapter system.adapter.sonos.0 because enabled
host.raspberrypi	2020-05-10 06:49:51.452	info	instance system.adapter.sonos.0 terminated with code 0 (NO_ERROR)
sonos.0	2020-05-10 06:49:51.251	error	at processTicksAndRejections (internal/process/task_queues.js:97:5)
sonos.0	2020-05-10 06:49:51.251	error	at /opt/iobroker/node_modules/standard-as-callback/built/index.js:19:49
sonos.0	2020-05-10 06:49:51.251	error	at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:11:23)
sonos.0	2020-05-10 06:49:51.251	error	at /opt/iobroker/node_modules/iobroker.objects-redis/index.js:1:93234
sonos.0	2020-05-10 06:49:51.251	error	at /opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:5012:26
sonos.0	2020-05-10 06:49:51.251	error	at checkState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4904:68)
sonos.0	2020-05-10 06:49:51.251	error	(14829) TypeError: Cannot read property 'state' of undefined
sonos.0	2020-05-10 06:49:51.250	error	(14829) uncaught exception: Cannot read property 'state' of undefined
sonos.0	2020-05-10 06:49:51.228	error	(14829) unknown user "undefined"
sonos.0	2020-05-10 06:49:50.987	error	at processTicksAndRejections (internal/process/task_queues.js:97:5)
sonos.0	2020-05-10 06:49:50.987	error	at /opt/iobroker/node_modules/standard-as-callback/built/index.js:19:49
sonos.0	2020-05-10 06:49:50.987	error	at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:11:23)
sonos.0	2020-05-10 06:49:50.987	error	at /opt/iobroker/node_modules/iobroker.objects-redis/index.js:1:93234
sonos.0	2020-05-10 06:49:50.987	error	at /opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:5012:26
sonos.0	2020-05-10 06:49:50.987	error	at checkState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4904:68)
sonos.0	2020-05-10 06:49:50.987	error	(14829) TypeError: Cannot read property 'state' of undefined
sonos.0	2020-05-10 06:49:50.986	error	(14829) uncaught exception: Cannot read property 'state' of undefined
sonos.0	2020-05-10 06:49:50.936	info	(14829) Terminated (NO_ERROR): Without reason
sonos.0	2020-05-10 06:49:50.935	info	(14829) terminating
sonos.0	2020-05-10 06:49:50.924	error	(14829) unknown user "undefined"
sonos.0	2020-05-10 06:49:50.858	info	(14829) terminating
sonos.0	2020-05-10 06:49:50.856	error	at processTicksAndRejections (internal/process/task_queues.js:97:5)
sonos.0	2020-05-10 06:49:50.856	error	at /opt/iobroker/node_modules/standard-as-callback/built/index.js:19:49
sonos.0	2020-05-10 06:49:50.856	error	at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:11:23)
sonos.0	2020-05-10 06:49:50.856	error	at /opt/iobroker/node_modules/iobroker.objects-redis/index.js:1:93234
sonos.0	2020-05-10 06:49:50.856	error	at /opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:5012:26
sonos.0	2020-05-10 06:49:50.856	error	at checkState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4904:68)
sonos.0	2020-05-10 06:49:50.856	error	(14829) TypeError: Cannot read property 'state' of undefined
sonos.0	2020-05-10 06:49:50.852	error	(14829) uncaught exception: Cannot read property 'state' of undefined
sonos.0	2020-05-10 06:49:50.839	error	(14829) unknown user "undefined"

                      EDIT: Das kam nach dem abschalten des Adapters dazu,

                      host.raspberrypi	2020-05-10 06:51:28.854	info	Do not restart adapter system.adapter.sonos.0 because disabled or deleted
host.raspberrypi	2020-05-10 06:51:28.853	error	instance system.adapter.sonos.0 terminated with code 3 (NO_ADAPTER_CONFIG_FOUND)
sonos.0	2020-05-10 06:51:28.315	warn	(16988) Terminated (NO_ADAPTER_CONFIG_FOUND): Without reason
sonos.0	2020-05-10 06:51:28.303	error	(16988) adapter disabled
host.raspberrypi	2020-05-10 06:51:12.560	info	"system.adapter.sonos.0" disabled
                      S Offline
                      S Offline
                      skokarl
                      wrote on last edited by
                      #874

                      @MichMein

                      mach ihn weg..... der geht sowieso schon lange nicht mehr richtig.

                      oder stell nen Issue auf Github ein.

                      Alternative

                      IOBroker mit Proxmox auf Celeron Nuc mit 16 GB und Debian11, Sonos API, Echo Show 15 als Wandtablet, Homematic IP, HUE, Sonos, Echos, DS718+ als Backup

                      MichMeinM 1 Reply Last reply
                      0
                      • S skokarl

                        @MichMein

                        mach ihn weg..... der geht sowieso schon lange nicht mehr richtig.

                        oder stell nen Issue auf Github ein.

                        Alternative

                        MichMeinM Online
                        MichMeinM Online
                        MichMein
                        wrote on last edited by
                        #875

                        @skokarl du bist ja ne Marke. Lässt mich nen riesigen Thread lesen und kurz vor Schluss kommt dann das 😂

                        @skokarl sagte in Sonos-HTTP-API Installation für Newbies, Dummies und mich:

                        ACHTUNG DAS UPDATE SONOS S2 MACHT DIE API EVTL. UNBRAUCHBAR

                        S2 Update

                        Danke, es hätte ja vielleicht tatsächlich ne Alternative sein können. Aber Ich warte erstmal ab was da nich so alles kommt. Sowohl der Adapter als auch die API stellt nicht die für mich interessanten zu automatisierenden Funktionen bereit. Abwarten und Kaffee trinken.

                        Gruß Michael
                        Sofern Beiträge hilfreich für Dich sind, nutze das Voting unten rechts.

                        1 Reply Last reply
                        1
                        • apollon77A apollon77

                          @Holger76 Ich habe gerade die 3.1.3 released die deine Probleme beheben sollte. Habe mich entschieden nach Check das ganze im js-controller zu fixen. Es lag daran das die Passwörter falsch entschlüsselt wurden. Bitte checke mal die 3.1.3 sobald Sie für dich da ist

                          Holger76H Offline
                          Holger76H Offline
                          Holger76
                          wrote on last edited by
                          #876

                          @apollon77 Alles i.O . mit der neuen Version, beide Adapter sind grün !! TOP

                          NUC8I5BEH (32GB,1TB-SSD) -> Proxmox VM [ioBroker.Pro auf Debian]+[InfluxDB/Grafana]+[AdGuard]+[ Rasp.matic] + [Conbee3] +[Graylog]+[Octopi]
                          NUC6CAYH (16GB) [Proxmox Backup Server]+[OMV]

                          1 Reply Last reply
                          0
                          • JB_SullivanJ Offline
                            JB_SullivanJ Offline
                            JB_Sullivan
                            wrote on last edited by
                            #877

                            Mal eine kurze Frage am Rande. Ich war jetzt eine Woche nicht aktiv und sehe heute, das schon wieder 9 Adapter Updates und ein js-controller Update anstehen.

                            In welcher Reihenfolge machte man es am "Richtigsten"?

                            Erst den js-controller und dann die Adapter Updates oder anders herum?

                            ioBroker auf Intel Core i3-5005U NUC und Windwos10 Pro

                            Thomas BraunT apollon77A 2 Replies Last reply
                            0
                            • JB_SullivanJ JB_Sullivan

                              Mal eine kurze Frage am Rande. Ich war jetzt eine Woche nicht aktiv und sehe heute, das schon wieder 9 Adapter Updates und ein js-controller Update anstehen.

                              In welcher Reihenfolge machte man es am "Richtigsten"?

                              Erst den js-controller und dann die Adapter Updates oder anders herum?

                              Thomas BraunT Online
                              Thomas BraunT Online
                              Thomas Braun
                              Most Active
                              wrote on last edited by Thomas Braun
                              #878

                              @JB_Sullivan Erst die Adapter, dann der controller. So mache ich es jedenfalls immer.
                              Und das darunter liegende System halte ich auch auf Stand.

                              Linux-Werkzeugkasten:
                              https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                              NodeJS Fixer Skript:
                              https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                              iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                              J 1 Reply Last reply
                              0
                              • Thomas BraunT Thomas Braun

                                @JB_Sullivan Erst die Adapter, dann der controller. So mache ich es jedenfalls immer.
                                Und das darunter liegende System halte ich auch auf Stand.

                                J Offline
                                J Offline
                                Jan1
                                wrote on last edited by
                                #879

                                @Thomas-Braun
                                Da hätte ich jetzt exakt anderes rum getippt. Zuerst das System dann das was drauf aufbaut. Wobei ich das schon so und so gemacht hatte und weder noch ein Problem damit 😉

                                1 Reply Last reply
                                0
                                • JB_SullivanJ Offline
                                  JB_SullivanJ Offline
                                  JB_Sullivan
                                  wrote on last edited by
                                  #880

                                  Ja ich habe auch schon beides gemacht, aber eigentlich habe ich immer Probleme ( siehe hier: https://forum.iobroker.net/topic/32892/update-prozess-unendlich-lang-iob-defekt/7 )

                                  Darum dachte ich das es ggf. eine zwingende Reihenfolge geben sollte.

                                  ioBroker auf Intel Core i3-5005U NUC und Windwos10 Pro

                                  Thomas BraunT J 2 Replies Last reply
                                  0
                                  • JB_SullivanJ JB_Sullivan

                                    Ja ich habe auch schon beides gemacht, aber eigentlich habe ich immer Probleme ( siehe hier: https://forum.iobroker.net/topic/32892/update-prozess-unendlich-lang-iob-defekt/7 )

                                    Darum dachte ich das es ggf. eine zwingende Reihenfolge geben sollte.

                                    Thomas BraunT Online
                                    Thomas BraunT Online
                                    Thomas Braun
                                    Most Active
                                    wrote on last edited by
                                    #881

                                    @JB_Sullivan Empfohlen wird es wohl so:

                                    Die folgenden Adapter müssen auf die genannten Minimalversionsnummern aktualisiert werden, da diese sonst nicht mit dem js-controller 3.0/3.1 funktionieren. Diese Updates am besten vorher ausführen, weil alle genannten Versionen auch mit den alten js-controller Versionen funktionieren.

                                    Linux-Werkzeugkasten:
                                    https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                                    NodeJS Fixer Skript:
                                    https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                                    iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                                    1 Reply Last reply
                                    0
                                    • JB_SullivanJ JB_Sullivan

                                      Ja ich habe auch schon beides gemacht, aber eigentlich habe ich immer Probleme ( siehe hier: https://forum.iobroker.net/topic/32892/update-prozess-unendlich-lang-iob-defekt/7 )

                                      Darum dachte ich das es ggf. eine zwingende Reihenfolge geben sollte.

                                      J Offline
                                      J Offline
                                      Jan1
                                      wrote on last edited by
                                      #882

                                      @JB_Sullivan
                                      Du bist auf nem Windows System mit IOBroker, da ist eh wieder alles anderes und nicht ganz so optimal.

                                      Thomas BraunT 1 Reply Last reply
                                      0
                                      • J Jan1

                                        @JB_Sullivan
                                        Du bist auf nem Windows System mit IOBroker, da ist eh wieder alles anderes und nicht ganz so optimal.

                                        Thomas BraunT Online
                                        Thomas BraunT Online
                                        Thomas Braun
                                        Most Active
                                        wrote on last edited by
                                        #883

                                        @Jan1 @JB_Sullivan
                                        Bei Windows-Installer soll man auf einen aktualisierten Installer warten, hab ich irgendwo gelesen. Aber da ich kein Windows fahre...

                                        Linux-Werkzeugkasten:
                                        https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                                        NodeJS Fixer Skript:
                                        https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                                        iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                                        JB_SullivanJ 1 Reply Last reply
                                        0
                                        • Thomas BraunT Thomas Braun

                                          @Jan1 @JB_Sullivan
                                          Bei Windows-Installer soll man auf einen aktualisierten Installer warten, hab ich irgendwo gelesen. Aber da ich kein Windows fahre...

                                          JB_SullivanJ Offline
                                          JB_SullivanJ Offline
                                          JB_Sullivan
                                          wrote on last edited by
                                          #884

                                          @Thomas-Braun

                                          Bei meinem Produktiv System würde ich das auch tun, aber ich kann die Finger nicht von diesen latest Updates auf meinem Testsystem lassen. Wenn das dann man baden geht, ist es prinzipell nicht schlimm, aber es Fuckt mich dann trotzdem immer wieder ab, wenn ich das Testsystem neu aufsetzten muss.

                                          ioBroker auf Intel Core i3-5005U NUC und Windwos10 Pro

                                          J 1 Reply Last reply
                                          0
                                          Reply
                                          • Reply as topic
                                          Log in to reply
                                          • Oldest to Newest
                                          • Newest to Oldest
                                          • Most Votes

                                          Support us

                                          ioBroker
                                          Community Adapters
                                          Donate
                                          FAQ Cloud / IOT
                                          HowTo: Node.js-Update
                                          HowTo: Backup/Restore
                                          Downloads
                                          BLOG

                                          112

                                          Online

                                          32.4k

                                          Users

                                          81.3k

                                          Topics

                                          1.3m

                                          Posts
                                          Community
                                          Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                          ioBroker Community 2014-2025
                                          logo
                                          • Login
                                          • Don't have an account? Register
                                          • Login or register to search.
                                          • First post
                                            Last post
                                          0
                                          • Recent
                                          • Tags
                                          • Unread 0
                                          • Categories
                                          • Unreplied
                                          • Popular
                                          • GitHub
                                          • Docu
                                          • Hilfe