N
I am obviously not doing something correctly. I have loaded the Device Management Node, I have selected the Storage Location and not entered anything else, mostly as I have no idea what is required. (I did try the WiFi SSD & password of my network but it made no difference) I then went to (I tried both Google Home & Alexa as they both chat to the device) add another assistant, got the 11 numbers and entered them into the node Pairing Code field (along with the device name) inject nothing and…
N
Hi, sorry for the delay. I've tested this now. I set up the same versions you have (Node-RED 5.0.9, Dashboard 1.34.0, ui-webcam 1.1.2) and opened the dashboard in Chromium on localhost. I imported both flows you posted: the full one from your first post and the single-node export with the blue dot. Both work for me. I click the power button, Chromium asks for camera permission, I allow it, and the camera starts. Your inject "on" works too. So your flow and the node look fine. The problem is…
N
Maybe i am missing what OG poster requires. The example flow will turn on relay if either temp is below minimum. If that is not their requirement, i must have misunderstood. [edit] @houser sorry mistook @gerry as OG poster
N
Am i missing something here? It looks like a simple Thermostat issue with an or gate at end . Two Thermostat codes one for either sensor then or the result.
N
I think you need to determine if either temp is out of range, then join the messages and output every intermediatory message. You and then determine if any of the values are true and fire the compressor if either is out of range. You can apply a rate limit on the shelly triggering also. Here is an example flow. [{"id":"547fede413fdded0","type":"inject","z":"613df62afc8a16bf","name":"freexer temp -16","props":[{"p":"payload"},{"p":"topic","vt":"str"}],"repe…
N
I would suggest that the higher and lower temperatures need to be defined for a proper Power Saving Application, hence my questions.
N
I decided that a refrigerator temperature would not respond fast enough to cause on/off cycles. The incoming sensor readings though might easily vary around the trigger level eg 6.001, 5.999, 6.001. Is hysteresis the right solution for variable input data like this?
N
The hysteresis node might be worth looking at for this situation... flows.nodered.org node-red-contrib-threshold-hysteresis Node-RED node for hysteresis logic - outputs boolean based on high/low thresholds
N
isso mesmo nos dois eu estou usando anonymous e o mesmo id por exemplo no UA expert ta asiim : 2 SIMATIC.S7-1200.OPC-UA.Application:PLC_1@192.168.2.100 ns=4;i=228 UDT_PARTIDAS/CORRENTE_NOMINAL_MOTORES/VALOR_ATUAL_S VALOR_ATUAL_S 44.6 A String 12:17:59.909 12:17:59.909 Good esse mesmo esta no Node_RED
N
Colin: Won't that give alternate OFF and ON when the value is between the two thresholds? Yes of course that's right. If the cooler is too warm but the freezer is not, it will alternately send ON and OFF. Doh. It should only send OFF if neither sensor reading is above it's threshold. So the OP needs to store the readings for comparison, either using context or a join node. Here is a revised flow [{"id":"960d854436046fc3","type":"inject","z":"c45e985e77331d…
N
Você está usando exatamente o mesmo NodeId e o mesmo usuário no UA Expert e no Node-RED? Pode mostrar o NodeId usado em cada um, ocultando nomes internos e outros dados privados? Não envie senhas.
N
jbudd: does a simple function like this work? Won't that give alternate OFF and ON when the value is between the two thresholds? I think maybe it needs a Join node in manual mode to merge the two temperatures into one message before doing the test.
N
Bom dia pessoal,estou com o seguinte problema: tenho um projetinho basico no s7-1200 opcua ja habilitados. consigo monitorar as variaveis pelo UA EXPERT,porém pelo Node-RED não aparece a seguinte mensagem (StatusCode: BadNotReadable (0x803a0000) The access level does not allow reading or subscribing to the Node.) estava usando uma versao mais nova ,ai instalei uma mais antiga para ver se resolvia o problema e nada as versoes que estou usando sao: Node-RED version: v5.0.9 Node.js version:…
N
I may yet end up sticking with Bookworm (12), we'll see. What I was most after was getting pi connect set up on my headless NR machine. I've been frustrated trying to make it work on Bookworm, just keeps giving errors I can't figure out how to fix. Doesn't omxplayer send audio to the RCA jack on the pi? I was looking for audio played in the active browser, wherever (and who ever) it was.
N
Sorry for delayed response, had to go out the rest of the day. Thanks for the replies and suggestions.
N
In 0.2.355, INFO reads the attributes of one NodeId from msg.topic; it doesn't recursively browse the server. If you already have an array of variable NodeIds, a core Split node can turn it into individual messages, so you don't need a JavaScript loop function. Each message would still need its NodeId in msg.topic before reaching INFO. That is still a separate INFO operation for each variable, not one server-wide request.
N
Understood. It seems like a very good starting point. I would like to replace my old thermostat code if possible as it is built for a Homekit thermostat and we no longer use HK. But one step at a time
N
Yes a function node. I used a function rather than the basic nodes because I assume that a sensor message contains either cooler or freezer temp, not both. You could store them in context (as I think you do) and compare, I just handle each message as it arrives. I do not think it's a complete solution. For example you might need to build in an alarm in case one or other sensor stops sending.
N
Thank you! @jbudd Yes, there are separate temp payloads from the shelly addon. Is the code you sent for a function node? Is it intended as a complete thermostat flow? Your concept seems to be correct to me and I will have a look at this and try it asap.
N
Assuming that you can distinguish the input sensor by msg.topic, does a simple function like this work? It will send "OFF" whenever a temperature reading arrives, unless one or other temperature reading exceeds it's threshold value, when it will send "ON" const coolertopic = "cooler" const freezertopic = "freezer" const coolermax = 6 const freezermax = -15 let output = "OFF" if (msg.topic == coolertopic && msg.payload > coolermax) { output = "ON" } else if (msg.topic == freezertopic &&…
N
I did, several years ago, some experimental stuff running a Python script using cv2 & MobileNetSSD (cv2.dnn.readNetFromCaffe("MobileNetSSD_lpr.prototxt","lpr.caffemodel") It worked ok but since I do not really need such a solution I stopped looking further. I expect that today you should have much better libraries, models and computer power available. From the perspective of object detection I think YOLO is totally outstanding compared to the rest. It should however run on a computer with lot…
N
Pull request node-red/node-red Delay node: add option for random interval between messages in rate mode (#6043) dev ← feixm1:delay-node-random-rate feixm1 opened 11:20AM - 27 Oct 26 UTC +159 -6 - [ ] Bugfix (non-breaking change which fixes an issue) - [x] New feature (non-b…reaking change which adds functionality) ## Proposed changes Adds an option for a random interval between messages in the Delay node's **Rate Limit → All messages** mode, as discussed on the forum:…
N
OpenAI's Agent Builder is scheduled to shut down on November 30, 2026. If a production workflow still depends on it, I would avoid a direct screenshot-for-screenshot rebuild. The safer migration target is the workflow's behavior: inputs, decisions, tool calls, state, approvals, retries, and outputs. The date and migration notice are in OpenAI's official Agent Builder documentation. Here is a Node-RED migration checklist that keeps those behaviors explicit. 1. Convert the canvas into contracts…
N
Just forgot to share the LL-HLS flow... [ { "id": "d472b66a882eda03", "type": "ui-template", "z": "3a2119e9c11365e2", "group": "b7971684f73a027c", "page": "", "ui": "", "name": "", "order": 0, "width": 0, "height": 0, "head": "", "format": "<template>\n <div>\n <!-- Rubrik med dynamisk statusindikator -->\n <div class=\"header-container\">\n <h2>Camera LL-HLS stream: Tapo</h2>\n <span :class=\"['status-dot', isPlaying ? 'status-online' : 'status-offline']\"></span>\n </div>\n\n <!-- HLS Video…
N
VisuDock: Have you tried adding more viewers on the RPi3 to see where the CPU starts to climb? Thanks, I just did a simple test opening the same several times, at most 5 on my mac in Safari & Chrome as well as another 2 on a Windows PC in Chrome and Edge (it worked fine in all) The CPU load increase on the RPi3 was pretty linear I think, it increased around 2% for each "viewer". I assume the load would also be dependent on the FPS, resolution and frame size. The TAPO is a super-cheap C200 set…
N
Thanks for the write-up. The "one connection to the camera" point has a second use: other readers can pull from mediamtx too, not only browsers. A snapshot grabber or an OCR step can read the mediamtx RTSP address (default port 8554, so rtsp://PI_IP:8554/tapo for your path) instead of opening another session on the camera. That matters with cheap cameras that only allow two or three connections. If you want a light preview for phones, you can add a second path that pulls the camera's sub…
N
JohnStiekema: node-red-contrib-ui-time-scheduler You can achieve something similar (or better) in Dashboard 2 - with a little vue work and cron-plus! This could also probably be made into a subflow if you wanted multiple schedules on one dashboard page (bit more work) Demo flow (use CTRL-I to import it) [{"id":"795366fbdbd28961","type":"inject","z":"7f5380ac4139f5dc","name":"Load saved schedules","props":[{"p":"payload","v":"","vt":"str"},{"p":"topic","v":…
N
Great to see & hear from you again!! Yeah, you know, the thing puzzled my mind a bit. I understand what you say, cool stuff you are upto!! For me the late wake up with mediamtx came the other day, but better late than never I also tried the HLS stream, it worked also fine I think (didn't try the LL- variant yet). I think the RTSP from it also works pretty good, I do have rather low latency on that one as well, at least compared to using ffmpeg as we did before. I have some further idea to use…
N
Yes, mediamtx is a good tool. I came across it a few months ago when I was stress testing my current cctv server project and didn't want to put that burden directly on my cameras. You know how flaky our cameras are when you have multiple or repeated connections. krambriw: With minimum latency! It's good to hear that you are still searching for the holy grail of latency. In my new system under development, I explored webrtc, but decided to take a different path. One of my ai agents informed me…
N
Since long many of us have been searching, trying, helping & contributing in our efforts to stream & view live video from networked cameras. With minimum latency! Many contributers have spent so many, many hours helping the rest of us; Like @kevinGodell, @BartButenaers and many others, not mentioned but never to be forgotten So far, what I have experienced myself, we do have useful & working solutions even if they are a bit tricky to setup & configure, requiering several nodes of various kind…