Skip to content
  • Home
  • 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
ioBroker Logo

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. Error/Bug
  4. Zuverlässigkeit IOBROKER

NEWS

  • Monatsrückblick Januar/Februar 2026 ist online!
    BluefoxB
    Bluefox
    18
    1
    656

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

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

Zuverlässigkeit IOBROKER

Scheduled Pinned Locked Moved Solved Error/Bug
iobroker zuverlässigkeitmultiple fehler
156 Posts 10 Posters 11.9k Views 11 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.
  • ? A Former User

    du hast 3 hm-rpc Instanzen angelegt, deaktivere mal 0 und 1 davon... irgendwas beisst sich da, laut deiner Fehlerbeschreibung.

    Sicher dass dein iobroker Internetzugang hat?

    M Offline
    M Offline
    michaelxhoffmann
    wrote on last edited by
    #8

    @ilovegym ja einmal für die hm Geräte, einmal für die ip Geräte und einmal für die Cux D Geräte. Die laufen alle über die gleiche ipadresse. 🤔

    Homematic CCU2 - Raspberry Pi 4 - IOS (siri) - Amazon Echo 3rd Gen.

    1 Reply Last reply
    0
    • ? A Former User

      du hast 3 hm-rpc Instanzen angelegt, deaktivere mal 0 und 1 davon... irgendwas beisst sich da, laut deiner Fehlerbeschreibung.

      Sicher dass dein iobroker Internetzugang hat?

      M Offline
      M Offline
      michaelxhoffmann
      wrote on last edited by
      #9

      @ilovegym Internetzugang? Wie soll ich den denn gesperrt haben? 🤔 das läuft doch alles intern

      Homematic CCU2 - Raspberry Pi 4 - IOS (siri) - Amazon Echo 3rd Gen.

      ? 1 Reply Last reply
      0
      • M michaelxhoffmann

        @ilovegym Internetzugang? Wie soll ich den denn gesperrt haben? 🤔 das läuft doch alles intern

        ? Offline
        ? Offline
        A Former User
        wrote on last edited by
        #10

        @michaelxhoffmann nee, du hast u.a. den iot-adapter installiert, der will natuerlich raus.. deshalb steht der auf Fehler..

        1 Reply Last reply
        0
        • liv-in-skyL Offline
          liv-in-skyL Offline
          liv-in-sky
          wrote on last edited by
          #11

          kannst du mal das ganze log vom iobroker anhängen? /opt/iobroker/log

          nach einem gelösten Thread wäre es sinnvoll dies in der Überschrift des ersten Posts einzutragen [gelöst]-... Bitte benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat. Forum-Tools: PicPick https://picpick.app/en/download/ und ScreenToGif https://www.screentogif.com/downloads.html

          1 Reply Last reply
          0
          • liv-in-skyL Offline
            liv-in-skyL Offline
            liv-in-sky
            wrote on last edited by
            #12

            hast du mal gecheckt, ob in der fritzbox irgend welche fehlermeldungen sind

            nach einem gelösten Thread wäre es sinnvoll dies in der Überschrift des ersten Posts einzutragen [gelöst]-... Bitte benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat. Forum-Tools: PicPick https://picpick.app/en/download/ und ScreenToGif https://www.screentogif.com/downloads.html

            M 1 Reply Last reply
            0
            • liv-in-skyL Offline
              liv-in-skyL Offline
              liv-in-sky
              wrote on last edited by
              #13

              auf dem terminal

              cat /var/log/messages | grep "TCP" | more

              vielleicht kommt dann was interessantes

              nach einem gelösten Thread wäre es sinnvoll dies in der Überschrift des ersten Posts einzutragen [gelöst]-... Bitte benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat. Forum-Tools: PicPick https://picpick.app/en/download/ und ScreenToGif https://www.screentogif.com/downloads.html

              M 1 Reply Last reply
              0
              • M michaelxhoffmann

                Ich verzweifele und habe zwischenzeitlich auch keinen Bock mehr. Niegelnagelneu aufgesetzt, von der Picke auf und alles was ich bisher erreicht habe ist ein unzuverlässiges System das nur Fehler produziert

                hm-rpc.0 2019-02-27 16:19:01.516 error Ping error: Error: read ECONNRESET
                host.rock64 2019-02-27 16:18:57.054 error instance system.adapter.hm-rpc.1 terminated with code 0 (OK)
                Caught 2019-02-27 16:18:57.053 error by controller[0]: at TCP.onread (net.js:622:25) errno: 'ECONNRESET', code: 'ECONNRESET', syscall: 'read' }
                Caught 2019-02-27 16:18:57.052 error by controller[0]: { Error: read ECONNRESET
                hm-rpc.1 2019-02-27 16:18:56.993 error at TCP.onread (net.js:622:25)
                hm-rpc.1 2019-02-27 16:18:56.993 error Error: read ECONNRESET
                hm-rpc.1 2019-02-27 16:18:56.992 error uncaught exception: read ECONNRESET
                hm-rpc.1 2019-02-27 16:18:43.587 error init error: Error: response timeout
                hm-rpc.1 2019-02-27 16:18:08.570 error Ping error: Error: response timeout
                iot.0 2019-02-27 16:10:24.421 warn Invalid URL key. Status update is disabled: {"error":"Unsupported version"}
                iot.0 2019-02-27 16:10:24.419 error Cannot report device state: null
                host.rock64 2019-02-27 16:09:55.503 warn multihost service started on 0.0.0.0:50005
                Host 2019-02-27 16:09:55.320 warn on this system is not possible, because IP address is for states is 0.0.0.0
                iot.0 2019-02-27 16:06:53.440 error read ECONNRESET
                host.rock64 2019-02-27 16:01:44.563 error instance system.adapter.hm-rpc.0 terminated with code 0 (OK)
                Caught 2019-02-27 16:01:44.562 error by controller[0]: at TCP.onread (net.js:622:25) errno: 'ECONNRESET', code: 'ECONNRESET', syscall: 'read' }
                Caught 2019-02-27 16:01:44.561 error by controller[0]: { Error: read ECONNRESET
                hm-rpc.0 2019-02-27 16:01:44.490 error at TCP.onread (net.js:622:25)
                hm-rpc.0 2019-02-27 16:01:44.490 error Error: read ECONNRESET
                hm-rpc.0 2019-02-27 16:01:44.489 error uncaught exception: read ECONNRESET
                hm-rpc.0 2019-02-27 16:01:32.123 error init error: Error: response timeout
                hm-rpc.0 2019-02-27 16:00:57.111 error Ping error: Error: response timeout
                host.rock64 2019-02-27 15:58:49.901 error instance system.adapter.hm-rpc.0 terminated with code 0 (OK)
                Caught 2019-02-27 15:58:49.900 error by controller[0]: at TCP.onread (net.js:622:25) errno: 'ECONNRESET', code: 'ECONNRESET', syscall: 'read' }
                Caught 2019-02-27 15:58:49.900 error by controller[0]: { Error: read ECONNRESET
                hm-rpc.0 2019-02-27 15:58:49.836 error at TCP.onread (net.js:622:25)
                hm-rpc.0 2019-02-27 15:58:49.836 error Error: read ECONNRESET
                hm-rpc.0 2019-02-27 15:58:49.832 error uncaught exception: read ECONNRESET
                host.rock64 2019-02-27 15:58:47.243 error instance system.adapter.hm-rpc.1 terminated with code 0 (OK)
                Caught 2019-02-27 15:58:47.242 error by controller[0]: at TCP.onread (net.js:622:25) errno: 'ECONNRESET', code: 'ECONNRESET', syscall: 'read' }
                Caught 2019-02-27 15:58:47.242 error by controller[0]: { Error: read ECONNRESET
                hm-rpc.1 2019-02-27 15:58:47.202 error at TCP.onread (net.js:622:25)
                hm-rpc.1 2019-02-27 15:58:47.202 error Error: read ECONNRESET
                hm-rpc.1 2019-02-27 15:58:47.201 error uncaught exception: read ECONNRESET
                hm-rpc.1 2019-02-27 15:58:34.872 error init error: Error: response timeout
                hm-rpc.0 2019-02-27 15:58:28.625 error Ping error: Error: response timeout
                hm-rpc.1 2019-02-27 15:57:59.856 error Ping error: Error: response timeout

                Dabei habe ich noch nicht mal viele Adapter. Aber selbst die wenigen funktionieren nicht mal ansatzweise zuverlässig. Jetzt meine Frage: Ich glaube nicht dass beide meiner MiniPC defekt sind, auch bezweifele ich dass es irgendetwas mit den Netzteilen zu tun hat., die wurden zwischenzeitlich mehrfach getauscht. Mit ist auch nicht klar weshalb der Homematicadapter rumspinnt. Was bedeutet das Econnreset und diese zahllosen timeouts? Die folgenden Adapter habe ich installiert
                system.adapter.admin.0 : admin - enabled, port: 8081, bind: 0.0.0.0, run as: admin
                system.adapter.alexa2.0 : alexa2 - enabled
                system.adapter.backitup.0 : backitup - enabled
                system.adapter.broadlink2.0 : broadlink2 - enabled
                system.adapter.cloud.0 : cloud - enabled
                system.adapter.discovery.0 : discovery - enabled
                system.adapter.history.0 : history - enabled
                system.adapter.hm-rega.0 : hm-rega - enabled
                system.adapter.hm-rpc.0 : hm-rpc - enabled, port: 18701
                system.adapter.hm-rpc.1 : hm-rpc - enabled, port: 12001
                system.adapter.hm-rpc.2 : hm-rpc - enabled, port: 12010
                system.adapter.iot.0 : iot - enabled
                system.adapter.javascript.0 : javascript - enabled
                system.adapter.milight.0 : milight - enabled, port: 5987
                system.adapter.mobile.0 : mobile - enabled
                system.adapter.scenes.0 : scenes - enabled
                system.adapter.sql.0 : sql - enabled, port: 0
                system.adapter.tr-064.0 : tr-064 - enabled
                system.adapter.web.0 : web - enabled, port: 8082, bind: 0.0.0.0, run as: admin

                Wo kann ich noch ansetzen?

                HomoranH Do not disturb
                HomoranH Do not disturb
                Homoran
                Global Moderator Administrators
                wrote on last edited by
                #14

                @michaelxhoffmann sagte in Zuverlässigkeit IOBROKER:

                alles was ich bisher erreicht habe ist ein unzuverlässiges System das nur Fehler produziert

                Das zieht sich jetzt leider durch mehrere Threads.
                Wie können wir dir noch helfen?

                Die beiden aktuell Helfenden sind dir schon mal sehr empfohlen ;-)

                Wärst du nochmal bereit ganz langsam ganz von vorne zu beginnen - damit wir den Wurm endlich finden?

                Gruß
                Rainer

                kein Support per PN! - Fragen im Forum stellen -
                Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
                Das Forum freut sich über eine Spende. Benutzt dazu den Spendenbutton im Header. Danke!
                der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -

                M 1 Reply Last reply
                0
                • liv-in-skyL liv-in-sky

                  hast du mal gecheckt, ob in der fritzbox irgend welche fehlermeldungen sind

                  M Offline
                  M Offline
                  michaelxhoffmann
                  wrote on last edited by
                  #15

                  @liv-in-sky

                  undefined2019-02-27 15:46:22.147 - info: hm-rpc.0 binrpc -> listDevices 36
                  2019-02-27 15:46:22.174 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                  2019-02-27 15:46:47.247 - info: host.rock64 object change system.adapter.scenes.0
                  2019-02-27 15:49:52.697 - info: hm-rpc.0 binrpc -> listDevices 36
                  2019-02-27 15:49:52.716 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                  2019-02-27 15:51:40.573 - info: host.rock64 object change system.adapter.broadlink2.0
                  2019-02-27 15:51:40.576 - info: host.rock64 stopInstance system.adapter.broadlink2.0
                  2019-02-27 15:51:40.576 - info: host.rock64 stopInstance system.adapter.broadlink2.0 killing pid 1987
                  2019-02-27 15:51:40.687 - info: host.rock64 instance system.adapter.broadlink2.0 terminated with code 0 (OK)
                  2019-02-27 15:51:43.098 - info: host.rock64 instance system.adapter.broadlink2.0 started with pid 2434
                  2019-02-27 15:52:11.588 - info: host.rock64 object change system.adapter.broadlink2.0
                  2019-02-27 15:52:11.589 - info: host.rock64 stopInstance system.adapter.broadlink2.0
                  2019-02-27 15:52:11.590 - info: host.rock64 stopInstance system.adapter.broadlink2.0 killing pid 2434
                  2019-02-27 15:52:11.670 - info: host.rock64 instance system.adapter.broadlink2.0 terminated with code 0 (OK)
                  2019-02-27 15:52:14.121 - info: host.rock64 instance system.adapter.broadlink2.0 started with pid 2445
                  2019-02-27 15:53:23.132 - info: hm-rpc.0 binrpc -> listDevices 36
                  2019-02-27 15:53:23.181 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                  2019-02-27 15:56:53.583 - info: hm-rpc.0 binrpc -> listDevices 36
                  2019-02-27 15:56:53.613 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                  2019-02-27 15:57:59.856 - error: hm-rpc.1 Ping error: Error: response timeout
                  2019-02-27 15:57:59.857 - info: hm-rpc.1 Disconnected
                  2019-02-27 15:58:28.625 - error: hm-rpc.0 Ping error: Error: response timeout
                  2019-02-27 15:58:28.626 - info: hm-rpc.0 Disconnected
                  2019-02-27 15:58:34.872 - error: hm-rpc.1 init error: Error: response timeout
                  2019-02-27 15:58:47.201 - error: hm-rpc.1 uncaught exception: read ECONNRESET
                  2019-02-27 15:58:47.202 - error: hm-rpc.1 Error: read ECONNRESET
                  at TCP.onread (net.js:622:25)
                  2019-02-27 15:58:47.204 - info: hm-rpc.1 binrpc -> 192.168.178.188:2001/ init ["xmlrpc_bin://192.168.178.21:12001",""]
                  2019-02-27 15:58:47.242 - error: Caught by controller[0]: { Error: read ECONNRESET
                  2019-02-27 15:58:47.242 - error: Caught by controller[0]: at TCP.onread (net.js:622:25) errno: 'ECONNRESET', code: 'ECONNRESET', syscall: 'read' }
                  2019-02-27 15:58:47.243 - error: host.rock64 instance system.adapter.hm-rpc.1 terminated with code 0 (OK)
                  2019-02-27 15:58:47.243 - info: host.rock64 Restart adapter system.adapter.hm-rpc.1 because enabled
                  2019-02-27 15:58:49.832 - error: hm-rpc.0 uncaught exception: read ECONNRESET
                  2019-02-27 15:58:49.836 - error: hm-rpc.0 Error: read ECONNRESET
                  at TCP.onread (net.js:622:25)
                  2019-02-27 15:58:49.840 - info: hm-rpc.0 binrpc -> 192.168.178.188:8701/ init ["xmlrpc_bin://192.168.178.21:18701",""]
                  2019-02-27 15:58:49.856 - info: hm-rpc.0 terminating
                  2019-02-27 15:58:49.900 - error: Caught by controller[0]: { Error: read ECONNRESET
                  2019-02-27 15:58:49.900 - error: Caught by controller[0]: at TCP.onread (net.js:622:25) errno: 'ECONNRESET', code: 'ECONNRESET', syscall: 'read' }
                  2019-02-27 15:58:49.901 - error: host.rock64 instance system.adapter.hm-rpc.0 terminated with code 0 (OK)
                  2019-02-27 15:58:49.902 - info: host.rock64 Restart adapter system.adapter.hm-rpc.0 because enabled
                  2019-02-27 15:59:17.263 - info: host.rock64 instance system.adapter.hm-rpc.1 started with pid 2535
                  2019-02-27 15:59:18.750 - info: hm-rpc.1 starting. Version 1.9.7 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v8.15.0
                  2019-02-27 15:59:19.166 - info: hm-rpc.1 binrpc server is trying to listen on 192.168.178.21:12001
                  2019-02-27 15:59:19.168 - info: hm-rpc.1 binrpc client is trying to connect to 192.168.178.188:2001/ with ["xmlrpc_bin://192.168.178.21:12001","hm-rpc.1"]
                  2019-02-27 15:59:19.218 - info: hm-rpc.1 binrpc <- system.listMethods ["hm-rpc.1"]
                  2019-02-27 15:59:19.238 - info: hm-rpc.1 binrpc <- listDevices ["hm-rpc.1"]
                  2019-02-27 15:59:19.268 - info: hm-rpc.1 binrpc -> 67 devices
                  2019-02-27 15:59:19.444 - info: hm-rpc.1 Connected
                  2019-02-27 15:59:19.921 - info: host.rock64 instance system.adapter.hm-rpc.0 started with pid 2545
                  2019-02-27 15:59:21.313 - info: hm-rpc.0 starting. Version 1.9.7 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v8.15.0
                  2019-02-27 15:59:21.728 - info: hm-rpc.0 binrpc server is trying to listen on 192.168.178.21:18701
                  2019-02-27 15:59:21.730 - info: hm-rpc.0 binrpc client is trying to connect to 192.168.178.188:8701/ with ["xmlrpc_bin://192.168.178.21:18701","hm-rpc.0"]
                  2019-02-27 15:59:22.075 - info: hm-rpc.0 binrpc -> listDevices 36
                  2019-02-27 15:59:22.095 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                  2019-02-27 15:59:22.100 - info: hm-rpc.0 Connected
                  2019-02-27 15:59:59.074 - info: host.rock64 object change system.adapter.broadlink2.0
                  2019-02-27 15:59:59.075 - info: host.rock64 stopInstance system.adapter.broadlink2.0
                  2019-02-27 15:59:59.076 - info: host.rock64 stopInstance system.adapter.broadlink2.0 killing pid 2445
                  2019-02-27 15:59:59.125 - info: host.rock64 instance system.adapter.broadlink2.0 terminated with code 0 (OK)
                  2019-02-27 16:00:01.607 - info: host.rock64 instance system.adapter.broadlink2.0 started with pid 2567
                  2019-02-27 16:00:57.111 - error: hm-rpc.0 Ping error: Error: response timeout
                  2019-02-27 16:00:57.112 - info: hm-rpc.0 Disconnected
                  2019-02-27 16:01:32.123 - error: hm-rpc.0 init error: Error: response timeout
                  2019-02-27 16:01:44.489 - error: hm-rpc.0 uncaught exception: read ECONNRESET
                  2019-02-27 16:01:44.490 - error: hm-rpc.0 Error: read ECONNRESET
                  at TCP.onread (net.js:622:25)
                  2019-02-27 16:01:44.494 - info: hm-rpc.0 binrpc -> 192.168.178.188:8701/ init ["xmlrpc_bin://192.168.178.21:18701",""]
                  2019-02-27 16:01:44.512 - info: hm-rpc.0 terminating
                  2019-02-27 16:01:44.561 - error: Caught by controller[0]: { Error: read ECONNRESET
                  2019-02-27 16:01:44.562 - error: Caught by controller[0]: at TCP.onread (net.js:622:25) errno: 'ECONNRESET', code: 'ECONNRESET', syscall: 'read' }
                  2019-02-27 16:01:44.563 - error: host.rock64 instance system.adapter.hm-rpc.0 terminated with code 0 (OK)
                  2019-02-27 16:01:44.563 - info: host.rock64 Restart adapter system.adapter.hm-rpc.0 because enabled
                  2019-02-27 16:02:15.498 - info: host.rock64 instance system.adapter.hm-rpc.0 started with pid 2598
                  2019-02-27 16:02:16.904 - info: hm-rpc.0 starting. Version 1.9.7 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v8.15.0
                  2019-02-27 16:02:17.320 - info: hm-rpc.0 binrpc server is trying to listen on 192.168.178.21:18701
                  2019-02-27 16:02:17.322 - info: hm-rpc.0 binrpc client is trying to connect to 192.168.178.188:8701/ with ["xmlrpc_bin://192.168.178.21:18701","hm-rpc.0"]
                  2019-02-27 16:02:17.947 - info: hm-rpc.0 binrpc -> listDevices 36
                  2019-02-27 16:02:17.981 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                  2019-02-27 16:02:17.986 - info: hm-rpc.0 Connected
                  2019-02-27 16:03:24.987 - info: iot.0 Request devices
                  2019-02-27 16:03:38.348 - info: iot.0 Request devices
                  2019-02-27 16:03:38.510 - info: iot.0 Request V3 devices
                  2019-02-27 16:03:45.512 - info: iot.0 Request devices
                  2019-02-27 16:03:45.682 - info: iot.0 Request V3 devices
                  2019-02-27 16:03:51.196 - info: iot.0 Request devices
                  2019-02-27 16:03:51.635 - info: iot.0 Request V3 devices
                  2019-02-27 16:04:27.764 - info: iot.0 Request devices
                  2019-02-27 16:04:28.354 - info: iot.0 Request V3 devices
                  2019-02-27 16:04:29.743 - info: hm-rpc.2 xmlrpc <- listDevices ["hm-rpc.2"]
                  2019-02-27 16:04:29.764 - info: hm-rpc.2 xmlrpc -> 0 devices
                  2019-02-27 16:04:30.605 - info: hm-rpc.2 xmlrpc <- newDevices 67
                  2019-02-27 16:04:30.621 - info: hm-rpc.2 new HmIP devices/channels after filter: 0
                  2019-02-27 16:04:31.617 - info: alexa2.0 Alexa-Push-Connection disconnected - retry: Retry Connection in 5s
                  2019-02-27 16:04:32.813 - info: iot.0 Request devices
                  2019-02-27 16:04:32.963 - info: iot.0 Request V3 devices
                  2019-02-27 16:04:38.820 - info: iot.0 Request devices
                  2019-02-27 16:04:39.126 - info: iot.0 Request V3 devices
                  2019-02-27 16:04:46.223 - info: iot.0 Request devices
                  2019-02-27 16:04:46.665 - info: iot.0 Request V3 devices
                  2019-02-27 16:04:51.798 - info: iot.0 Request devices
                  2019-02-27 16:04:52.402 - info: iot.0 Request V3 devices
                  2019-02-27 16:04:58.093 - info: iot.0 Request devices
                  2019-02-27 16:04:58.237 - info: iot.0 Request V3 devices
                  2019-02-27 16:05:40.658 - info: alexa2.0 Alexa-Push-Connection established. Disable Polling
                  2019-02-27 16:05:48.549 - info: hm-rpc.0 binrpc -> listDevices 36
                  2019-02-27 16:05:48.565 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                  2019-02-27 16:06:53.440 - error: iot.0 read ECONNRESET
                  2019-02-27 16:06:53.442 - info: iot.0 Connection changed: disconnect
                  2019-02-27 16:06:53.442 - info: iot.0 Connection lost
                  2019-02-27 16:06:54.381 - info: iot.0 Request devices
                  2019-02-27 16:06:58.769 - info: iot.0 Connection changed: connect
                  2019-02-27 16:07:02.912 - info: cloud.0 Request devices
                  2019-02-27 16:09:18.950 - info: hm-rpc.0 binrpc -> listDevices 36
                  2019-02-27 16:09:18.984 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                  2019-02-27 16:09:51.654 - info: host.rock64 received SIGTERM
                  2019-02-27 16:09:51.659 - info: admin.0 terminating http server on port 8081
                  2019-02-27 16:09:51.667 - info: web.0 terminating http server on port 8082
                  2019-02-27 16:09:51.677 - info: hm-rpc.2 xmlrpc -> 192.168.178.188:2010/ init ["http://192.168.178.21:12010",""]
                  2019-02-27 16:09:51.669 - info: web.0 terminated http server on port 8082
                  2019-02-27 16:09:51.698 - info: cloud.0 Connection changed: io client disconnect
                  2019-02-27 16:09:51.704 - info: admin.0 terminating http server on port 8081
                  2019-02-27 16:09:51.699 - info: cloud.0 Connection lost
                  2019-02-27 16:09:51.737 - info: hm-rpc.0 binrpc -> 192.168.178.188:8701/ init ["xmlrpc_bin://192.168.178.21:18701",""]
                  2019-02-27 16:09:51.708 - info: hm-rpc.1 binrpc -> 192.168.178.188:2001/ init ["xmlrpc_bin://192.168.178.21:12001",""]
                  2019-02-27 16:09:51.748 - info: hm-rpc.0 Disconnected
                  2019-02-27 16:09:51.757 - info: hm-rpc.2 Disconnected
                  2019-02-27 16:09:51.777 - info: hm-rpc.1 Disconnected
                  2019-02-27 16:09:51.811 - info: host.rock64 instance system.adapter.admin.0 terminated with code 0 (OK)
                  2019-02-27 16:09:51.918 - info: hm-rpc.2 xmlrpc -> 192.168.178.188:2010/ init ["http://192.168.178.21:12010",""]
                  2019-02-27 16:09:51.950 - info: hm-rpc.1 binrpc -> 192.168.178.188:2001/ init ["xmlrpc_bin://192.168.178.21:12001",""]
                  2019-02-27 16:09:51.953 - info: hm-rpc.0 binrpc -> 192.168.178.188:8701/ init ["xmlrpc_bin://192.168.178.21:18701",""]
                  2019-02-27 16:09:51.822 - info: host.rock64 instance system.adapter.discovery.0 terminated with code 0 (OK)
                  2019-02-27 16:09:51.831 - info: host.rock64 instance system.adapter.alexa2.0 terminated with code 0 (OK)
                  2019-02-27 16:09:51.841 - info: host.rock64 instance system.adapter.web.0 terminated with code 0 (OK)
                  2019-02-27 16:09:51.850 - info: host.rock64 instance system.adapter.history.0 terminated with code 0 (OK)
                  2019-02-27 16:09:51.859 - info: host.rock64 instance system.adapter.iot.0 terminated with code 0 (OK)
                  2019-02-27 16:09:51.868 - info: host.rock64 instance system.adapter.tr-064.0 terminated with code 0 (OK)
                  2019-02-27 16:09:51.878 - info: host.rock64 instance system.adapter.hm-rega.0 terminated with code 0 (OK)
                  2019-02-27 16:09:51.887 - info: host.rock64 instance system.adapter.cloud.0 terminated with code 0 (OK)
                  2019-02-27 16:09:51.899 - info: host.rock64 instance system.adapter.milight.0 terminated with code 0 (OK)
                  2019-02-27 16:09:51.976 - info: host.rock64 instance system.adapter.hm-rpc.2 terminated with code 0 (OK)
                  2019-02-27 16:09:51.986 - info: host.rock64 instance system.adapter.broadlink2.0 terminated with code 0 (OK)
                  2019-02-27 16:09:51.998 - info: host.rock64 instance system.adapter.hm-rpc.0 terminated with code 0 (OK)
                  2019-02-27 16:09:52.007 - info: host.rock64 instance system.adapter.hm-rpc.1 terminated with code 0 (OK)
                  2019-02-27 16:09:52.018 - info: host.rock64 instance system.adapter.javascript.0 terminated with code 0 (OK)
                  2019-02-27 16:09:52.190 - info: host.rock64 instance system.adapter.backitup.0 terminated with code 0 (OK)
                  2019-02-27 16:09:52.190 - info: host.rock64 All instances are stopped.
                  2019-02-27 16:09:52.307 - info: host.rock64 terminated
                  2019-02-27 16:09:54.396 - info: host.rock64 iobroker.js-controller version 1.4.2 js-controller starting
                  2019-02-27 16:09:54.406 - info: host.rock64 Copyright (c) 2014-2018 bluefox, 2014 hobbyquaker
                  2019-02-27 16:09:54.407 - info: host.rock64 hostname: rock64, node: v8.15.0
                  2019-02-27 16:09:54.413 - info: host.rock64 ip addresses: 192.168.178.21 2003:eb:bbc6:2700:e739:6bbe:555e:ffa9 fe80::cd14:ce15:d5be:dcbb
                  2019-02-27 16:09:54.580 - info: host.rock64 inMem-states listening on port 9000
                  2019-02-27 16:09:55.270 - info: host.rock64 inMem-objects listening on port 9001
                  2019-02-27 16:09:55.304 - info: host.rock64 InMemoryDB connected
                  2019-02-27 16:09:55.320 - warn: Host on this system is not possible, because IP address is for states is 0.0.0.0
                  2019-02-27 16:09:55.346 - info: host.rock64 19 instances found
                  2019-02-27 16:09:55.383 - info: host.rock64 starting 17 instances
                  2019-02-27 16:09:55.456 - info: host.rock64 instance system.adapter.admin.0 started with pid 2660
                  2019-02-27 16:09:55.503 - warn: host.rock64 multihost service started on 0.0.0.0:50005
                  2019-02-27 16:09:58.063 - info: admin.0 starting. Version 3.5.10 in /opt/iobroker/node_modules/iobroker.admin, node: v8.15.0
                  2019-02-27 16:09:58.110 - info: admin.0 requesting all states
                  2019-02-27 16:09:58.114 - info: admin.0 requesting all objects
                  2019-02-27 16:09:58.117 - info: admin.0 Request actual repository...
                  2019-02-27 16:09:59.465 - info: host.rock64 instance system.adapter.discovery.0 started with pid 2678
                  2019-02-27 16:09:59.614 - info: admin.0 received all states
                  2019-02-27 16:10:01.221 - info: discovery.0 starting. Version 1.2.4 in /opt/iobroker/node_modules/iobroker.discovery, node: v8.15.0
                  2019-02-27 16:10:03.407 - info: host.rock64 instance system.adapter.alexa2.0 started with pid 2688
                  2019-02-27 16:10:03.477 - info: admin.0 received all objects
                  2019-02-27 16:10:03.774 - info: admin.0 http server listening on port 8081
                  2019-02-27 16:10:03.774 - info: admin.0 Use link "http://localhost:8081" to configure.
                  2019-02-27 16:10:03.900 - info: host.rock64 Update repository "default" under "http://download.iobroker.net/sources-dist.json"
                  2019-02-27 16:10:05.060 - info: alexa2.0 starting. Version 1.1.3 in /opt/iobroker/node_modules/iobroker.alexa2, node: v8.15.0
                  2019-02-27 16:10:05.749 - info: alexa2.0 Proxy IP not set, use first network interface (192.168.178.21) instead
                  2019-02-27 16:10:07.416 - info: host.rock64 instance system.adapter.web.0 started with pid 2698
                  2019-02-27 16:10:07.427 - info: admin.0 Repository received successfully.
                  2019-02-27 16:10:09.582 - info: web.0 starting. Version 2.4.1 in /opt/iobroker/node_modules/iobroker.web, node: v8.15.0
                  2019-02-27 16:10:10.239 - info: web.0 socket.io server listening on port 8082
                  2019-02-27 16:10:10.246 - info: web.0 http server listening on port 8082
                  2019-02-27 16:10:10.730 - info: alexa2.0 Alexa-Push-Connection established. Disable Polling
                  2019-02-27 16:10:11.500 - info: host.rock64 instance system.adapter.backitup.0 started with pid 2708
                  2019-02-27 16:10:13.254 - info: backitup.0 starting. Version 1.1.2 in /opt/iobroker/node_modules/iobroker.backitup, node: v8.15.0
                  2019-02-27 16:10:13.315 - info: backitup.0 [minimal] backup was activated at 02:00 every 1 day(s)
                  2019-02-27 16:10:13.359 - info: backitup.0 [total] backup was activated at 03:00 every 3 day(s)
                  2019-02-27 16:10:15.416 - info: host.rock64 instance system.adapter.history.0 started with pid 2725
                  2019-02-27 16:10:16.971 - info: history.0 starting. Version 1.8.6 in /opt/iobroker/node_modules/iobroker.history, node: v8.15.0
                  2019-02-27 16:10:19.411 - info: host.rock64 instance system.adapter.iot.0 started with pid 2735
                  2019-02-27 16:10:21.957 - info: iot.0 starting. Version 0.3.1 in /opt/iobroker/node_modules/iobroker.iot, node: v8.15.0
                  2019-02-27 16:10:21.999 - info: iot.0 Connecting with a18wym7vjdl22g.iot.eu-west-1.amazonaws.com
                  2019-02-27 16:10:23.411 - info: host.rock64 instance system.adapter.tr-064.0 started with pid 2749
                  2019-02-27 16:10:24.174 - info: iot.0 Connection changed: connect
                  2019-02-27 16:10:24.419 - error: iot.0 Cannot report device state: null
                  2019-02-27 16:10:24.421 - warn: iot.0 Invalid URL key. Status update is disabled: {"error":"Unsupported version"}
                  2019-02-27 16:10:25.526 - info: tr-064.0 starting. Version 0.4.18 in /opt/iobroker/node_modules/iobroker.tr-064, node: v8.15.0
                  2019-02-27 16:10:27.410 - info: host.rock64 instance system.adapter.hm-rpc.0 started with pid 2763
                  2019-02-27 16:10:29.018 - info: hm-rpc.0 starting. Version 1.9.7 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v8.15.0
                  2019-02-27 16:10:29.200 - info: iot.0 Request devices
                  2019-02-27 16:10:29.409 - info: hm-rpc.0 binrpc server is trying to listen on 192.168.178.21:18701
                  2019-02-27 16:10:29.412 - info: hm-rpc.0 binrpc client is trying to connect to 192.168.178.188:8701/ with ["xmlrpc_bin://192.168.178.21:18701","hm-rpc.0"]
                  2019-02-27 16:10:29.977 - info: hm-rpc.0 binrpc -> listDevices 36
                  2019-02-27 16:10:29.999 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                  2019-02-27 16:10:30.004 - info: hm-rpc.0 Connected
                  2019-02-27 16:10:31.409 - info: host.rock64 instance system.adapter.hm-rpc.1 started with pid 2773
                  2019-02-27 16:10:32.930 - info: hm-rpc.1 starting. Version 1.9.7 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v8.15.0
                  2019-02-27 16:10:33.312 - info: hm-rpc.1 binrpc server is trying to listen on 192.168.178.21:12001
                  2019-02-27 16:10:33.314 - info: hm-rpc.1 binrpc client is trying to connect to 192.168.178.188:2001/ with ["xmlrpc_bin://192.168.178.21:12001","hm-rpc.1"]
                  2019-02-27 16:10:33.358 - info: hm-rpc.1 binrpc <- system.listMethods ["hm-rpc.1"]
                  2019-02-27 16:10:33.374 - info: hm-rpc.1 binrpc <- listDevices ["hm-rpc.1"]
                  2019-02-27 16:10:33.394 - info: hm-rpc.1 binrpc -> 67 devices
                  2019-02-27 16:10:33.549 - info: hm-rpc.1 Connected
                  2019-02-27 16:10:35.423 - info: host.rock64 instance system.adapter.hm-rpc.2 started with pid 2783
                  2019-02-27 16:10:36.836 - info: hm-rpc.2 starting. Version 1.9.7 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v8.15.0
                  2019-02-27 16:10:37.251 - info: hm-rpc.2 xmlrpc server is trying to listen on 192.168.178.21:12010
                  2019-02-27 16:10:37.253 - info: hm-rpc.2 xmlrpc client is trying to connect to 192.168.178.188:2010/ with ["http://192.168.178.21:12010","hm-rpc.2"]
                  2019-02-27 16:10:37.349 - info: hm-rpc.2 Connected
                  2019-02-27 16:10:37.520 - info: hm-rpc.2 xmlrpc <- listDevices ["hm-rpc.2"]
                  2019-02-27 16:10:37.536 - info: hm-rpc.2 xmlrpc -> 0 devices
                  2019-02-27 16:10:39.412 - info: host.rock64 instance system.adapter.hm-rega.0 started with pid 2793
                  2019-02-27 16:10:39.530 - info: hm-rpc.2 xmlrpc <- newDevices 67
                  2019-02-27 16:10:39.553 - info: hm-rpc.2 new HmIP devices/channels after filter: 0
                  2019-02-27 16:10:41.482 - info: hm-rega.0 starting. Version 2.3.0 in /opt/iobroker/node_modules/iobroker.hm-rega, node: v8.15.0
                  2019-02-27 16:10:41.534 - info: hm-rega.0 subscribe hm-rpc.1.BidCoS-RF.50.PRESS_SHORT
                  2019-02-27 16:10:41.741 - info: hm-rega.0 ReGaHSS 192.168.178.188 up
                  2019-02-27 16:10:41.842 - info: hm-rega.0 time difference local-ccu 1s
                  2019-02-27 16:10:41.934 - info: hm-rega.0 added/updated 4 favorites to enum.favorites
                  2019-02-27 16:10:42.044 - info: hm-rega.0 added/updated functions to enum.functions
                  2019-02-27 16:10:42.116 - info: hm-rega.0 added/updated rooms to enum.rooms
                  2019-02-27 16:10:42.899 - info: hm-rega.0 got 45 programs
                  2019-02-27 16:10:43.029 - info: hm-rega.0 added/updated 45 programs
                  2019-02-27 16:10:43.030 - info: hm-rega.0 deleted 0 programs
                  2019-02-27 16:10:43.581 - info: host.rock64 instance system.adapter.javascript.0 started with pid 2803
                  2019-02-27 16:10:43.645 - info: hm-rega.0 got 15 variables
                  2019-02-27 16:10:43.816 - info: hm-rega.0 added/updated 15 variables
                  2019-02-27 16:10:43.816 - info: hm-rega.0 deleted 0 variables
                  2019-02-27 16:10:43.818 - info: hm-rega.0 request state values
                  2019-02-27 16:10:45.125 - info: hm-rega.0 got state values
                  2019-02-27 16:10:47.477 - info: host.rock64 instance system.adapter.cloud.0 started with pid 2809
                  2019-02-27 16:10:47.894 - info: javascript.0 starting. Version 4.1.5 in /opt/iobroker/node_modules/iobroker.javascript, node: v8.15.0
                  2019-02-27 16:10:47.925 - info: javascript.0 requesting all states
                  2019-02-27 16:10:47.929 - info: javascript.0 requesting all objects
                  2019-02-27 16:10:49.478 - info: javascript.0 received all states
                  2019-02-27 16:10:49.735 - info: cloud.0 starting. Version 2.6.2 in /opt/iobroker/node_modules/iobroker.cloud, node: v8.15.0
                  2019-02-27 16:10:49.898 - info: cloud.0 Connecting with https://iobroker.pro:10555 with "
                  2019-02-27 16:10:50.726 - info: cloud.0 Trying to connect as system.user.admin
                  2019-02-27 16:10:50.789 - info: cloud.0 Connection changed: connect
                  2019-02-27 16:10:50.960 - info: cloud.0 Connection not changed: was connected
                  2019-02-27 16:10:52.902 - info: javascript.0 received all objects
                  2019-02-27 16:10:55.413 - info: host.rock64 instance system.adapter.broadlink2.0 started with pid 2823
                  2019-02-27 16:10:59.422 - info: host.rock64 instance system.adapter.milight.0 started with pid 2833
                  2019-02-27 16:11:00.812 - info: milight.0 starting. Version 0.3.6 in /opt/iobroker/node_modules/iobroker.milight, node: v8.15.0
                  2019-02-27 16:14:00.757 - info: hm-rpc.0 binrpc -> listDevices 36
                  2019-02-27 16:14:00.777 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                  2019-02-27 16:14:04.676 - info: cloud.0 Request devices
                  2019-02-27 16:14:05.533 - info: cloud.0 Request devices
                  2019-02-27 16:16:06.336 - info: cloud.0 Request devices
                  2019-02-27 16:16:06.839 - info: cloud.0 Request V3 devices
                  2019-02-27 16:16:20.948 - info: cloud.0 Request devices
                  2019-02-27 16:16:21.151 - info: cloud.0 Request V3 devices
                  2019-02-27 16:17:31.477 - info: hm-rpc.0 binrpc -> listDevices 36
                  2019-02-27 16:17:31.505 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                  2019-02-27 16:18:08.570 - error: hm-rpc.1 Ping error: Error: response timeout
                  2019-02-27 16:18:08.571 - info: hm-rpc.1 Disconnected
                  2019-02-27 16:18:43.587 - error: hm-rpc.1 init error: Error: response timeout
                  2019-02-27 16:18:56.992 - error: hm-rpc.1 uncaught exception: read ECONNRESET
                  2019-02-27 16:18:56.993 - error: hm-rpc.1 Error: read ECONNRESET
                  at TCP.onread (net.js:622:25)
                  2019-02-27 16:18:56.995 - info: hm-rpc.1 binrpc -> 192.168.178.188:2001/ init ["xmlrpc_bin://192.168.178.21:12001",""]
                  2019-02-27 16:18:57.021 - info: hm-rpc.1 terminating
                  2019-02-27 16:18:57.052 - error: Caught by controller[0]: { Error: read ECONNRESET
                  2019-02-27 16:18:57.053 - error: Caught by controller[0]: at TCP.onread (net.js:622:25) errno: 'ECONNRESET', code: 'ECONNRESET', syscall: 'read' }
                  2019-02-27 16:18:57.054 - error: host.rock64 instance system.adapter.hm-rpc.1 terminated with code 0 (OK)
                  2019-02-27 16:18:57.054 - info: host.rock64 Restart adapter system.adapter.hm-rpc.1 because enabled
                  2019-02-27 16:19:01.516 - error: hm-rpc.0 Ping error: Error: read ECONNRESET
                  2019-02-27 16:19:01.517 - info: hm-rpc.0 Disconnected
                  2019-02-27 16:19:27.074 - info: host.rock64 instance system.adapter.hm-rpc.1 started with pid 2897
                  2019-02-27 16:19:28.451 - info: hm-rpc.1 starting. Version 1.9.7 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v8.15.0
                  2019-02-27 16:19:28.827 - info: hm-rpc.1 binrpc server is trying to listen on 192.168.178.21:12001
                  2019-02-27 16:19:28.829 - info: hm-rpc.1 binrpc client is trying to connect to 192.168.178.188:2001/ with ["xmlrpc_bin://192.168.178.21:12001","hm-rpc.1"]
                  2019-02-27 16:19:28.867 - info: hm-rpc.1 binrpc <- system.listMethods ["hm-rpc.1"]
                  2019-02-27 16:19:28.880 - info: hm-rpc.1 binrpc <- listDevices ["hm-rpc.1"]
                  2019-02-27 16:19:28.897 - info: hm-rpc.1 binrpc -> 67 devices
                  2019-02-27 16:19:29.045 - info: hm-rpc.1 Connected
                  2019-02-27 16:20:01.984 - info: hm-rpc.0 binrpc -> listDevices 36
                  2019-02-27 16:20:02.033 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                  2019-02-27 16:20:02.036 - info: hm-rpc.0 Connected
                  2019-02-27 16:23:32.435 - info: hm-rpc.0 binrpc -> listDevices 36
                  2019-02-27 16:23:32.455 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                  2019-02-27 16:27:02.873 - info: hm-rpc.0 binrpc -> listDevices 36
                  2019-02-27 16:27:02.942 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                  2019-02-27 16:30:33.628 - info: hm-rpc.0 binrpc -> listDevices 36
                  2019-02-27 16:30:33.653 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                  2019-02-27 16:34:04.065 - info: hm-rpc.0 binrpc -> listDevices 36
                  2019-02-27 16:34:04.135 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                  2019-02-27 16:37:34.797 - info: hm-rpc.0 binrpc -> listDevices 36
                  2019-02-27 16:37:34.820 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                  2019-02-27 16:41:05.443 - info: hm-rpc.0 binrpc -> listDevices 36
                  2019-02-27 16:41:05.582 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                  2019-02-27 16:44:36.013 - info: hm-rpc.0 binrpc -> listDevices 36
                  2019-02-27 16:44:36.027 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                  2019-02-27 16:48:06.663 - info: hm-rpc.0 binrpc -> listDevices 36
                  2019-02-27 16:48:06.728 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                  2019-02-27 16:51:37.349 - info: hm-rpc.0 binrpc -> listDevices 36
                  2019-02-27 16:51:37.363 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                  2019-02-27 16:55:08.082 - info: hm-rpc.0 binrpc -> listDevices 36
                  2019-02-27 16:55:08.130 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                  2019-02-27 16:55:51.217 - error: cloud.0 Socket error: Error: websocket error
                  2019-02-27 16:55:51.226 - info: cloud.0 Connection changed: transport error
                  2019-02-27 16:55:51.226 - info: cloud.0 Connection lost
                  2019-02-27 16:55:53.883 - error: tr-064.0 --- To use the callmonitor, enable connects to port 1012 on FritsBox by dialing #965 and restart this adapter
                  2019-02-27 16:55:53.886 - error: tr-064.0 Cannot start callmonitor: Error: connect ECONNREFUSED 192.168.178.1:1012
                  2019-02-27 16:55:53.887 - error: tr-064.0 Cannot start callmonitor: Error: connect ECONNREFUSED 192.168.178.1:1012
                  2019-02-27 16:56:17.039 - error: hm-rega.0 post request error: connect EHOSTUNREACH 192.168.178.188:8181
                  2019-02-27 16:56:17.040 - error: hm-rega.0 CCU 192.168.178.188 unreachable
                  2019-02-27 16:56:43.148 - error: hm-rpc.0 Ping error: Error: response timeout
                  2019-02-27 16:56:43.149 - info: hm-rpc.0 Disconnected
                  2019-02-27 16:56:47.066 - error: hm-rega.0 CCU 192.168.178.188 unreachable
                  2019-02-27 16:56:51.277 - error: cloud.0 Error while connecting to cloud: Error: websocket error
                  2019-02-27 16:56:51.310 - info: cloud.0 Trying to connect as system.user.admin
                  2019-02-27 16:57:13.551 - info: hm-rpc.0 binrpc -> listDevices 36
                  2019-02-27 16:57:13.577 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                  2019-02-27 16:57:13.579 - info: hm-rpc.0 Connected
                  2019-02-27 16:57:14.916 - error: hm-rega.0 Cannot parse answer for devices: undefined
                  2019-02-27 16:57:17.223 - info: hm-rega.0 ReGaHSS 192.168.178.188 up
                  2019-02-27 16:57:17.251 - info: hm-rega.0 time difference local-ccu 0s
                  2019-02-27 16:57:17.307 - info: hm-rega.0 added/updated 4 favorites to enum.favorites
                  2019-02-27 16:57:17.429 - info: hm-rega.0 added/updated functions to enum.functions
                  2019-02-27 16:57:17.481 - info: hm-rega.0 added/updated rooms to enum.rooms
                  2019-02-27 16:57:18.016 - info: hm-rega.0 got 45 programs
                  2019-02-27 16:57:18.069 - info: hm-rega.0 added/updated 45 programs
                  2019-02-27 16:57:18.070 - info: hm-rega.0 deleted 0 programs
                  2019-02-27 16:57:18.088 - info: hm-rega.0 got 15 variables
                  2019-02-27 16:57:18.154 - info: hm-rega.0 added/updated 15 variables
                  2019-02-27 16:57:18.155 - info: hm-rega.0 deleted 0 variables
                  2019-02-27 16:57:18.155 - info: hm-rega.0 request state values
                  2019-02-27 16:57:18.659 - info: hm-rega.0 got state values
                  2019-02-27 16:57:39.398 - error: cloud.0 Error while connecting to cloud: Error: websocket error
                  2019-02-27 16:57:51.287 - info: cloud.0 Trying to connect as system.user.admin
                  2019-02-27 16:57:56.652 - info: cloud.0 Connection changed: connect
                  2019-02-27 16:57:56.689 - info: cloud.0 Connection not changed: was connected
                  2019-02-27 16:58:10.802 - info: alexa2.0 Alexa-Push-Connection disconnected - retry: Retry Connection in 5s
                  2019-02-27 16:58:16.767 - info: alexa2.0 Alexa-Push-Connection established. Disable Polling
                  2019-02-27 16:58:40.820 - info: alexa2.0 Alexa-Push-Connection disconnected - retry: Retry Connection in 5s
                  2019-02-27 16:58:46.758 - info: alexa2.0 Alexa-Push-Connection established. Disable Polling
                  2019-02-27 17:00:24.503 - error: iot.0 read ECONNRESET
                  2019-02-27 17:00:24.505 - info: iot.0 Connection changed: disconnect
                  2019-02-27 17:00:24.506 - info: iot.0 Connection lost
                  2019-02-27 17:00:29.815 - info: iot.0 Connection changed: connect
                  2019-02-27 17:00:44.231 - info: hm-rpc.0 binrpc -> listDevices 36
                  2019-02-27 17:00:44.299 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                  2019-02-27 17:04:14.712 - info: hm-rpc.0 binrpc -> listDevices 36
                  2019-02-27 17:04:14.726 - info: hm-rpc.0 new CUxD devices/channels after filter: 0

                  Darf nicht mehr in die Message reinschreiben Aber das ist das komplette log

                  Homematic CCU2 - Raspberry Pi 4 - IOS (siri) - Amazon Echo 3rd Gen.

                  1 Reply Last reply
                  0
                  • HomoranH Homoran

                    @michaelxhoffmann sagte in Zuverlässigkeit IOBROKER:

                    alles was ich bisher erreicht habe ist ein unzuverlässiges System das nur Fehler produziert

                    Das zieht sich jetzt leider durch mehrere Threads.
                    Wie können wir dir noch helfen?

                    Die beiden aktuell Helfenden sind dir schon mal sehr empfohlen ;-)

                    Wärst du nochmal bereit ganz langsam ganz von vorne zu beginnen - damit wir den Wurm endlich finden?

                    Gruß
                    Rainer

                    M Offline
                    M Offline
                    michaelxhoffmann
                    wrote on last edited by
                    #16

                    @Homoran Naja ich habe ja ganz am anfang angefangen. Ich komme ja noch nicht mal aus dem Startblock raus .... Zum Glück bin ich zur Zeit im Krankenstand, sonbst hätte ich schon längst alles wieder verworfen.

                    Homematic CCU2 - Raspberry Pi 4 - IOS (siri) - Amazon Echo 3rd Gen.

                    HomoranH 1 Reply Last reply
                    0
                    • liv-in-skyL liv-in-sky

                      auf dem terminal

                      cat /var/log/messages | grep "TCP" | more

                      vielleicht kommt dann was interessantes

                      M Offline
                      M Offline
                      michaelxhoffmann
                      wrote on last edited by
                      #17

                      @liv-in-sky sagte in Zuverlässigkeit IOBROKER:

                      cat /var/log/messages | grep "TCP" | more

                      Feb 26 14:17:04 localhost kernel: [ 1.602100] TCP established hash table entries: 16384 (order: 5, 131072 bytes)
                      Feb 26 14:17:04 localhost kernel: [ 1.602347] TCP bind hash table entries: 16384 (order: 7, 524288 bytes)
                      Feb 26 14:17:04 localhost kernel: [ 1.603118] TCP: Hash tables configured (established 16384 bind 16384)
                      Feb 26 14:39:20 localhost kernel: [ 1.610033] TCP established hash table entries: 16384 (order: 5, 131072 bytes)
                      Feb 26 14:39:20 localhost kernel: [ 1.610281] TCP bind hash table entries: 16384 (order: 7, 524288 bytes)
                      Feb 26 14:39:20 localhost kernel: [ 1.611061] TCP: Hash tables configured (established 16384 bind 16384)
                      Feb 26 14:51:21 localhost kernel: [ 1.605956] TCP established hash table entries: 16384 (order: 5, 131072 bytes)
                      Feb 26 14:51:21 localhost kernel: [ 1.606203] TCP bind hash table entries: 16384 (order: 7, 524288 bytes)
                      Feb 26 14:51:21 localhost kernel: [ 1.606980] TCP: Hash tables configured (established 16384 bind 16384)
                      Feb 26 17:46:37 localhost kernel: [ 1.610180] TCP established hash table entries: 16384 (order: 5, 131072 bytes)
                      Feb 26 17:46:37 localhost kernel: [ 1.610427] TCP bind hash table entries: 16384 (order: 7, 524288 bytes)
                      Feb 26 17:46:37 localhost kernel: [ 1.611203] TCP: Hash tables configured (established 16384 bind 16384)
                      Feb 26 20:54:31 localhost kernel: [ 1.602162] TCP established hash table entries: 16384 (order: 5, 131072 bytes)
                      Feb 26 20:54:31 localhost kernel: [ 1.602409] TCP bind hash table entries: 16384 (order: 7, 524288 bytes)
                      Feb 26 20:54:31 localhost kernel: [ 1.603191] TCP: Hash tables configured (established 16384 bind 16384)
                      Feb 26 20:57:02 localhost kernel: [ 1.610000] TCP established hash table entries: 16384 (order: 5, 131072 bytes)
                      Feb 26 20:57:02 localhost kernel: [ 1.610247] TCP bind hash table entries: 16384 (order: 7, 524288 bytes)
                      Feb 26 20:57:02 localhost kernel: [ 1.611026] TCP: Hash tables configured (established 16384 bind 16384)
                      Feb 27 15:41:38 localhost kernel: [ 1.602138] TCP established hash table entries: 16384 (order: 5, 131072 bytes)
                      Feb 27 15:41:38 localhost kernel: [ 1.602385] TCP bind hash table entries: 16384 (order: 7, 524288 bytes)
                      Feb 27 15:41:38 localhost kernel: [ 1.603165] TCP: Hash tables configured (established 16384 bind 16384)
                      root@rock64:/opt/iobroker/log#

                      Homematic CCU2 - Raspberry Pi 4 - IOS (siri) - Amazon Echo 3rd Gen.

                      1 Reply Last reply
                      0
                      • M michaelxhoffmann

                        @Homoran Naja ich habe ja ganz am anfang angefangen. Ich komme ja noch nicht mal aus dem Startblock raus .... Zum Glück bin ich zur Zeit im Krankenstand, sonbst hätte ich schon längst alles wieder verworfen.

                        HomoranH Do not disturb
                        HomoranH Do not disturb
                        Homoran
                        Global Moderator Administrators
                        wrote on last edited by
                        #18

                        @michaelxhoffmann
                        Ich tippe da auch auf das Netzwerk - bin da aber nicht so fit.

                        Ich würde jetzt ALLE Adapter, bis auf admin, hm-rega und den hm-rpc für rfd deaktivieren (also auch cuxD und HM-IP!)

                        dann sehen wir uns die Konfig der beiden hm-Adapter und die Konfig der CCU (welche genau?) an.

                        kein Support per PN! - Fragen im Forum stellen -
                        Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
                        Das Forum freut sich über eine Spende. Benutzt dazu den Spendenbutton im Header. Danke!
                        der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -

                        M 1 Reply Last reply
                        0
                        • HomoranH Homoran

                          @michaelxhoffmann
                          Ich tippe da auch auf das Netzwerk - bin da aber nicht so fit.

                          Ich würde jetzt ALLE Adapter, bis auf admin, hm-rega und den hm-rpc für rfd deaktivieren (also auch cuxD und HM-IP!)

                          dann sehen wir uns die Konfig der beiden hm-Adapter und die Konfig der CCU (welche genau?) an.

                          M Offline
                          M Offline
                          michaelxhoffmann
                          wrote on last edited by
                          #19

                          @Homoran ich habe die ccu2

                          Homematic CCU2 - Raspberry Pi 4 - IOS (siri) - Amazon Echo 3rd Gen.

                          HomoranH 1 Reply Last reply
                          0
                          • liv-in-skyL Offline
                            liv-in-skyL Offline
                            liv-in-sky
                            wrote on last edited by
                            #20

                            find idee gut von homoran - adapter aus und somit einkreisen ob iobroker sonst läuft

                            nach einem gelösten Thread wäre es sinnvoll dies in der Überschrift des ersten Posts einzutragen [gelöst]-... Bitte benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat. Forum-Tools: PicPick https://picpick.app/en/download/ und ScreenToGif https://www.screentogif.com/downloads.html

                            1 Reply Last reply
                            0
                            • M michaelxhoffmann

                              @Homoran ich habe die ccu2

                              HomoranH Do not disturb
                              HomoranH Do not disturb
                              Homoran
                              Global Moderator Administrators
                              wrote on last edited by Homoran
                              #21

                              @michaelxhoffmann sagte in Zuverlässigkeit IOBROKER:

                              @Homoran ich habe die ccu2

                              Gottseidank, dann sind die möglichen Probleme der CCU3 ja schon mal wenigstens vom Tisch

                              Tschakka, das schaffen wir

                              EDIT: Nur zur Sicherheit: Du hast einen Rock64 keinen Rockpro?

                              kein Support per PN! - Fragen im Forum stellen -
                              Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
                              Das Forum freut sich über eine Spende. Benutzt dazu den Spendenbutton im Header. Danke!
                              der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -

                              M 1 Reply Last reply
                              0
                              • HomoranH Homoran

                                @michaelxhoffmann sagte in Zuverlässigkeit IOBROKER:

                                @Homoran ich habe die ccu2

                                Gottseidank, dann sind die möglichen Probleme der CCU3 ja schon mal wenigstens vom Tisch

                                Tschakka, das schaffen wir

                                EDIT: Nur zur Sicherheit: Du hast einen Rock64 keinen Rockpro?

                                M Offline
                                M Offline
                                michaelxhoffmann
                                wrote on last edited by
                                #22

                                @Homoran Tja nun denn Nun habe ich alle Adapter mit Ausnahme des Admin der beiden HM deaktiviert. Gut so weit, aber ich habe ja die Probleme auch mit den Adaptern die jetzt abgeschaltet sind.

                                Homematic CCU2 - Raspberry Pi 4 - IOS (siri) - Amazon Echo 3rd Gen.

                                HomoranH 1 Reply Last reply
                                0
                                • M michaelxhoffmann

                                  @Homoran Tja nun denn Nun habe ich alle Adapter mit Ausnahme des Admin der beiden HM deaktiviert. Gut so weit, aber ich habe ja die Probleme auch mit den Adaptern die jetzt abgeschaltet sind.

                                  HomoranH Do not disturb
                                  HomoranH Do not disturb
                                  Homoran
                                  Global Moderator Administrators
                                  wrote on last edited by
                                  #23

                                  @michaelxhoffmann
                                  eins nach dem andern!

                                  Das wird schon!

                                  kein Support per PN! - Fragen im Forum stellen -
                                  Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
                                  Das Forum freut sich über eine Spende. Benutzt dazu den Spendenbutton im Header. Danke!
                                  der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -

                                  1 Reply Last reply
                                  0
                                  • M Offline
                                    M Offline
                                    michaelxhoffmann
                                    wrote on last edited by
                                    #24

                                    Das Log von dem Pi sieht noch viel schlimmer aus als das vom Rock

                                    Homematic CCU2 - Raspberry Pi 4 - IOS (siri) - Amazon Echo 3rd Gen.

                                    1 Reply Last reply
                                    0
                                    • liv-in-skyL Offline
                                      liv-in-skyL Offline
                                      liv-in-sky
                                      wrote on last edited by
                                      #25

                                      wir müssen irgendwie einkreisen - wenn du das iobroker log anschaust - was kommt da jetzt so - ohne adapter

                                      der pi läuft auch? - aber mit anderer ip adresse oder?

                                      nach einem gelösten Thread wäre es sinnvoll dies in der Überschrift des ersten Posts einzutragen [gelöst]-... Bitte benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat. Forum-Tools: PicPick https://picpick.app/en/download/ und ScreenToGif https://www.screentogif.com/downloads.html

                                      M 1 Reply Last reply
                                      0
                                      • liv-in-skyL Offline
                                        liv-in-skyL Offline
                                        liv-in-sky
                                        wrote on last edited by
                                        #26

                                        es sollten nicht beide geräte (pi und rock ) auf die ccu zugreifen - nur eines im moment

                                        nach einem gelösten Thread wäre es sinnvoll dies in der Überschrift des ersten Posts einzutragen [gelöst]-... Bitte benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat. Forum-Tools: PicPick https://picpick.app/en/download/ und ScreenToGif https://www.screentogif.com/downloads.html

                                        M 1 Reply Last reply
                                        0
                                        • liv-in-skyL liv-in-sky

                                          es sollten nicht beide geräte (pi und rock ) auf die ccu zugreifen - nur eines im moment

                                          M Offline
                                          M Offline
                                          michaelxhoffmann
                                          wrote on last edited by
                                          #27

                                          @liv-in-sky nein es greift ja nur der rock drauf zu. Auf dem Pi läuft nur der SQL Adapter und der Szenenadapter

                                          Homematic CCU2 - Raspberry Pi 4 - IOS (siri) - Amazon Echo 3rd Gen.

                                          1 Reply Last reply
                                          0

                                          Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                                          Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                                          With your input, this post could be even better 💗

                                          Register Login
                                          Reply
                                          • Reply as topic
                                          Log in to reply
                                          • Oldest to Newest
                                          • Newest to Oldest
                                          • Most Votes


                                          Support us

                                          ioBroker
                                          Community Adapters
                                          Donate

                                          538

                                          Online

                                          32.7k

                                          Users

                                          82.6k

                                          Topics

                                          1.3m

                                          Posts
                                          Community
                                          Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
                                          ioBroker Community 2014-2025
                                          logo
                                          • Login

                                          • Don't have an account? Register

                                          • Login or register to search.
                                          • First post
                                            Last post
                                          0
                                          • Home
                                          • Recent
                                          • Tags
                                          • Unread 0
                                          • Categories
                                          • Unreplied
                                          • Popular
                                          • GitHub
                                          • Docu
                                          • Hilfe