Js-controller 0.16
-
Bitte um Tests von js-controller 0.16.1:
` > # 0.16.1 (2017-02-27)-
(bluefox) use SHA256 instead of SHA1 (All passwords must be reset via "iobroker passwd username")
-
(bluefox) change cli commands for user: user add, user del, user set, user enable…
***** (bluefox) replace letsencrypt with greenlock****
***** (bluefox) try to fix sha256 issue with node.js 0.10.x****
***** (Apollon77) change reinstall.sh script****
-
(bluefox) add setStateChanged
-
(bluefox) implement event counters
-
(bluefox) read values from cache if possible in adapter
-
(bluefox) add parser adapter, smartmeter, fakeroku, wetty, fronius, Worx Landroid Rasenmäher, uniti
***** (bluefox) fix log sources****
-
(bluefox) fix callbacks calls by setObjectNotExists
-
(bluefox) fix getForeignObjects
***** (bluefox) write tests****
-
(Patrick) adapter.namespace now always int (was int or string mixed)
-
(Patrick) _fixId better results for empty obj and string (return namespace + '.')
-
(bluefox) small fixes for multihost
-
(bluefox) add getInstalledAdapter for autodiscovery `
Die Version ist die Vorbereitung für Auto-discovery. Die Zeigt auch Input/Output Anzahl von Meldungen.
Man braucht auch admin dafür.
-
-
Tried to test but after installation admin did not work at all and I went back to 15.3
-
Habe gerade auf meinem Master js-controller und admin updated. Bis jetzt keine Auffälligkeiten. Die Slaves folgen morgen…
-
@fsjoke:Tried to test but after installation admin did not work at all and I went back to 15.3 `
Hm… log? -
Wie der Herr wünscht.
Bei mir war aber alles soweit gut. Ausser, das der js-controller nicht neu neu-starten wollte. Nach````
iobroker restart>! ```` Drücke Strg+A und danach Strg+C, um den Inhalt in die Zwischenablage zu kopieren. Klicke irgendwo, um das Fenster zu schliessen. javascript.0 2017-02-28 07:40:00.925 info script.js.common._Solar.Poll_Modbus: Script Poll_Modbus; Heartbeat harmony.0 2017-02-28 07:33:13.909 info synced hub config harmony.0 2017-02-28 07:33:12.745 info connected to Harmony Hub YK harmony.0 2017-02-28 07:33:10.354 info connecting to Harmony Hub YK harmony.0 2017-02-28 07:33:10.157 info discovered Harmony Hub YK harmony.0 2017-02-28 07:32:22.419 warn could not connect to Harmony Hub YK: Error: Timed out after 5000 ms harmony.0 2017-02-28 07:32:12.366 info keep alive failed: Error: Timed out after 5000 ms harmony.0 2017-02-28 07:32:09.790 info client ended: Harmony_Hub_YK harmony.0 2017-02-28 07:32:09.767 warn lost Harmony Hub YK javascript.0 2017-02-28 07:30:00.925 info script.js.common._Solar.Poll_Modbus: Script Poll_Modbus; Heartbeat javascript.0 2017-02-28 07:20:00.925 info script.js.common._Solar.Poll_Modbus: Script Poll_Modbus; Heartbeat javascript.0 2017-02-28 07:10:00.926 info script.js.common._Solar.Poll_Modbus: Script Poll_Modbus; Heartbeat javascript.0 2017-02-28 07:00:00.924 info script.js.common._Solar.Poll_Modbus: Script Poll_Modbus; Heartbeat hm-rpc.0 2017-02-28 06:55:00.722 info setValue ['MEQ0188491:1','STATE',false] BOOL javascript.0 2017-02-28 06:55:00.705 info script.js.common._Keller.Keller-Geräte: Script Keller-Geräte; Status: Entfeuchter aus. (Tarif: Hochtarif, Solar: 0) javascript.0 2017-02-28 06:55:00.694 info script.js.common._Keller.Strom-Tarif: Script Strom-Tarif; Ab jetzt gilt Hochtarif (2) javascript.0 2017-02-28 06:50:00.926 info script.js.common._Solar.Poll_Modbus: Script Poll_Modbus; Heartbeat javascript.0 2017-02-28 06:40:00.927 info script.js.common._Solar.Poll_Modbus: Script Poll_Modbus; Heartbeat javascript.0 2017-02-28 06:30:00.927 info script.js.common._Solar.Poll_Modbus: Script Poll_Modbus; Heartbeat javascript.0 2017-02-28 06:20:00.928 info script.js.common._Solar.Poll_Modbus: Script Poll_Modbus; Heartbeat host.raspi3 2017-02-28 06:16:05.870 info instance system.adapter.solarwetter.0 terminated with code 0 (OK) solarwetter.0 2017-02-28 06:16:05.321 info force terminating adapter after 1 minute solarwetter.0 2017-02-28 06:15:05.310 info objects written solarwetter.0 2017-02-28 06:15:05.274 info Leistung eigene Anlage: 10.5 kWp solarwetter.0 2017-02-28 06:15:05.271 info 4-Tage-Prognose für: Freiburg solarwetter.0 2017-02-28 06:15:05.267 info Postcode: 798 solarwetter.0 2017-02-28 06:15:05.243 info starting. Version 0.1.2 in /opt/iobroker/node_modules/iobroker.solarwetter, node: v4.7.3 solarwetter.0 2017-02-28 06:15:05.154 info States connected to redis 127.0.0.1:6379 host.raspi3 2017-02-28 06:15:00.572 info instance system.adapter.solarwetter.0 started with pid 19527 javascript.0 2017-02-28 06:10:00.925 info script.js.common._Solar.Poll_Modbus: Script Poll_Modbus; Heartbeat javascript.0 2017-02-28 06:00:00.927 info script.js.common._Solar.Poll_Modbus: Script Poll_Modbus; Heartbeat javascript.0 2017-02-28 05:50:00.926 info script.js.common._Solar.Poll_Modbus: Script Poll_Modbus; Heartbeat javascript.0 2017-02-28 05:40:00.925 info script.js.common._Solar.Poll_Modbus: Script Poll_Modbus; Heartbeat javascript.0 2017-02-28 05:30:00.925 info script.js.common._Solar.Poll_Modbus: Script Poll_Modbus; Heartbeat javascript.0 2017-02-28 05:20:00.927 info script.js.common._Solar.Poll_Modbus: Script Poll_Modbus; Heartbeat javascript.0 2017-02-28 05:10:00.926 info script.js.common._Solar.Poll_Modbus: Script Poll_Modbus; Heartbeat javascript.0 2017-02-28 05:00:00.925 info script.js.common._Solar.Poll_Modbus: Script Poll_Modbus; Heartbeat javascript.0 2017-02-28 04:50:00.932 info script.js.common._Solar.Poll_Modbus: Script Poll_Modbus; Heartbeat javascript.0 2017-02-28 04:40:00.925 info script.js.common._Solar.Poll_Modbus: Script Poll_Modbus; Heartbeat javascript.0 2017-02-28 04:30:00.926 info script.js.common._Solar.Poll_Modbus: Script Poll_Modbus; Heartbeat javascript.0 2017-02-28 04:20:00.926 info script.js.common._Solar.Poll_Modbus: Script Poll_Modbus; Heartbeat javascript.0 2017-02-28 04:10:00.930 info script.js.common._Solar.Poll_Modbus: Script Poll_Modbus; Heartbeat javascript.0 2017-02-28 04:00:00.925 info script.js.common._Solar.Poll_Modbus: Script Poll_Modbus; Heartbeat javascript.0 2017-02-28 03:50:00.926 info script.js.common._Solar.Poll_Modbus: Script Poll_Modbus; Heartbeat javascript.0 2017-02-28 03:40:00.925 info script.js.common._Solar.Poll_Modbus: Script Poll_Modbus; Heartbeat javascript.0 2017-02-28 03:30:00.924 info script.js.common._Solar.Poll_Modbus: Script Poll_Modbus; Heartbeat javascript.0 2017-02-28 03:20:00.931 info script.js.common._Solar.Poll_Modbus: Script Poll_Modbus; Heartbeat javascript.0 2017-02-28 03:10:00.925 info script.js.common._Solar.Poll_Modbus: Script Poll_Modbus; Heartbeat javascript.0 2017-02-28 03:00:00.925 info script.js.common._Solar.Poll_Modbus: Script Poll_Modbus; Heartbeat javascript.0 2017-02-28 02:50:00.926 info script.js.common._Solar.Poll_Modbus: Script Poll_Modbus; Heartbeat javascript.0 2017-02-28 02:40:00.929 info script.js.common._Solar.Poll_Modbus: Script Poll_Modbus; Heartbeat javascript.0 2017-02-28 02:30:00.925 info script.js.common._Solar.Poll_Modbus: Script Poll_Modbus; Heartbeat javascript.0 2017-02-28 02:20:00.927 info script.js.common._Solar.Poll_Modbus: Script Poll_Modbus; Heartbeat javascript.0 2017-02-28 02:10:00.925 info script.js.common._Solar.Poll_Modbus: Script Poll_Modbus; Heartbeat host.raspi3 2017-02-28 02:06:37.876 info Delete log file iobroker.2017-02-21.log javascript.0 2017-02-28 02:00:00.926 info script.js.common._Solar.Poll_Modbus: Script Poll_Modbus; Heartbeat javascript.0 2017-02-28 01:50:00.935 info script.js.common._Solar.Poll_Modbus: Script Poll_Modbus; Heartbeat javascript.0 2017-02-28 01:40:00.926 info script.js.common._Solar.Poll_Modbus: Script Poll_Modbus; Heartbeat javascript.0 2017-02-28 01:30:00.928 info script.js.common._Solar.Poll_Modbus: Script Poll_Modbus; Heartbeat javascript.0 2017-02-28 01:20:00.930 info script.js.common._Solar.Poll_Modbus: Script Poll_Modbus; Heartbeat javascript.0 2017-02-28 01:10:00.927 info script.js.common._Solar.Poll_Modbus: Script Poll_Modbus; Heartbeat web.0 2017-02-28 01:09:50.741 info 2017-02-28T00:09:50.740Z Connected system.user.admin web.0 2017-02-28 01:09:50.671 info 2017-02-28T00:09:50.670Z Connected system.user.admin admin.0 2017-02-28 01:09:41.466 info Repository received successfully. web.0 2017-02-28 01:09:38.341 info 2017-02-28T00:09:38.340Z Connected system.user.admin host.raspi3 2017-02-28 01:09:12.213 info instance system.adapter.solarwetter.0 terminated with code 0 (OK) solarwetter.0 2017-02-28 01:09:11.630 info force terminating adapter after 1 minute host.raspi3 2017-02-28 01:09:08.890 info instance system.adapter.vis.0 terminated while should be started once vis.0 2017-02-28 01:09:08.283 info Uploaded. vis.0 2017-02-28 01:09:06.267 info 600 files uploaded... vis.0 2017-02-28 01:08:57.114 info 500 files uploaded... upnp.0 2017-02-28 01:08:40.838 info Auto discover: undefined upnp.0 2017-02-28 01:08:40.820 info starting. Version 0.3.5 in /opt/iobroker/node_modules/iobroker.upnp, node: v4.7.3 upnp.0 2017-02-28 01:08:40.639 info States connected to redis 127.0.0.1:6379 vis.0 2017-02-28 01:08:39.732 info 400 files uploaded... host.raspi3 2017-02-28 01:08:31.548 info instance system.adapter.upnp.0 started with pid 12390 vis.0 2017-02-28 01:08:29.722 info 300 files uploaded... vis.0 2017-02-28 01:08:18.325 info 200 files uploaded... sayit.1 2017-02-28 01:08:15.358 info All files uploaded sayit.1 2017-02-28 01:08:15.204 info Upload announce mp3 files sayit.1 2017-02-28 01:08:15.188 info starting. Version 1.5.1 in /opt/iobroker/node_modules/iobroker.sayit, node: v4.7.3 sayit.1 2017-02-28 01:08:15.012 info States connected to redis 127.0.0.1:6379 sayit.0 2017-02-28 01:08:12.776 info All files uploaded sayit.0 2017-02-28 01:08:12.421 info Upload announce mp3 files sayit.0 2017-02-28 01:08:12.378 info starting. Version 1.5.1 in /opt/iobroker/node_modules/iobroker.sayit, node: v4.7.3 sayit.0 2017-02-28 01:08:12.109 info States connected to redis 127.0.0.1:6379 solarwetter.0 2017-02-28 01:08:11.628 info objects written solarwetter.0 2017-02-28 01:08:11.579 info Leistung eigene Anlage: 10.5 kWp solarwetter.0 2017-02-28 01:08:11.576 info 4-Tage-Prognose für: Freiburg solarwetter.0 2017-02-28 01:08:11.567 info Postcode: 798 host.raspi3 2017-02-28 01:08:11.522 info instance system.adapter.sayit.1 started with pid 12249 solarwetter.0 2017-02-28 01:08:11.487 info starting. Version 0.1.2 in /opt/iobroker/node_modules/iobroker.solarwetter, node: v4.7.3 solarwetter.0 2017-02-28 01:08:11.340 info States connected to redis 127.0.0.1:6379 javascript.0 2017-02-28 01:08:10.139 warn script.js.common._Solar.Poll_Modbus: Script Poll_Modbus; Fehler in der Antwort vom Modbus Python Script. Antwort = 6 host.raspi3 2017-02-28 01:08:07.628 info instance system.adapter.sayit.0 started with pid 12197 vis.0 2017-02-28 01:08:03.991 info 100 files uploaded... host.raspi3 2017-02-28 01:08:03.585 info instance system.adapter.solarwetter.0 started with pid 12191 host.raspi3 2017-02-28 01:08:03.521 info instance scheduled system.adapter.solarwetter.0 15 6 * * * web.0 2017-02-28 01:07:51.453 info 2017-02-28T00:07:51.452Z Connected system.user.admin web.0 2017-02-28 01:07:49.819 info 2017-02-28T00:07:49.818Z Connected system.user.admin web.0 2017-02-28 01:07:49.488 info 2017-02-28T00:07:49.487Z Connected system.user.admin host.raspi3 2017-02-28 01:07:45.189 info Update repository 'online' under 'https://raw.githubusercontent.com/ioBroker/ioBroker.js-controller/master/conf/sources-dist.json' admin.0 2017-02-28 01:07:44.283 info received all objects host.raspi3 2017-02-28 01:07:42.988 info stopInstance system.adapter.vis.0 host.raspi3 2017-02-28 01:07:42.987 info 'system.adapter.vis.0' enabled host.raspi3 2017-02-28 01:07:42.986 info object change system.adapter.vis.0 host.raspi3 2017-02-28 01:07:42.925 info stopInstance system.adapter.vis.0 host.raspi3 2017-02-28 01:07:42.920 info 'system.adapter.vis.0' disabled host.raspi3 2017-02-28 01:07:42.918 info object change system.adapter.vis.0 vis.0 2017-02-28 01:07:37.813 info Upload vis anew, while changes detected... vis.0 2017-02-28 01:07:37.748 info Changes in index.html detected => update cache.manifest admin.0 2017-02-28 01:07:37.719 info received all states hm-rega.0 2017-02-28 01:07:37.646 info got state values hm-rega.0 2017-02-28 01:07:36.956 info request state values hm-rega.0 2017-02-28 01:07:36.953 info deleted 0 variables hm-rega.0 2017-02-28 01:07:36.952 info added/updated 4 variables hm-rega.0 2017-02-28 01:07:36.855 info got 4 variables hm-rega.0 2017-02-28 01:07:36.604 info deleted 0 programs hm-rega.0 2017-02-28 01:07:36.602 info added/updated 4 programs hm-rega.0 2017-02-28 01:07:36.444 info got 4 programs hm-rega.0 2017-02-28 01:07:32.725 info added/updated rooms to enum.rooms hm-rega.0 2017-02-28 01:07:32.647 info added/updated functions to enum.functions hm-rega.0 2017-02-28 01:07:32.535 info added/updated 0 favorites to enum.favorites hm-rega.0 2017-02-28 01:07:32.427 info time difference local-ccu 0s hm-rega.0 2017-02-28 01:07:32.344 info ReGaHSS 192.168.1.90 up hm-rega.0 2017-02-28 01:07:32.141 info system.adapter.admin.0: logging true hm-rega.0 2017-02-28 01:07:28.869 info subscribe hm-rpc.0.BidCoS-RF.50.PRESS_SHORT admin.0 2017-02-28 01:07:31.104 info system.adapter.admin.0: logging true sql.0 2017-02-28 01:07:31.057 info system.adapter.admin.0: logging true web.0 2017-02-28 01:07:31.065 info system.adapter.admin.0: logging true vis.0 2017-02-28 01:07:31.051 info system.adapter.admin.0: logging true fakeroku.0 2017-02-28 01:07:31.042 info system.adapter.admin.0: logging true javascript.0 2017-02-28 01:07:31.049 info system.adapter.admin.0: logging true harmony.0 2017-02-28 01:07:31.046 info system.adapter.admin.0: logging true javascript.0 2017-02-28 01:07:31.034 info system.adapter.admin.0: logging true sonos.0 2017-02-28 01:07:31.034 info system.adapter.admin.0: logging true hm-rpc.0 2017-02-28 01:07:31.038 info system.adapter.admin.0: logging true admin.0 2017-02-28 01:07:30.998 info Change log subscriber state: true admin.0 2017-02-28 01:07:28.502 info Use link 'http://localhost:8081' to configure. admin.0 2017-02-28 01:07:28.501 info http server listening on port 8081 admin.0 2017-02-28 01:07:28.494 info Request actual repository... admin.0 2017-02-28 01:07:28.492 info requesting all objects hm-rega.0 2017-02-28 01:07:28.824 info starting. Version 1.4.3 in /opt/iobroker/node_modules/iobroker.hm-rega, node: v4.7.3 admin.0 2017-02-28 01:07:28.487 info requesting all states hm-rega.0 2017-02-28 01:07:28.210 info States connected to redis 127.0.0.1:6379 admin.0 2017-02-28 01:07:28.133 info starting. Version 1.6.12 in /opt/iobroker/node_modules/iobroker.admin, node: v4.7.3 hm-rpc.0 2017-02-28 01:07:26.609 info Connected admin.0 2017-02-28 01:07:26.384 info States connected to redis 127.0.0.1:6379 sql.0 2017-02-28 01:07:26.332 info Connected to mysql sql.0 2017-02-28 01:07:25.989 info enabled logging of javascript.0.Solar.Sonnenstand.RSmax sql.0 2017-02-28 01:07:25.974 info enabled logging of javascript.0.Solar.Sonnenstand.PanelSimulate sql.0 2017-02-28 01:07:25.973 info enabled logging of javascript.0.Solar.Schneider.Inv1Export_kWh_d sql.0 2017-02-28 01:07:25.972 info enabled logging of javascript.0.Solar.Schneider.Inv1Import_kWh_d sql.0 2017-02-28 01:07:25.971 info enabled logging of javascript.0.Solar.Schneider.HausExport_kWh_d sql.0 2017-02-28 01:07:25.970 info enabled logging of javascript.0.Solar.Schneider.HausImport_kWh_d sql.0 2017-02-28 01:07:25.969 info enabled logging of hm-rpc.0.MEQ0350841.2.POWER sql.0 2017-02-28 01:07:25.946 info enabled logging of hm-rpc.0.MEQ0350837.2.POWER sql.0 2017-02-28 01:07:25.944 info enabled logging of javascript.0.Solar.Sonnenstand.RSmin sql.0 2017-02-28 01:07:25.943 info enabled logging of javascript.0.Solar.Sonnenstand.PanelPossible sql.0 2017-02-28 01:07:25.914 info enabled logging of javascript.0.Solar.Sonnenstand.Elevation sql.0 2017-02-28 01:07:25.913 info enabled logging of javascript.0.Solar.Haus.HausExport sql.0 2017-02-28 01:07:25.911 info enabled logging of javascript.0.Solar.Haus.HausImport sql.0 2017-02-28 01:07:25.910 info enabled logging of javascript.0.Solar.Haus.Verbrauch sql.0 2017-02-28 01:07:25.909 info enabled logging of javascript.0.Solar.Haus.VerbrauchL3 sql.0 2017-02-28 01:07:25.907 info enabled logging of javascript.0.Solar.Haus.VerbrauchL2 sql.0 2017-02-28 01:07:25.906 info enabled logging of javascript.0.Solar.Haus.VerbrauchL1 sql.0 2017-02-28 01:07:25.903 info enabled logging of javascript.0.Solar.Schneider.Inv1Power sql.0 2017-02-28 01:07:25.883 info enabled logging of javascript.0.Solar.Schneider.HausPower hm-rpc.0 2017-02-28 01:07:25.854 info binrpc -> 94 devices hm-rpc.0 2017-02-28 01:07:25.672 info binrpc <- listDevices ['hm-rpc.0'] hm-rpc.0 2017-02-28 01:07:25.596 info binrpc <- system.listMethods ['hm-rpc.0'] hm-rpc.0 2017-02-28 01:07:25.262 info binrpc client is trying to connect to 192.168.1.90:2001 with ['xmlrpc_bin://192.168.1.121:2001','hm-rpc.0'] hm-rpc.0 2017-02-28 01:07:25.260 info binrpc server is trying to listen on 192.168.1.121:2001 hm-rpc.0 2017-02-28 01:07:23.679 info starting. Version 1.4.2 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v4.7.3 vis.0 2017-02-28 01:07:23.472 info starting. Version 0.10.15 in /opt/iobroker/node_modules/iobroker.vis, node: v4.7.3 sql.0 2017-02-28 01:07:23.479 info starting. Version 1.4.6 in /opt/iobroker/node_modules/iobroker.sql, node: v4.7.3 hm-rpc.0 2017-02-28 01:07:23.220 info States connected to redis 127.0.0.1:6379 vis.0 2017-02-28 01:07:23.180 info States connected to redis 127.0.0.1:6379 sql.0 2017-02-28 01:07:23.170 info States connected to redis 127.0.0.1:6379 host.raspi3 2017-02-28 01:07:21.800 info instance system.adapter.hm-rega.0 started with pid 11900 web.0 2017-02-28 01:07:17.778 info 2017-02-28T00:07:17.778Z Connected system.user.admin web.0 2017-02-28 01:07:17.745 info 2017-02-28T00:07:17.744Z Connected system.user.admin host.raspi3 2017-02-28 01:07:16.726 info instance system.adapter.hm-rpc.0 started with pid 11851 host.raspi3 2017-02-28 01:07:16.103 info instance system.adapter.admin.0 started with pid 11845 sonos.0 2017-02-28 01:07:15.629 info http sonos server listening on port 8083 sonos.0 2017-02-28 01:07:15.035 info starting. Version 1.4.2 in /opt/iobroker/node_modules/iobroker.sonos, node: v4.7.3 sonos.0 2017-02-28 01:07:14.910 info States connected to redis 127.0.0.1:6379 sonos.0 2017-02-28 01:07:14.439 error no connection to objects DB javascript.0 2017-02-28 01:07:11.947 info script.js.common._Solar.Poll_Modbus: registered 0 subscriptions and 5 schedules javascript.0 2017-02-28 01:07:11.944 warn script.js.common._Solar.Poll_Modbus: Script Poll_Modbus; Script ist gestarted javascript.0 2017-02-28 01:07:11.868 info Start javascript script.js.common._Solar.Poll_Modbus javascript.0 2017-02-28 01:07:11.853 info script.js.common.test1.a_SayIt2_test: registered 1 subscription and 0 schedules javascript.0 2017-02-28 01:07:11.844 info Start javascript script.js.common.test1.a_SayIt2_test javascript.0 2017-02-28 01:07:11.841 info script.js.common._Diverses.a_Roku_test: registered 1 subscription and 0 schedules javascript.0 2017-02-28 01:07:11.799 info Start javascript script.js.common._Diverses.a_Roku_test javascript.0 2017-02-28 01:07:11.783 info script.js.common._Keller.Strom-Tarif: registered 0 subscriptions and 4 schedules javascript.0 2017-02-28 01:07:11.606 info Start javascript script.js.common._Keller.Strom-Tarif javascript.0 2017-02-28 01:07:11.586 info script.js.common._Solar.Sonnenstand: registered 0 subscriptions and 1 schedule javascript.0 2017-02-28 01:07:11.360 info Start javascript script.js.common._Solar.Sonnenstand javascript.0 2017-02-28 01:07:11.352 info script.js.common._Keller.Keller-Geräte: registered 4 subscriptions and 0 schedules fakeroku.0 2017-02-28 01:07:11.670 info starting. Version 0.2.1 in /opt/iobroker/node_modules/iobroker.fakeroku, node: v4.7.3 fakeroku.0 2017-02-28 01:07:11.414 info States connected to redis 127.0.0.1:6379 host.raspi3 2017-02-28 01:07:11.505 info instance system.adapter.sql.0 started with pid 11787 javascript.0 2017-02-28 01:07:11.275 info Start javascript script.js.common._Keller.Keller-Geräte web.0 2017-02-28 01:07:11.244 info 2017-02-28T00:07:11.244Z Connected system.user.admin web.0 2017-02-28 01:07:11.231 info 2017-02-28T00:07:11.231Z Connected system.user.admin web.0 2017-02-28 01:07:11.191 info 2017-02-28T00:07:11.190Z Connected system.user.admin javascript.0 2017-02-28 01:07:10.909 info received all objects web.0 2017-02-28 01:07:08.834 info http server listening on port 8082 web.0 2017-02-28 01:07:08.825 info socket.io server listening on port 8082 host.raspi3 2017-02-28 01:07:07.496 info instance system.adapter.fakeroku.0 started with pid 11735 javascript.0 2017-02-28 01:07:07.273 info received all states web.0 2017-02-28 01:07:06.296 info starting. Version 2.0.2 in /opt/iobroker/node_modules/iobroker.web, node: v4.7.3 web.0 2017-02-28 01:07:05.692 info States connected to redis 127.0.0.1:6379 host.raspi3 2017-02-28 01:07:05.258 info instance system.adapter.sonos.0 started with pid 11725 harmony.0 2017-02-28 01:07:02.980 info synced hub config harmony.0 2017-02-28 01:07:01.690 info connected to Harmony Hub YK javascript.0 2017-02-28 01:07:00.700 info requesting all objects javascript.0 2017-02-28 01:07:00.694 info requesting all states javascript.0 2017-02-28 01:07:00.672 info starting. Version 3.2.6 in /opt/iobroker/node_modules/iobroker.javascript, node: v4.7.3 javascript.0 2017-02-28 01:07:00.545 info States connected to redis 127.0.0.1:6379 host.raspi3 2017-02-28 01:06:59.481 info instance system.adapter.web.0 started with pid 11714 harmony.0 2017-02-28 01:06:58.977 info connecting to Harmony Hub YK harmony.0 2017-02-28 01:06:58.599 info discovered Harmony Hub YK harmony.0 2017-02-28 01:06:57.345 info searching for Harmony Hubs... harmony.0 2017-02-28 01:06:57.271 info starting. Version 0.7.0 in /opt/iobroker/node_modules/iobroker.harmony, node: v4.7.3 harmony.0 2017-02-28 01:06:57.137 info States connected to redis 127.0.0.1:6379 host.raspi3 2017-02-28 01:06:55.490 info instance system.adapter.javascript.0 started with pid 11661 host.raspi3 2017-02-28 01:06:51.483 info instance system.adapter.harmony.0 started with pid 11613 host.raspi3 2017-02-28 01:06:50.384 info Restart adapter system.adapter.hm-rega.0 because enabled host.raspi3 2017-02-28 01:06:50.383 error instance system.adapter.hm-rega.0 terminated with code 7 (Adapter already running) host.raspi3 2017-02-28 01:06:47.490 info instance system.adapter.hm-rega.0 started with pid 11603 host.raspi3 2017-02-28 01:06:46.638 info Restart adapter system.adapter.hm-rpc.0 because enabled host.raspi3 2017-02-28 01:06:46.637 error instance system.adapter.hm-rpc.0 terminated with code 7 (Adapter already running) host.raspi3 2017-02-28 01:06:45.947 info Restart adapter system.adapter.admin.0 because enabled host.raspi3 2017-02-28 01:06:45.944 error instance system.adapter.admin.0 terminated with code 7 (Adapter already running) host.raspi3 2017-02-28 01:06:43.483 info instance system.adapter.hm-rpc.0 started with pid 11588 host.raspi3 2017-02-28 01:06:39.612 info instance system.adapter.admin.0 started with pid 11540 host.raspi3 2017-02-28 01:06:39.513 info States connected to redis 127.0.0.1:6379 host.raspi3 2017-02-28 01:06:39.451 info starting 29 instances host.raspi3 2017-02-28 01:06:39.400 info 40 instances found host.raspi3 2017-02-28 01:06:39.253 info InMemoryDB connected host.raspi3 2017-02-28 01:06:39.218 info inMem-objects listening on port 9001 host.raspi3 2017-02-28 01:06:37.917 info ip addresses: 192.168.1.121 2a02:1205:502b:62b0:e66e:34e2:893d:6c57 fe80::41e2:25df:9a34:b721 host.raspi3 2017-02-28 01:06:37.914 info hostname: raspi3, node: v4.7.3 host.raspi3 2017-02-28 01:06:37.912 info Copyright (c) 2014-2016 bluefox, hobbyquaker host.raspi3 2017-02-28 01:06:37.886 info iobroker.js-controller version 0.16.1 js-controller starting host.raspi3 2017-02-28 01:06:32.488 info terminated host.raspi3 2017-02-28 01:06:32.398 info instance system.adapter.admin.0 started with pid 11399 host.raspi3 2017-02-28 01:06:32.305 info States connected to redis 127.0.0.1:6379 host.raspi3 2017-02-28 01:06:32.241 info starting 29 instances host.raspi3 2017-02-28 01:06:32.179 info 40 instances found host.raspi3 2017-02-28 01:06:32.021 info InMemoryDB connected iobroker 2017-02-28 01:06:31.978 info _restart uncaught 2017-02-28 01:06:31.956 error exception: listen EADDRINUSE :::9001 Another 2017-02-28 01:06:31.955 error instance is running or some application uses port! host.raspi3 2017-02-28 01:06:31.919 info inMem-objects listening on port 9001 host.raspi3 2017-02-28 01:06:30.410 info ip addresses: 192.168.1.121 2a02:1205:502b:62b0:e66e:34e2:893d:6c57 fe80::41e2:25df:9a34:b721 host.raspi3 2017-02-28 01:06:30.407 info hostname: raspi3, node: v4.7.3 host.raspi3 2017-02-28 01:06:30.404 info Copyright (c) 2014-2016 bluefox, hobbyquaker host.raspi3 2017-02-28 01:06:30.377 info iobroker.js-controller version 0.16.1 js-controller starting admin.0 2017-02-28 01:05:13.266 info Repository received successfully. host.raspi3 2017-02-28 01:04:19.495 info Update repository 'online' under 'https://raw.githubusercontent.com/ioBroker/ioBroker.js-controller/master/conf/sources-dist.json' admin.0 2017-02-28 01:04:18.454 info received all objects admin.0 2017-02-28 01:04:15.833 info received all states admin.0 2017-02-28 01:04:11.676 info system.adapter.admin.0: logging true fakeroku.0 2017-02-28 01:04:11.691 info system.adapter.admin.0: logging true admin.0 2017-02-28 01:04:11.674 info system.adapter.admin.0: logging true javascript.0 2017-02-28 01:04:11.665 info system.adapter.admin.0: logging true javascript.0 2017-02-28 01:04:11.663 info system.adapter.admin.0: logging true hm-rega.0 2017-02-28 01:04:11.643 info system.adapter.admin.0: logging true sql.0 2017-02-28 01:04:11.646 info system.adapter.admin.0: logging true upnp.0 2017-02-28 01:04:11.646 info system.adapter.admin.0: logging true web.0 2017-02-28 01:04:11.643 info system.adapter.admin.0: logging true harmony.0 2017-02-28 01:04:11.647 info system.adapter.admin.0: logging true web.0 2017-02-28 01:04:11.642 info system.adapter.admin.0: logging true sayit.0 2017-02-28 01:04:11.646 info system.adapter.admin.0: logging true sayit.1 2017-02-28 01:04:11.647 info system.adapter.admin.0: logging true sonos.0 2017-02-28 01:04:11.642 info system.adapter.admin.0: logging true hm-rpc.0 2017-02-28 01:04:11.642 info system.adapter.admin.0: logging true admin.0 2017-02-28 01:04:11.608 info Change log subscriber state: true admin.0 2017-02-28 01:04:08.843 info Use link 'http://localhost:8081' to configure. admin.0 2017-02-28 01:04:08.842 info http server listening on port 8081 admin.0 2017-02-28 01:04:08.836 info Request actual repository... admin.0 2017-02-28 01:04:08.833 info requesting all objects admin.0 2017-02-28 01:04:08.828 info requesting all states admin.0 2017-02-28 01:04:08.617 info starting. Version 1.6.12 in /opt/iobroker/node_modules/iobroker.admin, node: v4.7.3 admin.0 2017-02-28 01:04:08.471 info States connected to redis 127.0.0.1:6379 host.raspi3 2017-02-28 01:04:00.669 info instance system.adapter.admin.0 started with pid 10473 fakeroku.0 2017-02-28 01:03:59.180 info system.adapter.admin.0: logging false hm-rega.0 2017-02-28 01:03:58.818 info system.adapter.admin.0: logging false sonos.0 2017-02-28 01:03:58.751 info system.adapter.admin.0: logging false hm-rpc.0 2017-02-28 01:03:58.541 info system.adapter.admin.0: logging false web.0 2017-02-28 01:03:58.590 info system.adapter.admin.0: logging false -
uncaught 2017-02-28 01:06:31.956 error exception: listen EADDRINUSE :::9001 Another 2017-02-28 01:06:31.955 error instance is running or some application uses port!Deine alte Version lief noch.
-
Bei mir läuft Admin danach auch nicht mehr.
-
Admin vom Github auch aktualisiert?
-
Jetzt ja. JS-Controller läuft ohne Probleme.
-
Hallo BF,
ich habe beides (admin und js-controller) upgedatet. Es läuft alles wie geschmiert. Und ich möchte an dieser Stelle auch mal betonen, dass ich seit bestimmt einem Jahr alle meine Updates über die Admin-Oberfläche starte und nicht über die Konsole. Das funktioniert einwandfrei. Großes Kompliment!!
Jetzt sind ja auch die events zu sehen und da hab ich direkt eine Farge bzw. auch einen Wunsch.
Frage: gibt es die Möglichkeit ALLE in/out Events kumuliert zu sehen, oder kann man das irgendwie berechnen lassen??
Wunsch: Ähnlich dem Task Manager von Windows per Klick auf die Spaltenüberschriften die Adapterzeilen so neu zu sortieren, sodass man die Möglichkeit hätte, die mit dem höchsten Transaktionszahlen, bzw. die mit dem größten Speicherverbrauch nach Oben zu holen
Ansonsten sehe ich derzeit, dass mein System in Summe grob geschätzt etwa 4000-5000 "in"-Events und ca 1500 "out"-Events anzeigt. Auch wenn ich das noch nicht richtig deuten kann (Hier wäre etwas Interpretationshilfe toll) reicht es allemal, dass ich mit den Einstellungen die Du mit dem 0.16.1 js-controller auslieferst ständig "too many events" angezeigt bekomme. Den Wert werde ich jetzt mal hochsetzen.
-
Ja, zu den Events würde ich mir auch etwas Interpretationshilfe wünschen. Ich kann mir noch nicht so ganz einen Reim drauf machen was die aussagen…
-
So, auch ich habe das Update vom Controller und Admin gemacht. Alles läuft, genaue Tests werden im Praxisbetrieb folgen.
Lg
Günther
-
Update vom Master durchgeführt. Funktioniert.
ubuntu 16.04
Update über die Weboberfläche durchgeführt
Da reinstall.sh Skript hätte ich vorher gebraucht
Mein Fehler. Hatte mir einen Satelliten beim Upgrade von node von 4.x auf 6.x zerschossen.Mit input/output kann ich noch nicht viel anfangen.
-
Jeder Adapter empfängt und sendet updates für States. E.g. neue Temperatur oder noch irgendwas.
Da wird gezählt wie viele Ereignisse bekommt (oder generiert) ein oder anderer Adapter.
Ich erwarte, dass Javascript viel bekommen sollte (input) und hm-rpc viel generieren (output) o.ä.
-
Für welchen Zeitraum gelten denn die angezeigten Ereignisse?
-
Ich habe einen der Satelliten ebenfalls hochgezogen.
Ich vermute mal das es In/ und Output um Werte je Sekunde geht.
Output steht bei beiden Hosts fest auf 10 und Input schwankt um die 50.
Vom Bauch her würde ich sagen, dass das nicht plausibel klingt.
-
Habe das Testsystem auch auf die neuen Versionen gebracht. Ohne manuelle Installation (außerhalb vom web admin) und iobroker stop/start ging's leider nicht auf dem node 4.8 System.
Egal, die Ereignisse sind interessant. Hab rausgefunden dass das untere Limit von den 'out' 8 ist, also scheinen das die Adapter-Statusereignisse sein. Wollte eigentlich schon immer mal fragen ob man das nicht abstellen kann!
Ich will entscheiden können ob ich solche
! ````
stateChange system.adapter.sql.1.memRss 49.77 true sql.1 2017-03-02 00:12:27.625 2017-03-02 00:11:42.603
stateChange system.adapter.sql.1.connected true true sql.1 2017-03-02 00:12:27.622 2017-02-28 23:21:04.985
stateChange system.adapter.sql.1.alive true true sql.1 2017-03-02 00:12:27.612 2017-02-28 23:21:04.974
stateChange javascript.0.StateMachine_test.mPrint 116 false javascript.0 2017-03-02 00:12:25.573 2017-03-02 00:12:25.573
stateChange system.adapter.web.0.outputCount 8 true web.0 2017-03-02 00:12:24.261 2017-03-02 00:01:23.907
stateChange system.adapter.web.0.inputCount 80 true web.0 2017-03-02 00:12:24.260 2017-03-02 00:12:24.260
stateChange system.adapter.web.0.uptime 89518 true web.0 2017-03-02 00:12:24.258 2017-03-02 00:12:24.258
stateChange system.adapter.web.0.memHeapUsed 13.98 true web.0 2017-03-02 00:12:24.255 2017-03-02 00:12:24.255
stateChange system.adapter.web.0.memHeapTotal 17.39 true web.0 2017-03-02 00:12:24.242 2017-03-02 00:10:24.178
stateChange system.adapter.web.0.memRss 37.64 true web.0 2017-03-02 00:12:24.240 2017-03-02 00:12:24.240
stateChange system.adapter.web.0.connected true true web.0 2017-03-02 00:12:24.237 2017-02-28 23:20:29.813
stateChange system.adapter.web.0.alive true true web.0 2017-03-02 00:12:24.231 2017-02-28 23:20:29.809
stateChange rpi2.0.gpio.26.state false true rpi2.0 2017-03-02 00:12:22.804 2017-03-02 00:11:55.783
stateChange rpi2.0.gpio.26.state false false javascript.0 2017-03-02 00:12:22.792 2017-03-02 00:11:55.783
stateChange javascript.0.StateMachine_test.Led 0 false javascript.0 2017-03-02 00:12:22.725 2017-03-02 00:12:22.725
stateChange javascript.0.StateMachine_test.mPrint 115 false javascript.0 2017-03-02 00:12:22.673 2017-03-02 00:12:22.673
stateDann hab ich da noch einen Javascript-Adapter auf dem ich eines meiner (bald zu veröffentlichten) Projekte entwickle. Er zeigt >60 Ereignisse am in und ich weiß genau dass da nur alle 5-20 Sekunden ein Ereignis daherkommt. also warum werden dann so viele gezählt? Etwas verwirrend und eine klare Definition würde helfen. -
Das ist die Anzahl von Ereignissen in 30 Sekunden und wenn da 60 steht, dass heißt 2 Ereignisse pro Sekunde.
Die Ereignisse werden schon richtig gezählt. Die Basis Ereignisse 8 sind natürlich nicht alle nötig, aber 5 sind wichtig. Und wenn schon 5 da sind dann machen 8 in 30 Sekunden nicht so viel aus.
-
@fsjoke:Habe das Testsystem auch auf die neuen Versionen gebracht. Ohne manuelle Installation (außerhalb vom web admin) und iobroker stop/start ging's leider nicht auf dem node 4.8 System.
Egal, die Ereignisse sind interessant. Hab rausgefunden dass das untere Limit von den 'out' 8 ist, also scheinen das die Adapter-Statusereignisse sein. Wollte eigentlich schon immer mal fragen ob man das nicht abstellen kann!
Ich will entscheiden können ob ich solche
! ````
stateChange system.adapter.sql.1.memRss 49.77 true sql.1 2017-03-02 00:12:27.625 2017-03-02 00:11:42.603
stateChange system.adapter.sql.1.connected true true sql.1 2017-03-02 00:12:27.622 2017-02-28 23:21:04.985
stateChange system.adapter.sql.1.alive true true sql.1 2017-03-02 00:12:27.612 2017-02-28 23:21:04.974
stateChange javascript.0.StateMachine_test.mPrint 116 false javascript.0 2017-03-02 00:12:25.573 2017-03-02 00:12:25.573
stateChange system.adapter.web.0.outputCount 8 true web.0 2017-03-02 00:12:24.261 2017-03-02 00:01:23.907
stateChange system.adapter.web.0.inputCount 80 true web.0 2017-03-02 00:12:24.260 2017-03-02 00:12:24.260
stateChange system.adapter.web.0.uptime 89518 true web.0 2017-03-02 00:12:24.258 2017-03-02 00:12:24.258
stateChange system.adapter.web.0.memHeapUsed 13.98 true web.0 2017-03-02 00:12:24.255 2017-03-02 00:12:24.255
stateChange system.adapter.web.0.memHeapTotal 17.39 true web.0 2017-03-02 00:12:24.242 2017-03-02 00:10:24.178
stateChange system.adapter.web.0.memRss 37.64 true web.0 2017-03-02 00:12:24.240 2017-03-02 00:12:24.240
stateChange system.adapter.web.0.connected true true web.0 2017-03-02 00:12:24.237 2017-02-28 23:20:29.813
stateChange system.adapter.web.0.alive true true web.0 2017-03-02 00:12:24.231 2017-02-28 23:20:29.809
stateChange rpi2.0.gpio.26.state false true rpi2.0 2017-03-02 00:12:22.804 2017-03-02 00:11:55.783
stateChange rpi2.0.gpio.26.state false false javascript.0 2017-03-02 00:12:22.792 2017-03-02 00:11:55.783
stateChange javascript.0.StateMachine_test.Led 0 false javascript.0 2017-03-02 00:12:22.725 2017-03-02 00:12:22.725
stateChange javascript.0.StateMachine_test.mPrint 115 false javascript.0 2017-03-02 00:12:22.673 2017-03-02 00:12:22.673
stateDann hab ich da noch einen Javascript-Adapter auf dem ich eines meiner (bald zu veröffentlichten) Projekte entwickle. Er zeigt >60 Ereignisse am in und ich weiß genau dass da nur alle 5-20 Sekunden ein Ereignis daherkommt. also warum werden dann so viele gezählt? Etwas verwirrend und eine klare Definition würde helfen. `Javascript ist default massig an alle Ereignisse unterschreiben. Das heißt dein System hat Grundlast von 2 Ereignisse pro Sekunde. Gar nicht so viel.
Man kann dieses Wert auch verbessern in dem man Optimierung…. in Javascript einschaltet.
Man wird aber nicht können das Wert so zu lesen
getStste ('id').valSondern nur so
getState ('id', function (err,state){ state.val }) -
Das ist die Anzahl von Ereignissen in 30 Sekunden und wenn da 60 steht, dass heißt 2 Ereignisse pro Sekunde.
Die Ereignisse werden schon richtig gezählt. Die Basis Ereignisse 8 sind natürlich nicht alle nötig, aber 5 sind wichtig. Und wenn schon 5 da sind dann machen 8 in 30 Sekunden nicht so viel aus. `
Danke für die Erklärung - jetzt kann ich mir was drunter vorstellen. Dann hab ich allerdings mit jeweils durchschnittlich 10 bis in der Spitze auch mal 20 Ereignissen in 2 Javascript- und einem SQL-Adapter ganz schön viele - oder? Gibt's da sowas wie eine kritische Grenze?
