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. Error/Bug
  4. viele WARN seit Systemwechsel

NEWS

  • Monatsrückblick Januar/Februar 2026 ist online!
    BluefoxB
    Bluefox
    17
    1
    574

  • Jahresrückblick 2025 – unser neuer Blogbeitrag ist online! ✨
    BluefoxB
    Bluefox
    17
    1
    5.5k

  • Neuer Blogbeitrag: Monatsrückblick - Dezember 2025 🎄
    BluefoxB
    Bluefox
    13
    1
    1.4k

viele WARN seit Systemwechsel

Geplant Angeheftet Gesperrt Verschoben Error/Bug
7 Beiträge 3 Kommentatoren 567 Aufrufe 3 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.
  • NegaleinN Offline
    NegaleinN Offline
    Negalein
    Global Moderator
    schrieb am zuletzt editiert von
    #1
    Platform: linux
    os: linux
    Architecture: x64
    CPUs: 2
    Speed: 3547 MHz
    Model: Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz
    RAM: 6 GB 
    System uptime: 1 T. 12:37:13
    Node.js: v14.17.1
    NPM: 6.14.13
    Disk size: 9.8 GiB
    Disk free: 3.7 GiB
    adapters count: 421
    Uptime: 1 T. 08:42:02
    Active instances: 54
    location: /opt/iobroker/
    

    Hallo

    Seit dem Umzug von Synology Docker auf Proxmox (ioB als VM) hab ich viele Warn-Meldungen im Log.

    Unter anderem zB

    web.0	2021-07-07 22:08:25.904	warn	(19967) Read-only state "alexa2.0.Echo-Devices.G090U5099045059V.Player.mediaProgress" has been written without ack-flag with value "182"
    web.0	2021-07-07 22:08:22.179	warn	(19967) Read-only state "alexa2.0.Echo-Devices.G090U5099045059V.Player.mediaProgress" has been written without ack-flag with value "177"
    web.0	2021-07-07 22:08:12.292	warn	(19967) Read-only state "alexa2.0.Echo-Devices.G090U5099045059V.Player.mediaProgress" has been written without ack-flag with value "165"
    web.0	2021-07-07 22:08:12.230	warn	(19967) Read-only state "alexa2.0.Echo-Devices.G090U5099045059V.Player.mediaProgress" has been written without ack-flag with value "165"
    javascript.0	2021-07-07 22:08:08.070	warn	(10263) Read-only state "javascript.0.FensterUeberwachung.OverviewTable" has been written without ack-flag with value "<table style='width:100%; border-collapse: collapse; border: 0px solid black;'><
    web.0	2021-07-07 22:08:06.122	warn	(19967) Read-only state "alexa2.0.Echo-Devices.G090U5099045059V.Player.mediaProgress" has been written without ack-flag with value "161"
    web.0	2021-07-07 22:08:02.183	warn	(19967) Read-only state "alexa2.0.Echo-Devices.G090U5099045059V.Player.mediaProgress" has been written without ack-flag with value "155"
    javascript.0	2021-07-07 22:08:00.214	warn	(10263) at processTimers (internal/timers.js:500:7)
    javascript.0	2021-07-07 22:08:00.214	warn	(10263) at listOnTimeout (internal/timers.js:557:17)
    javascript.0	2021-07-07 22:08:00.214	warn	(10263) at Timeout._onTimeout (/opt/iobroker/node_modules/iobroker.javascript/node_modules/node-schedule/lib/schedule.js:510:7)
    javascript.0	2021-07-07 22:08:00.214	warn	(10263) at /opt/iobroker/node_modules/iobroker.javascript/node_modules/node-schedule/lib/schedule.js:552:11
    javascript.0	2021-07-07 22:08:00.214	warn	(10263) at Job.invoke (/opt/iobroker/node_modules/iobroker.javascript/node_modules/node-schedule/lib/schedule.js:173:10)
    javascript.0	2021-07-07 22:08:00.214	warn	(10263) at Job.job (/opt/iobroker/node_modules/iobroker.javascript/lib/sandbox.js:1301:34)
    javascript.0	2021-07-07 22:08:00.213	warn	(10263) at Object.<anonymous> (script.js.Fritz.Fritz-Onlinezeit:7:27)
    javascript.0	2021-07-07 22:08:00.213	warn	(10263) getState "tr-064.0.states.externalIP" not found (3)
    web.0	2021-07-07 22:07:54.301	warn	(19967) Read-only state "alexa2.0.Echo-Devices.G090U5099045059V.Player.mediaProgress" has been written without ack-flag with value "150"
    web.0	2021-07-07 22:07:51.195	warn	(19967) Read-only state "alexa2.0.Echo-Devices.G090U5099045059V.Player.mediaProgress" has been written without ack-flag with value "144"
    web.0	2021-07-07 22:07:41.282	warn	(19967) Read-only state "alexa2.0.Echo-Devices.G090U5099045059V.Player.mediaProgress" has been written without ack-flag with value "137"
    web.0	2021-07-07 22:07:38.186	warn	(19967) Read-only state "alexa2.0.Echo-Devices.G090U5099045059V.Player.mediaProgress" has been written without ack-flag with value "132"
    web.0	2021-07-07 22:07:31.664	warn	(19967) Read-only state "alexa2.0.Echo-Devices.G090U5099045059V.Player.mediaProgress" has been written without ack-flag with value "127"
    web.0	2021-07-07 22:07:28.193	warn	(19967) Read-only state "alexa2.0.Echo-Devices.G090U5099045059V.Player.mediaProgress" has been written without ack-flag with value "121"
    web.0	2021-07-07 22:07:20.365	warn	(19967) Read-only state "alexa2.0.Echo-Devices.G090U5099045059V.Player.mediaProgress" has been written without ack-flag with value "116"
    web.0	2021-07-07 22:07:17.180	warn	(19967) Read-only state "alexa2.0.Echo-Devices.G090U5099045059V.Player.mediaProgress" has been written without ack-flag with value "110"
    

    Ich hab ein Backup (mit Backitup erstellt) zurückgespielt.
    Es läuft eigentlich alles, bis auf diese Menge Warn-Meldungen.
    Log wird täglich ca. 50 MB groß :confounded:

    ° Node.js & System Update ---> sudo apt update, iob stop, sudo apt full-upgrade
    ° Node.js Fixer ---> iob nodejs-update
    ° Fixer ---> iob fix

    FeuersturmF 1 Antwort Letzte Antwort
    0
    • NegaleinN Negalein
      Platform: linux
      os: linux
      Architecture: x64
      CPUs: 2
      Speed: 3547 MHz
      Model: Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz
      RAM: 6 GB 
      System uptime: 1 T. 12:37:13
      Node.js: v14.17.1
      NPM: 6.14.13
      Disk size: 9.8 GiB
      Disk free: 3.7 GiB
      adapters count: 421
      Uptime: 1 T. 08:42:02
      Active instances: 54
      location: /opt/iobroker/
      

      Hallo

      Seit dem Umzug von Synology Docker auf Proxmox (ioB als VM) hab ich viele Warn-Meldungen im Log.

      Unter anderem zB

      web.0	2021-07-07 22:08:25.904	warn	(19967) Read-only state "alexa2.0.Echo-Devices.G090U5099045059V.Player.mediaProgress" has been written without ack-flag with value "182"
      web.0	2021-07-07 22:08:22.179	warn	(19967) Read-only state "alexa2.0.Echo-Devices.G090U5099045059V.Player.mediaProgress" has been written without ack-flag with value "177"
      web.0	2021-07-07 22:08:12.292	warn	(19967) Read-only state "alexa2.0.Echo-Devices.G090U5099045059V.Player.mediaProgress" has been written without ack-flag with value "165"
      web.0	2021-07-07 22:08:12.230	warn	(19967) Read-only state "alexa2.0.Echo-Devices.G090U5099045059V.Player.mediaProgress" has been written without ack-flag with value "165"
      javascript.0	2021-07-07 22:08:08.070	warn	(10263) Read-only state "javascript.0.FensterUeberwachung.OverviewTable" has been written without ack-flag with value "<table style='width:100%; border-collapse: collapse; border: 0px solid black;'><
      web.0	2021-07-07 22:08:06.122	warn	(19967) Read-only state "alexa2.0.Echo-Devices.G090U5099045059V.Player.mediaProgress" has been written without ack-flag with value "161"
      web.0	2021-07-07 22:08:02.183	warn	(19967) Read-only state "alexa2.0.Echo-Devices.G090U5099045059V.Player.mediaProgress" has been written without ack-flag with value "155"
      javascript.0	2021-07-07 22:08:00.214	warn	(10263) at processTimers (internal/timers.js:500:7)
      javascript.0	2021-07-07 22:08:00.214	warn	(10263) at listOnTimeout (internal/timers.js:557:17)
      javascript.0	2021-07-07 22:08:00.214	warn	(10263) at Timeout._onTimeout (/opt/iobroker/node_modules/iobroker.javascript/node_modules/node-schedule/lib/schedule.js:510:7)
      javascript.0	2021-07-07 22:08:00.214	warn	(10263) at /opt/iobroker/node_modules/iobroker.javascript/node_modules/node-schedule/lib/schedule.js:552:11
      javascript.0	2021-07-07 22:08:00.214	warn	(10263) at Job.invoke (/opt/iobroker/node_modules/iobroker.javascript/node_modules/node-schedule/lib/schedule.js:173:10)
      javascript.0	2021-07-07 22:08:00.214	warn	(10263) at Job.job (/opt/iobroker/node_modules/iobroker.javascript/lib/sandbox.js:1301:34)
      javascript.0	2021-07-07 22:08:00.213	warn	(10263) at Object.<anonymous> (script.js.Fritz.Fritz-Onlinezeit:7:27)
      javascript.0	2021-07-07 22:08:00.213	warn	(10263) getState "tr-064.0.states.externalIP" not found (3)
      web.0	2021-07-07 22:07:54.301	warn	(19967) Read-only state "alexa2.0.Echo-Devices.G090U5099045059V.Player.mediaProgress" has been written without ack-flag with value "150"
      web.0	2021-07-07 22:07:51.195	warn	(19967) Read-only state "alexa2.0.Echo-Devices.G090U5099045059V.Player.mediaProgress" has been written without ack-flag with value "144"
      web.0	2021-07-07 22:07:41.282	warn	(19967) Read-only state "alexa2.0.Echo-Devices.G090U5099045059V.Player.mediaProgress" has been written without ack-flag with value "137"
      web.0	2021-07-07 22:07:38.186	warn	(19967) Read-only state "alexa2.0.Echo-Devices.G090U5099045059V.Player.mediaProgress" has been written without ack-flag with value "132"
      web.0	2021-07-07 22:07:31.664	warn	(19967) Read-only state "alexa2.0.Echo-Devices.G090U5099045059V.Player.mediaProgress" has been written without ack-flag with value "127"
      web.0	2021-07-07 22:07:28.193	warn	(19967) Read-only state "alexa2.0.Echo-Devices.G090U5099045059V.Player.mediaProgress" has been written without ack-flag with value "121"
      web.0	2021-07-07 22:07:20.365	warn	(19967) Read-only state "alexa2.0.Echo-Devices.G090U5099045059V.Player.mediaProgress" has been written without ack-flag with value "116"
      web.0	2021-07-07 22:07:17.180	warn	(19967) Read-only state "alexa2.0.Echo-Devices.G090U5099045059V.Player.mediaProgress" has been written without ack-flag with value "110"
      

      Ich hab ein Backup (mit Backitup erstellt) zurückgespielt.
      Es läuft eigentlich alles, bis auf diese Menge Warn-Meldungen.
      Log wird täglich ca. 50 MB groß :confounded:

      FeuersturmF Offline
      FeuersturmF Offline
      Feuersturm
      schrieb am zuletzt editiert von Feuersturm
      #2

      @negalein Hi, du nutzt wohl den js-controller 3.3.x der noch im beta Stadium ist (https://forum.iobroker.net/topic/44624/js-controller-3-3-jetzt-im-beta)

      Die Warnungen müssen durch Anpassung in den entsprechenden Adaptern / Skripten gelöst werden. Schau am besten einmal nach, ob es bei den entsprechenden Adaptern auf GitHub schon passende issues gibt.

      Wenn es entsprechende issues gibt kannst du auch temporär das log Level auf error hochsetzen, bis die Adapter aktualisiert wurden.

      NegaleinN 1 Antwort Letzte Antwort
      0
      • FeuersturmF Feuersturm

        @negalein Hi, du nutzt wohl den js-controller 3.3.x der noch im beta Stadium ist (https://forum.iobroker.net/topic/44624/js-controller-3-3-jetzt-im-beta)

        Die Warnungen müssen durch Anpassung in den entsprechenden Adaptern / Skripten gelöst werden. Schau am besten einmal nach, ob es bei den entsprechenden Adaptern auf GitHub schon passende issues gibt.

        Wenn es entsprechende issues gibt kannst du auch temporär das log Level auf error hochsetzen, bis die Adapter aktualisiert wurden.

        NegaleinN Offline
        NegaleinN Offline
        Negalein
        Global Moderator
        schrieb am zuletzt editiert von
        #3

        @feuersturm sagte in viele WARN seit Systemwechsel:

        Die Warnungen müssen durch Anpassung in den entsprechenden Adaptern / Skripten gelöst werden. Schau am besten einmal nach, ob es bei den entsprechenden Adaptern auf GitHub schon passende issues gibt.

        Ja, den 3.3.14

        Dann werd ich mal Git durchforsten.

        ° Node.js & System Update ---> sudo apt update, iob stop, sudo apt full-upgrade
        ° Node.js Fixer ---> iob nodejs-update
        ° Fixer ---> iob fix

        1 Antwort Letzte Antwort
        0
        • NegaleinN Offline
          NegaleinN Offline
          Negalein
          Global Moderator
          schrieb am zuletzt editiert von
          #4

          Es dürfte an VIS liegen.
          Aber @apollon77 weiß auch gerade nicht weiter.
          Vielleicht hat noch jemand eine Idee?

          web.0	2021-07-07 22:08:25.904	warn	(19967) Read-only state "alexa2.0.Echo-Devices.G090U5099045059V.Player.mediaProgress" has been written without ack-flag with value "182"
          web.0	2021-07-07 22:08:22.179	warn	(19967) Read-only state "alexa2.0.Echo-Devices.G090U5099045059V.Player.mediaProgress" has been written without ack-flag with value "177"
          web.0	2021-07-07 22:08:12.292	warn	(19967) Read-only state "alexa2.0.Echo-Devices.G090U5099045059V.Player.mediaProgress" has been written without ack-flag with value "165"
          web.0	2021-07-07 22:08:12.230	warn	(19967) Read-only state "alexa2.0.Echo-Devices.G090U5099045059V.Player.mediaProgress" has been written without ack-flag with value "165"
          web.0	2021-07-07 22:08:06.122	warn	(19967) Read-only state "alexa2.0.Echo-Devices.G090U5099045059V.Player.mediaProgress" has been written without ack-flag with value "161"
          web.0	2021-07-07 22:08:02.183	warn	(19967) Read-only state "alexa2.0.Echo-Devices.G090U5099045059V.Player.mediaProgress" has been written without ack-flag with value "155"
          web.0	2021-07-07 22:07:54.301	warn	(19967) Read-only state "alexa2.0.Echo-Devices.G090U5099045059V.Player.mediaProgress" has been written without ack-flag with value "150"
          web.0	2021-07-07 22:07:51.195	warn	(19967) Read-only state "alexa2.0.Echo-Devices.G090U5099045059V.Player.mediaProgress" has been written without ack-flag with value "144"
          web.0	2021-07-07 22:07:41.282	warn	(19967) Read-only state "alexa2.0.Echo-Devices.G090U5099045059V.Player.mediaProgress" has been written without ack-flag with value "137"
          web.0	2021-07-07 22:07:38.186	warn	(19967) Read-only state "alexa2.0.Echo-Devices.G090U5099045059V.Player.mediaProgress" has been written without ack-flag with value "132"
          web.0	2021-07-07 22:07:31.664	warn	(19967) Read-only state "alexa2.0.Echo-Devices.G090U5099045059V.Player.mediaProgress" has been written without ack-flag with value "127"
          web.0	2021-07-07 22:07:28.193	warn	(19967) Read-only state "alexa2.0.Echo-Devices.G090U5099045059V.Player.mediaProgress" has been written without ack-flag with value "121"
          web.0	2021-07-07 22:07:20.365	warn	(19967) Read-only state "alexa2.0.Echo-Devices.G090U5099045059V.Player.mediaProgress" has been written without ack-flag with value "116"
          web.0	2021-07-07 22:07:17.180	warn	(19967) Read-only state "alexa2.0.Echo-Devices.G090U5099045059V.Player.mediaProgress" has been written without ack-flag with value "110"
          

          ° Node.js & System Update ---> sudo apt update, iob stop, sudo apt full-upgrade
          ° Node.js Fixer ---> iob nodejs-update
          ° Fixer ---> iob fix

          apollon77A 1 Antwort Letzte Antwort
          0
          • NegaleinN Negalein

            Es dürfte an VIS liegen.
            Aber @apollon77 weiß auch gerade nicht weiter.
            Vielleicht hat noch jemand eine Idee?

            web.0	2021-07-07 22:08:25.904	warn	(19967) Read-only state "alexa2.0.Echo-Devices.G090U5099045059V.Player.mediaProgress" has been written without ack-flag with value "182"
            web.0	2021-07-07 22:08:22.179	warn	(19967) Read-only state "alexa2.0.Echo-Devices.G090U5099045059V.Player.mediaProgress" has been written without ack-flag with value "177"
            web.0	2021-07-07 22:08:12.292	warn	(19967) Read-only state "alexa2.0.Echo-Devices.G090U5099045059V.Player.mediaProgress" has been written without ack-flag with value "165"
            web.0	2021-07-07 22:08:12.230	warn	(19967) Read-only state "alexa2.0.Echo-Devices.G090U5099045059V.Player.mediaProgress" has been written without ack-flag with value "165"
            web.0	2021-07-07 22:08:06.122	warn	(19967) Read-only state "alexa2.0.Echo-Devices.G090U5099045059V.Player.mediaProgress" has been written without ack-flag with value "161"
            web.0	2021-07-07 22:08:02.183	warn	(19967) Read-only state "alexa2.0.Echo-Devices.G090U5099045059V.Player.mediaProgress" has been written without ack-flag with value "155"
            web.0	2021-07-07 22:07:54.301	warn	(19967) Read-only state "alexa2.0.Echo-Devices.G090U5099045059V.Player.mediaProgress" has been written without ack-flag with value "150"
            web.0	2021-07-07 22:07:51.195	warn	(19967) Read-only state "alexa2.0.Echo-Devices.G090U5099045059V.Player.mediaProgress" has been written without ack-flag with value "144"
            web.0	2021-07-07 22:07:41.282	warn	(19967) Read-only state "alexa2.0.Echo-Devices.G090U5099045059V.Player.mediaProgress" has been written without ack-flag with value "137"
            web.0	2021-07-07 22:07:38.186	warn	(19967) Read-only state "alexa2.0.Echo-Devices.G090U5099045059V.Player.mediaProgress" has been written without ack-flag with value "132"
            web.0	2021-07-07 22:07:31.664	warn	(19967) Read-only state "alexa2.0.Echo-Devices.G090U5099045059V.Player.mediaProgress" has been written without ack-flag with value "127"
            web.0	2021-07-07 22:07:28.193	warn	(19967) Read-only state "alexa2.0.Echo-Devices.G090U5099045059V.Player.mediaProgress" has been written without ack-flag with value "121"
            web.0	2021-07-07 22:07:20.365	warn	(19967) Read-only state "alexa2.0.Echo-Devices.G090U5099045059V.Player.mediaProgress" has been written without ack-flag with value "116"
            web.0	2021-07-07 22:07:17.180	warn	(19967) Read-only state "alexa2.0.Echo-Devices.G090U5099045059V.Player.mediaProgress" has been written without ack-flag with value "110"
            
            apollon77A Offline
            apollon77A Offline
            apollon77
            schrieb am zuletzt editiert von
            #5

            @negalein Ich würde hjetzt sagen ... zeig doch mal die Konfig des Vis Widgets was die mediaProgress anzeigt ... weil irgendwie muss das ja aus versehen schreiben

            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
            NegaleinN 1 Antwort Letzte Antwort
            0
            • apollon77A apollon77

              @negalein Ich würde hjetzt sagen ... zeig doch mal die Konfig des Vis Widgets was die mediaProgress anzeigt ... weil irgendwie muss das ja aus versehen schreiben

              NegaleinN Offline
              NegaleinN Offline
              Negalein
              Global Moderator
              schrieb am zuletzt editiert von
              #6

              @apollon77 sagte in viele WARN seit Systemwechsel:

              eig doch mal die Konfig des Vis Widgets was die mediaProgress anzeigt

              [{"tpl":"tplValueString","data":{"oid":"alexa2.0.Echo-Devices.G090U5099045059V.Player.mediaProgressStr","g_fixed":true,"g_visibility":true,"g_css_font_text":true,"g_css_background":false,"g_css_shadow_padding":false,"g_css_border":false,"g_gestures":false,"g_signals":false,"g_last_change":false,"visibility-cond":"==","visibility-val":"","visibility-groups-action":"hide","signals-cond-0":"==","signals-val-0":true,"signals-icon-0":"/vis.0/Buchenweg/lowbattery.png","signals-icon-size-0":0,"signals-blink-0":false,"signals-horz-0":0,"signals-vert-0":0,"signals-hide-edit-0":false,"signals-cond-1":"==","signals-val-1":true,"signals-icon-1":"/vis.0/Buchenweg/lowbattery.png","signals-icon-size-1":0,"signals-blink-1":false,"signals-horz-1":0,"signals-vert-1":0,"signals-hide-edit-1":false,"signals-cond-2":"==","signals-val-2":true,"signals-icon-2":"/vis.0/Buchenweg/lowbattery.png","signals-icon-size-2":0,"signals-blink-2":false,"signals-horz-2":0,"signals-vert-2":0,"signals-hide-edit-2":false,"lc-type":"last-change","lc-is-interval":true,"lc-is-moment":false,"lc-format":"","lc-position-vert":"top","lc-position-horz":"right","lc-offset-vert":0,"lc-offset-horz":0,"lc-font-size":"12px","lc-font-family":"","lc-font-style":"","lc-bkg-color":"","lc-color":"","lc-border-width":"0","lc-border-style":"","lc-border-color":"","lc-border-radius":10,"lc-zindex":0,"visibility-oid":"","html_prepend":"","class":"mdui-blue-glow"},"style":{"left":"354px","top":"503px","color":"#ffffff","width":"78px","height":"37px","text-align":"left","font-style":"normal","font-size":"x-large","z-index":"58","font-weight":"bold","font-family":"RobotoCondensed-Light","text-shadow":"rgba(0, 0, 0, 0.9) 3px 3px 4px"},"widgetSet":"basic"}]
              

              Edit vis.png

              ° Node.js & System Update ---> sudo apt update, iob stop, sudo apt full-upgrade
              ° Node.js Fixer ---> iob nodejs-update
              ° Fixer ---> iob fix

              1 Antwort Letzte Antwort
              0
              • NegaleinN Offline
                NegaleinN Offline
                Negalein
                Global Moderator
                schrieb am zuletzt editiert von Negalein
                #7

                @apollon77

                fast 2 Monate war Ruhe.
                Heute wieder selbes Problem.

                web.0 2021-08-24 22:01:47.187	warn	Read-only state "alexa2.0.Echo-Devices.G090U5099045059V.Player.mediaProgress" has been written without ack-flag with value "210"
                

                ° Node.js & System Update ---> sudo apt update, iob stop, sudo apt full-upgrade
                ° Node.js Fixer ---> iob nodejs-update
                ° Fixer ---> iob fix

                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

                694

                Online

                32.7k

                Benutzer

                82.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