2019-10-04 16:18:41.729  - info: host.debian All instances are stopped.
2019-10-04 16:18:50.527  - info: host.debian terminated
2019-10-04 16:42:23.114  - info: host.debian iobroker.js-controller version 2.0.22 js-controller starting
2019-10-04 16:42:23.128  - info: host.debian Copyright (c) 2014-2019 bluefox, 2014 hobbyquaker
2019-10-04 16:42:23.128  - info: host.debian hostname: debian, node: v10.16.3
2019-10-04 16:42:23.129  - info: host.debian ip addresses: 192.168.66.68 fe80::6407:9eff:feb9:ec35
2019-10-04 16:42:23.328  - info: host.debian connected to Objects and States
2019-10-04 16:42:25.464  - info: host.debian Delete state "system.host.debian.compactModeEnabled"
2019-10-04 16:42:25.631  - info: host.debian 70 instances found
2019-10-04 16:42:25.998  - info: host.debian starting 58 instances
2019-10-04 16:42:26.175  - info: host.debian instance system.adapter.admin.0 started with pid 1235
2019-10-04 16:42:26.232  - info: host.debian Some obsolete host states deleted.
2019-10-04 16:42:29.692  - info: admin.0 (1235) starting. Version 3.6.7 in /opt/iobroker/node_modules/iobroker.admin, node: v10.16.3
2019-10-04 16:42:29.807  - info: admin.0 (1235) requesting all states
2019-10-04 16:42:29.817  - info: admin.0 (1235) requesting all objects
2019-10-04 16:42:29.827  - info: admin.0 (1235) Request actual repository...
2019-10-04 16:42:30.053  - info: host.debian instance system.adapter.netatmo.0 started with pid 1250
2019-10-04 16:42:32.928  - info: netatmo.0 (1250) starting. Version 1.3.1 in /opt/iobroker/node_modules/iobroker.netatmo, node: v10.16.3
2019-10-04 16:42:34.375  - info: host.debian Update repository "latest" under "http://download.iobroker.net/sources-dist-latest.json"
2019-10-04 16:42:36.170  - info: host.debian instance system.adapter.mqtt.0 started with pid 1265
2019-10-04 16:42:37.744  - info: admin.0 (1235) Repository received successfully.
2019-10-04 16:42:38.040  - info: host.debian instance scheduled system.adapter.yr.0 6 * * * *
2019-10-04 16:42:38.083  - info: host.debian instance system.adapter.yr.0 started with pid 1276
2019-10-04 16:42:38.489  - info: admin.0 (1235) received all states
2019-10-04 16:42:38.973  - info: mqtt.0 (1265) starting. Version 2.1.1 in /opt/iobroker/node_modules/iobroker.mqtt, node: v10.16.3
2019-10-04 16:42:41.126  - info: mqtt.0 (1265) Starting MQTT '  server on port 1883
2019-10-04 16:42:41.406  - info: yr.0 (1276) starting. Version 2.0.3 in /opt/iobroker/node_modules/iobroker.yr, node: v10.16.3
2019-10-04 16:42:42.052  - info: yr.0 (1276) got weather data from yr.no
2019-10-04 16:42:42.073  - info: host.debian instance system.adapter.smartmeter.0 started with pid 1295
2019-10-04 16:42:42.100  - info: admin.0 (1235) received all objects
2019-10-04 16:42:42.749  - info: admin.0 (1235) http server listening on port 8081
2019-10-04 16:42:42.750  - info: admin.0 (1235) Use link "http://localhost:8081" to configure.
2019-10-04 16:42:43.826  - info: mqtt.0 (1265) Client [MHI Schlafzimmer] connected with secret 1570200163802_2288
2019-10-04 16:42:44.189  - info: mqtt.0 (1265) Client [MHI Wintergarten] connected with secret 1570200164176_493
2019-10-04 16:42:44.316  - info: mqtt.0 (1265) Client [MHI Wintergarten] subscribes on topic "Wintergarten/Klima/Setpoint"
2019-10-04 16:42:44.317  - info: mqtt.0 (1265) Client [MHI Wintergarten] subscribes on topic "Wintergarten/Klima/State"
2019-10-04 16:42:44.318  - info: mqtt.0 (1265) Client [MHI Wintergarten] subscribes on topic "Wintergarten/Klima/Vanes"
2019-10-04 16:42:44.319  - info: mqtt.0 (1265) Client [MHI Wintergarten] subscribes on topic "Wintergarten/Klima/Fanspeed"
2019-10-04 16:42:44.319  - info: mqtt.0 (1265) Client [MHI Wintergarten] subscribes on topic "Wintergarten/Klima/service"
2019-10-04 16:42:44.334  - info: mqtt.0 (1265) Client [MHI Schlafzimmer] subscribes on topic "Schlafzimmer/Klima/Setpoint"
2019-10-04 16:42:44.340  - info: mqtt.0 (1265) Client [MHI Schlafzimmer] subscribes on topic "Schlafzimmer/Klima/State"
2019-10-04 16:42:44.344  - info: mqtt.0 (1265) Client [MHI Schlafzimmer] subscribes on topic "Schlafzimmer/Klima/Vanes"
2019-10-04 16:42:44.345  - info: mqtt.0 (1265) Client [MHI Schlafzimmer] subscribes on topic "Schlafzimmer/Klima/Fanspeed"
2019-10-04 16:42:44.349  - info: mqtt.0 (1265) Client [MHI Schlafzimmer] subscribes on topic "Schlafzimmer/Klima/service"
2019-10-04 16:42:45.684  - info: smartmeter.0 (1295) starting. Version 1.2.2 in /opt/iobroker/node_modules/iobroker.smartmeter, node: v10.16.3
2019-10-04 16:42:46.623  - info: smartmeter.0 (1295) Received 7 values, 7 updated
2019-10-04 16:42:47.497  - info: host.debian instance system.adapter.yr.0 terminated with code 0 (NO_ERROR)
2019-10-04 16:42:50.035  - info: host.debian instance system.adapter.history.0 started with pid 1310
2019-10-04 16:42:51.414  - info: history.0 (1310) starting. Version 1.8.7 in /opt/iobroker/node_modules/iobroker.history, node: v10.16.3
2019-10-04 16:42:53.266  - info: history.0 (1310) enabled logging of hm-rpc.0.MEQ1573948.2.ACTUAL_TEMPERATURE (Count=1), Alias=false
2019-10-04 16:42:53.267  - info: history.0 (1310) enabled logging of javascript.0.Strom.VerbrauchEG (Count=2), Alias=false
2019-10-04 16:42:53.267  - info: history.0 (1310) enabled logging of javascript.0.Strom.VerbrauchOG (Count=3), Alias=false
2019-10-04 16:42:53.267  - info: history.0 (1310) enabled logging of hm-rpc.0.NEQ0116733.2.POWER (Count=4), Alias=false
2019-10-04 16:42:53.268  - info: history.0 (1310) enabled logging of wiffi-wz.0.root.192_168_66_134.w_temperatur (Count=5), Alias=false
2019-10-04 16:42:53.268  - info: history.0 (1310) enabled logging of netatmo.0.CoyoteNetatmo.Outdoor.Temperature.Temperature (Count=6), Alias=false
2019-10-04 16:42:53.268  - info: history.0 (1310) enabled logging of smartmeter.0.1-0:15_7_0_255.value (Count=7), Alias=false
2019-10-04 16:42:53.268  - info: history.0 (1310) enabled logging of wiffi-wz.0.root.192_168_66_22.wiffi_pump (Count=8), Alias=false
2019-10-04 16:42:53.269  - info: history.0 (1310) enabled logging of netatmo.0.CoyoteNetatmo.Indoor.Temperature.Temperature (Count=9), Alias=false
2019-10-04 16:42:54.044  - info: host.debian instance system.adapter.zoneminder.0 started with pid 1325
2019-10-04 16:42:57.767  - info: zoneminder.0 (1325) starting. Version 0.2.1 in /opt/iobroker/node_modules/iobroker.zoneminder, node: v10.16.3
2019-10-04 16:42:58.146  - info: host.debian instance system.adapter.hm-rpc.1 started with pid 1340
2019-10-04 16:42:58.172  - info: zoneminder.0 (1325) check group user admin group admin: false
2019-10-04 16:42:58.566  - info: zoneminder.0 (1325) check user admin pw ioboker: true
2019-10-04 16:43:00.191  - info: hm-rpc.1 (1340) starting. Version 1.10.0 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v10.16.3
2019-10-04 16:43:00.384  - info: hm-rpc.1 (1340) [META] Meta data updated
2019-10-04 16:43:01.851  - info: hm-rpc.1 (1340) xmlrpc server is trying to listen on 192.168.66.68:2000
2019-10-04 16:43:01.854  - info: hm-rpc.1 (1340) xmlrpc client is trying to connect to 192.168.66.36:2000/ with ["http://192.168.66.68:2000","hm-rpc.1"]
2019-10-04 16:43:01.887  - info: hm-rpc.1 (1340) xmlrpc <- system.listMethods ["hm-rpc.1"]
2019-10-04 16:43:01.899  - info: hm-rpc.1 (1340) xmlrpc <- listDevices ["hm-rpc.1"]
2019-10-04 16:43:02.028  - info: hm-rpc.1 (1340) xmlrpc -> 237 devices
2019-10-04 16:43:02.135  - info: hm-rpc.1 (1340) Connected
2019-10-04 16:43:06.035  - info: host.debian instance system.adapter.sonos.0 started with pid 1355
2019-10-04 16:43:10.053  - info: host.debian instance system.adapter.iqontrol.0 started with pid 1366
2019-10-04 16:43:10.379  - info: sonos.0 (1355) starting. Version 1.8.0 in /opt/iobroker/node_modules/iobroker.sonos, node: v10.16.3
2019-10-04 16:43:11.345  - info: sonos.0 (1355) http sonos server listening on port 8080
2019-10-04 16:43:14.040  - info: host.debian instance system.adapter.simple-api.0 started with pid 1381
2019-10-04 16:43:15.341  - info: iqontrol.0 (1366) starting. Version 0.2.9 in /opt/iobroker/node_modules/iobroker.iqontrol, node: v10.16.3
2019-10-04 16:43:15.446  - info: iqontrol.0 (1366) Creating Toolbar...
2019-10-04 16:43:15.678  - info: iqontrol.0 (1366) Creating Views...
2019-10-04 16:43:17.019  - info: simple-api.0 (1381) starting. Version 2.1.2 in /opt/iobroker/node_modules/iobroker.simple-api, node: v10.16.3
2019-10-04 16:43:17.168  - info: simple-api.0 (1381) simpleAPI server listening on port 8087
2019-10-04 16:43:17.170  - info: simple-api.0 (1381) Allow states only when user is owner: false
2019-10-04 16:43:17.182  - info: simple-api.0 (1381) http server listening on port 8087
2019-10-04 16:43:18.076  - info: host.debian instance system.adapter.socketio.0 started with pid 1400
2019-10-04 16:43:22.067  - info: host.debian instance system.adapter.iqontrol.1 started with pid 1411
2019-10-04 16:43:22.817  - info: socketio.0 (1400) starting. Version 2.1.2 in /opt/iobroker/node_modules/iobroker.socketio, node: v10.16.3
2019-10-04 16:43:23.049  - info: socketio.0 (1400) socket.io server listening on port 8084
2019-10-04 16:43:25.573  - info: iqontrol.1 (1411) starting. Version 0.2.9 in /opt/iobroker/node_modules/iobroker.iqontrol, node: v10.16.3
2019-10-04 16:43:25.682  - info: iqontrol.1 (1411) Creating Toolbar...
2019-10-04 16:43:25.859  - info: iqontrol.1 (1411) Creating Views...
2019-10-04 16:43:30.054  - info: host.debian instance system.adapter.iot.0 started with pid 1430
2019-10-04 16:43:30.865  - info: iqontrol.1 (1411) Creating Options...
2019-10-04 16:43:30.884  - info: iqontrol.1 (1411) Deleting unused Objects...
2019-10-04 16:43:34.028  - info: host.debian instance scheduled system.adapter.daswetter.0 */15 * * * *
2019-10-04 16:43:38.032  - info: host.debian instance system.adapter.harmony.0 started with pid 1449
2019-10-04 16:43:40.274  - info: iot.0 (1430) starting. Version 1.1.8 in /opt/iobroker/node_modules/iobroker.iot, node: v10.16.3
2019-10-04 16:43:40.360  - info: iot.0 (1430) Connecting with a18wym7vjdl22g.iot.eu-west-1.amazonaws.com
2019-10-04 16:43:41.927  - error: iot.0 (1430) Api-Secret cannot be updated: Invalid password or user not exists
2019-10-04 16:43:42.067  - info: host.debian instance system.adapter.telegram.0 started with pid 1460
2019-10-04 16:43:45.425  - info: iot.0 (1430) Connection changed: connect
2019-10-04 16:43:45.685  - info: harmony.0 (1449) starting. Version 1.2.2 in /opt/iobroker/node_modules/iobroker.harmony, node: v10.16.3
2019-10-04 16:43:45.956  - info: harmony.0 (1449) [DISCOVER] Searching for Harmony Hubs on 255.255.255.255
2019-10-04 16:43:47.270  - info: harmony.0 (1449) [DISCOVER] Discovered CoyoteHarmonyHub (192.168.66.51) and will try to connect
2019-10-04 16:43:48.101  - info: harmony.0 (1449) [CONNECT] Connecting to CoyoteHarmonyHub (192.168.66.51)
2019-10-04 16:43:49.590  - info: harmony.0 (1449) [CONNECT] Connected to CoyoteHarmonyHub (192.168.66.51)
2019-10-04 16:43:50.735  - info: harmony.0 (1449) [PROCESS] Synced hub config for CoyoteHarmonyHub (192.168.66.51)
2019-10-04 16:43:54.035  - info: host.debian instance system.adapter.adapter-studio.0 started with pid 1490
2019-10-04 16:43:56.539  - info: vis.0 (1479) starting. Version 1.2.1 in /opt/iobroker/node_modules/iobroker.vis, node: v10.16.3
2019-10-04 16:43:56.722  - info: telegram.0 (1460) starting. Version 1.4.3 in /opt/iobroker/node_modules/iobroker.telegram, node: v10.16.3
2019-10-04 16:43:57.069  - info: vis.0 (1479) vis license is OK.
2019-10-04 16:43:58.136  - info: host.debian instance system.adapter.unifi.0 started with pid 1505
2019-10-04 16:43:58.652  - info: iot.0 (1430) hm-rpc.0.NEQ0751272.1 is auto added with type  dimmer.
2019-10-04 16:43:58.850  - info: iot.0 (1430) hm-rpc.1.MEQ0352008.3 is auto added with type  blind.
2019-10-04 16:43:59.340  - info: iot.0 (1430) hm-rpc.0.LEQ1259443.1 is auto added with type  dimmer.
2019-10-04 16:43:59.463  - info: iot.0 (1430) hm-rpc.0.MEQ0220989.1 is auto added with type  windowTilt.
2019-10-04 16:43:59.579  - info: iot.0 (1430) hm-rpc.0.NEQ0533309.1 is auto added with type  temperature.
2019-10-04 16:43:59.685  - info: iot.0 (1430) hm-rpc.0.OEQ0301619.1 is auto added with type  temperature.
2019-10-04 16:43:59.783  - info: iot.0 (1430) hm-rpc.0.OEQ1426971.1 is auto added with type  info.
2019-10-04 16:43:59.887  - info: iot.0 (1430) hm-rpc.1.MEQ1132540.3 is auto added with type  blind.
2019-10-04 16:44:00.040  - info: iot.0 (1430) hm-rpc.1.MEQ1132748.3 is auto added with type  blind.
2019-10-04 16:44:00.168  - info: iot.0 (1430) hm-rpc.0.MEQ1405861.1 is auto added with type  info.
2019-10-04 16:44:00.516  - info: iot.0 (1430) hm-rpc.0.MEQ1573948.2 is auto added with type  thermostat.
2019-10-04 16:44:00.634  - info: iot.0 (1430) hm-rpc.0.LEQ1242420.1 is auto added with type  info.
2019-10-04 16:44:00.692  - info: iot.0 (1430) hm-rpc.0.MEQ0222256.1 is auto added with type  windowTilt.
2019-10-04 16:44:00.705  - info: iot.0 (1430) hm-rpc.0.LEQ1252590.1.STATE is auto added with type  info.
2019-10-04 16:44:00.856  - info: iot.0 (1430) hm-rpc.0.LEQ1252590.1 is auto added with type  info.
2019-10-04 16:44:06.053  - info: host.debian instance system.adapter.tankerkoenig.0 started with pid 1520
2019-10-04 16:44:09.195  - info: unifi.0 (1505) starting. Version 0.3.1 in /opt/iobroker/node_modules/iobroker.unifi, node: v10.16.3
2019-10-04 16:44:09.787  - info: adapter-studio.0 (1490) starting. Version 0.7.0 in /opt/iobroker/node_modules/iobroker.adapter-studio, node: v10.16.3
2019-10-04 16:44:09.942  - info: adapter-studio.0 (1490) linux
2019-10-04 16:44:09.943  - info: adapter-studio.0 (1490) /opt/iobroker/node_modules/iobroker.adapter-studio
2019-10-04 16:44:10.113  - info: host.debian instance system.adapter.hm-rpc.0 started with pid 1540
2019-10-04 16:44:10.603  - info: vis.0 (1479) Terminated (NO_ERROR): Without reason
2019-10-04 16:44:09.467  - info: unifi.0 (1505) Starting UniFi-Controller query
2019-10-04 16:44:09.467  - info: unifi.0 (1505) update_interval = 60
2019-10-04 16:44:09.468  - info: unifi.0 (1505) controller = 192.168.66.35:8443
2019-10-04 16:44:12.360  - info: unifi.0 (1505) getSitesStats: default
2019-10-04 16:44:12.458  - info: unifi.0 (1505) getSiteSysinfo: 1
2019-10-04 16:44:12.586  - info: unifi.0 (1505) getClientDevices: 26
2019-10-04 16:44:13.901  - info: unifi.0 (1505) getAccessDevices: 5
2019-10-04 16:44:14.159  - info: host.debian instance system.adapter.tr-064-community.0 started with pid 1551
2019-10-04 16:44:18.274  - info: host.debian instance system.adapter.vis.0 terminated while should be started once
2019-10-04 16:44:18.346  - info: host.debian instance system.adapter.hue.0 started with pid 1558
2019-10-04 16:44:18.269  - info: hm-rpc.0 (1540) starting. Version 1.10.0 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v10.16.3
2019-10-04 16:44:18.770  - info: hm-rpc.0 (1540) [META] Meta data updated
2019-10-04 16:44:20.801  - info: tr-064-community.0 (1551) starting. Version 1.0.0 in /opt/iobroker/node_modules/iobroker.tr-064-community, node: v10.16.3
2019-10-04 16:44:22.158  - info: host.debian instance system.adapter.lgtv.0 started with pid 1577
2019-10-04 16:44:22.867  - info: hm-rpc.0 (1540) xmlrpc server is trying to listen on 192.168.66.68:2001
2019-10-04 16:44:22.868  - info: hm-rpc.0 (1540) xmlrpc client is trying to connect to 192.168.66.36:2001/ with ["http://192.168.66.68:2001","hm-rpc.0"]
2019-10-04 16:44:23.016  - info: hm-rpc.0 (1540) xmlrpc <- system.listMethods ["hm-rpc.0"]
2019-10-04 16:44:23.069  - info: hm-rpc.0 (1540) xmlrpc <- listDevices ["hm-rpc.0"]
2019-10-04 16:44:27.062  - info: hue.0 (1558) starting. Version 2.0.0 in /opt/iobroker/node_modules/iobroker.hue, node: v10.16.3
2019-10-04 16:44:27.351  - info: hm-rpc.0 (1540) xmlrpc -> 375 devices
2019-10-04 16:44:27.665  - info: lgtv.0 (1577) starting. Version 1.0.8 in /opt/iobroker/node_modules/iobroker.lgtv, node: v10.16.3
2019-10-04 16:44:27.929  - info: hm-rpc.0 (1540) Connected
2019-10-04 16:44:27.943  - info: lgtv.0 (1577) Ready. Configured WebOS TV IP: 192.168.66.156
2019-10-04 16:44:28.137  - info: hue.0 (1558) skip switch: Philips hue.Daylight.configured
2019-10-04 16:44:28.164  - info: hue.0 (1558) skip switch: Philips hue.Daylight.sunriseoffset
2019-10-04 16:44:28.165  - info: hue.0 (1558) skip switch: Philips hue.Daylight.sunsetoffset
2019-10-04 16:44:28.166  - info: hue.0 (1558) created/updated 1 sensor channels
2019-10-04 16:44:28.178  - info: hue.0 (1558) created/updated 6 light channels
2019-10-04 16:44:28.202  - info: hue.0 (1558) created/updated 6 groups channels
2019-10-04 16:44:28.363  - info: hue.0 (1558) created/updated 53 scenes
2019-10-04 16:44:28.364  - info: hue.0 (1558) creating/updating bridge device
2019-10-04 16:44:30.021  - info: host.debian instance scheduled system.adapter.dwd.0 */5 * * * *
2019-10-04 16:44:30.038  - info: host.debian instance system.adapter.dwd.0 started with pid 1600
2019-10-04 16:44:30.264  - info: tankerkoenig.0 (1520) starting. Version 2.0.6 in /opt/iobroker/node_modules/iobroker.tankerkoenig, node: v10.16.3
2019-10-04 16:44:30.354  - info: tankerkoenig.0 (1520) Sync time set to 5 minutes or 300000 ms
2019-10-04 16:44:30.538  - info: tankerkoenig.0 (1520) Reading data from tankerkoenig ...
2019-10-04 16:44:34.037  - info: host.debian instance system.adapter.ble.0 started with pid 1611
2019-10-04 16:44:36.688  - info: dwd.0 (1600) starting. Version 2.4.3 in /opt/iobroker/node_modules/iobroker.dwd, node: v10.16.3
2019-10-04 16:44:38.036  - info: host.debian instance scheduled system.adapter.ical.1 0,30 * * * *
2019-10-04 16:44:38.142  - info: host.debian instance system.adapter.ical.1 started with pid 1630
2019-10-04 16:44:38.329  - info: ble.0 (1611) starting. Version 0.10.0 in /opt/iobroker/node_modules/iobroker.ble, node: v10.16.3
2019-10-04 16:44:39.081  - info: ble.0 (1611) loaded plugins: Xiaomi, mi-flora, ruuvi-tag, _default
2019-10-04 16:44:39.259  - info: dwd.0 (1600) Terminated (NO_ERROR): Without reason
2019-10-04 16:44:40.766  - info: host.debian instance system.adapter.dwd.0 terminated with code 0 (NO_ERROR)
2019-10-04 16:44:39.082  - info: ble.0 (1611) enabled plugins: mi-flora, _default
2019-10-04 16:44:39.082  - info: ble.0 (1611) monitoring all services
2019-10-04 16:44:41.410  - info: ble.0 (1611) starting scan for services []
2019-10-04 16:44:42.034  - info: host.debian instance system.adapter.proxmox.0 started with pid 1643
2019-10-04 16:44:45.631  - info: ical.1 (1630) starting. Version 1.7.0 in /opt/iobroker/node_modules/iobroker.ical, node: v10.16.3
2019-10-04 16:44:46.040  - info: host.debian instance system.adapter.wiffi-wz.0 started with pid 1662
2019-10-04 16:44:47.078  - info: ical.1 (1630) processing URL: Müllkalender https://calendar.google.com/calendar/ical/a5e3g5donnkg5qr7kkg81ovaio%40group.calendar.google.com/public/basic.ics
2019-10-04 16:44:47.483  - info: ical.1 (1630) processing URL: AbfallPapier https://calendar.google.com/calendar/ical/ukul42136q3lu88ldrj7pu3ho8%40group.calendar.google.com/private-420b70aa7f555fec8e1468e8e68c7534/basic.ics
2019-10-04 16:44:47.839  - info: proxmox.0 (1643) starting. Version 0.5.1 in /opt/iobroker/node_modules/iobroker.proxmox, node: v10.16.3
2019-10-04 16:44:50.083  - info: host.debian instance system.adapter.mihome-vacuum.0 started with pid 1673
2019-10-04 16:44:52.947  - info: wiffi-wz.0 (1662) starting. Version 2.1.4 in /opt/iobroker/node_modules/iobroker.wiffi-wz, node: v10.16.3
2019-10-04 16:44:54.070  - info: host.debian instance system.adapter.javascript.1 started with pid 1692
2019-10-04 16:44:54.396  - info: ical.1 (1630) Terminated (NO_ERROR): Without reason
2019-10-04 16:44:54.465  - info: wiffi-wz.0 (1662) Opening local server on 0.0.0.0:8181
2019-10-04 16:44:54.495  - info: wiffi-wz.0 (1662) Server listening on 0.0.0.0:8181
2019-10-04 16:44:56.048  - info: host.debian instance system.adapter.ical.1 terminated with code 0 (NO_ERROR)
2019-10-04 16:44:57.460  - info: mihome-vacuum.0 (1673) starting. Version 1.1.5 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v10.16.3
2019-10-04 16:44:57.551  - info: mihome-vacuum.0 (1673) Expert mode enabled, states created
2019-10-04 16:44:57.553  - info: mihome-vacuum.0 (1673) Cloud control disabled
2019-10-04 16:44:57.673  - warn: mihome-vacuum.0 (1673) Time difference between Mihome Vacuum and ioBroker: 1 sec
2019-10-04 16:44:57.929  - info: mihome-vacuum.0 (1673) New generation or new fw detected, create new states
2019-10-04 16:44:58.040  - info: host.debian instance scheduled system.adapter.feiertage.0 0 0 * * *
2019-10-04 16:44:58.122  - info: host.debian instance system.adapter.feiertage.0 started with pid 1704
2019-10-04 16:45:00.083  - info: host.debian instance system.adapter.dwd.0 started with pid 1715
2019-10-04 16:45:01.681  - info: feiertage.0 (1704) starting. Version 1.0.11 in /opt/iobroker/node_modules/iobroker.feiertage, node: v10.16.3
2019-10-04 16:45:01.981  - info: feiertage.0 (1704) Next holiday: Allerheiligen (BW, BY, NW, RP, SL) is in 28 days on 01.11.2019
2019-10-04 16:45:01.993  - info: feiertage.0 (1704) adapter feiertage objects written
2019-10-04 16:45:02.097  - info: host.debian instance system.adapter.enigma2.0 started with pid 1726
2019-10-04 16:45:02.603  - info: feiertage.0 (1704) Terminated (NO_ERROR): Without reason
2019-10-04 16:45:04.525  - info: host.debian instance system.adapter.feiertage.0 terminated with code 0 (NO_ERROR)
2019-10-04 16:45:04.578  - info: host.debian instance system.adapter.daswetter.0 started with pid 1741
2019-10-04 16:45:05.620  - info: dwd.0 (1715) starting. Version 2.4.3 in /opt/iobroker/node_modules/iobroker.dwd, node: v10.16.3
2019-10-04 16:45:05.791  - info: javascript.1 (1692) starting. Version 4.1.16 in /opt/iobroker/node_modules/iobroker.javascript, node: v10.16.3
2019-10-04 16:45:06.081  - info: javascript.1 (1692) requesting all states
2019-10-04 16:45:06.082  - info: javascript.1 (1692) requesting all objects
2019-10-04 16:45:06.139  - info: host.debian instance system.adapter.worx.0 started with pid 1756
2019-10-04 16:45:09.407  - info: dwd.0 (1715) Terminated (NO_ERROR): Without reason
2019-10-04 16:45:09.425  - info: host.debian instance system.adapter.dwd.0 terminated with code 0 (NO_ERROR)
2019-10-04 16:45:10.057  - info: host.debian instance system.adapter.repetier.0 started with pid 1771
2019-10-04 16:45:14.942  - info: worx.0 (1756) starting. Version 0.4.0 in /opt/iobroker/node_modules/iobroker.worx, node: v10.16.3
2019-10-04 16:45:15.526  - info: daswetter.0 (1741) starting. Version 2.8.1 in /opt/iobroker/node_modules/iobroker.daswetter, node: v10.16.3
2019-10-04 16:45:16.270  - info: unifi.0 (1505) Starting UniFi-Controller query
2019-10-04 16:45:16.271  - info: unifi.0 (1505) update_interval = 60
2019-10-04 16:45:16.271  - info: unifi.0 (1505) controller = 192.168.66.35:8443
2019-10-04 16:45:16.722  - info: unifi.0 (1505) getSitesStats: default
2019-10-04 16:45:16.822  - info: unifi.0 (1505) getSiteSysinfo: 1
2019-10-04 16:45:16.927  - info: unifi.0 (1505) getClientDevices: 26
2019-10-04 16:45:17.016  - info: repetier.0 (1771) starting. Version 0.0.1 in /opt/iobroker/node_modules/iobroker.repetier, node: v10.16.3
2019-10-04 16:45:17.180  - info: enigma2.0 (1726) starting. Version 1.2.3 in /opt/iobroker/node_modules/iobroker.enigma2, node: v10.16.3
2019-10-04 16:45:17.288  - info: enigma2.0 (1726) starting Polling every 5000 ms
2019-10-04 16:45:17.998  - info: unifi.0 (1505) getAccessDevices: 5
2019-10-04 16:45:18.321  - info: daswetter.0 (1741) got wrong data structure! trying to repair...
2019-10-04 16:45:20.229  - info: vis-google-fonts.0 (1786) starting. Version 0.1.0 in /opt/iobroker/node_modules/iobroker.vis-google-fonts, node: v10.16.3
2019-10-04 16:45:22.474  - info: enigma2.0 (1726) enigma2 Verbunden!
2019-10-04 16:45:22.546  - info: vis-google-fonts.0 (1786) Terminated (NO_ERROR): Without reason
2019-10-04 16:45:23.434  - info: host.debian instance system.adapter.vis-google-fonts.0 terminated while should be started once
2019-10-04 16:45:26.068  - info: host.debian instance system.adapter.web.0 started with pid 1817
2019-10-04 16:45:29.064  - info: javascript.1 (1692) received all objects
2019-10-04 16:45:30.056  - info: host.debian instance system.adapter.sourceanalytix.0 started with pid 1824
2019-10-04 16:45:31.141  - info: javascript.1 (1692) received all states
2019-10-04 16:45:38.925  - info: sourceanalytix.0 (1824) starting. Version 0.2.281 in /opt/iobroker/node_modules/iobroker.sourceanalytix, node: v10.16.3
2019-10-04 16:45:39.026  - info: sourceanalytix.0 (1824) Adapter SourceAnalytix startet :-)
2019-10-04 16:45:39.027  - info: sourceanalytix.0 (1824) Initializing all enabled states for SourceAnalytix
2019-10-04 16:45:42.032  - info: host.debian instance scheduled system.adapter.ical.0 0,30 * * * *
2019-10-04 16:45:42.147  - info: host.debian instance system.adapter.ical.0 started with pid 1844
2019-10-04 16:45:45.009  - warn: hm-rpc.1 (1340) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.019  - warn: admin.0 (1235) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.042  - warn: iot.0 (1430) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.042  - warn: iot.0 (1430) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.043  - warn: iot.0 (1430) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.043  - warn: iot.0 (1430) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.044  - warn: iot.0 (1430) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.044  - warn: iot.0 (1430) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.044  - warn: iot.0 (1430) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.044  - warn: iot.0 (1430) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.044  - warn: iot.0 (1430) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.044  - warn: iot.0 (1430) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.044  - warn: iot.0 (1430) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.057  - warn: enigma2.0 (1726) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.079  - warn: telegram.0 (1460) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.086  - warn: adapter-studio.0 (1490) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.077  - warn: mqtt.0 (1265) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.090  - warn: iqontrol.1 (1411) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.088  - warn: sonos.0 (1355) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.065  - warn: hue.0 (1558) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.042  - warn: lgtv.0 (1577) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.089  - warn: mqtt.0 (1265) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.117  - warn: mqtt.0 (1265) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.117  - warn: mqtt.0 (1265) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.117  - warn: mqtt.0 (1265) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.117  - warn: mqtt.0 (1265) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.118  - warn: mqtt.0 (1265) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.127  - warn: iqontrol.0 (1366) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.055  - warn: worx.0 (1756) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.100  - warn: hue.0 (1558) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.126  - warn: hue.0 (1558) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.126  - warn: hue.0 (1558) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.126  - warn: hue.0 (1558) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.127  - warn: hue.0 (1558) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.127  - warn: hue.0 (1558) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.134  - warn: hue.0 (1558) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.134  - warn: hue.0 (1558) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.135  - warn: hue.0 (1558) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.135  - warn: hue.0 (1558) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.148  - error: ble.0 (1611) unhandled promise rejection: ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.184  - warn: mihome-vacuum.0 (1673) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.020  - warn: admin.0 (1235) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.020  - warn: admin.0 (1235) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.021  - warn: admin.0 (1235) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.021  - warn: admin.0 (1235) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.021  - warn: admin.0 (1235) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.021  - warn: admin.0 (1235) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.021  - warn: admin.0 (1235) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.021  - warn: admin.0 (1235) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.021  - warn: admin.0 (1235) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.022  - warn: admin.0 (1235) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.103  - warn: lgtv.0 (1577) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.104  - warn: lgtv.0 (1577) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.104  - warn: lgtv.0 (1577) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.104  - warn: lgtv.0 (1577) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.105  - warn: lgtv.0 (1577) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.105  - warn: lgtv.0 (1577) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.105  - warn: lgtv.0 (1577) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.224  - warn: lgtv.0 (1577) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.224  - warn: lgtv.0 (1577) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.224  - warn: lgtv.0 (1577) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.090  - warn: iqontrol.1 (1411) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.091  - warn: iqontrol.1 (1411) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.091  - warn: iqontrol.1 (1411) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.092  - warn: iqontrol.1 (1411) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.092  - warn: iqontrol.1 (1411) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.093  - warn: iqontrol.1 (1411) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.093  - warn: iqontrol.1 (1411) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.093  - warn: iqontrol.1 (1411) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.227  - warn: iqontrol.1 (1411) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.227  - warn: iqontrol.1 (1411) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.078  - warn: enigma2.0 (1726) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.078  - warn: enigma2.0 (1726) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.079  - warn: enigma2.0 (1726) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.079  - warn: enigma2.0 (1726) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.079  - warn: enigma2.0 (1726) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.079  - warn: enigma2.0 (1726) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.080  - warn: enigma2.0 (1726) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.080  - warn: enigma2.0 (1726) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.080  - warn: enigma2.0 (1726) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.080  - warn: enigma2.0 (1726) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.080  - warn: enigma2.0 (1726) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.160  - warn: enigma2.0 (1726) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.160  - warn: enigma2.0 (1726) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.160  - warn: enigma2.0 (1726) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.160  - warn: enigma2.0 (1726) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.161  - warn: enigma2.0 (1726) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.161  - warn: enigma2.0 (1726) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.161  - warn: enigma2.0 (1726) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.161  - warn: enigma2.0 (1726) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.161  - warn: enigma2.0 (1726) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.162  - warn: enigma2.0 (1726) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.258  - warn: enigma2.0 (1726) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.096  - warn: sonos.0 (1355) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.097  - warn: sonos.0 (1355) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.097  - warn: sonos.0 (1355) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.106  - warn: sonos.0 (1355) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.107  - warn: sonos.0 (1355) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.168  - warn: sonos.0 (1355) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.168  - warn: sonos.0 (1355) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.207  - warn: sonos.0 (1355) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.208  - warn: sonos.0 (1355) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.208  - warn: sonos.0 (1355) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.308  - warn: iqontrol.0 (1366) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.086  - warn: adapter-studio.0 (1490) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.202  - warn: adapter-studio.0 (1490) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.204  - warn: adapter-studio.0 (1490) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.204  - warn: adapter-studio.0 (1490) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.205  - warn: adapter-studio.0 (1490) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.223  - warn: adapter-studio.0 (1490) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.223  - warn: adapter-studio.0 (1490) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.308  - warn: adapter-studio.0 (1490) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.
2019-10-04 16:45:45.317  - warn: adapter-studio.0 (1490) get state ReplyError: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN N