[Bug]: Radio names not working

[Vulp35]

Contact Details

No response

What happened?

No radio data showing on main dashboard. No computer names showing under "Radio Names" in configuration. Manual computer name entry will let me set a computer name to a radio, but still does not show any radio information on dashboards.

Version

1.2.20

Environment

- **OS** : Armbian Bullseye (Inovato Quadra)
- **Node.js** : 16.19.1

What browsers are you seeing the problem on?

Firefox, Chrome

Relevant log output

3/26/2023, 2:50:27 PMnode: Add Placeholders and Options
function : (warn)
"{"StationName":"RUSS-LENOVO"}"
3/26/2023, 2:50:27 PMnode: Add Placeholders and Options
function : (warn)
"RUSS-LENOVO"
3/26/2023, 2:50:28 PMnode: Add Placeholders and Options
function : (warn)
[ "RUSS-LENOVO" ]

Code of Conduct

• I agree to follow this project's Code of Conduct

[kd9lsv]

Just want to make sure, that you've also configured N1MM to point to the Node Red install.

https://github.com/kylekrieg/Node-Red-Contesting-Dashboard/blob/master/INSTALL.md

If that is completed does the issue part of #59 include this?

[Vulp35]

I do! The contacts and everything else seem to be working. I'm not sure if the issue referenced includes this or not.

Going into the Dashboard Flow and looking at Radio Data Raw debug node I get this output:

{
  "RadioInfo": {
    "app": ["N1MM"],
    "StationName": ["RUSS-LENOVO"],
    "RadioNr": ["1"],
    "Freq": ["1424500"],
    "TXFreq": ["1424500"],
    "Mode": ["USB"],
    "OpCall": ["KF0JOU"],
    ...
  }
}

This is what my dashboard shows, and how configuration looks for the radios. (Note: the computer name was added manually.)

[kd9lsv]

I believe so. It has been a while since I've actually had a time and effort to put into this.

@KK1L is this the same thing that was wrong Ron?

[KK1L]

Yes. The computer name does not come from the "Radio Names". It is the Station Name from N1MM+, but they are hardcoded to Radio1, 2, 3, etc as the Group Name in the dashboards. I have a version which uses the name assigned in the Config page, but there is something in the flow which causes excessive CPU usage. I have not had the oportunity to spend time on the flow in well over a month now.

[KK1L]

Thiis what I coded vs stock turning off the group name for each of the radios in the dashboard (Radio1 Data, Radio2 Data) and using a varible label for the Operator label. I did have to pass Radio1Name into the payload. Somewhat straightforward but maybe cludgy.
Label for "Operator" of Radio1 = <font size="+2" color=#008000><b>{{msg.Radio1Name}}</b></font>

[kd9lsv]

Going to close due to matching with #59