SOLVED Zuverlässigkeit IOBROKER
-
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 -
@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.
-
@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.
-
@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# -
@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.
-
@Homoran ich habe die ccu2
-
find idee gut von homoran - adapter aus und somit einkreisen ob iobroker sonst läuft
-
@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?
-
@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.
-
@michaelxhoffmann
eins nach dem andern!Das wird schon!
-
Das Log von dem Pi sieht noch viel schlimmer aus als das vom Rock
-
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?
-
es sollten nicht beide geräte (pi und rock ) auf die ccu zugreifen - nur eines im moment
-
@liv-in-sky nein es greift ja nur der rock drauf zu. Auf dem Pi läuft nur der SQL Adapter und der Szenenadapter
-
also master slave system ?
-
@liv-in-sky Ja der Pi hat ne andere ipadresse. Jetzt kommen zumindest keine Warnhinweise oder Fehler. Ja der rock ist der Master, der pi der slave.
-
es laufen ja noch ein paar adapter - kannst du irgendwas ausprobieren um zu sehen , ob alles richtig kommuniziert und immer schön ins log kucken
schaltet der broadlink
alexa2 - kommen die befehle durch -
@liv-in-sky habe den IOT adapter zugeschaltet nun kommt dieser Fehler:
Cannot report device state: null
Aber ich glaube das ist der den man ignorieren kann? Weil der überarbeitet wird? -
bei gelegenheit - zeigtauch mal das pi log
-
host.ioBroker-Pi 2019-02-27 17:39:40.354 info object change system.adapter.iot.0
host.ioBroker-Pi 2019-02-27 17:39:36.701 info object change system.adapter.cloud.0
host.ioBroker-Pi 2019-02-27 17:35:36.721 info object change system.adapter.alexa2.0
host.ioBroker-Pi 2019-02-27 17:27:16.306 info object change system.adapter.hm-rpc.0
host.ioBroker-Pi 2019-02-27 17:22:51.140 info object change system.adapter.hm-rpc.2
host.ioBroker-Pi 2019-02-27 17:22:20.847 info object change system.adapter.hm-rpc.0
host.ioBroker-Pi 2019-02-27 17:21:50.178 info object change system.adapter.web.0
host.ioBroker-Pi 2019-02-27 17:21:48.803 info object change system.adapter.tr-064.0
host.ioBroker-Pi 2019-02-27 17:21:48.205 info Do not restart adapter system.adapter.sql.0 because disabled or deleted
host.ioBroker-Pi 2019-02-27 17:21:48.204 error instance system.adapter.sql.0 terminated with code 0 (OK)
sql.0 2019-02-27 17:21:48.184 info terminating
host.ioBroker-Pi 2019-02-27 17:21:47.670 info stopInstance system.adapter.sql.0
host.ioBroker-Pi 2019-02-27 17:21:47.669 info "system.adapter.sql.0" disabled
host.ioBroker-Pi 2019-02-27 17:21:47.668 info object change system.adapter.sql.0
sql.0 2019-02-27 17:21:47.668 info Adapter is disabled => stop
host.ioBroker-Pi 2019-02-27 17:21:47.216 info instance system.adapter.scenes.0 terminated with code 0 (OK)
scenes.0 2019-02-27 17:21:47.196 info terminating
scenes.0 2019-02-27 17:21:46.682 info Adapter is disabled => stop
host.ioBroker-Pi 2019-02-27 17:21:46.682 info stopInstance system.adapter.scenes.0 killing pid 9207
host.ioBroker-Pi 2019-02-27 17:21:46.682 info stopInstance system.adapter.scenes.0
host.ioBroker-Pi 2019-02-27 17:21:46.681 info "system.adapter.scenes.0" disabled
host.ioBroker-Pi 2019-02-27 17:21:46.680 info object change system.adapter.scenes.0
host.ioBroker-Pi 2019-02-27 17:21:45.510 info object change system.adapter.milight.0
host.ioBroker-Pi 2019-02-27 17:21:44.303 info object change system.adapter.javascript.0
host.ioBroker-Pi 2019-02-27 17:21:43.539 info object change system.adapter.iot.0
host.ioBroker-Pi 2019-02-27 17:21:32.715 info object change system.adapter.history.0
host.ioBroker-Pi 2019-02-27 17:21:31.504 info object change system.adapter.discovery.0
host.ioBroker-Pi 2019-02-27 17:21:29.564 info object change system.adapter.cloud.0
host.ioBroker-Pi 2019-02-27 17:21:28.572 info object change system.adapter.broadlink2.0
host.ioBroker-Pi 2019-02-27 17:21:27.443 info object change system.adapter.backitup.0
host.ioBroker-Pi 2019-02-27 17:21:26.014 info object change system.adapter.alexa2.0
scenes.0 2019-02-27 16:57:01.792 info starting. Version 1.1.0 in /opt/iobroker/node_modules/iobroker.scenes, node: v8.15.0
host.ioBroker-Pi 2019-02-27 16:57:00.565 info instance system.adapter.scenes.0 started with pid 9207
sql.0 2019-02-27 16:57:00.121 info enabled logging of Aussentemperatur, Alias=true, 2 points now activated
sql.0 2019-02-27 16:57:00.120 info enabled logging of Luftfeuchtigkeit Aussen, Alias=true, 1 points now activated
sql.0 2019-02-27 16:57:00.075 info Connected to mysql
sql.0 2019-02-27 16:56:59.768 info starting. Version 1.9.4 in /opt/iobroker/node_modules/iobroker.sql, node: v8.15.0
host.ioBroker-Pi 2019-02-27 16:56:56.568 info instance system.adapter.sql.0 started with pid 9196
host.ioBroker-Pi 2019-02-27 16:56:56.555 info starting 2 instances
host.ioBroker-Pi 2019-02-27 16:56:56.541 info 19 instances found
host.ioBroker-Pi 2019-02-27 16:56:56.185 info InMemoryDB 192.168.178.21:9001 connected
host.ioBroker-Pi 2019-02-27 16:56:27.082 info All instances are stopped.
host.ioBroker-Pi 2019-02-27 16:56:27.081 info instance system.adapter.sql.0 terminated with code 0 (OK)
host.ioBroker-Pi 2019-02-27 16:56:25.541 info stopInstance timeout "2000 system.adapter.sql.0 killing pid 8773
host.ioBroker-Pi 2019-02-27 16:56:25.064 info instance system.adapter.scenes.0 terminated with code 0 (OK)
host.ioBroker-Pi 2019-02-27 16:56:23.542 info stopInstance system.adapter.scenes.0 killing pid 8784
host.ioBroker-Pi 2019-02-27 16:56:23.541 info stopInstance system.adapter.scenes.0
host.ioBroker-Pi 2019-02-27 16:56:23.541 info stopInstance system.adapter.sql.0
host.ioBroker-Pi 2019-02-27 16:56:23.539 warn Slave controller detected disconnection. Stop all instances.
scenes.0 2019-02-27 16:18:51.470 info starting. Version 1.1.0 in /opt/iobroker/node_modules/iobroker.scenes, node: v8.15.0
sql.0 2019-02-27 16:18:50.290 info enabled logging of Aussentemperatur, Alias=true, 2 points now activated
sql.0 2019-02-27 16:18:50.289 info enabled logging of Luftfeuchtigkeit Aussen, Alias=true, 1 points now activated
host.ioBroker-Pi 2019-02-27 16:18:50.266 info instance system.adapter.scenes.0 started with pid 8784
sql.0 2019-02-27 16:18:50.216 info Connected to mysql
sql.0 2019-02-27 16:18:49.906 info starting. Version 1.9.4 in /opt/iobroker/node_modules/iobroker.sql, node: v8.15.0
host.ioBroker-Pi 2019-02-27 16:18:46.270 info instance system.adapter.sql.0 started with pid 8773
host.ioBroker-Pi 2019-02-27 16:18:46.256 info starting 2 instances
host.ioBroker-Pi 2019-02-27 16:18:46.251 info 19 instances found
host.ioBroker-Pi 2019-02-27 16:18:45.904 info InMemoryDB 192.168.178.21:9001 connected
host.ioBroker-Pi 2019-02-27 16:18:25.167 info All instances are stopped.
host.ioBroker-Pi 2019-02-27 16:18:25.166 info instance system.adapter.sql.0 terminated with code 0 (OK)
host.ioBroker-Pi 2019-02-27 16:18:23.626 info stopInstance timeout "2000 system.adapter.sql.0 killing pid 8701
host.ioBroker-Pi 2019-02-27 16:18:23.147 info instance system.adapter.scenes.0 terminated with code 0 (OK)
host.ioBroker-Pi 2019-02-27 16:18:21.626 info stopInstance system.adapter.scenes.0 killing pid 8708
host.ioBroker-Pi 2019-02-27 16:18:21.626 info stopInstance system.adapter.scenes.0
host.ioBroker-Pi 2019-02-27 16:18:21.625 info stopInstance system.adapter.sql.0
host.ioBroker-Pi 2019-02-27 16:18:21.624 warn Slave controller detected disconnection. Stop all instances.
scenes.0 2019-02-27 16:18:05.552 error at onwrite (_stream_writable.js:439:5)
scenes.0 2019-02-27 16:18:05.552 error at onwriteError (_stream_writable.js:417:12)
scenes.0 2019-02-27 16:18:05.552 error at Socket.emit (events.js:211:7)
scenes.0 2019-02-27 16:18:05.552 error at emitOne (events.js:116:13)
scenes.0 2019-02-27 16:18:05.552 error at WebSocket.finalize (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/ws/lib/WebSocket.js:182:41)
scenes.0 2019-02-27 16:18:05.552 error at WebSocket.emit (events.js:211:7)
scenes.0 2019-02-27 16:18:05.552 error at emitOne (events.js:116:13)
scenes.0 2019-02-27 16:18:05.552 error at WebSocket.onError (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/ws/lib/EventTarget.js:109:16)
scenes.0 2019-02-27 16:18:05.552 error at WebSocket.ws.onerror (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/engine.io-client/lib/transports/websocket.js:150:10)
scenes.0 2019-02-27 16:18:05.552 error at WS.Transport.onError (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/engine.io-client/lib/transport.js:64:13)
scenes.0 2019-02-27 16:18:05.552 error Error: websocket error
scenes.0 2019-02-27 16:18:05.546 error websocket error
host.ioBroker-Pi 2019-02-27 16:18:02.345 error at _combinedTickCallback (internal/process/next_tick.js:139:11)
host.ioBroker-Pi 2019-02-27 16:18:02.345 error at emitErrorNT (internal/streams/destroy.js:66:8)
host.ioBroker-Pi 2019-02-27 16:18:02.345 error at Socket.emit (events.js:211:7)
host.ioBroker-Pi 2019-02-27 16:18:02.345 error at emitOne (events.js:116:13)
host.ioBroker-Pi 2019-02-27 16:18:02.345 error at WebSocket.finalize (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/ws/lib/WebSocket.js:182:41)
host.ioBroker-Pi 2019-02-27 16:18:02.345 error at WebSocket.emit (events.js:211:7)
host.ioBroker-Pi 2019-02-27 16:18:02.345 error at emitOne (events.js:116:13)
host.ioBroker-Pi 2019-02-27 16:18:02.345 error at WebSocket.onError (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/ws/lib/EventTarget.js:109:16)
host.ioBroker-Pi 2019-02-27 16:18:02.345 error at WebSocket.ws.onerror (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/engine.io-client/lib/transports/websocket.js:150:10)
host.ioBroker-Pi 2019-02-27 16:18:02.345 error at WS.Transport.onError (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/engine.io-client/lib/transport.js:64:13)
host.ioBroker-Pi 2019-02-27 16:18:02.345 error Error: websocket error
host.ioBroker-Pi 2019-02-27 16:18:02.343 error websocket error
sql.0 2019-02-27 16:18:01.927 error at _combinedTickCallback (internal/process/next_tick.js:139:11)
sql.0 2019-02-27 16:18:01.927 error at emitErrorNT (internal/streams/destroy.js:66:8)
sql.0 2019-02-27 16:18:01.927 error at Socket.emit (events.js:211:7)
sql.0 2019-02-27 16:18:01.927 error at emitOne (events.js:116:13)
sql.0 2019-02-27 16:18:01.927 error at WebSocket.finalize (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/ws/lib/WebSocket.js:182:41)
sql.0 2019-02-27 16:18:01.927 error at WebSocket.emit (events.js:211:7)
sql.0 2019-02-27 16:18:01.927 error at emitOne (events.js:116:13)
sql.0 2019-02-27 16:18:01.927 error at WebSocket.onError (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/ws/lib/EventTarget.js:109:16)
sql.0 2019-02-27 16:18:01.927 error at WebSocket.ws.onerror (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/engine.io-client/lib/transports/websocket.js:150:10)
sql.0 2019-02-27 16:18:01.927 error at WS.Transport.onError (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/engine.io-client/lib/transport.js:64:13)
sql.0 2019-02-27 16:18:01.927 error Error: websocket error
sql.0 2019-02-27 16:18:01.924 error websocket error
sql.0 2019-02-27 16:10:05.321 info enabled logging of Aussentemperatur, Alias=true, 2 points now activated
sql.0 2019-02-27 16:10:05.319 info enabled logging of Luftfeuchtigkeit Aussen, Alias=true, 1 points now activated
sql.0 2019-02-27 16:10:05.265 info Connected to mysql
scenes.0 2019-02-27 16:10:05.183 info starting. Version 1.1.0 in /opt/iobroker/node_modules/iobroker.scenes, node: v8.15.0
sql.0 2019-02-27 16:10:04.945 info starting. Version 1.9.4 in /opt/iobroker/node_modules/iobroker.sql, node: v8.15.0
host.ioBroker-Pi 2019-02-27 16:10:03.940 info instance system.adapter.scenes.0 started with pid 8708
host.ioBroker-Pi 2019-02-27 16:09:59.938 info instance system.adapter.sql.0 started with pid 8701
host.ioBroker-Pi 2019-02-27 16:09:59.927 info starting 2 instances
host.ioBroker-Pi 2019-02-27 16:09:59.920 info 19 instances found
host.ioBroker-Pi 2019-02-27 16:09:59.554 info InMemoryDB 192.168.178.21:9001 connected
host.ioBroker-Pi 2019-02-27 16:09:56.022 info All instances are stopped.
host.ioBroker-Pi 2019-02-27 16:09:56.021 info instance system.adapter.sql.0 terminated with code 7 (Adapter already running)
sql.0 2019-02-27 16:09:55.987 error already running
host.ioBroker-Pi 2019-02-27 16:09:55.893 info instance system.adapter.scenes.0 terminated with code 0 (OK)
host.ioBroker-Pi 2019-02-27 16:09:54.371 info stopInstance system.adapter.scenes.0 killing pid 8653
host.ioBroker-Pi 2019-02-27 16:09:54.371 info stopInstance system.adapter.scenes.0
host.ioBroker-Pi 2019-02-27 16:09:54.370 info stopInstance system.adapter.sql.0
host.ioBroker-Pi 2019-02-27 16:09:54.369 warn Slave controller detected disconnection. Stop all instances.
scenes.0 2019-02-27 16:04:56.075 info restartAdapter
scenes.0 2019-02-27 16:04:50.010 info restartAdapter
scenes.0 2019-02-27 16:04:44.332 info restartAdapter
scenes.0 2019-02-27 16:04:36.927 info restartAdapter
scenes.0 2019-02-27 16:04:30.637 info restartAdapter
scenes.0 2019-02-27 16:04:25.727 info restartAdapter
scenes.0 2019-02-27 16:03:49.480 info restartAdapter
scenes.0 2019-02-27 16:03:43.630 info restartAdapter
scenes.0 2019-02-27 16:03:36.187 info restartAdapter
scenes.0 2019-02-27 16:02:21.021 info restartAdapter
scenes.0 2019-02-27 16:02:17.573 info restartAdapter
scenes.0 2019-02-27 16:02:12.172 info restartAdapter
scenes.0 2019-02-27 16:02:11.393 info restartAdapter
scenes.0 2019-02-27 16:02:08.878 info restartAdapter
scenes.0 2019-02-27 16:02:03.010 info restartAdapter
scenes.0 2019-02-27 16:01:57.043 info restartAdapter
scenes.0 2019-02-27 16:01:48.795 info restartAdapter
scenes.0 2019-02-27 16:01:48.769 info restartAdapter
scenes.0 2019-02-27 16:01:48.736 info restartAdapter
scenes.0 2019-02-27 16:01:48.694 info restartAdapter
scenes.0 2019-02-27 16:01:48.655 info restartAdapter
scenes.0 2019-02-27 16:01:48.620 info restartAdapter
scenes.0 2019-02-27 16:01:48.613 info restartAdapter
scenes.0 2019-02-27 16:01:48.595 info restartAdapter
scenes.0 2019-02-27 16:01:41.101 info starting. Version 1.1.0 in /opt/iobroker/node_modules/iobroker.scenes, node: v8.15.0
host.ioBroker-Pi 2019-02-27 16:01:39.861 info instance system.adapter.scenes.0 started with pid 8653
sql.0 2019-02-27 16:01:39.445 info enabled logging of Aussentemperatur, Alias=true, 2 points now activated
sql.0 2019-02-27 16:01:39.444 info enabled logging of Luftfeuchtigkeit Aussen, Alias=true, 1 points now activated
sql.0 2019-02-27 16:01:39.388 info Connected to mysql
sql.0 2019-02-27 16:01:39.080 info starting. Version 1.9.4 in /opt/iobroker/node_modules/iobroker.sql, node: v8.15.0
host.ioBroker-Pi 2019-02-27 16:01:35.861 info instance system.adapter.sql.0 started with pid 8642
host.ioBroker-Pi 2019-02-27 16:01:35.850 info starting 2 instances
host.ioBroker-Pi 2019-02-27 16:01:35.846 info 19 instances found
host.ioBroker-Pi 2019-02-27 16:01:35.553 info InMemoryDB 192.168.178.21:9001 connected
host.ioBroker-Pi 2019-02-27 16:01:13.882 info All instances are stopped.
host.ioBroker-Pi 2019-02-27 16:01:13.881 info instance system.adapter.sql.0 terminated with code 0 (OK)
host.ioBroker-Pi 2019-02-27 16:01:12.352 info stopInstance timeout "2000 system.adapter.sql.0 killing pid 8621
host.ioBroker-Pi 2019-02-27 16:01:11.872 info instance system.adapter.scenes.0 terminated with code 0 (OK)
host.ioBroker-Pi 2019-02-27 16:01:10.351 info stopInstance system.adapter.scenes.0 killing pid 8632
host.ioBroker-Pi 2019-02-27 16:01:10.351 info stopInstance system.adapter.scenes.0
host.ioBroker-Pi 2019-02-27 16:01:10.350 info stopInstance system.adapter.sql.0
host.ioBroker-Pi 2019-02-27 16:01:10.349 warn Slave controller detected disconnection. Stop all instances.
scenes.0 2019-02-27 16:00:58.613 error at onwrite (_stream_writable.js:439:5)
scenes.0 2019-02-27 16:00:58.613 error at onwriteError (_stream_writable.js:417:12)
scenes.0 2019-02-27 16:00:58.613 error at Socket.emit (events.js:211:7)
scenes.0 2019-02-27 16:00:58.613 error at emitOne (events.js:116:13)
scenes.0 2019-02-27 16:00:58.613 error at WebSocket.finalize (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/ws/lib/WebSocket.js:182:41)
scenes.0 2019-02-27 16:00:58.613 error at WebSocket.emit (events.js:211:7)
scenes.0 2019-02-27 16:00:58.613 error at emitOne (events.js:116:13)
scenes.0 2019-02-27 16:00:58.613 error at WebSocket.onError (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/ws/lib/EventTarget.js:109:16)
scenes.0 2019-02-27 16:00:58.613 error at WebSocket.ws.onerror (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/engine.io-client/lib/transports/websocket.js:150:10)
scenes.0 2019-02-27 16:00:58.613 error at WS.Transport.onError (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/engine.io-client/lib/transport.js:64:13)
scenes.0 2019-02-27 16:00:58.613 error Error: websocket error
scenes.0 2019-02-27 16:00:58.609 error websocket error
sql.0 2019-02-27 16:00:52.575 error at _combinedTickCallback (internal/process/next_tick.js:139:11)
sql.0 2019-02-27 16:00:52.575 error at emitErrorNT (internal/streams/destroy.js:66:8)
sql.0 2019-02-27 16:00:52.575 error at Socket.emit (events.js:211:7)
sql.0 2019-02-27 16:00:52.575 error at emitOne (events.js:116:13)
sql.0 2019-02-27 16:00:52.575 error at WebSocket.finalize (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/ws/lib/WebSocket.js:182:41)
sql.0 2019-02-27 16:00:52.575 error at WebSocket.emit (events.js:211:7)
sql.0 2019-02-27 16:00:52.575 error at emitOne (events.js:116:13)
sql.0 2019-02-27 16:00:52.575 error at WebSocket.onError (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/ws/lib/EventTarget.js:109:16)
sql.0 2019-02-27 16:00:52.575 error at WebSocket.ws.onerror (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/engine.io-client/lib/transports/websocket.js:150:10)
sql.0 2019-02-27 16:00:52.575 error at WS.Transport.onError (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/engine.io-client/lib/transport.js:64:13)
sql.0 2019-02-27 16:00:52.575 error Error: websocket error
sql.0 2019-02-27 16:00:52.571 error websocket error
host.ioBroker-Pi 2019-02-27 16:00:52.566 error at _combinedTickCallback (internal/process/next_tick.js:139:11)
host.ioBroker-Pi 2019-02-27 16:00:52.566 error at emitErrorNT (internal/streams/destroy.js:66:8)
host.ioBroker-Pi 2019-02-27 16:00:52.566 error at Socket.emit (events.js:211:7)
host.ioBroker-Pi 2019-02-27 16:00:52.566 error at emitOne (events.js:116:13)
host.ioBroker-Pi 2019-02-27 16:00:52.566 error at WebSocket.finalize (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/ws/lib/WebSocket.js:182:41)
host.ioBroker-Pi 2019-02-27 16:00:52.566 error at WebSocket.emit (events.js:211:7)
host.ioBroker-Pi 2019-02-27 16:00:52.566 error at emitOne (events.js:116:13)
host.ioBroker-Pi 2019-02-27 16:00:52.566 error at WebSocket.onError (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/ws/lib/EventTarget.js:109:16)
host.ioBroker-Pi 2019-02-27 16:00:52.566 error at WebSocket.ws.onerror (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/engine.io-client/lib/transports/websocket.js:150:10)
host.ioBroker-Pi 2019-02-27 16:00:52.566 error at WS.Transport.onError (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/engine.io-client/lib/transport.js:64:13)
host.ioBroker-Pi 2019-02-27 16:00:52.566 error Error: websocket error
host.ioBroker-Pi 2019-02-27 16:00:52.564 error websocket error
scenes.0 2019-02-27 16:00:29.944 info restartAdapter
scenes.0 2019-02-27 16:00:28.526 info restartAdapter
scenes.0 2019-02-27 16:00:17.753 info restartAdapter
host.ioBroker-Pi 2019-02-27 15:59:59.086 info object change system.adapter.broadlink2.0
scenes.0 2019-02-27 15:58:47.084 info restartAdapter
scenes.0 2019-02-27 15:58:47.081 info restartAdapter
scenes.0 2019-02-27 15:58:47.030 info restartAdapter
scenes.0 2019-02-27 15:58:43.508 info starting. Version 1.1.0 in /opt/iobroker/node_modules/iobroker.scenes, node: v8.15.0
host.ioBroker-Pi 2019-02-27 15:58:42.287 info instance system.adapter.scenes.0 started with pid 8632
sql.0 2019-02-27 15:58:41.853 info enabled logging of Aussentemperatur, Alias=true, 2 points now activated
sql.0 2019-02-27 15:58:41.852 info enabled logging of Luftfeuchtigkeit Aussen, Alias=true, 1 points now activated
sql.0 2019-02-27 15:58:41.805 info Connected to mysql
sql.0 2019-02-27 15:58:41.500 info starting. Version 1.9.4 in /opt/iobroker/node_modules/iobroker.sql, node: v8.15.0
host.ioBroker-Pi 2019-02-27 15:58:38.290 info instance system.adapter.sql.0 started with pid 8621
host.ioBroker-Pi 2019-02-27 15:58:38.277 info starting 2 instances
host.ioBroker-Pi 2019-02-27 15:58:38.273 info 19 instances found
host.ioBroker-Pi 2019-02-27 15:58:37.978 info InMemoryDB 192.168.178.21:9001 connected
host.ioBroker-Pi 2019-02-27 15:58:17.973 info All instances are stopped.
host.ioBroker-Pi 2019-02-27 15:58:17.972 info instance system.adapter.sql.0 terminated with code 0 (OK)
host.ioBroker-Pi 2019-02-27 15:58:16.431 info stopInstance timeout "2000 system.adapter.sql.0 killing pid 8489
host.ioBroker-Pi 2019-02-27 15:58:15.954 info instance system.adapter.scenes.0 terminated with code 0 (OK)
host.ioBroker-Pi 2019-02-27 15:58:14.431 info stopInstance system.adapter.scenes.0 killing pid 8539
host.ioBroker-Pi 2019-02-27 15:58:14.431 info stopInstance system.adapter.scenes.0
host.ioBroker-Pi 2019-02-27 15:58:14.430 info stopInstance system.adapter.sql.0
host.ioBroker-Pi 2019-02-27 15:58:14.429 warn Slave controller detected disconnection. Stop all instances.
sql.0 2019-02-27 15:57:50.871 error at _combinedTickCallback (internal/process/next_tick.js:139:11)
sql.0 2019-02-27 15:57:50.871 error at emitErrorNT (internal/streams/destroy.js:66:8)
sql.0 2019-02-27 15:57:50.871 error at Socket.emit (events.js:211:7)
sql.0 2019-02-27 15:57:50.871 error at emitOne (events.js:116:13)
sql.0 2019-02-27 15:57:50.871 error at WebSocket.finalize (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/ws/lib/WebSocket.js:182:41)
sql.0 2019-02-27 15:57:50.871 error at WebSocket.emit (events.js:211:7)
sql.0 2019-02-27 15:57:50.871 error at emitOne (events.js:116:13)
sql.0 2019-02-27 15:57:50.871 error at WebSocket.onError (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/ws/lib/EventTarget.js:109:16)
sql.0 2019-02-27 15:57:50.871 error at WebSocket.ws.onerror (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/engine.io-client/lib/transports/websocket.js:150:10)
sql.0 2019-02-27 15:57:50.871 error at WS.Transport.onError (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/engine.io-client/lib/transport.js:64:13)
sql.0 2019-02-27 15:57:50.871 error Error: websocket error
sql.0 2019-02-27 15:57:50.868 error websocket error
host.ioBroker-Pi 2019-02-27 15:57:50.759 error at _combinedTickCallback (internal/process/next_tick.js:139:11)
host.ioBroker-Pi 2019-02-27 15:57:50.759 error at emitErrorNT (internal/streams/destroy.js:66:8)
host.ioBroker-Pi 2019-02-27 15:57:50.759 error at Socket.emit (events.js:211:7)
host.ioBroker-Pi 2019-02-27 15:57:50.759 error at emitOne (events.js:116:13)
host.ioBroker-Pi 2019-02-27 15:57:50.759 error at WebSocket.finalize (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/ws/lib/WebSocket.js:182:41)
host.ioBroker-Pi 2019-02-27 15:57:50.759 error at WebSocket.emit (events.js:211:7)
host.ioBroker-Pi 2019-02-27 15:57:50.759 error at emitOne (events.js:116:13)
host.ioBroker-Pi 2019-02-27 15:57:50.759 error at WebSocket.onError (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/ws/lib/EventTarget.js:109:16)
host.ioBroker-Pi 2019-02-27 15:57:50.759 error at WebSocket.ws.onerror (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/engine.io-client/lib/transports/websocket.js:150:10)
host.ioBroker-Pi 2019-02-27 15:57:50.759 error at WS.Transport.onError (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/engine.io-client/lib/transport.js:64:13)
host.ioBroker-Pi 2019-02-27 15:57:50.759 error Error: websocket error
host.ioBroker-Pi 2019-02-27 15:57:50.758 error websocket error
scenes.0 2019-02-27 15:57:50.566 error at onwrite (_stream_writable.js:439:5)
scenes.0 2019-02-27 15:57:50.566 error at onwriteError (_stream_writable.js:417:12)
scenes.0 2019-02-27 15:57:50.566 error at Socket.emit (events.js:211:7)
scenes.0 2019-02-27 15:57:50.566 error at emitOne (events.js:116:13)
scenes.0 2019-02-27 15:57:50.566 error at WebSocket.finalize (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/ws/lib/WebSocket.js:182:41)
scenes.0 2019-02-27 15:57:50.566 error at WebSocket.emit (events.js:211:7)
scenes.0 2019-02-27 15:57:50.566 error at emitOne (events.js:116:13)
scenes.0 2019-02-27 15:57:50.566 error at WebSocket.onError (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/ws/lib/EventTarget.js:109:16)
scenes.0 2019-02-27 15:57:50.566 error at WebSocket.ws.onerror (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/engine.io-client/lib/transports/websocket.js:150:10)
scenes.0 2019-02-27 15:57:50.566 error at WS.Transport.onError (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/engine.io-client/lib/transport.js:64:13)
scenes.0 2019-02-27 15:57:50.566 error Error: websocket error
scenes.0 2019-02-27 15:57:50.561 error websocket error
scenes.0 2019-02-27 15:57:50.549 info restartAdapter
scenes.0 2019-02-27 15:57:33.261 info restartAdapter
scenes.0 2019-02-27 15:57:30.577 info restartAdapter
scenes.0 2019-02-27 15:57:27.724 info restartAdapter
scenes.0 2019-02-27 15:57:25.053 info restartAdapter
scenes.0 2019-02-27 15:57:09.406 info restartAdapter
scenes.0 2019-02-27 15:57:08.492 info restartAdapter
scenes.0 2019-02-27 15:56:52.058 info restartAdapter
scenes.0 2019-02-27 15:56:44.429 info restartAdapter
scenes.0 2019-02-27 15:56:40.520 info restartAdapter
scenes.0 2019-02-27 15:56:35.976 info restartAdapter
scenes.0 2019-02-27 15:56:31.540 info restartAdapter
scenes.0 2019-02-27 15:56:26.875 info restartAdapter
scenes.0 2019-02-27 15:56:24.148 info restartAdapter
scenes.0 2019-02-27 15:56:16.401 info restartAdapter
scenes.0 2019-02-27 15:56:09.730 info restartAdapter
scenes.0 2019-02-27 15:55:18.929 info restartAdapter
scenes.0 2019-02-27 15:54:54.049 info restartAdapter
scenes.0 2019-02-27 15:54:19.840 info restartAdapter
scenes.0 2019-02-27 15:54:18.664 info restartAdapter
scenes.0 2019-02-27 15:54:15.297 info restartAdapter
scenes.0 2019-02-27 15:54:09.434 info restartAdapter
scenes.0 2019-02-27 15:53:52.134 info restartAdapter
scenes.0 2019-02-27 15:53:49.564 info restartAdapter
scenes.0 2019-02-27 15:53:48.395 info restartAdapter
scenes.0 2019-02-27 15:53:42.131 info restartAdapter
scenes.0 2019-02-27 15:53:31.701 info restartAdapter
scenes.0 2019-02-27 15:52:51.314 info restartAdapter
scenes.0 2019-02-27 15:52:50.377 info restartAdapter
scenes.0 2019-02-27 15:52:49.483 info restartAdapter
scenes.0 2019-02-27 15:52:41.319 info restartAdapter
host.ioBroker-Pi 2019-02-27 15:52:11.603 info object change system.adapter.broadlink2.0
host.ioBroker-Pi 2019-02-27 15:51:40.614 info object change system.adapter.broadlink2.0
scenes.0 2019-02-27 15:49:55.788 info restartAdapter
scenes.0 2019-02-27 15:49:33.425 info restartAdapter
scenes.0 2019-02-27 15:48:09.323 info restartAdapter
scenes.0 2019-02-27 15:48:07.796 info restartAdapter
scenes.0 2019-02-27 15:48:05.839 info restartAdapter
scenes.0 2019-02-27 15:48:04.440 info restartAdapter
scenes.0 2019-02-27 15:47:54.376 info restartAdapter
scenes.0 2019-02-27 15:47:35.138 info restartAdapter
scenes.0 2019-02-27 15:47:09.890 info restartAdapter
scenes.0 2019-02-27 15:46:48.441 info starting. Version 1.1.0 in /opt/iobroker/node_modules/iobroker.scenes, node: v8.15.0
iobroker 2019-02-27 15:46:47.294 info exit 0
host.ioBroker-Pi 2019-02-27 15:46:47.289 info instance system.adapter.scenes.0 started with pid 8539
host.ioBroker-Pi 2019-02-27 15:46:47.262 info object change system.adapter.scenes.0
iobroker 2019-02-27 15:46:47.255 info host.ioBroker-Pi object system.adapter.scenes.0 created
iobroker 2019-02-27 15:46:47.212 info host.ioBroker-Pi object system.adapter.scenes.0.alive created
iobroker 2019-02-27 15:46:47.175 info host.ioBroker-Pi object system.adapter.scenes.0.connected created
iobroker 2019-02-27 15:46:47.136 info host.ioBroker-Pi object system.adapter.scenes.0.memHeapUsed created
iobroker 2019-02-27 15:46:47.098 info host.ioBroker-Pi object system.adapter.scenes.0.memHeapTotal created
iobroker 2019-02-27 15:46:46.998 info host.ioBroker-Pi object system.adapter.scenes.0.memRss created
iobroker 2019-02-27 15:46:46.960 info host.ioBroker-Pi object system.adapter.scenes.0.uptime created
iobroker 2019-02-27 15:46:46.921 info host.ioBroker-Pi object system.adapter.scenes.0.inputCount created
iobroker 2019-02-27 15:46:46.883 info host.ioBroker-Pi object system.adapter.scenes.0.outputCount created
iobroker 2019-02-27 15:46:46.864 info host.ioBroker-Pi create instance scenes
iobroker 2019-02-27 15:46:46.823 info host.ioBroker-Pi object system.adapter.scenes created
iobroker 2019-02-27 15:46:46.691 info upload [0] scenes.admin /opt/iobroker/node_modules/iobroker.scenes/admin/scenes.png scenes.png image/png
iobroker 2019-02-27 15:46:46.629 info upload [1] scenes.admin /opt/iobroker/node_modules/iobroker.scenes/admin/tab.html tab.html text/html
iobroker 2019-02-27 15:46:46.543 info upload [2] scenes.admin /opt/iobroker/node_modules/iobroker.scenes/admin/tab.js tab.js application/javascript
iobroker 2019-02-27 15:46:46.431 info upload [3] scenes.admin /opt/iobroker/node_modules/iobroker.scenes/admin/words.js words.js application/javascript
iobroker 2019-02-27 15:46:46.404 info got /opt/iobroker/node_modules/iobroker.scenes/admin
iobroker 2019-02-27 15:46:46.377 info host.ioBroker-Pi install adapter scenes
iobroker 2019-02-27 15:46:12.767 info npm install iobroker.scenes --production --save --prefix "/opt/iobroker" (System call)
iobroker 2019-02-27 15:46:11.946 info NPM version: 6.4.1
-
seh ich auch so - kannst du alexa etwas befehlen radio einschalten - setze mal alexa player tunein-station auf auf s25217