N
mudwalker: Lambdas For me, the ability to drop into a lower-level language from something higher-level is a familiar feature - since that was baked into BBC Basic on the BBC Microcomputer by Acorn back in the 80's! (You could drop into Assembly language within BBC Basic code) Though ESPHome gives it a technical name, it is just the ability to write snippets of C++ inside your YAML configuration. Very nice, extremely flexible.
N
Had my first experience recently with ESPHome. I have been drifting in and out of ESPHome for a while and initially found it quite complex to understand - you seemed to have to be 'in the know' to get things running. I did manage to get 5 Thermocouples talking to MQTT, a simple, quick, dirty project that came together in less than an hour. I had bought a Relay Board with a built in ESP32 because it might come in handy, and it did! That project required a little more finesse, but it actually…
N
With a repeating inject we can use a function node and file based context to pass only one message in a given time period, regardless of restarts. I don't think we can currently do this without a function, but I guess the delay node could be modified to retain a timestamp [per topic]. And a when gate can provide further filtering:
N
I understand the use case. it's been requested before, but the challenge is there aint one correct behaviour that suits all. Not that I can see anyhoo. Consider a few examples: Example 1: Daily schedule Schedule: Every day at 09:00 Node-RED starts at 11:30. Questions: Should Cron Plus trigger immediately because today's 09:00 event was missed? Should it do nothing because the event is already in the past? Should it only trigger if startup occurred within a configurable period after 09:00? How…
N
Steve-Mcl: Hold ctrl and: On Mac this seems to be shift at least on my setup: When I use the ctrl I just get the context menu.
N
Hold ctrl and: click in the middle of a node selects all connected upstream and downstream click far right of a node selects all connected downstream click far left of a node selects all connected upstream
N
Walter - your image is not accessible as it is stored on 'private-user-images'. Could you just do a screenshot of your NR flow and post that?
N
Hi, I really like the many possibilities and flexibilities w this node. So I just wonder, something I realize I miss, a setting that makes the node wake up at startup and activates the current relevant schedule. Like inte the example below; depending on when the node is (re)started it should check which of the shedules is currently active and then trigger that so the payload is sent out. If sun is up, I would expect the sunrise schedule to be triggered and the opposite if the sun is already…
N
Welcome to the forum @bushlander. Take a look at https://discourse.nodered.org/t/selecting-up-and-down-stream-nodes-without-backward-forward-traversal/101911
N
Ok but I don't right now suggest any badges that are not already shown, just showing them on more lines of the output. I don't know how simple it would be. Presumably both node and tab have actual error/dirty flags while groups do not. I did mention linter badges but @ThingsTinkerer says there is already a sidebar for linter, so no need to add these.
N
Hi, I'm using the version1, half control is made manually by dashboard's interface, half is by scenarios and automated logics. As I want to reflect the status of the automations I pass-by the message throught the button, so I enable the function. Now I would translate the button name to another language, so I input a msg.label only but as result I have a msg.payload output with the actual status, this will generate hardware commands that I would not do. Any way to make the button node output…
N
The speedcolors function is built as computed property Reasonable. in taht case you don't need to call it as a function but have that property usage defined in component Hwre's how: <svg ref="hn-gauge" width="100%" height="97.8%" viewBox="0 0 100 100" :style="{'--svg-fill-color':speedcolors }"> And you defenetely need to remove the ... setProperty thingy completely
N
Welcome to the forums @ottsm. I appreciate v11 changed things quite a bit, I needed to re-engineer a lot of the internals, as it got impossible to maintain. The new architecture allows me to better keep up with new features when the underlying driver introduces them. I have seen networks with 200+ nodes, that do initialisation routines, and they are always using the Global Value DB, so your switch to start using it, is the right one So I will answer based on using getValueDB (there are other…
N
I've been converting my old flows over to version 11 of zwave.js. First of all I appreciate all the hard work that was put into this development. I figured most of what is needed in my code to make the conversion. One issue is really got me struggling, at least as far as trying to make it as simple as possible. Before when I would first start a flow I would always use a GET command to retrieve the initial value. The get command would go to the device node and then pass the information into the…
N
Plugins can certainly add their own node annotations - as nrlint does. Whether they should propagate to the flow tab and explorer is another matter. The node body has space for multiple badges, but the space in the flow tab and explorer is limited and we risk it just looking bad with too much crammed in. Will need thinking about before jumping into implementing anything.
N
The linter I use has its own tab down right corner, next to debug, context etc. Think it was this one: node-red/nrlint: Node-RED Flow Linter
N
This is what I've got so far <script> export default{ data(){ return { //define me here min:0, max:100, label:"Gusts", measurement:"Speed", unit:"MPH", majorDivision:10, // number of input units for each (numbered) major division minorDivision: 2, // number of input units for each minor division //sectors:[{start:0,end:20,color:"forestgreen"},{start:20,end:40,color:"skyblue"},{start:40,end:60,color:"gold"},{start:60,end:80,color:"#e99200"},{start:80,end:100,color:"red"}], valueDecimalPlaces: 1,…
N
Colin: However it appears that for contributed dashboard nodes this does not happen automatically You are right, it doesn't - nodes have to use the same technique as dashboard does. Ideally, the size widget could be made to detect its environment and fall back to manual inputs. Not sure how feasible that it though. I'll have a chat with my colleague.
N
two important commands on Windows cmd prompt to stop and start (for example this is helpful for update) pm2 start node-red pm2 stop node-red
N
It'll be better for world if I don't try to explain the this in JavaScript. There are tons of free to read documents to examine. I saw the function you try to use, it does return color so it should work. But there's a lot of things what can be wrong. I'm really bad on blind debugging.
N
So in your example document. is similar to :root in as it refers to the top-level, documentElement. refers to the specific element. You wrote the setProperty() value as this.speedcolors(). My understanding is that this. is used in a function to refer to itself, is that correct?
N
When I use, for example, a ui-gauge in a subflow, instead of the usual Size field I see which allows the configuration of the size and the position in the subflow to be specified manually or passed in via subflow fields. However it appears that for contributed dashboard nodes this does not happen automatically. I think that the node author has to detect that the node is in a subflow and adjust the configuration dialog manually. Is how the author should do this documented somewhere? I notice…
N
For the future, please see this post for the recommended way to post flows - How to share code or flow json
N
Hi all, I help run APIVerve, an API catalog where one key works across 380+ APIs: email and phone validation, IP geolocation, DNS and WHOIS, weather, currency and stock data, PDF and QR generation, and more. We've built a Node-RED node for it. It's a single apiverve node: Pick the API from a list grouped by category. The edit dialog shows that API's parameters. Send parameters in msg.payload. A plain value fills the API's only required parameter, so an inject node can send just an email address…
N
The learning curve, oh ya yeah, this is a big one. I do prefer it over just straight raw interpretation of code That is a total different world for me. I remember learning it in preschool when I was a kid, but that pretty much changed once I hit junior high. Still, now I have got time on my hands Why not take on something that who knows Might just be a little fun lots of sarcasm here I did upload a full flow but it is quite large, if you would like something small im not sure what is considered…
N
It’s done Note: @types/node-red (the parent) has not yet moved to v5, as a few updates are still required.
N
kuema: I'm referring to things like include/import. Ah, I see. Yes, those weren't obvious to begin with. I think I had to ask in the forum. But once I'd set a base folder to my original ESPHome source folder, everything worked as before. kuema: With ESPHome it is quite advanced, because you can create reusable components by using the packages feature. Yes, I'd done this from the outset because I have multiple different microprocessor platform types with a lot of common sensors, controls and…
N
TotallyInformation: Didn't know that YAML had any advanced techniques? I'm referring to things like include/import. Those are not standard YAML (also not standardized), but mostly parser or runtime specific features. With ESPHome it is quite advanced, because you can create reusable components by using the packages feature. Even nesting multiple levels is possible. I've not seen comparable features in common parser libs like js-yaml for Node. ESPHome - Smart Home Made Simple Packages How to use…
N
Sounds good. Happy to look at a PR