Probleme mit node-red
-
Hallo,
vielleicht habe ich die Ursache der aktuellen Probleme mit Node-Red gefunden.
Auch bei mir hat sich Node-Red in eine gelegentliche Endlosschreife mit Neustarts begeben. Ich hab dann letzte Nacht node.js zurück auf 10.22 versetzt und dann mehrmals den Node-Red-Adapter neu installiert. Ohne dauerhaften Erfolg.
Im Log sah das dann so aus:
node-red-0 2015-08-13 19:31:18 info Starting node-red: --max-old-space-size=256 /opt/iobroker/node_modules/iobroker.node-red/node_modules/node-red/red.js -v --settings /opt/iobroker/iobroker-data/node-red/settings.js node-red-0 2015-08-13 19:31:13 info node-red exited with 1 node-red-0 2015-08-13 19:30:53 info Starting node-red: --max-old-space-size=256 /opt/iobroker/node_modules/iobroker.node-red/node_modules/node-red/red.js -v --settings /opt/iobroker/iobroker-data/node-red/settings.js node-red-0 2015-08-13 19:30:48 info node-red exited with 1 node-red-0 2015-08-13 19:30:28 info Starting node-red: --max-old-space-size=256 /opt/iobroker/node_modules/iobroker.node-red/node_modules/node-red/red.js -v --settings /opt/iobroker/iobroker-data/node-red/settings.js node-red-0 2015-08-13 19:30:27 info starting. Version 0.3.4 in /opt/iobroker/node_modules/iobroker.node-red host-raspberrypi 2015-08-13 19:30:24 info instance system.adapter.node-red.0 started with pid 9845Ich hab zum Test dann mal Nod-Red manuell gestartet:
node /opt/iobroker/node_modules/iobroker.node-red/node_modules/node-red/red.js -v --settings /opt/iobroker/iobroker-data/node-red/settings.jsDann kam folgendes:
`Welcome to Node-RED =================== 13 Aug 18:12:52 - [info] Node-RED version: v0.11.1 13 Aug 18:12:52 - [info] Node.js version: v0.10.22 13 Aug 18:12:52 - [info] Loading palette nodes 13 Aug 18:13:01 - [info] Settings file : /opt/iobroker/iobroker-data/node-red/settings.js 13 Aug 18:13:01 - [info] User directory : /opt/iobroker/iobroker-data/node-red/ 13 Aug 18:13:01 - [info] Flows file : /opt/iobroker/iobroker-data/node-red/flows.json 13 Aug 18:13:01 - [info] Server now running at http://127.0.0.1:1880/ 13 Aug 18:13:01 - [info] Starting flows 13 Aug 18:13:01 - [info] [inject:Start] repeat = 300000 13 Aug 18:13:02 - [info] [inject:6e7c85c0.91837c] repeat = 600000 13 Aug 18:13:02 - [info] [inject:9e79eb46.618618] repeat = 900000 13 Aug 18:13:03 - [info] [inject:ce490b03.31b6f8] repeat = 172800000 13 Aug 18:13:03 - [info] [inject:f3c893c6.0c377] repeat = 1200000 13 Aug 18:13:05 - [info] [inject:Abfrage Spritpreise] repeat = 600000 13 Aug 18:13:08 - [info] Started flows 13 Aug 18:13:08 - [info] [rpi-gpio in:Ebene 1] out: 1 : 13 Aug 18:13:08 - [info] [rpi-gpio in:Ebene 2] out: 0 : 13 Aug 18:13:08 - [info] [rpi-gpio in:Ebene 3] out: 0 : 13 Aug 18:13:08 - [red] Uncaught Exception: 13 Aug 18:13:08 - Error: ENOENT, open '[b]/opt/iobroker/opt/iobroker/log/iobroker.log.2015-08-13[/b]'` Da der Logfile-Pfad nicht stimmt, hat sich Node-Red einfach beim ersten Versuch einen Fehler direkt zu schreiben verabschiedet. Ich hab jetzt die folgenden Änderungen in der settings.js unter /opt/iobroker/node_modules/iobroker.node-red/node_modules/node-red vorgenommen: `~~[code]~~ //iobrokerConfig: '%%config%%', iobrokerConfig: {"network":{"IPv4":true,"IPv6":true,"bindAddress":null,"useSystemNpm":true},"objects":{"type":"file","typeComment":"Possible values: 'file' - [port 9001], redis - [port 6379], couch - [port 5984].","host":"127.0.0.1","port":9001,"user":"","pass":"","noFileCache":false,"dataDir":"../../iobroker-data/"},"states":{"type":"file","typeComment":"Possible values: 'file' - [port 9000], 'redis' - [port 6379].","host":"127.0.0.1","port":9000,"options":{"auth_pass":null,"retry_max_delay":15000},"dataDir":"../../iobroker-data/"},"log":{"level":"info","maxDays":7,"transport":{"file1":{"type":"file","enabled":true,"filename":"log/iobroker.log","maxsize":null,"maxFiles":null,"label":"","level":"info","json":false,"silent":false,"colorize":true,"datePattern":".yyyy-MM-dd"}}},"dataDirComment":"Always relative to iobroker.js-controller/"}, [/code]` Nun startet der Adapter und Node-Red wieder. Die Stelle, wo die Variable %%config%% gesetzt wird, hab ich noch nicht gesucht/gefunden. Der Grund für den Log-Eintrag ist übrigens, das Node-Red nicht auf die states.db zugreifen kann. gehört die zu node-red oder zu iobroker? `~~[code]~~node-red-0 2015-08-13 19:35:10 error no connection to states DB node-red-0 2015-08-13 19:34:50 info Starting node-red: --max-old-space-size=256 /opt/iobroker/node_modules/iobroker.node-red/node_modules/node-red/red.js -v --settings /opt/iobroker/iobroker-data/node-red/settings.js node-red-0 2015-08-13 19:34:49 info starting. Version 0.3.4 in /opt/iobroker/node_modules/iobroker.node-red host-raspberrypi 2015-08-13 19:34:47 info instance system.adapter.node-red.0 started with pid 11710[/code]` host-raspberrypi 2015-08-13 19:34:47 info "system.adapter.node-red.0" enabled[/red] -
Bitte alle, die das Problem mit node-red haben: Versuchen auf die neueste Version upzudaten
cd /opt/iobroker iobroker stop npm install https://github.com/ioBroker/ioBroker.js-controller/tarball/master iobroker start -
Jetzt bin ich aber verwirrt:
` > root@quad-pi:~# cd /opt/iobrokerroot@quad-pi:/opt/iobroker# iobroker stop
ioBroker controller daemon is not running
root@quad-pi:/opt/iobroker# npm install https://github.com/ioBroker/ioBroker.js- controller/tarball/master
npm http GET https://github.com/ioBroker/ioBroker.js … all/master `
Dabei läuft die WebUI auch jetzt noch einwandfrei!
top zeigt an:
` > 2454 root 20 0 189m 137m 8716 S 10,9 14,9 260:26.92 io.js-controlle2460 root 20 0 99620 56m 8500 S 4,9 6,1 102:15.66 io.admin.0 `
nach iobroker start gab es kein Error, aber:
29514 root 20 0 35620 14m 8332 R 38,5 1,6 0:01.17 io.js-controlle 2454 root 20 0 197m 146m 8716 S 34,2 15,8 260:49.15 io.js-controlle 29507 root 20 0 33172 10m 7336 S 26,0 1,1 0:00.79 nodeselbst ein restart über dien Tab hosts änderte nichts an zwei laufenden controllern.
Dann erschien die 0.7.8
jetzt läuft der reboot
Danach nur noch ein controller.
node-red läuft.
haben sich die Pfade geändert?
ich bekomme immer noch:
Imported unrecognised types: pushbullet-config pushbulletobwohl ich es neu installiert hatte
siehe oben.
Gruß
Rainer
-
Jetzt bin ich aber verwirrt:
` > root@quad-pi:~# cd /opt/iobrokerroot@quad-pi:/opt/iobroker# iobroker stop
ioBroker controller daemon is not running
root@quad-pi:/opt/iobroker# npm install https://github.com/ioBroker/ioBroker.js- controller/tarball/master
npm http GET https://github.com/ioBroker/ioBroker.js … all/master `
Dabei läuft die WebUI auch jetzt noch einwandfrei!
top zeigt an:
` > 2454 root 20 0 189m 137m 8716 S 10,9 14,9 260:26.92 io.js-controlle2460 root 20 0 99620 56m 8500 S 4,9 6,1 102:15.66 io.admin.0 `
nach iobroker start gab es kein Error, aber:
29514 root 20 0 35620 14m 8332 R 38,5 1,6 0:01.17 io.js-controlle 2454 root 20 0 197m 146m 8716 S 34,2 15,8 260:49.15 io.js-controlle 29507 root 20 0 33172 10m 7336 S 26,0 1,1 0:00.79 nodeselbst ein restart über dien Tab hosts änderte nichts an zwei laufenden controllern.
Dann erschien die 0.7.8
jetzt läuft der reboot
Danach nur noch ein controller.
node-red läuft.
haben sich die Pfade geändert?
ich bekomme immer noch:
Imported unrecognised types: pushbullet-config pushbulletobwohl ich es neu installiert hatte
siehe oben.
Gruß
Rainer `
Du solltest alles als root machen oder mit sudo. Jetzt neu starten. -
Du solltest alles als root machen `
Mach ich immer, bin zu faul mit sudo.Jetzt neu starten. `
habe ich komplett neu gestartet, der pushbullet node bleibt verschollen.Installation war wie folgt (als root!):
root@quad-pi:/opt/iobroker/node_modules/iobroker.node-red/node_modules# npm install node-red-node-pushbullet npm http GET https://registry.npmjs.org/when npm http 304 https://registry.npmjs.org/when node-red-node-pushbullet@0.0.6 node-red-node-pushbullet └── when@3.7.3Die Struktur ist auch vorhanden, die vom log angemeckerte Datei:
node-red-0 2015-08-13 19:04:55 warn 13 Aug 19:04:55 - [warn] ------------------------------------------ node-red-0 2015-08-13 19:04:55 warn 13 Aug 19:04:55 - [warn] [pushbullet] Error: Cannot find module 'qs' node-red-0 2015-08-13 19:04:55 warn 13 Aug 19:04:55 - [warn] ------------------------------------------habe ich jedoch nicht finden können.
Danke
Rainer
-
Verzeichnis ist falsch:
root@quad-pi:/opt/iobroker/node_modules/iobroker.node-red/[color]node_modules[/color]# npm install node-red-node-pushbulletEs muss "/opt/iobroker/node_modules/iobroker.node-red/" sein.
Und vor allem die neueste Version unterstützt, so dass du das konfigurieren kannst. Einfach in "Zusätzliche NPM-Module" "node-red-node-pushbullet" eintragen.
-
Einfach in "Zusätzliche NPM-Module" "node-red-node-pushbullet" eintragen. `
Hatte ich auch probiert, klappte ebenfalls nicht.Muss ich erst das alte löschen?
und wenn ja, wie?
Den Pfad hattest du damals irgendwo im Forum angegeben, und ich habs in die Doku übernommen.
@[url=http://www.iobroker.net/?page_id=166⟨=de:~~Doku"]~~Importieren von weiteren nodes
Auf der Seite von node-red werden weitere nodes angeboten. Dort finden sich dann auch die jeweiligen Installationsanleitungen.
Auf der iobroker-Installation geht man dazu in das node-red Verzeichnis (z.B. auf dem Raspberry2):
/opt/iobroker/node_modules/iobroker.node-red/node_modules
und ruft da den Installationsbefehl von der node-red Website auf, z.B. :
npm install node-red-node-fitbit
Anschließend muss der node-red Adapter neu gestartet werden. Danach steht der neue node zur Verfügung. `
Bis zuletzt hat es auch noch so geklappt.http://www.forum.iobroker.org/viewtopic … 4295#p4289
Sorry für die Mühen
Rainer
-
Ich weiß nicht warum es funktioniert hat. Aber es war definitiv falsch.
Mache bitte folgendes:
cd /opt/iobroker/node_modules/iobroker.node-red sudo rm node_modules/node-red-node-pushbullet/* -R sudo rmdir node_modules/node-red-node-pushbullet npm install node-red-node-pushbullet cd /opt/iobroker/ iobroker restart node-red.0 -
Danke,
aber klappt immer noch nicht.
Die Struktur sieht jetzt so aus:
Sind das noch Reste (von gestern) von der falschen Installation?
Gruß
Rainer
PS lass mal, ich versuche es selber
scheint zwei nodes zu geben:
-
node-pushbullet
-
node-red-node-pushbullet
Vielleicht hatte ich ja vor dem Problem den anderen (?)
-
-
Also es läuft!
Ich hatte schon den node-red-node-pushbullet (wozu die Suche im Forum doch gut ist
)Ich habe nochmals alles gelöscht und nach deiner Anleitung neu installiert - ohne Erfolg
dann wieder gelöscht und nach "meiner" Anleitung in /opt/iobroker/node_modules/iobroker.node-red/node_modules installiert.
Frag mich nicht warum, aber es klappt.
Auch pix hat es nach der Anleitung erfolgreich geschafft.
http://www.forum.iobroker.org/viewtopic.php?f=32&t=621
kann also so falsch nicht sein
EDiT:
Es muss am Löschen der alten Struktur gelegen haben, denn jetzt endete die Installation mit:
node-red-node-pushbullet@0.0.6 node-red-node-pushbullet ├── when@3.7.3 └── pushbullet@1.4.3 (mime@1.2.11, request@2.44.0, websocket@1.0.21) root@quad-pi:/opt/iobroker/node_modules/iobroker.node-red/node_modules#beim letzten mal war da nur "when@3.7.3" und nicht "pushbullet@1.4.3" dabei - außerdem war die Ausführung extrem kurz:
root@quad-pi:/opt/iobroker/node_modules/iobroker.node-red# npm install node-red-node-pushbullet npm http GET https://registry.npmjs.org/node-red-node-pushbullet npm http 304 https://registry.npmjs.org/node-red-node-pushbullet npm http GET https://registry.npmjs.org/when npm http 304 https://registry.npmjs.org/when node-red-node-pushbullet@0.0.6 node_modules/node-red-node-pushbullet └── when@3.7.3diesmal waren es194 Zeilen!
Gruß
Rainer
-
node-red lässt sich nicht mehr aufrufen.
Die fixes von bluefox und der neue js-controller laufen sonst spitze.
Beim Versuch node-red aufzurufen erscheint bei Aufruf über den Tab:
> server hat die Verbindung abgelehntBei Aufruf über <ip>:1880
> ERR_CONNECTION_REFUSED
was wohl das selbe istim log steht:
! ````
2015-08-24 19:18:05.871 - info: host.quad-pi instance system.adapter.node-red.0 started with pid 31808
2015-08-24 19:18:08.643 - debug: node-red.0 objectDB connected
2015-08-24 19:18:08.687 - debug: node-red.0 statesDB connected
2015-08-24 19:18:09.107 - info: node-red.0 starting. Version 0.3.5 in /opt/iobroker/node_modules/iobroker.node-red
2015-08-24 19:18:11.301 - info: node-red.0 Starting node-red: /opt/iobroker/node_modules/iobroker.node-red/node_modules/node-red/red.js -v --settings /opt/iobroker/iobroker-data/node-red/settings.js
2015-08-24 19:18:15.638 - debug: node-red.0 Unable to load settings file: /opt/iobroker/iobroker-data/node-red/settings.js
! 2015-08-24 19:18:15.671 - info: node-red.0 node-red exited with 0
2015-08-24 19:18:20.674 - info: node-red.0 Starting node-red: /opt/iobroker/node_modules/iobroker.node-red/node_modules/node-red/red.js -v --settings /opt/iobroker/iobroker-data/node-red/settings.js
2015-08-24 19:18:25.132 - debug: node-red.0 Unable to load settings file: /opt/iobroker/iobroker-data/node-red/settings.jsund das geht immer so weiter Die datei /opt/iobroker/iobroker-data/node-red/settings.js ist vorhanden und hat die Rechte 777 Gruß Rainer iobroker auf RasPi 2 RaspBian vom 05.05.2015 js-controller 0.7.11 node-red 0.3.5 WIN7 Home mit Chrome</ip> -
node-red lässt sich nicht mehr aufrufen.
Die fixes von bluefox und der neue js-controller laufen sonst spitze.
Beim Versuch node-red aufzurufen erscheint bei Aufruf über den Tab:
> server hat die Verbindung abgelehntBei Aufruf über <ip>:1880
> ERR_CONNECTION_REFUSED
was wohl das selbe istim log steht:
! ````
2015-08-24 19:18:05.871 - info: host.quad-pi instance system.adapter.node-red.0 started with pid 31808
2015-08-24 19:18:08.643 - debug: node-red.0 objectDB connected
2015-08-24 19:18:08.687 - debug: node-red.0 statesDB connected
2015-08-24 19:18:09.107 - info: node-red.0 starting. Version 0.3.5 in /opt/iobroker/node_modules/iobroker.node-red
2015-08-24 19:18:11.301 - info: node-red.0 Starting node-red: /opt/iobroker/node_modules/iobroker.node-red/node_modules/node-red/red.js -v --settings /opt/iobroker/iobroker-data/node-red/settings.js
2015-08-24 19:18:15.638 - debug: node-red.0 Unable to load settings file: /opt/iobroker/iobroker-data/node-red/settings.js
! 2015-08-24 19:18:15.671 - info: node-red.0 node-red exited with 0
2015-08-24 19:18:20.674 - info: node-red.0 Starting node-red: /opt/iobroker/node_modules/iobroker.node-red/node_modules/node-red/red.js -v --settings /opt/iobroker/iobroker-data/node-red/settings.js
2015-08-24 19:18:25.132 - debug: node-red.0 Unable to load settings file: /opt/iobroker/iobroker-data/node-red/settings.jsund das geht immer so weiter Die datei /opt/iobroker/iobroker-data/node-red/settings.js ist vorhanden und hat die Rechte 777 Gruß Rainer iobroker auf RasPi 2 RaspBian vom 05.05.2015 js-controller 0.7.11 node-red 0.3.5 WIN7 Home mit Chrome</ip> `Hast du zusätzliche Module in Settings?
-
Hast du zusätzliche Module in Settings? `
Ja!node-pushbullet
Gruß
Rainer
EDIT:
Ohne läufts auch nicht!
EDIT2:
ist aber bereits installiert:
/opt/iobroker/node_modules/iobroker.node-red/node_modules/node-pushbullet -
-
Heute nicht mehr
Gesendet von meinem LIFETAB_S785X mit Tapatalk
-
Hier:
/** * Copyright 2013 IBM Corp. * * Licensed under the Apache License, Version 2.0 (the "License"); * you may not use this file except in compliance with the License. * You may obtain a copy of the License at * * http://www.apache.org/licenses/LICENSE-2.0 * * Unless required by applicable law or agreed to in writing, software * distributed under the License is distributed on an "AS IS" BASIS, * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. * See the License for the specific language governing permissions and * limitations under the License. **/ // The `https` setting requires the `fs` module. Uncomment the following // to make it available: //var fs = require("fs"); module.exports = { // the tcp port that the Node-RED web server is listening on uiPort: '%%port%%', // By default, the Node-RED UI accepts connections on all IPv4 interfaces. // The following property can be used to listen on a specific interface. For // example, the following would only allow connections from the local machine. //uiHost: "127.0.0.1", iobrokerInstance: '%%instance%%', iobrokerConfig: '%%config%%', // Retry time in milliseconds for MQTT connections mqttReconnectTime: 15000, // Retry time in milliseconds for Serial port connections serialReconnectTime: 15000, // Retry time in milliseconds for TCP socket connections //socketReconnectTime: 10000, // Timeout in milliseconds for TCP server socket connections // defaults to no timeout //socketTimeout: 120000, // Maximum number of lines in debug window before pruning debugMaxLength: 1000, // The file containing the flows. If not set, it defaults to flows_<hostname>.json flowFile: 'flows.json', // To enabled pretty-printing of the flow within the flow file, set the following // property to true: flowFilePretty: true, // By default, all user data is stored in the Node-RED install directory. To // use a different location, the following property can be used userDir: __dirname + '/', // Node-RED scans the `nodes` directory in the install directory to find nodes. // The following property can be used to specify an additional directory to scan. nodesDir: '%%nodesdir%%', // By default, the Node-RED UI is available at http://localhost:1880/ // The following property can be used to specify a different root path. // If set to false, this is disabled. //httpAdminRoot: '/admin', // You can protect the user interface with a userid and password by using the following property. // The password must be an md5 hash eg.. 5f4dcc3b5aa765d61d8327deb882cf99 ('password') //httpAdminAuth: {user:"user",pass:"5f4dcc3b5aa765d61d8327deb882cf99"}, // Some nodes, such as HTTP In, can be used to listen for incoming http requests. // By default, these are served relative to '/'. The following property // can be used to specifiy a different root path. If set to false, this is // disabled. //httpNodeRoot: '/nodes', // To password protect the node-defined HTTP endpoints, the following property // can be used. // The password must be an md5 hash eg.. 5f4dcc3b5aa765d61d8327deb882cf99 ('password') //httpNodeAuth: {user:"user",pass:"5f4dcc3b5aa765d61d8327deb882cf99"}, // When httpAdminRoot is used to move the UI to a different root path, the // following property can be used to identify a directory of static content // that should be served at http://localhost:1880/. //httpStatic: '/home/nol/node-red-dashboard/', // To password protect the static content, the following property can be used. // The password must be an md5 hash eg.. 5f4dcc3b5aa765d61d8327deb882cf99 ('password') //httpStaticAuth: {user:"user",pass:"5f4dcc3b5aa765d61d8327deb882cf99"}, // The following property can be used in place of 'httpAdminRoot' and 'httpNodeRoot', // to apply the same root to both parts. //httpRoot: '/red', // The following property can be used in place of 'httpAdminAuth' and 'httpNodeAuth', // to apply the same authentication to both parts. //httpAuth: {user:"user",pass:"5f4dcc3b5aa765d61d8327deb882cf99"}, // The following property can be used to disable the editor. The admin API // is not affected by this option. To disable both the editor and the admin // API, use either the httpRoot or httpAdminRoot properties //disableEditor: false, // The following property can be used to enable HTTPS // See http://nodejs.org/api/https.html#https_https_createserver_options_requestlistener // for details on its contents. // See the comment at the top of this file on how to load the `fs` module used by // this setting. // //https: { // key: fs.readFileSync('privatekey.pem'), // cert: fs.readFileSync('certificate.pem') //}, // The following property can be used to configure cross-origin resource sharing // in the HTTP nodes. // See https://github.com/troygoode/node-cors#configuration-options for // details on its contents. The following is a basic permissive set of options: //httpNodeCors: { // origin: "*", // methods: "GET,PUT,POST,DELETE" //}, // Anything in this hash is globally available to all functions. // It is accessed as context.global. // eg: // functionGlobalContext: { os:require('os') } // can be accessed in a function block as: // context.global.os functionGlobalContext: { //'%%functionGlobalContext%%' // os:require('os'), // bonescript:require('bonescript'), // arduino:require('duino') } }</hostname>Gruß
Rainer
Gesendet von meinem LIFETAB_S785X mit Tapatalk
-
Bist du sicher, dass es wirklich
/opt/iobroker/iobroker-data/node-red/settings.js
ist, weil es sieht nach
/opt/iobroker/node_modules/iobroker.node-red/settings.js
aus?
-
Sorry, du hast wahrscheinlich recht wie immer
Mach ich, wenn ich wieder zu Hause bin.
Gruß
Rainer
Gesendet von meinem Cynus T7 mit Tapatalk
5104_akku.png
5104_battery.txt -
Hallo Bluefox,
die Datei /opt/iobroker/iobroker-data/node-red/settings.js sieht so aus:
! ````
/**- Copyright 2013 IBM Corp.
- Licensed under the Apache License, Version 2.0 (the "License");
- you may not use this file except in compliance with the License.
- You may obtain a copy of the License at
- http://www.apache.org/licenses/LICENSE-2.0
- Unless required by applicable law or agreed to in writing, software
- distributed under the License is distributed on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- See the License for the specific language governing permissions and
- limitations under the License.
**/
! // The
httpssetting requires thefsmodule. Uncomment the following
// to make it available:
//var fs = require("fs");
! module.exports = {
// the tcp port that the Node-RED web server is listening on
uiPort: 1880,
! // By default, the Node-RED UI accepts connections on all IPv4 interfaces.
// The following property can be used to listen on a specific interface. For
// example, the following would only allow connections from the local machine.
//uiHost: "127.0.0.1",
iobrokerInstance: 0,
iobrokerConfig: {"network":{"IPv4":true,"IPv6":true,"bindAddress":null},"objects":{"type":"file","typeComment":"Possible values: 'file' - [port 9001], redis - [port 6379], couch - [port 5984].","host":"127.0.0.1","port":9001,"user":"","pass":"","noFileCache":false},"states":{"type":"file","typeComment":"Possible values: 'file' - [port 9000], 'redis' - [port 6379].","host":"127.0.0.1","port":9000,"options":{"auth_pass":null,"retry_max_delay":15000}},"log":{"level":"debug","transport":{"syslog1":{"type":"syslog","enabled":false,"host":"127.0.0.1","port":"514","protocol":"udp4","facility":"local0"},"file1":{"type":"file","enabled":true,"filename":"log/iobroker.log","maxsize":null,"maxFiles":null}}},"dataDirComment":"Always relative to iobroker.js-controller/","dataDir":"../../iobroker-data/"},
! // Retry time in milliseconds for MQTT connections
mqttReconnectTime: 15000,
! // Retry time in milliseconds for Serial port connections
serialReconnectTime: 15000,
! // Retry time in milliseconds for TCP socket connections
//socketReconnectTime: 10000,
! // Timeout in milliseconds for TCP server socket connections
// defaults to no timeout
//socketTimeout: 120000,
! // Maximum number of lines in debug window before pruning
debugMaxLength: 1000,
! // The file containing the flows. If not set, it defaults to flows_<hostname>.json
flowFile: 'flows.json',
! // To enabled pretty-printing of the flow within the flow file, set the following
// property to true:
flowFilePretty: true,// By default, all user data is stored in the Node-RED install directory. To // use a different location, the following property can be used userDir: __dirname + '/',! // Node-RED scans the
nodesdirectory in the install directory to find nodes.
// The following property can be used to specify an additional directory to scan.
nodesDir: "/opt/iobroker/node_modules/iobroker.node-red/nodes/",
! // By default, the Node-RED UI is available at http://localhost:1880/
// The following property can be used to specify a different root path.
// If set to false, this is disabled.
//httpAdminRoot: '/admin',
! // You can protect the user interface with a userid and password by using the following property.
// The password must be an md5 hash eg.. 5f4dcc3b5aa765d61d8327deb882cf99 ('password')
//httpAdminAuth: {user:"user",pass:"5f4dcc3b5aa765d61d8327deb882cf99"},
! // Some nodes, such as HTTP In, can be used to listen for incoming http requests.
// By default, these are served relative to '/'. The following property
// can be used to specifiy a different root path. If set to false, this is
// disabled.
//httpNodeRoot: '/nodes',// To password protect the node-defined HTTP endpoints, the following property // can be used. // The password must be an md5 hash eg.. 5f4dcc3b5aa765d61d8327deb882cf99 ('password') //httpNodeAuth: {user:"user",pass:"5f4dcc3b5aa765d61d8327deb882cf99"}, // When httpAdminRoot is used to move the UI to a different root path, the // following property can be used to identify a directory of static content // that should be served at http://localhost:1880/. //httpStatic: '/home/nol/node-red-dashboard/',! // To password protect the static content, the following property can be used.
// The password must be an md5 hash eg.. 5f4dcc3b5aa765d61d8327deb882cf99 ('password')
//httpStaticAuth: {user:"user",pass:"5f4dcc3b5aa765d61d8327deb882cf99"},// The following property can be used in place of 'httpAdminRoot' and 'httpNodeRoot', // to apply the same root to both parts. //httpRoot: '/red', // The following property can be used in place of 'httpAdminAuth' and 'httpNodeAuth', // to apply the same authentication to both parts. //httpAuth: {user:"user",pass:"5f4dcc3b5aa765d61d8327deb882cf99"}, // The following property can be used to disable the editor. The admin API // is not affected by this option. To disable both the editor and the admin // API, use either the httpRoot or httpAdminRoot properties //disableEditor: false, // The following property can be used to enable HTTPS // See http://nodejs.org/api/https.html#https_https_createserver_options_requestlistener // for details on its contents. // See the comment at the top of this file on how to load the `fs` module used by // this setting. // //https: { // key: fs.readFileSync('privatekey.pem'), // cert: fs.readFileSync('certificate.pem') //},! // The following property can be used to configure cross-origin resource sharing
// in the HTTP nodes.
// See https://github.com/troygoode/node-cors#configuration-options for
// details on its contents. The following is a basic permissive set of options:
//httpNodeCors: {
// origin: "*",
// methods: "GET,PUT,POST,DELETE"
//},// Anything in this hash is globally available to all functions. // It is accessed as context.global. // eg: // functionGlobalContext: { os:require('os') } // can be accessed in a function block as: // context.global.os! functionGlobalContext: {
//
"node-pushbullet": require("/opt/iobroker/node_modules/iobroker.node-red/node_modules/node-pushbullet")
// os:require('os'),
// bonescript:require('bonescript'),
// arduino:require('duino')
}
! }</hostname>die Datei /opt/iobroker/node_modules/iobroker.node-red/settings.js sieht so aus: >! ```` /** * Copyright 2013 IBM Corp. * * Licensed under the Apache License, Version 2.0 (the "License"); * you may not use this file except in compliance with the License. * You may obtain a copy of the License at * * http://www.apache.org/licenses/LICENSE-2.0 * * Unless required by applicable law or agreed to in writing, software * distributed under the License is distributed on an "AS IS" BASIS, * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. * See the License for the specific language governing permissions and * limitations under the License. **/ >! // The `https` setting requires the `fs` module. Uncomment the following // to make it available: //var fs = require("fs"); >! module.exports = { // the tcp port that the Node-RED web server is listening on uiPort: '%%port%%', >! // By default, the Node-RED UI accepts connections on all IPv4 interfaces. // The following property can be used to listen on a specific interface. For // example, the following would only allow connections from the local machine. //uiHost: "127.0.0.1", iobrokerInstance: '%%instance%%', iobrokerConfig: '%%config%%', >! // Retry time in milliseconds for MQTT connections mqttReconnectTime: 15000, >! // Retry time in milliseconds for Serial port connections serialReconnectTime: 15000, >! // Retry time in milliseconds for TCP socket connections //socketReconnectTime: 10000, >! // Timeout in milliseconds for TCP server socket connections // defaults to no timeout //socketTimeout: 120000, >! // Maximum number of lines in debug window before pruning debugMaxLength: 1000, >! // The file containing the flows. If not set, it defaults to flows_<hostname>.json flowFile: 'flows.json', >! // To enabled pretty-printing of the flow within the flow file, set the following // property to true: flowFilePretty: true, // By default, all user data is stored in the Node-RED install directory. To // use a different location, the following property can be used userDir: __dirname + '/', >! // Node-RED scans the `nodes` directory in the install directory to find nodes. // The following property can be used to specify an additional directory to scan. nodesDir: '%%nodesdir%%', >! // By default, the Node-RED UI is available at http://localhost:1880/ // The following property can be used to specify a different root path. // If set to false, this is disabled. //httpAdminRoot: '/admin', >! // You can protect the user interface with a userid and password by using the following property. // The password must be an md5 hash eg.. 5f4dcc3b5aa765d61d8327deb882cf99 ('password') //httpAdminAuth: {user:"user",pass:"5f4dcc3b5aa765d61d8327deb882cf99"}, >! // Some nodes, such as HTTP In, can be used to listen for incoming http requests. // By default, these are served relative to '/'. The following property // can be used to specifiy a different root path. If set to false, this is // disabled. //httpNodeRoot: '/nodes', // To password protect the node-defined HTTP endpoints, the following property // can be used. // The password must be an md5 hash eg.. 5f4dcc3b5aa765d61d8327deb882cf99 ('password') //httpNodeAuth: {user:"user",pass:"5f4dcc3b5aa765d61d8327deb882cf99"}, // When httpAdminRoot is used to move the UI to a different root path, the // following property can be used to identify a directory of static content // that should be served at http://localhost:1880/. //httpStatic: '/home/nol/node-red-dashboard/', >! // To password protect the static content, the following property can be used. // The password must be an md5 hash eg.. 5f4dcc3b5aa765d61d8327deb882cf99 ('password') //httpStaticAuth: {user:"user",pass:"5f4dcc3b5aa765d61d8327deb882cf99"}, // The following property can be used in place of 'httpAdminRoot' and 'httpNodeRoot', // to apply the same root to both parts. //httpRoot: '/red', // The following property can be used in place of 'httpAdminAuth' and 'httpNodeAuth', // to apply the same authentication to both parts. //httpAuth: {user:"user",pass:"5f4dcc3b5aa765d61d8327deb882cf99"}, // The following property can be used to disable the editor. The admin API // is not affected by this option. To disable both the editor and the admin // API, use either the httpRoot or httpAdminRoot properties //disableEditor: false, // The following property can be used to enable HTTPS // See http://nodejs.org/api/https.html#https_https_createserver_options_requestlistener // for details on its contents. // See the comment at the top of this file on how to load the `fs` module used by // this setting. // //https: { // key: fs.readFileSync('privatekey.pem'), // cert: fs.readFileSync('certificate.pem') //}, >! // The following property can be used to configure cross-origin resource sharing // in the HTTP nodes. // See https://github.com/troygoode/node-cors#configuration-options for // details on its contents. The following is a basic permissive set of options: //httpNodeCors: { // origin: "*", // methods: "GET,PUT,POST,DELETE" //}, // Anything in this hash is globally available to all functions. // It is accessed as context.global. // eg: // functionGlobalContext: { os:require('os') } // can be accessed in a function block as: // context.global.os >! functionGlobalContext: { //'%%functionGlobalContext%%' // os:require('os'), // bonescript:require('bonescript'), // arduino:require('duino') } >! }</hostname>Gruß
Rainer
-
@Rainer: Ist noch aktuell?
