File /!1! Flows by Type/RELAYS/DEVANTECH.json uploaded
#file-notice
The following files and folders have been uploaded to
the Files area of the [email protected] group.
By: Garnet <gdrakiotes@...>
Description:
Devantech 8 relay Controller. US supplier https://acroname.com/ THANK-YOU to the previous work of Dave De Coons WO2X and the wonderful tutorials of Kyle - AA0Z! "On the shoulders of giants." Extensive comments in the flow. Probably not too many users of the ETH008 but perhaps some out there. 73, Garnet WA1VJH
|
I’m still at version 14.x? Not sure exact as I am traveling.?
Upgraded last night and tested Node Red locally and while traveling. Everything is operational that I have tried.?
Dave wo2x Sent from my waxed string and tin cans.?
toggle quoted message
Show quoted text
On Jul 15, 2022, at 3:07 PM, Alan Blind, WA9WUD <a.alan.blind@...> wrote:
?I updated my "test" RPI Node-Red to v3.
The BASH script told me I needed to update Node-JS from version 12. ?It gave me the extra commands to include the Node-JS and the option to select the version. ?I liked the latest, v18.
What version of Node-JS is another running when upgrading to Node-Red v3?
Alan. WA9WUD
|
I updated my "test" RPI Node-Red to v3.
The BASH script told me I needed to update Node-JS from version 12. ?It gave me the extra commands to include the Node-JS and the option to select the version. ?I liked the latest, v18.
What version of Node-JS is another running when upgrading to Node-Red v3?
Alan. WA9WUD
|
I loaded v3 yesterday evening. Preliminary testing showed everything working.?
I ran the bash script on the Pi from a telnet session after stopping Node Red.?
Dave wo2x Sent from my waxed string and tin cans.?
toggle quoted message
Show quoted text
On Jul 15, 2022, at 9:46 AM, Mick - W8BE <w8bea2b2c2@...> wrote:
?I loaded the beta release a couple of weeks ago. No issues with the beta release and I loaded the prod release yesterday. ?No issues their either. ?
--
Mick, W8BE
|
I loaded the beta release a couple of weeks ago. No issues with the beta release and I loaded the prod release yesterday. ?No issues their either. ?
--
Mick, W8BE
|
Working to run some tests today on v3 just to be safe. Thus far, it matters more which version of NodeJS you are using than which version of NodeRed.
I don’t see anything in the release notes that I think would break anything.
|
Hi Barry,
This week has been a bear for me. Topping if off with long road trip later this morning (Friday).
If you like, I can help you remotely one day next week. We can update the Node Red to new version 3. I upgraded mine earlier and if any issues I should know by time we do your upgrade. I am using Stephen’s version 1.2 Flex nodes.
We can update the flows to be Stream Deck ready and incorporate Alan’s tuner sweep flow. That way whenever you get the Stream Deck it will be easy to integrate.
E-mail me direct and we’ll coordinate.
73
Dave wo2x
toggle quoted message
Show quoted text
On Jul 14, 2022, at 11:29 PM, Barry Baines via groups.io <bbaines@...> wrote:
?
Dave:
On Jul 14, 2022, at 3:46 AM, David De Coons wo2x <RocketNJ@...> wrote:
I did a live demo at Xenia with my Stream Deck plugged into my laptop. Using a combination of FRStack on the laptop with StreamDeck REST commands and then websocket back to Node RedPi in shack in NJ I had full control.
I like the 32 button vs 15 as I don’t have to switch between screens for commonly used controls (AC power outlets, rotor control, relays, antenna switch, PG XL amp, Tuner Genius and radio.)
There is a zip file in files section of the site with my different flows, Stream Deck plug-ins, and my profile for Stream Deck. Also have a video on YouTube where we cover configuring the Stream Deck. Thank you for the update. I seem to recall having a conversation with you at Hamvention about Node Red and you mentioned using your laptop for demos, but don’t recall whether we discussed Stream Deck.
At this point I’m inclined to defer on getting the Stream Deck given that the 32 button version is probably the one to get and the current discount is not as significant as the 15 button version. There is a learning curve and I do need to learn more about what you’ve posted as well as the videos you’ve created before ordering the device.
Another question that comes to mind is what strategy to follow regarding updating/upgrading my current Node Red configuration. Late last year I downloaded/installed what you had created for PGXL, Tuner Genius, Antenna Genius, and DLI Power Switch. So now it is 7+ months later and apparently a number of new/updated flows are now available from Alan and you in particular which means I should probably update my Node Red configuration to take advantage of these new capabilities.
Consequently, am I better off to:
1. Wipe the slate clean and do a fresh download/install of desired flows; or
2. Do incremental changes presuming that each flow is independent of the other?
There is also the question of perhaps having multiple UI ‘pages’ of flows based upon the real estate of what will fit on a given display. Any thoughts on this?
73,
Barry, WD4ASW/1
73
Dave wo2x
|
Dave: On Jul 14, 2022, at 3:46 AM, David De Coons wo2x <RocketNJ@...> wrote:
I did a live demo at Xenia with my Stream Deck plugged into my laptop. Using a combination of FRStack on the laptop with StreamDeck REST commands and then websocket back to Node RedPi in shack in NJ I had full control.
I like the 32 button vs 15 as I don’t have to switch between screens for commonly used controls (AC power outlets, rotor control, relays, antenna switch, PG XL amp, Tuner Genius and radio.)
There is a zip file in files section of the site with my different flows, Stream Deck plug-ins, and my profile for Stream Deck. Also have a video on YouTube where we cover configuring the Stream Deck. Thank you for the update. I seem to recall having a conversation with you at Hamvention about Node Red and you mentioned using your laptop for demos, but don’t recall whether we discussed Stream Deck. At this point I’m inclined to defer on getting the Stream Deck given that the 32 button version is probably the one to get and the current discount is not as significant as the 15 button version. There is a learning curve and I do need to learn more about what you’ve posted as well as the videos you’ve created before ordering the device. Another question that comes to mind is what strategy to follow regarding updating/upgrading my current Node Red configuration. Late last year I downloaded/installed what you had created for PGXL, Tuner Genius, Antenna Genius, and DLI Power Switch. So now it is 7+ months later and apparently a number of new/updated flows are now available from Alan and you in particular which means I should probably update my Node Red configuration to take advantage of these new capabilities. Consequently, am I better off to: 1. Wipe the slate clean and do a fresh download/install of desired flows; or 2. Do incremental changes presuming that each flow is independent of the other? There is also the question of perhaps having multiple UI ‘pages’ of flows based upon the real estate of what will fit on a given display. Any thoughts on this? 73, Barry, WD4ASW/1
73
Dave wo2x
|
David,
Much thanks for taking the plunge for the team...? also great to hear no major problems so far.
--
Mike / K5MAP
|
I took the plunge and upgraded to Node Red 3.0 on my production Pi (after backing up). All went smooth by stopping Node Red, running the bash command, then starting Node Red. I also enabled the Monaco editor while Node Red was stopped (in the Node Red settings.js file). ? All seems to be running fine. I’ll let it burn in for a few hours (nap time for me). ? One new feature is the junction node. This is handy if you have several nodes connecting to a single node. You can create the junction for the various nodes to connect to then from there have only one connection to the other node. This is useful to minimize “wires” running across various areas of your flow. It just makes things “cleaner”. The other function that can be useful is Insert Link Nodes. If you have a connection going from the bottom of your flow to the top you can highlight the connection and right click then choose Insert/Link Nodes and it will change the connection to a pair of Link In/Link Out nodes, again cleaning up the wiring on the flow. ? 73 Dave wo2x ? ?
toggle quoted message
Show quoted text
From: [email protected] < [email protected]> On Behalf Of Mike Pate - K5MAP Sent: Thursday, July 14, 2022 6:01 PM To: [email protected]Subject: [nodered-hamradio] NR v3 released ? In case you haven't heard, Node-Red v3.0 has been released...?
Any volunteers willing to try NR v3 with Stephen's Flex nodes?? :)
--
Mike / K5MAP
|
I’ll back up and try an upgrade. Just about to shut the radio for the evening. Will let you know how it goes. If it “blows up” I’ll just rebuild the Pi. ? 73 Dave wo2x ? ?
toggle quoted message
Show quoted text
From: [email protected] < [email protected]> On Behalf Of Mike Pate - K5MAP Sent: Thursday, July 14, 2022 6:01 PM To: [email protected]Subject: [nodered-hamradio] NR v3 released ? In case you haven't heard, Node-Red v3.0 has been released...?
Any volunteers willing to try NR v3 with Stephen's Flex nodes?? :)
--
Mike / K5MAP
|
In case you haven't heard, Node-Red v3.0 has been released...?
Any volunteers willing to try NR v3 with Stephen's Flex nodes?? :)
--
Mike / K5MAP
|
Adrian, sorry it took so long to respond. Nope, the dog didn't eat the homework, my mommy is coming?into town for 3 weeks and I'm in the middle of a massive house cleaning!
Anyway, Buffer.from([85,85,85,1,13,13]: - Byte 1: Always 85
- Byte 2: Always 85
- Byte 3: Always 85
- Byte 4: Always 1 (length)
- Byte 5: The decimal value of the hexadecimal command in the SPE API table I sent you
- Byte 6: Repeat of byte 5
That help?
Ron, do you have the buffer codes for those please ?
73
Adrian
|
Re: Pi Problems with node red
You can set static IP but is very frowned upon. You are better off doing dhcp reservation in router for following reasons:
- you want to connect radio direct to computer. If radio is DHCP and router normally handles reservation, a direct connection will use a 169.254.X.X link local IP. Othwise you need to remember radio IP and set PC to static IP on same subnet.
- you get new router. Either from your ISP or you buy one. The subnet can be different leaving you with no communications to radio.
- most hams do not understand networking that well and wouldn’t understand subnetting or subnet masks.
- KISS. Keep It Simple Simon (was going to say stupid). You want things to work out of the box without the user having to have a degree in computer science.
I might be over dramatic but making a point why decisions are made. As far as my Flex Radio flow and having to change the Ping node IP, it is in the ReadMe node in the flow. Again my money is wagered on his radio’s IP changed with the new router replacement.
73
toggle quoted message
Show quoted text
On Jul 14, 2022, at 4:23 PM, Adrian Fewster <vk4tux@...> wrote:
?Dave, does the radio not have the manual ability to set static IP ? it relies on auto dhcp only ?
73
Adrian
|
Re: Pi Problems with node red
Yes, he can connect to api but my $$$ is on the radio IP address changed.
73 Dave wo2x Sent from my waxed string and tin cans.?
toggle quoted message
Show quoted text
On Jul 14, 2022, at 3:37 PM, Alan Blind, WA9WUD <a.alan.blind@...> wrote:
? agree.....but, I assumed since Scott was able to connect to the Pi via Putty, he knew and was using the updated IP address in Node-Red. ?
Scott, do as Dave says, first, just to make sure.
Alan On Thu, Jul 14, 2022 at 3:18 PM David De Coons wo2x < RocketNJ@...> wrote: No!
By changing your router your radio IP probably changed. Check IP of radio then in Flex Radio flow change ping node IP to match radio.?
Deploy and shut down and restart client. Or worst case reboot api after, then reboot radio, then connect.?
Dave wo2x Sent from my waxed string and tin cans.? ?Scott
Since you can Putty into the Pi, the first step is to verify Node-Red is running.? If you followed the script from the site to install Node-Red, it is installed as a "Service", and the below commands will work.
Run this command to check Node-Red Status: ? ? ?systemctl status nodered.service
You should see "active(running)" in the return.
If not try this command to start Node-Red, then run the status command: ??systemctl start nodered.service
If Node-Red is not running, run the install script from?Nodered.org
If Node -Red is?running, then its a LAN / IP number issue.
Alan.? WA9WUD
|
Re: Pi Problems with node red
agree.....but, I assumed since Scott was able to connect to the Pi via Putty, he knew and was using the updated IP address in Node-Red. ?
Scott, do as Dave says, first, just to make sure.
Alan
On Thu, Jul 14, 2022 at 3:18 PM David De Coons wo2x < RocketNJ@...> wrote: No!
By changing your router your radio IP probably changed. Check IP of radio then in Flex Radio flow change ping node IP to match radio.?
Deploy and shut down and restart client. Or worst case reboot api after, then reboot radio, then connect.?
Dave wo2x Sent from my waxed string and tin cans.? ?Scott
Since you can Putty into the Pi, the first step is to verify Node-Red is running.? If you followed the script from the site to install Node-Red, it is installed as a "Service", and the below commands will work.
Run this command to check Node-Red Status: ? ? ?systemctl status nodered.service
You should see "active(running)" in the return.
If not try this command to start Node-Red, then run the status command: ??systemctl start nodered.service
If Node-Red is not running, run the install script from?Nodered.org
If Node -Red is?running, then its a LAN / IP number issue.
Alan.? WA9WUD
|
Re: Pi Problems with node red
No!
By changing your router your radio IP probably changed. Check IP of radio then in Flex Radio flow change ping node IP to match radio.?
Deploy and shut down and restart client. Or worst case reboot api after, then reboot radio, then connect.?
Dave wo2x Sent from my waxed string and tin cans.?
toggle quoted message
Show quoted text
On Jul 14, 2022, at 3:05 PM, Alan Blind, WA9WUD <a.alan.blind@...> wrote:
?Scott
Since you can Putty into the Pi, the first step is to verify Node-Red is running. ?If you followed the script from the node-red.org site to install Node-Red, it is installed as a "Service", and the below commands will work.
Run this command to check Node-Red Status: ? ? ?systemctl status nodered.service
You should see "active(running)" in the return.
If not try this command to start Node-Red, then run the status command: ??systemctl start nodered.service
If Node-Red is not running, run the install script from?Nodered.org
If Node -Red is?running, then its a LAN / IP number issue.
Alan. ?WA9WUD
|
Re: Pi Problems with node red
Scott
Since you can Putty into the Pi, the first step is to verify Node-Red is running. ?If you followed the script from the node-red.org site to install Node-Red, it is installed as a "Service", and the below commands will work.
Run this command to check Node-Red Status: ? ? ?systemctl status nodered.service
You should see "active(running)" in the return.
If not try this command to start Node-Red, then run the status command: ??systemctl start nodered.service
If Node-Red is not running, run the install script from?Nodered.org
If Node -Red is?running, then its a LAN / IP number issue.
Alan. ?WA9WUD
|
Pi Problems with node red
Ok all so old router died, spectrum issued me a new one and now my nightmare has begun.? I try to start node red on pi and it just spams error of:
(error) (function:getDBM) TypeError: Cannot read property of 'smeters' of undefined
I did nothing but change router out.? I can putty into pi with no issue, zerotier sees pi no issues but I cannot connect to node-red or get it started.? Im sure something changed like a ip address or something but it is beyond me.
Anyone got any ideas?? I would like to not lose my flows or installs either.? :(
Scott
|
Re: Dashboard activates but doesn't reflect
Thanks so much Alan! Problem solved. Another lesson learned.
--
73,
Ed KA9EES
|
Dave wo2x
Stephen Houser, N1SH
Mike Pate - K5MAP
Edward Dowdy KA9EES