Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. sven12

    NEWS

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    S
    • Profile
    • Following 0
    • Followers 1
    • Topics 1
    • Posts 20
    • Best 1
    • Groups 1

    sven12

    @sven12

    1
    Reputation
    25
    Profile views
    20
    Posts
    1
    Followers
    0
    Following
    Joined Last Online

    sven12 Follow
    Starter

    Best posts made by sven12

    • RE: [Neuer Adapter] Poolcontroller

      Hallo,

      heute einge Änderungen im github übernommen.
      Betrifft nur Kompatibilität zur aktuellen iobroker Version.
      Ansonsten leider noch keine neuen Funktionen.
      https://github.com/svenp/ioBroker.poolcontroller

      Gruß
      Sven

      posted in Entwicklung
      S
      sven12

    Latest posts made by sven12

    • RE: Test js-controller v2.0.x (GitHub)

      @apollon77
      Sorry für die Umstände... Shelly auf 3.1.1 hoch gezogen, keine Änderung.
      Reboot ,
      Jetzt läuft der Shelly Adapter ohne Probleme..

      Also wie immer Reboot tut gut...

      posted in Tester
      S
      sven12
    • RE: Test js-controller v2.0.x (GitHub)

      @apollon77
      @Stuebi
      Ich habe den shelly Adapter mal deinstalliert.
      Eine erneute installation brachte folgenden Fehler zu Tage...

      2019-10-05 13:20:51.118  - info: host.iobroker-host iobroker host.iobroker-host install adapter shelly
      2019-10-05 13:20:51.133  - info: host.iobroker-host iobroker upload [2] shelly.admin /opt/iobroker/node_modules/iobroker.shelly/admin/words.js words.js application/javascript
      2019-10-05 13:20:51.217  - info: host.iobroker-host iobroker upload [1] shelly.admin /opt/iobroker/node_modules/iobroker.shelly/admin/shelly.png shelly.png image/png
      2019-10-05 13:20:51.272  - info: host.iobroker-host iobroker upload [0] shelly.admin /opt/iobroker/node_modules/iobroker.shelly/admin/index_m.html index_m.html text/html
      2019-10-05 13:20:51.347  - info: host.iobroker-host iobroker host.iobroker-host object system.adapter.shelly created/updated
      2019-10-05 13:20:51.503  - info: host.iobroker-host iobroker host.iobroker-host create instance shelly
      2019-10-05 13:20:51.508  - info: host.iobroker-host iobroker host.iobroker-host object shelly.0.info.connection created
      2019-10-05 13:20:51.537  - info: host.iobroker-host iobroker host.iobroker-host object shelly.0.info created
      2019-10-05 13:20:51.568  - info: host.iobroker-host iobroker host.iobroker-host object system.adapter.shelly.0.sigKill created
      2019-10-05 13:20:51.602  - info: host.iobroker-host iobroker host.iobroker-host object system.adapter.shelly.0.eventLoopLag created
      2019-10-05 13:20:51.633  - info: host.iobroker-host iobroker host.iobroker-host object system.adapter.shelly.0.outputCount created
      2019-10-05 13:20:51.664  - info: host.iobroker-host iobroker host.iobroker-host object system.adapter.shelly.0.inputCount created
      2019-10-05 13:20:51.695  - info: host.iobroker-host iobroker host.iobroker-host object system.adapter.shelly.0.uptime created
      2019-10-05 13:20:51.725  - info: host.iobroker-host iobroker host.iobroker-host object system.adapter.shelly.0.memRss created
      2019-10-05 13:20:51.756  - info: host.iobroker-host iobroker host.iobroker-host object system.adapter.shelly.0.memHeapTotal created
      2019-10-05 13:20:51.805  - info: host.iobroker-host iobroker host.iobroker-host object system.adapter.shelly.0.memHeapUsed created
      2019-10-05 13:20:51.864  - info: host.iobroker-host iobroker host.iobroker-host object system.adapter.shelly.0.cputime created
      2019-10-05 13:20:51.894  - info: host.iobroker-host iobroker host.iobroker-host object system.adapter.shelly.0.cpu created
      2019-10-05 13:20:51.938  - info: host.iobroker-host iobroker host.iobroker-host object system.adapter.shelly.0.compactMode created
      2019-10-05 13:20:51.968  - info: host.iobroker-host iobroker host.iobroker-host object system.adapter.shelly.0.connected created
      2019-10-05 13:20:51.997  - info: host.iobroker-host iobroker host.iobroker-host object system.adapter.shelly.0.alive created
      2019-10-05 13:20:52.039  - info: host.iobroker-host iobroker host.iobroker-host object system.adapter.shelly.0 created
      2019-10-05 13:20:52.045  - error: host.iobroker-host iobroker (node:19932) UnhandledPromiseRejectionWarning: Error: Connection is closed.    at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:115:25)    at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:82:20)    at Object.onceWrapper (events.js:315:30)    at emitOne (events.js:116:13)    at Socket.emit (events.js:211:7)    at TCP._handle.close [as _onclose] (net.js:561:12)(node:19932) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)(node:19932) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
      2019-10-05 13:20:53.043  - info: host.iobroker-host iobroker exit 0
      
      
      
      

      Hilft das weiter?

      Uninstall

      2019-10-05 13:24:46.024  - info: host.iobroker-host iobroker del shelly
      2019-10-05 13:24:47.014  - info: host.iobroker-host iobroker Delete adapter "shelly"
      2019-10-05 13:24:47.037  - info: host.iobroker-host iobroker host.iobroker-host Counted 1 instances of shelly
      2019-10-05 13:24:47.042  - info: host.iobroker-host iobroker host.iobroker-host Counted 1 adapter for shelly
      2019-10-05 13:24:47.060  - info: host.iobroker-host iobroker host.iobroker-host Counted 1 channels of shelly
      2019-10-05 13:24:47.158  - info: host.iobroker-host iobroker host.iobroker-host Counted 14 states of shelly
      2019-10-05 13:24:47.211  - info: host.iobroker-host iobroker host.iobroker-host Deleting 17 object(s).
      2019-10-05 13:24:48.038  - info: host.iobroker-host object deleted system.adapter.shelly.0
      2019-10-05 13:24:48.043  - info: host.iobroker-host iobroker npm uninstall iobroker.shelly --silent --save --prefix "/opt/iobroker" (System call)
      2019-10-05 13:24:48.204  - error: host.iobroker-host Cannot write files: /opt/iobroker/iobroker-data/files/shelly.admin/_data.json: ENOENT: no such file or directory, open '/opt/iobroker/iobroker-data/files/shelly.admin/_data.json'
      2019-10-05 13:25:00.031  - info: host.iobroker-host instance system.adapter.poolcontroller.0 started with pid 27732
      2019-10-05 13:25:14.532  - info: host.iobroker-host iobroker exit 0
      
      
      posted in Tester
      S
      sven12
    • RE: Test js-controller v2.0.x (GitHub)

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

      addrinuse

      Also das "addrinuse" kam ja nur weil die alte Instanz noch nicht sauber beendet war als ich die Instanz neu gestartet habe.
      Ich glaube das kann ich mittlerweile ausschließen. Habe einfach zu schnell den Adapter neu gestartet
      Die letzten Logs haben das ja auch nicht mehr angezeigt.... Ich glaube das ist nicht das Problem..
      Reboot geht heute nicht mehr.. Morgen evtl.

      posted in Tester
      S
      sven12
    • RE: Test js-controller v2.0.x (GitHub)

      @apollon77
      Nein auf beiden läuft kein Prozess mehr...

      posted in Tester
      S
      sven12
    • RE: Test js-controller v2.0.x (GitHub)

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

      ps auxww|grep shelly

      iobroker@iobroker-host:/opt/iobroker$ ps auxww|grep shelly
      iobroker 26889  0.0  0.0  12780   928 pts/3    S+   20:48   0:00 grep shelly
      iobroker@iobroker-host:/opt/iobroker$ node node_modules/iobroker.shelly/shelly.js --force --logs
      2019-10-04 20:48:48.376  - error: shelly.0 (27548) shelly.0 invalid process id scenario 25918 vs. 27548. Stopping
      
      
      
      posted in Tester
      S
      sven12
    • RE: Test js-controller v2.0.x (GitHub)

      @apollon77
      Wenn ich den Adapter im Admin gestoppt habe, kommt auf der Konsole das hier:

      iobroker@iobroker-host:/opt/iobroker$ node node_modules/iobroker.shelly/shelly.js --force --logs
      2019-10-04 20:45:07.776  - error: shelly.0 (20885) adapter disabled
      2019-10-04 20:45:07.779  - info: shelly.0 (20885) starting. Version 3.1.0 in /opt/iobroker/node_modules/iobroker.shelly, node: v8.16.1
      2019-10-04 20:45:07.841  - info: shelly.0 (20885) Stating Shelly adapter in CoAP modus.
      Exception: Error: addMembership EADDRINUSE/Error: addMembership EADDRINUSE
      2019-10-04 20:45:07.960  - error: shelly.0 (20885) Exception: Error: addMembership EADDRINUSE
      2019-10-04 20:45:07.961  - info: shelly.0 (20885) Closing Adapter
      
      
      posted in Tester
      S
      sven12
    • RE: Test js-controller v2.0.x (GitHub)

      @apollon77
      Nicht wirklich viel mehr Infos.....

      iobroker@iobroker-host:/opt/iobroker$ node node_modules/iobroker.shelly/shelly.js --force --logs
      2019-10-04 20:27:32.109  - error: shelly.0 (22205) shelly.0 invalid process id scenario 22181 vs. 22205. Stopping
      2019-10-04 20:27:44.707  - warn: shelly.0 (22205) Got terminate signal. Checking desired PID: 0 vs own PID 22205
      2019-10-04 20:27:44.742  - warn: shelly.0 (22205) Got terminate signal. Checking desired PID: 22651 vs own PID 22205
      2019-10-04 20:28:17.631  - warn: shelly.0 (22205) Got terminate signal. Checking desired PID: 0 vs own PID 22205
      2019-10-04 20:28:17.640  - warn: shelly.0 (22205) Got terminate signal. Checking desired PID: 23570 vs own PID 22205
      2019-10-04 20:28:49.488  - warn: shelly.0 (22205) Got terminate signal. Checking desired PID: 0 vs own PID 22205
      2019-10-04 20:28:49.499  - warn: shelly.0 (22205) Got terminate signal. Checking desired PID: 24494 vs own PID 22205
      2019-10-04 20:29:21.317  - warn: shelly.0 (22205) Got terminate signal. Checking desired PID: 0 vs own PID 22205
      2019-10-04 20:29:21.328  - warn: shelly.0 (22205) Got terminate signal. Checking desired PID: 25431 vs own PID 22205
      2019-10-04 20:29:21.486  - info: shelly.0 (22205) Got terminate signal TERMINATE_YOURSELF
      2019-10-04 20:29:28.431  - warn: shelly.0 (22205) Got terminate signal. Checking desired PID: 0 vs own PID 22205
      2019-10-04 20:29:28.442  - warn: shelly.0 (22205) Got terminate signal. Checking desired PID: 25668 vs own PID 22205
      2019-10-04 20:30:00.174  - warn: shelly.0 (22205) Got terminate signal. Checking desired PID: 0 vs own PID 22205
      2019-10-04 20:30:00.186  - warn: shelly.0 (22205) Got terminate signal. Checking desired PID: 26586 vs own PID 22205
      2019-10-04 20:30:36.686  - warn: shelly.0 (22205) Got terminate signal. Checking desired PID: 0 vs own PID 22205
      2019-10-04 20:30:36.697  - warn: shelly.0 (22205) Got terminate signal. Checking desired PID: 27752 vs own PID 22205
      
      

      iobroker Log

      2019-10-04 20:29:22.826  - error: shelly.0 (25431) adapter disabled
      2019-10-04 20:29:22.880  - warn: shelly.0 (25431) Terminated (NO_ADAPTER_CONFIG_FOUND): Without reason
      2019-10-04 20:29:22.898  - info: host.iobroker-host instance system.adapter.shelly.0 terminated with code 3 (NO_ADAPTER_CONFIG_FOUND)
      2019-10-04 20:29:23.686  - info: mqtt.0 (27417) Client [WetterStation] connected with secret 1570213763685_8509
      2019-10-04 20:29:23.713  - info: mqtt.0 (27417) Client [WetterStation] subscribes on "mqtt.0.WetterStation"
      2019-10-04 20:29:23.713  - info: mqtt.0 (27417) Client [WetterStation] publishOnSubscribe
      2019-10-04 20:29:24.429  - info: host.iobroker-host instance system.adapter.poolcontroller.0 terminated with code 0 (NO_ERROR)
      2019-10-04 20:29:28.427  - info: host.iobroker-host "system.adapter.shelly.0" enabled
      2019-10-04 20:29:28.431  - warn: shelly.0 (22205) Got terminate signal. Checking desired PID: 0 vs own PID 22205
      2019-10-04 20:29:28.442  - warn: shelly.0 (22205) Got terminate signal. Checking desired PID: 25668 vs own PID 22205
      2019-10-04 20:29:28.443  - info: host.iobroker-host instance system.adapter.shelly.0 started with pid 25668
      2019-10-04 20:29:29.142  - debug: shelly.0 (25668) Redis Objects: Use Redis connection: 0.0.0.0:9001
      2019-10-04 20:29:29.184  - debug: shelly.0 (25668) objectDB connected
      2019-10-04 20:29:29.186  - debug: shelly.0 (25668) Redis States: Use Redis connection: 0.0.0.0:9000
      2019-10-04 20:29:29.188  - debug: shelly.0 (25668) Objects connected to redis: 0.0.0.0:9001
      2019-10-04 20:29:29.192  - debug: shelly.0 (25668) statesDB connected
      2019-10-04 20:29:29.205  - debug: shelly.0 (25668) States connected to redis: 0.0.0.0:9000
      2019-10-04 20:29:29.969  - info: shelly.0 (25668) starting. Version 3.1.0 in /opt/iobroker/node_modules/iobroker.shelly, node: v8.16.1
      2019-10-04 20:29:30.041  - info: shelly.0 (25668) Stating Shelly adapter in CoAP modus.
      2019-10-04 20:29:30.162  - info: host.iobroker-host instance system.adapter.shelly.0 terminated with code 0 (NO_ERROR)
      2019-10-04 20:29:30.163  - info: host.iobroker-host Restart adapter system.adapter.shelly.0 because enabled
      
      
      posted in Tester
      S
      sven12
    • RE: Test js-controller v2.0.x (GitHub)

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

      n denn die Werte die da im log stehen so aktualisert? Auf was stehen die werte im Admin? Kannst Du schalten? bzw jetzt sag mal bitte ganz genau was "ist rot

      OK ich versuche es nochmal Verständlicher zu erklären.
      Normalerweise läuft der Shelly Adapter auf dem Host System. Der grüne Punkt im Admin ist normal ja grün (Punkt vor dem Adapter) wenn der Adapter läuft. Aktuell das nicht der Fall. Dort wird ein roter Punkt angezeigt. Ein schalten über die Objekte (switch true/flase) wird beim shelly nicht ausgeführt. Auch die Zustände unter Objekte ändern sich nicht wenn ich den Shelly über seine Weboberfläche schalte. Fazit Shelly Adapter roter Punkt davor und keine Funktion.

      Verschiebe ich die Shelly Instanz auf den client (ccu2rfdpieasy) bei mir ein pi3. Wird der Punkt vor dem Adapter grün. Der Shelly lässt sich über Objekte schalten. Änderungen der Schaltzustände am Shelly über die Shelly Weboberfläche werden dann auch unter ioBroker Objekte angezeigt.

      Shelly_client.png client_objekte.png shelly_host.png

      Ich hoffe es ist jetzt verständlich.
      Gruß
      Sven

      Hier noch die Logs als Ergänzung

      
      Hier keine Funktion beim Start der Instanz auf dem Host
      2019-10-04 18:36:23.356  - info: host.iobroker-host instance system.adapter.shelly.0 started with pid 30257
      2019-10-04 18:36:24.789  - debug: shelly.0 (30257) Redis Objects: Use Redis connection: 0.0.0.0:9001
      2019-10-04 18:36:25.439  - debug: shelly.0 (30257) Objects connected to redis: 0.0.0.0:9001
      2019-10-04 18:36:25.444  - debug: shelly.0 (30257) objectDB connected
      2019-10-04 18:36:25.446  - debug: shelly.0 (30257) Redis States: Use Redis connection: 0.0.0.0:9000
      2019-10-04 18:36:25.450  - debug: shelly.0 (30257) statesDB connected
      2019-10-04 18:36:25.461  - debug: shelly.0 (30257) States connected to redis: 0.0.0.0:9000
      2019-10-04 18:36:26.416  - info: shelly.0 (30257) starting. Version 3.1.0 in /opt/iobroker/node_modules/iobroker.shelly, node: v8.16.1
      2019-10-04 18:36:26.487  - info: shelly.0 (30257) Stating Shelly adapter in CoAP modus.
      2019-10-04 18:36:26.561  - info: host.iobroker-host instance system.adapter.shelly.0 terminated with code 0 (NO_ERROR)
      2019-10-04 18:36:26.562  - info: host.iobroker-host Restart adapter system.adapter.shelly.0 because enabled
      
      
      Hier ein Startvorgang auf dem Client (Pi) 
      2019-10-04 16:36:36.813  - info: host.ccu2rfdpieasy instance system.adapter.shelly.0 started with pid 1482
      2019-10-04 16:36:41.669  - debug: shelly.0 (1482) Redis Objects: Use Redis connection: 192.168.10.57:9001
      2019-10-04 16:36:42.083  - debug: shelly.0 (1482) objectDB connected
      2019-10-04 16:36:42.096  - debug: shelly.0 (1482) Redis States: Use Redis connection: 192.168.10.57:9000
      2019-10-04 16:36:42.109  - debug: shelly.0 (1482) Objects connected to redis: 192.168.10.57:9001
      2019-10-04 16:36:42.133  - debug: shelly.0 (1482) statesDB connected
      2019-10-04 16:36:42.246  - debug: shelly.0 (1482) States connected to redis: 192.168.10.57:9000
      2019-10-04 16:36:43.103  - info: shelly.0 (1482) starting. Version 3.1.0 in /opt/iobroker/node_modules/iobroker.shelly, node: v8.16.1
      2019-10-04 16:36:43.280  - info: shelly.0 (1482) Stating Shelly adapter in CoAP modus.
      2019-10-04 16:36:43.783  - info: shelly.0 (1482) Listening for Shelly packets in the network
      2019-10-04 16:36:50.340  - debug: shelly.0 (1482) CoAP status package received: {"3332":"SHSW-1#5BAC87#1","3412":38400,"3420":1792,"Uri-Path":"cit/s"} / {"G":[[0,112,0],[0,118,0]]}
      2019-10-04 16:36:50.343  - debug: shelly.0 (1482) Status update received for SHSW-1#5BAC87#1: {"G":[[0,112,0],[0,118,0]]}
      2019-10-04 16:36:50.346  - debug: shelly.0 (1482) CoAP device description request for SHSW-1#5BAC87#1 to 192.168.10.79(0)
      2019-10-04 16:36:50.384  - debug: shelly.0 (1482) CoAP response: {"3332":"SHSW-1#5BAC87#1"}
      2019-10-04 16:36:50.386  - debug: shelly.0 (1482) Device description received: {"3332":"SHSW-1#5BAC87#1"} / {"blk":[{"I":0,"D":"Relay0"},{"I":118,"T":"S","D":"Input","R":"0/1/2","L":1}],"sen":[{"I":112,"T":"Switch","R":"0/1","L":0}],"act":[{"I":211,"D":"Switch","L":0,"P":[{"I":2011,"D":"ToState","R":"0/1"}]}]}
      2019-10-04 16:36:50.394  - info: shelly.0 (1482) Shelly device 192.168.10.79 (shelly1 / shelly1-5BAC87 / SHSW-1#5BAC87#1) with CoAP connected!
      2019-10-04 16:36:50.463  - debug: shelly.0 (1482) CoAP Message for SHSW-1#5BAC87#1 : {"G":[[0,112,0],[0,118,0]]}
      2019-10-04 16:36:50.466  - debug: shelly.0 (1482) Create State : SHSW-1#5BAC87#1.Relay0.Switch, Payload: {"G":[[0,112,0],[0,118,0]]}for SHSW-1#5BAC87#1
      2019-10-04 16:36:50.468  - debug: shelly.0 (1482) State change : SHSW-1#5BAC87#1.Relay0.Switch, Value: false for 192.168.10.79 (shelly1 / shelly1-5BAC87 / SHSW-1#5BAC87#1)
      
      
      posted in Tester
      S
      sven12
    • RE: Test js-controller v2.0.x (GitHub)

      @apollon77

      bin jetzt auf 2.0.22. Shelly am Host immer noch rot und ohne Funktion.
      Bei mir läuft ioBroker Host auf Debian 9 in einer VM unter Proxmox.
      Ein Multihostclient auf Raspi.
      Der Shelly Adapter auf dem Host läuft nicht und ist rot, wenn ich den auf den PI verschiebe funktioniert er dort aber.
      Edit: Wobei ich erwähnen sollte, das die ip 192.168.10.57 der debian host ist, der client auf dem es läuft hat 192.168.10.25
      Hier das Log vom pi

      2019-10-04 14:24:08.435  - info: host.ccu2rfdpieasy instance system.adapter.shelly.0 started with pid 30156
      2019-10-04 14:24:13.261  - debug: shelly.0 (30156) Redis Objects: Use Redis connection: 192.168.10.57:9001
      2019-10-04 14:24:13.691  - debug: shelly.0 (30156) objectDB connected
      2019-10-04 14:24:13.701  - debug: shelly.0 (30156) Redis States: Use Redis connection: 192.168.10.57:9000
      2019-10-04 14:24:13.711  - debug: shelly.0 (30156) Objects connected to redis: 192.168.10.57:9001
      2019-10-04 14:24:13.731  - debug: shelly.0 (30156) statesDB connected
      2019-10-04 14:24:13.811  - debug: shelly.0 (30156) States connected to redis: 192.168.10.57:9000
      2019-10-04 14:24:14.538  - info: shelly.0 (30156) starting. Version 3.1.0 in /opt/iobroker/node_modules/iobroker.shelly, node: v8.16.1
      2019-10-04 14:24:14.768  - info: shelly.0 (30156) Stating Shelly adapter in CoAP modus.
      2019-10-04 14:24:15.312  - info: shelly.0 (30156) Listening for Shelly packets in the network
      2019-10-04 14:24:19.295  - debug: shelly.0 (30156) CoAP status package received: {"3332":"SHSW-1#5BAC87#1","3412":38400,"3420":1024,"Uri-Path":"cit/s"} / {"G":[[0,112,1],[0,118,0]]}
      2019-10-04 14:24:19.298  - debug: shelly.0 (30156) Status update received for SHSW-1#5BAC87#1: {"G":[[0,112,1],[0,118,0]]}
      2019-10-04 14:24:19.303  - debug: shelly.0 (30156) CoAP device description request for SHSW-1#5BAC87#1 to 192.168.10.79(0)
      2019-10-04 14:24:19.341  - debug: shelly.0 (30156) CoAP response: {"3332":"SHSW-1#5BAC87#1"}
      2019-10-04 14:24:19.343  - debug: shelly.0 (30156) Device description received: {"3332":"SHSW-1#5BAC87#1"} / {"blk":[{"I":0,"D":"Relay0"},{"I":118,"T":"S","D":"Input","R":"0/1/2","L":1}],"sen":[{"I":112,"T":"Switch","R":"0/1","L":0}],"act":[{"I":211,"D":"Switch","L":0,"P":[{"I":2011,"D":"ToState","R":"0/1"}]}]}
      2019-10-04 14:24:19.352  - info: shelly.0 (30156) Shelly device 192.168.10.79 (shelly1 / shelly1-5BAC87 / SHSW-1#5BAC87#1) with CoAP connected!
      2019-10-04 14:24:19.430  - debug: shelly.0 (30156) CoAP Message for SHSW-1#5BAC87#1 : {"G":[[0,112,1],[0,118,0]]}
      2019-10-04 14:24:19.432  - debug: shelly.0 (30156) Create State : SHSW-1#5BAC87#1.Relay0.Switch, Payload: {"G":[[0,112,1],[0,118,0]]}for SHSW-1#5BAC87#1
      2019-10-04 14:24:19.435  - debug: shelly.0 (30156) State change : SHSW-1#5BAC87#1.Relay0.Switch, Value: true for 192.168.10.79 (shelly1 / shelly1-5BAC87 / SHSW-1#5BAC87#1)
      2019-10-04 14:24:19.649  - debug: shelly.0 (30156) Set state SHSW-1#5BAC87#1.Relay0.AutoTimerOff, Value: 0 for 192.168.10.79 (shelly1 / shelly1-5BAC87 / SHSW-1#5BAC87#1)
      2019-10-04 14:24:19.654  - debug: shelly.0 (30156) Set state SHSW-1#5BAC87#1.Relay0.AutoTimerOn, Value: 0 for 192.168.10.79 (shelly1 / shelly1-5BAC87 / SHSW-1#5BAC87#1)
      2019-10-04 14:24:19.658  - debug: shelly.0 (30156) Set state SHSW-1#5BAC87#1.version, Value: "20190821-094851/v1.5.2@4148d2b7" for 192.168.10.79 (shelly1 / shelly1-5BAC87 / SHSW-1#5BAC87#1)
      2019-10-04 14:24:19.749  - debug: shelly.0 (30156) Set state SHSW-1#5BAC87#1.firmware, Value: false for 192.168.10.79 (shelly1 / shelly1-5BAC87 / SHSW-1#5BAC87#1)
      2019-10-04 14:24:19.755  - debug: shelly.0 (30156) Set state SHSW-1#5BAC87#1.uptime, Value: "01:31:39" for 192.168.10.79 (shelly1 / shelly1-5BAC87 / SHSW-1#5BAC87#1)
      2019-10-04 14:24:19.757  - debug: shelly.0 (30156) Set state SHSW-1#5BAC87#1.hostname, Value: "192.168.10.79" for 192.168.10.79 (shelly1 / shelly1-5BAC87 / SHSW-1#5BAC87#1)
      2019-10-04 14:24:19.760  - debug: shelly.0 (30156) Set state SHSW-1#5BAC87#1.rssi, Value: -56 for 192.168.10.79 (shelly1 / shelly1-5BAC87 / SHSW-1#5BAC87#1)
      2019-10-04 14:24:24.939  - debug: shelly.0 (30156) Set state SHSW-1#5BAC87#1.uptime, Value: "01:31:44" for 192.168.10.79 (shelly1 / shelly1-5BAC87 / SHSW-1#5BAC87#1)
      2019-10-04 14:24:24.942  - debug: shelly.0 (30156) Set state SHSW-1#5BAC87#1.rssi, Value: -57 for 192.168.10.79 (shelly1 / shelly1-5BAC87 / SHSW-1#5BAC87#1)
      2019-10-04 14:24:30.121  - debug: shelly.0 (30156) Set state SHSW-1#5BAC87#1.uptime, Value: "01:31:50" for 192.168.10.79 (shelly1 / shelly1-5BAC87 / SHSW-1#5BAC87#1)
      2019-10-04 14:24:30.126  - debug: shelly.0 (30156) Set state SHSW-1#5BAC87#1.rssi, Value: -56 for 192.168.10.79 (shelly1 / shelly1-5BAC87 / SHSW-1#5BAC87#1)
      2019-10-04 14:24:34.249  - debug: shelly.0 (30156) CoAP data ignored: {"3332":"SHSW-1#5BAC87#1","3412":38400,"3420":1024,"Uri-Path":"cit/s"} / {"G":[[0,112,1],[0,118,0]]}
      2019-10-04 14:24:35.308  - debug: shelly.0 (30156) Set state SHSW-1#5BAC87#1.uptime, Value: "01:31:55" for 192.168.10.79 (shelly1 / shelly1-5BAC87 / SHSW-1#5BAC87#1)
      2019-10-04 14:24:35.313  - debug: shelly.0 (30156) Set state SHSW-1#5BAC87#1.rssi, Value: -54 for 192.168.10.79 (shelly1 / shelly1-5BAC87 / SHSW-1#5BAC87#1)
      2019-10-04 14:24:40.493  - debug: shelly.0 (30156) Set state SHSW-1#5BAC87#1.uptime, Value: "01:32:00" for 192.168.10.79 (shelly1 / shelly1-5BAC87 / SHSW-1#5BAC87#1)
      2019-10-04 14:24:40.496  - debug: shelly.0 (30156) Set state SHSW-1#5BAC87#1.rssi, Value: -55 for 192.168.10.79 (shelly1 / shelly1-5BAC87 / SHSW-1#5BAC87#1)
      
      
      

      @Stuebi könnte also mit Redis zusammen hängen, möglicherweise ist es auf dem Pi drauf und auf dem Debian 9 x64 Host nicht.... Weiß nur nicht wie ich das rausfinden kann

      posted in Tester
      S
      sven12
    • RE: Test js-controller v2.0.x (GitHub)

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

      @sven12 tut er noch oder nur "rot?

      Ob er noch tut kann ich jetzt gerade nicht testen. Reiche ich aber morgen nach....
      Gruß
      Sven

      Hier das Logfile

      2019-10-03 22:19:06.731  - debug: shelly.0 (20158) objectDB connected
      2019-10-03 22:19:06.735  - debug: shelly.0 (20158) Redis States: Use Redis connection: 0.0.0.0:9000
      2019-10-03 22:19:06.738  - debug: shelly.0 (20158) Objects connected to redis: 0.0.0.0:9001
      2019-10-03 22:19:06.742  - debug: shelly.0 (20158) statesDB connected
      2019-10-03 22:19:06.757  - debug: shelly.0 (20158) States connected to redis: 0.0.0.0:9000
      2019-10-03 22:19:07.699  - info: shelly.0 (20158) starting. Version 3.1.0 in /opt/iobroker/node_modules/iobroker.shelly, node: v8.16.1
      2019-10-03 22:19:07.755  - info: shelly.0 (20158) Stating Shelly adapter in CoAP modus.
      2019-10-03 22:19:07.824  - info: host.iobroker-host instance system.adapter.shelly.0 terminated with code 0 (NO_ERROR)
      2019-10-03 22:19:07.825  - info: host.iobroker-host Restart adapter system.adapter.shelly.0 because enabled
      2019-10-03 22:19:08.676  - info: host.iobroker-host instance system.adapter.shelly.0 started with pid 20387
      2019-10-03 22:19:09.600  - debug: shelly.0 (20387) Redis Objects: Use Redis connection: 0.0.0.0:9001
      2019-10-03 22:19:09.642  - debug: shelly.0 (20387) objectDB connected
      2019-10-03 22:19:09.644  - debug: shelly.0 (20387) Redis States: Use Redis connection: 0.0.0.0:9000
      2019-10-03 22:19:09.645  - debug: shelly.0 (20387) Objects connected to redis: 0.0.0.0:9001
      2019-10-03 22:19:09.649  - debug: shelly.0 (20387) statesDB connected
      2019-10-03 22:19:09.659  - debug: shelly.0 (20387) States connected to redis: 0.0.0.0:9000
      2019-10-03 22:19:10.512  - info: shelly.0 (20387) starting. Version 3.1.0 in /opt/iobroker/node_modules/iobroker.shelly, node: v8.16.1
      2019-10-03 22:19:10.558  - info: shelly.0 (20387) Stating Shelly adapter in CoAP modus.
      2019-10-03 22:19:10.645  - info: host.iobroker-host instance system.adapter.shelly.0 terminated with code 0 (NO_ERROR)
      2019-10-03 22:19:10.646  - info: host.iobroker-host Restart adapter system.adapter.shelly.0 because enabled
      2019-10-03 22:19:22.846  - info: host.iobroker-host instance system.adapter.poolcontroller.0 terminated with code 0 (NO_ERROR)
      2019-10-03 22:19:40.682  - info: host.iobroker-host instance system.adapter.shelly.0 started with pid 21308
      2019-10-03 22:19:41.789  - debug: shelly.0 (21308) Redis Objects: Use Redis connection: 0.0.0.0:9001
      2019-10-03 22:19:41.834  - debug: shelly.0 (21308) objectDB connected
      2019-10-03 22:19:41.835  - debug: shelly.0 (21308) Redis States: Use Redis connection: 0.0.0.0:9000
      2019-10-03 22:19:41.837  - debug: shelly.0 (21308) Objects connected to redis: 0.0.0.0:9001
      2019-10-03 22:19:41.841  - debug: shelly.0 (21308) statesDB connected
      2019-10-03 22:19:41.853  - debug: shelly.0 (21308) States connected to redis: 0.0.0.0:9000
      2019-10-03 22:19:43.147  - info: shelly.0 (21308) starting. Version 3.1.0 in /opt/iobroker/node_modules/iobroker.shelly, node: v8.16.1
      2019-10-03 22:19:43.884  - info: shelly.0 (21308) Stating Shelly adapter in CoAP modus.
      2019-10-03 22:19:44.298  - info: host.iobroker-host instance system.adapter.shelly.0 terminated with code 0 (NO_ERROR)
      2019-10-03 22:19:44.298  - info: host.iobroker-host Restart adapter system.adapter.shelly.0 because enabled
      2019-10-03 22:20:00.050  - info: host.iobroker-host instance system.adapter.poolcontroller.0 started with pid 21795
      
      
      posted in Tester
      S
      sven12
    Community
    Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
    The ioBroker Community 2014-2023
    logo