How to trigger

[chrisegge]

How do you trigger the node to start running automatically

[namgk]

Hi you can wire an inject node to it.

…

On Friday, 3 May 2019, chrisegge ***@***.***> wrote: How do you trigger the node to start running automatically — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#12>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAHU7IH5EVL7N4M5RKGZ5P3PTROL5ANCNFSM4HKVDEFQ> .

[chrisegge]

Yea I had the continuous checked so it wouldn't let me. What about the output? Instead of individual outputs like a function node running it's an ever growing array of data. Is this normal?

[namgk]

Can you share a sample flow?

…

On Saturday, 4 May 2019, chrisegge ***@***.***> wrote: Yea I had the continuous checked so it wouldn't let me. What about the output? Instead of individual outputs like a function node running it's an ever growing array of data. Is this normal? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#12 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAHU7IB2FKFBYRTNTA4OZ6LPTY6YVANCNFSM4HKVDEFQ> .

[DotoPototo]

When ticking the 'continuous' option, you can no longer inject into the pythonshell node. This means I can't get the pythonshell node to start on startup

[namgk]

As I remember, it starts when it gets the first message. Can you double check?

[DotoPototo]

I tried but it did not work. The only way I can get it working is to manually start it.

[ozett]

yeah, still buggy... cant check "continous" or "std-in" separately.... hope the update is integrated soon -> #15 (comment)

[BigJerBD]

@ozett the node , when continuous is true , by default receives input with stdin. This is why once you set have continuous to True you cannot check the stdin button anymore. It is also because a continuous that does not recieve any input does not make a lot of sense .

A process that have stdIn to true without being continuous will be run once when a payload is recieved. If you send an other payload, it will not trigger another time, I rarely use in and just use continuous instead most of the time :

• If I want python to use the same process I just use a while loop in my python code get the inputs
• if not , once the python process is over you can still send an other payload to the node, it will start another process.

Would you mind explaining your use case? Maybe I could recommend you the proper way to run your node depending on your answer

[ozett]

my use case:
my camera at the front door triggers internally motion-detection, i pass this motion-alert to mqtt in node-red, grab an image and feed this image into an python script for face-detection.

to be a little flexible i wanted to pass some parameters via std-in from node-red to the python script.
i thought i have to check the box named "std-in" to pass my args to the script.
but that did not worked.

i only wanted to trigger the script once for every image, but i sounds a cool option to let it run contiunously.
i dont see clearly how to configure this. but could be cool maybe to feed a video-sequence to the script.

[ozett]

i assumed that i had to check th "std-in" box, to send my args via std-in from node-red to the script.
but std-in alone is not checkable...
(i am also not sure if the virtual-path is correct and works as i expect.
normally i switched to the virtual-env on the cmd-line with: "workon virtname"...

[BigJerBD]

In your situation I think setting continuous and stdin to True will work. The word continuous does not mean that the script is alway running, but only that the node can receive a stream of input

I have similar use case when instead of image input , i have text data that needs a python trigger .
I those cases I set both to true and in my code I call the input() python function to get the data from stdin

the node will then :

• receive the payload
• start the python script (without any argument )
• pipe the payload into the process (thats why you need input() in your code
• process ends

if an other image is received it should do the same thing again and again

[ozett]

i will give it a try.
any idea how to activate my virtual environment from the node?
i normally use workon to activate -> https://virtualenvwrapper.readthedocs.io/en/latest/command_ref.html#workon

[ozett]

found some hints to "activate" virt-envs while using python3 directly from the path of the virt-env.
https://stackoverflow.com/a/26172104

what is the way with this pythonshell-node? any example available? thx.