@Swen said in Node-red for pimatic available:
a separated installation is not a solution for me. There is a preinstalled version and I prefer this version.
Why? The node-red version embedded with the plugin is outdated already (required version 0.16.2, current version 0.17.5)! Besides that, I think the embedded node-red version does not have much benefit as
- node-red requires its own listener endpoint (pretty much the same than what you have with node-red standalone setup), and
- there is no navigation between pimatic and node-red UI.
You may argue that the embedded version is more efficient as the node-red-pimatic node implementation uses the pimatic API directly rather than using the WebSocket API. However, I believe the overhead is neglectible for the typical application scenarios.
If this won’t work, then I don’t use this plug-in.
Ok, I think @Jos-Hendriks can sort this out for you. I leave it up to you guys
EDIT: Perhaps off-topic for you, but of concern for other users. Please pimatic-node-red interferes with pimatic-johnny-five. The problem is that pimatic-node-red comes with node-red-contrib-gpio which uses pigpio and does no orderly shutdown. This will cause a pimatic-johnny-five initialization error if pimatic is restarted via pimatic-mobile-frontend. Work-around for the time being is to restart pimatic with the service wrapper.
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law