Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. ioBroker extrem langsam

    NEWS

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

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    ioBroker extrem langsam

    This topic has been deleted. Only users with topic management privileges can see it.
    • Homoran
      Homoran Global Moderator Administrators @Spidermike last edited by

      @spidermike sagte in ioBroker extrem langsam:

      ich bin über 50 jahre alt.

      soo jung war ich auch irgend wann mal.

      @spidermike sagte in ioBroker extrem langsam:

      Und hab ehrlich gesagt nicht die Zeit mich Stundenlang hinzusetzen um alles im Forum oder Internet zu suchen

      willnicht kannnicht?

      @spidermike sagte in ioBroker extrem langsam:

      da stellt du mich wieder vor Herrausforderungen,

      einfach lesen und Bildchen gucken
      https://forum.iobroker.net/topic/51555/hinweise-für-gute-forenbeiträge/1

      S 1 Reply Last reply Reply Quote 0
      • S
        Spidermike @Homoran last edited by

        @homoran sagte in ioBroker extrem langsam:

        @spidermike sagte in ioBroker extrem langsam:

        ich bin über 50 jahre alt.

        soo jung war ich auch irgend wann mal.

        @spidermike sagte in ioBroker extrem langsam:

        Und hab ehrlich gesagt nicht die Zeit mich Stundenlang hinzusetzen um alles im Forum oder Internet zu suchen

        willnicht kannnicht?

        @spidermike sagte in ioBroker extrem langsam:

        da stellt du mich wieder vor Herrausforderungen,

        einfach lesen und Bildchen gucken
        https://forum.iobroker.net/topic/51555/hinweise-für-gute-forenbeiträge/1

        ok verstehe,
        ich bin zu blöd für mein alter und habe keine Lust (willnicht kannnicht) um zu lesen und Bildchen zu gucken weil ich einfach keine Zeit dafür habe.

        aber trotzdem danke ich Dir @Thomas-Braun für Deine Hilfe bei meinen Problemen
        Gruß Maik

        Thomas Braun Homoran 2 Replies Last reply Reply Quote 0
        • Thomas Braun
          Thomas Braun Most Active @Spidermike last edited by Thomas Braun

          @spidermike sagte in ioBroker extrem langsam:

          weil ich einfach keine Zeit dafür habe.

          Die Basics muss/kann man sich aneignen. Musste ich auch irgendwann machen.

          Logfile schaut man u. a. per

          iob logs --watch | uniq
          

          an.

          S 1 Reply Last reply Reply Quote 0
          • Homoran
            Homoran Global Moderator Administrators @Spidermike last edited by Homoran

            @spidermike sagte in ioBroker extrem langsam:

            ok verstehe,

            nicht falsch verstehen!!

            @spidermike sagte in ioBroker extrem langsam:

            weil ich einfach keine Zeit dafür habe.

            das war es was ich andeutete.
            Ein wenig Zeit findet sich immer.

            und hier hilft dir jeder gerne. Dann geht's noch schneller

            S 1 Reply Last reply Reply Quote 0
            • S
              Spidermike @Homoran last edited by

              @homoran sagte in ioBroker extrem langsam:

              @spidermike sagte in ioBroker extrem langsam:

              ok verstehe,

              nicht falsch verstehen!!

              @spidermike sagte in ioBroker extrem langsam:

              weil ich einfach keine Zeit dafür habe.

              das war es was ich andeutete.
              Ein wenig Zeit findet sich immer.

              und hier hilft dir jeder gerne. Dann geht's noch schneller

              klar für Euch ist das alles einfach weil ihr jeden Tag damit zu tun habt. Ich mache das nebebei zu meinen Job (bin selbstständig) ich bin so schon über 12 Std am arbeiten. egal

              ich bin ja auch dankbar das es Euch gibt aber diese Hinweise "Ein wenig Zeit findet sich immer" hilft mir nicht.
              Wenn man eine Familie mit zwei Kindern und Job hat dann ist die Zeit das größte Problem. Ich glaube da brauche nicht weiter darüber zu schreiben, wer in der gleichen Sitution ist weiß was ich meine.
              ok lassen wir das Thema, ich schaue mal wie es mit mit meinen problemen weiter geht.

              Danke an Euch und gute Nacht

              Thomas Braun Homoran 2 Replies Last reply Reply Quote 0
              • Thomas Braun
                Thomas Braun Most Active @Spidermike last edited by

                @spidermike sagte in ioBroker extrem langsam:

                weil ihr jeden Tag damit zu tun habt.

                Das ist aber auch nicht mein Job hier. Meine Brötchen verdiene ich natürlich auch anders.

                1 Reply Last reply Reply Quote 0
                • Homoran
                  Homoran Global Moderator Administrators @Spidermike last edited by Homoran

                  @spidermike sagte in ioBroker extrem langsam:

                  klar für Euch ist das alles einfach weil ihr jeden Tag damit zu tun habt. Ich mache das nebebei zu meinen Job (bin selbstständig) ich bin so schon über 12 Std am arbeiten. egal

                  mit 50+ hab ich noch nichts von Javascript, Linux&Co gekannt. Smarthome hatte ich nicht mal auf dem Schirm.
                  Ich hab mich auch erst mit ioBroker damit beschäftigt, auch bei 60h Wochen und länger.

                  2 Kinder & Job (mit Chefs!) hatte ich auch.
                  Und der Job hatte nicht annähernd irgendetwas mit hier dem Kram zu tun.
                  Ist alles nur Hobby nebenbei

                  @spidermike sagte in ioBroker extrem langsam:

                  wer in der gleichen Sitution ist weiß was ich meine.

                  genau!
                  Und deswegen bin ich sicher, dass du es auch noch hinbekommen wirst.

                  Deswegen unterstützen wir ja auch die, die erst anfangen.

                  1 Reply Last reply Reply Quote 0
                  • S
                    Spidermike @Thomas Braun last edited by Spidermike

                    @thomas-braun sagte in ioBroker extrem langsam:

                    iob logs --watch | uniq

                    Hallo

                    konnte mich erst jetzt wieder melden, sorry.

                    hier die Auswertung

                    2023-10-21 11:35:54.551  - error: host.raspberrypi4-iobroker Caught by controller[15]: 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:
                    2023-10-21 11:35:54.551  - error: host.raspberrypi4-iobroker Caught by controller[15]: Error: DB closed
                    2023-10-21 11:35:54.551  - error: host.raspberrypi4-iobroker Caught by controller[15]:     at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
                    2023-10-21 11:35:54.551  - error: host.raspberrypi4-iobroker Caught by controller[15]:     at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
                    2023-10-21 11:35:54.551  - error: host.raspberrypi4-iobroker Caught by controller[15]:     at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
                    2023-10-21 11:35:54.551  - error: host.raspberrypi4-iobroker Caught by controller[15]:     at Growatt._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7711:34)
                    2023-10-21 11:35:54.551  - error: host.raspberrypi4-iobroker Caught by controller[15]:     at runNextTicks (node:internal/process/task_queues:60:5)
                    2023-10-21 11:35:54.551  - error: host.raspberrypi4-iobroker Caught by controller[15]:     at processImmediate (node:internal/timers:447:9)
                    2023-10-21 11:35:54.551  - error: host.raspberrypi4-iobroker Caught by controller[15]: 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:
                    2023-10-21 11:35:54.551  - error: host.raspberrypi4-iobroker Caught by controller[15]: Error: DB closed
                    2023-10-21 11:35:54.551  - error: host.raspberrypi4-iobroker Caught by controller[15]:     at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
                    2023-10-21 11:35:54.552  - error: host.raspberrypi4-iobroker Caught by controller[15]:     at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
                    2023-10-21 11:35:54.552  - error: host.raspberrypi4-iobroker Caught by controller[15]:     at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
                    2023-10-21 11:35:54.552  - error: host.raspberrypi4-iobroker Caught by controller[15]:     at Growatt._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7711:34)
                    2023-10-21 11:35:54.552  - error: host.raspberrypi4-iobroker Caught by controller[15]:     at runNextTicks (node:internal/process/task_queues:60:5)
                    2023-10-21 11:35:54.552  - error: host.raspberrypi4-iobroker Caught by controller[15]:     at processImmediate (node:internal/timers:447:9)
                    2023-10-21 11:35:54.552  - error: host.raspberrypi4-iobroker Caught by controller[15]: 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:
                    2023-10-21 11:35:54.552  - error: host.raspberrypi4-iobroker Caught by controller[15]: Error: DB closed
                    2023-10-21 11:35:54.552  - error: host.raspberrypi4-iobroker Caught by controller[15]:     at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
                    2023-10-21 11:35:54.552  - error: host.raspberrypi4-iobroker Caught by controller[15]:     at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
                    2023-10-21 11:35:54.552  - error: host.raspberrypi4-iobroker Caught by controller[15]:     at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
                    2023-10-21 11:35:54.552  - error: host.raspberrypi4-iobroker Caught by controller[15]:     at Growatt._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7711:34)
                    2023-10-21 11:35:54.552  - error: host.raspberrypi4-iobroker Caught by controller[15]:     at runNextTicks (node:internal/process/task_queues:60:5)
                    2023-10-21 11:35:54.553  - error: host.raspberrypi4-iobroker Caught by controller[15]:     at processImmediate (node:internal/timers:447:9)
                    2023-10-21 11:35:54.553  - error: host.raspberrypi4-iobroker Caught by controller[15]: 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:
                    2023-10-21 11:35:54.553  - error: host.raspberrypi4-iobroker Caught by controller[15]: Error: DB closed
                    2023-10-21 11:35:54.553  - error: host.raspberrypi4-iobroker Caught by controller[15]:     at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
                    2023-10-21 11:35:54.553  - error: host.raspberrypi4-iobroker Caught by controller[15]:     at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
                    2023-10-21 11:35:54.553  - error: host.raspberrypi4-iobroker Caught by controller[15]:     at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
                    2023-10-21 11:35:54.553  - error: host.raspberrypi4-iobroker Caught by controller[15]:     at Growatt._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7711:34)
                    2023-10-21 11:35:54.553  - error: host.raspberrypi4-iobroker Caught by controller[15]:     at runNextTicks (node:internal/process/task_queues:60:5)
                    2023-10-21 11:35:54.553  - error: host.raspberrypi4-iobroker Caught by controller[15]:     at processImmediate (node:internal/timers:447:9)
                    2023-10-21 11:35:54.553  - error: host.raspberrypi4-iobroker Caught by controller[15]: 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:
                    2023-10-21 11:35:54.553  - error: host.raspberrypi4-iobroker Caught by controller[15]: Error: DB closed
                    2023-10-21 11:35:54.553  - error: host.raspberrypi4-iobroker Caught by controller[15]:     at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
                    2023-10-21 11:35:54.554  - error: host.raspberrypi4-iobroker Caught by controller[15]:     at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
                    2023-10-21 11:35:54.554  - error: host.raspberrypi4-iobroker Caught by controller[15]:     at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
                    2023-10-21 11:35:54.554  - error: host.raspberrypi4-iobroker Caught by controller[15]:     at Growatt._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7711:34)
                    2023-10-21 11:35:54.554  - error: host.raspberrypi4-iobroker Caught by controller[15]:     at runNextTicks (node:internal/process/task_queues:60:5)
                    2023-10-21 11:35:54.554  - error: host.raspberrypi4-iobroker Caught by controller[15]:     at processImmediate (node:internal/timers:447:9)
                    2023-10-21 11:35:54.554  - error: host.raspberrypi4-iobroker Caught by controller[15]: 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:
                    2023-10-21 11:35:54.554  - error: host.raspberrypi4-iobroker Caught by controller[15]: Error: DB closed
                    2023-10-21 11:35:54.554  - error: host.raspberrypi4-iobroker Caught by controller[15]:     at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
                    2023-10-21 11:35:54.554  - error: host.raspberrypi4-iobroker Caught by controller[15]:     at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
                    2023-10-21 11:35:54.554  - error: host.raspberrypi4-iobroker Caught by controller[15]:     at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
                    2023-10-21 11:35:54.554  - error: host.raspberrypi4-iobroker Caught by controller[15]:     at Growatt._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7711:34)
                    2023-10-21 11:35:54.554  - error: host.raspberrypi4-iobroker Caught by controller[15]:     at runNextTicks (node:internal/process/task_queues:60:5)
                    2023-10-21 11:35:54.555  - error: host.raspberrypi4-iobroker Caught by controller[15]:     at processImmediate (node:internal/timers:447:9)
                    2023-10-21 11:35:54.555  - error: host.raspberrypi4-iobroker Caught by controller[15]: 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:
                    2023-10-21 11:35:54.555  - error: host.raspberrypi4-iobroker Caught by controller[15]: Error: DB closed
                    2023-10-21 11:35:54.555  - error: host.raspberrypi4-iobroker Caught by controller[15]:     at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
                    2023-10-21 11:35:54.555  - error: host.raspberrypi4-iobroker Caught by controller[15]:     at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
                    2023-10-21 11:35:54.555  - error: host.raspberrypi4-iobroker Caught by controller[15]:     at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
                    2023-10-21 11:35:54.555  - error: host.raspberrypi4-iobroker Caught by controller[15]:     at Growatt._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7711:34)
                    2023-10-21 11:35:54.555  - error: host.raspberrypi4-iobroker Caught by controller[15]:     at runNextTicks (node:internal/process/task_queues:60:5)
                    2023-10-21 11:35:54.555  - error: host.raspberrypi4-iobroker Caught by controller[15]:     at processImmediate (node:internal/timers:447:9)
                    2023-10-21 11:35:54.555  - error: host.raspberrypi4-iobroker Caught by controller[15]: 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:
                    2023-10-21 11:35:54.555  - error: host.raspberrypi4-iobroker Caught by controller[15]: Error: DB closed
                    2023-10-21 11:35:54.555  - error: host.raspberrypi4-iobroker Caught by controller[15]:     at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
                    2023-10-21 11:35:54.556  - error: host.raspberrypi4-iobroker Caught by controller[15]:     at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
                    2023-10-21 11:35:54.556  - error: host.raspberrypi4-iobroker Caught by controller[15]:     at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
                    2023-10-21 11:35:54.556  - error: host.raspberrypi4-iobroker Caught by controller[15]:     at Growatt._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7711:34)
                    2023-10-21 11:35:54.556  - error: host.raspberrypi4-iobroker Caught by controller[15]:     at runNextTicks (node:internal/process/task_queues:60:5)
                    2023-10-21 11:35:54.556  - error: host.raspberrypi4-iobroker Caught by controller[15]:     at processImmediate (node:internal/timers:447:9)
                    2023-10-21 11:35:54.556  - error: host.raspberrypi4-iobroker Caught by controller[15]: 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:
                    2023-10-21 11:35:54.556  - error: host.raspberrypi4-iobroker Caught by controller[15]: Error: DB closed
                    2023-10-21 11:35:54.556  - error: host.raspberrypi4-iobroker Caught by controller[15]:     at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
                    2023-10-21 11:35:54.556  - error: host.raspberrypi4-iobroker Caught by controller[15]:     at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
                    2023-10-21 11:35:54.556  - error: host.raspberrypi4-iobroker Caught by controller[15]:     at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
                    2023-10-21 11:35:54.557  - error: host.raspberrypi4-iobroker Caught by controller[15]:     at Growatt._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7711:34)
                    2023-10-21 11:35:54.557  - error: host.raspberrypi4-iobroker Caught by controller[15]:     at runNextTicks (node:internal/process/task_queues:60:5)
                    2023-10-21 11:35:54.557  - error: host.raspberrypi4-iobroker Caught by controller[15]:     at processImmediate (node:internal/timers:447:9)
                    2023-10-21 11:35:54.557  - error: host.raspberrypi4-iobroker Caught by controller[15]: 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:
                    2023-10-21 11:35:54.557  - error: host.raspberrypi4-iobroker Caught by controller[15]: Error: DB closed
                    2023-10-21 11:35:54.557  - error: host.raspberrypi4-iobroker Caught by controller[15]:     at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
                    2023-10-21 11:35:54.557  - error: host.raspberrypi4-iobroker Caught by controller[15]:     at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
                    2023-10-21 11:35:54.557  - error: host.raspberrypi4-iobroker Caught by controller[15]:     at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
                    
                    
                    

                    das ist nur ein kleiner Ausug, bekomme es nicht alles in eine Nachricht
                    da scheint noch mehr probleme zu geben

                    Homoran 1 Reply Last reply Reply Quote 0
                    • Homoran
                      Homoran Global Moderator Administrators @Spidermike last edited by

                      @Spidermike
                      das sind ja mehrere Einträge innerhalb einer Millisekunde.

                      ich kann da nichts zuordnen, nur

                      @spidermike sagte in ioBroker extrem langsam:

                      Growatt._setState

                      bleibt es wenn du den Adapter deaktivierst?

                      S 1 Reply Last reply Reply Quote 0
                      • S
                        Spidermike @Homoran last edited by

                        @homoran sagte in ioBroker extrem langsam:

                        @Spidermike
                        das sind ja mehrere Einträge innerhalb einer Millisekunde.

                        ich kann da nichts zuordnen, nur

                        @spidermike sagte in ioBroker extrem langsam:

                        Growatt._setState

                        bleibt es wenn du den Adapter deaktivierst?

                        es war kurz nach einen neustart befehl "sudo reboot" weil nur dadurch bebomme ich dann relativ schnellen zugriff auf den iobroker

                        ? 1 Reply Last reply Reply Quote 0
                        • ?
                          A Former User @Spidermike last edited by

                          @spidermike sagte in ioBroker extrem langsam:

                          es war kurz nach einen neustart befehl "sudo reboot" weil nur dadurch bebomme ich dann relativ schnellen zugriff auf den iobroker

                          Moin,

                          meine Fantasie geht mal wieder mit mir durch, aber kann man den RasPI nicht nach einem Reboot, beim Neustart in den abgesicherten Modus hochfahren, da sollten ja dann keine Applikationen starten.
                          Dann, einzeln die Adapter starten, die man zum Anmelden an den ioBroker braucht

                          # iob start <adapter>
                          

                          Dann alle anderen ausschalten und neu booten, dann wieder ein Adapter nach dem anderen starten und schauen wie sich die Kiste verhält.

                          VG
                          Bernd

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

                          Support us

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

                          500
                          Online

                          31.6k
                          Users

                          79.5k
                          Topics

                          1.3m
                          Posts

                          iobroker keine aktualisierung möglich langsam
                          8
                          95
                          5279
                          Loading More Posts
                          • Oldest to Newest
                          • Newest to Oldest
                          • Most Votes
                          Reply
                          • Reply as topic
                          Log in to reply
                          Community
                          Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                          The ioBroker Community 2014-2023
                          logo