While I've been getting into Node-RED in a big way and like it very much I've noticed a broader class of similar software. These systems help tie potentially disparate "systems" together into a cohesive centralized server allowing for "meta-automations" / rules / triggers etc across the whole app space - kind of a flexible glue.
In the interests of expanding knowledge thought I put it out there - is anyone using any of these? Something different? Thoughts?
n8n.io / ioBroker / zapier
edit: Also relevant to the discussion is why use something like this?
My reasons for using Node-RED initially had to do with trying to solve the slowdown issues on my main hub. Had been following @JasonJoel's adventures in all things Node-RED and decided to try it out. For me the visual aspect of creating flows and sequences is very powerful. It's easy to see whats going on and making changes is relatively trivial. The ability to integrate different systems means that as a consumer I am not beholden to any one product. Also the opensource aspect is very nice - it allows for a wide range of customizations, expansions and more in depth troubleshooting.
All things considered I really love the HE platform (all 5 hubs and counting) and plan on a using it for a long time including recommending it and providing support to others. However I am not part of the company so my priorities are different and my solutions ultimately may end up being as well.
1 Like
My $0.02....
I am primarily a node-RED guy, but I've dabbled with a few others.
-
n8n.io - Have used it for a few workflow automation tests. Seemed to work pretty well. Documentation is in pretty good shape as well. I think of it more as a local IFTTT, but it can do more than that.
-
ioBroker - I found trying to use this very frustrating. English isn't the developer's 1st language, and some of the explanations/comments just don't make sense to me (to be fair he speaks English much better than I speak German, or any other language...). Documentation is almost non-existent, to the point it really isn't usable/a resource to use. Looks like it has a lot of potential, but be prepared to roll up your sleeves to dig into this one, if proceeding. Not much, if any, hand holding here.
-
Zapier - Never tried it.
-
total.js is pretty interesting, too. But I haven't found any good reason to use it over node-RED for visual flow sheets (total.js is interesting for other non-flow uses though).
As for the "why", you summarized that nicely. My Hubitat hubs (which I love) have never ran so well as they do now that I took almost 100% of the apps off them. I never have to reboot them any more, and they don't slow down.
The logic runs much faster in node-red, and it never slows down - much more CPU available, more memory available, much higher iops available in the storage subsystem.
Having logic in a multi-vendor 3rd party platform has other uses. For instance, I wanted to test out zigbee2mqtt the other day. After pairing devices to the new controller it took maybe 30 minutes to fix 100% of my logic in node-red. Just some swapping out of input and output nodes. The core logic itself was never touched, so I know it all works and does what I expect.
Took about 30 minutes when I decided to move the device from z2m back to Hubitat, too.
Would take about 30 minutes if I wanted to move the devices over to Home Assistant...
I think you get the picture. I view using a multi-vendor application like node-red as an opportunity to for me to protect my intellectual property and time. I am sick of redoing the same home automation rules over and over if I switch hubs, or want to integrate features hub A has but hub B doesn't.
5 Likes
