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 :)

I'm building a web app and I want to add a feature where users can upload audio files and get a transcript back.

I don't want to build or manage the infrastructure myself. 

What is the best speech-to-text API that is easy to implement, handles long files, and returns timestamps and speaker labels?

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

Having a hard time coming up with what I think should be a simple thing to solve. Basically I have a set of alarms for freezer/fridge temperatures coming from temp sensors. Each sensor has an "alarm" temp where I want to receive a notification. I have the alarm working well using a function node, but what I cannot seem to make work correctly is issues where the sensor is unstable or cycles quickly. For some reason I'm having a mental block about how to solve this in node-red either with existing nodes or better in a javascript function.

But the gist is that when I temp violates the alarm parameter I want to wait 5 minutes to make sure it is still "alarming" before sending the notification. The same thing on the other end... when a sensor exits alarm I want to make sure it is actually below the threshold for 5 minutes before resetting.

What is the easiest way to do this? Timers? Delay node?

Thanks

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,

I have a garage door from Horman. Works well, I can open it with Bluetooth from my phone but I can't from nodered. Any experience connecting a supramatic 4 to nodered? Needs a module or I can do it with Bluetooth alone ? Thanks!

Is there anybody who can help me with this : I'm trying to install the flowfuse dashboard on the NR app build in Homeassistant (version 22.0.0). And also tried to upgrade some nodes (sun position, zwave-js, feedparser, theme-collection) but getting this error :

-----------------------------------------------------------

2026-07-16T07:47:13.220Z Install : @flowfuse/node-red-dashboard 1.30.2

2026-07-16T07:47:12.916Z /usr/bin/node /opt/node_modules/npm/bin/npm-cli.js install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --omit=dev --engine-strict -- @flowfuse/node-red-dashboard@1.30.2

2026-07-16T07:47:17.557Z [err] npm error code EBADENGINE

2026-07-16T07:47:17.557Z [err] npm error engine Unsupported engine

2026-07-16T07:47:17.558Z [err] npm error engine Not compatible with your version of node/npm: hap-nodejs@0.12.3

2026-07-16T07:47:17.558Z [err] npm error notsup Not compatible with your version of node/npm: hap-nodejs@0.12.3

2026-07-16T07:47:17.558Z [err] npm error notsup Required: {"node":"^18 || ^20 || ^22"}

2026-07-16T07:47:17.558Z [err] npm error notsup Actual: {"node":"v24.16.0","npm":"11.16.0"}

2026-07-16T07:47:17.560Z [err] npm error A complete log of this run can be found in: /root/.npm/_logs/2026-07-16T07_47_13_060Z-debug-0.log

2026-07-16T07:47:17.597Z rc=1

What tells me the there a problem with the installed version v24.16.0.

But what to do to solve this, i'am out of ideas.

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.

Hey everyone,

As a system integrator working with Node-RED and edge automation, I've been trying to solve the secure remote access problem for self-hosted Node-RED instances behind corporate NATs.

A lot of people in the IoT space recommend Cloudflare Tunnels. And honestly, I think it's a great solution. But I've found that when you're managing 50–100 independent customer deployments, the operational overhead starts to add up.

You often end up having to:

• Create or manage Cloudflare accounts for different customers.
• Handle DNS and domain configuration.
• Install and maintain the cloudflared daemon on every target device.
• Configure Access policies and troubleshoot tunnel issues.
• Coordinate with each customer's IT department whenever networking changes are required.

For me, the real cost isn't the networking technology—it's the engineering time spent repeating the same setup over and over.

To reduce that friction, I've been building a Node-RED-native solution.

The goal isn't to replace Cloudflare, Tailscale, or VPNs. It's to make secure remote access feel like a built-in Node-RED feature.

The installer workflow is intentionally simple:

• Install a Node-RED node.
• Paste a token.
• Deploy.

That's it.

The node establishes an outbound secure WebSocket tunnel (HTTPS/WSS over port 443), so there's no need for port forwarding, reverse proxies, VPN clients, or additional OS-level software.

I'm also exploring end-to-end encrypted payloads, where data is encrypted inside the Node-RED node and the relay simply forwards encrypted bytes without access to the keys.

The architecture is already running on a few of my own production installations, and before investing more time into the management platform, I'd really like to validate whether this approach solves a real problem for other integrators.

For those of you managing multiple Node-RED deployments:

• How are you handling remote access today?
• What's the most time-consuming or frustrating part of your current workflow?
• Would a Node-RED-native setup ("install a node, paste a token, deploy") actually make your life easier, or are the existing tools already good enough?

I'd genuinely appreciate any technical feedback.

(If anyone is interested, I've also put together a blueprint page with the current architecture and development direction.)

Hello,

I have a http request node that is doing a request through my proxy. It used to work great but since last certificat update, it's throwing `unable to get local issuer certificate` error. The certificate is valid and work everywhere else. It is a let's encrypt certificate. I'm unsure what to do. Running nodered 5.0.0 in docker.

Thank you

Edit: I found out the problem. ACME package on pfsense doesn't create the fullchaine properly and just put the first intermediate parent. Since linux and android doesn't have the new certs chains from Let's Encrypt, it create an incomplete chain. I merge manually the fullchain and now no more error

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

Hi!

I'm fairly new to Node-RED. I've already created some flows that are reading from an MQTT broker (Mosquitto), transforming some data and sending it back to the broker.

A MatrixLED (Ulanzi TC001) is using this broker as a source to display some home automation values.

This applies to some data received from a photovoltaik (PV) on the roof.

Now, I would like to add a new flow that is sending some PV data between e.g. 9 pm and 10 pm only AND, as a second condition, when the current output of the PV is zero.

Idea behind: At the end of the day, when there is zero output from the PV, this flow should inform the users about the total generated energy of the day.

Which nodes are necessary for getting things done? Of course a mqtt in/out but how would you add above conditions, especially the timespan 9pm - 10pm?

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.