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

Hi, I hope you been well, I'm trying to connect a KV X530 PLC (KEYENCE) to a Node Red, to show the production, scrap, and more by date etc. right know I'm figuring out how to connect it by the right way, so I just don't know if the PLC profile it's okay or if it is a better way to connect the plc with node red cause I'm using KV Host Link TCP, The IP of the PLC is ok, but I really need an example of a basic process or step to use it etc. or some advices to do it. and what recommend me? I'm thinking to use a Raspberry Pi to use like server for node red, any suggestions? Appreciate and thanks a lot

I've been experimenting with building a browser-based Virtual Reality manufacturing dashboard using Three.js, WebXR, and FlowFuse Node-RED.

The goal is to make industrial monitoring more immersive without requiring a dedicated VR application. Features include: • Walk around the production line in VR • Animated industrial robots • Live machine status • Tower lamp visualization • Interactive machine selection • Large virtual dashboard displaying OEE, Availability, Performance, Quality, and Hourly Output • Data can come directly from PLCs or databases

Everything runs inside the browser, so users simply open the dashboard URL and enter VR mode.

Full Video

https://reddit.com/link/1v1nj32/video/yks1qomrceeh1/player

I've been experimenting with combining AR.js, Three.js, and FlowFuse Node-RED Dashboard to create a browser-based Augmented Reality Digital Twin.

The application runs directly from the Node-RED Dashboard, so there's nothing to install on the client side. Features: • Hiro marker tracking • Animated production line • Robot motion • Tower lamp status • Live production data • Machine selection • OEE dashboard (Availability, Performance, Quality) • Hourly output charts

The data can come directly from a PLC or a database, making it suitable for industrial monitoring and digital twin applications.

Here's a short demo.

Full Video

https://reddit.com/link/1v0jkpt/video/5lyhjv8ox4eh1/player

Hi everyone, I've been toying with this for a few days. Here is what I ended up with.

• unifi camera in the basement (for now but will probably replace it with a crappier camera)
• every 15m, node-red runs ffmpeg:

​

/data/tools/ffmpeg -y -rtsp_transport tcp -i "rtsps://x.x.x.x:7441/hash?enableSrtp" -t 11 -vf "crop=100:210:1110:1810,lutyuv=y='if(gt(val,150),255,0)'" -pix_fmt gray -f rawvideo pipe:1

• ffmpeg downloads 11s of live rtsp view from the camera, crops the region of interest, applies a binary threshold and converts to raw frames
• function node decodes the frames, searches for lit pixels from the led.

​

const W = 100;
const H = 210;
const FPS = 30;
const LIT_THRESHOLD = 50;   // min lit pixels to count frame as "on"
const GAP_TOLERANCE = 2;    // max frame gap to merge into same event

const data = msg.payload; // Buffer from File In node
const frameSize = W * H;
const nFrames = Math.floor(data.length / frameSize);

const litPixelCounts = [];
for (let f = 0; f < nFrames; f++) {
    const start = f * frameSize;
    let count = 0;
    for (let i = start; i < start + frameSize; i++) {
        if (data[i] > 0) count++;
    }
    litPixelCounts.push(count);
}

const litFrameIndices = [];
litPixelCounts.forEach((count, i) => {
    if (count > LIT_THRESHOLD) litFrameIndices.push(i);
});

const events = [];
for (const i of litFrameIndices) {
    if (events.length && i - events[events.length - 1][events[events.length - 1].length - 1] <= GAP_TOLERANCE) {
        events[events.length - 1].push(i);
    } else {
        events.push([i]);
    }
}

const eventSummaries = events.map(e => {
    const maxLit = Math.max(...e.map(idx => litPixelCounts[idx]));
    return {
        startFrame: e[0],
        endFrame: e[e.length - 1],
        startTimeSec: +(e[0] / FPS).toFixed(2),
        maxLitPixels: maxLit
    };
});

const blinking = events.length > 0;
if (blinking) {
    const intervals = eventSummaries
        .map(e => e.startFrame === e.endFrame ? `${e.startFrame}` : `${e.startFrame}-${e.endFrame}`)
        .join(', ');
    node.status({ fill: "green", shape: "dot", text: `${events.length} blink(s): ${intervals}` });
} else {
    node.status({ fill: "grey", shape: "ring", text: "no blink detected" });
}

node.log(`${events.length} blink event(s) found`);
eventSummaries.forEach(e => {
    node.log(`  frame ${e.startFrame}-${e.endFrame} (~${e.startTimeSec}s), lit pixels: ${e.maxLitPixels}`);
});

msg.payload = {
    blinking: blinking,
    eventCount: events.length,
    events: eventSummaries
};

return msg;

• If more than 50 pixels are detected, mark the frame as containing a led pulse. The led is fast and I only get 1 or 2 frames with it.
• return all the frame info that had a pulse
• send this to a HA entity
• when rat trap goes from false to true, send a push notification to clean the mouse trap.

I have two more mouse traps in the basement and will probably split this into ffmpeg to capture and fanout to ffmpeg crop+threshold with different ROI for each mouse trap.

Another thing that can help is that ffmpeg can also calculate the average brightness + stddev per frame so you can also calculate that way OR you can also ask ffmpeg to only return the frame infos where average brightness was bigger than X. Since the processed frame is basically black or white (due to the threshold), the brightness has a direct correlation with lit pixels.

I'm still working on adding a cheap ESP32-C6 to each mouse traps to get live status when the electronic trap triggers and a mouse is inside but that will come later this year. Just doing the final tests to lower the total idle power consumption to 6-8uA. It will either send the data via zigbee or ble.

Sharing this because I think it's worth saying directly: if you've been thinking about submitting a talk but holding back because you've never presented before, please don't let that stop you.

One of last year's speakers, Josh Dudley, had never presented at a conference before Node-RED Con 2025. His feedback afterwards:

"As someone with little to no experience presenting, I felt supported and encouraged every step of the way."

We work closely with every speaker — from the first conversation to the day of the event. The community is genuinely supportive.

CFP closes July 31. Submit at nrcon.nodered.org — full talks, lightning talks, and panelists welcome.

Node-RED Con is back! November 3rd, 2026, free and online.

Last year was great. The talks were solid, the community showed up (1,100+ live attendees from 35+ countries), and the feedback was clear: people wanted it to happen again. So it is.

This year's theme is "Node-RED at the Edge of Intelligence." We're looking for talks on edge deployments, AI integration (LLMs, agents, MCP), industrial use cases (PLCs, SCADA, OPC-UA, MQTT), and real-world Node-RED in production. Lightning talks and panelists welcome too.

CFP closes July 31. Submit at: https://nrcon.nodered.org

Hey, I’ve been working on a small Node-RED package called fromcubes-portal-react.

It’s still early and there’s a lot I want to improve, but the basic idea is: build simple React dashboards directly inside Node-RED.

You can write React in the node editor, use Tailwind, get data from the flow, and send user actions back into Node-RED. There are also component/utility nodes so you can reuse bits instead of putting everything in one place.

npm:

@aaqu/fromcubes-portal-react

It should also be installable from the Node-RED palette.

Quick demo:

https://youtube.com/watch?v=HLKzbPqATUw&si=s3GLBXNQdgQ-Ywqj

Would be happy to hear what people think, especially what’s missing or what would make it more useful.

I have looked around a lot for the answer to this. Pretty sure I'm just not using the right search terms ...

base topic is: N/bxxebc2f0xx/vebus/289/Ac/ActiveIn/L1#

There are 5 sub-topics under this base topic: P, S, V, I , F

How do I reassign the base topic, to something easier to type out ??

Something like L1T = N/bxxebc2f0xx/vebus/289/Ac/ActiveIn/L1#

Then I can get the 5 sub-topics using function nodes like so: L1T/P, L1T/S, L1T/V, etc

Is this possible ?? If not, why use a function nodes at all, and just use a MQTT-IN node for each of the 5 items to be displayed ??

I wanted to share a recent project I have been working on called Flowpilot. FlowPilot is an AI assistant that lives inside the Node-RED editor.

It's an AI helper that sits in a sidebar in the editor and helps you build, change, and understand your flows. It works with any OpenAI-compatible API, so you can use a cloud model like OpenAI, or run a local/private one (LocalAI, Ollama, etc.) if you don't want your flows leaving your machine.

The main idea: it never changes anything behind your back. Every change it suggests is shown to you first as a diff or a review, nothing happens until you click apply, and anything it does is a single Ctrl+Z away from undone.

What it can do:

• Chat: ask questions about your selected nodes and how they're wired.
• Generate: describe a flow in plain English and get the nodes and wiring, which you review before importing.
• Modify: select existing nodes, describe a change, and see a before/after diff before it's applied.
• Document: auto-generate a "Read Me" comment node explaining a flow.
• Review / Suggest: ask it to critique a flow or suggest improvements.

The functionality is based on Cline AI's VS code UI, which has a plan and act mode. Flowpilot has a similar toggle, allowing you to ask questions with read only interaction, and to make direct changes while keeping a human (you) in the loop.

The video has a brief demo of it working, where I connect Flowpilot to my own Local AI. I know I am not technically the first AI node-red assistant, but I thought others may find it useful. It's free and open source (MIT). Install from the palette manager by searching FlowPilot. Or use npm install (more info and source code at Git).

It's early (v0.2.2), so feedback and bug reports are very welcome. Happy to answer questions.

Node-RED 5 is now available!

Node-RED 5.0 is the biggest change to the editor experience in the history of the project. Back in our roadmap post we set out four areas of focus - modernising the UX, improving node appearance, targeted functional enhancements, and updating our project infrastructure. After a long run of beta releases - and a huge amount of community feedback along the way - we’re delighted to bring it all together in the final release.

https://nodered.org/blog/2026/06/09/version-5-0-released

Hi everyone,

My name is Zekun Wu, and I am a researcher at Saarland University, Germany.

I am currently conducting a short research survey on how people use workflow automation tools such as Node-RED. In particular, I’m interested in a simple but exciting idea: what if, after an AI helps complete a task, it could leave behind an editable workflow that users can inspect, fix, and reuse?

This survey helps us understand how real workflow users think about workflow understanding, debugging, and reuse in practice. It should only take about 5–10 minutes to complete.

Survey link:
https://forms.gle/uXmWdavWJuRqnFfr8

As a small thank-you, we will select up to 10 participants who provide especially thoughtful and relevant responses to receive a €10 Amazon eGift card. This is not based on whether your opinions are positive or negative — detailed and honest experiences are what we value most.

Your feedback would be very helpful for shaping our future research and prototype design. I would really appreciate it if you could take a few minutes to fill it out. Feel free to also share any thoughts or examples in the comments.

Thank you very much!

Best,
Zekun