I recently upgraded to Node-RED 2.03 and? dotnet 5.0.5.? ?I noticed I am getting error msgs like below:
Jul 29 16:55:44 raspberrypi dotnet: Radio Meter AM Signal strength after AM - NO Data Ready handler
Jul 29 16:55:44 raspberrypi dotnet: Waterfall::StatusUpdate: Key not parsed (band_zoom=0)
Jul 29 16:55:44 raspberrypi dotnet: Waterfall::StatusUpdate: Key not parsed (segment_zoom=0)
Jul 29 16:55:44 raspberrypi dotnet: Waterfall::StatusUpdate: Key not parsed (daxiq_channel=0)
Jul 29 16:55:44 raspberrypi dotnet: Slice::StatusUpdate: Key not parsed (sample_rate=24000)
Jul 29 16:55:44 raspberrypi dotnet: RXRemoteAudioStream::StatusUpdate: Invalid key/value pair ()
Jul 29 16:55:44 raspberrypi dotnet: RXRemoteAudioStream::StatusUpdate: Key not parsed (ip=10.0.0.55)
Jul 29 16:55:44 raspberrypi dotnet: ParseInterlockStatus: Error - Invalid reason (OUT_OF_PA_RANGE)
Jul 29 16:56:10 raspberrypi dotnet: ParseInterlockStatus: Error - Invalid reason (OUT_OF_PA_RANGE)
I loaded up a new pi with dotnet 5.0.3 and the latest Node-Red / FRStack and still see the errors.? I then loaded Mark's json to test and? see if something in my flow could be the issue but I see the same errors using the Mark's json.? ? ?I am curious if anyone has notice this.? ?I have not lost any functionality, I just don't like to see errors eating up cpu ticks to post a message to /var/log.? ?
Regards,
Mick
?
