2019-03-05 05:42:31.071  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGSEGV
2019-03-05 05:42:31.073  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 05:42:31.073  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 05:42:32.517  - error: Caught by controller[0]: *** Error in `io.tr-064.0': corrupted size vs. prev_size: 0x0261d310 ***
2019-03-05 05:42:32.529  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGABRT
2019-03-05 05:42:32.530  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 05:42:32.531  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 05:42:37.351  - warn: host.raspberrypi instance system.adapter.telegram.0 terminated due to SIGSEGV
2019-03-05 05:42:37.352  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code null ()
2019-03-05 05:42:37.353  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2019-03-05 05:43:01.114  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 17350
2019-03-05 05:43:02.215  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 05:43:02.215  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 05:43:02.216  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 05:43:02.556  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 17362
2019-03-05 05:43:05.127  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGILL
2019-03-05 05:43:05.128  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 05:43:05.129  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 05:43:07.379  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 17390
2019-03-05 05:43:10.328  - error: Caught by controller[0]: Tue, 05 Mar 2019 04:43:10 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
2019-03-05 05:43:10.329  - error: Caught by controller[0]: In the future, you will have to enable it yourself.
2019-03-05 05:43:10.329  - error: Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30
2019-03-05 05:43:10.329  - warn: host.raspberrypi instance system.adapter.telegram.0 terminated due to SIGILL
2019-03-05 05:43:10.329  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code null ()
2019-03-05 05:43:10.330  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2019-03-05 05:43:32.241  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 17505
2019-03-05 05:43:33.322  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 05:43:33.323  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 05:43:33.323  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 05:43:35.159  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 17524
2019-03-05 05:43:37.858  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGILL
2019-03-05 05:43:37.859  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 05:43:37.859  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 05:43:40.388  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 17551
2019-03-05 05:43:43.323  - error: Caught by controller[0]: Tue, 05 Mar 2019 04:43:43 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
2019-03-05 05:43:43.324  - error: Caught by controller[0]: In the future, you will have to enable it yourself.
2019-03-05 05:43:43.324  - error: Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30
2019-03-05 05:43:43.324  - warn: host.raspberrypi instance system.adapter.telegram.0 terminated due to SIGILL
2019-03-05 05:43:43.325  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code null ()
2019-03-05 05:43:43.325  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2019-03-05 05:44:03.352  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 17654
2019-03-05 05:44:04.514  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 05:44:04.514  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 05:44:04.515  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 05:44:07.886  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 17679
2019-03-05 05:44:10.603  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGILL
2019-03-05 05:44:10.604  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 05:44:10.604  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 05:44:13.352  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 17708
2019-03-05 05:44:16.358  - error: Caught by controller[0]: Tue, 05 Mar 2019 04:44:16 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
2019-03-05 05:44:16.359  - error: Caught by controller[0]: In the future, you will have to enable it yourself.
2019-03-05 05:44:16.359  - error: Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30
2019-03-05 05:44:16.359  - warn: host.raspberrypi instance system.adapter.telegram.0 terminated due to SIGILL
2019-03-05 05:44:16.360  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code null ()
2019-03-05 05:44:16.360  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2019-03-05 05:44:34.554  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 17801
2019-03-05 05:44:35.675  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 05:44:35.676  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 05:44:35.676  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 05:44:40.647  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 17831
2019-03-05 05:44:43.342  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGILL
2019-03-05 05:44:43.342  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 05:44:43.343  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 05:44:46.400  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 17860
2019-03-05 05:44:49.525  - error: Caught by controller[0]: Tue, 05 Mar 2019 04:44:49 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
2019-03-05 05:44:49.526  - error: Caught by controller[0]: In the future, you will have to enable it yourself.
2019-03-05 05:44:49.526  - error: Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30
2019-03-05 05:44:49.527  - warn: host.raspberrypi instance system.adapter.telegram.0 terminated due to SIGILL
2019-03-05 05:44:49.527  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code null ()
2019-03-05 05:44:49.527  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2019-03-05 05:45:05.704  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 17940
2019-03-05 05:45:06.836  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 05:45:06.836  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 05:45:06.837  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 05:45:13.369  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 17975
2019-03-05 05:45:16.165  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGILL
2019-03-05 05:45:16.165  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 05:45:16.166  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 05:45:19.570  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 18005
2019-03-05 05:45:22.657  - error: Caught by controller[0]: Tue, 05 Mar 2019 04:45:22 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
2019-03-05 05:45:22.657  - error: Caught by controller[0]: In the future, you will have to enable it yourself.
2019-03-05 05:45:22.658  - error: Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30
2019-03-05 05:45:22.658  - warn: host.raspberrypi instance system.adapter.telegram.0 terminated due to SIGILL
2019-03-05 05:45:22.658  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code null ()
2019-03-05 05:45:22.659  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2019-03-05 05:45:36.864  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 18075
2019-03-05 05:45:37.935  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 05:45:37.936  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 05:45:37.936  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 05:45:46.192  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 18115
2019-03-05 05:45:48.819  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGILL
2019-03-05 05:45:48.820  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 05:45:48.820  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 05:45:52.685  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 18147
2019-03-05 05:45:55.667  - error: Caught by controller[0]: Tue, 05 Mar 2019 04:45:55 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
2019-03-05 05:45:55.668  - error: Caught by controller[0]: In the future, you will have to enable it yourself.
2019-03-05 05:45:55.668  - error: Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30
2019-03-05 05:45:55.668  - warn: host.raspberrypi instance system.adapter.telegram.0 terminated due to SIGILL
2019-03-05 05:45:55.669  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code null ()
2019-03-05 05:45:55.669  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2019-03-05 05:46:07.980  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 18208
2019-03-05 05:46:09.049  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 05:46:09.049  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 05:46:09.050  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 05:46:18.848  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 18253
2019-03-05 05:46:21.421  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGILL
2019-03-05 05:46:21.421  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 05:46:21.422  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 05:46:25.696  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 18283
2019-03-05 05:46:28.801  - error: Caught by controller[0]: Tue, 05 Mar 2019 04:46:28 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
2019-03-05 05:46:28.801  - error: Caught by controller[0]: In the future, you will have to enable it yourself.
2019-03-05 05:46:28.802  - error: Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30
2019-03-05 05:46:28.802  - warn: host.raspberrypi instance system.adapter.telegram.0 terminated due to SIGILL
2019-03-05 05:46:28.802  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code null ()
2019-03-05 05:46:28.803  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2019-03-05 05:46:39.075  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 18336
2019-03-05 05:46:40.163  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 05:46:40.164  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 05:46:40.165  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 05:46:51.447  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 18385
2019-03-05 05:46:54.025  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGILL
2019-03-05 05:46:54.025  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 05:46:54.026  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 05:46:58.828  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 18416
2019-03-05 05:47:01.869  - error: Caught by controller[0]: Tue, 05 Mar 2019 04:47:01 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
2019-03-05 05:47:01.870  - error: Caught by controller[0]: In the future, you will have to enable it yourself.
2019-03-05 05:47:01.870  - error: Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30
2019-03-05 05:47:01.870  - warn: host.raspberrypi instance system.adapter.telegram.0 terminated due to SIGILL
2019-03-05 05:47:01.871  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code null ()
2019-03-05 05:47:01.871  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2019-03-05 05:47:10.191  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 18460
2019-03-05 05:47:11.371  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 05:47:11.371  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 05:47:11.372  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 05:47:24.080  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 18513
2019-03-05 05:47:26.713  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGILL
2019-03-05 05:47:26.714  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 05:47:26.714  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 05:47:31.897  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 18545
2019-03-05 05:47:34.991  - error: Caught by controller[0]: Tue, 05 Mar 2019 04:47:34 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
2019-03-05 05:47:34.992  - error: Caught by controller[0]: In the future, you will have to enable it yourself.
2019-03-05 05:47:34.992  - error: Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30
2019-03-05 05:47:34.992  - warn: host.raspberrypi instance system.adapter.telegram.0 terminated due to SIGILL
2019-03-05 05:47:34.993  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code null ()
2019-03-05 05:47:34.993  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2019-03-05 05:47:41.397  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 18583
2019-03-05 05:47:42.455  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 05:47:42.456  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 05:47:42.457  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 05:47:56.741  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 18639
2019-03-05 05:47:59.316  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGILL
2019-03-05 05:47:59.317  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 05:47:59.317  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 05:48:05.023  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 18671
2019-03-05 05:48:08.023  - error: Caught by controller[0]: Tue, 05 Mar 2019 04:48:07 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
2019-03-05 05:48:08.023  - error: Caught by controller[0]: In the future, you will have to enable it yourself.
2019-03-05 05:48:08.024  - error: Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30
2019-03-05 05:48:08.024  - warn: host.raspberrypi instance system.adapter.telegram.0 terminated due to SIGILL
2019-03-05 05:48:08.024  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code null ()
2019-03-05 05:48:08.024  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2019-03-05 05:48:12.483  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 18702
2019-03-05 05:48:13.577  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 05:48:13.578  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 05:48:13.578  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 05:48:29.345  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 18761
2019-03-05 05:48:31.964  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGILL
2019-03-05 05:48:31.964  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 05:48:31.965  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 05:48:38.064  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 18795
2019-03-05 05:48:41.080  - error: Caught by controller[0]: Tue, 05 Mar 2019 04:48:40 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
2019-03-05 05:48:41.080  - error: Caught by controller[0]: In the future, you will have to enable it yourself.
2019-03-05 05:48:41.081  - error: Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30
2019-03-05 05:48:41.081  - warn: host.raspberrypi instance system.adapter.telegram.0 terminated due to SIGILL
2019-03-05 05:48:41.081  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code null ()
2019-03-05 05:48:41.081  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2019-03-05 05:48:43.618  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 18819
2019-03-05 05:48:44.780  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 05:48:44.781  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 05:48:44.782  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 05:49:01.989  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 18884
2019-03-05 05:49:04.635  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGILL
2019-03-05 05:49:04.635  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 05:49:04.636  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 05:49:11.104  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 18918
2019-03-05 05:49:14.159  - error: Caught by controller[0]: Tue, 05 Mar 2019 04:49:13 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
2019-03-05 05:49:14.160  - error: Caught by controller[0]: In the future, you will have to enable it yourself.
2019-03-05 05:49:14.160  - error: Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30
2019-03-05 05:49:14.160  - warn: host.raspberrypi instance system.adapter.telegram.0 terminated due to SIGILL
2019-03-05 05:49:14.161  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code null ()
2019-03-05 05:49:14.161  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2019-03-05 05:49:14.806  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 18936
2019-03-05 05:49:15.912  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 05:49:15.913  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 05:49:15.914  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 05:49:34.660  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 19002
2019-03-05 05:49:37.407  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGILL
2019-03-05 05:49:37.408  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 05:49:37.408  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 05:49:44.188  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 19036
2019-03-05 05:49:46.011  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 19048
2019-03-05 05:49:47.249  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 05:49:47.251  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 05:49:47.252  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 05:49:47.365  - error: Caught by controller[0]: Tue, 05 Mar 2019 04:49:47 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
2019-03-05 05:49:47.366  - error: Caught by controller[0]: In the future, you will have to enable it yourself.
2019-03-05 05:49:47.366  - error: Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30
2019-03-05 05:49:47.366  - warn: host.raspberrypi instance system.adapter.telegram.0 terminated due to SIGILL
2019-03-05 05:49:47.366  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code null ()
2019-03-05 05:49:47.367  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2019-03-05 05:50:07.441  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 19118
2019-03-05 05:50:10.175  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGILL
2019-03-05 05:50:10.176  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 05:50:10.177  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 05:50:17.291  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 19153
2019-03-05 05:50:17.389  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 19159
2019-03-05 05:50:18.403  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 05:50:18.403  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 05:50:18.404  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 05:50:20.395  - error: Caught by controller[0]: Tue, 05 Mar 2019 04:50:20 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
2019-03-05 05:50:20.395  - error: Caught by controller[0]: In the future, you will have to enable it yourself.
2019-03-05 05:50:20.396  - error: Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30
2019-03-05 05:50:20.396  - warn: host.raspberrypi instance system.adapter.telegram.0 terminated due to SIGILL
2019-03-05 05:50:20.396  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code null ()
2019-03-05 05:50:20.397  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2019-03-05 05:50:40.209  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 19231
2019-03-05 05:50:42.875  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGILL
2019-03-05 05:50:42.876  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 05:50:42.876  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 05:50:48.438  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 19261
2019-03-05 05:50:49.527  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 05:50:49.528  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 05:50:49.528  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 05:50:50.417  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 19273
2019-03-05 05:50:53.534  - error: Caught by controller[0]: Tue, 05 Mar 2019 04:50:53 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
2019-03-05 05:50:53.535  - error: Caught by controller[0]: In the future, you will have to enable it yourself.
2019-03-05 05:50:53.535  - error: Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30
2019-03-05 05:50:53.535  - warn: host.raspberrypi instance system.adapter.telegram.0 terminated due to SIGILL
2019-03-05 05:50:53.536  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code null ()
2019-03-05 05:50:53.536  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2019-03-05 05:51:12.898  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 19345
2019-03-05 05:51:15.520  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGILL
2019-03-05 05:51:15.521  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 05:51:15.521  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 05:51:19.579  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 19369
2019-03-05 05:51:20.732  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 05:51:20.732  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 05:51:20.733  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 05:51:23.560  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 19387
2019-03-05 05:51:26.581  - error: Caught by controller[0]: Tue, 05 Mar 2019 04:51:26 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
2019-03-05 05:51:26.582  - error: Caught by controller[0]: In the future, you will have to enable it yourself.
2019-03-05 05:51:26.582  - error: Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30
2019-03-05 05:51:26.583  - warn: host.raspberrypi instance system.adapter.telegram.0 terminated due to SIGILL
2019-03-05 05:51:26.583  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code null ()
2019-03-05 05:51:26.583  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2019-03-05 05:51:45.546  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 19454
2019-03-05 05:51:48.107  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGILL
2019-03-05 05:51:48.108  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 05:51:48.108  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 05:51:50.756  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 19475
2019-03-05 05:51:51.866  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 05:51:51.866  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 05:51:51.867  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 05:51:56.608  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 19497
2019-03-05 05:51:59.628  - error: Caught by controller[0]: Tue, 05 Mar 2019 04:51:59 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
2019-03-05 05:51:59.629  - error: Caught by controller[0]: In the future, you will have to enable it yourself.
2019-03-05 05:51:59.630  - error: Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30
2019-03-05 05:51:59.630  - warn: host.raspberrypi instance system.adapter.telegram.0 terminated due to SIGILL
2019-03-05 05:51:59.630  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code null ()
2019-03-05 05:51:59.630  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2019-03-05 05:52:18.132  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 19562
2019-03-05 05:52:20.672  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGILL
2019-03-05 05:52:20.672  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 05:52:20.673  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 05:52:21.886  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 19578
2019-03-05 05:52:22.958  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 05:52:22.958  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 05:52:22.958  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 05:52:29.651  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 19605
2019-03-05 05:52:32.672  - error: Caught by controller[0]: Tue, 05 Mar 2019 04:52:32 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
2019-03-05 05:52:32.673  - error: Caught by controller[0]: In the future, you will have to enable it yourself.
2019-03-05 05:52:32.673  - error: Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30
2019-03-05 05:52:32.674  - warn: host.raspberrypi instance system.adapter.telegram.0 terminated due to SIGILL
2019-03-05 05:52:32.674  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code null ()
2019-03-05 05:52:32.674  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2019-03-05 05:52:50.721  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 19668
2019-03-05 05:52:52.986  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 19681
2019-03-05 05:52:53.470  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGILL
2019-03-05 05:52:53.471  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 05:52:53.471  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 05:52:54.111  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 05:52:54.112  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 05:52:54.113  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 05:53:02.709  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 19712
2019-03-05 05:53:05.774  - error: Caught by controller[0]: Tue, 05 Mar 2019 04:53:05 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
2019-03-05 05:53:05.774  - error: Caught by controller[0]: In the future, you will have to enable it yourself.
2019-03-05 05:53:05.774  - error: Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30
2019-03-05 05:53:05.775  - warn: host.raspberrypi instance system.adapter.telegram.0 terminated due to SIGILL
2019-03-05 05:53:05.775  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code null ()
2019-03-05 05:53:05.775  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2019-03-05 05:53:23.493  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 19773
2019-03-05 05:53:24.134  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 19781
2019-03-05 05:53:25.295  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 05:53:25.296  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 05:53:25.296  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 05:53:26.350  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGILL
2019-03-05 05:53:26.351  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 05:53:26.351  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 05:53:35.798  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 19817
2019-03-05 05:53:38.881  - error: Caught by controller[0]: Tue, 05 Mar 2019 04:53:38 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
2019-03-05 05:53:38.882  - error: Caught by controller[0]: In the future, you will have to enable it yourself.
2019-03-05 05:53:38.882  - error: Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30
2019-03-05 05:53:38.883  - warn: host.raspberrypi instance system.adapter.telegram.0 terminated due to SIGILL
2019-03-05 05:53:38.883  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code null ()
2019-03-05 05:53:38.883  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2019-03-05 05:53:55.317  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 19874
2019-03-05 05:53:56.387  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 19884
2019-03-05 05:53:56.396  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 05:53:56.397  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 05:53:56.397  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 05:53:58.998  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGILL
2019-03-05 05:53:58.999  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 05:53:58.999  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 05:54:08.908  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 19923
2019-03-05 05:54:12.011  - error: Caught by controller[0]: Tue, 05 Mar 2019 04:54:11 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
2019-03-05 05:54:12.012  - error: Caught by controller[0]: In the future, you will have to enable it yourself.
2019-03-05 05:54:12.013  - error: Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30
2019-03-05 05:54:12.013  - warn: host.raspberrypi instance system.adapter.telegram.0 terminated due to SIGILL
2019-03-05 05:54:12.013  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code null ()
2019-03-05 05:54:12.013  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2019-03-05 05:54:26.420  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 19974
2019-03-05 05:54:27.537  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 05:54:27.538  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 05:54:27.538  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 05:54:29.021  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 19987
2019-03-05 05:54:31.751  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGILL
2019-03-05 05:54:31.752  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 05:54:31.752  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 05:54:42.035  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 20026
2019-03-05 05:54:45.088  - error: Caught by controller[0]: Tue, 05 Mar 2019 04:54:44 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
2019-03-05 05:54:45.089  - error: Caught by controller[0]: In the future, you will have to enable it yourself.
2019-03-05 05:54:45.089  - error: Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30
2019-03-05 05:54:45.090  - warn: host.raspberrypi instance system.adapter.telegram.0 terminated due to SIGILL
2019-03-05 05:54:45.090  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code null ()
2019-03-05 05:54:45.090  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2019-03-05 05:54:57.559  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 20071
2019-03-05 05:54:58.697  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 05:54:58.698  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 05:54:58.698  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 05:55:01.787  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 20087
2019-03-05 05:55:04.378  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGILL
2019-03-05 05:55:04.378  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 05:55:04.379  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 05:55:15.125  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 20126
2019-03-05 05:55:18.034  - error: Caught by controller[0]: Tue, 05 Mar 2019 04:55:17 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
2019-03-05 05:55:18.035  - error: Caught by controller[0]: In the future, you will have to enable it yourself.
2019-03-05 05:55:18.035  - error: Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30
2019-03-05 05:55:18.036  - warn: host.raspberrypi instance system.adapter.telegram.0 terminated due to SIGILL
2019-03-05 05:55:18.036  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code null ()
2019-03-05 05:55:18.036  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2019-03-05 05:55:28.720  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 20166
2019-03-05 05:55:29.811  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 05:55:29.812  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 05:55:29.812  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 05:55:34.406  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 20186
2019-03-05 05:55:36.980  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGILL
2019-03-05 05:55:36.981  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 05:55:36.981  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 05:55:48.058  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 20225
2019-03-05 05:55:51.019  - error: Caught by controller[0]: Tue, 05 Mar 2019 04:55:50 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
2019-03-05 05:55:51.020  - error: Caught by controller[0]: In the future, you will have to enable it yourself.
2019-03-05 05:55:51.020  - error: Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30
2019-03-05 05:55:51.021  - warn: host.raspberrypi instance system.adapter.telegram.0 terminated due to SIGILL
2019-03-05 05:55:51.021  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code null ()
2019-03-05 05:55:51.021  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2019-03-05 05:55:59.837  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 20262
2019-03-05 05:56:00.901  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 05:56:00.902  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 05:56:00.902  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 05:56:07.014  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 20285
2019-03-05 05:56:09.635  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGILL
2019-03-05 05:56:09.636  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 05:56:09.636  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 05:56:21.042  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 20325
2019-03-05 05:56:24.049  - error: Caught by controller[0]: Tue, 05 Mar 2019 04:56:23 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
2019-03-05 05:56:24.050  - error: Caught by controller[0]: In the future, you will have to enable it yourself.
2019-03-05 05:56:24.050  - error: Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30
2019-03-05 05:56:24.050  - warn: host.raspberrypi instance system.adapter.telegram.0 terminated due to SIGILL
2019-03-05 05:56:24.051  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code null ()
2019-03-05 05:56:24.051  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2019-03-05 05:56:30.932  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 20355
2019-03-05 05:56:32.075  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 05:56:32.076  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 05:56:32.076  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 05:56:39.671  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 20381
2019-03-05 05:56:42.281  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGILL
2019-03-05 05:56:42.282  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 05:56:42.282  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 05:56:54.074  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 20419
2019-03-05 05:56:57.003  - error: Caught by controller[0]: Tue, 05 Mar 2019 04:56:56 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
2019-03-05 05:56:57.004  - error: Caught by controller[0]: In the future, you will have to enable it yourself.
2019-03-05 05:56:57.004  - error: Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30
2019-03-05 05:56:57.004  - warn: host.raspberrypi instance system.adapter.telegram.0 terminated due to SIGILL
2019-03-05 05:56:57.005  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code null ()
2019-03-05 05:56:57.005  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2019-03-05 05:57:02.100  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 20443
2019-03-05 05:57:03.199  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 05:57:03.199  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 05:57:03.200  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 05:57:12.304  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 20473
2019-03-05 05:57:15.001  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGILL
2019-03-05 05:57:15.002  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 05:57:15.003  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 05:57:27.029  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 20511
2019-03-05 05:57:30.174  - error: Caught by controller[0]: Tue, 05 Mar 2019 04:57:29 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
2019-03-05 05:57:30.174  - error: Caught by controller[0]: In the future, you will have to enable it yourself.
2019-03-05 05:57:30.175  - error: Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30
2019-03-05 05:57:30.175  - warn: host.raspberrypi instance system.adapter.telegram.0 terminated due to SIGILL
2019-03-05 05:57:30.175  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code null ()
2019-03-05 05:57:30.175  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2019-03-05 05:57:33.223  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 20531
2019-03-05 05:57:34.331  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 05:57:34.331  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 05:57:34.332  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 05:57:45.028  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 20564
2019-03-05 05:57:47.682  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGILL
2019-03-05 05:57:47.682  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 05:57:47.683  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 05:58:00.198  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 20604
2019-03-05 05:58:03.193  - error: Caught by controller[0]: Tue, 05 Mar 2019 04:58:02 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
2019-03-05 05:58:03.194  - error: Caught by controller[0]: In the future, you will have to enable it yourself.
2019-03-05 05:58:03.194  - error: Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30
2019-03-05 05:58:03.194  - warn: host.raspberrypi instance system.adapter.telegram.0 terminated due to SIGILL
2019-03-05 05:58:03.195  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code null ()
2019-03-05 05:58:03.195  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2019-03-05 05:58:04.371  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 20619
2019-03-05 05:58:05.457  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 05:58:05.457  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 05:58:05.458  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 05:58:17.709  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 20655
2019-03-05 05:58:20.417  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGILL
2019-03-05 05:58:20.418  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 05:58:20.418  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 05:58:33.223  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 20696
2019-03-05 05:58:35.486  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 20708
2019-03-05 05:58:36.314  - error: Caught by controller[0]: Tue, 05 Mar 2019 04:58:36 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
2019-03-05 05:58:36.315  - error: Caught by controller[0]: In the future, you will have to enable it yourself.
2019-03-05 05:58:36.316  - error: Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30
2019-03-05 05:58:36.316  - warn: host.raspberrypi instance system.adapter.telegram.0 terminated due to SIGILL
2019-03-05 05:58:36.317  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code null ()
2019-03-05 05:58:36.317  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2019-03-05 05:58:36.669  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 05:58:36.670  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 05:58:36.671  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 05:58:50.445  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 20746
2019-03-05 05:58:53.287  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGILL
2019-03-05 05:58:53.287  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 05:58:53.288  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 05:59:06.341  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 20788
2019-03-05 05:59:06.718  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 20794
2019-03-05 05:59:07.868  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 05:59:07.869  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 05:59:07.869  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 05:59:09.437  - error: Caught by controller[0]: Tue, 05 Mar 2019 04:59:09 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
2019-03-05 05:59:09.438  - error: Caught by controller[0]: In the future, you will have to enable it yourself.
2019-03-05 05:59:09.438  - error: Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30
2019-03-05 05:59:09.439  - warn: host.raspberrypi instance system.adapter.telegram.0 terminated due to SIGILL
2019-03-05 05:59:09.439  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code null ()
2019-03-05 05:59:09.439  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2019-03-05 05:59:23.312  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 20837
2019-03-05 05:59:25.945  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGILL
2019-03-05 05:59:25.946  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 05:59:25.946  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 05:59:37.892  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 20875
2019-03-05 05:59:38.978  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 05:59:38.979  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 05:59:38.979  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 05:59:39.463  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 20884
2019-03-05 05:59:42.634  - error: Caught by controller[0]: Tue, 05 Mar 2019 04:59:42 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
2019-03-05 05:59:42.635  - error: Caught by controller[0]: In the future, you will have to enable it yourself.
2019-03-05 05:59:42.635  - error: Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30
2019-03-05 05:59:42.636  - warn: host.raspberrypi instance system.adapter.telegram.0 terminated due to SIGILL
2019-03-05 05:59:42.636  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code null ()
2019-03-05 05:59:42.636  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2019-03-05 05:59:55.984  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 20927
2019-03-05 05:59:58.590  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGILL
2019-03-05 05:59:58.591  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 05:59:58.591  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 06:00:09.005  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 20960
2019-03-05 06:00:10.046  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 06:00:10.047  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 06:00:10.047  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 06:00:12.671  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 20974
2019-03-05 06:00:15.638  - error: Caught by controller[0]: Tue, 05 Mar 2019 05:00:15 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
2019-03-05 06:00:15.638  - error: Caught by controller[0]: In the future, you will have to enable it yourself.
2019-03-05 06:00:15.639  - error: Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30
2019-03-05 06:00:15.639  - warn: host.raspberrypi instance system.adapter.telegram.0 terminated due to SIGILL
2019-03-05 06:00:15.639  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code null ()
2019-03-05 06:00:15.639  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2019-03-05 06:00:28.616  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 21015
2019-03-05 06:00:31.226  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGILL
2019-03-05 06:00:31.227  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 06:00:31.228  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 06:00:40.073  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 21045
2019-03-05 06:00:41.237  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 06:00:41.237  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 06:00:41.238  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 06:00:45.666  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 21064
2019-03-05 06:00:48.775  - error: Caught by controller[0]: Tue, 05 Mar 2019 05:00:48 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
2019-03-05 06:00:48.776  - error: Caught by controller[0]: In the future, you will have to enable it yourself.
2019-03-05 06:00:48.777  - error: Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30
2019-03-05 06:00:48.777  - warn: host.raspberrypi instance system.adapter.telegram.0 terminated due to SIGILL
2019-03-05 06:00:48.777  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code null ()
2019-03-05 06:00:48.777  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2019-03-05 06:01:01.251  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 21105
2019-03-05 06:01:03.938  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGILL
2019-03-05 06:01:03.939  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 06:01:03.939  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 06:01:11.262  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 21132
2019-03-05 06:01:12.352  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 06:01:12.353  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 06:01:12.353  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 06:01:18.806  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 21153
2019-03-05 06:01:21.975  - error: Caught by controller[0]: Tue, 05 Mar 2019 05:01:21 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
2019-03-05 06:01:21.976  - error: Caught by controller[0]: In the future, you will have to enable it yourself.
2019-03-05 06:01:21.976  - error: Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30
2019-03-05 06:01:21.977  - warn: host.raspberrypi instance system.adapter.telegram.0 terminated due to SIGILL
2019-03-05 06:01:21.977  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code null ()
2019-03-05 06:01:21.977  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2019-03-05 06:01:33.965  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 21191
2019-03-05 06:01:36.563  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGILL
2019-03-05 06:01:36.564  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 06:01:36.564  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 06:01:42.376  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 21215
2019-03-05 06:01:43.418  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 06:01:43.418  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 06:01:43.419  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 06:01:52.001  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 21241
2019-03-05 06:01:55.004  - error: Caught by controller[0]: Tue, 05 Mar 2019 05:01:54 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
2019-03-05 06:01:55.005  - error: Caught by controller[0]: In the future, you will have to enable it yourself.
2019-03-05 06:01:55.005  - error: Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30
2019-03-05 06:01:55.005  - warn: host.raspberrypi instance system.adapter.telegram.0 terminated due to SIGILL
2019-03-05 06:01:55.006  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code null ()
2019-03-05 06:01:55.006  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2019-03-05 06:02:06.589  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 21277
2019-03-05 06:02:09.233  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGILL
2019-03-05 06:02:09.235  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 06:02:09.235  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 06:02:13.458  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 21297
2019-03-05 06:02:14.600  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 06:02:14.601  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 06:02:14.601  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 06:02:25.030  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 21327
2019-03-05 06:02:27.998  - error: Caught by controller[0]: Tue, 05 Mar 2019 05:02:27 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
2019-03-05 06:02:27.998  - error: Caught by controller[0]: In the future, you will have to enable it yourself.
2019-03-05 06:02:27.999  - error: Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30
2019-03-05 06:02:27.999  - warn: host.raspberrypi instance system.adapter.telegram.0 terminated due to SIGILL
2019-03-05 06:02:27.999  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code null ()
2019-03-05 06:02:27.999  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2019-03-05 06:02:39.260  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 21362
2019-03-05 06:02:41.797  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGILL
2019-03-05 06:02:41.798  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 06:02:41.798  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 06:02:44.626  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 21379
2019-03-05 06:02:45.716  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 06:02:45.717  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 06:02:45.717  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 06:02:58.023  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 21411
2019-03-05 06:03:00.945  - error: Caught by controller[0]: Tue, 05 Mar 2019 05:03:00 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
2019-03-05 06:03:00.946  - error: Caught by controller[0]: In the future, you will have to enable it yourself.
2019-03-05 06:03:00.947  - error: Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30
2019-03-05 06:03:00.947  - warn: host.raspberrypi instance system.adapter.telegram.0 terminated due to SIGILL
2019-03-05 06:03:00.948  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code null ()
2019-03-05 06:03:00.948  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2019-03-05 06:03:11.824  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 21445
2019-03-05 06:03:14.489  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGILL
2019-03-05 06:03:14.489  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 06:03:14.490  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 06:03:15.742  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 21459
2019-03-05 06:03:16.843  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 06:03:16.844  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 06:03:16.844  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 06:03:30.973  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 21496
2019-03-05 06:03:34.021  - error: Caught by controller[0]: Tue, 05 Mar 2019 05:03:33 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
2019-03-05 06:03:34.022  - error: Caught by controller[0]: In the future, you will have to enable it yourself.
2019-03-05 06:03:34.022  - error: Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30
2019-03-05 06:03:34.022  - warn: host.raspberrypi instance system.adapter.telegram.0 terminated due to SIGILL
2019-03-05 06:03:34.023  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code null ()
2019-03-05 06:03:34.023  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2019-03-05 06:03:44.514  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 21529
2019-03-05 06:03:46.869  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 21540
2019-03-05 06:03:47.115  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGILL
2019-03-05 06:03:47.115  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 06:03:47.116  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 06:03:48.022  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 06:03:48.023  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 06:03:48.024  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 06:04:04.048  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 21581
2019-03-05 06:04:07.017  - error: Caught by controller[0]: Tue, 05 Mar 2019 05:04:06 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
2019-03-05 06:04:07.017  - error: Caught by controller[0]: In the future, you will have to enable it yourself.
2019-03-05 06:04:07.018  - error: Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30
2019-03-05 06:04:07.018  - warn: host.raspberrypi instance system.adapter.telegram.0 terminated due to SIGILL
2019-03-05 06:04:07.018  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code null ()
2019-03-05 06:04:07.019  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2019-03-05 06:04:17.140  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 21613
2019-03-05 06:04:18.048  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 21620
2019-03-05 06:04:19.262  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 06:04:19.262  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 06:04:19.263  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 06:04:19.859  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGILL
2019-03-05 06:04:19.860  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 06:04:19.860  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 06:04:37.048  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 21665
2019-03-05 06:04:39.956  - error: Caught by controller[0]: Tue, 05 Mar 2019 05:04:39 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
2019-03-05 06:04:39.957  - error: Caught by controller[0]: In the future, you will have to enable it yourself.
2019-03-05 06:04:39.957  - error: Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30
2019-03-05 06:04:39.958  - warn: host.raspberrypi instance system.adapter.telegram.0 terminated due to SIGILL
2019-03-05 06:04:39.958  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code null ()
2019-03-05 06:04:39.958  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2019-03-05 06:04:49.302  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 21695
2019-03-05 06:04:49.890  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 21702
2019-03-05 06:04:50.444  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 06:04:50.444  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 06:04:50.445  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 06:04:52.702  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGILL
2019-03-05 06:04:52.703  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 06:04:52.704  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 06:05:09.984  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 21747
2019-03-05 06:05:12.923  - error: Caught by controller[0]: Tue, 05 Mar 2019 05:05:12 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
2019-03-05 06:05:12.924  - error: Caught by controller[0]: In the future, you will have to enable it yourself.
2019-03-05 06:05:12.924  - error: Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30
2019-03-05 06:05:12.925  - warn: host.raspberrypi instance system.adapter.telegram.0 terminated due to SIGILL
2019-03-05 06:05:12.925  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code null ()
2019-03-05 06:05:12.925  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2019-03-05 06:05:20.472  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 21772
2019-03-05 06:05:21.574  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 06:05:21.574  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 06:05:21.575  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 06:05:22.732  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 21783
2019-03-05 06:05:25.352  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGILL
2019-03-05 06:05:25.353  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 06:05:25.354  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 06:05:42.948  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 21828
2019-03-05 06:05:46.100  - error: Caught by controller[0]: Tue, 05 Mar 2019 05:05:45 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
2019-03-05 06:05:46.100  - error: Caught by controller[0]: In the future, you will have to enable it yourself.
2019-03-05 06:05:46.101  - error: Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30
2019-03-05 06:05:46.101  - warn: host.raspberrypi instance system.adapter.telegram.0 terminated due to SIGILL
2019-03-05 06:05:46.101  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code null ()
2019-03-05 06:05:46.101  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2019-03-05 06:05:51.597  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 21850
2019-03-05 06:05:52.710  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 06:05:52.710  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 06:05:52.711  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 06:05:55.411  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 21865
2019-03-05 06:05:58.049  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGILL
2019-03-05 06:05:58.049  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 06:05:58.050  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 06:06:16.130  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 21914
2019-03-05 06:06:19.135  - error: Caught by controller[0]: Tue, 05 Mar 2019 05:06:18 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
2019-03-05 06:06:19.137  - error: Caught by controller[0]: In the future, you will have to enable it yourself.
2019-03-05 06:06:19.137  - error: Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30
2019-03-05 06:06:19.137  - warn: host.raspberrypi instance system.adapter.telegram.0 terminated due to SIGILL
2019-03-05 06:06:19.138  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code null ()
2019-03-05 06:06:19.138  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2019-03-05 06:06:22.735  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 21932
2019-03-05 06:06:23.781  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 06:06:23.782  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 06:06:23.782  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 06:06:28.074  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 21948
2019-03-05 06:06:30.694  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGILL
2019-03-05 06:06:30.695  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 06:06:30.695  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 06:06:49.164  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 21994
2019-03-05 06:06:52.158  - error: Caught by controller[0]: Tue, 05 Mar 2019 05:06:51 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
2019-03-05 06:06:52.158  - error: Caught by controller[0]: In the future, you will have to enable it yourself.
2019-03-05 06:06:52.159  - error: Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30
2019-03-05 06:06:52.159  - warn: host.raspberrypi instance system.adapter.telegram.0 terminated due to SIGILL
2019-03-05 06:06:52.159  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code null ()
2019-03-05 06:06:52.160  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2019-03-05 06:06:53.807  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 22009
2019-03-05 06:06:54.886  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 06:06:54.887  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 06:06:54.887  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 06:07:00.720  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 22028
2019-03-05 06:07:03.384  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGILL
2019-03-05 06:07:03.385  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 06:07:03.385  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 06:07:22.199  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 22073
2019-03-05 06:07:24.914  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 22085
2019-03-05 06:07:25.310  - error: Caught by controller[0]: Tue, 05 Mar 2019 05:07:24 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
2019-03-05 06:07:25.312  - error: Caught by controller[0]: In the future, you will have to enable it yourself.
2019-03-05 06:07:25.313  - error: Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30
2019-03-05 06:07:25.313  - warn: host.raspberrypi instance system.adapter.telegram.0 terminated due to SIGILL
2019-03-05 06:07:25.313  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code null ()
2019-03-05 06:07:25.314  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2019-03-05 06:07:26.024  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 06:07:26.024  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 06:07:26.025  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 06:07:33.421  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 22107
2019-03-05 06:07:36.138  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGILL
2019-03-05 06:07:36.138  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 06:07:36.139  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 06:07:55.341  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 22153
2019-03-05 06:07:56.051  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 22161
2019-03-05 06:07:57.203  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 06:07:57.204  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 06:07:57.204  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 06:07:58.479  - error: Caught by controller[0]: Tue, 05 Mar 2019 05:07:58 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
2019-03-05 06:07:58.480  - error: Caught by controller[0]: In the future, you will have to enable it yourself.
2019-03-05 06:07:58.481  - error: Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30
2019-03-05 06:07:58.481  - warn: host.raspberrypi instance system.adapter.telegram.0 terminated due to SIGILL
2019-03-05 06:07:58.481  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code null ()
2019-03-05 06:07:58.482  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2019-03-05 06:08:06.162  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 22186
2019-03-05 06:08:08.967  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGILL
2019-03-05 06:08:08.967  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 06:08:08.968  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 06:08:27.229  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 22230
2019-03-05 06:08:28.403  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 06:08:28.404  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 06:08:28.404  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 06:08:28.506  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 22238
2019-03-05 06:08:31.631  - error: Caught by controller[0]: Tue, 05 Mar 2019 05:08:31 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
2019-03-05 06:08:31.632  - error: Caught by controller[0]: In the future, you will have to enable it yourself.
2019-03-05 06:08:31.632  - error: Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30
2019-03-05 06:08:31.633  - warn: host.raspberrypi instance system.adapter.telegram.0 terminated due to SIGILL
2019-03-05 06:08:31.633  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code null ()
2019-03-05 06:08:31.633  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2019-03-05 06:08:39.008  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 22264
2019-03-05 06:08:41.641  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGILL
2019-03-05 06:08:41.642  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 06:08:41.642  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 06:08:58.441  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 22306
2019-03-05 06:08:59.524  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 06:08:59.525  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 06:08:59.525  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 06:09:01.659  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 22318
2019-03-05 06:09:04.798  - error: Caught by controller[0]: Tue, 05 Mar 2019 05:09:04 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
2019-03-05 06:09:04.798  - error: Caught by controller[0]: In the future, you will have to enable it yourself.
2019-03-05 06:09:04.799  - error: Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30
2019-03-05 06:09:04.799  - warn: host.raspberrypi instance system.adapter.telegram.0 terminated due to SIGILL
2019-03-05 06:09:04.799  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code null ()
2019-03-05 06:09:04.799  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2019-03-05 06:09:11.667  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 22342
2019-03-05 06:09:14.242  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGILL
2019-03-05 06:09:14.242  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 06:09:14.243  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 06:09:29.565  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 22379
2019-03-05 06:09:30.628  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 06:09:30.628  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 06:09:30.629  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 06:09:34.821  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 22396
2019-03-05 06:09:37.843  - error: Caught by controller[0]: Tue, 05 Mar 2019 05:09:37 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
2019-03-05 06:09:37.843  - error: Caught by controller[0]: In the future, you will have to enable it yourself.
2019-03-05 06:09:37.844  - error: Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30
2019-03-05 06:09:37.844  - warn: host.raspberrypi instance system.adapter.telegram.0 terminated due to SIGILL
2019-03-05 06:09:37.844  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code null ()
2019-03-05 06:09:37.844  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2019-03-05 06:09:44.276  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 22418
2019-03-05 06:09:46.875  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGILL
2019-03-05 06:09:46.876  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 06:09:46.877  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 06:10:00.650  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 22453
2019-03-05 06:10:01.822  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 06:10:01.823  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 06:10:01.823  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 06:10:07.864  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 22471
2019-03-05 06:10:10.891  - error: Caught by controller[0]: Tue, 05 Mar 2019 05:10:10 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
2019-03-05 06:10:10.892  - error: Caught by controller[0]: In the future, you will have to enable it yourself.
2019-03-05 06:10:10.892  - error: Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30
2019-03-05 06:10:10.892  - warn: host.raspberrypi instance system.adapter.telegram.0 terminated due to SIGILL
2019-03-05 06:10:10.892  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code null ()
2019-03-05 06:10:10.893  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2019-03-05 06:10:16.897  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 22494
2019-03-05 06:10:19.597  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGILL
2019-03-05 06:10:19.598  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 06:10:19.598  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 06:10:31.844  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 22527
2019-03-05 06:10:32.894  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 06:10:32.895  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 06:10:32.895  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 06:10:40.912  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 22549
2019-03-05 06:10:43.908  - error: Caught by controller[0]: Tue, 05 Mar 2019 05:10:43 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
2019-03-05 06:10:43.908  - error: Caught by controller[0]: In the future, you will have to enable it yourself.
2019-03-05 06:10:43.909  - error: Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30
2019-03-05 06:10:43.909  - warn: host.raspberrypi instance system.adapter.telegram.0 terminated due to SIGILL
2019-03-05 06:10:43.909  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code null ()
2019-03-05 06:10:43.909  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2019-03-05 06:10:49.618  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 22570
2019-03-05 06:10:52.382  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGILL
2019-03-05 06:10:52.383  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 06:10:52.383  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 06:11:02.927  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 22602
2019-03-05 06:11:04.017  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 06:11:04.018  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 06:11:04.018  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 06:11:13.934  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 22627
2019-03-05 06:11:17.050  - error: Caught by controller[0]: Tue, 05 Mar 2019 05:11:16 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
2019-03-05 06:11:17.050  - error: Caught by controller[0]: In the future, you will have to enable it yourself.
2019-03-05 06:11:17.051  - error: Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30
2019-03-05 06:11:17.051  - warn: host.raspberrypi instance system.adapter.telegram.0 terminated due to SIGILL
2019-03-05 06:11:17.051  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code null ()
2019-03-05 06:11:17.051  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2019-03-05 06:11:22.405  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 22648
2019-03-05 06:11:25.135  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGILL
2019-03-05 06:11:25.136  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 06:11:25.137  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 06:11:34.040  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 22674
2019-03-05 06:11:35.197  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 06:11:35.200  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 06:11:35.200  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 06:11:47.072  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 22703
2019-03-05 06:11:50.024  - error: Caught by controller[0]: Tue, 05 Mar 2019 05:11:49 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
2019-03-05 06:11:50.025  - error: Caught by controller[0]: In the future, you will have to enable it yourself.
2019-03-05 06:11:50.025  - error: Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30
2019-03-05 06:11:50.026  - warn: host.raspberrypi instance system.adapter.telegram.0 terminated due to SIGILL
2019-03-05 06:11:50.026  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code null ()
2019-03-05 06:11:50.026  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2019-03-05 06:11:55.158  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 22722
2019-03-05 06:11:57.759  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGILL
2019-03-05 06:11:57.760  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 06:11:57.760  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 06:12:05.234  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 22746
2019-03-05 06:12:06.418  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 06:12:06.419  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 06:12:06.419  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 06:12:20.059  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 22778
2019-03-05 06:12:23.122  - error: Caught by controller[0]: Tue, 05 Mar 2019 05:12:22 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
2019-03-05 06:12:23.123  - error: Caught by controller[0]: In the future, you will have to enable it yourself.
2019-03-05 06:12:23.123  - error: Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30
2019-03-05 06:12:23.123  - warn: host.raspberrypi instance system.adapter.telegram.0 terminated due to SIGILL
2019-03-05 06:12:23.124  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code null ()
2019-03-05 06:12:23.124  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2019-03-05 06:12:27.783  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 22798
2019-03-05 06:12:30.503  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGILL
2019-03-05 06:12:30.504  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 06:12:30.504  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 06:12:36.443  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 22819
2019-03-05 06:12:37.566  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 06:12:37.567  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 06:12:37.568  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 06:12:53.145  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 22854
2019-03-05 06:12:56.271  - error: Caught by controller[0]: Tue, 05 Mar 2019 05:12:55 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
2019-03-05 06:12:56.272  - error: Caught by controller[0]: In the future, you will have to enable it yourself.
2019-03-05 06:12:56.272  - error: Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30
2019-03-05 06:12:56.272  - warn: host.raspberrypi instance system.adapter.telegram.0 terminated due to SIGILL
2019-03-05 06:12:56.272  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code null ()
2019-03-05 06:12:56.273  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2019-03-05 06:13:00.528  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 22872
2019-03-05 06:13:03.341  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGILL
2019-03-05 06:13:03.342  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 06:13:03.342  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 06:13:07.604  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 22890
2019-03-05 06:13:08.707  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 06:13:08.708  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 06:13:08.709  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 06:13:26.295  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 22927
2019-03-05 06:13:29.249  - error: Caught by controller[0]: Tue, 05 Mar 2019 05:13:28 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
2019-03-05 06:13:29.249  - error: Caught by controller[0]: In the future, you will have to enable it yourself.
2019-03-05 06:13:29.250  - error: Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30
2019-03-05 06:13:29.250  - warn: host.raspberrypi instance system.adapter.telegram.0 terminated due to SIGILL
2019-03-05 06:13:29.250  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code null ()
2019-03-05 06:13:29.251  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2019-03-05 06:13:33.362  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 22945
2019-03-05 06:13:35.895  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGILL
2019-03-05 06:13:35.896  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 06:13:35.896  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 06:13:38.733  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 22959
2019-03-05 06:13:39.912  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 06:13:39.913  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 06:13:39.913  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 06:13:59.271  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 23000
2019-03-05 06:14:02.189  - error: Caught by controller[0]: Tue, 05 Mar 2019 05:14:01 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
2019-03-05 06:14:02.189  - error: Caught by controller[0]: In the future, you will have to enable it yourself.
2019-03-05 06:14:02.190  - error: Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30
2019-03-05 06:14:02.190  - warn: host.raspberrypi instance system.adapter.telegram.0 terminated due to SIGILL
2019-03-05 06:14:02.190  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code null ()
2019-03-05 06:14:02.190  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2019-03-05 06:14:05.931  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 23016
2019-03-05 06:14:08.549  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGILL
2019-03-05 06:14:08.550  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 06:14:08.550  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 06:14:09.947  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 23029
2019-03-05 06:14:11.031  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 06:14:11.032  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 06:14:11.032  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 06:14:32.212  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 23072
2019-03-05 06:14:35.303  - error: Caught by controller[0]: Tue, 05 Mar 2019 05:14:35 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
2019-03-05 06:14:35.303  - error: Caught by controller[0]: In the future, you will have to enable it yourself.
2019-03-05 06:14:35.304  - error: Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30
2019-03-05 06:14:35.304  - warn: host.raspberrypi instance system.adapter.telegram.0 terminated due to SIGILL
2019-03-05 06:14:35.304  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code null ()
2019-03-05 06:14:35.305  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2019-03-05 06:14:38.583  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 23089
2019-03-05 06:14:41.056  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 23099
2019-03-05 06:14:41.150  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGILL
2019-03-05 06:14:41.151  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 06:14:41.151  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 06:14:42.111  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 06:14:42.111  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 06:14:42.112  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 06:15:05.338  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 23143
2019-03-05 06:15:08.334  - error: Caught by controller[0]: Tue, 05 Mar 2019 05:15:08 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
2019-03-05 06:15:08.335  - error: Caught by controller[0]: In the future, you will have to enable it yourself.
2019-03-05 06:15:08.335  - error: Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30
2019-03-05 06:15:08.336  - warn: host.raspberrypi instance system.adapter.telegram.0 terminated due to SIGILL
2019-03-05 06:15:08.336  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code null ()
2019-03-05 06:15:08.337  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2019-03-05 06:15:11.187  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 23158
2019-03-05 06:15:12.135  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 23166
2019-03-05 06:15:13.352  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 06:15:13.353  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 06:15:13.354  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 06:15:13.916  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGILL
2019-03-05 06:15:13.916  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 06:15:13.917  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 06:15:38.373  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 23213
2019-03-05 06:15:41.393  - error: Caught by controller[0]: Tue, 05 Mar 2019 05:15:41 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
2019-03-05 06:15:41.394  - error: Caught by controller[0]: In the future, you will have to enable it yourself.
2019-03-05 06:15:41.394  - error: Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30
2019-03-05 06:15:41.394  - warn: host.raspberrypi instance system.adapter.telegram.0 terminated due to SIGILL
2019-03-05 06:15:41.395  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code null ()
2019-03-05 06:15:41.395  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2019-03-05 06:15:43.388  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 23227
2019-03-05 06:15:43.946  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 23234
2019-03-05 06:15:44.538  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 06:15:44.539  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 06:15:44.539  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 06:15:46.600  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGILL
2019-03-05 06:15:46.601  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 06:15:46.601  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 06:16:11.429  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 23286
2019-03-05 06:16:14.444  - error: Caught by controller[0]: Tue, 05 Mar 2019 05:16:14 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
2019-03-05 06:16:14.444  - error: Caught by controller[0]: In the future, you will have to enable it yourself.
2019-03-05 06:16:14.445  - error: Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30
2019-03-05 06:16:14.445  - warn: host.raspberrypi instance system.adapter.telegram.0 terminated due to SIGILL
2019-03-05 06:16:14.446  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code null ()
2019-03-05 06:16:14.446  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2019-03-05 06:16:14.560  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 23298
2019-03-05 06:16:15.593  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 06:16:15.594  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 06:16:15.594  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 06:16:16.635  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 23307
2019-03-05 06:16:19.293  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGILL
2019-03-05 06:16:19.294  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 06:16:19.294  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 06:16:44.469  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 23358
2019-03-05 06:16:45.617  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 23366
2019-03-05 06:16:46.812  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 06:16:46.813  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 06:16:46.813  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 06:16:47.554  - error: Caught by controller[0]: Tue, 05 Mar 2019 05:16:47 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
2019-03-05 06:16:47.555  - error: Caught by controller[0]: In the future, you will have to enable it yourself.
2019-03-05 06:16:47.555  - error: Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30
2019-03-05 06:16:47.555  - warn: host.raspberrypi instance system.adapter.telegram.0 terminated due to SIGILL
2019-03-05 06:16:47.555  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code null ()
2019-03-05 06:16:47.556  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2019-03-05 06:16:49.318  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 23378
2019-03-05 06:16:51.909  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGILL
2019-03-05 06:16:51.910  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 06:16:51.911  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 06:17:16.841  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 23431
2019-03-05 06:17:17.580  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 23439
2019-03-05 06:17:18.063  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 06:17:18.063  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 06:17:18.064  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 06:17:20.564  - error: Caught by controller[0]: Tue, 05 Mar 2019 05:17:20 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
2019-03-05 06:17:20.564  - error: Caught by controller[0]: In the future, you will have to enable it yourself.
2019-03-05 06:17:20.565  - error: Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30
2019-03-05 06:17:20.565  - warn: host.raspberrypi instance system.adapter.telegram.0 terminated due to SIGILL
2019-03-05 06:17:20.566  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code null ()
2019-03-05 06:17:20.566  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2019-03-05 06:17:21.936  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 23452
2019-03-05 06:17:24.484  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGILL
2019-03-05 06:17:24.484  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 06:17:24.485  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 06:17:48.104  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 23499
2019-03-05 06:17:49.151  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 06:17:49.152  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 06:17:49.152  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 06:17:50.590  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 23509
2019-03-05 06:17:53.618  - error: Caught by controller[0]: Tue, 05 Mar 2019 05:17:53 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
2019-03-05 06:17:53.619  - error: Caught by controller[0]: In the future, you will have to enable it yourself.
2019-03-05 06:17:53.619  - error: Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30
2019-03-05 06:17:53.619  - warn: host.raspberrypi instance system.adapter.telegram.0 terminated due to SIGILL
2019-03-05 06:17:53.619  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code null ()
2019-03-05 06:17:53.620  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2019-03-05 06:17:54.510  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 23521
2019-03-05 06:17:57.063  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGILL
2019-03-05 06:17:57.065  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 06:17:57.065  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 06:18:19.176  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 23566
2019-03-05 06:18:20.310  - warn: host.raspberrypi instance system.adapter.broadlink2.0 terminated due to SIGILL
2019-03-05 06:18:20.310  - error: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code null ()
2019-03-05 06:18:20.311  - info: host.raspberrypi Restart adapter system.adapter.broadlink2.0 because enabled
2019-03-05 06:18:23.659  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 23579
2019-03-05 06:18:26.665  - error: Caught by controller[0]: Tue, 05 Mar 2019 05:18:26 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
2019-03-05 06:18:26.665  - error: Caught by controller[0]: In the future, you will have to enable it yourself.
2019-03-05 06:18:26.666  - error: Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30
2019-03-05 06:18:26.666  - warn: host.raspberrypi instance system.adapter.telegram.0 terminated due to SIGILL
2019-03-05 06:18:26.666  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code null ()
2019-03-05 06:18:26.667  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2019-03-05 06:18:27.088  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 23591
2019-03-05 06:18:29.824  - warn: host.raspberrypi instance system.adapter.tr-064.0 terminated due to SIGILL
2019-03-05 06:18:29.824  - error: host.raspberrypi instance system.adapter.tr-064.0 terminated with code null ()
2019-03-05 06:18:29.825  - info: host.raspberrypi Restart adapter system.adapter.tr-064.0 because enabled
2019-03-05 06:01:19.212  - info: host.raspberrypi iobroker.js-controller version 1.5.7 js-controller starting
2019-03-05 06:01:19.225  - info: host.raspberrypi Copyright (c) 2014-2018 bluefox, 2014 hobbyquaker
2019-03-05 06:01:19.226  - info: host.raspberrypi hostname: raspberrypi, node: v8.15.1
2019-03-05 06:01:19.234  - info: host.raspberrypi ip addresses: 192.168.0.195 2a02:8071:3eb2:d900:76de:54f9:2364:a90d fe80::a094:393e:29f3:7201
2019-03-05 06:01:19.352  - info: host.raspberrypi  inMem-states listening on port 9000
2019-03-05 06:01:20.116  - info: host.raspberrypi  inMem-objects listening on port 9001
2019-03-05 06:01:20.165  - info: host.raspberrypi InMemoryDB connected
2019-03-05 06:01:20.207  - info: host.raspberrypi 27 instances found
2019-03-05 06:01:20.285  - info: host.raspberrypi starting 19 instances
2019-03-05 06:01:20.485  - info: host.raspberrypi instance system.adapter.admin.0 started with pid 537
2019-03-05 06:01:24.312  - info: host.raspberrypi instance system.adapter.discovery.0 started with pid 543
2019-03-05 06:01:26.140  - info: admin.0 starting. Version 3.6.0 in /opt/iobroker/node_modules/iobroker.admin, node: v8.15.1
2019-03-05 06:01:26.241  - info: admin.0 requesting all states
2019-03-05 06:01:26.246  - info: admin.0 requesting all objects
2019-03-05 06:01:26.249  - info: admin.0 Request actual repository...
2019-03-05 06:01:27.001  - info: admin.0 received all states
2019-03-05 06:01:27.102  - info: discovery.0 starting. Version 1.2.4 in /opt/iobroker/node_modules/iobroker.discovery, node: v8.15.1
2019-03-05 06:01:27.689  - info: admin.0 received all objects
2019-03-05 06:01:27.708  - warn: admin.0 No repository source configured
2019-03-05 06:01:27.774  - info: admin.0 http server listening on port 8081
2019-03-05 06:01:27.775  - info: admin.0 Use link "http://localhost:8081" to configure.
2019-03-05 06:01:28.222  - info: host.raspberrypi Update repository "latest" under "http://download.iobroker.net/sources-dist-latest.json"
2019-03-05 06:01:29.493  - info: host.raspberrypi instance system.adapter.javascript.0 started with pid 565
2019-03-05 06:01:32.530  - info: host.raspberrypi instance system.adapter.web.0 started with pid 571
2019-03-05 06:01:33.385  - info: admin.0 Repository received successfully.
2019-03-05 06:01:36.323  - info: host.raspberrypi instance system.adapter.lgtv.1 started with pid 582
2019-03-05 06:01:36.257  - info: web.0 starting. Version 2.4.1 in /opt/iobroker/node_modules/iobroker.web, node: v8.15.1
2019-03-05 06:01:36.915  - info: web.0 socket.io server listening on port 8082
2019-03-05 06:01:36.924  - info: web.0 http server listening on port 8082
2019-03-05 06:01:37.099  - info: javascript.0 starting. Version 4.1.8 in /opt/iobroker/node_modules/iobroker.javascript, node: v8.15.1
2019-03-05 06:01:37.213  - info: javascript.0 requesting all states
2019-03-05 06:01:37.219  - info: javascript.0 requesting all objects
2019-03-05 06:01:37.834  - info: javascript.0 received all states
2019-03-05 06:31:53.287  - info: javascript.0 received all objects
2019-03-05 06:31:53.602  - info: javascript.0 Start javascript script.js.Bridge.RF_Bridge
2019-03-05 06:31:53.716  - info: javascript.0 script.js.Bridge.RF_Bridge: registered 2 subscriptions and 0 schedules
2019-03-05 06:31:53.728  - info: javascript.0 Start javascript script.js.Multimedia.Fernseher
2019-03-05 06:31:53.748  - info: javascript.0 script.js.Multimedia.Fernseher: registered 7 subscriptions and 0 schedules
2019-03-05 06:31:53.752  - info: javascript.0 Start javascript script.js.Beleuchtung.Flur
2019-03-05 06:31:53.765  - info: javascript.0 script.js.Beleuchtung.Flur: registered 1 subscription and 0 schedules
2019-03-05 06:31:53.771  - info: javascript.0 Start javascript script.js.Beleuchtung.Schlafzimmer
2019-03-05 06:31:53.787  - info: javascript.0 script.js.Beleuchtung.Schlafzimmer: registered 7 subscriptions and 0 schedules
2019-03-05 06:31:53.791  - info: javascript.0 Start javascript script.js.Beleuchtung.Wohnzimmer
2019-03-05 06:31:53.803  - info: javascript.0 script.js.Beleuchtung.Wohnzimmer: registered 1 subscription and 0 schedules
2019-03-05 06:31:53.809  - info: javascript.0 Start javascript script.js.Szenen.Zentral_Steuerung
2019-03-05 06:31:53.822  - info: javascript.0 script.js.Szenen.Zentral_Steuerung: registered 3 subscriptions and 0 schedules
2019-03-05 06:31:53.843  - info: javascript.0 Start javascript script.js.Vis.Fernseher
2019-03-05 06:31:53.860  - info: javascript.0 script.js.Vis.Fernseher: registered 5 subscriptions and 0 schedules
2019-03-05 06:31:53.865  - info: javascript.0 Start javascript script.js.Meldungen.Telegram
2019-03-05 06:31:53.880  - info: javascript.0 script.js.Meldungen.Telegram: registered 4 subscriptions and 0 schedules
2019-03-05 06:31:53.793  - info: lgtv.1 starting. Version 1.0.7 in /opt/iobroker/node_modules/iobroker.lgtv, node: v8.15.1
2019-03-05 06:31:53.875  - info: lgtv.1 Ready. Configured WebOS TV IP: 192.168.0.31
2019-03-05 06:31:55.059  - info: host.raspberrypi instance system.adapter.sonoff.0 started with pid 624
2019-03-05 06:31:56.749  - info: web.0 ==>Connected system.user.admin from ::ffff:192.168.0.28
2019-03-05 06:31:57.833  - info: web.0 ==>Connected system.user.admin from ::ffff:192.168.0.28
2019-03-05 06:31:57.887  - info: sonoff.0 starting. Version 2.2.2 in /opt/iobroker/node_modules/iobroker.sonoff, node: v8.15.1
2019-03-05 06:31:58.030  - info: sonoff.0 Starting MQTT authenticated  server on port 1883
2019-03-05 06:31:59.060  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 668
2019-03-05 06:31:59.331  - warn: sonoff.0 Client "Nachtlicht Benchy" not connected
2019-03-05 06:32:01.041  - info: broadlink2.0 starting. Version 1.9.1 in /opt/iobroker/node_modules/iobroker.broadlink2, node: v8.15.1
2019-03-05 06:32:02.171  - info: broadlink2.0 Discover UDP devices for 10sec on broadlink2.0
2019-03-05 06:32:02.560  - info: broadlink2.0 Device RM:BroadlinkMini dedected: 192.168.0.32,IPv4,80,128,10039,rm,RM:BroadlinkMini,RM Mini,37:27:20:0:a8:c0
2019-03-05 06:32:06.405  - info: sonoff.0 Client [Sonoff_Bridge] connected with secret 1551763926373_919
2019-03-05 06:32:06.800  - info: sonoff.0 Client [Nachtlicht Marcus] connected with secret 1551763926763_2752
2019-03-05 06:32:06.967  - info: sonoff.0 Client [Nachtlicht Liah] connected with secret 1551763926964_4805
2019-03-05 06:32:07.656  - info: sonoff.0 Client [Nachtlicht Benchy] connected with secret 1551763927654_8603
2019-03-05 06:32:07.873  - info: broadlink2.0 Adapter broadlink2.0 started and found 1 devices named 'RM:BroadlinkMini'.
2019-03-05 06:32:08.286  - info: sonoff.0 Client [Stehlampe] connected with secret 1551763928284_6188
2019-03-05 06:32:17.510  - info: vis.0 starting. Version 1.1.10 in /opt/iobroker/node_modules/iobroker.vis, node: v8.15.1
2019-03-05 06:32:17.878  - info: vis.0 vis license is OK.
2019-03-05 06:32:19.063  - info: host.raspberrypi instance system.adapter.sayit.0 started with pid 781
2019-03-05 06:32:19.589  - info: host.raspberrypi instance system.adapter.vis.0 terminated while should be started once
2019-03-05 06:32:21.112  - info: sayit.0 starting. Version 1.7.0 in /opt/iobroker/node_modules/iobroker.sayit, node: v8.15.1
2019-03-05 06:32:21.176  - info: sayit.0 Upload announce mp3 files
2019-03-05 06:32:21.295  - info: sayit.0 All files uploaded
2019-03-05 06:32:31.071  - info: host.raspberrypi instance system.adapter.shelly.0 started with pid 795
2019-03-05 06:32:33.548  - info: shelly.0 starting. Version 2.1.4 in /opt/iobroker/node_modules/iobroker.shelly, node: v8.15.1
2019-03-05 06:32:33.631  - info: shelly.0 Starting shelly.0 in version 2.1.4
2019-03-05 06:32:34.622  - info: shelly.0 Listening for Shelly packets in the network
2019-03-05 06:32:35.071  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 809
2019-03-05 06:32:39.079  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 815
2019-03-05 06:32:39.557  - info: telegram.0 starting. Version 1.4.3 in /opt/iobroker/node_modules/iobroker.telegram, node: v8.15.1
2019-03-05 06:32:42.714  - info: tr-064.0 starting. Version 0.4.18 in /opt/iobroker/node_modules/iobroker.tr-064, node: v8.15.1
2019-03-05 06:32:43.078  - info: host.raspberrypi instance system.adapter.iot.0 started with pid 837
2019-03-05 06:32:47.078  - info: host.raspberrypi instance system.adapter.zigbee.0 started with pid 843
2019-03-05 06:32:47.758  - info: iot.0 starting. Version 0.3.1 in /opt/iobroker/node_modules/iobroker.iot, node: v8.15.1
2019-03-05 06:32:47.927  - info: iot.0 Connecting with a18wym7vjdl22g.iot.eu-west-1.amazonaws.com
2019-03-05 06:32:49.857  - info: iot.0 Connection changed: connect
2019-03-05 06:32:49.923  - error: iot.0 Cannot report device state: null
2019-03-05 06:32:49.926  - warn: iot.0 Invalid URL key. Status update is disabled: {"error":"Unsupported version"}
2019-03-05 06:32:51.583  - info: zigbee.0 starting. Version 0.9.2 in /opt/iobroker/node_modules/iobroker.zigbee, node: v8.15.1
2019-03-05 06:32:51.652  - info: zigbee.0 Start on port: /dev/serial/by-id/usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B0018E1AA6E-if00 with panID 6754 channel 11
2019-03-05 06:32:51.653  - info: zigbee.0 Queue is: true
2019-03-05 06:32:51.759  - info: zigbee.0 Reset coordinator
2019-03-05 06:32:53.182  - info: zigbee.0 zigbee-shepherd started!
2019-03-05 06:32:53.192  - info: zigbee.0 zigbee-shepherd ready. version: 2.6.3 rev 20180815
2019-03-05 06:39:51.571  - info: web.0 <==Disconnect system.user.admin from ::ffff:192.168.0.28 material.0
2019-03-05 06:39:52.560  - info: web.0 <==Disconnect system.user.admin from ::ffff:192.168.0.28 material.0
2019-03-05 07:07:24.742  - info: web.0 ==>Connected system.user.admin from ::ffff:192.168.0.30
2019-03-05 07:09:13.994  - info: web.0 <==Disconnect system.user.admin from ::ffff:192.168.0.30 material.0
2019-03-05 07:16:05.313  - info: javascript.0 script.js.Multimedia.Fernseher: stehlampe ausschalten
2019-03-05 07:16:05.315  - info: javascript.0 script.js.Multimedia.Fernseher: NaN
2019-03-05 07:16:05.317  - info: javascript.0 script.js.Multimedia.Fernseher: NaN
2019-03-05 07:16:05.320  - info: javascript.0 script.js.Multimedia.Fernseher: Lautstärke ist auf 12
2019-03-05 07:21:08.766  - info: javascript.0 script.js.Multimedia.Fernseher: fernseher play
2019-03-05 07:21:08.768  - info: javascript.0 script.js.Multimedia.Fernseher: NaN
2019-03-05 07:21:08.769  - info: javascript.0 script.js.Multimedia.Fernseher: NaN
2019-03-05 07:21:08.772  - info: javascript.0 script.js.Multimedia.Fernseher: Lautstärke ist auf 12
2019-03-05 14:48:09.718  - info: javascript.0 script.js.Multimedia.Fernseher: stehlampe einschalten
2019-03-05 14:48:09.721  - info: javascript.0 script.js.Multimedia.Fernseher: NaN
2019-03-05 14:48:09.722  - info: javascript.0 script.js.Multimedia.Fernseher: NaN
2019-03-05 14:48:09.722  - info: javascript.0 script.js.Multimedia.Fernseher: Lautstärke ist auf 12
2019-03-05 16:06:13.719  - info: javascript.0 script.js.Multimedia.Fernseher: stehlampe ausschalten
2019-03-05 16:06:13.721  - info: javascript.0 script.js.Multimedia.Fernseher: NaN
2019-03-05 16:06:13.722  - info: javascript.0 script.js.Multimedia.Fernseher: NaN
2019-03-05 16:06:13.723  - info: javascript.0 script.js.Multimedia.Fernseher: Lautstärke ist auf 13
2019-03-05 16:18:12.688  - info: javascript.0 script.js.Multimedia.Fernseher: stehlampe einschalten
2019-03-05 16:18:12.689  - info: javascript.0 script.js.Multimedia.Fernseher: NaN
2019-03-05 16:18:12.690  - info: javascript.0 script.js.Multimedia.Fernseher: NaN
2019-03-05 16:18:12.691  - info: javascript.0 script.js.Multimedia.Fernseher: Lautstärke ist auf 15
2019-03-05 16:42:40.997  - info: javascript.0 script.js.Multimedia.Fernseher: fernseher pause
2019-03-05 16:42:40.998  - info: javascript.0 script.js.Multimedia.Fernseher: NaN
2019-03-05 16:42:40.999  - info: javascript.0 script.js.Multimedia.Fernseher: NaN
2019-03-05 16:42:41.002  - info: javascript.0 script.js.Multimedia.Fernseher: Lautstärke ist auf 13
2019-03-05 16:52:41.985  - info: javascript.0 script.js.Multimedia.Fernseher: pro 7
2019-03-05 16:52:41.987  - info: javascript.0 script.js.Multimedia.Fernseher: 7
2019-03-05 16:52:41.989  - info: javascript.0 script.js.Multimedia.Fernseher: 7
2019-03-05 16:52:41.990  - info: javascript.0 script.js.Multimedia.Fernseher: Lautstärke ist auf 13
2019-03-05 17:20:52.475  - info: web.0 ==>Connected system.user.admin from ::ffff:192.168.0.28
2019-03-05 17:31:08.672  - info: web.0 <==Disconnect system.user.admin from ::ffff:192.168.0.28 material.0
2019-03-05 17:43:15.374  - info: web.0 ==>Connected system.user.admin from ::ffff:192.168.0.28
2019-03-05 17:43:16.918  - info: web.0 ==>Connected system.user.admin from ::ffff:192.168.0.28
2019-03-05 17:43:18.249  - info: web.0 ==>Connected system.user.admin from ::ffff:192.168.0.28
2019-03-05 17:44:00.524  - info: web.0 <==Disconnect system.user.admin from ::ffff:192.168.0.28 material.0
2019-03-05 17:44:00.529  - info: web.0 <==Disconnect system.user.admin from ::ffff:192.168.0.28 material.0
2019-03-05 17:44:40.438  - info: web.0 <==Disconnect system.user.admin from ::ffff:192.168.0.28 material.0
2019-03-05 17:59:32.825  - info: web.0 ==>Connected system.user.admin from ::ffff:192.168.0.30
2019-03-05 17:59:33.472  - info: web.0 ==>Connected system.user.admin from ::ffff:192.168.0.30
2019-03-05 18:05:43.277  - info: web.0 <==Disconnect system.user.admin from ::ffff:192.168.0.30 material.0
2019-03-05 18:05:44.271  - info: web.0 <==Disconnect system.user.admin from ::ffff:192.168.0.30 material.0
2019-03-05 18:06:33.391  - info: web.0 ==>Connected system.user.admin from ::ffff:192.168.0.30
2019-03-05 18:06:33.404  - info: web.0 ==>Connected system.user.admin from ::ffff:192.168.0.30
2019-03-05 18:06:33.511  - info: web.0 <==Disconnect system.user.admin from ::ffff:192.168.0.30 material.0
2019-03-05 18:06:34.465  - info: web.0 ==>Connected system.user.admin from ::ffff:192.168.0.30
2019-03-05 18:06:48.084  - info: web.0 <==Disconnect system.user.admin from ::ffff:192.168.0.30 material.0
2019-03-05 18:07:58.408  - info: web.0 <==Disconnect system.user.admin from ::ffff:192.168.0.30 
2019-03-05 18:29:30.647  - info: web.0 ==>Connected system.user.admin from ::ffff:192.168.0.28
2019-03-05 18:36:03.838  - info: web.0 <==Disconnect system.user.admin from ::ffff:192.168.0.28 material.0
2019-03-05 18:39:10.046  - info: javascript.0 script.js.Multimedia.Fernseher: stehlampe einschalten
2019-03-05 18:39:10.048  - info: javascript.0 script.js.Multimedia.Fernseher: NaN
2019-03-05 18:39:10.049  - info: javascript.0 script.js.Multimedia.Fernseher: NaN
2019-03-05 18:39:10.050  - info: javascript.0 script.js.Multimedia.Fernseher: Lautstärke ist auf 14
2019-03-05 18:44:41.967  - info: web.0 ==>Connected system.user.admin from ::ffff:192.168.0.30
2019-03-05 18:44:58.317  - info: web.0 <==Disconnect system.user.admin from ::ffff:192.168.0.30 material.0
2019-03-05 20:58:37.194  - info: javascript.0 Stop script script.js.Meldungen.Telegram
2019-03-05 20:58:37.234  - info: javascript.0 Start javascript script.js.Meldungen.Telegram
2019-03-05 20:58:37.261  - warn: javascript.0 Wrong type of telegram.0.communicate.response: "undefined". Please fix, while deprecated and will not work in next versions.
2019-03-05 20:58:37.282  - warn: javascript.0     at setState (/opt/iobroker/node_modules/iobroker.javascript/lib/sandbox.js:1258:20)
2019-03-05 20:58:37.283  - warn: javascript.0     at script.js.Meldungen.Telegram:4:1
2019-03-05 20:58:37.285  - info: javascript.0 script.js.Meldungen.Telegram: registered 4 subscriptions and 0 schedules
2019-03-05 21:01:27.341  - info: javascript.0 Stop script script.js.Meldungen.Telegram
2019-03-05 21:01:27.381  - info: javascript.0 Start javascript script.js.Meldungen.Telegram
2019-03-05 21:01:27.395  - info: javascript.0 script.js.Meldungen.Telegram: registered 4 subscriptions and 0 schedules
2019-03-05 21:02:07.290  - info: javascript.0 Stop script script.js.Meldungen.Telegram
2019-03-05 21:02:07.336  - info: javascript.0 Start javascript script.js.Meldungen.Telegram
2019-03-05 21:02:07.349  - info: javascript.0 script.js.Meldungen.Telegram: registered 4 subscriptions and 0 schedules
2019-03-05 21:02:44.667  - info: javascript.0 Stop script script.js.Meldungen.Telegram
2019-03-05 21:02:44.720  - info: javascript.0 Start javascript script.js.Meldungen.Telegram
2019-03-05 21:02:44.734  - info: javascript.0 script.js.Meldungen.Telegram: registered 4 subscriptions and 0 schedules
2019-03-05 21:02:50.364  - info: javascript.0 Stop script script.js.Meldungen.Telegram
2019-03-05 21:02:50.395  - info: javascript.0 Start javascript script.js.Meldungen.Telegram
2019-03-05 21:02:50.407  - info: javascript.0 script.js.Meldungen.Telegram: registered 4 subscriptions and 0 schedules
2019-03-05 21:04:19.214  - info: iobroker upgrade javascript
2019-03-05 21:04:23.270  - info: iobroker Update javascript from @4.1.8 to @4.1.9
2019-03-05 21:04:25.036  - info: iobroker NPM version: 6.8.0
2019-03-05 21:04:26.825  - info: iobroker npm install iobroker.javascript@4.1.9 --production --save --prefix "/opt/iobroker" (System call)
2019-03-05 21:05:06.618  - info: iobroker npm
2019-03-05 21:05:06.621  - info: iobroker  WARN deprecated coffee-script@1.12.7: CoffeeScript on NPM has moved to "coffeescript" (no hyphen)
2019-03-05 21:06:29.887  - info: iobroker npm install --production (System call) in "/opt/iobroker/node_modules/iobroker.javascript"
2019-03-05 21:06:38.163  - info: iobroker npm
2019-03-05 21:06:38.166  - info: iobroker  WARN deprecated coffee-script@1.12.7: CoffeeScript on NPM has moved to "coffeescript" (no hyphen)
2019-03-05 21:06:43.562  - info: web.0 ==>Connected system.user.admin from ::ffff:192.168.0.28
2019-03-05 21:06:44.843  - info: iobroker npm
2019-03-05 21:06:44.845  - info: iobroker  
2019-03-05 21:06:44.848  - info: iobroker WARN 
2019-03-05 21:06:44.852  - info: iobroker deprecated gulp-util@3.0.8: gulp-util is deprecated - replace it, following the guidelines at https://medium.com/gulpjs/gulp-util-ca3b1f9f9ac5
2019-03-05 21:06:57.390  - info: iobroker npm
2019-03-05 21:06:57.392  - info: iobroker  WARN deprecated graceful-fs@3.0.11: please upgrade to graceful-fs 4 for compatibility with current and future versions of Node.js
2019-03-05 21:07:02.650  - info: iobroker npm WARN deprecated circular-json@0.3.3: CircularJSON is in maintenance only, flatted is its successor.
2019-03-05 21:07:03.845  - info: iobroker npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
2019-03-05 21:07:11.869  - info: iobroker npm WARN deprecated
2019-03-05 21:07:11.871  - info: iobroker  minimatch@0.2.14: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
2019-03-05 21:07:14.049  - info: iobroker npm
2019-03-05 21:07:14.052  - info: iobroker  WARN deprecated graceful-fs@1.2.3: please upgrade to graceful-fs 4 for compatibility with current and future versions of Node.js
2019-03-05 21:08:11.282  - info: iobroker Update "system.adapter.javascript.0"
2019-03-05 21:08:11.327  - info: host.raspberrypi object change system.adapter.javascript.0
2019-03-05 21:08:11.342  - info: javascript.0 Stop script script.js.Bridge.RF_Bridge
2019-03-05 21:08:11.333  - info: host.raspberrypi stopInstance system.adapter.javascript.0
2019-03-05 21:08:11.334  - info: host.raspberrypi stopInstance system.adapter.javascript.0 killing pid 565
2019-03-05 21:08:11.357  - info: iobroker got /opt/iobroker/node_modules/iobroker.javascript/admin
2019-03-05 21:08:11.345  - info: javascript.0 Stop script script.js.Multimedia.Fernseher
2019-03-05 21:08:11.347  - info: javascript.0 Stop script script.js.Beleuchtung.Flur
2019-03-05 21:08:11.349  - info: javascript.0 Stop script script.js.Beleuchtung.Schlafzimmer
2019-03-05 21:08:11.350  - info: javascript.0 Stop script script.js.Beleuchtung.Wohnzimmer
2019-03-05 21:08:11.352  - info: javascript.0 Stop script script.js.Szenen.Zentral_Steuerung
2019-03-05 21:08:11.353  - info: javascript.0 Stop script script.js.Vis.Fernseher
2019-03-05 21:08:11.355  - info: javascript.0 Stop script script.js.Meldungen.Telegram
2019-03-05 21:08:11.438  - info: host.raspberrypi instance system.adapter.javascript.0 terminated with code 0 (OK)
2019-03-05 21:08:13.879  - info: host.raspberrypi instance system.adapter.javascript.0 started with pid 4529
2019-03-05 21:08:18.437  - info: iobroker upload [100] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/vs/basic-languages/razor/razor.js vs/basic-languages/razor/razor.js application/javascript
2019-03-05 21:08:19.145  - info: iobroker upload [90] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/vs/basic-languages/msdax/msdax.js vs/basic-languages/msdax/msdax.js application/javascript
2019-03-05 21:08:19.885  - info: iobroker upload [80] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/vs/basic-languages/dockerfile/dockerfile.js vs/basic-languages/dockerfile/dockerfile.js application/javascript
2019-03-05 21:08:20.690  - info: iobroker upload [70] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/static/media/copy-content.770c7d5d.svg static/media/copy-content.770c7d5d.svg image/svg+xml
2019-03-05 21:08:22.038  - info: javascript.0 starting. Version 4.1.9 in /opt/iobroker/node_modules/iobroker.javascript, node: v8.15.1
2019-03-05 21:08:22.194  - info: javascript.0 requesting all states
2019-03-05 21:08:22.201  - info: javascript.0 requesting all objects
2019-03-05 21:08:23.194  - info: javascript.0 received all states
2019-03-05 21:08:23.863  - info: javascript.0 received all objects
2019-03-05 21:08:24.190  - info: javascript.0 Start javascript script.js.Meldungen.Telegram
2019-03-05 21:08:24.282  - info: javascript.0 script.js.Meldungen.Telegram: registered 4 subscriptions and 0 schedules
2019-03-05 21:08:24.293  - info: javascript.0 Start javascript script.js.Bridge.RF_Bridge
2019-03-05 21:08:24.308  - info: javascript.0 script.js.Bridge.RF_Bridge: registered 2 subscriptions and 0 schedules
2019-03-05 21:08:24.311  - info: javascript.0 Start javascript script.js.Multimedia.Fernseher
2019-03-05 21:08:24.343  - info: javascript.0 script.js.Multimedia.Fernseher: registered 7 subscriptions and 0 schedules
2019-03-05 21:08:24.346  - info: javascript.0 Start javascript script.js.Beleuchtung.Flur
2019-03-05 21:08:24.358  - info: javascript.0 script.js.Beleuchtung.Flur: registered 1 subscription and 0 schedules
2019-03-05 21:08:24.362  - info: javascript.0 Start javascript script.js.Beleuchtung.Schlafzimmer
2019-03-05 21:08:24.377  - info: javascript.0 script.js.Beleuchtung.Schlafzimmer: registered 7 subscriptions and 0 schedules
2019-03-05 21:08:24.389  - info: javascript.0 Start javascript script.js.Beleuchtung.Wohnzimmer
2019-03-05 21:08:24.400  - info: javascript.0 script.js.Beleuchtung.Wohnzimmer: registered 1 subscription and 0 schedules
2019-03-05 21:08:24.404  - info: javascript.0 Start javascript script.js.Szenen.Zentral_Steuerung
2019-03-05 21:08:24.454  - info: javascript.0 script.js.Szenen.Zentral_Steuerung: registered 3 subscriptions and 0 schedules
2019-03-05 21:08:24.463  - info: javascript.0 Start javascript script.js.Vis.Fernseher
2019-03-05 21:08:24.485  - info: javascript.0 script.js.Vis.Fernseher: registered 5 subscriptions and 0 schedules
2019-03-05 21:08:25.404  - info: iobroker upload [60] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/precache-manifest.d1f73cb716e92676c08a58445cbc4e3c.js precache-manifest.d1f73cb716e92676c08a58445cbc4e3c.js application/javascript
2019-03-05 21:08:26.141  - info: iobroker upload [50] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/google-blockly/own/msg/fr.js google-blockly/own/msg/fr.js application/javascript
2019-03-05 21:08:26.963  - info: iobroker upload [40] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/google-blockly/own/blocks_time.js google-blockly/own/blocks_time.js application/javascript
2019-03-05 21:08:27.790  - info: iobroker upload [30] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/google-blockly/msg/js/pl.js google-blockly/msg/js/pl.js application/javascript
2019-03-05 21:08:28.535  - info: iobroker upload [20] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/google-blockly/media/quote0.png google-blockly/media/quote0.png image/png
2019-03-05 21:08:28.603  - info: iobroker upload [19] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/google-blockly/media/handopen.cur google-blockly/media/handopen.cur application/octet-stream
2019-03-05 21:08:28.672  - info: iobroker upload [18] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/google-blockly/media/handdelete.cur google-blockly/media/handdelete.cur application/octet-stream
2019-03-05 21:08:28.741  - info: iobroker upload [17] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/google-blockly/media/handclosed.cur google-blockly/media/handclosed.cur application/octet-stream
2019-03-05 21:08:28.809  - info: iobroker upload [16] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/google-blockly/media/disconnect.wav google-blockly/media/disconnect.wav audio/x-wav
2019-03-05 21:08:28.881  - info: iobroker upload [15] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/google-blockly/media/disconnect.ogg google-blockly/media/disconnect.ogg audio/ogg
2019-03-05 21:08:28.959  - info: iobroker upload [14] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/google-blockly/media/disconnect.mp3 google-blockly/media/disconnect.mp3 audio/mpeg
2019-03-05 21:08:29.036  - info: iobroker upload [13] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/google-blockly/media/delete.wav google-blockly/media/delete.wav audio/x-wav
2019-03-05 21:08:29.116  - info: iobroker upload [12] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/google-blockly/media/delete.ogg google-blockly/media/delete.ogg audio/ogg
2019-03-05 21:08:29.185  - info: iobroker upload [11] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/google-blockly/media/delete.mp3 google-blockly/media/delete.mp3 audio/mpeg
2019-03-05 21:08:29.252  - info: iobroker upload [10] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/google-blockly/media/click.wav google-blockly/media/click.wav audio/x-wav
2019-03-05 21:08:29.324  - info: iobroker upload [9] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/google-blockly/media/click.ogg google-blockly/media/click.ogg audio/ogg
2019-03-05 21:08:29.391  - info: iobroker upload [8] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/google-blockly/media/click.mp3 google-blockly/media/click.mp3 audio/mpeg
2019-03-05 21:08:29.458  - info: iobroker upload [7] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/google-blockly/media/1x1.gif google-blockly/media/1x1.gif image/gif
2019-03-05 21:08:29.522  - info: iobroker upload [6] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/google-blockly/javascript_compressed.js google-blockly/javascript_compressed.js application/javascript
2019-03-05 21:08:29.601  - info: iobroker upload [5] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/google-blockly/blocks_compressed.js google-blockly/blocks_compressed.js application/javascript
2019-03-05 21:08:29.690  - info: iobroker upload [4] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/google-blockly/blockly_compressed.js google-blockly/blockly_compressed.js application/javascript
2019-03-05 21:08:30.065  - info: iobroker upload [3] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/google-blockly/LICENSE google-blockly/LICENSE application/octet-stream
2019-03-05 21:08:30.134  - info: iobroker upload [2] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/favicon.ico favicon.ico image/x-icon
2019-03-05 21:08:30.227  - info: iobroker upload [1] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/asset-manifest.json asset-manifest.json application/json
2019-03-05 21:08:30.292  - info: iobroker upload [0] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/adminWords.js adminWords.js application/javascript
2019-03-05 21:08:30.363  - info: iobroker Adapter "javascript" updated
2019-03-05 21:08:30.639  - info: iobroker exit 0
2019-03-05 21:09:50.491  - info: javascript.0 Stop script script.js.Meldungen.Telegram
2019-03-05 21:09:50.541  - info: javascript.0 Start javascript script.js.Meldungen.Telegram
2019-03-05 21:09:50.569  - info: javascript.0 script.js.Meldungen.Telegram: registered 4 subscriptions and 0 schedules
2019-03-05 21:09:57.334  - info: javascript.0 Stop script script.js.Meldungen.Telegram
2019-03-05 21:09:57.396  - info: javascript.0 Start javascript script.js.Meldungen.Telegram
2019-03-05 21:09:57.416  - info: javascript.0 script.js.Meldungen.Telegram: registered 4 subscriptions and 0 schedules
2019-03-05 21:15:43.588  - info: web.0 <==Disconnect system.user.admin from ::ffff:192.168.0.28 material.0
2019-03-05 21:33:15.446  - info: javascript.0 script.js.Multimedia.Fernseher: zentral wohn ausschalten
2019-03-05 21:33:15.448  - info: javascript.0 script.js.Multimedia.Fernseher: NaN
2019-03-05 21:33:15.449  - info: javascript.0 script.js.Multimedia.Fernseher: NaN
2019-03-05 21:33:15.451  - info: javascript.0 script.js.Multimedia.Fernseher: Lautstärke ist auf 10
2019-03-05 21:38:10.386  - info: javascript.0 script.js.Multimedia.Fernseher: schlafzimmerlicht ausschalten
2019-03-05 21:38:10.387  - info: javascript.0 script.js.Multimedia.Fernseher: NaN
2019-03-05 21:38:10.388  - info: javascript.0 script.js.Multimedia.Fernseher: NaN
2019-03-05 21:38:10.389  - info: javascript.0 script.js.Multimedia.Fernseher: Lautstärke ist auf 0
2019-03-05 21:42:09.353  - info: host.raspberrypi received SIGTERM
2019-03-05 21:42:09.371  - info: sayit.0 stopping...
2019-03-05 21:42:09.357  - info: admin.0 terminating http server on port 8081
2019-03-05 21:42:09.368  - info: web.0 terminating http server on port 8082
2019-03-05 21:42:09.381  - info: web.0 terminated http server on port 8082
2019-03-05 21:42:09.400  - info: javascript.0 Stop script script.js.Bridge.RF_Bridge
2019-03-05 21:42:09.408  - info: sayit.0 stopping...
2019-03-05 21:42:09.403  - info: javascript.0 Stop script script.js.Multimedia.Fernseher
2019-03-05 21:42:09.405  - info: javascript.0 Stop script script.js.Beleuchtung.Flur
2019-03-05 21:42:09.407  - info: javascript.0 Stop script script.js.Beleuchtung.Schlafzimmer
2019-03-05 21:42:09.419  - info: javascript.0 Stop script script.js.Beleuchtung.Wohnzimmer
2019-03-05 21:42:09.421  - info: javascript.0 Stop script script.js.Szenen.Zentral_Steuerung
2019-03-05 21:42:09.422  - info: javascript.0 Stop script script.js.Vis.Fernseher
2019-03-05 21:42:09.423  - info: javascript.0 Stop script script.js.Meldungen.Telegram
2019-03-05 21:42:09.439  - info: zigbee.0 zigbee-shepherd stopped
2019-03-05 21:42:09.470  - info: web.0 terminating http server on port 8082
2019-03-05 21:42:09.473  - info: admin.0 terminating http server on port 8081
2019-03-05 21:42:09.496  - info: iot.0 Connection changed: disconnect
2019-03-05 21:42:09.519  - info: host.raspberrypi instance system.adapter.web.0 terminated with code 0 (OK)
2019-03-05 21:42:09.529  - info: host.raspberrypi instance system.adapter.lgtv.1 terminated with code 0 (OK)
2019-03-05 21:42:09.537  - info: host.raspberrypi instance system.adapter.broadlink2.0 terminated with code 0 (OK)
2019-03-05 21:42:09.545  - info: host.raspberrypi instance system.adapter.sayit.0 terminated with code 0 (OK)
2019-03-05 21:42:09.551  - info: host.raspberrypi instance system.adapter.tr-064.0 terminated with code 0 (OK)
2019-03-05 21:42:09.564  - info: host.raspberrypi instance system.adapter.admin.0 terminated with code 0 (OK)
2019-03-05 21:42:09.570  - info: host.raspberrypi instance system.adapter.discovery.0 terminated with code 0 (OK)
2019-03-05 21:42:09.575  - info: host.raspberrypi instance system.adapter.shelly.0 terminated with code 0 (OK)
2019-03-05 21:42:09.578  - info: host.raspberrypi instance system.adapter.iot.0 terminated with code 0 (OK)
2019-03-05 21:42:09.582  - info: host.raspberrypi instance system.adapter.zigbee.0 terminated with code 0 (OK)
2019-03-05 21:42:09.586  - info: host.raspberrypi instance system.adapter.javascript.0 terminated with code 0 (OK)
2019-03-05 21:42:09.920  - info: host.raspberrypi instance system.adapter.sonoff.0 terminated with code 0 (OK)
2019-03-05 21:42:09.941  - info: host.raspberrypi instance system.adapter.telegram.0 terminated with code 0 (OK)
2019-03-05 21:42:09.942  - info: host.raspberrypi All instances are stopped.
2019-03-05 21:42:09.992  - info: host.raspberrypi terminated
2019-03-05 21:42:39.321  - info: host.raspberrypi iobroker.js-controller version 1.5.7 js-controller starting
2019-03-05 21:42:39.334  - info: host.raspberrypi Copyright (c) 2014-2018 bluefox, 2014 hobbyquaker
2019-03-05 21:42:39.334  - info: host.raspberrypi hostname: raspberrypi, node: v8.15.1
2019-03-05 21:42:39.343  - info: host.raspberrypi ip addresses: 192.168.0.195 2a02:8071:3eb2:d900:76de:54f9:2364:a90d fe80::a094:393e:29f3:7201
2019-03-05 21:42:39.432  - info: host.raspberrypi  inMem-states listening on port 9000
2019-03-05 21:42:40.081  - info: host.raspberrypi  inMem-objects listening on port 9001
2019-03-05 21:42:40.125  - info: host.raspberrypi InMemoryDB connected
2019-03-05 21:42:40.168  - info: host.raspberrypi 27 instances found
2019-03-05 21:42:40.225  - info: host.raspberrypi starting 19 instances
2019-03-05 21:42:40.394  - info: host.raspberrypi instance system.adapter.admin.0 started with pid 4763
2019-03-05 21:42:44.252  - info: host.raspberrypi instance system.adapter.discovery.0 started with pid 4769
2019-03-05 21:42:45.142  - info: admin.0 starting. Version 3.6.0 in /opt/iobroker/node_modules/iobroker.admin, node: v8.15.1
2019-03-05 21:42:45.960  - info: admin.0 requesting all states
2019-03-05 21:42:45.967  - info: admin.0 requesting all objects
2019-03-05 21:42:45.971  - info: admin.0 Request actual repository...
2019-03-05 21:42:46.694  - info: admin.0 received all states
2019-03-05 21:42:46.850  - info: discovery.0 starting. Version 1.2.4 in /opt/iobroker/node_modules/iobroker.discovery, node: v8.15.1
2019-03-05 21:42:47.417  - info: admin.0 received all objects
2019-03-05 21:42:47.436  - warn: admin.0 No repository source configured
2019-03-05 21:42:47.503  - info: admin.0 http server listening on port 8081
2019-03-05 21:42:47.503  - info: admin.0 Use link "http://localhost:8081" to configure.
2019-03-05 21:42:47.944  - info: host.raspberrypi Update repository "latest" under "http://download.iobroker.net/sources-dist-latest.json"
2019-03-05 21:42:48.837  - info: host.raspberrypi instance system.adapter.javascript.0 started with pid 4792
2019-03-05 21:42:52.257  - info: host.raspberrypi instance system.adapter.web.0 started with pid 4798
2019-03-05 21:42:52.685  - info: admin.0 Repository received successfully.
2019-03-05 21:42:55.701  - info: web.0 starting. Version 2.4.1 in /opt/iobroker/node_modules/iobroker.web, node: v8.15.1
2019-03-05 21:42:55.776  - info: javascript.0 starting. Version 4.1.9 in /opt/iobroker/node_modules/iobroker.javascript, node: v8.15.1
2019-03-05 21:42:55.894  - info: javascript.0 requesting all states
2019-03-05 21:42:55.900  - info: javascript.0 requesting all objects
2019-03-05 21:42:56.326  - info: host.raspberrypi instance system.adapter.lgtv.1 started with pid 4820
2019-03-05 21:42:56.469  - info: javascript.0 received all states
2019-03-05 21:42:56.737  - info: web.0 socket.io server listening on port 8082
2019-03-05 21:42:56.749  - info: web.0 http server listening on port 8082
2019-03-05 21:42:57.188  - info: javascript.0 received all objects
2019-03-05 21:42:57.520  - info: javascript.0 Start javascript script.js.Bridge.RF_Bridge
2019-03-05 21:42:57.605  - info: javascript.0 script.js.Bridge.RF_Bridge: registered 2 subscriptions and 0 schedules
2019-03-05 21:42:57.610  - info: javascript.0 Start javascript script.js.Multimedia.Fernseher
2019-03-05 21:42:57.628  - info: javascript.0 script.js.Multimedia.Fernseher: registered 7 subscriptions and 0 schedules
2019-03-05 21:42:57.632  - info: javascript.0 Start javascript script.js.Beleuchtung.Flur
2019-03-05 21:42:57.643  - info: javascript.0 script.js.Beleuchtung.Flur: registered 1 subscription and 0 schedules
2019-03-05 21:42:57.653  - info: javascript.0 Start javascript script.js.Beleuchtung.Schlafzimmer
2019-03-05 21:42:57.669  - info: javascript.0 script.js.Beleuchtung.Schlafzimmer: registered 7 subscriptions and 0 schedules
2019-03-05 21:42:57.672  - info: javascript.0 Start javascript script.js.Beleuchtung.Wohnzimmer
2019-03-05 21:42:57.684  - info: javascript.0 script.js.Beleuchtung.Wohnzimmer: registered 1 subscription and 0 schedules
2019-03-05 21:42:57.688  - info: javascript.0 Start javascript script.js.Szenen.Zentral_Steuerung
2019-03-05 21:42:57.700  - info: javascript.0 script.js.Szenen.Zentral_Steuerung: registered 3 subscriptions and 0 schedules
2019-03-05 21:42:57.705  - info: javascript.0 Start javascript script.js.Vis.Fernseher
2019-03-05 21:42:57.718  - info: javascript.0 script.js.Vis.Fernseher: registered 5 subscriptions and 0 schedules
2019-03-05 21:42:57.722  - info: javascript.0 Start javascript script.js.Meldungen.Telegram
2019-03-05 21:42:57.735  - info: javascript.0 script.js.Meldungen.Telegram: registered 4 subscriptions and 0 schedules
2019-03-05 21:42:58.752  - info: lgtv.1 starting. Version 1.0.7 in /opt/iobroker/node_modules/iobroker.lgtv, node: v8.15.1
2019-03-05 21:42:58.816  - info: lgtv.1 Ready. Configured WebOS TV IP: 192.168.0.31
2019-03-05 21:43:00.274  - info: host.raspberrypi instance system.adapter.sonoff.0 started with pid 4834
2019-03-05 21:43:02.642  - info: sonoff.0 starting. Version 2.2.2 in /opt/iobroker/node_modules/iobroker.sonoff, node: v8.15.1
2019-03-05 21:43:02.782  - info: sonoff.0 Starting MQTT authenticated  server on port 1883
2019-03-05 21:43:04.276  - info: host.raspberrypi instance system.adapter.broadlink2.0 started with pid 4848
2019-03-05 21:43:05.120  - info: sonoff.0 Client [Sonoff_Bridge] connected with secret 1551818585084_2425
2019-03-05 21:43:05.678  - info: sonoff.0 Client [Stehlampe] connected with secret 1551818585445_5743
2019-03-05 21:43:05.684  - info: sonoff.0 Client [Nachtlicht Benchy] connected with secret 1551818585450_9540
2019-03-05 21:43:05.688  - info: sonoff.0 Client [Nachtlicht Marcus] connected with secret 1551818585452_7735
2019-03-05 21:43:05.692  - info: sonoff.0 Client [Nachtlicht Liah] connected with secret 1551818585454_4600
2019-03-05 21:43:06.398  - info: broadlink2.0 starting. Version 1.9.1 in /opt/iobroker/node_modules/iobroker.broadlink2, node: v8.15.1
2019-03-05 21:43:07.518  - info: broadlink2.0 Discover UDP devices for 10sec on broadlink2.0
2019-03-05 21:43:07.866  - info: broadlink2.0 Device RM:BroadlinkMini dedected: 192.168.0.32,IPv4,80,128,10039,rm,RM:BroadlinkMini,RM Mini,37:27:20:0:a8:c0
2019-03-05 21:43:13.083  - info: broadlink2.0 Adapter broadlink2.0 started and found 1 devices named 'RM:BroadlinkMini'.
2019-03-05 21:43:22.426  - info: vis.0 starting. Version 1.1.10 in /opt/iobroker/node_modules/iobroker.vis, node: v8.15.1
2019-03-05 21:43:22.767  - info: vis.0 vis license is OK.
2019-03-05 21:43:24.292  - info: host.raspberrypi instance system.adapter.sayit.0 started with pid 4889
2019-03-05 21:43:24.339  - info: host.raspberrypi instance system.adapter.vis.0 terminated while should be started once
2019-03-05 21:43:26.338  - info: sayit.0 starting. Version 1.7.0 in /opt/iobroker/node_modules/iobroker.sayit, node: v8.15.1
2019-03-05 21:43:26.404  - info: sayit.0 Upload announce mp3 files
2019-03-05 21:43:26.574  - info: sayit.0 All files uploaded
2019-03-05 21:43:36.269  - info: host.raspberrypi instance system.adapter.shelly.0 started with pid 4904
2019-03-05 21:43:38.762  - info: shelly.0 starting. Version 2.1.4 in /opt/iobroker/node_modules/iobroker.shelly, node: v8.15.1
2019-03-05 21:43:38.843  - info: shelly.0 Starting shelly.0 in version 2.1.4
2019-03-05 21:43:39.690  - info: shelly.0 Listening for Shelly packets in the network
2019-03-05 21:43:40.248  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 4918
2019-03-05 21:43:44.248  - info: host.raspberrypi instance system.adapter.tr-064.0 started with pid 4924
2019-03-05 21:43:44.740  - info: telegram.0 starting. Version 1.4.3 in /opt/iobroker/node_modules/iobroker.telegram, node: v8.15.1
2019-03-05 21:43:48.088  - info: tr-064.0 starting. Version 0.4.18 in /opt/iobroker/node_modules/iobroker.tr-064, node: v8.15.1
2019-03-05 21:43:48.250  - info: host.raspberrypi instance system.adapter.iot.0 started with pid 4946
2019-03-05 21:43:52.252  - info: host.raspberrypi instance system.adapter.zigbee.0 started with pid 4952
2019-03-05 21:43:53.089  - info: iot.0 starting. Version 0.3.1 in /opt/iobroker/node_modules/iobroker.iot, node: v8.15.1
2019-03-05 21:43:53.217  - info: iot.0 Connecting with a18wym7vjdl22g.iot.eu-west-1.amazonaws.com
2019-03-05 21:43:55.228  - error: iot.0 Cannot report device state: null
2019-03-05 21:43:55.231  - warn: iot.0 Invalid URL key. Status update is disabled: {"error":"Unsupported version"}
2019-03-05 21:43:55.265  - info: iot.0 Connection changed: connect
2019-03-05 21:43:56.668  - info: zigbee.0 starting. Version 0.9.2 in /opt/iobroker/node_modules/iobroker.zigbee, node: v8.15.1
2019-03-05 21:43:56.740  - info: zigbee.0 Start on port: /dev/serial/by-id/usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B0018E1AA6E-if00 with panID 6754 channel 11
2019-03-05 21:43:56.741  - info: zigbee.0 Queue is: true
2019-03-05 21:43:56.849  - info: zigbee.0 Reset coordinator
2019-03-05 21:43:57.675  - info: zigbee.0 zigbee-shepherd started!
2019-03-05 21:43:57.695  - info: zigbee.0 zigbee-shepherd ready. version: 2.6.3 rev 20180815