Node-red for pimatic available

---

I’ve just released pimatic-node-red!

If you do not know node-red, look at it first. This plugin starts node-red from the pimatic framework and allows you to act on changes and control devices using node-red flows!

Please note that this is a very early version. One of the things is that it runs its own webserver on port 8000. Not yet configurable, sorry… So the flow editor can be found under <your raspberry ip>:8000/red
I’m looking forward to hear/see any improvements that I can implement.

First of all thanks for this nice plugin! I’ve started to play with it and I think it could simplify some rules from pimatic. Would it be possible to have the variable name in each input block? That would improve readability.

And how can I compare two different pimatic variables to each other and do something from that result?

@Jos-Hendriks I would like to create a flow that does something with an output based on two variable input messages. So it should be possible to see in the message which origin the variable is. Now I add a property to each variable so I can distinguish them. Could that be integrated in the input block?

one more question came up… how can I send parameters to a device? eg changeDimlevelTo needs a parameter to be included.

I see that you also found your way to the github repo. Let’s dicuss the issues over there!

all right thanks!
Let’s not call them issues but improvements

Any idea whats to do to use it behind nginx?

        location /red/ {
                rewrite ^/red/(.*) /$1 break;
                proxy_pass http://127.0.0.1:8000;
                proxy_set_header X-Real-IP $remote_addr;
                proxy_set_header Host 'MY.DOMAIN.COM';
                        proxy_redirect http://MY.DOMAIN.COM/ https://MC.DOMAIN.COM/red/;
                        sub_filter '"/' '"/red/';
                        sub_filter_once off;
        }

I suppose you can find more about that on node-red. I do know node-red’s UI also uses a websocket connection.

this works for nginx:

 location /red/ {
    proxy_pass http://localhost:8000;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";
  }

@Jos-Hendriks could you please explain how to use node with pimatic

You can use variables from pimatic as input to a flow. The flow responds on changes of the variables.
The output activates a function of pimatic, eg turnOn
I found these in the pimatic api. Functions using parameters are not supported yet (eg dimLevelTo). I send these over mqtt and pimatic acts upon change of the value. This is a temporary workaround and I hope setting parameters will be supported soon

@rikki78

http://prnt.sc/cic5bk
http://prnt.sc/cic5nf

What is the correct Action for my dummy-switch?

I guess you want to turn on the switch, so turnOn.
It Isn’t documented very well, I used this for the appropriate keywords
https://pimatic.org/guide/development/providing-devices/

currently the installation of the plugin dont work.
It gets installed but then this is displayed in the log at start:

14:11:58.542 [pimatic] info: Loading plugin: “pimatic-node-red” (1.0.2)
14:11:58.552 [pimatic] error: Cannot find module ‘node-red’

any idea?

@Felix-Haverkamp How did you install the plugin? Did you get some error messages during installation?

via the pimatic plugin manager.
tried it twice…

there was a file called “node_modules” in the module folder. deleted and made a npm install nodered. now its working

I just released version 1.0.3 The previous version was made using a different version of npm and nodejs, which appears not to work well…

Can you please give it a try and let me know if this works on your system?

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

I just released version 1.0.3 The previous version was made using a different version of npm and nodejs, which appears not to work well…

Can you please give it a try and let me know if this works on your system?

I wasn’t able to install the previous version, but installation of version 1.0.3 works Thanks for the update.

@Jos-Hendriks What’s the purpose of the plugin configuration option “option1”? Is it just a dummy?

@mwittig Oops, I should have removed that a long time ago… Will fix in the next release