Node-RED

Raised as a usability problem by 15 people on Hacker News over 12 years (2014–2025), in 14 threads.

People raised many different problems with Node-RED, but no single problem has yet been raised by 3 people in 3 different months and threads.

Unreviewed issues were grouped by machine: Claude Haiku labelled each comment as a usability complaint, named what it's about and summed up the problem in a line, and a small model grouped similar problems. Nobody has checked them by hand. Expect mistakes.

The newest 15 complaints

Workflows become cumbersome and hard for newcomers to understand at scale2025-07-17
Node.js software is a hassle to maintain outside a container2025-05-16
Node-RED is hard to manage and not easily updatable on mobile2025-01-25
Passing data between nodes is unintuitive and hard to visualise when flows converge2023-02-12
Node-RED randomly loses Homebridge devices and reconnects, making automations flaky2022-05-16
Hard to change, duplicate, or arrange items once built2021-11-09
Flows save as single-line JSON, reorder nodes and cause cluttered git diffs and merge conflicts2021-10-25
Wiring boxes and filling in parameters feels laborious, no easier than writing code2021-09-30
Everything feels cumbersome and slow to work with2021-07-20
Hard to set up, and hard to debug flows like failing HTTP calls2019-12-12
Not user friendly for non-tech people; requires knowing HTTP servers and device communication2019-05-10
Basic usage answers are hard to find; issues closed without linking to the actual solution2019-01-09
Debugging is painful; only a scrolling console output and debug nodes are available2019-01-09
Requires too much mouse and typing, not touchscreen-friendly2019-01-04
Screenshot too small to read and no way to enlarge it; description unclear about what it does2014-08-24