Skip to content
  • Home
  • Aktuell
  • Tags
  • 0 Ungelesen 0
  • Kategorien
  • Unreplied
  • Beliebt
  • GitHub
  • Docu
  • Hilfe
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Standard: (Kein Skin)
  • Kein Skin
Einklappen
ioBroker Logo

Community Forum

  1. ioBroker Community Home
  2. Deutsch
  3. Tester
  4. Test js-controller v2.0.x (GitHub)

NEWS

  • UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?
    apollon77A
    apollon77
    48
    3
    8.2k

  • Monatsrückblick – September 2025
    BluefoxB
    Bluefox
    13
    1
    1.9k

  • Neues Video "KI im Smart Home" - ioBroker plus n8n
    BluefoxB
    Bluefox
    15
    1
    2.2k

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

Geplant Angeheftet Gesperrt Verschoben Tester
js-controller
1.0k Beiträge 48 Kommentatoren 313.5k Aufrufe 35 Watching
  • Älteste zuerst
  • Neuste zuerst
  • Meiste Stimmen
Antworten
  • In einem neuen Thema antworten
Anmelden zum Antworten
Dieses Thema wurde gelöscht. Nur Nutzer mit entsprechenden Rechten können es sehen.
  • Dr. BakteriusD 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.

    VIS.jpg

    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

    apollon77A Offline
    apollon77A Offline
    apollon77
    schrieb am zuletzt editiert von
    #89

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

    Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

    • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
    • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
    1 Antwort Letzte Antwort
    0
    • J 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
      

      apollon77A Offline
      apollon77A Offline
      apollon77
      schrieb am zuletzt editiert von
      #90

      @Jan1 Mist. Schaue ich mir an

      Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

      • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
      • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
      J 1 Antwort Letzte Antwort
      0
      • apollon77A apollon77

        @Jan1 Mist. Schaue ich mir an

        J Offline
        J Offline
        Jan1
        schrieb am zuletzt editiert von
        #91

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

        1 Antwort Letzte Antwort
        0
        • Dr. BakteriusD 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.

          VIS.jpg

          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

          opossumO Offline
          opossumO Offline
          opossum
          schrieb am zuletzt editiert von
          #92

          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:
          539defb3-b16c-4371-bcc7-4a8b0ed5f948-image.png

          Aber sie werden mir im Auswahldialog leider nicht angezeigt:
          fad89f14-af50-4933-9522-2223543c125d-image.png
          Irgend etwas ist noch nicht korrekt bei mir. Klicke ich auf den Uploadbutton, dann kommt bei mir folgendes:
          971d1d40-288b-4c57-b58f-6c10aa3d21f6-image.png
          Ich kann von dort auch hochladen, aber in der Auswahl sieht das dann so aus:
          c3650268-9d05-425c-b874-20496f3670a0-image.png
          Dabei stehen die Rechte der Dateien wie folgt:
          24626e76-ecd7-45ba-bc9f-abbb4da7a6a1-image.png
          Sorry, wenn ich nerve.
          Gruß
          Egbert

          https://schlepper-petersdorf.jimdofree.com/

          apollon77A 1 Antwort Letzte Antwort
          0
          • J 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
            

            apollon77A Offline
            apollon77A Offline
            apollon77
            schrieb am zuletzt editiert von
            #93

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

            Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

            • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
            • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
            1 Antwort Letzte Antwort
            0
            • opossumO 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:
              539defb3-b16c-4371-bcc7-4a8b0ed5f948-image.png

              Aber sie werden mir im Auswahldialog leider nicht angezeigt:
              fad89f14-af50-4933-9522-2223543c125d-image.png
              Irgend etwas ist noch nicht korrekt bei mir. Klicke ich auf den Uploadbutton, dann kommt bei mir folgendes:
              971d1d40-288b-4c57-b58f-6c10aa3d21f6-image.png
              Ich kann von dort auch hochladen, aber in der Auswahl sieht das dann so aus:
              c3650268-9d05-425c-b874-20496f3670a0-image.png
              Dabei stehen die Rechte der Dateien wie folgt:
              24626e76-ecd7-45ba-bc9f-abbb4da7a6a1-image.png
              Sorry, wenn ich nerve.
              Gruß
              Egbert

              apollon77A Offline
              apollon77A Offline
              apollon77
              schrieb am zuletzt editiert von
              #94

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

              Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

              • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
              • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
              opossumO 1 Antwort Letzte Antwort
              0
              • apollon77A apollon77

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

                opossumO Offline
                opossumO Offline
                opossum
                schrieb am zuletzt editiert von opossum
                #95

                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

                https://schlepper-petersdorf.jimdofree.com/

                1 Antwort Letzte Antwort
                0
                • J Jan1

                  @apollon77
                  Hier mal das Log wenn ich den BLE neustarte:

                  host.Beelink	2019-09-20 18:01:34.337	info	Restart compact group controller 1
                  host.Beelink	2019-09-20 18:01:34.337	error	Caught by controller[13]: at process._fatalException (internal/bootstrap/node.js:496:27)
                  host.Beelink	2019-09-20 18:01:34.337	error	Caught by controller[13]: at process.emit (events.js:203:15)
                  host.Beelink	2019-09-20 18:01:34.336	error	Caught by controller[13]: at process.on.err (/opt/iobroker/node_modules/iobroker.ble/build/main.js:382:17)
                  host.Beelink	2019-09-20 18:01:34.336	error	Caught by controller[13]: TypeError: Cannot read property 'error' of undefined
                  host.Beelink	2019-09-20 18:01:34.336	error	Caught by controller[13]: ^
                  host.Beelink	2019-09-20 18:01:34.336	error	Caught by controller[13]: adapter.log.error("unhandled exception:" + err.message);
                  host.Beelink	2019-09-20 18:01:34.336	error	Caught by controller[13]: /opt/iobroker/node_modules/iobroker.ble/build/main.js:382
                  host.Beelink	2019-09-20 18:01:34.336	error	Caught by controller[12]: at process._tickCallback (internal/process/next_tick.js:69:34)
                  host.Beelink	2019-09-20 18:01:34.336	error	Caught by controller[12]: at emitPromiseRejectionWarnings (internal/process/promises.js:119:20)
                  host.Beelink	2019-09-20 18:01:34.336	error	Caught by controller[12]: at process.emit (events.js:198:13)
                  host.Beelink	2019-09-20 18:01:34.336	error	Caught by controller[12]: at process.on.r (/opt/iobroker/node_modules/iobroker.ble/build/main.js:377:17)
                  host.Beelink	2019-09-20 18:01:34.335	error	Caught by controller[12]: TypeError: Cannot read property 'error' of undefined
                  host.Beelink	2019-09-20 18:01:34.335	error	Caught by controller[11]: at process._tickCallback (internal/process/next_tick.js:69:34)
                  host.Beelink	2019-09-20 18:01:34.335	error	Caught by controller[11]: at emitPromiseRejectionWarnings (internal/process/promises.js:119:20)
                  host.Beelink	2019-09-20 18:01:34.335	error	Caught by controller[11]: at process.emit (events.js:198:13)
                  host.Beelink	2019-09-20 18:01:34.335	error	Caught by controller[11]: at process.on.r (/opt/iobroker/node_modules/iobroker.ble/build/main.js:377:17)
                  host.Beelink	2019-09-20 18:01:34.335	error	Caught by controller[11]: TypeError: Cannot read property 'error' of undefined
                  host.Beelink	2019-09-20 18:01:34.335	error	Caught by controller[10]: at process._tickCallback (internal/process/next_tick.js:69:34)
                  host.Beelink	2019-09-20 18:01:34.335	error	Caught by controller[10]: at emitPromiseRejectionWarnings (internal/process/promises.js:119:20)
                  host.Beelink	2019-09-20 18:01:34.335	error	Caught by controller[10]: at process.emit (events.js:198:13)
                  host.Beelink	2019-09-20 18:01:34.335	error	Caught by controller[10]: at process.on.r (/opt/iobroker/node_modules/iobroker.ble/build/main.js:377:17)
                  host.Beelink	2019-09-20 18:01:34.334	error	Caught by controller[10]: TypeError: Cannot read property 'error' of undefined
                  host.Beelink	2019-09-20 18:01:34.334	error	Caught by controller[9]: at process._tickCallback (internal/process/next_tick.js:69:34)
                  host.Beelink	2019-09-20 18:01:34.334	error	Caught by controller[9]: at emitPromiseRejectionWarnings (internal/process/promises.js:119:20)
                  host.Beelink	2019-09-20 18:01:34.334	error	Caught by controller[9]: at process.emit (events.js:198:13)
                  host.Beelink	2019-09-20 18:01:34.334	error	Caught by controller[9]: at process.on.r (/opt/iobroker/node_modules/iobroker.ble/build/main.js:377:17)
                  host.Beelink	2019-09-20 18:01:34.334	error	Caught by controller[9]: TypeError: Cannot read property 'error' of undefined
                  host.Beelink	2019-09-20 18:01:34.334	error	Caught by controller[8]: at process._tickCallback (internal/process/next_tick.js:69:34)
                  host.Beelink	2019-09-20 18:01:34.334	error	Caught by controller[8]: at emitPromiseRejectionWarnings (internal/process/promises.js:119:20)
                  host.Beelink	2019-09-20 18:01:34.333	error	Caught by controller[8]: at process.emit (events.js:198:13)
                  host.Beelink	2019-09-20 18:01:34.333	error	Caught by controller[8]: at process.on.r (/opt/iobroker/node_modules/iobroker.ble/build/main.js:377:17)
                  host.Beelink	2019-09-20 18:01:34.333	error	Caught by controller[8]: TypeError: Cannot read property 'error' of undefined
                  host.Beelink	2019-09-20 18:01:34.333	error	Caught by controller[7]: at process._tickCallback (internal/process/next_tick.js:69:34)
                  host.Beelink	2019-09-20 18:01:34.333	error	Caught by controller[7]: at emitPromiseRejectionWarnings (internal/process/promises.js:119:20)
                  host.Beelink	2019-09-20 18:01:34.333	error	Caught by controller[7]: at process.emit (events.js:198:13)
                  host.Beelink	2019-09-20 18:01:34.333	error	Caught by controller[7]: at process.on.r (/opt/iobroker/node_modules/iobroker.ble/build/main.js:377:17)
                  host.Beelink	2019-09-20 18:01:34.333	error	Caught by controller[7]: TypeError: Cannot read property 'error' of undefined
                  host.Beelink	2019-09-20 18:01:34.332	error	Caught by controller[6]: at process._tickCallback (internal/process/next_tick.js:69:34)
                  host.Beelink	2019-09-20 18:01:34.332	error	Caught by controller[6]: at emitPromiseRejectionWarnings (internal/process/promises.js:119:20)
                  host.Beelink	2019-09-20 18:01:34.332	error	Caught by controller[6]: at process.emit (events.js:198:13)
                  host.Beelink	2019-09-20 18:01:34.332	error	Caught by controller[6]: at process.on.r (/opt/iobroker/node_modules/iobroker.ble/build/main.js:377:17)
                  host.Beelink	2019-09-20 18:01:34.332	error	Caught by controller[6]: TypeError: Cannot read property 'error' of undefined
                  host.Beelink	2019-09-20 18:01:34.332	error	Caught by controller[5]: at process._tickCallback (internal/process/next_tick.js:69:34)
                  host.Beelink	2019-09-20 18:01:34.332	error	Caught by controller[5]: at emitPromiseRejectionWarnings (internal/process/promises.js:119:20)
                  host.Beelink	2019-09-20 18:01:34.332	error	Caught by controller[5]: at process.emit (events.js:198:13)
                  host.Beelink	2019-09-20 18:01:34.332	error	Caught by controller[5]: at process.on.r (/opt/iobroker/node_modules/iobroker.ble/build/main.js:377:17)
                  host.Beelink	2019-09-20 18:01:34.331	error	Caught by controller[5]: TypeError: Cannot read property 'error' of undefined
                  host.Beelink	2019-09-20 18:01:34.331	error	Caught by controller[4]: at process._tickCallback (internal/process/next_tick.js:69:34)
                  host.Beelink	2019-09-20 18:01:34.331	error	Caught by controller[4]: at emitPromiseRejectionWarnings (internal/process/promises.js:119:20)
                  host.Beelink	2019-09-20 18:01:34.331	error	Caught by controller[4]: at process.emit (events.js:198:13)
                  host.Beelink	2019-09-20 18:01:34.331	error	Caught by controller[4]: at process.on.r (/opt/iobroker/node_modules/iobroker.ble/build/main.js:377:17)
                  host.Beelink	2019-09-20 18:01:34.331	error	Caught by controller[4]: TypeError: Cannot read property 'error' of undefined
                  host.Beelink	2019-09-20 18:01:34.331	error	Caught by controller[3]: at process._tickCallback (internal/process/next_tick.js:69:34)
                  host.Beelink	2019-09-20 18:01:34.331	error	Caught by controller[3]: at emitPromiseRejectionWarnings (internal/process/promises.js:119:20)
                  host.Beelink	2019-09-20 18:01:34.330	error	Caught by controller[3]: at process.emit (events.js:198:13)
                  host.Beelink	2019-09-20 18:01:34.330	error	Caught by controller[3]: at process.on.r (/opt/iobroker/node_modules/iobroker.ble/build/main.js:377:17)
                  host.Beelink	2019-09-20 18:01:34.330	error	Caught by controller[3]: TypeError: Cannot read property 'error' of undefined
                  host.Beelink	2019-09-20 18:01:34.330	error	Caught by controller[2]: at process._tickCallback (internal/process/next_tick.js:69:34)
                  host.Beelink	2019-09-20 18:01:34.330	error	Caught by controller[2]: at emitPromiseRejectionWarnings (internal/process/promises.js:119:20)
                  host.Beelink	2019-09-20 18:01:34.330	error	Caught by controller[2]: at process.emit (events.js:198:13)
                  host.Beelink	2019-09-20 18:01:34.330	error	Caught by controller[2]: at process.on.r (/opt/iobroker/node_modules/iobroker.ble/build/main.js:377:17)
                  host.Beelink	2019-09-20 18:01:34.330	error	Caught by controller[2]: TypeError: Cannot read property 'error' of undefined
                  host.Beelink	2019-09-20 18:01:34.330	error	Caught by controller[1]: at process._tickCallback (internal/process/next_tick.js:69:34)
                  host.Beelink	2019-09-20 18:01:34.329	error	Caught by controller[1]: at emitPromiseRejectionWarnings (internal/process/promises.js:119:20)
                  host.Beelink	2019-09-20 18:01:34.329	error	Caught by controller[1]: at process.emit (events.js:198:13)
                  host.Beelink	2019-09-20 18:01:34.329	error	Caught by controller[1]: at process.on.r (/opt/iobroker/node_modules/iobroker.ble/build/main.js:377:17)
                  host.Beelink	2019-09-20 18:01:34.329	error	Caught by controller[1]: TypeError: Cannot read property 'error' of undefined
                  iqontrol.0	2019-09-20 18:01:34.188	error	(COMPACT) uncaught exception: Cannot read property 'error' of undefined
                  alexa2.0	2019-09-20 18:01:34.185	warn	(COMPACT) Exception: TypeError: Cannot read property 'error' of undefined
                  info.0	2019-09-20 18:01:34.183	error	(COMPACT) uncaught exception: Cannot read property 'error' of undefined
                  fritzdect.0	2019-09-20 18:01:34.181	error	(COMPACT) uncaught exception: Cannot read property 'error' of undefined
                  javascript.0	2019-09-20 18:01:34.169	error	(COMPACT) uncaught exception: Cannot read property 'error' of undefined
                  telegram.0	2019-09-20 18:01:34.167	error	(COMPACT) uncaught exception: Cannot read property 'error' of undefined
                  tankerkoenig.0	2019-09-20 18:01:34.165	error	(COMPACT) uncaught exception: Cannot read property 'error' of undefined
                  harmony.0	2019-09-20 18:01:34.162	error	(COMPACT) uncaught exception: Cannot read property 'error' of undefined
                  history.0	2019-09-20 18:01:34.155	error	(COMPACT) uncaught exception: Cannot read property 'error' of undefined
                  iot.0	2019-09-20 18:01:34.152	error	(COMPACT) uncaught exception: Cannot read property 'error' of undefined
                  backitup.0	2019-09-20 18:01:34.150	error	(COMPACT) uncaught exception: Cannot read property 'error' of undefined
                  admin.0	2019-09-20 18:01:34.138	error	(COMPACT) uncaught exception: Cannot read property 'error' of undefined
                  ble	2019-09-20 18:01:33.387	warn	(COMPACT) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                  ble	2019-09-20 18:01:33.386	error	(COMPACT) ble.0 already running
                  host.Beelink.compactgroup1	2019-09-20 18:01:33.361	error	Cannot start ble.0 in compact mode: Cannot read property 'on' of undefined
                  host.Beelink	2019-09-20 18:01:33.351	info	stopInstance system.adapter.ble.0
                  host.Beelink	2019-09-20 18:01:33.350	info	object change system.adapter.ble.0 (from: system.adapter.admin.0)
                  host.Beelink.compactgroup1	2019-09-20 18:01:41.391	info	instance system.adapter.backitup.0 started in COMPACT mode
                  

                  Dann noch die comact mode Übersicht:

                  root@Beelink:~# 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 disabled
                  + 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
                  
                  

                  AlCalzoneA Offline
                  AlCalzoneA Offline
                  AlCalzone
                  Developer
                  schrieb am zuletzt editiert von
                  #96

                  @Jan1 Kannst du bitte BLE v0.9.1 probieren?

                  Warum `sudo` böse ist: https://forum.iobroker.net/post/17109

                  apollon77A 1 Antwort Letzte Antwort
                  0
                  • AlCalzoneA AlCalzone

                    @Jan1 Kannst du bitte BLE v0.9.1 probieren?

                    apollon77A Offline
                    apollon77A Offline
                    apollon77
                    schrieb am zuletzt editiert von
                    #97

                    @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

                    Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

                    • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
                    • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
                    1 Antwort Letzte Antwort
                    0
                    • apollon77A Offline
                      apollon77A Offline
                      apollon77
                      schrieb am zuletzt editiert von
                      #98

                      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

                      Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

                      • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
                      • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
                      J E 2 Antworten Letzte Antwort
                      2
                      • apollon77A 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
                        J Offline
                        J Offline
                        Jan1
                        schrieb am zuletzt editiert von Jan1
                        #99

                        @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.

                        apollon77A 1 Antwort Letzte Antwort
                        0
                        • J 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.

                          apollon77A Offline
                          apollon77A Offline
                          apollon77
                          schrieb am zuletzt editiert von
                          #100

                          @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

                          Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

                          • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
                          • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
                          J 1 Antwort Letzte Antwort
                          0
                          • apollon77A 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

                            J Offline
                            J Offline
                            Jan1
                            schrieb am zuletzt editiert von
                            #101

                            @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.

                            apollon77A 1 Antwort Letzte Antwort
                            0
                            • J 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.

                              apollon77A Offline
                              apollon77A Offline
                              apollon77
                              schrieb am zuletzt editiert von
                              #102

                              @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.

                              Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

                              • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
                              • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
                              J 1 Antwort Letzte Antwort
                              0
                              • apollon77A 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.

                                J Offline
                                J Offline
                                Jan1
                                schrieb am zuletzt editiert von Jan1
                                #103

                                @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
                                
                                

                                1 Antwort Letzte Antwort
                                0
                                • apollon77A Offline
                                  apollon77A Offline
                                  apollon77
                                  schrieb am zuletzt editiert von
                                  #104

                                  Ok, sehe schon :-) alles ok. Ich fixe noch was ... grrrr :-)

                                  Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

                                  • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
                                  • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
                                  1 Antwort Letzte Antwort
                                  0
                                  • apollon77A apollon77

                                    @SBorg den git clone Fehler hatte Arteck auch mal plötzlich. Ursache muss irgendwo bei npm liegen. Aber gut zu wissen das das andere Kommando tat.

                                    Node-red release ich dann heute Abend.

                                    SBorgS Offline
                                    SBorgS Offline
                                    SBorg
                                    Forum Testing Most Active
                                    schrieb am zuletzt editiert von
                                    #105

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

                                    @SBorg den git clone Fehler hatte Arteck auch mal plötzlich. Ursache muss irgendwo bei npm liegen...

                                    Zumindest habe ich ihn jetzt permanent. Ohne "sudo -H..." lässt sich nichts mehr installieren. Die Fehlermeldung seitens npm scheint mir aber auch irreführend. Ich habe ja alle Rechte im tmp-Verzeichnis und spaßeshalber ein chmod 777 darauf bringt keinerlei Besserung. Ev. bringt ja ein neues npm-Release Besserung ;)

                                    LG SBorg ( SBorg auf GitHub)
                                    Projekte: Lebensmittelwarnung.de | WLAN-Wetterstation | PimpMyStation

                                    AlCalzoneA 1 Antwort Letzte Antwort
                                    0
                                    • C Offline
                                      C Offline
                                      CADYTA
                                      schrieb am zuletzt editiert von Stabilostick
                                      #106

                                      Auf Systemen, die mit dem neuen Windows Installer eingerichtet wurden, darf der js-controller nicht mir npm aktualisiert werden. Es wird eine neue Version des Windows Installers geben, die das Update des js-controllers mit wenigen Mausklicks ermöglicht. Wir updaten dazu hier im Thread.

                                      [Edit: Defekte Links entfernt. 24.09.19, stabilostick]

                                      1 Antwort Letzte Antwort
                                      0
                                      • SBorgS SBorg

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

                                        @SBorg den git clone Fehler hatte Arteck auch mal plötzlich. Ursache muss irgendwo bei npm liegen...

                                        Zumindest habe ich ihn jetzt permanent. Ohne "sudo -H..." lässt sich nichts mehr installieren. Die Fehlermeldung seitens npm scheint mir aber auch irreführend. Ich habe ja alle Rechte im tmp-Verzeichnis und spaßeshalber ein chmod 777 darauf bringt keinerlei Besserung. Ev. bringt ja ein neues npm-Release Besserung ;)

                                        AlCalzoneA Offline
                                        AlCalzoneA Offline
                                        AlCalzone
                                        Developer
                                        schrieb am zuletzt editiert von
                                        #107

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

                                        Ohne "sudo -H..." lässt sich nichts mehr installieren

                                        Mal den Fixer ausgeführt?

                                        Warum `sudo` böse ist: https://forum.iobroker.net/post/17109

                                        1 Antwort Letzte Antwort
                                        0
                                        • SBorgS Offline
                                          SBorgS Offline
                                          SBorg
                                          Forum Testing Most Active
                                          schrieb am zuletzt editiert von
                                          #108

                                          @AlCalzone Mehrmals, dürfte aber nix bringen, da NPM meckert, dass er im /[User-Verzeichnis]/.npm/_cacache/tmp/git-clone... das Verzeichnis zum DL nicht anlegen kann. Mit NPM 6.4.1 ging es noch, erst mit dem Update auf 6.11.3 trat es bei mir auf. NPM selbst verriet ja noch, dass es bei älteren Versionen durchaus zu Fehlern in den Userrechten kam. Der vorgeschlagene Fix fruchtet aber auch nicht.
                                          Ist zumindest kein Problem vom Broker/JS-Controller.

                                          LG SBorg ( SBorg auf GitHub)
                                          Projekte: Lebensmittelwarnung.de | WLAN-Wetterstation | PimpMyStation

                                          AlCalzoneA 2 Antworten Letzte Antwort
                                          0
                                          Antworten
                                          • In einem neuen Thema antworten
                                          Anmelden zum Antworten
                                          • Älteste zuerst
                                          • Neuste zuerst
                                          • Meiste Stimmen


                                          Support us

                                          ioBroker
                                          Community Adapters
                                          Donate

                                          392

                                          Online

                                          32.4k

                                          Benutzer

                                          81.4k

                                          Themen

                                          1.3m

                                          Beiträge
                                          Community
                                          Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
                                          ioBroker Community 2014-2025
                                          logo
                                          • Anmelden

                                          • Du hast noch kein Konto? Registrieren

                                          • Anmelden oder registrieren, um zu suchen
                                          • Erster Beitrag
                                            Letzter Beitrag
                                          0
                                          • Home
                                          • Aktuell
                                          • Tags
                                          • Ungelesen 0
                                          • Kategorien
                                          • Unreplied
                                          • Beliebt
                                          • GitHub
                                          • Docu
                                          • Hilfe