I wrote the tutorial that’s been posted, I went all in and have converted about 95% of my YAML automations to Node-Red. I left a couple of things as YAML but otherwise have been using Node-Red for several months for everything without any issues. It’s been very stable.
Main pros to me is it’s just easier to manage and it’s much, much faster to make and debug automations. I had to watch a few Youtube videos to get the interface and what’s happening with the “msg” but I think it’s pretty intuitive. Once I started converting them I could consolidate a lot of stuff that took multiple YAML automations into simpler logic.
The big con to me is that it’s not really meant to track states. You can declare variables globally within Node-Red but it seems pretty hacky. But this is what Home Assistant is good at, and why they pair well. Any time I need a state, or to perform an action, I just use the Hass nodes. So Hass tracks states and deals with the devices, Node-Red just does the logic.
A few people have commented and said they think automations run slow, but I have not found this to be true (my motion triggered lights seem to respond just as fast as before when they were YAML).
It seems like quite a bit is possible with Node-Red but I have to admit I am no developer, so would love to see other examples. Probably the most interesting thing I have done is log my GPS updates into a MySQL database. I then use a simple python script to read that information and replot it as a custom map using gmplot. So I get a map with: a heat map of the last 6 months of GPS updates, tracks of the last 7 days, and plot a bunch of things with info from Hass (my position, beacons position). ie
Curious @flamingm0e if you can post an example, I find multiple triggers and multiple conditions much easier in Node-Red, there are kind of a lot of ways to do things though.