I have uninstalled nodered from jessy.
How are the steps to get a new nodered and working with pimatic… i’m not sure how to install.
-
Installing node-red and node-red-contrib-pimatic
-
@Swen said in Node-red for pimatic available:
How are the steps to get a new nodered and working with pimatic… i’m not sure how to install.
I have installed it as follows (assuming you have nodejs installed - I am using node 4.x as I am running Pimatic on the same box):
Installing node-red
sudo npm install node-red --globalRunning node-red as a service
sudo wget https://raw.githubusercontent.com/node-red/raspbian-deb-package/master/resources/nodered.service -O /lib/systemd/system/nodered.service sudo wget https://raw.githubusercontent.com/node-red/raspbian-deb-package/master/resources/node-red-start -O /usr/bin/node-red-start sudo wget https://raw.githubusercontent.com/node-red/raspbian-deb-package/master/resources/node-red-stop -O /usr/bin/node-red-stop sudo chmod +x /usr/bin/node-red-st* sudo systemctl daemon-reload sudo systemctl enable nodered.service sudo systemctl start noderedNotes
by default, the service wrapper will run node-red as user pi (flows and config will be stored in
/home/pi/.node-red) and the it will listen on port 1880 (unless you have changed/home/pi/.node-red/settings.jswith a prior setup).Changing the node-red user
If you want to run the node-red as different users you can do so as follows:
# EDIT the file "/lib/systemd/system/nodered.service", for example: sudo vi /lib/systemd/system/nodered.service # Change the following variables to your needs User=pi Group=pi WorkingDirectory=/home/pi # To apply changes you need to execute the following steps: sudo systemctl daemon-reload sudo systemctl restart noderedChanging the node-red listener ports
Assuming you run node-red as user pi with defaults you need to perform the following steps
# EDIT the file "/home/pi/.node-red/settings.js", for example: vi /home/pi/.node-red/settings.js # search for uiPort and change the value as you need # finally restart node-red sudo systemctl restart noderedAdding plugins
Add plugin using the web UI. Choose “Manage Palette” from the menu in the top right corner. Choose the “Install” tab and search for pimatic … see screenshot below (in my case “install” is greyed out as the package is already installed on my setup).
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
-
Thank you very much!!! I will give a try.
-
Ok, try to install, but i get some err and thereafter i get short a website with missing CSS and more after restart no nodered server any more… I must investigate in this but i don’t have much time…
sudo npm install node-red --global npm WARN deprecated nodemailer@1.11.0: All versions below 4.0.1 of Nodemailer ar e deprecated. See https://nodemailer.com/status/ npm WARN deprecated node-uuid@1.4.8: Use uuid module instead npm WARN deprecated i18next-client@1.10.3: you can use npm install i18next from version 2.0.0 \ > bcrypt@1.0.2 install /usr/local/lib/node_modules/node-red/node_modules/bcrypt > node-pre-gyp install --fallback-to-build node-pre-gyp ERR! Tried to download(404): https://github.com/kelektiv/node.bcryp t.js/releases/download/v1.0.2/bcrypt_lib-v1.0.2-node-v46-linux-arm.tar.gz node-pre-gyp ERR! Pre-built binaries not found for bcrypt@1.0.2 and node@4.6.2 ( node-v46 ABI) (falling back to source compile with node-gyp) gyp WARN EACCES user "root" does not have permission to access the dev dir "/roo t/.node-gyp/4.6.2" gyp WARN EACCES attempting to reinstall using temporary dev dir "/usr/local/lib/ node_modules/node-red/node_modules/bcrypt/.node-gyp" make: Entering directory '/usr/local/lib/node_modules/node-red/node_modules/bcry pt/build' make: *** No rule to make target '../.node-gyp/4.6.2/include/node/common.gypi', needed by 'Makefile'. Stop. make: Leaving directory '/usr/local/lib/node_modules/node-red/node_modules/bcryp t/build' gyp ERR! build error gyp ERR! stack Error: `make` failed with exit code: 2 gyp ERR! stack at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_ modules/node-gyp/lib/build.js:276:23) gyp ERR! stack at emitTwo (events.js:87:13) gyp ERR! stack at ChildProcess.emit (events.js:172:7) gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_proces s.js:211:12) gyp ERR! System Linux 4.9.35-v7+ gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_mod ules/node-gyp/bin/node-gyp.js" "build" "--fallback-to-build" "--module=/usr/loca l/lib/node_modules/node-red/node_modules/bcrypt/lib/binding/bcrypt_lib.node" "-- module_name=bcrypt_lib" "--module_path=/usr/local/lib/node_modules/node-red/node _modules/bcrypt/lib/binding" gyp ERR! cwd /usr/local/lib/node_modules/node-red/node_modules/bcrypt gyp ERR! node -v v4.6.2 gyp ERR! node-gyp -v v3.4.0 gyp ERR! not ok node-pre-gyp ERR! build error node-pre-gyp ERR! stack Error: Failed to execute '/usr/local/bin/node /usr/local /lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to- build --module=/usr/local/lib/node_modules/node-red/node_modules/bcrypt/lib/bind ing/bcrypt_lib.node --module_name=bcrypt_lib --module_path=/usr/local/lib/node_m odules/node-red/node_modules/bcrypt/lib/binding' (1) node-pre-gyp ERR! stack at ChildProcess.<anonymous> (/usr/local/lib/node_mod ules/node-red/node_modules/bcrypt/node_modules/node-pre-gyp/lib/util/compile.js: 83:29) node-pre-gyp ERR! stack at emitTwo (events.js:87:13) node-pre-gyp ERR! stack at ChildProcess.emit (events.js:172:7) node-pre-gyp ERR! stack at maybeClose (internal/child_process.js:854:16) node-pre-gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/chi ld_process.js:222:5) node-pre-gyp ERR! System Linux 4.9.35-v7+ node-pre-gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/nod e-red/node_modules/bcrypt/node_modules/.bin/node-pre-gyp" "install" "--fallback- to-build" node-pre-gyp ERR! cwd /usr/local/lib/node_modules/node-red/node_modules/bcrypt node-pre-gyp ERR! node -v v4.6.2 node-pre-gyp ERR! node-pre-gyp -v v0.6.32 node-pre-gyp ERR! not ok Failed to execute '/usr/local/bin/node /usr/local/lib/node_modules/npm/node_modu les/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/usr/local/lib/n ode_modules/node-red/node_modules/bcrypt/lib/binding/bcrypt_lib.node --module_na me=bcrypt_lib --module_path=/usr/local/lib/node_modules/node-red/node_modules/bc rypt/lib/binding' (1) npm WARN optional dep failed, continuing bcrypt@1.0.2 /usr/local/bin/node-red -> /usr/local/lib/node_modules/node-red/red.js /usr/local/bin/node-red-pi -> /usr/local/lib/node_modules/node-red/bin/node-red- pi node-red@0.17.5 /usr/local/lib/node_modules/node-red ├── is-utf8@0.2.1 ├── on-headers@1.0.1 ├── media-typer@0.3.0 ├── cookie@0.3.1 ├── basic-auth@1.1.0 ├── clone@2.1.1 ├── semver@5.3.0 ├── node-red-node-rbe@0.1.11 ├── json-stringify-safe@5.0.1 ├── hash-sum@1.0.2 ├── jsonata@1.2.6 ├── mustache@2.3.0 ├── cookie-parser@1.4.3 (cookie-signature@1.0.6) ├── passport-http-bearer@1.0.1 (passport-strategy@1.0.0) ├── passport-oauth2-client-password@0.1.2 (passport-strategy@1.0.0) ├── nopt@3.0.6 (abbrev@1.1.0) ├── passport@0.3.2 (passport-strategy@1.0.0, pause@0.0.1) ├── sentiment@2.1.0 ├── bcryptjs@2.4.3 ├── fs.notify@0.0.4 (async@0.1.22, retry@0.6.1) ├── cors@2.8.3 (object-assign@4.1.1, vary@1.1.1) ├── ws@1.1.1 (options@0.0.6, ultron@1.0.2) ├── raw-body@2.2.0 (bytes@2.4.0, unpipe@1.0.0, iconv-lite@0.4.15) ├── follow-redirects@1.2.4 (debug@2.6.8) ├── express-session@1.15.2 (cookie-signature@1.0.6, utils-merge@1.0.0, parseurl@ 1.3.1, depd@1.1.1, crc@3.4.4, uid-safe@2.1.5, debug@2.6.3) ├── fs-extra@1.0.0 (graceful-fs@4.1.11, jsonfile@2.4.0, klaw@1.3.1) ├── oauth2orize@1.8.0 (uid2@0.0.3, utils-merge@1.0.0, debug@2.6.8) ├── when@3.7.8 ├── uglify-js@3.0.20 (commander@2.9.0, source-map@0.5.6) ├── body-parser@1.17.2 (bytes@2.4.0, content-type@1.0.2, depd@1.1.1, qs@6.4.0, o n-finished@2.3.0, http-errors@1.6.2, debug@2.6.7, iconv-lite@0.4.15, type-is@1.6 .15) ├── express@4.15.3 (utils-merge@1.0.0, cookie-signature@1.0.6, content-type@1.0. 2, parseurl@1.3.1, methods@1.1.2, setprototypeof@1.0.3, escape-html@1.0.3, array -flatten@1.1.1, merge-descriptors@1.0.1, encodeurl@1.0.1, range-parser@1.2.0, fr esh@0.5.0, path-to-regexp@0.1.7, vary@1.1.1, etag@1.8.0, content-disposition@0.5 .2, serve-static@1.12.3, statuses@1.3.1, depd@1.1.1, qs@6.4.0, on-finished@2.3.0 , debug@2.6.7, proxy-addr@1.1.5, send@0.15.3, type-is@1.6.15, accepts@1.3.3, fin alhandler@1.0.4) ├── cheerio@0.22.0 (lodash.pick@4.4.0, lodash.flatten@4.4.0, lodash.foreach@4.5. 0, lodash.assignin@4.2.0, lodash.defaults@4.2.0, lodash.bind@4.2.1, lodash.filte r@4.6.0, lodash.reject@4.6.0, lodash.some@4.6.0, lodash.reduce@4.6.0, lodash.mer ge@4.6.0, lodash.map@4.6.0, entities@1.1.1, dom-serializer@0.1.0, css-select@1.2 .0, htmlparser2@3.9.2) ├── js-yaml@3.8.4 (esprima@3.1.3, argparse@1.0.9) ├── multer@1.3.0 (object-assign@3.0.0, xtend@4.0.1, append-field@0.1.0, on-finis hed@2.3.0, type-is@1.6.15, mkdirp@0.5.1, concat-stream@1.6.0, busboy@0.2.14) ├── node-red-node-email@0.1.24 (imap@0.8.19, mailparser@0.6.2, poplib@0.1.7, nod emailer@1.11.0) ├── mqtt@2.9.0 (inherits@2.0.3, xtend@4.0.1, reinterval@1.1.0, minimist@1.2.0, c oncat-stream@1.6.0, commist@1.0.0, split2@2.1.1, end-of-stream@1.4.0, pump@1.0.2 , mqtt-packet@5.4.0, readable-stream@2.3.3, websocket-stream@5.0.1, help-me@1.1. 0) ├── i18next@1.10.6 (cookies@0.7.0, json5@0.2.0, i18next-client@1.10.3) ├── node-red-node-twitter@0.1.11 (twitter-ng@0.6.2, oauth@0.9.14, request@2.81.0 ) ├── cron@1.2.1 (moment-timezone@0.5.13) ├── xml2js@0.4.17 (sax@1.2.4, xmlbuilder@4.2.1) └── node-red-node-feedparser@0.1.8 (feedparser@1.1.3, request@2.74.0) -
@Swen Try to install again with
sudo npm install node-red --global --unsafe-perm"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
-
So nodered is working but plugin crash pimatic again
09:35:36.386 [pimatic] info: Starting pimatic version 0.9.40 09:35:42.896 [pimatic, ppm] info: 2.15.12 09:35:42.982 [pimatic] info: Loading plugin: "pimatic-cron" (0.8.8) 09:35:43.966 [pimatic] info: Loading plugin: "pimatic-mobile-frontend" (0.9.11) 09:35:45.422 [pimatic] info: Loading plugin: "pimatic-ping" (0.9.5) 09:35:45.524 [pimatic] info: Loading plugin: "pimatic-sysinfo" (0.9.4) 09:35:45.856 [pimatic] info: Loading plugin: "pimatic-fritz" (0.5.6) 09:35:49.229 [pimatic] info: Loading plugin: "pimatic-sunrise" (0.8.7) 09:35:49.304 [pimatic] info: Loading plugin: "pimatic-denon-avr" (0.9.9) 09:35:50.599 [pimatic] info: Loading plugin: "pimatic-ifttt" (0.1.1) 09:35:50.662 [pimatic] info: Loading plugin: "pimatic-iframe" (0.2.0) 09:35:50.711 [pimatic] info: Loading plugin: "pimatic-netatmo" (0.0.9) 09:35:52.344 [pimatic] info: Loading plugin: "pimatic-openweather" (0.9.4) 09:35:52.478 [pimatic] info: Loading plugin: "pimatic-shell-execute" (0.9.11) 09:35:52.562 [pimatic] info: Loading plugin: "pimatic-mail" (0.8.6) 09:35:53.917 [pimatic] info: Loading plugin: "pimatic-z-way" (1.4.2) 09:35:53.987 [pimatic] info: Loading plugin: "pimatic-amazing-dash-button" (0.9.12) 09:35:54.100 [pimatic] info: Loading plugin: "pimatic-metar-weather" (0.9.1) 09:35:55.375 [pimatic] info: Loading plugin: "pimatic-telegram" (1.1.6) 09:35:57.217 [pimatic] info: Loading plugin: "pimatic-mysensors" (0.9.0) 09:35:57.391 [pimatic] info: Loading plugin: "pimatic-angular-material-frontend" (0.3.3) 09:35:57.446 [pimatic] info: Loading plugin: "pimatic-dwd-weather" (0.9.0) 09:36:04.280 [pimatic] info: Loading plugin: "pimatic-node-red" (1.0.6) 09:36:08.659 [pimatic-cron] info: the time is: Sun Aug 06 2017 09:36:08 GMT+0200 (CEST) 09:36:09.252 [pimatic-sunrise] info: Your location is set to lat: 52.3158742, long: 10.5479455 09:36:09.590 [pimatic-netatmo] info: Starting pimatic-netatmo plugin 09:36:10.091 [pimatic-z-way] info: initialized pimatic-z-way with hostname localhost 09:36:11.354 [pimatic-mysensors] debug: <- TimeOffset -7200 09:36:11.983 [pimatic-mysensors] debug: initializing SerialPortDriver 09:36:12.477 [pimatic-angular-material-frontend] info: Mounted material frontend on '/material' 09:36:13.902 [pimatic] error: An uncaught exception occurred: Error: listen EADDRINUSE :::1880 09:36:13.902 [pimatic] error:> at Object.exports._errnoException (util.js:911:11) 09:36:13.902 [pimatic] error:> at exports._exceptionWithHostPort (util.js:934:20) 09:36:13.902 [pimatic] error:> at Server._listen2 (net.js:1248:14) 09:36:13.902 [pimatic] error:> at listen (net.js:1284:10) 09:36:13.902 [pimatic] error:> at Server.listen (net.js:1380:5) 09:36:13.902 [pimatic] error:> at NodeRed.init (/home/pi/pimatic-app/node_modules/pimatic-node-red/node-red.coffee:25:14) 09:36:13.902 [pimatic] error:> at NodeRed.init (/home/pi/pimatic-app/node_modules/pimatic-node-red/node-red.coffee:1:1) 09:36:13.902 [pimatic] error:> at PluginManager.initPlugins (/home/pi/pimatic-app/node_modules/pimatic/lib/plugins.coffee:532:25) 09:36:13.902 [pimatic] error:> at /home/pi/pimatic-app/node_modules/pimatic/lib/framework.coffee:931:34 09:36:13.902 [pimatic] error:> at tryCatcher (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/util.js:16:23) 09:36:13.902 [pimatic] error:> at Promise._settlePromiseFromHandler (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:512:31) 09:36:13.902 [pimatic] error:> at Promise._settlePromise (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:569:18) 09:36:13.902 [pimatic] error:> at Promise._settlePromise0 (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:614:10) 09:36:13.902 [pimatic] error:> at Promise._settlePromises (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:693:18) 09:36:13.902 [pimatic] error:> at Async._drainQueue (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:133:16) 09:36:13.902 [pimatic] error:> at Async._drainQueues (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:143:10) 09:36:13.902 [pimatic] error:> at Immediate.Async.drainQueues [as _onImmediate] (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:17:14) 09:36:13.902 [pimatic] error:> at processImmediate [as _immediateCallback] (timers.js:383:17) 09:36:13.902 [pimatic] error:> This is most probably a bug in pimatic or in a module, please report it! 09:36:13.908 [pimatic] info: exiting... -
@Swen said in Node-red for pimatic available:
EADDRINUSE
Most likely this is, because the node-red instance embedded with
pimatic-node-redand the node-red instance you have setup are using the same port (1880). Remove thepimatic-node-redplugin as follows.- Make sure pimatic is not running:
sudo service pimatic stop - cd pimatic-app/
- Edit config.json, search for “node-red” and set the value for “active” to false. The plugin entry must look like as follows:
{ "plugin": "node-red", "active": false }, sudo service pimatic start
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
- Make sure pimatic is not running:
-
@Swen Did you manage to solve the issue?
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
-
I think so. I restart pimatic without an error. I get access now via 8000. But i don’t have time to test it generally. The main issue will be solved i think.
Thanks for your help.
