Test js-controller v2.0.x (GitHub)

opossum

Hallo,

@apollon77 sagte in [Aufruf] js-controller 2.0 Beta Test:

Ps: die Idee war das wir einen „User-files“ Ordner anlegen und auch dahin uploads erlauben. Aber auch dann wäre das wohl ein anderer Name als dein aktueller ;-)

… wo muss ich meine eigenen Icons jetzt hinkopieren? In meinen Views werden alle eigenen Icons nicht mehr angezeigt, ich kann sie auch nicht mehr in dem ursprünglichen Pfad auswählen (auch dort werden sie nicht mehr angezeigt im Auswahldialog). Ich würde dann halt meine Views umbauen müssen. Aber ich möchte das nur einmal machen, daher wäre es gut, wenn ich den Pfad wüsste. Ich habe unter vis.0 einmal main/img/ und einmal /Project_1/ mehrere Ordner mit eigenen Icons. Vielen Dank.

Gruß
Egbert

e-s

@apollon77
Oh Mann, ist das peinlich. Hatte tatsächlich das cd vergessen. Passiert wenn man sich nur schnell über Putty einloggt und über die hochtaste die letzten Befehle wiederholen will und nicht weit genug nach oben geht. Hatte aber trotzdem wieder Fehlermeldungen:

santa@ubuntuserver:/opt/iobroker$ npm install ioBroker/ioBroker.js-controller
npm ERR! code EPERM
npm ERR! syscall spawn
npm ERR! errno EPERM
npm ERR! Error: spawn EPERM
npm ERR!     at ChildProcess.spawn (internal/child_process.js:366:11)
npm ERR!     at spawn (child_process.js:551:9)
npm ERR!     at execFile (child_process.js:221:15)
npm ERR!     at tryCatcher (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/util.js:16:23)
npm ERR!     at ret (eval at makeNodePromisifiedEval (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/promisify.js:184:12), <anonymous>:16:23)
npm ERR!     at promiseRetry (/usr/local/lib/node_modules/npm/node_modules/pacote/lib/util/git.js:192:14)
npm ERR!     at /usr/local/lib/node_modules/npm/node_modules/promise-retry/index.js:29:24
npm ERR!  { Error: spawn EPERM
npm ERR!     at ChildProcess.spawn (internal/child_process.js:366:11)
npm ERR!     at spawn (child_process.js:551:9)
npm ERR!     at execFile (child_process.js:221:15)
npm ERR!     at tryCatcher (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/util.js:16:23)
npm ERR!     at ret (eval at makeNodePromisifiedEval (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/promisify.js:184:12), <anonymous>:16:23)
npm ERR!     at promiseRetry (/usr/local/lib/node_modules/npm/node_modules/pacote/lib/util/git.js:192:14)
npm ERR!     at /usr/local/lib/node_modules/npm/node_modules/promise-retry/index.js:29:24
npm ERR!   cause:
npm ERR!    { Error: spawn EPERM
npm ERR!        at ChildProcess.spawn (internal/child_process.js:366:11)
npm ERR!        at spawn (child_process.js:551:9)
npm ERR!        at execFile (child_process.js:221:15)
npm ERR!        at tryCatcher (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/util.js:16:23)
npm ERR!        at ret (eval at makeNodePromisifiedEval (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/promisify.js:184:12), <anonymous>:16:23)
npm ERR!        at promiseRetry (/usr/local/lib/node_modules/npm/node_modules/pacote/lib/util/git.js:192:14)
npm ERR!        at /usr/local/lib/node_modules/npm/node_modules/promise-retry/index.js:29:24 errno: 'EPERM', code: 'EPERM', syscall: 'spawn' },
npm ERR!   stack:
npm ERR!    'Error: spawn EPERM\n    at ChildProcess.spawn (internal/child_process.js:366:11)\n    at spawn (child_process.js:551:9)\n    at execFile (child_process.js:221:15)\n    at tryCatcher (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/util.js:16:23)\n    at ret (eval at makeNodePromisifiedEval (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/promisify.js:184:12), <anonymous>:16:23)\n    at promiseRetry (/usr/local/lib/node_modules/npm/node_modules/pacote/lib/util/git.js:192:14)\n    at /usr/local/lib/node_modules/npm/node_modules/promise-retry/index.js:29:24',
npm ERR!   errno: 'EPERM',
npm ERR!   code: 'EPERM',
npm ERR!   syscall: 'spawn',
npm ERR!   parent: 'iobroker' }
npm ERR!
npm ERR! The operation was rejected by your operating system.
npm ERR! It is likely you do not have the permissions to access this file as the current user
npm ERR!
npm ERR! If you believe this might be a permissions issue, please double-check the
npm ERR! permissions of the file and its containing directories, or try running
npm ERR! the command again as root/Administrator.

npm ERR! A complete log of this run can be found in:
npm ERR!     /media/HDD/.npm/_logs/2019-09-22T06_17_39_413Z-debug.log

Anschließend die sudo Variante, Update lief jetzt mit warns durch und wird auch mit 2.0.6 in iobroker angezeigt:

santa@ubuntuserver:/opt/iobroker$ sudo -H -u iobroker npm install ioBroker/ioBroker.js-controller
[sudo] Passwort fÃ¼r santa:

> iobroker.js-controller@2.0.6 preinstall /opt/iobroker/node_modules/iobroker.js-controller
> node lib/preinstallCheck.js

NPM version: 6.11.3

> iobroker.js-controller@2.0.6 install /opt/iobroker/node_modules/iobroker.js-controller
> node iobroker.js setup first

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.0.7 (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.0.7: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@1.0.4 (node_modules/osx-temperature-sensor):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

+ iobroker.js-controller@2.0.6
added 4 packages from 3 contributors, removed 1 package, updated 4 packages and audited 27832 packages in 75.021s
found 34 vulnerabilities (23 low, 11 high)
  run `npm audit fix` to fix them, or `npm audit` for details

Jan1

@apollon77
Hab nun ein großes Problem mit der Version 2.0.6, IOBroker stürzt ab bevor alle Instanzen wieder laufen.
Bin jetzt gerade am Testen welche Instanz den Absturz verursacht und ob es am compakt mode liegt, der eigentlich genau das vermeiden soll.

Dr. Bakterius

@opossum sagte in [Aufruf] js-controller 2.0 Beta Test:

… wo muss ich meine eigenen Icons jetzt hinkopieren?

Am Besten im VIS-Editor unter 'Setup' - 'Dateimanager' in den Ordner '/vis.0/' hochladen indem du auf den Upload-Button klickst.

Unter vis.0 kann man auch eigene Unterordner erstellen.

Wenn man das direkt auf dem ioBroker-Rechner machen möchte, gehören die Dateien nach /opt/iobroker/iobroker-data/files/vis.0

Jan1

@apollon77
Der compact mode läuft mit Version 2.0.6 nicht mehr. Der admin restartet ständig.
hier mal ein Log:

admin.0	2019-09-22 08:50:22.584	info	(COMPACT) received all states
admin.0	2019-09-22 08:50:22.024	info	(COMPACT) Request actual repository...
admin.0	2019-09-22 08:50:22.024	info	(COMPACT) requesting all objects
admin.0	2019-09-22 08:50:22.022	info	(COMPACT) requesting all states
admin.0	2019-09-22 08:50:22.015	info	(COMPACT) starting. Version 3.6.5 in /opt/iobroker/node_modules/iobroker.admin, node: v10.16.3
admin.0	2019-09-22 08:49:51.387	info	(COMPACT) terminating
admin.0	2019-09-22 08:49:50.884	info	(COMPACT) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
admin.0	2019-09-22 08:49:50.881	info	(COMPACT) terminating
admin.0	2019-09-22 08:49:50.880	info	(COMPACT) terminating http server on port 8081
admin.0	2019-09-22 08:49:50.877	info	(COMPACT) Got terminate signal.
tankerkoenig.0	2019-09-22 08:49:44.927	info	(COMPACT) Reading data from tankerkoenig ...
tankerkoenig.0	2019-09-22 08:49:44.907	info	(COMPACT) Sync time set to 9 minutes or 540000 ms
tankerkoenig.0	2019-09-22 08:49:44.905	info	(COMPACT) starting. Version 2.0.6 in /opt/iobroker/node_modules/iobroker.tankerkoenig, node: v10.16.3
telegram.0	2019-09-22 08:49:43.651	info	(COMPACT) starting. Version 1.4.3 in /opt/iobroker/node_modules/iobroker.telegram, node: v10.16.3
host.Beelink.compactgroup1	2019-09-22 08:49:43.068	info	instance system.adapter.telegram.0 started in COMPACT mode
harmony.0	2019-09-22 08:49:38.881	info	(COMPACT) [PROCESS] Synced hub config for Harmony Hub (192.168.100.44)
host.Beelink.compactgroup1	2019-09-22 08:49:38.871	info	instance system.adapter.tankerkoenig.0 started in COMPACT mode
harmony.0	2019-09-22 08:49:37.791	info	(COMPACT) [CONNECT] Connected to Harmony Hub (192.168.100.44)
harmony.0	2019-09-22 08:49:36.633	info	(COMPACT) [CONNECT] Connecting to Harmony Hub (192.168.100.44)
harmony.0	2019-09-22 08:49:36.556	info	(COMPACT) [DISCOVER] Discovered Harmony Hub (192.168.100.44) and will try to connect
harmony.0	2019-09-22 08:49:35.362	info	(COMPACT) [DISCOVER] Searching for Harmony Hubs on 255.255.255.255
harmony.0	2019-09-22 08:49:35.354	info	(COMPACT) starting. Version 1.2.2 in /opt/iobroker/node_modules/iobroker.harmony, node: v10.16.3
host.Beelink.compactgroup1	2019-09-22 08:49:34.995	info	instance system.adapter.harmony.0 started in COMPACT mode
history.0	2019-09-22 08:49:31.181	info	(COMPACT) enabled logging of admin.0.Datenpunkte.Heizung.HZ_Regelung_laeuft (Count=1), Alias=false
history.0	2019-09-22 08:49:31.155	info	(COMPACT) starting. Version 1.8.7 in /opt/iobroker/node_modules/iobroker.history, node: v10.16.3
host.Beelink.compactgroup1	2019-09-22 08:49:30.736	info	instance system.adapter.history.0 started in COMPACT mode
backitup.0	2019-09-22 08:49:28.851	info	(COMPACT) [total] backup was activated at 03:00 every 7 day(s)
backitup.0	2019-09-22 08:49:28.838	info	(COMPACT) [minimal] backup was activated at 02:00 every 2 day(s)
backitup.0	2019-09-22 08:49:28.818	info	(COMPACT) starting. Version 1.2.0 in /opt/iobroker/node_modules/iobroker.backitup, node: v10.16.3
host.Beelink.compactgroup1	2019-09-22 08:49:27.952	info	instance system.adapter.backitup.0 started in COMPACT mode
admin.0	2019-09-22 08:49:25.560	info	(COMPACT) Repository received successfully.
admin.0	2019-09-22 08:49:25.004	info	(COMPACT) Use link "http://localhost:8081" to configure.
admin.0	2019-09-22 08:49:25.003	info	(COMPACT) http server listening on port 8081
admin.0	2019-09-22 08:49:24.916	info	(COMPACT) received all objects
admin.0	2019-09-22 08:49:24.626	info	(COMPACT) received all states
host.Beelink	2019-09-22 08:49:24.613	info	Update repository "latest" under "http://download.iobroker.net/sources-dist-latest.json"
admin.0	2019-09-22 08:49:24.112	info	(COMPACT) Request actual repository...
admin.0	2019-09-22 08:49:24.110	info	(COMPACT) requesting all objects
admin.0	2019-09-22 08:49:24.108	info	(COMPACT) requesting all states
admin.0	2019-09-22 08:49:24.100	info	(COMPACT) starting. Version 3.6.5 in /opt/iobroker/node_modules/iobroker.admin, node: v10.16.3
host.Beelink.compactgroup1	2019-09-22 08:49:23.304	info	instance system.adapter.admin.0 started in COMPACT mode
host.Beelink.compactgroup1	2019-09-22 08:49:22.703	info	starting 6 instances
host.Beelink.compactgroup1	2019-09-22 08:49:22.546	info	connected to Objects and States
host.Beelink.compactgroup1	2019-09-22 08:49:22.465	info	iobroker.js-controller version 2.0.6 js-controller starting
host.Beelink	2019-09-22 08:49:21.895	info	instance system.adapter.telegram.0 is handled by compact group controller pid 10508
host.Beelink	2019-09-22 08:49:21.876	info	start controller for compactgroup 1
   2019-09-22 08:49:20.872	info	"system.adapter.admin.0","system.adapter.backitup.0","system.adapter.iot.0","system.adapter.history.0","system.adapter.harmony.0","system.adapter.tankerkoenig.0","system.adapter.telegram.0","system.ad
host.Beelink	2019-09-22 08:49:20.872	info	Restart compact group controller 1
host.Beelink	2019-09-22 08:49:20.872	error	Caught by controller[11]: at Timer.processTimers (timers.js:223:10)
host.Beelink	2019-09-22 08:49:20.872	error	Caught by controller[11]: at listOnTimeout (timers.js:263:5)
host.Beelink	2019-09-22 08:49:20.872	error	Caught by controller[11]: at tryOnTimeout (timers.js:300:5)
host.Beelink	2019-09-22 08:49:20.872	error	Caught by controller[11]: at ontimeout (timers.js:436:11)
host.Beelink	2019-09-22 08:49:20.871	error	Caught by controller[11]: at Timeout.setTimeout [as _onTimeout] (/opt/iobroker/node_modules/iobroker.js-controller/main.js:3425:38)
host.Beelink	2019-09-22 08:49:20.871	error	Caught by controller[11]: at process.exit (internal/process/per_thread.js:168:15)
host.Beelink	2019-09-22 08:49:20.871	error	Caught by controller[11]: at process.emit (events.js:203:15)
host.Beelink	2019-09-22 08:49:20.871	error	Caught by controller[11]: at Object.onceWrapper (events.js:286:20)
host.Beelink	2019-09-22 08:49:20.871	error	Caught by controller[11]: at process.stop (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6730:18)
host.Beelink	2019-09-22 08:49:20.871	error	Caught by controller[11]: at Adapter.emit (events.js:198:13)
host.Beelink	2019-09-22 08:49:20.871	error	Caught by controller[11]: at Adapter.adapter.on (/opt/iobroker/node_modules/iobroker.telegram/main.js:172:50)
host.Beelink	2019-09-22 08:49:20.871	error	Caught by controller[11]: at Adapter.setState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4846:33)
host.Beelink	2019-09-22 08:49:20.871	error	Caught by controller[11]: TypeError: Cannot read property 'setState' of null
host.Beelink	2019-09-22 08:49:20.871	error	Caught by controller[10]: at Timer.processTimers (timers.js:223:10)
host.Beelink	2019-09-22 08:49:20.871	error	Caught by controller[10]: at listOnTimeout (timers.js:263:5)
host.Beelink	2019-09-22 08:49:20.871	error	Caught by controller[10]: at tryOnTimeout (timers.js:300:5)
host.Beelink	2019-09-22 08:49:20.871	error	Caught by controller[10]: at ontimeout (timers.js:436:11)
host.Beelink	2019-09-22 08:49:20.870	error	Caught by controller[10]: at Timeout.setTimeout [as _onTimeout] (/opt/iobroker/node_modules/iobroker.js-controller/main.js:3425:38)
host.Beelink	2019-09-22 08:49:20.870	error	Caught by controller[10]: at process.exit (internal/process/per_thread.js:168:15)
host.Beelink	2019-09-22 08:49:20.870	error	Caught by controller[10]: at process.emit (events.js:203:15)
host.Beelink	2019-09-22 08:49:20.870	error	Caught by controller[10]: at Object.onceWrapper (events.js:286:20)
host.Beelink	2019-09-22 08:49:20.870	error	Caught by controller[10]: at process.stop (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6730:18)
host.Beelink	2019-09-22 08:49:20.870	error	Caught by controller[10]: at Adapter.emit (events.js:198:13)
host.Beelink	2019-09-22 08:49:20.870	error	Caught by controller[10]: at Adapter.adapter.on (/opt/iobroker/node_modules/iobroker.telegram/main.js:172:50)
host.Beelink	2019-09-22 08:49:20.870	error	Caught by controller[10]: at Adapter.setState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4846:33)
host.Beelink	2019-09-22 08:49:20.870	error	Caught by controller[10]: TypeError: Cannot read property 'setState' of null
host.Beelink	2019-09-22 08:49:20.870	error	Caught by controller[9]: at Timer.processTimers (timers.js:223:10)
host.Beelink	2019-09-22 08:49:20.870	error	Caught by controller[9]: at listOnTimeout (timers.js:263:5)
host.Beelink	2019-09-22 08:49:20.870	error	Caught by controller[9]: at tryOnTimeout (timers.js:300:5)
host.Beelink	2019-09-22 08:49:20.870	error	Caught by controller[9]: at ontimeout (timers.js:436:11)
host.Beelink	2019-09-22 08:49:20.869	error	Caught by controller[9]: at Timeout.setTimeout [as _onTimeout] (/opt/iobroker/node_modules/iobroker.js-controller/main.js:3425:38)
host.Beelink	2019-09-22 08:49:20.869	error	Caught by controller[9]: at process.exit (internal/process/per_thread.js:168:15)
host.Beelink	2019-09-22 08:49:20.869	error	Caught by controller[9]: at process.emit (events.js:203:15)
host.Beelink	2019-09-22 08:49:20.869	error	Caught by controller[9]: at Object.onceWrapper (events.js:286:20)
host.Beelink	2019-09-22 08:49:20.869	error	Caught by controller[9]: at process.stop (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6730:18)
host.Beelink	2019-09-22 08:49:20.869	error	Caught by controller[9]: at Adapter.emit (events.js:198:13)
host.Beelink	2019-09-22 08:49:20.869	error	Caught by controller[9]: at Adapter.adapter.on (/opt/iobroker/node_modules/iobroker.telegram/main.js:172:50)
host.Beelink	2019-09-22 08:49:20.869	error	Caught by controller[9]: at Adapter.setState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4846:33)
host.Beelink	2019-09-22 08:49:20.869	error	Caught by controller[9]: TypeError: Cannot read property 'setState' of null
host.Beelink	2019-09-22 08:49:20.869	error	Caught by controller[8]: at Timer.processTimers (timers.js:223:10)
host.Beelink	2019-09-22 08:49:20.869	error	Caught by controller[8]: at listOnTimeout (timers.js:263:5)
host.Beelink	2019-09-22 08:49:20.869	error	Caught by controller[8]: at tryOnTimeout (timers.js:300:5)
host.Beelink	2019-09-22 08:49:20.868	error	Caught by controller[8]: at ontimeout (timers.js:436:11)
host.Beelink	2019-09-22 08:49:20.868	error	Caught by controller[8]: at Timeout.setTimeout [as _onTimeout] (/opt/iobroker/node_modules/iobroker.js-controller/main.js:3425:38)
host.Beelink	2019-09-22 08:49:20.868	error	Caught by controller[8]: at process.exit (internal/process/per_thread.js:168:15)
host.Beelink	2019-09-22 08:49:20.868	error	Caught by controller[8]: at process.emit (events.js:203:15)
host.Beelink	2019-09-22 08:49:20.868	error	Caught by controller[8]: at Object.onceWrapper (events.js:286:20)
host.Beelink	2019-09-22 08:49:20.868	error	Caught by controller[8]: at process.stop (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6730:18)
host.Beelink	2019-09-22 08:49:20.868	error	Caught by controller[8]: at Adapter.emit (events.js:198:13)
host.Beelink	2019-09-22 08:49:20.868	error	Caught by controller[8]: at Adapter.adapter.on (/opt/iobroker/node_modules/iobroker.telegram/main.js:172:50)
host.Beelink	2019-09-22 08:49:20.868	error	Caught by controller[8]: at Adapter.setState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4846:33)
host.Beelink	2019-09-22 08:49:20.868	error	Caught by controller[8]: TypeError: Cannot read property 'setState' of null
host.Beelink	2019-09-22 08:49:20.868	error	Caught by controller[7]: at Timer.processTimers (timers.js:223:10)
host.Beelink	2019-09-22 08:49:20.868	error	Caught by controller[7]: at listOnTimeout (timers.js:263:5)
host.Beelink	2019-09-22 08:49:20.868	error	Caught by controller[7]: at tryOnTimeout (timers.js:300:5)
host.Beelink	2019-09-22 08:49:20.867	error	Caught by controller[7]: at ontimeout (timers.js:436:11)
host.Beelink	2019-09-22 08:49:20.867	error	Caught by controller[7]: at Timeout.setTimeout [as _onTimeout] (/opt/iobroker/node_modules/iobroker.js-controller/main.js:3425:38)
host.Beelink	2019-09-22 08:49:20.867	error	Caught by controller[7]: at process.exit (internal/process/per_thread.js:168:15)
host.Beelink	2019-09-22 08:49:20.867	error	Caught by controller[7]: at process.emit (events.js:203:15)
host.Beelink	2019-09-22 08:49:20.867	error	Caught by controller[7]: at Object.onceWrapper (events.js:286:20)
host.Beelink	2019-09-22 08:49:20.867	error	Caught by controller[7]: at process.stop (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6730:18)
host.Beelink	2019-09-22 08:49:20.867	error	Caught by controller[7]: at Adapter.emit (events.js:198:13)
host.Beelink	2019-09-22 08:49:20.867	error	Caught by controller[7]: at Adapter.adapter.on (/opt/iobroker/node_modules/iobroker.telegram/main.js:172:50)
host.Beelink	2019-09-22 08:49:20.867	error	Caught by controller[7]: at Adapter.setState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4846:33)
host.Beelink	2019-09-22 08:49:20.867	error	Caught by controller[7]: TypeError: Cannot read property 'setState' of null
host.Beelink	2019-09-22 08:49:20.867	error	Caught by controller[7]: at Timer.processTimers (timers.js:223:10)
host.Beelink	2019-09-22 08:49:20.867	error	Caught by controller[7]: at listOnTimeout (timers.js:263:5)
host.Beelink	2019-09-22 08:49:20.867	error	Caught by controller[7]: at tryOnTimeout (timers.js:300:5)
host.Beelink	2019-09-22 08:49:20.866	error	Caught by controller[7]: at ontimeout (timers.js:436:11)
host.Beelink	2019-09-22 08:49:20.866	error	Caught by controller[7]: at Timeout.setTimeout [as _onTimeout] (/opt/iobroker/node_modules/iobroker.js-controller/main.js:3425:38)
host.Beelink	2019-09-22 08:49:20.866	error	Caught by controller[7]: at process.exit (internal/process/per_thread.js:168:15)
host.Beelink	2019-09-22 08:49:20.866	error	Caught by controller[7]: at process.emit (events.js:203:15)
host.Beelink	2019-09-22 08:49:20.866	error	Caught by controller[7]: at Object.onceWrapper (events.js:286:20)
host.Beelink	2019-09-22 08:49:20.866	error	Caught by controller[7]: at process.stop (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6730:18)
host.Beelink	2019-09-22 08:49:20.866	error	Caught by controller[7]: at Adapter.emit (events.js:198:13)
host.Beelink	2019-09-22 08:49:20.866	error	Caught by controller[7]: at Adapter.adapter.on (/opt/iobroker/node_modules/iobroker.telegram/main.js:172:50)
host.Beelink	2019-09-22 08:49:20.866	error	Caught by controller[7]: at Adapter.setState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4846:33)
host.Beelink	2019-09-22 08:49:20.866	error	Caught by controller[7]: TypeError: Cannot read property 'setState' of null
host.Beelink	2019-09-22 08:49:20.866	error	Caught by controller[6]: at process._tickCallback (internal/process/next_tick.js:61:11)
host.Beelink	2019-09-22 08:49:20.866	error	Caught by controller[6]: at /opt/iobroker/node_modules/iobroker.admin/node_modules/socket.io/lib/socket.js:503:12
host.Beelink	2019-09-22 08:49:20.866	error	Caught by controller[6]: at Socket.emit (events.js:198:13)
host.Beelink	2019-09-22 08:49:20.865	error	Caught by controller[6]: at Socket.<anonymous> (/opt/iobroker/node_modules/iobroker.admin/lib/socket.js:878:25)
host.Beelink	2019-09-22 08:49:20.865	error	Caught by controller[6]: at Adapter.sendToHost (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4732:29)
host.Beelink	2019-09-22 08:49:20.865	error	Caught by controller[6]: TypeError: Cannot read property 'pushMessage' of null
host.Beelink	2019-09-22 08:49:20.865	error	Caught by controller[5]: at process._tickCallback (internal/process/next_tick.js:61:11)
host.Beelink	2019-09-22 08:49:20.865	error	Caught by controller[5]: at /opt/iobroker/node_modules/iobroker.admin/node_modules/socket.io/lib/socket.js:503:12
host.Beelink	2019-09-22 08:49:20.865	error	Caught by controller[5]: at Socket.emit (events.js:198:13)
host.Beelink	2019-09-22 08:49:20.865	error	Caught by controller[5]: at Socket.<anonymous> (/opt/iobroker/node_modules/iobroker.admin/lib/socket.js:878:25)
host.Beelink	2019-09-22 08:49:20.865	error	Caught by controller[5]: at Adapter.sendToHost (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4732:29)
host.Beelink	2019-09-22 08:49:20.865	error	Caught by controller[5]: TypeError: Cannot read property 'pushMessage' of null
host.Beelink	2019-09-22 08:49:20.865	error	Caught by controller[4]: at process._tickCallback (internal/process/next_tick.js:61:11)
host.Beelink	2019-09-22 08:49:20.865	error	Caught by controller[4]: at /opt/iobroker/node_modules/iobroker.admin/node_modules/socket.io/lib/socket.js:503:12
host.Beelink	2019-09-22 08:49:20.865	error	Caught by controller[4]: at Socket.emit (events.js:198:13)
host.Beelink	2019-09-22 08:49:20.864	error	Caught by controller[4]: at Socket.<anonymous> (/opt/iobroker/node_modules/iobroker.admin/lib/socket.js:878:25)
host.Beelink	2019-09-22 08:49:20.864	error	Caught by controller[4]: at Adapter.sendToHost (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4732:29)
host.Beelink	2019-09-22 08:49:20.864	error	Caught by controller[4]: TypeError: Cannot read property 'pushMessage' of null
host.Beelink	2019-09-22 08:49:20.864	error	Caught by controller[3]: at process._tickCallback (internal/process/next_tick.js:61:11)
host.Beelink	2019-09-22 08:49:20.864	error	Caught by controller[3]: at /opt/iobroker/node_modules/iobroker.admin/node_modules/socket.io/lib/socket.js:503:12
host.Beelink	2019-09-22 08:49:20.864	error	Caught by controller[3]: at Socket.emit (events.js:198:13)
host.Beelink	2019-09-22 08:49:20.864	error	Caught by controller[3]: at Socket.<anonymous> (/opt/iobroker/node_modules/iobroker.admin/lib/socket.js:878:25)
host.Beelink	2019-09-22 08:49:20.864	error	Caught by controller[3]: at Adapter.sendToHost (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4732:29)
host.Beelink	2019-09-22 08:49:20.864	error	Caught by controller[3]: TypeError: Cannot read property 'pushMessage' of null
host.Beelink	2019-09-22 08:49:20.864	error	Caught by controller[2]: at process._tickCallback (internal/process/next_tick.js:61:11)
host.Beelink	2019-09-22 08:49:20.864	error	Caught by controller[2]: at /opt/iobroker/node_modules/iobroker.admin/node_modules/socket.io/lib/socket.js:503:12
host.Beelink	2019-09-22 08:49:20.864	error	Caught by controller[2]: at Socket.emit (events.js:198:13)
host.Beelink	2019-09-22 08:49:20.863	error	Caught by controller[2]: at Socket.<anonymous> (/opt/iobroker/node_modules/iobroker.admin/lib/socket.js:878:25)
host.Beelink	2019-09-22 08:49:20.863	error	Caught by controller[2]: at Adapter.sendToHost (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4732:29)
host.Beelink	2019-09-22 08:49:20.863	error	Caught by controller[2]: TypeError: Cannot read property 'pushMessage' of null
host.Beelink	2019-09-22 08:49:20.863	error	Caught by controller[1]: at process._tickCallback (internal/process/next_tick.js:61:11)
host.Beelink	2019-09-22 08:49:20.863	error	Caught by controller[1]: at /opt/iobroker/node_modules/iobroker.admin/node_modules/socket.io/lib/socket.js:503:12
host.Beelink	2019-09-22 08:49:20.863	error	Caught by controller[1]: at Socket.emit (events.js:198:13)
host.Beelink	2019-09-22 08:49:20.863	error	Caught by controller[1]: at Socket.<anonymous> (/opt/iobroker/node_modules/iobroker.admin/lib/socket.js:878:25)
host.Beelink	2019-09-22 08:49:20.863	error	Caught by controller[1]: at Adapter.sendToHost (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4732:29)
host.Beelink	2019-09-22 08:49:20.863	error	Caught by controller[1]: TypeError: Cannot read property 'pushMessage' of null
host.Beelink	2019-09-22 08:49:20.863	error	Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at internal/modules/cjs/loader.js:778:30
host.Beelink	2019-09-22 08:49:20.863	error	Caught by controller[0]: In the future, you will have to enable it yourself.
host.Beelink	2019-09-22 08:49:20.862	error	Caught by controller[0]: Sun, 22 Sep 2019 06:49:06 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
host.Beelink.compactgroup1	2019-09-22 08:49:20.735	warn	stopInstance system.adapter.simple-api.0 not running
host.Beelink.compactgroup1	2019-09-22 08:49:20.735	info	stopInstance system.adapter.simple-api.0
host.Beelink.compactgroup1	2019-09-22 08:49:20.735	info	stopInstance system.adapter.iqontrol.0
host.Beelink.compactgroup1	2019-09-22 08:49:20.735	info	stopInstance system.adapter.alexa2.0
host.Beelink.compactgroup1	2019-09-22 08:49:20.735	info	stopInstance system.adapter.info.0
host.Beelink.compactgroup1	2019-09-22 08:49:20.735	info	stopInstance system.adapter.fritzdect.0
host.Beelink.compactgroup1	2019-09-22 08:49:20.734	info	stopInstance system.adapter.javascript.0
host.Beelink.compactgroup1	2019-09-22 08:49:20.734	warn	stopInstance system.adapter.telegram.0 not running
host.Beelink.compactgroup1	2019-09-22 08:49:20.734	info	stopInstance system.adapter.telegram.0
host.Beelink.compactgroup1	2019-09-22 08:49:20.734	warn	stopInstance system.adapter.tankerkoenig.0 not running
host.Beelink.compactgroup1	2019-09-22 08:49:20.734	info	stopInstance system.adapter.tankerkoenig.0
host.Beelink.compactgroup1	2019-09-22 08:49:20.734	warn	stopInstance system.adapter.harmony.0 not running
host.Beelink.compactgroup1	2019-09-22 08:49:20.733	info	stopInstance system.adapter.harmony.0
host.Beelink.compactgroup1	2019-09-22 08:49:20.733	warn	stopInstance system.adapter.history.0 not running
host.Beelink.compactgroup1	2019-09-22 08:49:20.733	info	stopInstance system.adapter.history.0
host.Beelink.compactgroup1	2019-09-22 08:49:20.732	info	stopInstance system.adapter.iot.0
host.Beelink.compactgroup1	2019-09-22 08:49:20.732	warn	stopInstance system.adapter.backitup.0 not running
host.Beelink.compactgroup1	2019-09-22 08:49:20.732	info	stopInstance system.adapter.backitup.0
host.Beelink.compactgroup1	2019-09-22 08:49:20.731	warn	stopInstance system.adapter.admin.0 not running
host.Beelink.compactgroup1	2019-09-22 08:49:20.731	info	stopInstance system.adapter.admin.0
host.Beelink.compactgroup1	2019-09-22 08:49:20.728	warn	Slave controller detected disconnection. Stop all instances.
tankerkoenig.0	2019-09-22 08:49:20.286	info	(COMPACT) terminating
harmony.0	2019-09-22 08:49:20.285	info	(COMPACT) terminating
backitup.0	2019-09-22 08:49:20.279	info	(COMPACT) terminating
admin.0	2019-09-22 08:49:20.278	info	(COMPACT) terminating
telegram.0	2019-09-22 08:49:19.786	error	(COMPACT) exception by stop: Cannot read property 'setState' of null
telegram.0	2019-09-22 08:49:19.786	error	at Timer.processTimers (timers.js:223:10)
telegram.0	2019-09-22 08:49:19.786	error	at listOnTimeout (timers.js:263:5)
telegram.0	2019-09-22 08:49:19.786	error	at tryOnTimeout (timers.js:300:5)
telegram.0	2019-09-22 08:49:19.786	error	at ontimeout (timers.js:436:11)
telegram.0	2019-09-22 08:49:19.786	error	at Timeout.setTimeout [as _onTimeout] (/opt/iobroker/node_modules/iobroker.js-controller/main.js:3425:38)
telegram.0	2019-09-22 08:49:19.786	error	at process.exit (internal/process/per_thread.js:168:15)
telegram.0	2019-09-22 08:49:19.786	error	at process.emit (events.js:203:15)
telegram.0	2019-09-22 08:49:19.786	error	at Object.onceWrapper (events.js:286:20)
telegram.0	2019-09-22 08:49:19.786	error	at process.stop (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6730:18)
telegram.0	2019-09-22 08:49:19.786	error	at Adapter.emit (events.js:198:13)
telegram.0	2019-09-22 08:49:19.786	error	at Adapter.adapter.on (/opt/iobroker/node_modules/iobroker.telegram/main.js:172:50)
telegram.0	2019-09-22 08:49:19.786	error	at Adapter.setState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4846:33)
telegram.0	2019-09-22 08:49:19.786	error	(COMPACT) TypeError: Cannot read property 'setState' of null
tankerkoenig.0	2019-09-22 08:49:19.785	error	at Timer.processTimers (timers.js:223:10)
tankerkoenig.0	2019-09-22 08:49:19.785	error	at listOnTimeout (timers.js:263:5)
tankerkoenig.0	2019-09-22 08:49:19.785	error	at tryOnTimeout (timers.js:300:5)
tankerkoenig.0	2019-09-22 08:49:19.785	error	at ontimeout (timers.js:436:11)
tankerkoenig.0	2019-09-22 08:49:19.785	error	at Timeout.setTimeout [as _onTimeout] (/opt/iobroker/node_modules/iobroker.js-controller/main.js:3425:38)
tankerkoenig.0	2019-09-22 08:49:19.785	error	at process.exit (internal/process/per_thread.js:168:15)
tankerkoenig.0	2019-09-22 08:49:19.785	error	at process.emit (events.js:203:15)
tankerkoenig.0	2019-09-22 08:49:19.785	error	at Object.onceWrapper (events.js:286:20)
tankerkoenig.0	2019-09-22 08:49:19.785	error	at process.stop (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6730:18)
tankerkoenig.0	2019-09-22 08:49:19.785	error	at Adapter.emit (events.js:198:13)
tankerkoenig.0	2019-09-22 08:49:19.785	error	at Adapter.adapter.on (/opt/iobroker/node_modules/iobroker.telegram/main.js:172:50)
tankerkoenig.0	2019-09-22 08:49:19.785	error	at Adapter.setState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4846:33)
tankerkoenig.0	2019-09-22 08:49:19.785	error	(COMPACT) TypeError: Cannot read property 'setState' of null
history.0	2019-09-22 08:49:19.783	info	(COMPACT) terminating
history.0	2019-09-22 08:49:19.783	error	at Timer.processTimers (timers.js:223:10)
history.0	2019-09-22 08:49:19.783	error	at listOnTimeout (timers.js:263:5)
history.0	2019-09-22 08:49:19.783	error	at tryOnTimeout (timers.js:300:5)
history.0	2019-09-22 08:49:19.783	error	at ontimeout (timers.js:436:11)
history.0	2019-09-22 08:49:19.783	error	at Timeout.setTimeout [as _onTimeout] (/opt/iobroker/node_modules/iobroker.js-controller/main.js:3425:38)
history.0	2019-09-22 08:49:19.783	error	at process.exit (internal/process/per_thread.js:168:15)
history.0	2019-09-22 08:49:19.783	error	at process.emit (events.js:203:15)
history.0	2019-09-22 08:49:19.783	error	at Object.onceWrapper (events.js:286:20)
history.0	2019-09-22 08:49:19.783	error	at process.stop (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6730:18)
history.0	2019-09-22 08:49:19.783	error	at Adapter.emit (events.js:198:13)
history.0	2019-09-22 08:49:19.783	error	at Adapter.adapter.on (/opt/iobroker/node_modules/iobroker.telegram/main.js:172:50)
history.0	2019-09-22 08:49:19.783	error	at Adapter.setState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4846:33)
history.0	2019-09-22 08:49:19.783	error	(COMPACT) TypeError: Cannot read property 'setState' of null
backitup.0	2019-09-22 08:49:19.778	error	at Timer.processTimers (timers.js:223:10)
backitup.0	2019-09-22 08:49:19.778	error	at listOnTimeout (timers.js:263:5)
backitup.0	2019-09-22 08:49:19.778	error	at tryOnTimeout (timers.js:300:5)
backitup.0	2019-09-22 08:49:19.778	error	at ontimeout (timers.js:436:11)
backitup.0	2019-09-22 08:49:19.778	error	at Timeout.setTimeout [as _onTimeout] (/opt/iobroker/node_modules/iobroker.js-controller/main.js:3425:38)
backitup.0	2019-09-22 08:49:19.778	error	at process.exit (internal/process/per_thread.js:168:15)
backitup.0	2019-09-22 08:49:19.778	error	at process.emit (events.js:203:15)
backitup.0	2019-09-22 08:49:19.778	error	at Object.onceWrapper (events.js:286:20)
backitup.0	2019-09-22 08:49:19.778	error	at process.stop (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6730:18)
backitup.0	2019-09-22 08:49:19.778	error	at Adapter.emit (events.js:198:13)
backitup.0	2019-09-22 08:49:19.778	error	at Adapter.adapter.on (/opt/iobroker/node_modules/iobroker.telegram/main.js:172:50)
backitup.0	2019-09-22 08:49:19.778	error	at Adapter.setState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4846:33)
backitup.0	2019-09-22 08:49:19.778	error	(COMPACT) TypeError: Cannot read property 'setState' of null
harmony.0	2019-09-22 08:49:19.784	info	(COMPACT) terminating
harmony.0	2019-09-22 08:49:19.784	info	(COMPACT) [END] Terminating
harmony.0	2019-09-22 08:49:19.784	error	at Timer.processTimers (timers.js:223:10)
harmony.0	2019-09-22 08:49:19.784	error	at listOnTimeout (timers.js:263:5)
harmony.0	2019-09-22 08:49:19.784	error	at tryOnTimeout (timers.js:300:5)
harmony.0	2019-09-22 08:49:19.784	error	at ontimeout (timers.js:436:11)
harmony.0	2019-09-22 08:49:19.784	error	at Timeout.setTimeout [as _onTimeout] (/opt/iobroker/node_modules/iobroker.js-controller/main.js:3425:38)
harmony.0	2019-09-22 08:49:19.784	error	at process.exit (internal/process/per_thread.js:168:15)
harmony.0	2019-09-22 08:49:19.784	error	at process.emit (events.js:203:15)
harmony.0	2019-09-22 08:49:19.784	error	at Object.onceWrapper (events.js:286:20)
harmony.0	2019-09-22 08:49:19.784	error	at process.stop (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6730:18)
harmony.0	2019-09-22 08:49:19.784	error	at Adapter.emit (events.js:198:13)
harmony.0	2019-09-22 08:49:19.784	error	at Adapter.adapter.on (/opt/iobroker/node_modules/iobroker.telegram/main.js:172:50)
harmony.0	2019-09-22 08:49:19.784	error	at Adapter.setState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4846:33)
harmony.0	2019-09-22 08:49:19.784	error	(COMPACT) TypeError: Cannot read property 'setState' of null
harmony.0	2019-09-22 08:49:19.784	error	(COMPACT) uncaught exception: Cannot read property 'setState' of null
admin.0	2019-09-22 08:49:19.777	info	(COMPACT) terminating
admin.0	2019-09-22 08:49:19.776	info	(COMPACT) terminating http server on port 8081

apollon77

@Dr-Bakterius direkt ins file Skootern ist nicht wirklich supporters weil dann Meta Daten fehlen.

apollon77

@Jan1 Mist. Schaue ich mir an

Jan1

@apollon77
keine Panik, wenn ich den compact modus disable, läuft ja alles und das ist in ein paar Sekunden umgestellt :wink:

opossum

Hallo,
erst mal danke für die schnelle Antwort.

@Dr-Bakterius sagte in [Aufruf] js-controller 2.0 Beta Test:

Wenn man das direkt auf dem ioBroker-Rechner machen möchte, gehören die Dateien nach /opt/iobroker/iobroker-data/files/vis.0

habe ich kopiert:

Aber sie werden mir im Auswahldialog leider nicht angezeigt:

Irgend etwas ist noch nicht korrekt bei mir. Klicke ich auf den Uploadbutton, dann kommt bei mir folgendes:

Ich kann von dort auch hochladen, aber in der Auswahl sieht das dann so aus:

Dabei stehen die Rechte der Dateien wie folgt:

Sorry, wenn ich nerve.
Gruß
Egbert

apollon77

@Jan1 Liegt nicht direkt an der 2.0.6 ... ist ein "Timing" thema. fix kommt in 2.0.7

apollon77

@opossum vis upload vor der 1.2.1 war kaputt. Bitte 1.2.1 aus latest installieren

opossum

Hallo,

@opossum vis upload vor der 1.2.1 war kaputt. Bitte 1.2.1 aus latest installieren

das war es, nun funktioniert das. Danke @apollon77, dann werde meine vis umstellen.

Gruß
Egbert

AlCalzone

@Jan1 Kannst du bitte BLE v0.9.1 probieren?

apollon77

@AlCalzone @Jan1 bitte warte mal noch :-)) Ich würde gern das Du die alte nochmal mit der 2.0.7 vom controller testet :-)) geht das? Ich finalisiere den jetzt

apollon77

Sooooooo ... Auf GitHub haben wir jetzt die 2.0.7 vom js-controller.

Änderungen und Test-Bitten:

Ich habe nochmal am Fallback-Handling bei Adaptern mit "kaputtem" Compact-Mode gearbeitet. Bitte mit der "alten" BLE Version nochmal testen :-) Danach die neue gern auch
In einigen Fällen konnten in den File-DB-Strukturen Fehler entstehen die dann dazugefhrt haben das Files nicht angezeigt wurden, Diese werden nun beim lesen behoben.
Slaves sollten jetzt Disconnects (von der Objects-DB!) besser erkennen und ggf in 30s Intervallen neu versuchen. @e-i-k-e Schaunochmal wie sich die Slaves jetzt verhalten wenn der Master weg ist. AM besten die Slaves zuerst auf 2.0.7, dann starten und dann den Master ... Ein Log wäre wieder interessant

Jan1

@apollon77
jetzt läuft alles im compact mode wie es soll (mit BLE 0.9.0). Keine Fehler oder Warnungen im Log, ale Adapter lassen sich einzeln neu starten, ohne Auswirkung auf das System

@AlCalzone
BLE 0.9.1 funktioniert nun auch im compact modus.

apollon77

@Jan1 sagte in [Aufruf] js-controller 2.0 Beta Test:

@apollon77
jetzt läuft alles im compact mode wie es soll (mit BLE 0.9.0). Keine Fehler oder Warnungen im Log, ale Adapter lassen sich einzeln neu starten, ohne Auswirkung auf das System

Hast Du mal noch ein Log von so einem 0.9.0 versuch?! Aber cool

Jan1

@apollon77
nein, weil alles sauber war und keine Fehler oder Warnungen drin standen. Wenn Du willst, hau ich noch mal die 0.9.0 Version ndes BLE drauf.

apollon77

@Jan1 Ich hätte mindestesn eine Meldung "compact geht nicht daher starte ich normal" erwartet und dann sollte der start direkt erfolgen und ein pot. gestarteter compact sollte sich beenden.

Jan1

@apollon77
so hab noch mal die 0.9.0 drauf und den compact modus aktiviert, jetzt waren plötzlich viele Fehler im Log

host.Beelink.compactgroup1	2019-09-23 08:56:08.158	info	Restart adapter system.adapter.ble.0 because enabled
host.Beelink.compactgroup1	2019-09-23 08:56:08.157	error	instance system.adapter.ble.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
ble	2019-09-23 08:56:08.097	error	(13338) ble.0 already running
ble.0	2019-09-23 08:56:07.851	info	(COMPACT) monitored services: fe95
ble.0	2019-09-23 08:56:07.851	info	(COMPACT) enabled plugins: mi-flora, _default
ble.0	2019-09-23 08:56:07.850	info	(COMPACT) loaded plugins: Xiaomi, mi-flora, ruuvi-tag, _default
ble.0	2019-09-23 08:56:07.721	info	(COMPACT) starting. Version 0.9.0 in /opt/iobroker/node_modules/iobroker.ble, node: v10.16.3
host.Beelink.compactgroup1	2019-09-23 08:56:07.407	info	instance system.adapter.ble.0 started with pid 13338
   2019-09-23 08:56:07.385	error	ndefined
host.Beelink.compactgroup1	2019-09-23 08:56:07.385	error	Cannot start ble.0 in compact mode. Fallback to normal start! : Cannot read property 'on' of undefined
host.Beelink.compactgroup1	2019-09-23 08:55:37.362	info	Restart adapter system.adapter.ble.0 because enabled
host.Beelink.compactgroup1	2019-09-23 08:55:37.361	error	instance system.adapter.ble.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
ble	2019-09-23 08:55:37.295	error	(12663) ble.0 already running
ble.0	2019-09-23 08:55:37.177	info	(COMPACT) terminating
ble.0	2019-09-23 08:55:37.175	info	(COMPACT) terminating
ble	2019-09-23 08:55:36.694	warn	(COMPACT) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
ble	2019-09-23 08:55:36.693	error	(COMPACT) ble.0 already running
ble.0	2019-09-23 08:55:36.676	info	(COMPACT) terminating
ble.0	2019-09-23 08:55:36.675	info	(COMPACT) stopping scan
ble.0	2019-09-23 08:55:36.675	info	(COMPACT) Got terminate signal 12663
ble.0	2019-09-23 08:55:36.674	info	(COMPACT) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
ble.0	2019-09-23 08:55:36.674	info	(COMPACT) terminating
ble.0	2019-09-23 08:55:36.673	info	(COMPACT) stopping scan
ble.0	2019-09-23 08:55:36.672	info	(COMPACT) Got terminate signal -1
host.Beelink.compactgroup1	2019-09-23 08:55:36.667	info	instance system.adapter.ble.0 started with pid 12663
   2019-09-23 08:55:36.648	error	ndefined
host.Beelink.compactgroup1	2019-09-23 08:55:36.648	error	Cannot start ble.0 in compact mode. Fallback to normal start! : Cannot read property 'on' of undefined
host.Beelink.compactgroup1	2019-09-23 08:55:06.630	info	Restart adapter system.adapter.ble.0 because enabled
host.Beelink.compactgroup1	2019-09-23 08:55:06.629	error	instance system.adapter.ble.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
ble	2019-09-23 08:55:06.569	error	(11988) ble.0 already running
ble.0	2019-09-23 08:55:06.435	info	(COMPACT) monitored services: fe95
ble.0	2019-09-23 08:55:06.435	info	(COMPACT) enabled plugins: mi-flora, _default
ble.0	2019-09-23 08:55:06.434	info	(COMPACT) loaded plugins: Xiaomi, mi-flora, ruuvi-tag, _default
ble.0	2019-09-23 08:55:06.278	info	(COMPACT) starting. Version 0.9.0 in /opt/iobroker/node_modules/iobroker.ble, node: v10.16.3
host.Beelink.compactgroup1	2019-09-23 08:55:05.904	info	instance system.adapter.ble.0 started with pid 11988
   2019-09-23 08:55:05.886	error	ndefined
host.Beelink.compactgroup1	2019-09-23 08:55:05.885	error	Cannot start ble.0 in compact mode. Fallback to normal start! : Cannot read property 'on' of undefined
host.Beelink.compactgroup1	2019-09-23 08:54:35.866	info	Restart adapter system.adapter.ble.0 because enabled
host.Beelink.compactgroup1	2019-09-23 08:54:35.865	error	instance system.adapter.ble.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
ble	2019-09-23 08:54:35.798	error	(11309) ble.0 already running
ble.0	2019-09-23 08:54:35.630	info	(COMPACT) terminating
ble.0	2019-09-23 08:54:35.628	info	(COMPACT) terminating
ble	2019-09-23 08:54:35.179	warn	(COMPACT) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
ble	2019-09-23 08:54:35.179	error	(COMPACT) ble.0 already running
ble.0	2019-09-23 08:54:35.128	info	(COMPACT) terminating
ble.0	2019-09-23 08:54:35.128	info	(COMPACT) stopping scan
ble.0	2019-09-23 08:54:35.128	info	(COMPACT) Got terminate signal 11309
ble.0	2019-09-23 08:54:35.127	info	(COMPACT) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
ble.0	2019-09-23 08:54:35.126	info	(COMPACT) terminating
ble.0	2019-09-23 08:54:35.125	info	(COMPACT) stopping scan
ble.0	2019-09-23 08:54:35.124	info	(COMPACT) Got terminate signal -1
host.Beelink.compactgroup1	2019-09-23 08:54:35.095	info	instance system.adapter.ble.0 started with pid 11309
   2019-09-23 08:54:35.071	error	ndefined
host.Beelink.compactgroup1	2019-09-23 08:54:35.071	error	Cannot start ble.0 in compact mode. Fallback to normal start! : Cannot read property 'on' of undefined
host.Beelink.compactgroup1	2019-09-23 08:54:05.056	info	Restart adapter system.adapter.ble.0 because enabled
host.Beelink.compactgroup1	2019-09-23 08:54:05.056	error	instance system.adapter.ble.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
ble	2019-09-23 08:54:04.991	error	(10634) ble.0 already running
ble.0	2019-09-23 08:54:04.623	info	(COMPACT) monitored services: fe95
ble.0	2019-09-23 08:54:04.623	info	(COMPACT) enabled plugins: mi-flora, _default
ble.0	2019-09-23 08:54:04.622	info	(COMPACT) loaded plugins: Xiaomi, mi-flora, ruuvi-tag, _default
ble.0	2019-09-23 08:54:04.510	info	(COMPACT) starting. Version 0.9.0 in /opt/iobroker/node_modules/iobroker.ble, node: v10.16.3
host.Beelink.compactgroup1	2019-09-23 08:54:04.130	info	instance system.adapter.ble.0 started with pid 10634
   2019-09-23 08:54:04.105	error	ndefined
host.Beelink.compactgroup1	2019-09-23 08:54:04.104	error	Cannot start ble.0 in compact mode. Fallback to normal start! : Cannot read property 'on' of undefined
node-red.0	2019-09-23 08:54:03.727	warn	23 Sep 08:54:03 - [warn] Projekte inaktiviert: setze editorTheme.projects.enabled=true zum Aktivieren
node-red.0	2019-09-23 08:54:03.727	warn	(10445) 23 Sep 08:54:03 - [info] Benutzerverzeichnis: /opt/iobroker/iobroker-data/node-red/
node-red.0	2019-09-23 08:54:03.317	warn	(10445) 23 Sep 08:54:03 - [warn] rpi-gpio : Pi RPi.GPIO-Python-Bibliothek nicht gefunden
node-red.0	2019-09-23 08:54:03.311	warn	(10445) 23 Sep 08:54:03 - [warn] rpi-gpio : Raspberry Pi-spezifische Nodes inaktiv
node-red.0	2019-09-23 08:53:59.523	info	(10445) Starting node-red: --max-old-space-size=128 /opt/iobroker/node_modules/node-red/red.js -v --settings /opt/iobroker/iobroker-data/node-red/settings.js
node-red.0	2019-09-23 08:53:58.974	info	(10445) starting. Version 1.9.0 in /opt/iobroker/node_modules/iobroker.node-red, node: v10.16.3
host.Beelink	2019-09-23 08:53:57.433	info	instance system.adapter.node-red.0 started with pid 10445
host.Beelink	2019-09-23 08:53:53.437	info	instance system.adapter.sonoff.0 started with pid 10418
host.Beelink	2019-09-23 08:53:49.417	info	instance system.adapter.ble.0 is handled by compact group controller pid 8673
iqontrol.0	2019-09-23 08:53:45.419	info	(COMPACT) state system.adapter.iqontrol.0.sigKill changed: 0 (ack = false)
host.Beelink	2019-09-23 08:53:45.418	info	instance system.adapter.iqontrol.0 is handled by compact group controller pid 8673
tr-064-community.0	2019-09-23 08:53:43.109	info	(10087) starting. Version 1.0.0 in /opt/iobroker/node_modules/iobroker.tr-064-community, node: v10.16.3
host.Beelink	2019-09-23 08:53:41.430	info	instance system.adapter.tr-064-community.0 started with pid 10087
host.Beelink	2019-09-23 08:53:37.456	info	instance system.adapter.zigbee.0 started with pid 10056
wifilight.0	2019-09-23 08:53:35.007	info	(9890) starting. Version 0.2.0 in /opt/iobroker/node_modules/iobroker.wifilight, node: v10.16.3
host.Beelink.compactgroup1	2019-09-23 08:53:34.094	info	Restart adapter system.adapter.ble.0 because enabled
host.Beelink.compactgroup1	2019-09-23 08:53:34.093	error	instance system.adapter.ble.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
ble	2019-09-23 08:53:34.028	error	(9878) ble.0 already running
ble.0	2019-09-23 08:53:33.778	info	(COMPACT) terminating
ble.0	2019-09-23 08:53:33.777	info	(COMPACT) terminating
host.Beelink	2019-09-23 08:53:33.437	info	instance system.adapter.wifilight.0 started with pid 9890
ble	2019-09-23 08:53:33.287	warn	(COMPACT) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
ble	2019-09-23 08:53:33.287	error	(COMPACT) ble.0 already running
ble.0	2019-09-23 08:53:33.271	info	(COMPACT) terminating
ble.0	2019-09-23 08:53:33.271	info	(COMPACT) stopping scan
ble.0	2019-09-23 08:53:33.270	info	(COMPACT) Got terminate signal 9878
ble.0	2019-09-23 08:53:33.267	info	(COMPACT) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
ble.0	2019-09-23 08:53:33.266	info	(COMPACT) terminating
ble.0	2019-09-23 08:53:33.265	info	(COMPACT) stopping scan
ble.0	2019-09-23 08:53:33.264	info	(COMPACT) Got terminate signal -1
host.Beelink.compactgroup1	2019-09-23 08:53:33.260	info	instance system.adapter.ble.0 started with pid 9878
   2019-09-23 08:53:33.237	error	ndefined
host.Beelink.compactgroup1	2019-09-23 08:53:33.237	error	Cannot start ble.0 in compact mode. Fallback to normal start! : Cannot read property 'on' of undefined
enigma2.0	2019-09-23 08:53:31.542	info	(9519) enigma2 Verbunden!
host.Beelink	2019-09-23 08:53:29.414	info	instance system.adapter.alexa2.0 is handled by compact group controller pid 8673
info.0	2019-09-23 08:53:25.426	info	(COMPACT) ack is not set!
info.0	2019-09-23 08:53:25.425	info	(COMPACT) stateChange system.adapter.info.0.sigKill {"val":0,"ack":false,"ts":1569221605415,"q":0,"from":"system.host.Beelink","lc":1569221570394}
host.Beelink	2019-09-23 08:53:25.415	info	instance system.adapter.info.0 is handled by compact group controller pid 8673
host.Beelink	2019-09-23 08:53:21.416	info	instance system.adapter.fritzdect.0 is handled by compact group controller pid 8673
host.Beelink	2019-09-23 08:53:17.431	info	instance system.adapter.google-sharedlocations.0 started with pid 9550
enigma2.0	2019-09-23 08:53:16.301	info	(9519) starting Polling every 15000 ms
enigma2.0	2019-09-23 08:53:16.270	info	(9519) starting. Version 1.2.3 in /opt/iobroker/node_modules/iobroker.enigma2, node: v10.16.3
host.Beelink	2019-09-23 08:53:13.436	info	instance system.adapter.enigma2.0 started with pid 9519
email.0	2019-09-23 08:53:10.755	info	(9360) starting. Version 1.0.5 in /opt/iobroker/node_modules/iobroker.email, node: v10.16.3
host.Beelink	2019-09-23 08:53:09.430	info	instance system.adapter.email.0 started with pid 9360
host.Beelink	2019-09-23 08:53:05.416	info	instance system.adapter.javascript.0 is handled by compact group controller pid 8673
vr200.0	2019-09-23 08:53:03.576	info	(9174) devices found: 1
host.Beelink.compactgroup1	2019-09-23 08:53:03.219	info	Restart adapter system.adapter.ble.0 because enabled
host.Beelink.compactgroup1	2019-09-23 08:53:03.218	error	instance system.adapter.ble.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
ble.0	2019-09-23 08:53:03.174	info	(COMPACT) starting scan for services ["fe95"]
ble	2019-09-23 08:53:03.153	error	(9328) ble.0 already running
ble.0	2019-09-23 08:53:02.837	info	(COMPACT) monitored services: fe95
ble.0	2019-09-23 08:53:02.835	info	(COMPACT) enabled plugins: mi-flora, _default
vr200.0	2019-09-23 08:53:02.926	info	(9174) starting. Version 1.0.0 in /opt/iobroker/node_modules/iobroker.vr200, node: v10.16.3
ble.0	2019-09-23 08:53:02.834	info	(COMPACT) loaded plugins: Xiaomi, mi-flora, ruuvi-tag, _default
ble.0	2019-09-23 08:53:02.728	info	(COMPACT) starting. Version 0.9.0 in /opt/iobroker/node_modules/iobroker.ble, node: v10.16.3
host.Beelink.compactgroup1	2019-09-23 08:53:02.387	info	instance system.adapter.ble.0 started with pid 9328
   2019-09-23 08:53:02.362	error	ndefined
host.Beelink.compactgroup1	2019-09-23 08:53:02.361	error	Cannot start ble.0 in compact mode. Fallback to normal start! : Cannot read property 'on' of undefined
host.Beelink	2019-09-23 08:53:01.431	info	instance system.adapter.vr200.0 started with pid 9174
alexa2.0	2019-09-23 08:53:00.806	info	(COMPACT) Alexa-Push-Connection established. Disable Polling
iqontrol.0	2019-09-23 08:52:59.028	info	(COMPACT) Deleting unused Objects...

War ne blöde Idee noch mal auf 0.9.0 zurück zu gehen, jetzt startet der BLE Adapter nicht mehr. Bin gerade am reparieren.
Läuft wieder nach dem der Fixer drüber ist

root@Beelink:/opt/iobroker# iobroker list instances
+ system.adapter.admin.0                 : admin                 -  enabled, compact enabled (group 1), port: 8081, bind: 0.0.0.0, run as: admin
 system.adapter.admin.1                 : admin                 - disabled, compact disabled, port: 8082, bind: 0.0.0.0 (SSL), run as: admin
+ system.adapter.alexa2.0                : alexa2                -  enabled, compact enabled (group 1)
+ system.adapter.backitup.0              : backitup              -  enabled, compact enabled (group 1)
+ system.adapter.ble.0                   : ble                   -  enabled, compact enabled (group 1)
+ system.adapter.email.0                 : email                 -  enabled, compact disabled
+ system.adapter.enigma2.0               : enigma2               -  enabled, compact disabled
+ system.adapter.fritzdect.0             : fritzdect             -  enabled, compact enabled (group 1)
+ system.adapter.google-sharedlocations.0: google-sharedlocations -  enabled, compact disabled
+ system.adapter.harmony.0               : harmony               -  enabled, compact enabled (group 1)
+ system.adapter.history.0               : history               -  enabled, compact enabled (group 1)
 system.adapter.ical.0                  : ical                  -  enabled, compact disabled
+ system.adapter.info.0                  : info                  -  enabled, compact enabled (group 1)
+ system.adapter.iot.0                   : iot                   -  enabled, compact enabled (group 1)
+ system.adapter.iqontrol.0              : iqontrol              -  enabled, compact enabled (group 1)
+ system.adapter.javascript.0            : javascript            -  enabled, compact enabled (group 1)
+ system.adapter.milight-smart-light.0   : milight-smart-light   -  enabled, compact disabled
+ system.adapter.node-red.0              : node-red              -  enabled, compact disabled, port: 1880, bind: 0.0.0.0
 system.adapter.openweathermap.0        : openweathermap        -  enabled, compact disabled
+ system.adapter.scenes.0                : scenes                -  enabled, compact disabled
 system.adapter.simple-api.0            : simple-api            -  enabled, compact enabled (group 1), port: 8087, bind: 0.0.0.0, run as: admin
+ system.adapter.sonoff.0                : sonoff                -  enabled, compact disabled, port: 1883, bind: 0.0.0.0
+ system.adapter.tankerkoenig.0          : tankerkoenig          -  enabled, compact enabled (group 1)
+ system.adapter.telegram.0              : telegram              -  enabled, compact enabled (group 1), port: 8443, bind: 0.0.0.0
+ system.adapter.tr-064-community.0      : tr-064-community      -  enabled, compact disabled
+ system.adapter.vr200.0                 : vr200                 -  enabled, compact disabled
+ system.adapter.web.0                   : web                   -  enabled, compact disabled, port: 8082, bind: 0.0.0.0, run as: admin
+ system.adapter.wifilight.0             : wifilight             -  enabled, compact disabled
+ system.adapter.zigbee.0                : zigbee                -  enabled, compact disabled, port: /dev/serial/by-id/usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B0018ED3DD2-if00

+ instance is alive

Community Forum

NEWS

Test js-controller v2.0.x (GitHub)

Support us

761

32.4k

81.4k

1.3m