This is a little lengthy, but I wanted to share the tactical details of my use case to give you a full picture:

I use Node-Red for a few scheduled activities: archiving Reddit posts or tweets I upvote and pulling information from real estate websites that match criteria I’m interested in.

I like Node-Red vs. cron-managed shell/Python scripts for several reasons:

  - the admin/editor UI is accessible on any device with a web browser (no git, ssh, etc. tooling required)
  - the node-based visual flow is easy to reason about and debug (so even after years of ignoring my scripts I can quickly come back to them and grok what’s going on)
  - the barrier to entry continues to be low (I can pop in and create a new flow in <1 hr)

I prefer it over Zapier or IFTTT since it’s more flexible. I’ve authored arbitrary JavaScript and request logic to retrieve and filter data in ways these pre-packaged tools can’t.

I run it on an AWS LightSail server for ~$4 per month. I use Ansible to manage Ubuntu with podman + systemd running the Node-Red docker image and TLS provided by Caddy. Roughly ~4 hours to setup from scratch and something I return to once every ~18 months to update/tweak with minimal issue.

To sum it up, I appreciate the grok-ability + flexibility + accessibility. It just works and it scales in complexity as I need it to!

Seems a bit similar to what huginn is designed for. Can anyone familiar with both describe the difference between them?

Huginn is designed as an automation system where as Node-red is designed as a visual programing system. Node-red is much more flexible than Huginn out of the box and you can extend it quite easily. Some basic tasks might need more setup and general understanding of what you are doing than with Huginn, but I found Node-red much more straight forward for getting useful outputs.

I use it for a lot of minor things:

* It watches an email folder and converts the email to a task.

* Filters my Facebook event calendar and splits accepted and not accepted events into seperate calendars so I can subscribe to them seperatly.

* Converts the Wikipedia current events page to an RSS feed.

* Monitors my server uptime/stats and reports it to Homeassistant.

* Recieves and forwards location data from my phone to a Homeassistant and nextcloud so I don't need multiple endpoints.

* Acts as a webhook enpoint for various git pojects to automate things

Basically I'm using it as a tube of glue. I used to do a bunch of it via bash scripts, but node-red makes it just a touch easier to grok

How do you access Facebook event calendar from Node-RED (or anywhere else)?

For home automation I do this with Node Red:

* We watch all the content on Jellyfin/Netflix/BBC on computer attached to our TV. Node-Red checks if browser is in full screen periodically and sends status to Home Assistant via MQTT. With this I can change the lights when watching TV.

Generally I have migrated some scripts to Node-Red like:

* Mirror FTP, extract archives, look for keywords, clean mp3 tags, add to Jellyfin

* Check emails for daily emails of solar plant, run regex to extract number and feed into Home Assistant.

* Send requests to website with property listings for a certain area, if there is a result, send a notification to my phone.

I had no idea really about node-red either as I prefer to code vs WYSIWG code. However, I found premade node-red dashboard extremely helpful. Heres a real example. https://medium.com/@mitchross09/solar-energy-monitoring-with...

I’ve used nod-red in corporate production for: (1) Mapping partner leads that could only be provided as an email into our CRM endpoint. (2) Synthetic canaries for application connectivity. (3) Other integrations where an existing service provider was not able to provide a modern solution (webhook) and this filled the gap for low volume.

I find it’s a tool that can be used to get something up and running very rapidly and be used for a longer period beyond proof of concept.

It's good for IoT and automation because it's fundamentally a framework for discrete functional reactive programming. It could be good for any context where you need to tie together a bunch of events from different contexts that all depend on each other to drive some other behavior. You can design design nodes and flows that minimize state and keep it local.

NodeRed doesn't really have anything specific related to IoT. It's just a generic automation platform for doing things like cronjobs and putting together simple dashboards.