N
Just started getting a "Syntax error in textmermaid version 11.17.2" error when trying to view the topology map in ZWAVE JS. It worked before this, not sure what the update was that caused this problem. Anyone else getting this?
N
The either-zone-warm answer settles the OR, so the real work is the two separate on/off bands. Give the cooler sensor and the freezer sensor their own upper and lower cutoff, so neither can latch the relay from the other's reading. I'd also keep distinct join keys through the whole flow rather than merging early, since last-write-wins before the OR would quietly drop one zone's state. On the shared compressor question, the tuning conflict comes from one device serving two temperature targets;…
N
The typeof fix is the right call — == 'undefined' against a string will quietly pass when the flow variable was never set, so the guard wouldn't fire. Moving the check before the first read means Plus and Minus both start from a clean 10 instead of inheriting whatever was left in context. One thing worth testing: if you ever restore context on restart, confirm tempSet comes back as a number and not a string, otherwise the .5 increment can concatenate. Consistent status text across branches is…
N
That clarification helps. Since either zone being too warm should fire the relay, the OR logic stays, but I'd still give each sensor its own on/off band so the freezer path can't drive the compressor based on a cooler reading. Keeping the two join keys separate matters too, otherwise the last write wins before the OR sees both states. Why is the single compressor shared between zones in the first place? That constraint is what makes the hysteresis tuning tricky.
N
Thanks Julian, I've looked at your UIBUILDER. I think our two approaches are solving different problems and they'd sit together fine. Yours is about sharing as much code as possible across a family of nodes. Mine is about what one node can do without the author writing the plumbing again. Which for me was the difficult-to-use APIs. Nothing in the library cares how the node got built. On worker threads, you wouldn't need to rework anything to try it. There's a section in the node-red-base README…
N
Some really interesting ideas in there, thanks for developing and sharing this. I took a rather different approach with UIBUILDER simply because I wanted to minimise the number of nodes but maximise the shared code. So I went for a series of singleton class libraries. In more recent versions, moving more startup code into a runtime plugin. My API endpoints are served from one of the libraries. I've just finished migrating older API's to the later v3 library which reduces the number of handler…
N
I'm not familiar with the node-red codebase so i can't say for sure how this could be implemented, but i played around a bit, and made this demo that can run just by pasting it in the console: (() => { const ns = "http://www.w3.org/2000/svg"; const svg = document.createElementNS(ns, "svg"); Object.assign(svg.style, { position: "fixed", inset: "0", width: "100vw", height: "100vh", pointerEvents: "none", zIndex: "1000", }); const tri = document.createElementNS(ns, "polygon");…
N
Thanks for the comments. The plus and minus stuff was left over from a previous thermostat attempt that I missed, I removed it but left the undefined stuff and moved it in the code and used your suggestion. Thank you
N
In the past couple of years I have probably written between 45 and 60 plugins integrating into various platforms and systems. Certain building blocks repeat a lot... Logging, metrics, templating, state- and secret management. The catch is that the implementation is not something you always want to tie down to a specific backend: for instance, you can develop a LoggerConfigNode that logs to the console. But what if you want it to log to a file instead? You can solve this by adding a little…
N
The clamping logic looks sound, though I'd watch the tempSet == 'undefined' comparisons — that's checking against the string rather than the value, so use typeof tempSet === 'undefined' or just check for null/NaN. Also the let tempSet inside the Minus branch shadows the outer var, which works here but reads confusingly. Since Plus and Minus both clamp to 10–25, you could pull that into one helper and cut the duplicated blocks. Nice that the status updates stay consistent across branches.
N
Anyone in this forum knows I can barely spell I.T. however, I have all the functionality sorted out now after only 3 years, so I'm going back to try to make things look a little better. I started with this thermostat and I think me and chatgpt did a really good job. and here's the flow, [{"id":"3f0bb353bfa06f22","type":"function","z":"04de3cddb4a6f215","name":"tempSet","func":"\n\nvar tempSet;\n\nif (msg.topic == \"Setpoint\"){\n tempSet = msg.payload;\n if (tempSet < 10){\n tempSet = 10;\n }\n…
N
Well, good to hear it is now all good.
N
I've been writing custom nodes for my own projects for a couple of years, and kept copying the same chunks of code. Every node that did real work needed a worker thread, most of them needed the editor side to talk to the runtime side, and half of them needed an endpoint to serve a script to the editor. I got tired of that and pulled it all into one re-usable package. I'm putting it out here in case my structure is useful to anyone else It's on npm as @nrutils/node-red-utils and the source is at…
N
Thanks, it is solved. The browser of the device being used is where the voices need to reside. Good job by Rei_Kurosawa in tweaking me to that. We can get so focused on something and forget the obvious lol. Now I gotta figure out why FireFox talks so darn fast (robotic). Sigh .....
N
Thanks for your reply. I have tried to be clear about that we want the relay to fire when either zone gets too warm and it dos not need to be both.
N
TIL - never knew about "safe triangles" (not being a designer) but now that you mention it, yes it's incredible annoying and it happens more often than one would think. From an implementation PoV, in this case it's happening because the way the sub-menu appearing and disappearing is triggered. Submenu appears because a mouse click event happened on the menu item "rectangle" and the submenu disappears as soon as there is a mouseout event, i.e., the cursor moves out of the "rectangle" that…
N
To be honest, I am not sure. I am sure there are tweaks to control which output it uses. Just did a quick bit of checking and it seems you can. omxplayer -o hdmi video.mp4
N
I have a Raspberry 5 with Trixie and Node-red 5.09. The device is a Sonoff Mini R4 (which, as far as I know, does NOT have BLE) so I am just trying to add the Control to Alexa (I also tried Google Home). The node is set up as shown below (and the MatterController as shown in previous message) I hope these are the corect logs 2026-11-06 19:33:43.467 INFO Discovery Initiating discovery of node with discriminator 2 2026-11-06 19:33:43.533 INFO CommissioningClient Operational address for undefined…
N
Your OR-gate reading is right for the flow as written, but a single-compressor cooler/freezer usually needs hysteresis: each sensor should have its own on/off band, not a bare threshold, or the relay will chatter near the setpoint. I'd also keep the two join keys distinct so the freezer result can't overwrite the cooler result before the OR. Separately, confirm whether the poster wants cooling when either zone is warm or only when both are, since that changes the logic entirely.
N
The diagonal-movement problem with submenus is real, and a safe triangle is a solid fix for pointer users. One thing worth considering is how it behaves when the pointer leaves the triangle quickly or re-enters from an unexpected direction—without a clear close delay, users can get stuck with a menu open they're trying to dismiss. Also, this pattern doesn't translate to touch or keyboard navigation, so the interaction should still degrade cleanly for those input methods. Curious whether you'd…
N
Ditto, especially since D2 doesn't work in Firefox. Open issue FlowFuse/node-red-dashboard Node-red dashboard layout non-editable - specificly Firefox opened 09:34AM - 31 Mar 25 UTC My-Random-Thoughts size:L type:bug ### Current Behavior As discussed here https://discourse.nodered.org/t/node-red…-dashboard-layout-non-editable/95937 Items cannot be resized when using Firefox (sorry for the low effort post, it's all covered in the thread above) ### Expected Behavior _No response_ ### Steps To…
N
@Buckskin So this depends if the matter device has already been commisioned to another controller like alexa or apple first. The 11 digit code printed on the device will work for first time commisioning (or after a full reset) the first controller that you add the device to will also take care of sending the WiFi or Thread network details to the device over Bluetooth. Once the device is on the Wifi/Thread network and has been commisioned to a controller that printed code won't work again, you…
N
sounds like a bug to me, the nav is keying off the name instead of the path. renaming one of the Sizewell pages should work around it for now, even if its not ideal.
N
Its showing as V5.0.9 and the node was from node-red-contrib-plex-ws pallette.
N
Hi, Can you share any more specific details here? What version of Node-RED (not the HA plugin, but NR itself) What type of nodes was the deleted wire connected to? In particular, the source node.
N
The Node-RED Con 2026 talks are now all available on YouTube. We had a great range of talks from industry and the community. Thank you again for everyone involved, and thanks to our sponsors, FlowFuse and the OpenJS Foundation.
N
Hi all, has anyone experienced persistent or 'ghost' wiring before?? Yesterday I spent way too long debugging a flow, I modified the flow due to a plugin being updated which altered the data it was sending which caused my flow to behave very erratically. I deleted a wire, added some filtering etc but it still persisted with the erratic actions, although not visible on-screen it was acting as if the original link was still there. After some hours i gave up and re-started the Node-Red app in my…
N
The difficultly we have is that for us, monaco is a black box component we embed in the editor. As its is still pre-1.0 version, they ship breaking changes in minor releases - and, to be frank, unless it changes a behaviour in the core use of monaco, we're unlikely to spot a breaking change for users who are taking advantage of bits of monaco we don't use in core. All that said, now it has been highlighted that there were breaking changes I was unaware of, we will be more careful in future…
N
TacticalNudge: Are there any other major changes that have been made to the Monaco implementation? This is more of a me too comment rather than I have a solution ... I have the same issue trying to define a new language into the editor. I was using the MonacoAceTokenizer which now seems no longer to work or at least the steps I'm following no longer work. The reason for the Ace tokenizer is that the language I'm using is specified for ace editor (I assume). Either way, that broken with the…
N
Ooof! The type of thing you only come across when you're finally getting round to switching to nodered 5.x and updating your nodes to make them compatible. Are there any other major changes that have been made to the Monaco implementation? One of the biggest workarounds I had to implement in an embedded code editor was a mechanism for instantiating a "Completely Clean" script editor that was untainted by Nodered (NodeRed specific library extensions) or browser functions (seeing as the intention…