https://github.com/FlowHistory/FlowHistory

A self-hosted backup and restore tool for Node-RED flow files. Runs as a Docker container that manages backups for one or more Node-RED instances, local (file-based) or remote (API-based). Automatically detects flow changes, creates compressed backups, and provides a web UI for managing backups, viewing diffs, and restoring.

Features

- Multi-instance support - manage backups for multiple Node-RED instances from a single deployment

- Local and remote instances - watch local files via inotify or poll remote instances via the Node-RED Admin API

- Automatic backups on change - file watching (local) or API polling (remote) with configurable intervals

- Scheduled backups - hourly, daily, or weekly via APScheduler

- Manual backups - one-click from the dashboard

- Visual diff viewer - see which tabs, subflows, and nodes changed between any two backups, with field-level diffs

- One-click restore - restores files (local) or deploys flows via API (remote), optionally restarts the container

- Pre-restore safety backup - always created before overwriting current flows

- Checksum deduplication - skips backup if flows haven't changed (SHA256)

- Retention policies - by max count and max age, with protection for pinned and recent safety backups

- Backup import/export - upload backup archives from other instances or download them for offline storage

- Credentials and settings backup - optionally include flows_cred.json and settings.js (local only)

- Labels and notes - annotate backups with descriptions

- Notifications - alerts via Discord, Slack, Telegram, Pushbullet, or Home Assistant for backup failures, restores, and more

- Dark mode - with system preference detection and manual toggle

- Optional password auth - simple shared password via environment variable

- Health check endpoint - for Docker healthcheck integration

- Prometheus /metrics endpoint - HTTP and per-instance backup metrics for scraping

https://github.com/FlowHistory/FlowHistory

We opened registration last week, and Nick recorded a quick video about what to expect from this year’s event.

We had more than 1,000 people join the livestream last year, and this year’s CFP brought in a great mix of talks again — AI, edge deployments, industrial automation, hobbyist projects and plenty of real-world Node-RED.

It’s happening November 3 and it’s free and online.

If you haven’t registered yet, save your spot now.

I help coordinate the event, and I have to say: I'm really excited about this year's programme. The submissions were strong and picking was genuinely hard, but the talks we ended up with cover edge deployments, AI integration, industrial automation, and some real unexpected gems.

Last year was great, and I think this one is going to be even better.

Free, online, November 3rd. Hope to see you there.

Save your spot today!

If you use macOS, here's a heads up. Safari on macOS 27 is broken with Node-Red. As shown in my video, clicking on the tab for any flow simply reloads the entire page so the main/first tab becomes active again.

Bonjour,

Je n'arrive pas à découvrir un point du simulateur de Yabe. Je découvre bien le Devices. Avec l'ajout du noeud Change, le noeud Discover Point tombe en Time Out (30 sec), et si je ne le met pas il indique Invalid data...

En haut, c'est la config du noeud Change.

J'aimerais trouver une config qui fonctionne. Si vous connaissez un autre simulateur ou pouvez m'aider à avancer avec cela ça serait bien apprécié. J'utilise la palette " @/halsystems/red-bacnet" 2.2.0 présentement. Je roule sous Windows 11, pare-feu désactivé...

Merci

I am New user first time on reddit please follow 👍

Really excited about this one. Phil hosts Unplugged, An IIoT Podcast, and has been part of the Node-RED community for years.

He's based in Brisbane, Australia, which means he'll be up all night hosting this. Conference runs midnight to 6am his time on November 3rd, and he said yes anyway.

Registration opens soon. Sign up to be notified: flowfuse.com/blog/2026/06/announcing-node-red-con-2026/#stay-in-the-loop

We know, it's been quiet, Node-RED Con 2026 went a bit silent after the CFP closed. The truth is the submissions were so good that the team really struggled to pick. The agenda is coming together now.

Registration opens once it's ready. The FlowFuse team is handling notifications, sign up here if you want to be the first to know: flowfuse.com/blog/2026/06/announcing-node-red-con-2026/#stay-in-the-loop

I’ve been experimenting with Node-RED as the backbone of a manufacturing monitoring system combined with a 3D/VR production simulation.

The system connects production data to a 3D dashboard for monitoring OEE, machine status, target vs. actual production, and operator activity.

The VR side simulates a CNC production process, including material handling, machining, inspection, and finished goods handling.

Node-RED handles the data flow between the production simulation, database, and dashboard, making it possible to visualize the manufacturing process in real time.

I’m exploring how Node-RED can be used beyond traditional dashboards for interactive 3D manufacturing visualization and VR-based production simulation.

Sharing a short demo curious to see what other interesting manufacturing use cases people are building with Node-RED.

I'm a huge fan and proponent of Node-RED, it has been running my smart home for years, and will continue to for many more!

I'm also a heavy python user and maker of many computer vision pipelines. NR didn't lend itself to this kind of work, with OpenCV, pytorch, yolo models, etc. etc. it's not designed for that kind of use case.

Thanks to Claude, I was able tackle something that's been on my todo list for ages, a pure python node-based flow engine and editor inspired by Node-RED. Got it working pretty well last year. Now I've added a UDP node to pynode so I can seamlessly move data between platforms!

https://github.com/olkham/pynode

To make it absolutely clear this isn't me trying to compete with NR, it's a ground up implementation designed to be familiar to NR users that want to build python heavy flows. I figured if I find this useful there are probably a few others in this community that might too!

so basically a bit of context i had been trying for 2 hours BUT WHEN IT FINALLY CONNECTS IT REFUSES TO ACCEPT MY KEY THINGYS and i feel im goin insane so yea i really need help

I dont know if anybody ever going to use this, but i prompted a website for sharing or saving flows.

Nodebin.xyz

Any feedback welcome.

With Raspberry Pi the obvious fan-favorite SBC for thinkering, an enclosure that's easily 3D printed within a few hours on an A1 Mini, and using the Edgeberry ecosystem for essential IoT robustness, ... . I'm not done yet, but too excited not to share: https://github.com/ThatRedBox

The 𝐒𝐦𝐢𝐭𝐡𝐭𝐞𝐤 𝐏𝐚𝐬𝐬𝐏𝐨𝐫𝐭 is ready to go as a standalone gateway for your next IoT or automation project.

𝐁𝐮𝐢𝐥𝐭-𝐢𝐧 𝐍𝐨𝐝𝐞-𝐑𝐄𝐃 means you can build your flows, connect your gear and run your logic right at the edge.

RS485. USB. Ethernet. Wi-Fi. 4G. Long-range RF. Satellite. GPS. 𝐌𝐮𝐥𝐭𝐢𝐩𝐥𝐞 𝐚𝐬𝐬𝐞𝐭𝐬. 𝐎𝐧𝐞 𝐠𝐚𝐭𝐞𝐰𝐚𝐲.

𝐀𝐥𝐫𝐞𝐚𝐝𝐲 𝐰𝐨𝐫𝐤𝐢𝐧𝐠 𝐰𝐢𝐭𝐡 𝐍𝐨𝐝𝐞-𝐑𝐄𝐃? Bring your flows, PassPort is ready for the field.

And when it’s deployed,𝐏𝐚𝐬𝐬𝐏𝐨𝐫𝐭 𝐌𝐚𝐧𝐚𝐠𝐞𝐫 gives you simple remote access and gateway management, 𝐜𝐨𝐦𝐩𝐥𝐞𝐭𝐞𝐥𝐲 𝐟𝐫𝐞𝐞.

FIND IT HERE:
https://www.smithtek.com.au/product-page/passport-igw-nodered-australia

I built a DIY 6-DOF robot controlled using Node-RED, ESP8266, and Modbus TCP, with a real-time 3D visualization using Three.js.

The Node-RED dashboard can control each joint, save robot positions, and run movement sequences. The 3D model also includes the multi-link gripper, so the physical robot and virtual model can move together.

I’d be interested to hear your feedback or suggestions for improving the system.

Hi!

I've been working on an open-source project called Sekalum around a problem that becomes more noticeable when Node-RED is part of a larger automation environment:

Credentials start living in many different places.

Node-RED may have credentials for APIs and services, while Home Assistant, n8n, AI tools or custom applications maintain their own copies and OAuth connections.

Sekalum explores a different architecture:

Provider → Sekalum → authorized consumer

Credentials and their lifecycle are managed in a separate self-hosted service. Consumers are explicitly granted access and resolve only the credential data they are authorized to use at runtime.

This isn't intended to replace Node-RED's own credential handling. The interesting use case is when Node-RED is one of several consumers that need access to external services.

I'm currently looking at a dedicated Node-RED integration, but before building it I'd be interested in how Node-RED users see this approach.

Would an external credential lifecycle layer be useful in your setup, or would it just add unnecessary complexity?

Sekalum is open source and self-hosted. Architecture, security model and technical details are documented here:

GitHub:
https://github.com/workingcuriosity/sekalum

Regards

Luis

I built an interactive 3D visualization of a 4-machine CNC production line using Three.js and FlowFuse Node-RED Dashboard.

Each machine shows its status, OEE, target and actual output, with simple door and spindle animations.
The monitor is also interactive, so clicking a machine can trigger a detailed information popup through Node-RED.
The data is currently simulated, but it can be connected to real-time data from PLC, MQTT, or a database.

What do you think does 3D visualization add value compared to a traditional 2D manufacturing dashboard?

When you do use a "Link Call Node", you set what "Link Inn Node" it goes to, You can not see this in Node Red. When you have a simple "Link Inn Node" and "Link Out Node", you see a dotted line when one of the two nodes is selected. I would love to see the same with "Link Call Node". Or is it just me that miss some :)

Last chance — the Call for Papers closes tomorrow, Friday July 31st.

There are already some really interesting proposals in. If you've been thinking about it and keep putting it off, today is genuinely the last day.

Full details and submission form at nrcon.nodered.org.

I've been working on a 3D warehouse visualization using Three.js and the FlowFuse Node-RED Dashboard. Instead of viewing inventory in a traditional table, users can interact directly with the 3D warehouse by selecting pallets to see information such as material ID, material name, supplier, storage location, and current status.

The goal is to create a more intuitive way to monitor warehouse operations while staying connected to real-time data from Node-RED.

I’m using a Radxa board as a small Node-RED HMI. It can run a self-hosted Node-RED instance or display a dashboard from a remote server. The system includes a built-in PostgreSQL database, a database explorer, a VNC server, and an MQTT broker.

Three.js demo on fromcubes-portal-react.

I've been working on integrating Three.js with the FlowFuse Node-RED Dashboard to build a more interactive production monitoring system.

Instead of only displaying a 3D production line, each machine can be clicked to open a detailed dashboard with real-time production information, including:

• OEE (Availability, Performance, Quality)
• Hourly production output
• Production charts
• Machine-specific status and metrics

The idea is to combine the strengths of a 3D Digital Twin for plant visualization with a traditional 2D dashboard for detailed analysis. Users can quickly navigate from the overall production line to machine-level information without leaving the 3D scene.

This is Part 8 of my Three.js in FlowFuse Node-RED Dashboard series.

I'd love to hear your feedback or ideas for improving this approach!

https://reddit.com/link/1v7od0a/video/5z3poad6uofh1/player

I've been experimenting with Three.js inside the FlowFuse Node-RED Dashboard to build interactive industrial dashboards.

This project is a 3D Greenhouse Monitoring Dashboard featuring animated fans, ventilation turbines, lights, doors, water level visualization, weather station, multiple camera views, and clickable monitor screens.

To make it closer to a real industrial application, I use Modbus TCP. Device status is stored in Coil Registers, while sensor values are stored in Holding Registers, making it easy to replace the simulation with a real PLC or Modbus device.

Full Video Tutorial

https://reddit.com/link/1v56ccj/video/e3nf10bva5fh1/player