Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Error/Bug
    4. Zuverlässigkeit IOBROKER

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

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

    • ioBroker goes Matter ... Matter Adapter in Stable

    SOLVED Zuverlässigkeit IOBROKER

    This topic has been deleted. Only users with topic management privileges can see it.
    • M
      michaelxhoffmann @liv-in-sky last edited by

      @liv-in-sky Hmh OK Dann werde ich mir mal die Kabelgeschichte auch noch anschauen. Woran erkennt man eigentlich ein Cat 5e oder ein Cat6 Kabel? :))

      1 Reply Last reply Reply Quote 0
      • M
        michaelxhoffmann @Homoran last edited by michaelxhoffmann

        @Homoran genau das war mein Problem ich habe hier 2 Drucker und dieser Sch.... canondrucker meinte sich selbst eine IP Adresse reservieren zu müssen. Ich bin nur durch Zufall auf dieser Druckerwebseite mit Netzwerkkonfiguration gestolpert. Da erst fiel mir auf, dass der Drucker auch gar nicht in den Netzwerkeinstellungen meiner Fritzbox auftauchte :)) In den Netzwerkeinstellungen vom Drucker umstellen auf DHCP beziehen vom Gateway (Fritzbox) und alles ist gut. Ich hatte heute keinerlei Fehlermeldungen mehr. Alles so wie es sein soll! 😉 Glücklicherweise hatte ich hier aber auch geduldige Helfer 😉 In den Netzwerkeinstellungen vom Drucker umstellen auf DHCP beziehen vom Gateway (Fritzbox) und alles ist gut.

        1 Reply Last reply Reply Quote 0
        • liv-in-sky
          liv-in-sky last edited by liv-in-sky

          steht drauf - falls nichts draufsteht kabel "vernichten" 🙂

          ich hattemich früher immer gewundert, warum meine transferraten im netz so klein waren - bis ich mal alle kabel ausgetauscht habe - huuiii - dann war alles um einiges schneller

          M 1 Reply Last reply Reply Quote 0
          • M
            michaelxhoffmann @liv-in-sky last edited by

            @liv-in-sky ja gerade gecheckt der rock ist an einem cat5e Kabel. der pi auch :)) Na denn ich vermute mal ich gehe heute Mittag netzwerkkabel kaufen ...

            1 Reply Last reply Reply Quote 0
            • liv-in-sky
              liv-in-sky last edited by

              kann auf jeden fasll nicht schaden - vergiß deien pc (mac) nicht

              1 Reply Last reply Reply Quote 0
              • liv-in-sky
                liv-in-sky last edited by

                du kannst aber - wenn lust - mal auf 100Mbit runterschalten und ein backup starten - vorher rock neustarten

                M 1 Reply Last reply Reply Quote 0
                • M
                  michaelxhoffmann @liv-in-sky last edited by

                  @liv-in-sky Nein der Mac hat auch ein cat 6 kabel lol den rock auf 100 mbit runterschalten, versuche ich auch mal allerdings habe ich gerade mit dem backitup adapter ein Backup angestossen, ich glaube da läuft irgendwas unrund

                  1 Reply Last reply Reply Quote 0
                  • liv-in-sky
                    liv-in-sky last edited by liv-in-sky

                    den backitup kenn ich nicht - ich würde iobroker erstmal auschliessen( abschalten) und das system ansich testen

                    wir wissen ja noch nicht, ob es die netzwerkebene ist - erst wenn die ausgeschlossen ist, kannst du iobroker testen - andersherum bringt - denke ich - nicht viel

                    oder du tauscht die kabel vom mac und dem rock - und machst wieder ein backup - wäre sozusagen ein schnelltest

                    1 Reply Last reply Reply Quote 0
                    • M
                      michaelxhoffmann @wendy2702 last edited by

                      @wendy2702 Ja das Syslog

                      2019-02-28 00:00:26.089 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 00:00:26.107 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 00:03:36.169 - warn: broadlink2.0 Device RM:Broadlink not reachable
                      2019-02-28 00:03:56.567 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 00:03:56.635 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 00:07:27.224 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 00:07:27.242 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 00:10:57.831 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 00:10:57.896 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 00:11:56.356 - warn: broadlink2.0 Device RM:Broadlink not reachable
                      2019-02-28 00:14:28.558 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 00:14:28.573 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 00:17:59.218 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 00:17:59.281 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 00:20:16.530 - warn: broadlink2.0 Device RM:Broadlink not reachable
                      2019-02-28 00:21:29.819 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 00:21:29.836 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 00:25:00.439 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 00:25:00.504 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 00:28:31.160 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 00:28:31.175 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 00:28:36.704 - warn: broadlink2.0 Device RM:Broadlink not reachable
                      2019-02-28 00:32:01.548 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 00:32:01.613 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 00:35:32.189 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 00:35:32.209 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 00:36:56.875 - warn: broadlink2.0 Device RM:Broadlink not reachable
                      2019-02-28 00:39:02.552 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 00:39:02.619 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 00:42:33.281 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 00:42:33.298 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 00:45:17.050 - warn: broadlink2.0 Device RM:Broadlink not reachable
                      2019-02-28 00:46:04.022 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 00:46:04.069 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 00:49:34.617 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 00:49:34.637 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 00:53:05.071 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 00:53:05.138 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 00:53:37.227 - warn: broadlink2.0 Device RM:Broadlink not reachable
                      2019-02-28 00:56:35.674 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 00:56:35.691 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 01:00:06.382 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 01:00:06.448 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 01:01:57.404 - warn: broadlink2.0 Device RM:Broadlink not reachable
                      2019-02-28 01:03:36.788 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 01:03:36.822 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 01:07:07.220 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 01:07:07.287 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 01:10:17.573 - warn: broadlink2.0 Device RM:Broadlink not reachable
                      2019-02-28 01:10:37.691 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 01:10:37.709 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 01:14:08.115 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 01:14:08.162 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 01:17:38.777 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 01:17:38.797 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 01:21:09.425 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 01:21:09.490 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 01:24:40.006 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 01:24:40.022 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 01:28:10.354 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 01:28:10.423 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 01:31:41.082 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 01:31:41.102 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 01:35:11.449 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 01:35:11.512 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 01:38:42.193 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 01:38:42.227 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 01:42:12.899 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 01:42:12.947 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 01:45:43.251 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 01:45:43.288 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 01:49:13.653 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 01:49:13.719 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 01:52:44.403 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 01:52:44.419 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 01:56:14.734 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 01:56:14.801 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 01:59:45.210 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 01:59:45.229 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 02:00:32.002 - error: hm-rpc.1 Ping error: Error: response timeout
                      2019-02-28 02:00:32.004 - info: hm-rpc.1 Disconnected
                      2019-02-28 02:01:07.012 - error: hm-rpc.1 init error: Error: response timeout
                      2019-02-28 02:01:20.241 - error: hm-rpc.0 Ping error: Error: response timeout
                      2019-02-28 02:01:20.241 - info: hm-rpc.0 Disconnected
                      2019-02-28 02:01:37.013 - error: hm-rpc.1 init error: Error: response timeout
                      2019-02-28 02:01:55.259 - error: hm-rpc.0 init error: Error: response timeout
                      2019-02-28 02:02:07.017 - error: hm-rpc.1 init error: Error: response timeout
                      2019-02-28 02:02:25.267 - error: hm-rpc.0 init error: Error: response timeout
                      2019-02-28 02:02:37.017 - error: hm-rpc.1 init error: Error: response timeout
                      2019-02-28 02:02:37.226 - error: hm-rpc.2 Ping error: Error: connect ETIMEDOUT 192.168.178.188:2010
                      2019-02-28 02:02:37.228 - info: hm-rpc.2 Disconnected
                      2019-02-28 02:02:52.074 - info: alexa2.0 Alexa-Push-Connection disconnected - retry: Retry Connection in 5s
                      2019-02-28 02:02:55.275 - error: hm-rpc.0 init error: Error: response timeout
                      2019-02-28 02:02:55.274 - error: hm-rega.0 post request error: connect ETIMEDOUT 192.168.178.188:8181
                      2019-02-28 02:02:55.277 - error: hm-rega.0 CCU 192.168.178.188 unreachable
                      2019-02-28 02:03:07.020 - error: hm-rpc.1 init error: Error: response timeout
                      2019-02-28 02:03:07.300 - info: hm-rpc.2 Connected
                      2019-02-28 02:03:07.849 - info: hm-rpc.2 xmlrpc <- listDevices ["hm-rpc.2"]
                      2019-02-28 02:03:07.883 - info: hm-rpc.2 xmlrpc -> 0 devices
                      2019-02-28 02:03:08.849 - info: hm-rpc.2 xmlrpc <- newDevices 67
                      2019-02-28 02:03:08.872 - info: hm-rpc.2 new HmIP devices/channels after filter: 0
                      2019-02-28 02:03:10.211 - error: hm-rega.0 Cannot parse answer for devices: undefined
                      2019-02-28 02:03:25.281 - error: hm-rpc.0 init error: Error: response timeout
                      2019-02-28 02:03:25.442 - info: hm-rega.0 ReGaHSS 192.168.178.188 up
                      2019-02-28 02:03:25.477 - info: hm-rega.0 time difference local-ccu 0s
                      2019-02-28 02:03:25.542 - info: hm-rega.0 added/updated 4 favorites to enum.favorites
                      2019-02-28 02:03:25.646 - info: hm-rega.0 added/updated functions to enum.functions
                      2019-02-28 02:03:25.713 - info: hm-rega.0 added/updated rooms to enum.rooms
                      2019-02-28 02:03:26.223 - info: hm-rega.0 got 45 programs
                      2019-02-28 02:03:26.276 - info: hm-rega.0 added/updated 45 programs
                      2019-02-28 02:03:26.277 - info: hm-rega.0 deleted 0 programs
                      2019-02-28 02:03:26.299 - info: hm-rega.0 got 15 variables
                      2019-02-28 02:03:26.367 - info: hm-rega.0 added/updated 15 variables
                      2019-02-28 02:03:26.368 - info: hm-rega.0 deleted 0 variables
                      2019-02-28 02:03:26.372 - info: hm-rega.0 request state values
                      2019-02-28 02:03:26.882 - info: hm-rega.0 got state values
                      2019-02-28 02:03:37.022 - error: hm-rpc.1 init error: Error: response timeout
                      2019-02-28 02:03:55.290 - error: hm-rpc.0 init error: Error: response timeout
                      2019-02-28 02:03:56.352 - error: hm-rpc.1 uncaught exception: read ECONNRESET
                      2019-02-28 02:03:56.352 - error: hm-rpc.1 Error: read ECONNRESET
                      at TCP.onread (net.js:622:25)
                      2019-02-28 02:03:56.356 - info: hm-rpc.1 binrpc -> 192.168.178.188:2001/ init ["xmlrpc_bin://192.168.178.21:12001",""]
                      2019-02-28 02:03:56.402 - error: Caught by controller[0]: { Error: read ECONNRESET
                      2019-02-28 02:03:56.403 - error: Caught by controller[0]: at TCP.onread (net.js:622:25) errno: 'ECONNRESET', code: 'ECONNRESET', syscall: 'read' }
                      2019-02-28 02:03:56.403 - error: host.rock64 instance system.adapter.hm-rpc.1 terminated with code 0 (OK)
                      2019-02-28 02:03:56.404 - info: host.rock64 Restart adapter system.adapter.hm-rpc.1 because enabled
                      2019-02-28 02:04:07.333 - error: hm-rpc.2 Ping error: Error: connect ETIMEDOUT 192.168.178.188:2010
                      2019-02-28 02:04:07.334 - info: hm-rpc.2 Disconnected
                      2019-02-28 02:04:25.298 - error: hm-rpc.0 init error: Error: response timeout
                      2019-02-28 02:04:26.434 - info: host.rock64 instance system.adapter.hm-rpc.1 started with pid 6175
                      2019-02-28 02:04:27.878 - info: hm-rpc.1 starting. Version 1.9.7 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v8.15.0
                      2019-02-28 02:04:28.241 - info: hm-rpc.1 binrpc server is trying to listen on 192.168.178.21:12001
                      2019-02-28 02:04:28.242 - 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-28 02:04:28.278 - info: hm-rpc.1 binrpc <- system.listMethods ["hm-rpc.1"]
                      2019-02-28 02:04:28.291 - info: hm-rpc.1 binrpc <- listDevices ["hm-rpc.1"]
                      2019-02-28 02:04:28.311 - info: hm-rpc.1 binrpc -> 67 devices
                      2019-02-28 02:04:28.462 - info: hm-rpc.1 Connected
                      2019-02-28 02:04:37.420 - info: hm-rpc.2 Connected
                      2019-02-28 02:04:37.614 - info: hm-rpc.2 xmlrpc <- listDevices ["hm-rpc.2"]
                      2019-02-28 02:04:37.634 - info: hm-rpc.2 xmlrpc -> 0 devices
                      2019-02-28 02:04:38.415 - info: hm-rpc.2 xmlrpc <- newDevices 67
                      2019-02-28 02:04:38.432 - info: hm-rpc.2 new HmIP devices/channels after filter: 0
                      2019-02-28 02:04:44.733 - error: hm-rpc.0 uncaught exception: read ECONNRESET
                      2019-02-28 02:04:44.734 - error: hm-rpc.0 Error: read ECONNRESET
                      at TCP.onread (net.js:622:25)
                      2019-02-28 02:04:44.739 - info: hm-rpc.0 binrpc -> 192.168.178.188:8701/ init ["xmlrpc_bin://192.168.178.21:18701",""]
                      2019-02-28 02:04:44.755 - info: hm-rpc.0 terminating
                      2019-02-28 02:04:44.783 - error: Caught by controller[0]: { Error: read ECONNRESET
                      2019-02-28 02:04:44.784 - error: Caught by controller[0]: at TCP.onread (net.js:622:25) errno: 'ECONNRESET', code: 'ECONNRESET', syscall: 'read' }
                      2019-02-28 02:04:44.784 - error: host.rock64 instance system.adapter.hm-rpc.0 terminated with code 0 (OK)
                      2019-02-28 02:04:44.785 - info: host.rock64 Restart adapter system.adapter.hm-rpc.0 because enabled
                      2019-02-28 02:05:04.421 - info: alexa2.0 Alexa-Push-Connection Error: Error: connect ETIMEDOUT 176.32.99.148:443
                      2019-02-28 02:05:04.422 - info: alexa2.0 Alexa-Push-Connection disconnected - retry: Retry Connection in 5s
                      2019-02-28 02:05:14.821 - info: host.rock64 instance system.adapter.hm-rpc.0 started with pid 6190
                      2019-02-28 02:05:16.256 - info: hm-rpc.0 starting. Version 1.9.7 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v8.15.0
                      2019-02-28 02:05:16.625 - info: hm-rpc.0 binrpc server is trying to listen on 192.168.178.21:18701
                      2019-02-28 02:05:16.626 - 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-28 02:05:17.243 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 02:05:17.263 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 02:05:17.269 - info: hm-rpc.0 Connected
                      2019-02-28 02:05:56.820 - error: iot.0 read ECONNRESET
                      2019-02-28 02:05:56.822 - info: iot.0 Connection changed: disconnect
                      2019-02-28 02:05:56.822 - info: iot.0 Connection lost
                      2019-02-28 02:06:02.139 - info: iot.0 Connection changed: connect
                      2019-02-28 02:06:13.143 - info: alexa2.0 Alexa-Push-Connection disconnected - fallback to poll data: Cookie invalid
                      2019-02-28 02:08:47.965 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 02:08:47.987 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 02:12:18.534 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 02:12:18.550 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 02:15:49.276 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 02:15:49.321 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 02:19:19.924 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 02:19:19.945 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 02:22:50.381 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 02:22:50.444 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 02:26:21.158 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 02:26:21.179 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 02:27:49.550 - warn: broadlink2.0 Device RM:Broadlink not reachable
                      2019-02-28 02:29:51.761 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 02:29:51.824 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 02:33:22.404 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 02:33:22.427 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 02:36:53.046 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 02:36:53.109 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 02:40:23.773 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 02:40:23.793 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 02:43:54.448 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 02:43:54.512 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 02:47:24.842 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 02:47:24.861 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 02:48:30.117 - warn: broadlink2.0 Device RM:Broadlink not reachable
                      2019-02-28 02:50:55.570 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 02:50:55.634 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 02:54:26.250 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 02:54:26.270 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 02:56:50.305 - warn: broadlink2.0 Device RM:Broadlink not reachable
                      2019-02-28 02:57:56.844 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 02:57:56.907 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 03:01:27.244 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 03:01:27.261 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 03:04:57.636 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 03:04:57.703 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 03:08:28.308 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 03:08:28.327 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 03:11:58.725 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 03:11:58.788 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 03:15:29.110 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 03:15:29.126 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 03:18:59.817 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 03:18:59.882 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 03:22:30.598 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 03:22:30.619 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 03:26:01.037 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 03:26:01.080 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 03:29:31.786 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 03:29:31.805 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 03:33:02.146 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 03:33:02.211 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 03:36:32.825 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 03:36:32.846 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 03:40:03.529 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 03:40:03.593 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 03:43:33.993 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 03:43:34.009 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 03:47:04.698 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 03:47:04.744 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 03:50:35.161 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 03:50:35.181 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 03:54:05.823 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 03:54:05.898 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 03:56:51.914 - warn: broadlink2.0 Device RM:Broadlink not reachable
                      2019-02-28 03:57:36.261 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 03:57:36.290 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 04:01:06.771 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 04:01:06.844 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 04:04:37.569 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 04:04:37.590 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 04:05:12.129 - warn: broadlink2.0 Device RM:Broadlink not reachable
                      2019-02-28 04:08:08.204 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 04:08:08.268 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 04:11:38.988 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 04:11:39.009 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 04:13:32.308 - warn: broadlink2.0 Device RM:Broadlink not reachable
                      2019-02-28 04:15:09.682 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 04:15:09.728 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 04:18:40.367 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 04:18:40.387 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 04:22:10.992 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 04:22:11.069 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 04:25:41.711 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 04:25:41.728 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 04:27:56.646 - error: cloud.0 Ping timeout
                      2019-02-28 04:27:56.647 - info: cloud.0 Connection changed: Ping timeout
                      2019-02-28 04:27:56.648 - info: cloud.0 Connection lost
                      2019-02-28 04:28:56.674 - info: cloud.0 Trying to connect as system.user.admin
                      2019-02-28 04:28:56.856 - info: cloud.0 Connection changed: connect
                      2019-02-28 04:28:56.893 - info: cloud.0 Connection not changed: was connected
                      2019-02-28 04:29:12.395 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 04:29:12.445 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 04:31:02.539 - error: iot.0 read ECONNRESET
                      2019-02-28 04:31:02.540 - info: iot.0 Connection changed: disconnect
                      2019-02-28 04:31:02.540 - info: iot.0 Connection lost
                      2019-02-28 04:31:07.928 - info: iot.0 Connection changed: connect
                      2019-02-28 04:32:42.778 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 04:32:42.806 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 04:36:13.132 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 04:36:13.197 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 04:39:43.560 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 04:39:43.583 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 04:43:14.055 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 04:43:14.104 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 04:46:44.429 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 04:46:44.446 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 04:50:15.167 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 04:50:15.238 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 04:53:45.841 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 04:53:45.865 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 04:57:16.557 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 04:57:16.621 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 05:00:47.097 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 05:00:47.113 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 05:04:17.863 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 05:04:17.911 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 05:07:48.566 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 05:07:48.587 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 05:11:19.252 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 05:11:19.320 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 05:14:49.932 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 05:14:49.949 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 05:18:20.553 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 05:18:20.617 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 05:21:51.252 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 05:21:51.275 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 05:25:22.022 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 05:25:22.066 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 05:28:52.440 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 05:28:52.457 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 05:32:23.203 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 05:32:23.274 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 05:35:53.981 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 05:35:53.996 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 05:39:24.709 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 05:39:24.759 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 05:42:55.383 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 05:42:55.402 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 05:46:26.034 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 05:46:26.102 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 05:49:56.793 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 05:49:56.812 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 05:53:27.439 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 05:53:27.502 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 05:56:58.203 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 05:56:58.228 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 06:00:28.613 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 06:00:28.677 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 06:03:59.266 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 06:03:59.287 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 06:07:29.665 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 06:07:29.711 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 06:11:00.026 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 06:11:00.041 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 06:14:30.422 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 06:14:30.490 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 06:18:01.197 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 06:18:01.220 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 06:21:31.946 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 06:21:32.013 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 06:25:02.398 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 06:25:02.416 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 06:28:32.801 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 06:28:32.852 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 06:32:03.540 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 06:32:03.563 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 06:35:33.990 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 06:35:34.059 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 06:39:04.783 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 06:39:04.801 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 06:42:35.267 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 06:42:35.314 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 06:46:05.927 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 06:46:05.947 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 06:49:36.374 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 06:49:36.443 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 06:53:07.156 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 06:53:07.171 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 06:56:37.590 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 06:56:37.651 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 07:00:08.305 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 07:00:08.327 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 07:03:38.745 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 07:03:38.794 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 07:07:09.406 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 07:07:09.421 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 07:10:39.782 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 07:10:39.853 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 07:14:10.174 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 07:14:10.196 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 07:17:40.800 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 07:17:40.917 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 07:21:11.619 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 07:21:11.653 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 07:24:42.404 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 07:24:42.456 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 07:28:13.171 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 07:28:13.185 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 07:31:43.596 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 07:31:43.662 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 07:35:14.373 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 07:35:14.402 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 07:38:45.038 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 07:38:45.100 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 07:42:15.428 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 07:42:15.444 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 07:45:46.099 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 07:45:46.161 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 07:49:16.825 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 07:49:16.849 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 07:52:47.564 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 07:52:47.630 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 07:56:18.361 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 07:56:18.375 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 07:59:49.084 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 07:59:49.151 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 08:03:19.815 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 08:03:19.836 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 08:06:50.486 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 08:06:50.533 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 08:10:21.201 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 08:10:21.215 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 08:13:51.526 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 08:13:51.605 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 08:17:22.170 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 08:17:22.191 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 08:20:52.522 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 08:20:52.591 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 08:24:23.268 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 08:24:23.288 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 08:27:54.057 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 08:27:54.105 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 08:31:24.450 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 08:31:24.465 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 08:34:54.796 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 08:34:54.871 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 08:38:25.483 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 08:38:25.498 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 08:40:35.543 - error: hm-rpc.1 Ping error: Error: response timeout
                      2019-02-28 08:40:35.544 - info: hm-rpc.1 Disconnected
                      2019-02-28 08:40:38.956 - warn: broadlink2.0 Device RM:Broadlink not reachable
                      2019-02-28 08:40:57.252 - error: hm-rpc.1 uncaught exception: read ECONNRESET
                      2019-02-28 08:40:57.253 - error: hm-rpc.1 Error: read ECONNRESET
                      at TCP.onread (net.js:622:25)
                      2019-02-28 08:40:57.257 - info: hm-rpc.1 binrpc -> 192.168.178.188:2001/ init ["xmlrpc_bin://192.168.178.21:12001",""]
                      2019-02-28 08:40:57.334 - error: Caught by controller[0]: { Error: read ECONNRESET
                      2019-02-28 08:40:57.335 - error: Caught by controller[0]: at TCP.onread (net.js:622:25) errno: 'ECONNRESET', code: 'ECONNRESET', syscall: 'read' }
                      2019-02-28 08:40:57.336 - error: host.rock64 instance system.adapter.hm-rpc.1 terminated with code 0 (OK)
                      2019-02-28 08:40:57.337 - info: host.rock64 Restart adapter system.adapter.hm-rpc.1 because enabled
                      2019-02-28 08:41:27.369 - info: host.rock64 instance system.adapter.hm-rpc.1 started with pid 8082
                      2019-02-28 08:41:28.776 - info: hm-rpc.1 starting. Version 1.9.7 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v8.15.0
                      2019-02-28 08:41:29.146 - info: hm-rpc.1 binrpc server is trying to listen on 192.168.178.21:12001
                      2019-02-28 08:41:29.148 - 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-28 08:41:29.184 - info: hm-rpc.1 binrpc <- system.listMethods ["hm-rpc.1"]
                      2019-02-28 08:41:29.197 - info: hm-rpc.1 binrpc <- listDevices ["hm-rpc.1"]
                      2019-02-28 08:41:29.216 - info: hm-rpc.1 binrpc -> 67 devices
                      2019-02-28 08:41:29.363 - info: hm-rpc.1 Connected
                      2019-02-28 08:41:56.132 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 08:41:56.196 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 08:45:16.242 - error: iot.0 read ECONNRESET
                      2019-02-28 08:45:16.242 - info: iot.0 Connection changed: disconnect
                      2019-02-28 08:45:16.243 - info: iot.0 Connection lost
                      2019-02-28 08:45:21.563 - info: iot.0 Connection changed: connect
                      2019-02-28 08:45:26.825 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 08:45:26.844 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 08:48:57.192 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 08:48:57.256 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 08:52:27.628 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 08:52:27.644 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 08:55:57.970 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 08:55:58.034 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 08:59:28.443 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 08:59:28.466 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 09:02:58.955 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 09:02:59.021 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 09:06:29.672 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 09:06:29.688 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 09:10:00.210 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 09:10:00.255 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 09:13:30.961 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 09:13:30.976 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 09:14:31.071 - warn: alexa2.0 Reconnection to DB.
                      2019-02-28 09:14:31.097 - warn: hm-rpc.1 Reconnection to DB.
                      2019-02-28 09:14:31.087 - warn: alexa2.0 Reconnection to DB.
                      2019-02-28 09:14:31.061 - warn: discovery.0 Reconnection to DB.
                      2019-02-28 09:14:31.079 - warn: discovery.0 Reconnection to DB.
                      2019-02-28 09:14:31.074 - warn: milight.0 Reconnection to DB.
                      2019-02-28 09:14:31.091 - warn: milight.0 Reconnection to DB.
                      2019-02-28 09:14:31.105 - warn: hm-rpc.1 Reconnection to DB.
                      2019-02-28 09:14:31.264 - error: discovery.0 already running
                      2019-02-28 09:14:31.321 - error: milight.0 already running
                      2019-02-28 09:14:31.315 - error: hm-rpc.1 already running
                      2019-02-28 09:14:31.309 - warn: web.0 Reconnection to DB.
                      2019-02-28 09:14:31.324 - warn: web.0 Reconnection to DB.
                      2019-02-28 09:14:31.458 - error: host.rock64 instance system.adapter.backitup.0 terminated with code 7 (Adapter already running)
                      2019-02-28 09:14:31.459 - info: host.rock64 Restart adapter system.adapter.backitup.0 because enabled
                      2019-02-28 09:14:31.469 - error: host.rock64 instance system.adapter.discovery.0 terminated with code 7 (Adapter already running)
                      2019-02-28 09:14:31.469 - info: host.rock64 Restart adapter system.adapter.discovery.0 because enabled
                      2019-02-28 09:14:31.478 - error: host.rock64 instance system.adapter.milight.0 terminated with code 7 (Adapter already running)
                      2019-02-28 09:14:31.479 - info: host.rock64 Restart adapter system.adapter.milight.0 because enabled
                      2019-02-28 09:14:31.488 - error: host.rock64 instance system.adapter.hm-rpc.1 terminated with code 7 (Adapter already running)
                      2019-02-28 09:14:31.488 - info: host.rock64 Restart adapter system.adapter.hm-rpc.1 because enabled
                      2019-02-28 09:14:31.517 - error: alexa2.0 already running
                      2019-02-28 09:14:31.553 - error: host.rock64 instance system.adapter.alexa2.0 terminated with code 7 (Adapter already running)
                      2019-02-28 09:14:31.553 - info: host.rock64 Restart adapter system.adapter.alexa2.0 because enabled
                      2019-02-28 09:14:31.762 - error: web.0 already running
                      2019-02-28 09:14:31.797 - error: host.rock64 instance system.adapter.web.0 terminated with code 7 (Adapter already running)
                      2019-02-28 09:14:31.798 - info: host.rock64 Restart adapter system.adapter.web.0 because enabled
                      2019-02-28 09:14:34.811 - warn: javascript.0 Reconnection to DB.
                      2019-02-28 09:14:34.823 - warn: javascript.0 Reconnection to DB.
                      2019-02-28 09:15:01.487 - info: host.rock64 instance system.adapter.backitup.0 started with pid 8262
                      2019-02-28 09:15:01.523 - info: host.rock64 instance system.adapter.discovery.0 started with pid 8263
                      2019-02-28 09:15:01.556 - info: host.rock64 instance system.adapter.milight.0 started with pid 8273
                      2019-02-28 09:15:01.593 - info: host.rock64 instance system.adapter.hm-rpc.1 started with pid 8279
                      2019-02-28 09:15:01.646 - info: host.rock64 instance system.adapter.alexa2.0 started with pid 8281
                      2019-02-28 09:15:01.866 - info: host.rock64 instance system.adapter.web.0 started with pid 8294
                      2019-02-28 09:15:04.193 - info: alexa2.0 starting. Version 1.1.3 in /opt/iobroker/node_modules/iobroker.alexa2, node: v8.15.0
                      2019-02-28 09:15:04.395 - info: discovery.0 starting. Version 1.2.4 in /opt/iobroker/node_modules/iobroker.discovery, node: v8.15.0
                      2019-02-28 09:15:04.627 - info: alexa2.0 Proxy IP not set, use first network interface (192.168.178.21) instead
                      2019-02-28 09:15:04.646 - info: hm-rpc.1 starting. Version 1.9.7 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v8.15.0
                      2019-02-28 09:15:04.695 - info: backitup.0 starting. Version 1.1.2 in /opt/iobroker/node_modules/iobroker.backitup, node: v8.15.0
                      2019-02-28 09:15:04.703 - info: milight.0 starting. Version 0.3.6 in /opt/iobroker/node_modules/iobroker.milight, node: v8.15.0
                      2019-02-28 09:15:04.899 - info: backitup.0 [minimal] backup was activated at 02:00 every 1 day(s)
                      2019-02-28 09:15:04.961 - info: backitup.0 [total] backup was activated at 03:00 every 3 day(s)
                      2019-02-28 09:15:05.157 - info: hm-rpc.1 binrpc server is trying to listen on 192.168.178.21:12001
                      2019-02-28 09:15:05.159 - 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-28 09:15:05.121 - info: web.0 starting. Version 2.4.1 in /opt/iobroker/node_modules/iobroker.web, node: v8.15.0
                      2019-02-28 09:15:05.204 - info: hm-rpc.1 binrpc <- system.listMethods ["hm-rpc.1"]
                      2019-02-28 09:15:05.221 - info: hm-rpc.1 binrpc <- listDevices ["hm-rpc.1"]
                      2019-02-28 09:15:05.271 - info: hm-rpc.1 binrpc -> 67 devices
                      2019-02-28 09:15:05.468 - info: hm-rpc.1 Connected
                      2019-02-28 09:15:05.738 - info: web.0 socket.io server listening on port 8082
                      2019-02-28 09:15:05.745 - info: web.0 http server listening on port 8082
                      2019-02-28 09:15:09.543 - info: alexa2.0 Alexa-Push-Connection established. Disable Polling
                      2019-02-28 09:17:01.616 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 09:17:01.683 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 09:20:32.062 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 09:20:32.086 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 09:24:02.488 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 09:24:02.535 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 09:27:33.194 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 09:27:33.211 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 09:31:03.607 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 09:31:03.672 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 09:34:34.424 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 09:34:34.445 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 09:38:05.098 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 09:38:05.151 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 09:41:35.787 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 09:41:35.805 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 09:45:06.164 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 09:45:06.231 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 09:48:36.616 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 09:48:36.632 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 09:52:07.226 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 09:52:07.274 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 09:55:37.877 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 09:55:37.898 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 09:59:08.517 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 09:59:08.583 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 10:02:39.008 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 10:02:39.024 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 10:06:09.741 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 10:06:09.812 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 10:09:40.433 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 10:09:40.454 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 10:13:10.837 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 10:13:10.912 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 10:16:41.545 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 10:16:41.563 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 10:20:12.051 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 10:20:12.103 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 10:23:42.423 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 10:23:42.442 - info: hm-rpc.0 new CUxD devices/channels after filter: 0
                      2019-02-28 10:27:13.181 - info: hm-rpc.0 binrpc -> listDevices 36
                      2019-02-28 10:27:13.247 - info: hm-rpc.0 new CUxD devices/channels after filter: 0

                      Der Rock bezieht die IPadresse von der Fritzbox, so wie alle meine Netzwerkgeräte. JS Controller ist 1.4.2 Naja wenn der Rock nicht erreichbar war, war auch der Broker nicht erreichbar.
                      Wie trenne ich das Master slavesystem wieder auf? gibt es einen Befehl dafür?

                      1 Reply Last reply Reply Quote 0
                      • wendy2702
                        wendy2702 last edited by

                        Ich meinte das Linux Syslog.

                        Ich persönlich glaube nicht an das Kabel, jeder halbwegs Moderne PC/Switch/HUB macht heute ein Autonegotiation und stellt die maximale Physikalische Geschwindigkeit ein.... aber man sieht ja schon mal Pferde vor der Apotheke kotz....

                        Ich habe das Master - Slave noch manuell einrichten müssen. Wie hast du es gemacht?

                        Schau mal hier. Früher hat es gereicht im Slave die IP des Masters zu löschen und den Host dann wie am Ende der Seite beschrieben aus dem Master zu entfernen.

                        http://www.iobroker.net/docu/?page_id=3068&lang=de

                        1 Reply Last reply Reply Quote 0
                        • Röstkartoffel
                          Röstkartoffel @michaelxhoffmann last edited by Röstkartoffel

                          @michaelxhoffmann sagte in Zuverlässigkeit IOBROKER:

                          @Röstkartoffel ich habe hier Repeater laufen, und eine zweite Fritzbox, die aber auch nur als Repeater fungiert, die hat auch einen anderen WLAN Namen. Was meinst Du mit Lanbrücke im repeater umstellen?

                          Alle Geräte sind aktuell mit der v7.01, der Repeater ist mit dem Netzwerkkabel an der Fritzbox angeschlossen.

                          Fritzbox als Repeater:
                          Fritz als Repeater.JPG

                          Anschluß des Repeaters:
                          Repeater.JPG

                          Repeater umstellen zwischen LAN oder WLAN Verbindung zur Fritzbox
                          Repeater umstellen.JPG

                          1 Reply Last reply Reply Quote 0
                          • Röstkartoffel
                            Röstkartoffel last edited by Röstkartoffel

                            Nach meiner leidlichen Erfahrung vor ein paar Tagen kann mir vorstellen, das du die Fritzbox mit dem Kabel angeschlossen und den Heimnetzzugang per WLAN aktiviert haben könntest.
                            Genauso war das nämlich an meinem System durch mein Eigentor.
                            Die merkwürdigsten Dinge sind da mit dem ioBroker passiert und obwohl das System bei mir seit Moanten ohne Störung lief. Errormeldungen deiner Art habe ich nie so gesehen.

                            M 1 Reply Last reply Reply Quote 0
                            • M
                              michaelxhoffmann @Röstkartoffel last edited by Homoran

                              @Röstkartoffel So, OK also ich habe eine weitere Fritzbox als Repeater die hängt im Garten und hat einen eigenen WLAN Namen, dazu habe ich zwei fritz wlanrepeater also die Teile die nur das vorhandene WLANsignal verstärken. Aktuell ist mein Log wieder voll mit Fehlermeldungen, diesmal vom IOT Adapter.
                              Der ist auch gelb und keine Ahnung was das wieder soll 😞
                              getaddrinfo ENOTFOUND Schlüssel ENTFERNT
                              Irgendwie entpuppt sich der Broker bei mir als Wundertüte. Reiss auf und staune was kommt... Ich habe jetzt erst mal cat6 Kabel bestellt heute abend schalte ich den rock mal auf 100 mbit und dann mal sehen, ich fürchte nur der Wurm sitzt ganz woanders.

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

                                @michaelxhoffmann sagte in Zuverlässigkeit IOBROKER:

                                Irgendwie entpuppt sich der Broker bei mir als Wundertüte.

                                Das ist nicht der ioBroker.

                                Es ist definitiv ein Netzwerkproblem.
                                Ich habe den Key entfernt, aber der ioT kam nicht auf den Amazon-Server

                                1 Reply Last reply Reply Quote 0
                                • M
                                  michaelxhoffmann last edited by

                                  Hmh was hat der iot adapter mit Amazon zu tun?

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

                                    @michaelxhoffmann
                                    wegen Alexa - oder wofür nutzst du ihn

                                    M 1 Reply Last reply Reply Quote 0
                                    • M
                                      michaelxhoffmann @Homoran last edited by

                                      @Homoran ach so ja klar. Sorry ich stand gerade auf dem Schlauch. Ich habe alles neu gestartet.

                                      1 Reply Last reply Reply Quote 0
                                      • M
                                        michaelxhoffmann last edited by

                                        So, nun habe ich keinerei Fehlermeldungen, mit Ausnahme von Alexa und IOT. Dafür funktionieren jetzt die Alexas nicht mehr. An dieser Stelle habe ich den Adapter cloud.pro entfernt da Alexa moniert hat dass i
                                        ch den Skill zzu dem zu bedienenden Gerät deaktivieren und wieder aktivieren solle. Ergebnis: Deaktivierung hat funktioniert, jedoch nicht die neue Aktivierung!
                                        Ist ja nicht weiter schlimm, ich habe ja noch den iot Adapter aktiv. Aber Fehlanzeige: Diese Geräte aus dem IOT Adapter werden gar nicht erst in alexa übernommen.
                                        Ich habe das doch richtig verstanden dass ich den IOT Adapter auch ohne Pro Cloud adapter nutzen kann? (Ich habe einen aktiven pro Account)

                                        1 Reply Last reply Reply Quote 0
                                        • liv-in-sky
                                          liv-in-sky last edited by

                                          hi michael - bedeutet das, der rock funktioniert jetzt - wenn ja was hast du geändert

                                          M 1 Reply Last reply Reply Quote 0
                                          • M
                                            michaelxhoffmann @liv-in-sky last edited by michaelxhoffmann

                                            @liv-in-sky Naja geändert habe ich nichts, ausser dass seit gestern abend Alexa nicht mehr läuft. Also Sprachsteuerung ist nicht. Das sind jetzt alle Fehlermeldungen.

                                            iot.0 2019-03-01 11:05:59.345 warn Invalid URL key. Status update is disabled: {"error":"Unsupported version"}
                                            iot.0 2019-03-01 11:05:59.342 error Cannot report device state: null
                                            host.rock64 2019-03-01 11:04:16.930 error instance system.adapter.cloud.0 terminated with code 0 (OK)
                                            alexa2.0 2019-03-01 11:01:11.373 error Error: You can try to get the cookie manually by opening http://192.168.178.21:36092/ with your browser.
                                            alexa2.0 2019-03-01 11:01:11.371 error Error: Login unsuccessfull. Please check credentials.

                                            1 Reply Last reply Reply Quote 0
                                            • liv-in-sky
                                              liv-in-sky last edited by

                                              manchmal verwirrst du mich - ist das problem jetzt wie von zauberhand verschwunden - das der alexa adapter ein problem hat, ist ja - im vergleich zu vorher - eher unbedeutend - ich meine, dass es doch erstmal wichtig ist, das der rock stabil mit deinen ccu-adaptern läuft und nicht über nacht das log plötzlich vollmüllt (wenn z.b das backup beginnt)

                                              was ist deine priorität - ein einzelner adapter oder das das iobroker-gesamt-system stabiil läuft

                                              marvin-sitzt-kleiner.png

                                              M Homoran 2 Replies Last reply Reply Quote 0
                                              • First post
                                                Last post

                                              Support us

                                              ioBroker
                                              Community Adapters
                                              Donate

                                              943
                                              Online

                                              31.9k
                                              Users

                                              80.2k
                                              Topics

                                              1.3m
                                              Posts

                                              iobroker zuverlässigkeit multiple fehler
                                              10
                                              156
                                              9973
                                              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