2 ms·
I use it for home automation with HomeKit/Zigbee2MQTT and a few other things. Pluses: - You can stuff it into a container very easily (https://github.com/rcarm
by rcarmo 8y ago
I use it for home automation with HomeKit/Zigbee2MQTT and a few other things. Pluses:
- You can stuff it into a container very easily (https://github.com/rcarmo/docker-node-red https://github.com/rcarmo/docker-node-red - use the Ubuntu branch)
- There are loads of extra components for IoT, automation and cloud services (including low end stuff like sniffing multicast packets and doing WoL, both of which I use a lot)
- Works beautifully with MQTT
- You can build simple metrics and control dashboards with nearly zero code (although it helps if you know Angular to inject directives into the templating)
- It’s very easy to develop your own nodes using JavaScript without leaving the GUI
Minuses:
- Being based on Node means you have to deal with a dependency dumpster fire now and then (and I worry a lot about security)
- Many plugins are old, brittle, unmaintained and buggy (HomeKit support crashes the entire runtime now and then)
- Component behavior is inconsistent (some nodes pass on msg.topic, others eat it, etc.), even for built-ins.
- Debugging can be a massive pain, since effectively all you get is a scrolling console output in the inspector pane and the ability to add more debug nodes to your flows to “sniff” traffic into it.
- it’s very easy to shoot yourself in the foot with JavaScript, and it does not support anything else in the function nodes (I would vastly prefer ClojureScript or Python, for instance)
- there is no easy/intuitive way to join flows (i.e., do an AND gate) without doing trickery
- versioning is a major pain (I snapshot my setup by pretty-printing the JSON flow store every now and then - https://gist.github.com/rcarmo/f2a8a14ef5f3d77759555f3fea5e7c37 https://gist.github.com/rcarmo/f2a8a14ef5f3d77759555f3fea5e7...)
- The GUI doesn’t scale to manage large numbers of flows (I have 40 or something)
But I’ve resigned myself to all the above, because the alternatives are worse.
And, as an experiment, I recently built on it an App Store notification service to check when apps are discounted, GUI and all, with a SQLite back-end. Works great, although it lacks some elegance when dealing with databases.
Edit: forgot to add that it can be self-documenting up to a point (you can add Markdown notes to flows, and have a comments Node that you can drop amid your flows to annotate them), which is extremely useful when you go back to something a few months later and have to trace an entire flow end to end to figure out why it broke.