Node-RED co-creator and project lead here. Happy to answer any questions you have.
Would love a swagger api importer!
Node-RED: Low-code programming for event-driven applications
31–40 of 93 posts
Re: Node-RED: Low-code programming for event-driven applications
#32We're (extremely early days into) looking to use NodeRed to provide customised configurations for a fleet of telegraf agents.
Telegraf has the ability to phone home and ask for its telegraf.conf as it starts up, but the server-side of that equation is frustratingly left as an exercise for the reader.
There's not many ways to skin that particular cat, which is odd and unsettling in its own way.
Re: Node-RED: Low-code programming for event-driven applications
#33I use Node-RED in combination with home assistant, for automations. It's sometimes overly complicated to follow the flows, or do something relatively simple, but otherwise it's a nice middle ground between built in YAML based automations, and something like AppDaemon which requires writing python scripts.
They changed the engine a lot so you can script the automations from the UI now. See: https://www.home-assistant.io/docs/automation/editor/
The new UI editor is a better experience than yaml, but still has limitations that make node-red valuable for more complex automations. In particular juggling timers, state, and Boolean conditions with HA automations can be kind of awkward as they require you to coordinate across multiple automations, but very easy in node-red.
All in all I use both. I use the native ones for simpler automations (exterior lights on at dusk, blinds up at sunrise, etc.j and node red for the complex stuff (bathroom fan on for 5 minutes unless if the door is closed or the humidity is above 65%, turn off two minutes after the door is opened and the humidity is below 60%j.
Re: Node-RED: Low-code programming for event-driven applications
#34Is anyone using the node-RED ecosystem to deliver end-user customization of their not-home-automation product/service? I’m looking for ways to offer practical/accessible low-code (or not considered scary code) composition for our internal users who are running light industry factory production lines, but open to learning about commercial applications in any field to draw inspiration from.
We use it as a flow designer, we export the graph data it produces to handle real procution code. It's open source, highly customizable & well made.
Re: Node-RED: Low-code programming for event-driven applications
#35How does this compare to n8n? I read somewhere that node red was more focused on IoT applications, is that correct?
It originated in that space, but the ecosystem has taken it in very different directions. It has lower-level abstractions than n8n (which focuses on automating third-party SaaS), but can arguably do the same. I've used it for an insane amount of things, starting with home automation and telemetry but also fairly sophisticated uses, including: - Sniffing for multicast streams on a LAN and exposing IPTV set top boxes a…
thanks for listing all of these examples... i really like node-RED, and wrote up a tutorial on it a few years back, but have never actually reached for it to solve a real problem. you've given me some ideas!
Re: Node-RED: Low-code programming for event-driven applications
#36Node-RED co-creator and project lead here. Happy to answer any questions you have.
How do you feel Node-RED stacks up against products like Boomi, MuleSoft, SnapLogic, etc., and is competing with those iPaaS vendors something you want to do?
Re: Node-RED: Low-code programming for event-driven applications
#37Node-RED co-creator and project lead here. Happy to answer any questions you have.
Node-RED is a great prototyping tool.
Thank you, I have been a fan since the beginning.
Re: Node-RED: Low-code programming for event-driven applications
#38I'd like to hear from some people that don't like Node-RED.
Re: Node-RED: Low-code programming for event-driven applications
#39Node-RED co-creator and project lead here. Happy to answer any questions you have.
What are the flaws of Node-RED? The areas that you plan (or hope) to give many, many necessary love somewhere in the future?
What is something people use the software for, where you would say they should not do this?
Node-RED seems so far optimized for IoT and online services. Is there any ability (or plans for them) to use it locally for desktop-automation, similiar to AppleScript & Automator on MacOS, shell & batch-scripts, Selenium for websites, Tasker on android, etc.?
How would you see the state of the project generally and feature-wise ? Is it still growing for the next decade? Or has it reached it's peak and will move to settle down at its optimum somewhere in the next years? Should it reinvent itself every some years and stay fresh and adapting?
Re: Node-RED: Low-code programming for event-driven applications
#40I have just been going through a HELL of a time building a web-based app ("PWA" in progressive lingo) that needs to auto-discover certain devices on the user's LAN. This is a rebuild of an existing AIR-based app that's been in use in a corporate setting for 10 years and needs to be replaced because "death of flash". The AIR app I wrote back then handled discovering the local devices fantastically well. The problem no…
We're a industrial-control company whose traditional UI has been standard win32 applications - we've slowing converting our stack over to a web interface but as our UI needs to talk to lots of local devices, we've hit the problems you described.
Our solution has been to basically mandate that the user install either a small embedded device (ie. RPI or equiv) or manually launch a container. These essentially just serve as a local websocket / api router so Chrome connects to some local "device/container" and then that connects to all the local devices.
Although this is a logistical hurdle, its actually simplified other aspects of development since now this device/container has a bit of intelligence and can act as real middleware to simplify what the UI needs to contemplate. Basically MVC-style development using hardware bits as Controller.