Skip to content
  • Home
  • Recent
  • Tags
  • 0 Unread 0
  • Categories
  • Unreplied
  • Popular
  • 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
  • Default (No Skin)
  • No Skin
Collapse
ioBroker Logo

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

NEWS

  • Weihnachtsangebot 2025! 🎄
    BluefoxB
    Bluefox
    22
    1
    1.2k
  • UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?
    apollon77A
    apollon77
    48
    3
    9.2k
  • Monatsrückblick – September 2025
    BluefoxB
    Bluefox
    14
    1
    2.5k

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

Scheduled Pinned Locked Moved Tester
js-controller
1.0k Posts 48 Posters 322.9k Views 35 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • D darkiop

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

    Danke für die Tests!!

    Gern!

    • Testfall 3 Bitte mit der neuen 2.0.31 auf Github nochmal testen

    Da stimmt was nicht:

    ┬─[darkiop@odin:~]─[13:35:02]
╰─>$ docker stop iobroker-redis
iobroker-redis
┬─[darkiop@odin:~]─[13:41:53]
╰─>$ docker start iobroker-redis
iobroker-redis

    Log Master:

    2019-10-15 13:41:48.364  - error: scenes.0 (1492) connect ETIMEDOUT
2019-10-15 13:41:48.366  - error: pi-hole.0 (1228) connect ETIMEDOUT
2019-10-15 13:41:48.368  - error: harmony.0 (388) connect ETIMEDOUT
2019-10-15 13:41:48.368  - error: simple-api.0 (1695) connect ETIMEDOUT
2019-10-15 13:41:48.372  - error: javascript.1 (1068) connect ETIMEDOUT
2019-10-15 13:41:48.372  - error: sql.0 (1819) connect ETIMEDOUT
2019-10-15 13:41:48.372  - error: telegram.0 (2364) connect ETIMEDOUT
2019-10-15 13:41:48.375  - error: host.iobroker-master connect ETIMEDOUT
2019-10-15 13:41:48.379  - error: hm-rega.0 (403) connect ETIMEDOUT
2019-10-15 13:41:48.379  - error: hs100.0 (480) connect ETIMEDOUT
2019-10-15 13:41:48.379  - error: tr-064-community.0 (2710) connect ETIMEDOUT
2019-10-15 13:41:48.385  - error: stiebel-isg.0 (2029) connect ETIMEDOUT
2019-10-15 13:41:48.385  - error: moma.0 (1162) connect ETIMEDOUT
2019-10-15 13:41:48.390  - error: ping.0 (1378) connect ETIMEDOUT
2019-10-15 13:41:48.391  - error: hm-rpc.1 (426) connect ETIMEDOUT
2019-10-15 13:41:48.392  - error: backitup.0 (457) connect ETIMEDOUT
2019-10-15 13:41:48.393  - error: hm-rpc.2 (450) connect ETIMEDOUT
2019-10-15 13:41:48.393  - error: javascript.0 (808) connect ETIMEDOUT
2019-10-15 13:41:48.399  - error: mercedesme.0 (1108) connect ETIMEDOUT
2019-10-15 13:41:48.407  - error: info.0 (789) connect ETIMEDOUT
2019-10-15 13:42:00.004  - warn: host.iobroker-master instance system.adapter.daswetter.0 already running with pid 11372
2019-10-15 13:42:03.215  - info: host.iobroker-master instance system.adapter.daswetter.0 terminated with code 0 (NO_ERROR)
2019-10-15 13:42:04.501  - debug: harmony.0 (388) system.adapter.admin.0: logging true
2019-10-15 13:42:04.532  - debug: harmony.0 (388) States connected to redis: 192.168.1.86:6379
2019-10-15 13:42:20.048  - error: admin.0 (419) uncaught exception: Maximum call stack size exceeded
2019-10-15 13:42:20.052  - error: admin.0 (419) RangeError: Maximum call stack size exceeded
    at Sender.frameAndSend (/opt/iobroker/node_modules/ws/lib/Sender.js:166:14)
    at /opt/iobroker/node_modules/ws/lib/Sender.js:126:12
    at Sender.applyExtensions (/opt/iobroker/node_modules/ws/lib/Sender.js:287:5)
    at /opt/iobroker/node_modules/ws/lib/Sender.js:120:10
    at Sender.flush (/opt/iobroker/node_modules/ws/lib/Sender.js:268:3)
    at /opt/iobroker/node_modules/ws/lib/Sender.js:270:10
    at /opt/iobroker/node_modules/ws/lib/Sender.js:127:7
    at Sender.applyExtensions (/opt/iobroker/node_modules/ws/lib/Sender.js:287:5)
    at /opt/iobroker/node_modules/ws/lib/Sender.js:120:10
    at Sender.flush (/opt/iobroker/node_modules/ws/lib/Sender.js:268:3)
2019-10-15 13:42:20.318  - error: host.iobroker-master Caught by controller[0]: RangeError: Maximum call stack size exceeded
2019-10-15 13:42:20.320  - error: host.iobroker-master Caught by controller[0]:     at Sender.frameAndSend (/opt/iobroker/node_modules/ws/lib/Sender.js:166:14)
2019-10-15 13:42:20.321  - error: host.iobroker-master Caught by controller[0]:     at /opt/iobroker/node_modules/ws/lib/Sender.js:126:12
2019-10-15 13:42:20.323  - error: host.iobroker-master Caught by controller[0]:     at Sender.applyExtensions (/opt/iobroker/node_modules/ws/lib/Sender.js:287:5)
2019-10-15 13:42:20.324  - error: host.iobroker-master Caught by controller[0]:     at /opt/iobroker/node_modules/ws/lib/Sender.js:120:10
2019-10-15 13:42:20.325  - error: host.iobroker-master Caught by controller[0]:     at Sender.flush (/opt/iobroker/node_modules/ws/lib/Sender.js:268:3)
2019-10-15 13:42:20.326  - error: host.iobroker-master Caught by controller[0]:     at /opt/iobroker/node_modules/ws/lib/Sender.js:270:10
2019-10-15 13:42:20.327  - error: host.iobroker-master Caught by controller[0]:     at /opt/iobroker/node_modules/ws/lib/Sender.js:127:7
2019-10-15 13:42:20.328  - error: host.iobroker-master Caught by controller[0]:     at Sender.applyExtensions (/opt/iobroker/node_modules/ws/lib/Sender.js:287:5)
2019-10-15 13:42:20.328  - error: host.iobroker-master Caught by controller[0]:     at /opt/iobroker/node_modules/ws/lib/Sender.js:120:10
2019-10-15 13:42:20.329  - error: host.iobroker-master Caught by controller[0]:     at Sender.flush (/opt/iobroker/node_modules/ws/lib/Sender.js:268:3)
2019-10-15 13:42:20.331  - info: host.iobroker-master instance system.adapter.admin.0 terminated with code 0 (NO_ERROR)
2019-10-15 13:42:20.333  - info: host.iobroker-master Restart adapter system.adapter.admin.0 because enabled
2019-10-15 13:42:20.340  - debug: harmony.0 (388) system.adapter.admin.0: logging false
2019-10-15 13:42:49.810  - info: tankerkoenig.0 (2155) Reading data from tankerkoenig ...
2019-10-15 13:42:50.388  - info: host.iobroker-master instance system.adapter.admin.0 started with pid 27743
2019-10-15 13:43:00.021  - info: host.iobroker-master instance system.adapter.daswetter.0 started with pid 28216
2019-10-15 13:43:09.649  - info: host.iobroker-master instance system.adapter.daswetter.0 terminated with code 0 (NO_ERROR)

    Keine neue States da:

    8c13e0ad-b485-4464-b5b5-2fb9bf9a6f8e-grafik.png

    apollon77A Offline
    apollon77A Offline
    apollon77
    wrote on last edited by
    #787

    @darkiop in dem Fall ist Admin gestorben weil sich irgendwie Dinge aufgestaut haben und Admin restartet. Ggf fehlen dadurch Daten? Lad im browser mal neu. Jetzt fehlende States da?

    Ansonsten hat sich der iobroker aber wieder gefangen mit der Version oder?!

    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 Reply Last reply
    0
    • D darkiop

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

      Danke für die Tests!!

      Gern!

      • Testfall 3 Bitte mit der neuen 2.0.31 auf Github nochmal testen

      Da stimmt was nicht:

      ┬─[darkiop@odin:~]─[13:35:02]
╰─>$ docker stop iobroker-redis
iobroker-redis
┬─[darkiop@odin:~]─[13:41:53]
╰─>$ docker start iobroker-redis
iobroker-redis

      Log Master:

      2019-10-15 13:41:48.364  - error: scenes.0 (1492) connect ETIMEDOUT
2019-10-15 13:41:48.366  - error: pi-hole.0 (1228) connect ETIMEDOUT
2019-10-15 13:41:48.368  - error: harmony.0 (388) connect ETIMEDOUT
2019-10-15 13:41:48.368  - error: simple-api.0 (1695) connect ETIMEDOUT
2019-10-15 13:41:48.372  - error: javascript.1 (1068) connect ETIMEDOUT
2019-10-15 13:41:48.372  - error: sql.0 (1819) connect ETIMEDOUT
2019-10-15 13:41:48.372  - error: telegram.0 (2364) connect ETIMEDOUT
2019-10-15 13:41:48.375  - error: host.iobroker-master connect ETIMEDOUT
2019-10-15 13:41:48.379  - error: hm-rega.0 (403) connect ETIMEDOUT
2019-10-15 13:41:48.379  - error: hs100.0 (480) connect ETIMEDOUT
2019-10-15 13:41:48.379  - error: tr-064-community.0 (2710) connect ETIMEDOUT
2019-10-15 13:41:48.385  - error: stiebel-isg.0 (2029) connect ETIMEDOUT
2019-10-15 13:41:48.385  - error: moma.0 (1162) connect ETIMEDOUT
2019-10-15 13:41:48.390  - error: ping.0 (1378) connect ETIMEDOUT
2019-10-15 13:41:48.391  - error: hm-rpc.1 (426) connect ETIMEDOUT
2019-10-15 13:41:48.392  - error: backitup.0 (457) connect ETIMEDOUT
2019-10-15 13:41:48.393  - error: hm-rpc.2 (450) connect ETIMEDOUT
2019-10-15 13:41:48.393  - error: javascript.0 (808) connect ETIMEDOUT
2019-10-15 13:41:48.399  - error: mercedesme.0 (1108) connect ETIMEDOUT
2019-10-15 13:41:48.407  - error: info.0 (789) connect ETIMEDOUT
2019-10-15 13:42:00.004  - warn: host.iobroker-master instance system.adapter.daswetter.0 already running with pid 11372
2019-10-15 13:42:03.215  - info: host.iobroker-master instance system.adapter.daswetter.0 terminated with code 0 (NO_ERROR)
2019-10-15 13:42:04.501  - debug: harmony.0 (388) system.adapter.admin.0: logging true
2019-10-15 13:42:04.532  - debug: harmony.0 (388) States connected to redis: 192.168.1.86:6379
2019-10-15 13:42:20.048  - error: admin.0 (419) uncaught exception: Maximum call stack size exceeded
2019-10-15 13:42:20.052  - error: admin.0 (419) RangeError: Maximum call stack size exceeded
    at Sender.frameAndSend (/opt/iobroker/node_modules/ws/lib/Sender.js:166:14)
    at /opt/iobroker/node_modules/ws/lib/Sender.js:126:12
    at Sender.applyExtensions (/opt/iobroker/node_modules/ws/lib/Sender.js:287:5)
    at /opt/iobroker/node_modules/ws/lib/Sender.js:120:10
    at Sender.flush (/opt/iobroker/node_modules/ws/lib/Sender.js:268:3)
    at /opt/iobroker/node_modules/ws/lib/Sender.js:270:10
    at /opt/iobroker/node_modules/ws/lib/Sender.js:127:7
    at Sender.applyExtensions (/opt/iobroker/node_modules/ws/lib/Sender.js:287:5)
    at /opt/iobroker/node_modules/ws/lib/Sender.js:120:10
    at Sender.flush (/opt/iobroker/node_modules/ws/lib/Sender.js:268:3)
2019-10-15 13:42:20.318  - error: host.iobroker-master Caught by controller[0]: RangeError: Maximum call stack size exceeded
2019-10-15 13:42:20.320  - error: host.iobroker-master Caught by controller[0]:     at Sender.frameAndSend (/opt/iobroker/node_modules/ws/lib/Sender.js:166:14)
2019-10-15 13:42:20.321  - error: host.iobroker-master Caught by controller[0]:     at /opt/iobroker/node_modules/ws/lib/Sender.js:126:12
2019-10-15 13:42:20.323  - error: host.iobroker-master Caught by controller[0]:     at Sender.applyExtensions (/opt/iobroker/node_modules/ws/lib/Sender.js:287:5)
2019-10-15 13:42:20.324  - error: host.iobroker-master Caught by controller[0]:     at /opt/iobroker/node_modules/ws/lib/Sender.js:120:10
2019-10-15 13:42:20.325  - error: host.iobroker-master Caught by controller[0]:     at Sender.flush (/opt/iobroker/node_modules/ws/lib/Sender.js:268:3)
2019-10-15 13:42:20.326  - error: host.iobroker-master Caught by controller[0]:     at /opt/iobroker/node_modules/ws/lib/Sender.js:270:10
2019-10-15 13:42:20.327  - error: host.iobroker-master Caught by controller[0]:     at /opt/iobroker/node_modules/ws/lib/Sender.js:127:7
2019-10-15 13:42:20.328  - error: host.iobroker-master Caught by controller[0]:     at Sender.applyExtensions (/opt/iobroker/node_modules/ws/lib/Sender.js:287:5)
2019-10-15 13:42:20.328  - error: host.iobroker-master Caught by controller[0]:     at /opt/iobroker/node_modules/ws/lib/Sender.js:120:10
2019-10-15 13:42:20.329  - error: host.iobroker-master Caught by controller[0]:     at Sender.flush (/opt/iobroker/node_modules/ws/lib/Sender.js:268:3)
2019-10-15 13:42:20.331  - info: host.iobroker-master instance system.adapter.admin.0 terminated with code 0 (NO_ERROR)
2019-10-15 13:42:20.333  - info: host.iobroker-master Restart adapter system.adapter.admin.0 because enabled
2019-10-15 13:42:20.340  - debug: harmony.0 (388) system.adapter.admin.0: logging false
2019-10-15 13:42:49.810  - info: tankerkoenig.0 (2155) Reading data from tankerkoenig ...
2019-10-15 13:42:50.388  - info: host.iobroker-master instance system.adapter.admin.0 started with pid 27743
2019-10-15 13:43:00.021  - info: host.iobroker-master instance system.adapter.daswetter.0 started with pid 28216
2019-10-15 13:43:09.649  - info: host.iobroker-master instance system.adapter.daswetter.0 terminated with code 0 (NO_ERROR)

      Keine neue States da:

      8c13e0ad-b485-4464-b5b5-2fb9bf9a6f8e-grafik.png

      apollon77A Offline
      apollon77A Offline
      apollon77
      wrote on last edited by
      #788

      @darkiop Aahhh noch eine Frage: du hast nur States im redis, korrekt?

      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
      D 1 Reply Last reply
      0
      • D Offline
        D Offline
        darkiop
        Most Active
        wrote on last edited by darkiop
        #789

        Ok, zweiter Test - jetzt ohne den admin.0 crash ....

        der Master ist wieder auf den Beinen, der Slave hat es aber nicht geschaft. stop/start aufm Slave und er ist wieder verbunden.

        c96f9e81-1b16-4465-afaa-d74b44acdc4c-grafik.png

        Puffert der controller auch Logs? Die 3 hier sind eigentlich entstanden während redis weg war, geschrieben wurden sie nach dem redis wieder da war:

        2019-10-15 14:00:00.786  - info: javascript.0 (618) script.js.PRODUKTIV.Beleuchtung.01_Bewegungsmelder_Flur: +++ Bewegung im Flur. Helligkeitsschwelle bei < 10 | Aktuelle Helligkeit: 31.8 | Licht wird nicht geschaltet. +++
2019-10-15 14:00:01.180  - info: javascript.0 (618) script.js.PRODUKTIV.Beleuchtung.01_Bewegungsmelder_Flur: +++ Bewegung im Flur. Helligkeitsschwelle bei < 10 | Aktuelle Helligkeit: 32.6 | Licht wird nicht geschaltet. +++
2019-10-15 14:00:01.523  - info: javascript.0 (618) script.js.PRODUKTIV.Beleuchtung.01_Bewegungsmelder_Flur: +++ Bewegung im Flur. Helligkeitsschwelle bei < 10 | Aktuelle Helligkeit: 32.6 | Licht wird nicht geschaltet. +++

        Edit:

        So lange war redis weg:

        d57fbaeb-9e0a-49d0-bf9d-53f79fde46ad-grafik.png

        Proxmox-ioBroker-Redis-HA Doku: https://forum.iobroker.net/topic/47478/dokumentation-einer-proxmox-iobroker-redis-ha-umgebung

        apollon77A 1 Reply Last reply
        0
        • apollon77A apollon77

          @darkiop Aahhh noch eine Frage: du hast nur States im redis, korrekt?

          D Offline
          D Offline
          darkiop
          Most Active
          wrote on last edited by
          #790

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

          Aahhh noch eine Frage: du hast nur States im redis, korrekt?

          Ja.

          Proxmox-ioBroker-Redis-HA Doku: https://forum.iobroker.net/topic/47478/dokumentation-einer-proxmox-iobroker-redis-ha-umgebung

          1 Reply Last reply
          0
          • apollon77A apollon77

            @smartboart mehr log bitte

            smartboartS Offline
            smartboartS Offline
            smartboart
            wrote on last edited by
            #791

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

            @smartboart mehr log bitte

            gerne


            2019-10-14 19:36:28.810 - info: host.ioBroker-Rock Update repository "latest" under "http://download.iobroker.net/sources-dist-latest.json"
            2019-10-14 19:37:21.257 - info: host.ioBroker-Rock iobroker upgrade statistics
            2019-10-14 19:37:23.968 - info: host.ioBroker-Rock iobroker Update statistics from @0.2.0 to @0.2.2
            2019-10-14 19:37:25.117 - info: host.ioBroker-Rock iobroker NPM version: 6.9.0npm install iobroker.statistics@0.2.2 --loglevel error --production --save --prefix "/opt/iobroker" (System call)
            2019-10-14 19:39:04.319 - info: host.ioBroker-Rock iobroker In file included from ../node_modules/nan/nan.h:82:0, from ../src/bufferutil.cc:16:../node_modules/nan/nan_new.h: In function ‘v8::Local NanIntern::To(v8::Handle) [with T = v8::Integer; v8::Handle = v8::Local]’:../node_modules/nan/nan_new.h:29:66: warning: ‘v8::Local v8::Value::ToInteger() const’ is deprecated: Use maybe version [-Wdeprecated-declarations] To(v8::Handle i) { return i->ToInteger(); } ^
            2019-10-14 19:39:04.321 - info: host.ioBroker-Rock iobroker In file included from ../src/bufferutil.cc:7:0:/home/iobroker/.node-gyp/10.16.3/include/node/v8.h:10052:16: note: declared here Local Value::ToInteger() const { ^In file included from ../node_modules/nan/nan.h:82:0, from ../src/bufferutil.cc:16:../node_modules/nan/nan_new.h: In function ‘v8::Local NanIntern::To(v8::Handle) [with T = v8::Int32; v8::Handle = v8::Local]’:../node_modules/nan/nan_new.h:34:64: error: no matching function for call to ‘v8::Integer::ToInt32()’ To(v8::Handle i) { return i->ToInt32(); } ^In file included from ../src/bufferutil.cc:7:0:/home/iobroker/.node-gyp/10.16.3/include/node/v8.h:2437:43: note: candidate: v8::MaybeLocal v8::Value::ToInt32(v8::Local) const V8_WARN_UNUSED_RESULT MaybeLocal ToInt32(Local context) const; ^/home/iobroker/.node-gyp/10.16.3/include/node/v8.h:2437:43: note: candidate expects 1 argument, 0 providedIn file included from /home/iobroker/.node-gyp/10.16.3/include/node/v8.h:26:0, from ../src/bufferutil.cc:7:/home/iobroker/.node-gyp/10.16.3/include/node/v8.h:2450:30: note: candidate: v8::Local v8::Value::ToInt32(v8::Isolate*) const Local ToInt32(Isolate* isolate) const); ^/home/iobroker/.node-gyp/10.16.3/include/node/v8config.h:324:3: note: in definition of macro ‘V8_DEPRECATED’ declarator attribute((deprecated(message))) ^~~~~~~~
            2019-10-14 19:39:04.324 - info: host.ioBroker-Rock iobroker /home/iobroker/.node-gyp/10.16.3/include/node/v8.h:2450:30: note: candidate expects 1 argument, 0 provided Local ToInt32(Isolate* isolate) const); ^/home/iobroker/.node-gyp/10.16.3/include/node/v8config.h:324:3: note: in definition of macro ‘V8_DEPRECATED’ declarator attribute((deprecated(message))) ^~~~~~~~~~
            2019-10-14 19:39:04.327 - info: host.ioBroker-Rock iobroker In file included from ../node_modules/nan/nan.h:82:0, from ../src/bufferutil.cc:16:../node_modules/nan/nan_new.h: In function ‘v8::Local NanIntern::To(v8::Handle) [with T = v8::Uint32; v8::Handle = v8::Local]’:../node_modules/nan/nan_new.h:39:65: error: no matching function for call to ‘v8::Integer::ToUint32()’ To(v8::Handle i) { return i->ToUint32(); } ^In file included from ../src/bufferutil.cc:7:0:/home/iobroker/.node-gyp/10.16.3/include/node/v8.h:2435:44: note: candidate: v8::MaybeLocal v8::Value::ToUint32(v8::Local) const V8_WARN_UNUSED_RESULT MaybeLocal ToUint32( ^~/home/iobroker/.node-gyp/10.16.3/include/node/v8.h:2435:44: note: candidate expects 1 argument, 0 provided
            2019-10-14 19:39:04.349 - info: host.ioBroker-Rock iobroker In file included from ../node_modules/nan/nan_new.h:189:0, from ../node_modules/nan/nan.h:82, from ../src/bufferutil.cc:16:../node_modules/nan/nan_implementation_12_inl.h: In static member function ‘static NanIntern::FactoryBase::return_t NanIntern::Factory::New(bool)’:../node_modules/nan/nan_implementation_12_inl.h:49:38: error: no matching function for call to ‘v8::BooleanObject::New(bool&)’ return v8::BooleanObject::New(value).As(); ^
            2019-10-14 19:39:04.352 - info: host.ioBroker-Rock iobroker In file included from ../src/bufferutil.cc:7:0:/home/iobroker/.node-gyp/10.16.3/include/node/v8.h:5035:23: note: candidate: static v8::Local v8::BooleanObject::New(v8::Isolate*, bool) static Local New(Isolate* isolate, bool value); ^            /home/iobroker/.node-gyp/10.16.3/include/node/v8.h:5035:23: note: candidate expects 2 arguments, 1 providedIn file included from ../node_modules/nan/nan_new.h:189:0, from ../node_modules/nan/nan.h:82, from ../src/bufferutil.cc:16:../node_modules/nan/nan_implementation_12_inl.h:49:60: error: expected primary-expression before ‘>’ token return v8::BooleanObject::New(value).As(); ^../node_modules/nan/nan_implementation_12_inl.h:49:62: error: expected primary-expression before ‘)’ token return v8::BooleanObject::New(value).As(); ^
            2019-10-14 19:39:04.371 - info: host.ioBroker-Rock iobroker ../node_modules/nan/nan_implementation_12_inl.h: In static member function ‘static NanIntern::FactoryBase::return_t NanIntern::Factory::New(v8::Handle, v8::RegExp::Flags)’:../node_modules/nan/nan_implementation_12_inl.h:158:40: warning: ‘static v8::Local v8::RegExp::New(v8::Local, v8::RegExp::Flags)’ is deprecated: Use maybe version [-Wdeprecated-declarations] return v8::RegExp::New(pattern, flags); ^
            2019-10-14 19:39:04.373 - info: host.ioBroker-Rock iobroker In file included from /home/iobroker/.node-gyp/10.16.3/include/node/v8.h:26:0, from ../src/bufferutil.cc:7:/home/iobroker/.node-gyp/10.16.3/include/node/v8.h:5110:38: note: declared here Local New(Local pattern, Flags flags)); ^/home/iobroker/.node-gyp/10.16.3/include/node/v8config.h:324:3: note: in definition of macro ‘V8_DEPRECATED’ declarator attribute((deprecated(message))) ^            ~~~~~
            2019-10-14 19:39:04.378 - info: host.ioBroker-Rock iobroker In file included from ../node_modules/nan/nan_new.h:189:0, from ../node_modules/nan/nan.h:82, from ../src/bufferutil.cc:16:../node_modules/nan/nan_implementation_12_inl.h: In static member function ‘static NanIntern::FactoryBase::return_t NanIntern::Factory::New(v8::Local)’:../node_modules/nan/nan_implementation_12_inl.h:166:69: error: no matching function for call to ‘v8::ScriptCompiler::Compile(v8::Isolate*, v8::ScriptCompiler::Source*)’ return v8::ScriptCompiler::Compile(v8::Isolate::GetCurrent(), &src); ^In file included from ../src/bufferutil.cc:7:0:/home/iobroker/.node-gyp/10.16.3/include/node/v8.h:1510:51: note: candidate: static v8::MaybeLocal v8::ScriptCompiler::Compile(v8::Local, v8::ScriptCompiler::Source*, v8::ScriptCompiler::CompileOptions, v8::ScriptCompiler::NoCacheReason) static V8_WARN_UNUSED_RESULT MaybeLocal

            apollon77A 1 Reply Last reply
            0
            • smartboartS Offline
              smartboartS Offline
              smartboart
              wrote on last edited by smartboart
              #792

              Mir ist noch was aufgefallen. Hab für den fullybrowser nen Chron Job im Admin angelegt.
              Alle 4 Stunden neustarten.... Der Log sieht dann so aus. Ist der einzige adapter mit nem Chron job bei mir..


              host.ioBroker-Rock 2019-10-15 12:56:00.433 error instance system.adapter.fullybrowser.0 terminated with code 156 (156)
              host.ioBroker-Rock 2019-10-15 12:55:01.467 info instance system.adapter.fullybrowser.0 started with pid 28554
              host.ioBroker-Rock 2019-10-15 12:55:00.449 info Restart adapter system.adapter.fullybrowser.0 because enabled
              host.ioBroker-Rock 2019-10-15 12:55:00.443 error instance system.adapter.fullybrowser.0 terminated with code 156 (156)
              host.ioBroker-Rock 2019-10-15 12:54:01.492 info instance system.adapter.fullybrowser.0 started with pid 27182
              host.ioBroker-Rock 2019-10-15 12:54:00.446 info Restart adapter system.adapter.fullybrowser.0 because enabled
              host.ioBroker-Rock 2019-10-15 12:54:00.446 error instance system.adapter.fullybrowser.0 terminated with code 156 (156)
              host.ioBroker-Rock 2019-10-15 12:53:01.526 info instance system.adapter.fullybrowser.0 started with pid 25634
              host.ioBroker-Rock 2019-10-15 12:53:00.508 info Restart adapter system.adapter.fullybrowser.0 because enabled
              host.ioBroker-Rock 2019-10-15 12:53:00.507 error instance system.adapter.fullybrowser.0 terminated with code 156 (156)
              host.ioBroker-Rock 2019-10-15 12:52:01.455 info instance system.adapter.fullybrowser.0 started with pid 24280
              host.ioBroker-Rock 2019-10-15 12:52:00.435 info Restart adapter system.adapter.fullybrowser.0 because enabled
              host.ioBroker-Rock 2019-10-15 12:52:00.434 error instance system.adapter.fullybrowser.0 terminated with code 156 (156)
              host.ioBroker-Rock 2019-10-15 12:51:01.458 info instance system.adapter.fullybrowser.0 started with pid 22758
              host.ioBroker-Rock 2019-10-15 12:51:00.441 info Restart adapter system.adapter.fullybrowser.0 because enabled
              host.ioBroker-Rock 2019-10-15 12:51:00.440 error instance system.adapter.fullybrowser.0 terminated with code 156 (156)

              apollon77A 1 Reply Last reply
              0
              • smartboartS smartboart

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

                @smartboart mehr log bitte

                gerne


                2019-10-14 19:36:28.810 - info: host.ioBroker-Rock Update repository "latest" under "http://download.iobroker.net/sources-dist-latest.json"
                2019-10-14 19:37:21.257 - info: host.ioBroker-Rock iobroker upgrade statistics
                2019-10-14 19:37:23.968 - info: host.ioBroker-Rock iobroker Update statistics from @0.2.0 to @0.2.2
                2019-10-14 19:37:25.117 - info: host.ioBroker-Rock iobroker NPM version: 6.9.0npm install iobroker.statistics@0.2.2 --loglevel error --production --save --prefix "/opt/iobroker" (System call)
                2019-10-14 19:39:04.319 - info: host.ioBroker-Rock iobroker In file included from ../node_modules/nan/nan.h:82:0, from ../src/bufferutil.cc:16:../node_modules/nan/nan_new.h: In function ‘v8::Local NanIntern::To(v8::Handle) [with T = v8::Integer; v8::Handle = v8::Local]’:../node_modules/nan/nan_new.h:29:66: warning: ‘v8::Local v8::Value::ToInteger() const’ is deprecated: Use maybe version [-Wdeprecated-declarations] To(v8::Handle i) { return i->ToInteger(); } ^
                2019-10-14 19:39:04.321 - info: host.ioBroker-Rock iobroker In file included from ../src/bufferutil.cc:7:0:/home/iobroker/.node-gyp/10.16.3/include/node/v8.h:10052:16: note: declared here Local Value::ToInteger() const { ^In file included from ../node_modules/nan/nan.h:82:0, from ../src/bufferutil.cc:16:../node_modules/nan/nan_new.h: In function ‘v8::Local NanIntern::To(v8::Handle) [with T = v8::Int32; v8::Handle = v8::Local]’:../node_modules/nan/nan_new.h:34:64: error: no matching function for call to ‘v8::Integer::ToInt32()’ To(v8::Handle i) { return i->ToInt32(); } ^In file included from ../src/bufferutil.cc:7:0:/home/iobroker/.node-gyp/10.16.3/include/node/v8.h:2437:43: note: candidate: v8::MaybeLocal v8::Value::ToInt32(v8::Local) const V8_WARN_UNUSED_RESULT MaybeLocal ToInt32(Local context) const; ^/home/iobroker/.node-gyp/10.16.3/include/node/v8.h:2437:43: note: candidate expects 1 argument, 0 providedIn file included from /home/iobroker/.node-gyp/10.16.3/include/node/v8.h:26:0, from ../src/bufferutil.cc:7:/home/iobroker/.node-gyp/10.16.3/include/node/v8.h:2450:30: note: candidate: v8::Local v8::Value::ToInt32(v8::Isolate*) const Local ToInt32(Isolate* isolate) const); ^/home/iobroker/.node-gyp/10.16.3/include/node/v8config.h:324:3: note: in definition of macro ‘V8_DEPRECATED’ declarator attribute((deprecated(message))) ^~~~~~~~
                2019-10-14 19:39:04.324 - info: host.ioBroker-Rock iobroker /home/iobroker/.node-gyp/10.16.3/include/node/v8.h:2450:30: note: candidate expects 1 argument, 0 provided Local ToInt32(Isolate* isolate) const); ^/home/iobroker/.node-gyp/10.16.3/include/node/v8config.h:324:3: note: in definition of macro ‘V8_DEPRECATED’ declarator attribute((deprecated(message))) ^~~~~~~~~~
                2019-10-14 19:39:04.327 - info: host.ioBroker-Rock iobroker In file included from ../node_modules/nan/nan.h:82:0, from ../src/bufferutil.cc:16:../node_modules/nan/nan_new.h: In function ‘v8::Local NanIntern::To(v8::Handle) [with T = v8::Uint32; v8::Handle = v8::Local]’:../node_modules/nan/nan_new.h:39:65: error: no matching function for call to ‘v8::Integer::ToUint32()’ To(v8::Handle i) { return i->ToUint32(); } ^In file included from ../src/bufferutil.cc:7:0:/home/iobroker/.node-gyp/10.16.3/include/node/v8.h:2435:44: note: candidate: v8::MaybeLocal v8::Value::ToUint32(v8::Local) const V8_WARN_UNUSED_RESULT MaybeLocal ToUint32( ^~/home/iobroker/.node-gyp/10.16.3/include/node/v8.h:2435:44: note: candidate expects 1 argument, 0 provided
                2019-10-14 19:39:04.349 - info: host.ioBroker-Rock iobroker In file included from ../node_modules/nan/nan_new.h:189:0, from ../node_modules/nan/nan.h:82, from ../src/bufferutil.cc:16:../node_modules/nan/nan_implementation_12_inl.h: In static member function ‘static NanIntern::FactoryBase::return_t NanIntern::Factory::New(bool)’:../node_modules/nan/nan_implementation_12_inl.h:49:38: error: no matching function for call to ‘v8::BooleanObject::New(bool&)’ return v8::BooleanObject::New(value).As(); ^
                2019-10-14 19:39:04.352 - info: host.ioBroker-Rock iobroker In file included from ../src/bufferutil.cc:7:0:/home/iobroker/.node-gyp/10.16.3/include/node/v8.h:5035:23: note: candidate: static v8::Local v8::BooleanObject::New(v8::Isolate*, bool) static Local New(Isolate* isolate, bool value); ^                /home/iobroker/.node-gyp/10.16.3/include/node/v8.h:5035:23: note: candidate expects 2 arguments, 1 providedIn file included from ../node_modules/nan/nan_new.h:189:0, from ../node_modules/nan/nan.h:82, from ../src/bufferutil.cc:16:../node_modules/nan/nan_implementation_12_inl.h:49:60: error: expected primary-expression before ‘>’ token return v8::BooleanObject::New(value).As(); ^../node_modules/nan/nan_implementation_12_inl.h:49:62: error: expected primary-expression before ‘)’ token return v8::BooleanObject::New(value).As(); ^
                2019-10-14 19:39:04.371 - info: host.ioBroker-Rock iobroker ../node_modules/nan/nan_implementation_12_inl.h: In static member function ‘static NanIntern::FactoryBase::return_t NanIntern::Factory::New(v8::Handle, v8::RegExp::Flags)’:../node_modules/nan/nan_implementation_12_inl.h:158:40: warning: ‘static v8::Local v8::RegExp::New(v8::Local, v8::RegExp::Flags)’ is deprecated: Use maybe version [-Wdeprecated-declarations] return v8::RegExp::New(pattern, flags); ^
                2019-10-14 19:39:04.373 - info: host.ioBroker-Rock iobroker In file included from /home/iobroker/.node-gyp/10.16.3/include/node/v8.h:26:0, from ../src/bufferutil.cc:7:/home/iobroker/.node-gyp/10.16.3/include/node/v8.h:5110:38: note: declared here Local New(Local pattern, Flags flags)); ^/home/iobroker/.node-gyp/10.16.3/include/node/v8config.h:324:3: note: in definition of macro ‘V8_DEPRECATED’ declarator attribute((deprecated(message))) ^                ~~~~~
                2019-10-14 19:39:04.378 - info: host.ioBroker-Rock iobroker In file included from ../node_modules/nan/nan_new.h:189:0, from ../node_modules/nan/nan.h:82, from ../src/bufferutil.cc:16:../node_modules/nan/nan_implementation_12_inl.h: In static member function ‘static NanIntern::FactoryBase::return_t NanIntern::Factory::New(v8::Local)’:../node_modules/nan/nan_implementation_12_inl.h:166:69: error: no matching function for call to ‘v8::ScriptCompiler::Compile(v8::Isolate*, v8::ScriptCompiler::Source*)’ return v8::ScriptCompiler::Compile(v8::Isolate::GetCurrent(), &src); ^In file included from ../src/bufferutil.cc:7:0:/home/iobroker/.node-gyp/10.16.3/include/node/v8.h:1510:51: note: candidate: static v8::MaybeLocal v8::ScriptCompiler::Compile(v8::Local, v8::ScriptCompiler::Source*, v8::ScriptCompiler::CompileOptions, v8::ScriptCompiler::NoCacheReason) static V8_WARN_UNUSED_RESULT MaybeLocal

                apollon77A Offline
                apollon77A Offline
                apollon77
                wrote on last edited by
                #793

                @smartboart denke alles nur Warnungen.

                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
                smartboartS 1 Reply Last reply
                0
                • smartboartS smartboart

                  Mir ist noch was aufgefallen. Hab für den fullybrowser nen Chron Job im Admin angelegt.
                  Alle 4 Stunden neustarten.... Der Log sieht dann so aus. Ist der einzige adapter mit nem Chron job bei mir..


                  host.ioBroker-Rock 2019-10-15 12:56:00.433 error instance system.adapter.fullybrowser.0 terminated with code 156 (156)
                  host.ioBroker-Rock 2019-10-15 12:55:01.467 info instance system.adapter.fullybrowser.0 started with pid 28554
                  host.ioBroker-Rock 2019-10-15 12:55:00.449 info Restart adapter system.adapter.fullybrowser.0 because enabled
                  host.ioBroker-Rock 2019-10-15 12:55:00.443 error instance system.adapter.fullybrowser.0 terminated with code 156 (156)
                  host.ioBroker-Rock 2019-10-15 12:54:01.492 info instance system.adapter.fullybrowser.0 started with pid 27182
                  host.ioBroker-Rock 2019-10-15 12:54:00.446 info Restart adapter system.adapter.fullybrowser.0 because enabled
                  host.ioBroker-Rock 2019-10-15 12:54:00.446 error instance system.adapter.fullybrowser.0 terminated with code 156 (156)
                  host.ioBroker-Rock 2019-10-15 12:53:01.526 info instance system.adapter.fullybrowser.0 started with pid 25634
                  host.ioBroker-Rock 2019-10-15 12:53:00.508 info Restart adapter system.adapter.fullybrowser.0 because enabled
                  host.ioBroker-Rock 2019-10-15 12:53:00.507 error instance system.adapter.fullybrowser.0 terminated with code 156 (156)
                  host.ioBroker-Rock 2019-10-15 12:52:01.455 info instance system.adapter.fullybrowser.0 started with pid 24280
                  host.ioBroker-Rock 2019-10-15 12:52:00.435 info Restart adapter system.adapter.fullybrowser.0 because enabled
                  host.ioBroker-Rock 2019-10-15 12:52:00.434 error instance system.adapter.fullybrowser.0 terminated with code 156 (156)
                  host.ioBroker-Rock 2019-10-15 12:51:01.458 info instance system.adapter.fullybrowser.0 started with pid 22758
                  host.ioBroker-Rock 2019-10-15 12:51:00.441 info Restart adapter system.adapter.fullybrowser.0 because enabled
                  host.ioBroker-Rock 2019-10-15 12:51:00.440 error instance system.adapter.fullybrowser.0 terminated with code 156 (156)

                  apollon77A Offline
                  apollon77A Offline
                  apollon77
                  wrote on last edited by
                  #794

                  @smartboart sicher das es 4 stündlich ist? Das siehe eher nach minütlich aus.

                  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
                  smartboartS 1 Reply Last reply
                  0
                  • D darkiop

                    Ok, zweiter Test - jetzt ohne den admin.0 crash ....

                    der Master ist wieder auf den Beinen, der Slave hat es aber nicht geschaft. stop/start aufm Slave und er ist wieder verbunden.

                    c96f9e81-1b16-4465-afaa-d74b44acdc4c-grafik.png

                    Puffert der controller auch Logs? Die 3 hier sind eigentlich entstanden während redis weg war, geschrieben wurden sie nach dem redis wieder da war:

                    2019-10-15 14:00:00.786  - info: javascript.0 (618) script.js.PRODUKTIV.Beleuchtung.01_Bewegungsmelder_Flur: +++ Bewegung im Flur. Helligkeitsschwelle bei < 10 | Aktuelle Helligkeit: 31.8 | Licht wird nicht geschaltet. +++
2019-10-15 14:00:01.180  - info: javascript.0 (618) script.js.PRODUKTIV.Beleuchtung.01_Bewegungsmelder_Flur: +++ Bewegung im Flur. Helligkeitsschwelle bei < 10 | Aktuelle Helligkeit: 32.6 | Licht wird nicht geschaltet. +++
2019-10-15 14:00:01.523  - info: javascript.0 (618) script.js.PRODUKTIV.Beleuchtung.01_Bewegungsmelder_Flur: +++ Bewegung im Flur. Helligkeitsschwelle bei < 10 | Aktuelle Helligkeit: 32.6 | Licht wird nicht geschaltet. +++

                    Edit:

                    So lange war redis weg:

                    d57fbaeb-9e0a-49d0-bf9d-53f79fde46ad-grafik.png

                    apollon77A Offline
                    apollon77A Offline
                    apollon77
                    wrote on last edited by
                    #795

                    @darkiop hast du hier bitte das Slave log komplett von dem Zeitraum?

                    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
                    D 1 Reply Last reply
                    0
                    • apollon77A apollon77

                      @smartboart sicher das es 4 stündlich ist? Das siehe eher nach minütlich aus.

                      smartboartS Offline
                      smartboartS Offline
                      smartboart
                      wrote on last edited by smartboart
                      #796

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

                      @smartboart sicher das es 4 stündlich ist? Das siehe eher nach minütlich aus.
                      ja sehr sicher...

                      Das ist jadas verwunderliche...noch dazu der Fehler.
                      instance system.adapter.fullybrowser.0 terminated with code 156 (156)
                      Unbenannt.JPG

                      J 1 Reply Last reply
                      0
                      • smartboartS smartboart

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

                        @smartboart sicher das es 4 stündlich ist? Das siehe eher nach minütlich aus.
                        ja sehr sicher...

                        Das ist jadas verwunderliche...noch dazu der Fehler.
                        instance system.adapter.fullybrowser.0 terminated with code 156 (156)
                        Unbenannt.JPG

                        J Offline
                        J Offline
                        Jan1
                        wrote on last edited by
                        #797

                        @smartboart
                        das ist alle 4 Stunden jede Minute

                        smartboartS 1 Reply Last reply
                        0
                        • J Jan1

                          @smartboart
                          das ist alle 4 Stunden jede Minute

                          smartboartS Offline
                          smartboartS Offline
                          smartboart
                          wrote on last edited by
                          #798

                          @Jan1 oh ok..ich glaube ich sollte mich nochmal mit den Chron Zeiten auseinanderstzen..Danke!!!

                          1 Reply Last reply
                          0
                          • apollon77A apollon77

                            @smartboart denke alles nur Warnungen.

                            smartboartS Offline
                            smartboartS Offline
                            smartboart
                            wrote on last edited by
                            #799

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

                            @smartboart denke alles nur Warnungen.

                            ok danke..hab ich mir gedacht, macht auch keine Probleme. Wenn du oder sonst wer dennoch ne Idee hat wie man diese gyp und nan Warnungen abstellt, gerne her damit.....

                            smartboartS 1 Reply Last reply
                            0
                            • apollon77A apollon77

                              @darkiop hast du hier bitte das Slave log komplett von dem Zeitraum?

                              D Offline
                              D Offline
                              darkiop
                              Most Active
                              wrote on last edited by
                              #800

                              @apollon77

                              Das ist alles von heute aufm Slave ab dem Zeitpunkt des Redis-Tests:

                              log_slave.txt

                              Proxmox-ioBroker-Redis-HA Doku: https://forum.iobroker.net/topic/47478/dokumentation-einer-proxmox-iobroker-redis-ha-umgebung

                              1 Reply Last reply
                              0
                              • apollon77A Offline
                                apollon77A Offline
                                apollon77
                                wrote on last edited by
                                #801

                                Sooooooo @darkiop Super Feedback!!

                                Die 2.0.32 ist auf GitHub, könntest Du alle 4 cases nochmal checken bitte?

                                Bisher wurden Adapter beim verlieren der States Connection beendet, aber der Host hat nur bei Objects-DB-verlust was getan ... Damit gab es Edge cases. Ist jetzt geändert.

                                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
                                D 2 Replies Last reply
                                0
                                • D Offline
                                  D Offline
                                  darkiop
                                  Most Active
                                  wrote on last edited by
                                  #802

                                  Danke. Ich schau mal ob ich heut noch dazu komme :D

                                  Proxmox-ioBroker-Redis-HA Doku: https://forum.iobroker.net/topic/47478/dokumentation-einer-proxmox-iobroker-redis-ha-umgebung

                                  1 Reply Last reply
                                  0
                                  • apollon77A apollon77

                                    Sooooooo @darkiop Super Feedback!!

                                    Die 2.0.32 ist auf GitHub, könntest Du alle 4 cases nochmal checken bitte?

                                    Bisher wurden Adapter beim verlieren der States Connection beendet, aber der Host hat nur bei Objects-DB-verlust was getan ... Damit gab es Edge cases. Ist jetzt geändert.

                                    D Offline
                                    D Offline
                                    darkiop
                                    Most Active
                                    wrote on last edited by
                                    #803

                                    @apollon77 Noch ne Frage, kann ich eigentlich auch über Github eine alte Version ziehen? Also wie müsste ich z.b. vorgehen wenn ich jetzt wieder die 2.0.25 möchte für die es aber keine NPM Version gibt?

                                    Proxmox-ioBroker-Redis-HA Doku: https://forum.iobroker.net/topic/47478/dokumentation-einer-proxmox-iobroker-redis-ha-umgebung

                                    apollon77A 1 Reply Last reply
                                    0
                                    • SBorgS Offline
                                      SBorgS Offline
                                      SBorg
                                      Forum Testing Most Active
                                      wrote on last edited by
                                      #804

                                      Die Versionsnummer mit anhängen (geht bei allen NPM-Paketen), also npm install ioBroker/ioBroker.js-controller@2.0.25

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

                                      D 1 Reply Last reply
                                      0
                                      • apollon77A apollon77

                                        Sooooooo @darkiop Super Feedback!!

                                        Die 2.0.32 ist auf GitHub, könntest Du alle 4 cases nochmal checken bitte?

                                        Bisher wurden Adapter beim verlieren der States Connection beendet, aber der Host hat nur bei Objects-DB-verlust was getan ... Damit gab es Edge cases. Ist jetzt geändert.

                                        D Offline
                                        D Offline
                                        darkiop
                                        Most Active
                                        wrote on last edited by
                                        #805

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

                                        Sooooooo @darkiop Super Feedback!!

                                        Die 2.0.32 ist auf GitHub, könntest Du alle 4 cases nochmal checken bitte?

                                        Bisher wurden Adapter beim verlieren der States Connection beendet, aber der Host hat nur bei Objects-DB-verlust was getan ... Damit gab es Edge cases. Ist jetzt geändert.

                                        Das war jetzt doch Aufwändiger als Gedacht, siehe TF3 :D

                                        tf_2-0-32.pdf

                                        Mein Log von Heute ging eben auch per Mail an dich raus.

                                        Proxmox-ioBroker-Redis-HA Doku: https://forum.iobroker.net/topic/47478/dokumentation-einer-proxmox-iobroker-redis-ha-umgebung

                                        apollon77A 2 Replies Last reply
                                        0
                                        • SBorgS SBorg

                                          Die Versionsnummer mit anhängen (geht bei allen NPM-Paketen), also npm install ioBroker/ioBroker.js-controller@2.0.25

                                          D Offline
                                          D Offline
                                          darkiop
                                          Most Active
                                          wrote on last edited by
                                          #806

                                          @SBorg Jep, das kenne ich - hab mich glaub falsch ausgedrückt. Kann ich auch zu einem Zeitpunkt eines Commits springen zu dem es keine Version gibt?

                                          Proxmox-ioBroker-Redis-HA Doku: https://forum.iobroker.net/topic/47478/dokumentation-einer-proxmox-iobroker-redis-ha-umgebung

                                          1 Reply Last reply
                                          0
                                          Reply
                                          • Reply as topic
                                          Log in to reply
                                          • Oldest to Newest
                                          • Newest to Oldest
                                          • Most Votes

                                          Support us

                                          ioBroker
                                          Community Adapters
                                          Donate

                                          536

                                          Online

                                          32.5k

                                          Users

                                          81.7k

                                          Topics

                                          1.3m

                                          Posts
                                          Community
                                          Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
                                          ioBroker Community 2014-2025
                                          logo
                                          • Login
                                          • Don't have an account? Register
                                          • Login or register to search.
                                          • First post
                                            Last post
                                          0
                                          • Home
                                          • Recent
                                          • Tags
                                          • Unread 0
                                          • Categories
                                          • Unreplied
                                          • Popular
                                          • GitHub
                                          • Docu
                                          • Hilfe