Can anyone share the scripts that a ham radio club uses to give access to club members to a Flex6400 radio? We currently use a VPN and it works BUT users are presented witth the standard SmartSDR. I saw several examples of custom UIs that only give usess access to functions the club let's them use.

?

I for one wants to learn how to use Node Red but to do so, I need a jump start. If you can share scropts, we can use them for our club and I will then work with others to learn how to customize them, and share back. It's like how I learned how to configure code plugs for DMR and P25 ... I started wth functional code plugs, then learned how to build them

Hey Neal,

?

You should be good to complete a full upgrade on your Pi.??

?

Backup your flow to another machine before you start your upgrade.? I would also re-run the Node Red installer to make sure you are fully up to date on Node Red.? Then upgrade all your nodes to the latest by the pallet manager.

?

Good luck in your upgrades!

?

Kyle

AA0Z

?

?

On Tue, Mar 11, 2025 at 12:53 PM, Ken Kayser wrote:

antenna graphic and had a .png file, how would I create the code to include in the build node??

Ken

?

A easy way to start creating SVG code, is to use any of the popular graphic applications. ?Expoet the file as a SVG formatted file. ?This will be the code to use in the various node Red functions. ?that is how I built the meter SVG.?

?

?

You can also, embed an image file within SVG Code. ? Select in image, use an online tool to convert it to base 64. ?Put his into a fiction with msg.image = base 64 image code here. ?Put this upstream of my sag functions, in the SVG build like, add the image and you will now see he image in the button. ?The order of elements in the SVG code sets the layers, top to bottom, so put the image at the end of the SVG code.

?

?

?

Again, build a function where msg.image is the base64 code of the desired image, put this upstream of the "build StreamDeck Button" function. ? Add a variable to the line 35 SVG code, image as below. ?This will put the Image in the SGV background.

?

?

You can also use common SVG element codes, like a line or triangle shapes. ? ?The rotor graphic uses math to allowing moving the shape a coordinates of the shape, ie the one and the triangle shapes. ? Its all X/U coordinates in pixels to create the shapes, with a little trigonometry to move the stuff around in a circle.

?

Alan

Hey Warren.? I had no idea i could have the context "persist" across startups.? That's a great technique and I'll set it up.? I also see how Alan is building the graphics nodes although I have to think through the "contextR1" logic each time - I'm sure it will be clearer as I work with it.? I am still uncertain about how he comes up with the strings that actually make up the image that represents an actual graphic.? For example, if I wanted an antenna graphic and had a .png file, how would I create the code to include in the build node?? That's the piece I seem to be missing at the moment but I'm confident that you or one of the group will make it clear.? I must confess that this rabbit hole is a lot deeper and wider than I had imagined but it's great to have such willing and knowledgeable guides on the journey.? BTW, I have tried a couple of on-line png to svg converters but the output give me multiple syntax errors when I past the resulting <path> contents into the appropriate function node.? Best regards, Ken, K2KXK.

Ken

?

Excellent.? Glad you persisted with solving the issues and now have a better idea of what is going on!? ?

?

Yes, the boundary condition of not knowing all of the button contexts at startup is bothersome, but not unsolvable!?

?

You can do one of two things.? ?

?

First, you can just create a node that sets up a copy of the streamdeckContexts after it is fully populated with buttons and then assign it to the actual Global variable.?

Then fire a message from an Inject node into it, configured to fire one time 0.5 secs after node-red starts up. This would work, it's relatively easy but not very savory as it will be a maintenance

problem when you add more SD buttons.? ? Also, it's a future out-of-sight bug in the making!

?

OR, second, take the route I use and configure node-red to allow variables to be persisted on the Operating System.? You have to modify the node-red settings.js from stock to allow this.

?

?

I'm running Node-Red on a raspberry Pi so,? I'll use the nano text editor.? ?Since I have my node-red settings file "protected" by changing it's owner to root (chown), I have to use sudo ahead of nano to elevate for read/write.? If you run Node-Red on a different OS, just find where the settings.js is and edit it.

?

?

Your settings.js file should be open in nano. Now use the "Where" command to do a text search--press Ctrl+w?

and type:? context storage

then press Enter

?

?

Nano will scroll down to the Context Storage section.

?

The Context Storage section is commented out by default in Node-Red.? Remove the comment characters and make your section look like this:

?

?

This will setup the ability to save / read variables that are saved to the operating system instead of running memory.

I've changed the flushInterval to 360 from the default of 30.? This mean it will only do a hard write to the SD card every 6 minutes

but if needed.

?

Now, save the file (Ctrl+w)?

?

Node-Red will need to be restarted for this change to take affect.? These two commands will do that without rebooting the Pi.

?

sudo node-red-stop

sudo node-red-start

?

You will see the startup log scroll by, and if you didn't make any typos, node-red should be running again.

Press Ctrl+c to exit from the trace log and get back to the bash prompt.

?

Now it gets interesting.? In node-red, create a function node and read the current value of the?

global SD context variable.

?

Now, turn around use the .set command to save it back ...But first...

?

You might not have noticed yet, but the .get and .set methods have optional parameters.

Now that you have enabled a second variable store called "persist"? in the settings file

?

(remember this?)

?

?

Change the .set command to use the 'persist' store instead of the default one called 'default'

?

?

It should now look like this:

?

?

Add an inject node so you can tickle this function.? Click the inject handle.

Now, refresh your Global Context variables and look what just showed up!??

Notice the different storage context ('store') show up to tell you where it is.

?

?

Now, if you restart node-red (or reboot), if you go immediately back into the Context variables you will see the 'persist' version is still there!

Now, in your flow startup area, you can switch around the functions above to read from 'persist' and save back to 'default' . Poof, you have your?

stream deck button contexts back, and you haven't pressed the Stream Deck device buttons at all!

?

Now, if you prefer, you can use the new 'persist' storage context in the "Change" node.

?

Just click the dropdown and select the desired context.? Here is the above function coded in a Change node.

The context is hard to see, but it's there...

?

So, if you wire in above change node after the sd-input node (I'd put it after I filtered off? for just the keyDown event)

then the 'persist' version of streamdeckContexts will always be up-to-date.

?

Then, finally, make another Change node that is the reverse of the above assign 'persist' to 'default'? and wire it in to fire using an auto triggering inject node at flow startup.

When you flow first starts, the streamdeckContext (in the memory or 'default' store) will get automatically put back.

?

Clear as mud right?

?

Enjoy

?

Warren, KD4Z

?

I last used my Node-Red Raspberry Pi in 2020 at a previous home.

I just now dug it out, and it boots ok and works.

But naturally, after 4 full years, Pi-OS is offering updates and upgrades.

Does the OS upgrade break node-red? Or do people have a checklist
or suggestions before I proceed?

?

Thanks,

?

Neal? AB6G

Hey Guys. I'm overwhelmed by the generosity of the group members in trying to educate me.? I'm taking it all in and now have a working flow with the buttons changing color as Warren showed.? I have not yet attempted sending graphics but that will be tomorrow's project.? Warren, I did use your "format for SD" node instead of the SD-Out node but still ran into trouble when I had a graphic set in the SD editor.? Once I reset that to Default, all was good.? I probably had something else miscoded.? Thanks for your explanation on the "context" property.? I had noticed the context IDs in the Global NR section and based on your comments and some testing, assumed they were populated by the? SD-In node the first time each button is pressed.? I see that Alan chose to populate the flow context with the same values instead of using the global values in his sample flow..? I assume this is because he didn't use the SD-In node but rather converted to JSON on his own.? As Alan mentioned, it would be nice if we could get NR to populate these values at start up so they don't require a push of each button.? I really enjoy learning new things and it seems like I'll be busy with the process for a while.? Thanks again for everyone's help.

Ken

Hey Ken,

?

Glad you have made progress!? ?Alan has extended my "Create Basic Button" idea to have more of the fun graphic stuff, which is what I was implying could be done.

I'll let Alan keep guiding you deeper with extending the options for SVG on-the-fly.? My intent was to get you to write dynamic code and not rely on hard wired PNG files.

?

Yes, the "context" is just a Globally Unique Identifier (GUID) generated when you create a button in the Stream Deck software.? It's just a 32 byte long string of characters. When you press that button, the data that comes into the websocket in node has that GUID passed as a unique way to identify that particular button.? When your code sends data back to the Stream Deck, that context is used by the Stream Deck software to figure out which button to update.? Since you got to pick the "id" (Button ID), that isn't guaranteed to be

unique. The context is used to figure out which button to change.? After all, you could have more than one button with the same "ID"

?

If you select "Context Data" in the node-red workspace screen, then scroll down and open up "Global", (click on the "refresh" icon next it too)

You should see a variable called streamdeckContexts?It is an array object, so the first time you press a Stream Deck button, you should see an element appear in this variable.

?

In my example flow, there are four buttons with id's "ant1", "ant2", "ant3" and "ant4"? So, after I have pressed each button at least one time, the streamdeckContexts variable

will look like this:

?

?

(your GUIDs will be different than mine!)

?

You can see each button has a 32 byte identifier collected in this array.? When you get to the last part of your code that generates the data to send back to the Stream Deck device,??the sd-output node does a lookup in this context array of the "button ID" that you want to update, and then grabs the button context string to pass along to the Stream Deck.

?

My sample flow included a Function node called "Format for SD" which isn't magical as it was just the original Stream Deck out node code, stripped down.? However, it appears you didn't use it originally and ran into the quirk I've found with the Stream Deck Out (sd-output) node --and that is, the design time parameters take precedence over runtime variables being passed in.? That bit caught you out (as it has me)?

?

So I present two? Stream Deck node Quirks:

?

Rule 1:? If you use the sd-input node (which is just fine) you must always configure the preceding WebSocket In node to Send/Receive "payload"? If you set it to "Entire message",

a couple bad things happen in the following sd-input node as it is poorly written and stupidly attempts to do a JSON conversion on an input that is already a JSON object.? The result is, you will see an error in the Debug window stating "SyntaxError: Unexpected token o in JSON at position 1"?

?

If you see your sd-output node show "no context", this issue is likely the cause as the code bails out with the above error before it stuffs your button's GUID into the Global streamdeckContexts variable.? ?Another reason you might see the sd-output node show "no context" is if you don't have your Stream Deck plugged into the USB port!

?

I have written my own "sd-input" function that handles this situation with a single extra line that bypasses the JSON.parse(msg.payload); statement if the payload needs that conversion.? i.e.

?

I've run into this issue when importing sample flows from this group!? My custom sd-input ignores this issue and also keeps track of the device identifier from the Stream Deck device as part of caching?the button context.? This allows using more that one Stream Deck with the same named button actions and they can all get broadcasted updates from each other.

?

So, just configure your websocket in to output "payload" and life will get better for you.? (double click the node, then click on the "edit pencil" button on Path, to see the configured value.

?

Rule 2:? Don't set ANYTHING at design time on Properties sheet for the sd-output node!? ?The code in the sd-output node will assume you want the design-time values and ignore runtime values passed into it. ??If you do, remove the node, and add it back into the flow without touching any properties.? ?You could also delete the Configuration Node data for that node and start it over as well.?

?

That's the two biggest rules you need to pay attention to.? There could be more.

?

I've modified my sample flow to be a complete working sample.? All you need to do is create four buttons in your Stream Deck with the ids of ant1, ant2, ant3 and ant4, Point each button to the ip address and port of your node red instance with the WebSocket endpoint of /4way? For example "ws://192.168.1.100:1880/4way

?

Also for each button, click the little down arrow at the end of the Title line (after the "T") and uncheck the "Show Title" option.? You don't want the button to have your title superimposed on top of your dynamically generated button graphic.

?

I've attached the fully working flow of the 4-Gang dynamic two line button example to this message.

?

Warren, KD4Z

?

?

?

?

Ken

?

I have attache a demo flow you can use to follow along below.

?

First, for sending images to the buttons, you must send the following object.

?

{"event":"setImage","device":"3B4A178B0FA8D7408582138E1F192969", "context":"b92505aa7b38be8abe13cb04ee0c242e", ?

"payload":{"image":"data:image/svg+xml;charset=utf8,<svg viewBox = \"0 0 72 72\" width = \"72\" height = \"72\" ><rect width=\"72\" height=\"72\" style=\"stroke: rgb(0, 0, 0); fill: red; fill-opacity: 1;\"></rect><text style=\"fill: white; font-family: Arial, sans-serif; font-size: 25px; white-space: pre; text-anchor: middle;\" x=\"36\" y=\"30\" bx:origin=\"0.5 0.479796\">Red </text><text style=\"fill: blue; font-family: Arial, sans-serif; font-size: 15px; white-space: pre; text-anchor: middle;\" x=\"36\" y=\"50\" bx:origin=\"0.5 0.479796\">On </text></svg>"}}

?

event is the action you want to command to the button, in this case, "set image". ? See the StreamDeck developer document for all the available actions.

?

context is the button identification, not to be confused with the "id" you assigned the button in the config panel. ?This number is sent when you first push the button, so that future commands from Node-Red can use this id to oommand the button. ? ?Because your button graphics are not updating, I suspect you are not using the correct context number.

?

In this case, the payload is a SVG image to build a red background and some test of various size, position, and color.

?

?

Attache is my version of the SD Flow. ?It uses the same concepts that Warren showed you, but different coding.

?

The function, ""Process Stream Deck Input" will, for each unique button id (the name you gave the button) but into Node-Red flow context the context (button) and the device numbers. ?Below is the example for the button we pushed, above. ? The "device' number can be included in the command object, if you have multiple Stream Deck devices.

?

?

{"context":"b92505aa7b38be8abe13cb04ee0c242e",

"device":"3B4A178B0FA8D7408582138E1F192969",

"id":"toggle","

server":"ws://192.168.70.38:1880/streamdeck"}

?

?

Ok, Now we have everything in flow context to use the button id to search for the correspoiding context (button) and device numbers.

?

Lets look at this flow that build a gauge. ? In this gauge, we have multiple SVC components, that can be modified to your situation:

?

?

The "Build Streamdeck Button", has pre build SVG elements, background, gauge, text one, text two, switch icon, mic icon, speaker icon, and image.

?

?

At the bottom of this function, you build the button with the SVG elements you desire, in the case of the above gauge button, the line is:

?

?

?