TPFlow vs Node-Red

I siste webinar la FH veldig vekt på at Node-Red skal få økt fokus/prioriteres fremover. Det er jo spennende, men et naturlig spørsmål for meg er hva som er hovedforskjellen, fordeler og ulemper på Node-Red vs TPFlow?

Har noen her kunnskap om dette og kan dele noen tanker rundt hva som er “best” eller ihvertfall hva som “bør” kjøres hvor? :slight_smile:

I can answer the question, as the original author of tpflow engine and someone who met creator of Node-Red in IBM research lab in UK back in a days .
Node-Red has been considered as main rule engine before starting tpflow project but due to very high memory, CPU usage and certain security concerns we had to turn down the option and that was the starting point for tpflow project . Now , more powerful hubs can run docker(required for security) and node-red but most likely ( I don’t work for FH) it wont be available for existing and older hubs .

Node-Red - has immense community , many integrations and perfect for DIY makers

tpflow - high performance, low memory footprint, well integrated with FH but can be used as stand alone software, can be embedded into other systems.


Nice, thank you.

Would a general generalization be that smaller/straigthforward automations is best set up through TP Flow?
And that bigger/more complicated automations, especially the ones that ties into other systems would be better suited for Node-Red?

I have hardware for Node-Red (Docker etc), but trying to understand what usecases that should trigger me to start using it instead of TP Flow.

Right now Ecollector+Influx and Tibber API is my main usage outside of “normal” automations.

Yes, I would say it’s a correct generalization.