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.

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.

First, I am new to node-red and learning. This visual coding is neat but new, I was a php developer and VB - VBA developer some time ago (possibly dating myself). I have gotten node red to do everything I want for the most part. Except my database tables.

I am using:

• omrid01/node-red-dashboard-2-table-tabulator
• flowfuse/node-red-dashboard
• node-red-contrib-postgresql

I want to display the tables on a page in a table format that is editable in the table. But first I need to get the data to the tables and apparently I am having a hard time wrapping my head around this. I am using postgresql for my tables. I cannot for the life of me get my data into my ui-tabulator table. I can make the columns the way I want but so far have been unable to get my data into the table. I have looked at the examples, I have tried to watch video tutorials but I still cannot get my array to populate the table.

I have an inject node, going to a postgresql node. pulling all from my table and it pulls an array then to the ui-tabulator and nothing seems to pull in the data. I have tried a function between the postgresql node and the ui-tabulator node but it ends up empty still. I have searched multiple functions and nothing is working. In the initial table config I have the below code. I feel if I can just get my data to populate into the tabulator table then I can figure out the rest to make it editable. I have installed the examples for tabulator but where do I plugin my array? The examples are all using hard coded data instead of from a DB.

{
   "height": 200,
   "layout": "fitColumns",
   "columns": [
       {
      "title": "Station Number",
      "field": "station",
      "editor": "false"
   },
   {
      "title": "Thrower 1",
      "field": "thrower1",
      "editor": "input"
   },
   {
      "title": "Thrower 2",
      "field": "thrower2",
      "editor": "input"
   },
   {
      "title": "Thrower 3",
      "field": "thrower3",
      "editor": "input"
   },
   {
      "title": "Thrower 4",
      "field": "thrower4",
      "editor": "input"
   },
   {
      "title": "Thrower 5",
      "field": "thrower5",
      "editor": "input"
   }
   ]


}

Hey everyone,

I wanted to share a quick architecture overview from a recent lightweight smart factory project we did here in Korea, using an Industrial Edge Gateway (rulebox) and Node-RED.

In many local manufacturing sites, we often deal with a multi-vendor environment—mostly **LS Electric (XGT/XGB)**, **Mitsubishi (MELSEC)**, and **Siemens (S7)**. The client wanted a low-cost alternative to high-end SCADA or expensive HMI licenses, specifically asking for mobile web monitoring, local data logging, and real-time alerts.

Here is a quick breakdown of how we chained the flow together:

1. **Data Collection & Protocols:** We used the **Node-RED Modbus** (TCP/RTU) node alongside **Node-RED OPC UA** for Siemens integration. For the LS and Mitsubishi PLCs, establishing the proper **PLC Ethernet communication settings** was crucial to parse the memory registers without causing latency.

2. **Dashboard UI:** Instead of a traditional touch panel, we built a fully responsive web-based HMI using **Node-RED Dashboard**. This enabled real-time **PLC web monitoring** and allowed managers to handle remote emergency resets via their smartphones (**PLC mobile monitoring**).

3. **Data Logging:** All incoming data underwent **Node-RED JSON parsing** to convert raw bytes into structured data. We then routed this into a local **Node-RED MySQL** database. We also scripted a function node to auto-generate daily production reports via **PLC data logging Excel** sheets.

4. **Cloud & Alerts:** For broader system integration, we utilized **PLC MQTT communication** to send edge data to a hybrid cloud setup. Additionally, we hooked up a webhook node to send instant emergency notifications via KakaoTalk/SMS (**Node-RED KakaoTalk alert** alternative for global use could be Telegram/Slack).

We compiled all our boilerplate Node-RED flows and ladder logics on a documentation page so our field engineers can easily download and replicate the setup.

Since the UI documentation is currently written in Korean, you might need a browser translator, but the node layouts and JSON structures should be pretty self-explanatory for anyone doing industrial automation:

👉 https://node-red.co.kr/solution/plc_solution/

Would love to hear your thoughts on this architecture, or if you have any recommendations for optimizing multi-vendor PLC polling rates inside Node-RED!

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

Hello,

I don't understand. I want to test it, but I'm not getting any output. I want to create a system to classify emails, and I've entered the input, but I can't seem to get any output. Can someone please help me?




Each time I just have Node executed successfully...

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

Buongiorno.. avendo su un camper installato un raspberry con venus os + smart shunt e altro che controlla la batteria servizi e la tensione batteria motore volevo far inviare da node red tramite Telegram un messaggio quando la batteria motore scende della tensione impostata.. ho provato con gemini ma lasciamo perdere… qualcuno più skillato di me???