MMM-PythonPrint customisation

[karsten13]

@diemen112 said in MMM-PythonPrint customisation:

I have added - /usr/bin/python3:/usr/bin/python3 to the docker compose

this will not work. You have to use the fat image, see my post above (Apr 11)

[diemen112]

Thank you for the help,
I made it work with adding some python dependent directory’s to the docker-compose file

[kayakbabe]

Sam,

Thank you for this MMM-PythonPrint. More than the sample module this really helped me follow how to wrap my head around how the script.js node_helper and anything else work together. The way you worded the variables and the input and output text really made sense and made it easy to follow what is happening. I am learning a lot. Again, Thank you.

Kelly

[sdetweil]

@kayakbabe awesome, glad it helped!

[kayakbabe]

@sdetweil I’m looking at the configuration variable repetative and trying to figure out what it is for.

is this correct logic for true and false?

repetative: true
if your python script runs in a loop forever by itself so the spawn in node helper will just keep its connection to the python script open

repetative: false
if your python script runs one time, and you need node_helper to keep spawning over and over so you can get the info from the python script over and over

[sdetweil]

@kayakbabe so , maybe your python script starts and runs, prints one line, and ends. current temp is x

is that all you want your module to present, one line?

or do you want the output every few seconds minutes

this is repetative:false, but my module will rerun the script every cycle time milliseconds

but some python scripts do that internally.

print, sleep, print, sleep, print, sleep, print…

this is repetative: true
my module will just start the python script

there are two different ways to capture the output

should have named parm

script_is_long_running

I provided a sample of each

also, in many cases, you are using someone else’s script and don’t have control over how it works, and don’t want to rewrite it