@dynamite said in Node-red for pimatic available:

the error is: [deploy failed, no response from server]

Where do you get this error message? Is it display below the node next to the red box?

Could you also explain the principle related to the action field of device action? The action is an action operation are operation on a device which can be called via the API. These are device method which have been declared as action of the device. See the SwitchActuator, for example:

  class SwitchActuator extends Actuator
    _state: null

    actions:
      turnOn:
        description: "Turns the switch on"
      turnOff:
        description: "Turns the switch off"
      changeStateTo:
        description: "Changes the switch to on or off"
        params:
          state:
            type: t.boolean
      toggle:
        description: "Toggle the state of the switch"
      getState:
        description: "Returns the current state of the switch"
        returns:
          state:
            type: t.boolean

Below is an example of node which calls changeStateTo on a switch device. The action parameter value is sent in (msg.payload) using a dashboard switch.

Perhaps it is easier for most users to use action expressions as used with rule actions. Thus I am planning to add other node type for this which then allows for soemthing like “switch edi-1 {{ msg.payload }}”

@mwittig Hi thanks for the explanation, however I need to fix the connection first.

If I hit the deploy butten I get the error message in node-red top center screen: deploy failed …
And under the variable device there is a message: parameter not found.

@dynamite said in Node-red for pimatic available:

And under the variable device there is a message: parameter not found.

Are you sure it is “parameter not found”?
If it is “variable not found” may be you provided the variable name with leading $ sign? In case, remove the $ sign from the node configuration, e.g. write “responseTime” instead of “$responseTime”. Also avoid leading spaces

The next version will handle this automatically.

EDIT: Make sure to “Deploy” each time you make configuration changes to apply them.

EDIT2: I have a published a new version. When you reload the node-red in the browser, “Managed Palette” should highlight the update on the “Nodes” tab. When the update has been installed you’ll need to restart node-red.

@mwittig
It was indeed variable not found! However adding/removing the $ does not make a difference

I also tried the device action:

But during deploying it gives me the error message…
(deploy failed no response from server) in red top middle of the screen.

The config for the controller looks like this:

I have ran an dist-update to the system and a reboot and now things are starting to work!

@dynamite said in Node-red for pimatic available:

I have ran an dist-update to the system and a reboot and now things are starting to work!

Ah, OK. Did the “variable not found” error disappear?

How about the action? Are you still getting this “deploy failed no response from server” error from node-red?

@dynamite said in Node-red for pimatic available:

But now I try it again but no response…?

Before you start the node-red server you can set environment variable PIMATIC_DEBUG to some value to enable debug output on the console. Maybe you can redirect this to a file and send me the output and the flow file?

Here es an example I use for updating a dashboard UI switch widget and for executing an action when the switch widget is flipped.

@mwittig Hi can you tell me which plugin you have used for the switch?

I looks like my nodered is not running stable anymore? If I hit the deploy just after starting, no problem green message. But it stops after a while and I can not make any connection and have to restart. Don’t know if it is related to the dist-upgrade or the plugin install.

@dynamite said in Node-red for pimatic available:

But it stops after a while and I can not make any connection and have to restart. Don’t know if it is related to the dist-upgrade or the plugin install.

That’s strange. I have tested on Raspi 3 and Windows including a long running test without problems! Which version of node-red are you using? Is it the latest version available (0.17.4 at the time of writing)? If not, you should update.

@mwittig Hi, no it is not the latest version. It is still 15.something. I was already looking for the update procedure. (any hints on that?)

@dynamite said in Node-red for pimatic available:

I was already looking for the update procedure. (any hints on that?)

How did you install node-red?

sudo npm install -g node-red?

If yes, just execute that again and it should install the latest version. To be safe make backups of your flows first.

EDIT: If you run node-red on user pi the flows should be located in /home/pi/ .node-red

@mwittig It took some effort to upgrade as I installed it by apt-get package. And upgrading as mentioned did not do the complete trick.
I have been able to build the test setup as mentioned earlier and it works!
But… I am still having stability issues.
edit1 If I restart node-red and the first time hit save I get a green bar succesfull.
If I hit the deploy again after a shift of a node I get an error message and I cannot acces node red anymore.
edit2 If I enable deploy on modified nodes I don’t get the error message.

@dynamite said in Node-red for pimatic available:

edit1 If I restart node-red and the first time hit save I get a green bar succesfull.
If I hit the deploy again after a shift of a node I get an error message and I cannot acces node red anymore.
edit2 If I enable deploy on modified nodes I don’t get the error message.

Strange, I need to reproduce that. Can you please let me know which node version you run. Ideally, please post the first lines of the node-red log output which should look as shown in the example below. Are you running a current Raspbian distribution?

17 Jul 22:18:19 - [info] Node-RED version: v0.17.4
17 Jul 22:18:19 - [info] Node.js  version: v4.7.3
17 Jul 22:18:19 - [info] Windows_NT 10.0.15063 x64 LE
17 Jul 22:18:20 - [info] Loading palette nodes

@mwittig
Hi here is the log when I start up node-red at my pimatic:

Welcome to Node-RED

18 Jul 08:58:30 - [info] Node-RED version: v0.17.4
18 Jul 08:58:30 - [info] Node.js version: v4.6.2
18 Jul 08:58:30 - [info] Linux 4.9.35-v7+ arm LE
18 Jul 08:58:31 - [info] Loading palette nodes
18 Jul 08:58:34 - [info] Dashboard up and running
18 Jul 08:58:34 - [info] node-red-contrib-pimatic@1.0.2 started
node-telegram-bot-api deprecated Node.js v5.x and below will no longer be supported in the future module.js:409:26
18 Jul 08:58:37 - [info] Dashboard version 2.4.3-beta started at /ui
18 Jul 08:58:40 - [info] Settings file : /home/pi/.node-red/settings.js
18 Jul 08:58:40 - [info] User directory : /home/pi/.node-red
18 Jul 08:58:40 - [info] Flows file : /home/pi/.node-red/flows_RASPI3.json
18 Jul 08:58:40 - [info] Server now running at http://127.0.0.1:1880/
18 Jul 08:58:40 - [info] Starting flows
18 Jul 08:58:40 - [info] [socketio-config:12fd9073.7fb54] Created server bind to Node-red port
18 Jul 08:58:41 - [info] Started flows
18 Jul 08:58:41 - [info] [mqtt-broker:cd46eff.89e6b1] Connected to broker: mqtt://192.168.178.10:1883

Basically it looks like the front end is crashing. As the process keeps running but I can not enter the front end anymore. This also happens after a while of running. I did not look into it but can I increase the debug level of node-red?

I do not want to upgrade node.js as this will give a conflict with pimatic? Or am I wrong about this?

@dynamite said in Node-red for pimatic available:

Basically it looks like the front end is crashing. As the process keeps running but I can not enter the front end anymore.

Which browser are you using?

It might be server-side issue though. Check memory usage and the ulimits for the user running node-red. Do you start node-red from the command line by typing “node-red” or does the apt package installation comes along with some sort of service wrapper?

This also happens after a while of running. I did not look into it but can I increase the debug level of node-red?

node-red has a verbose option which you can use if you start node-red from the command line: node-red -v.

I do not want to upgrade node.js as this will give a conflict with pimatic? Or am I wrong about this?

Yes, for the time being please stick to node 4.x which I am also running it here due to the pimatic limitations.

Can you pelase also let me know which non-core nodes (additional packages) you have installed? It might be a combination of packages causing the issue.

@mwittig said in Node-red for pimatic available:

Which browser are you using?

I am using various browsers…but mainly firefox and chrome

It might be server-side issue though. Check memory usage and the ulimits for the user running node-red. Do you start node-red from the command line by typing “node-red” or does the apt package installation comes along with some sort of service wrapper?

I have remove the apt-get package and installed it via npm to have more control. I have started it via the console but also as a service via a script (raspberry script for node-red)

This also happens after a while of running. I did not look into it but can I increase the debug level of node-red?

node-red has a verbose option which you can use if you start node-red from the command line: node-red -v.
Ok I will run a console with this option to see the output…
18 Jul 22:10:03 - [info] Stopped flows
18 Jul 22:10:03 - [info] Starting flows
18 Jul 22:10:03 - [info] [socketio-config:12fd9073.7fb54] Created server bind to Node-red port
18 Jul 22:10:03 - [info] [inject:6f383581.b72cec] repeat = 300000
18 Jul 22:10:03 - [info] [inject:Weather query] repeat = 300000
18 Jul 22:10:03 - [info] [inject:bf2cffb.d7efd] repeat = 30000
18 Jul 22:10:03 - [info] [inject:92f6524a.3197b] repeat = 300000
18 Jul 22:10:03 - [info] [inject:a878321d.411298] repeat = 900000
18 Jul 22:10:03 - [info] Started flows
18 Jul 22:10:03 - [info] [mqtt-broker:cd46eff.89e6b1] Connected to broker: mqtt://192.168.178.10:1883
18 Jul 22:10:03 - [error] [tcp request:e69c8507.4b01a8] connect failed 192.168.178.41:8899

Can you pelase also let me know which non-core nodes (additional packages) you have installed? It might be a combination of packages causing the issue.


Maybe socketio is doing the trick…

@mwittig I have removed the socketio package and removed the settings from the websocket node. I was playing with these to connect to pimatic so some old settings were still activated. Let us hope this was the cause of conflict…

Update, still running now. So I think existing (web)socket(io) were conflicting with the plugin…But changes are of course low that someone else is playing with these and connecting to pimatic…;-)

@mwittig I have tested the set value as well. It works very well. A point of improvement is maybe some “content” testing. By accident I have parsed an object as payload. The value in Pimatic is still set as [object]. I think this will lead to problems in Pimatic if values are set which are not realistic?

Additionally: Would there be an option to set a parameter with multiple attributes with one message? For example I use node-red to read my MiFlore plant sensors via a script. These are now forwarded via a simple MQTT output in which the complete object with data could be parsed.

MiFlora/FicusBenja : msg.payload : Object
object
fw: "3.1.4"
Name: "Ficus Benja"
temp: "23.7"
Moisture: "45"
Light: "160"
Conductivity: "504"
Battery: “99”

I have now have a MQTT sensor with multiple attributes which are set by receiving the MQTT message.

@dynamite That’s great. I tried the node-red-contrib-socketio extension and a faulty node configuration blew-up my node-red setup. The only way to fix it was to remove the node manually from the json file which contains the flows. The implementation of the socketio-in and socketio-out node has some flaws like it does not handle exceptions gracefully. My recommendation is to avoid using the plugin!

Generally, the suggested extension to set multiple variables from msg.payload properties make sense to me. Note, however, this is only possible for variables! Attributes (that is $<device-id>.<attribute-name>) are read-only and can only be modified through action operations, e.g. changeStateToto change the state attribute of a switch device.

How, about Name: "Ficus Benja". Is this a variable in your setup? I am just wondering if some payload properties need to be disregarded (filtered out).

Perhaps you can provide some more information about the Pimatic setup you have for to present the data from your MiFlore plant sensor?

@mwittig
Hi this is my current setup for the mi flora

I am using a python script to read the data from the various sensors (3 plants). The output of the script is converted into a msg format in a function:
var tokens = msg.payload.split("\n");
msg.payload = {
fw : tokens[1],
Name : “Ficus Benja”,
temp : tokens[5],
Moisture : tokens[7],
Light : tokens [9],
Conductivity : tokens [11],
Battery : tokens [13]
}
msg.topic = "MiFlora/FicusBenja"
return msg;
This is sent to my influx database, MQTT gateway and if the moisture level is to low to telegram. (So my wife can water the plants )
The MQTT message is now used in pimatic as a MQTT Sensor:

The question is indeed whether you can set the attributes?