Dave,
I upgraded to dotnet 5.0.8 this morning.? ?Same results.? ?So I did a quick test.? ?I don't think the issue has anything to do with Node-RED.? ?I stopped the Node-Red process and then restarted the FRStackWebApi.? ?Now with no Node-Red running and my radio on here is what I see in the log:
pi@raspberrypi:/usr/local/frstack $ sudo systemctl restart FRStackWebApi
pi@raspberrypi:/usr/local/frstack $ journalctl --unit FRStackWebApi --follow
-- Logs begin at Thu 2021-07-29 16:24:31 EDT. --
Jul 30 06:29:34 raspberrypi dotnet[19756]: Radio Meter LEVEL Signal strength of signals in the filter passband - NO Data Ready handler
Jul 30 06:29:34 raspberrypi dotnet[19756]: Radio Meter AGC+ Signal strength after AGC - NO Data Ready handler
Jul 30 06:29:34 raspberrypi dotnet[19756]: Radio Meter AM Signal strength after AM - NO Data Ready handler
Jul 30 06:29:34 raspberrypi dotnet[19756]: Waterfall::StatusUpdate: Key not parsed (band_zoom=0)
Jul 30 06:29:34 raspberrypi dotnet[19756]: Waterfall::StatusUpdate: Key not parsed (segment_zoom=0)
Jul 30 06:29:34 raspberrypi dotnet[19756]: Waterfall::StatusUpdate: Key not parsed (daxiq_channel=0)
Jul 30 06:29:34 raspberrypi dotnet[19756]: Slice::StatusUpdate: Key not parsed (sample_rate=24000)
Jul 30 06:29:34 raspberrypi dotnet[19756]: RXRemoteAudioStream::StatusUpdate: Invalid key/value pair ()
Jul 30 06:29:34 raspberrypi dotnet[19756]: RXRemoteAudioStream::StatusUpdate: Key not parsed (ip=10.0.0.55)
Jul 30 06:29:34 raspberrypi dotnet[19756]: ParseInterlockStatus: Error - Invalid reason (OUT_OF_PA_RANGE)
I wanted to post this test as Mark will eventually see it and advise.? Upgrading to dotnet 5.0.8 was a worthwhile endeavor.? It gave me the idea to test the FRStackWebApi with no conflicting processes.??
Regards