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. Error/Bug
  4. IoBroker mach nur noch Probleme

NEWS

  • UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?
    apollon77A
    apollon77
    48
    3
    8.0k

  • Monatsrückblick – September 2025
    BluefoxB
    Bluefox
    13
    1
    1.8k

  • Neues Video "KI im Smart Home" - ioBroker plus n8n
    BluefoxB
    Bluefox
    15
    1
    2.0k

IoBroker mach nur noch Probleme

IoBroker mach nur noch Probleme

Scheduled Pinned Locked Moved Error/Bug
46 Posts 6 Posters 4.5k Views
  • 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.
  • E Offline
    E Offline
    Elektroman
    wrote on last edited by
    #33

    Hallo Dutchman,

    läuft aber nicht über Docker. Docker gibt es für mein NAS nicht.

    Ich bin nicht der Profi, ich glaube aber das NAS ist nicht mehr mein Problem

    1 Reply Last reply
    0
    • E Offline
      E Offline
      Elektroman
      wrote on last edited by
      #34

      Platform: linux

      Architecture: arm

      CPUs: 2

      Speed: 0 MHz

      Model: Marvell PJ4Bv7 Processor rev 2 (v7l)

      RAM: 1009.4 MB

      System uptime: 4 T. 08:33:45

      Node.js: v6.12.3

      NPM: 4.6.1

      adapters count: 198

      Uptime: 03:57:02

      1 Reply Last reply
      0
      • E Offline
        E Offline
        Elektroman
        wrote on last edited by
        #35

        Ich komme nicht mehr weiter

        Es kommen immer neue Fehlermeldungen dazu:

        m-rpc.3	2018-10-11 20:37:24.517	error	Error: You are sending too fast
        hm-rpc.3	2018-10-11 20:37:24.517	error	Error: You are sending too fast
        hm-rpc.3	2018-10-11 20:37:24.517	error	binrpc -> setValue ["1","ON_TIME",30] FLOAT
        hm-rpc.3	2018-10-11 20:37:24.517	error	binrpc -> setValue ["1","ON_TIME",30] FLOAT
        hm-rpc.3	2018-10-11 20:37:24.517	error	binrpc -> setValue ["1","ON_TIME",30] FLOAT
        hm-rpc.3	2018-10-11 20:37:24.517	error	Error: You are sending too fast
        hm-rpc.3	2018-10-11 20:37:24.517	error	Error: You are sending too fast
        hm-rpc.3	2018-10-11 20:37:24.516	error	Error: You are sending too fast
        hm-rpc.3	2018-10-11 20:37:24.515	error	binrpc -> setValue ["1","STATE",true] BOOL
        hm-rpc.3	2018-10-11 20:37:24.515	error	binrpc -> setValue ["1","STATE",true] BOOL
        hm-rpc.3	2018-10-11 20:37:24.515	error	binrpc -> setValue ["1","STATE",true] BOOL
        hm-rpc.3	2018-10-11 20:37:24.515	error	Error: You are sending too fast
        hm-rpc.3	2018-10-11 20:37:24.515	error	Error: You are sending too fast
        hm-rpc.3	2018-10-11 20:37:24.515	error	Error: You are sending too fast
        hm-rpc.3	2018-10-11 20:37:24.515	error	binrpc -> setValue ["1","ON_TIME",30] FLOAT
        hm-rpc.3	2018-10-11 20:37:24.515	error	binrpc -> setValue ["1","ON_TIME",30] FLOAT
        hm-rpc.3	2018-10-11 20:37:24.514	error	binrpc -> setValue ["1","ON_TIME",30] FLOAT
        hm-rpc.3	2018-10-11 20:37:24.514	error	Error: You are sending too fast
        hm-rpc.3	2018-10-11 20:37:24.514	error	Error: You are sending too fast
        hm-rpc.3	2018-10-11 20:37:24.514	error	Error: You are sending too fast
        hm-rpc.3	2018-10-11 20:37:24.514	error	binrpc -> setValue ["1","STATE",true] BOOL
        hm-rpc.3	2018-10-11 20:37:24.514	error	binrpc -> setValue ["1","STATE",true] BOOL
        hm-rpc.3	2018-10-11 20:37:24.514	error	binrpc -> setValue ["1","STATE",true] BOOL
        hm-rpc.3	2018-10-11 20:37:24.514	error	Error: You are sending too fast
        hm-rpc.3	2018-10-11 20:37:24.513	error	Error: You are sending too fast
        hm-rpc.3	2018-10-11 20:37:24.513	error	Error: You are sending too fast
        hm-rpc.3	2018-10-11 20:37:24.513	error	binrpc -> setValue ["1","ON_TIME",30] FLOAT
        
        1 Reply Last reply
        0
        • E Offline
          E Offline
          Elektroman
          wrote on last edited by
          #36
          host.ioBroker-Pi3-slave-sw	2018-10-11 20:38:17.429	error	instance system.adapter.web.0 terminated with code 7 (Adapter already running)
          host.ioBroker-Pi3-slave-sw	2018-10-11 20:38:17.167	info	Restart adapter system.adapter.hm-rpc.0 because enabled
          host.ioBroker-Pi3-slave-sw	2018-10-11 20:38:17.167	error	instance system.adapter.hm-rpc.0 terminated with code 7 (Adapter already running)
          host.ioBroker-Pi3-slave-sw	2018-10-11 20:38:17.043	info	Restart adapter system.adapter.hm-rega.0 because enabled
          host.ioBroker-Pi3-slave-sw	2018-10-11 20:38:17.042	error	instance system.adapter.hm-rega.0 terminated with code 7 (Adapter already running)
          host.ioBroker-Pi3-slave-sw	2018-10-11 20:38:14.197	info	Restart adapter system.adapter.javascript.1 because enabled
          host.ioBroker-Pi3-slave-sw	2018-10-11 20:38:14.196	error	instance system.adapter.javascript.1 terminated with code 7 (Adapter already running)
          host.ioBroker-Pi3-slave-sw	2018-10-11 20:38:16.648	info	Restart adapter system.adapter.javascript.2 because enabled
          host.ioBroker-Pi3-slave-sw	2018-10-11 20:38:16.646	error	instance system.adapter.javascript.2 terminated with code 7 (Adapter already running)
          
          1 Reply Last reply
          0
          • apollon77A Online
            apollon77A Online
            apollon77
            wrote on last edited by
            #37

            @Elektroman:

            Hallo,

            was soll ich sagen, die Ram Probleme sind weg.

            Ich habe aber leider weiterhin Adapter die nicht mehr funktionieren u.a. "s7" bzw. Adapter die immer mal wieder neu starten (grün-rot-grün)

            host.raspberrypi	2018-10-11 18:39:59.376	error	instance system.adapter.s7.0 terminated with code 0 (OK)
            host.raspberrypi	2018-10-11 18:39:59.376	error	Caught by controller[0]: at Module._compile (module.js:577:32)
            host.raspberrypi	2018-10-11 18:39:59.376	error	Caught by controller[0]: at Object. <anonymous>(/opt/iobroker/node_modules/iobroker.s7/node_modules/node-snap7/lib/node-snap7.js:9:45)
            host.raspberrypi	2018-10-11 18:39:59.375	error	Caught by controller[0]: at bindings (/opt/iobroker/node_modules/iobroker.s7/node_modules/node-snap7/node_modules/bindings/bindings.js:76:44)
            host.raspberrypi	2018-10-11 18:39:59.375	error	Caught by controller[0]: at require (internal/module.js:20:19)
            host.raspberrypi	2018-10-11 18:39:59.375	error	Caught by controller[0]: at Module.require (module.js:504:17)
            host.raspberrypi	2018-10-11 18:39:59.374	error	Caught by controller[0]: at Function.Module._load (module.js:445:3)
            host.raspberrypi	2018-10-11 18:39:59.374	error	Caught by controller[0]: at tryModuleLoad (module.js:453:12)
            host.raspberrypi	2018-10-11 18:39:59.374	error	Caught by controller[0]: at Module.load (module.js:494:32)
            host.raspberrypi	2018-10-11 18:39:59.373	error	Caught by controller[0]: at Object.Module._extensions..node (module.js:604:18)
            host.raspberrypi	2018-10-11 18:39:59.373	error	Caught by controller[0]: at Error (native)
            host.raspberrypi	2018-10-11 18:39:59.372	error	Caught by controller[0]: Error: Module version mismatch. Expected 48, got 46.</anonymous>
            ```` `  
            

            Kann es sein das du nodejs Update gemacht hast?

            Betroffenen Adapter Neu installieren sollte das fixen.

            Oder in das Verzeichnis des Adapters in node_modules und npm rebuild eingeben.

            Gesendet vom Handy …

            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
            • apollon77A Online
              apollon77A Online
              apollon77
              wrote on last edited by
              #38

              @Elektroman:

              Ich komme nicht mehr weiter

              Es kommen immer neue Fehlermeldungen dazu:

              m-rpc.3	2018-10-11 20:37:24.517	error	Error: You are sending too fast
              hm-rpc.3	2018-10-11 20:37:24.517	error	Error: You are sending too fast
              hm-rpc.3	2018-10-11 20:37:24.517	error	binrpc -> setValue ["1","ON_TIME",30] FLOAT
              hm-rpc.3	2018-10-11 20:37:24.517	error	binrpc -> setValue ["1","ON_TIME",30] FLOAT
              hm-rpc.3	2018-10-11 20:37:24.517	error	binrpc -> setValue ["1","ON_TIME",30] FLOAT
              hm-rpc.3	2018-10-11 20:37:24.517	error	Error: You are sending too fast
              hm-rpc.3	2018-10-11 20:37:24.517	error	Error: You are sending too fast
              hm-rpc.3	2018-10-11 20:37:24.516	error	Error: You are sending too fast
              hm-rpc.3	2018-10-11 20:37:24.515	error	binrpc -> setValue ["1","STATE",true] BOOL
              hm-rpc.3	2018-10-11 20:37:24.515	error	binrpc -> setValue ["1","STATE",true] BOOL
              hm-rpc.3	2018-10-11 20:37:24.515	error	binrpc -> setValue ["1","STATE",true] BOOL
              hm-rpc.3	2018-10-11 20:37:24.515	error	Error: You are sending too fast
              hm-rpc.3	2018-10-11 20:37:24.515	error	Error: You are sending too fast
              hm-rpc.3	2018-10-11 20:37:24.515	error	Error: You are sending too fast
              hm-rpc.3	2018-10-11 20:37:24.515	error	binrpc -> setValue ["1","ON_TIME",30] FLOAT
              hm-rpc.3	2018-10-11 20:37:24.515	error	binrpc -> setValue ["1","ON_TIME",30] FLOAT
              hm-rpc.3	2018-10-11 20:37:24.514	error	binrpc -> setValue ["1","ON_TIME",30] FLOAT
              hm-rpc.3	2018-10-11 20:37:24.514	error	Error: You are sending too fast
              hm-rpc.3	2018-10-11 20:37:24.514	error	Error: You are sending too fast
              hm-rpc.3	2018-10-11 20:37:24.514	error	Error: You are sending too fast
              hm-rpc.3	2018-10-11 20:37:24.514	error	binrpc -> setValue ["1","STATE",true] BOOL
              hm-rpc.3	2018-10-11 20:37:24.514	error	binrpc -> setValue ["1","STATE",true] BOOL
              hm-rpc.3	2018-10-11 20:37:24.514	error	binrpc -> setValue ["1","STATE",true] BOOL
              hm-rpc.3	2018-10-11 20:37:24.514	error	Error: You are sending too fast
              hm-rpc.3	2018-10-11 20:37:24.513	error	Error: You are sending too fast
              hm-rpc.3	2018-10-11 20:37:24.513	error	Error: You are sending too fast
              hm-rpc.3	2018-10-11 20:37:24.513	error	binrpc -> setValue ["1","ON_TIME",30] FLOAT
              ```` `  
              

              Welches deiner Skripte setzt diese States? Dann checke diese Skripte. Scheinbar läuft da was Amok und sendet viel zu schnell Kommandos an hm-rpc.3. Und genau so ein Skript Problem kann die Ursache für „reconnection to dB“ sein.

              Gesendet vom Handy …

              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
              • apollon77A Online
                apollon77A Online
                apollon77
                wrote on last edited by
                #39

                @Elektroman:

                host.ioBroker-Pi3-slave-sw	2018-10-11 20:38:17.429	error	instance system.adapter.web.0 terminated with code 7 (Adapter already running)
                host.ioBroker-Pi3-slave-sw	2018-10-11 20:38:17.167	info	Restart adapter system.adapter.hm-rpc.0 because enabled
                host.ioBroker-Pi3-slave-sw	2018-10-11 20:38:17.167	error	instance system.adapter.hm-rpc.0 terminated with code 7 (Adapter already running)
                host.ioBroker-Pi3-slave-sw	2018-10-11 20:38:17.043	info	Restart adapter system.adapter.hm-rega.0 because enabled
                host.ioBroker-Pi3-slave-sw	2018-10-11 20:38:17.042	error	instance system.adapter.hm-rega.0 terminated with code 7 (Adapter already running)
                host.ioBroker-Pi3-slave-sw	2018-10-11 20:38:14.197	info	Restart adapter system.adapter.javascript.1 because enabled
                host.ioBroker-Pi3-slave-sw	2018-10-11 20:38:14.196	error	instance system.adapter.javascript.1 terminated with code 7 (Adapter already running)
                host.ioBroker-Pi3-slave-sw	2018-10-11 20:38:16.648	info	Restart adapter system.adapter.javascript.2 because enabled
                host.ioBroker-Pi3-slave-sw	2018-10-11 20:38:16.646	error	instance system.adapter.javascript.2 terminated with code 7 (Adapter already running)
                ```` `  
                

                Siehe letzter Post. Ich tippe darauf das bei dir irgend ein Skript Müll baut und das der verursacher ist.

                Gesendet vom Handy …

                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
                • E Offline
                  E Offline
                  Elektroman
                  wrote on last edited by
                  #40

                  Ok, vielen Dank für die schnelle Hilfe

                  Ich schaue morgen mal weiter.

                  Ich habe für heute die Nase voll. Ich drehe mich jetzt schon seit Wochen im Kreis

                  1 Reply Last reply
                  0
                  • E Offline
                    E Offline
                    Elektroman
                    wrote on last edited by
                    #41

                    @apollon77:

                    @Elektroman:

                    Hallo,

                    was soll ich sagen, die Ram Probleme sind weg.

                    Ich habe aber leider weiterhin Adapter die nicht mehr funktionieren u.a. "s7" bzw. Adapter die immer mal wieder neu starten (grün-rot-grün)

                    host.raspberrypi	2018-10-11 18:39:59.376	error	instance system.adapter.s7.0 terminated with code 0 (OK)
                    host.raspberrypi	2018-10-11 18:39:59.376	error	Caught by controller[0]: at Module._compile (module.js:577:32)
                    host.raspberrypi	2018-10-11 18:39:59.376	error	Caught by controller[0]: at Object. <anonymous>(/opt/iobroker/node_modules/iobroker.s7/node_modules/node-snap7/lib/node-snap7.js:9:45)
                    host.raspberrypi	2018-10-11 18:39:59.375	error	Caught by controller[0]: at bindings (/opt/iobroker/node_modules/iobroker.s7/node_modules/node-snap7/node_modules/bindings/bindings.js:76:44)
                    host.raspberrypi	2018-10-11 18:39:59.375	error	Caught by controller[0]: at require (internal/module.js:20:19)
                    host.raspberrypi	2018-10-11 18:39:59.375	error	Caught by controller[0]: at Module.require (module.js:504:17)
                    host.raspberrypi	2018-10-11 18:39:59.374	error	Caught by controller[0]: at Function.Module._load (module.js:445:3)
                    host.raspberrypi	2018-10-11 18:39:59.374	error	Caught by controller[0]: at tryModuleLoad (module.js:453:12)
                    host.raspberrypi	2018-10-11 18:39:59.374	error	Caught by controller[0]: at Module.load (module.js:494:32)
                    host.raspberrypi	2018-10-11 18:39:59.373	error	Caught by controller[0]: at Object.Module._extensions..node (module.js:604:18)
                    host.raspberrypi	2018-10-11 18:39:59.373	error	Caught by controller[0]: at Error (native)
                    host.raspberrypi	2018-10-11 18:39:59.372	error	Caught by controller[0]: Error: Module version mismatch. Expected 48, got 46.</anonymous>
                    ```` `  
                    

                    Kann es sein das du nodejs Update gemacht hast?

                    Betroffenen Adapter Neu installieren sollte das fixen.

                    Oder in das Verzeichnis des Adapters in node_modules und npm rebuild eingeben.

                    Gesendet vom Handy … `

                    Beim Master oder bei einem der Slaves?

                    1 Reply Last reply
                    0
                    • apollon77A Online
                      apollon77A Online
                      apollon77
                      wrote on last edited by
                      #42

                      Na da Wonder s7 Adapter installiert ist der da meckert …

                      Gesendet vom Handy ...

                      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
                      • E Offline
                        E Offline
                        Elektroman
                        wrote on last edited by
                        #43

                        Neuer Tag neues Glück

                        Hallo,

                        ich habe beim Master und bei einem der zwei Slave das Verzeichnis "iobroker.s7" vorhanden? Habe es bei beiden es ausgeführt

                        1 Reply Last reply
                        0
                        • E Offline
                          E Offline
                          Elektroman
                          wrote on last edited by
                          #44

                          Es sind mehrere Adapter 😢

                          npm rebuild ergab keine Besserung

                          host.ioBroker-Pi3-slave-sw	2018-10-12 18:40:39.388	info	Restart adapter system.adapter.admin.0 because enabled
                          host.ioBroker-Pi3-slave-sw	2018-10-12 18:40:39.387	error	instance system.adapter.admin.0 terminated with code 7 (Adapter already running)
                          host.ioBroker-Pi3-slave-sw	2018-10-12 18:40:38.401	info	Restart adapter system.adapter.hm-rega.0 because enabled
                          host.ioBroker-Pi3-slave-sw	2018-10-12 18:40:38.401	error	instance system.adapter.hm-rega.0 terminated with code 7 (Adapter already running)
                          host.ioBroker-Pi3-slave-sw	2018-10-12 18:40:36.886	info	instance system.adapter.hm-rega.0 started with pid 3386
                          host.ioBroker-Pi3-slave-sw	2018-10-12 18:40:36.439	info	instance system.adapter.admin.0 started with pid 3380
                          host.ioBroker-Pi3-slave-sw	2018-10-12 18:40:35.691	info	Restart adapter system.adapter.hm-rpc.0 because enabled
                          
                          1 Reply Last reply
                          0
                          • apollon77A Online
                            apollon77A Online
                            apollon77
                            wrote on last edited by
                            #45

                            npm rebuild von s7 sorgt erstmal nur dafür das s7 wieder tut … alles andere ist was anderes.

                            Schau Die betroffenen Adapter an die mit error 7 gemeckert werden und kille die prozesse die da laufen oder mach nen reboot

                            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
                            • E Offline
                              E Offline
                              Elektroman
                              wrote on last edited by
                              #46

                              Ich bin gerade vorsichtig optimistisch. 😉

                              Habe vor ca. 3 Std einen reboot an allen Hosts durchgeführt, bis jetzt bleibt es ruhig

                              Hat doch was gebracht, danke dafür

                              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

                              407

                              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