Node-red for pimatic available

---

could someone build a little tutorial “how to use node red with pimatic”?

i have tried to use it but dont understand whats to do

Maybe a little youtube clip?

First you should try to understand how node-red works

This is a good starting point
Www.noderedguide.com

@n3ro I have started playing with it. Actually, it is very easy to get into it once you have familiarized with basic concepts. Have a look at the guide as @rikki78 suggested. Regarding examples for pimatic I am planning to put to together a tutorial. I am also experimenting with node-red-dashboard which allows for using node-red to build a dashboard for pimatic. As part of my experiments I am also working with the plugin code to eventually add new features.

My dashboard is still in its infancies and I have done much yet to improve design, but its great fun

Hey guys!

I have never posted on the forum but must say I really love pimatic. It’s such a cool system! Now that I have installed node-red + the dashboard for pimatic, I have one question: How do I reach the dashboard? Normally, it would be reached via <IP>:1880/ui So, I thought I would be able to reach it on <IP>:8000/red/ui but I only get an error (“Cannot GET /red/ui”).

Can you help me out on this?

Thanks!

Hey, I just found out myself. It’s <IP>:8000/red/api/ui

When you click on the link in the dashboard plugin within Node-RED it try to open /red/apiui - the slash is missing. Maybe, this can be fixed in the next version?!

@Dee Well that ia up the maintainer op node-red-dashboard to fix

Meanwhile I released version 1.0.4. It should now be possible to install node-red plugins in the pimatic main dir. I also removed a useless config setting.

@Jos-Hendriks Sounds great, thanks for your efforts! I am just trying to develop a nice dashboard and it really is fun.

@Jos-Hendriks said in Node-red for pimatic available:

Meanwhile I released version 1.0.4. It should now be possible to install node-red plugins in the pimatic main dir. I also removed a useless config setting.

Oops, did something wrong again, please use 1.0.5…

Glad I haven’t updated yst.

@Jos-Hendriks said in Node-red for pimatic available:

Well that ia up the maintainer op node-red-dashboard to fix

Well, it can be fixed with a minor change in the plugin code. I’ll file a PR tomorrow.

Unfortunately, I am not able to update to version 1.0.5.

Any idea? I have “nopt” installed.

The error messages:

module.js:327
throw err;
^
Error: Cannot find module 'npm/node_modules/nopt’
at Function.Module._resolveFilename (module.js:325:15)
at Function.Module._load (module.js:276:25)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
at Object.<anonymous> (/home/pi/pimatic-app/node_modules/pimatic/ppm.js:32:12)
at Module._compile (module.js:409:26)
at Object.Module._extensions…js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Function.Module.runMain (module.js:441:10)
module.js:327
throw err;
^
Error: Cannot find module 'npm/node_modules/nopt’
at Function.Module._resolveFilename (module.js:325:15)
at Function.Module._load (module.js:276:25)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
at Object.<anonymous> (/home/pi/pimatic-app/node_modules/pimatic/ppm.js:32:12)
at Module._compile (module.js:409:26)
at Object.Module._extensions…js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Function.Module.runMain (module.js:441:10)

would it be possible to set the port in the settings of the plugins?
i always can’t start pimatic after install/update pimatic-node-red, because i have to change the port manually…

Mit freundlichen Grüßen
Chris

@Dee said in Node-red for pimatic available:

Unfortunately, I am not able to update to version 1.0.5.

Any idea? I have “nopt” installed.

The error messages:

module.js:327
throw err;
^
Error: Cannot find module ‘npm/node_modules/nopt’
…

This is a log of the the upgrade? Maybe you can do a fresh install of the plugin?

I must say that I never do uprgades myself. Always a fresh install. I run pimatic on docker which means I just create a new docker image which I can then deploy on my raspberry.

@chris said in Node-red for pimatic available:

would it be possible to set the port in the settings of the plugins?
…

Sure, I created an issue in github to fix that.

Hi, I am running Pimatic for a long time now and I also use node-red for combining various inputs and output and it is a great system combining both would be even better!
Is there a way to use the pimatic nodes and dashboard within my current install of node-red. I prefer not to install node-red as a “container” within my pimatic setup.

@mwittig said in Node-red for pimatic available:

Well, it can be fixed with a minor change in the plugin code. I’ll file a PR tomorrow.

Finally, I have filed my PR fixing the dashboard-link issue and also adding a few other things.

https://github.com/joshendriks/pimatic-node-red/issues/17
https://github.com/joshendriks/pimatic-node-red/issues/15
https://github.com/joshendriks/pimatic-node-red/pull/16

@dynamite said in Node-red for pimatic available:

Hi, I am running Pimatic for a long time now and I also use node-red for combining various inputs and output and it is a great system combining both would be even better!
Is there a way to use the pimatic nodes and dashboard within my current install of node-red. I prefer not to install node-red as a “container” within my pimatic setup.

The dashboard: Yes. It is just a node-red plugin. It is not specifically made for pimatic.
The pimatic nodes: No. These are hooked directly onto the pimatic framework events. I found this to be the best option to integrate pimatic and node-red. The choice came with the drawback of running node-red as a “container” in pimatic.

@Jos-Hendriks Any changes that you can “upgrade” this pimatic plugin to be an “official” plugin for node-red?

Is this warning normal while updating?

npm WARN engine pimatic-node-red@1.0.5: wanted: {“node”:">4.x.x",“npm”:">2.x.x"} (current: {“node”:“4.4.7”,“npm”:“2.15.12”})