RNodeMultiInterface RSSI and SNR reporting incorrectly

[jacobeva]

There is a bug in RNodeMultiInterface which is causing it to mix up the RSSI and SNR values when two announces are received close to each other.

Here's what this looks like:

[2024-10-22 15:49:28] [Extra] Valid announce for <redacted> 1 hops away, received via <redacted> on openCom XL[HIGHDATARATE] [RSSI 20dBm, SNR 0.25dB]
[2024-10-22 15:49:28] [Debug] Destination <redacted> is now 1 hops away via <redacted> on openCom XL[HIGHDATARATE]
[2024-10-22 15:49:28] [Extra] Valid announce for <redacted> 1 hops away, received via <redacted> on openCom XL[LOWDATARATE]
[2024-10-22 15:49:31] [Extra] Valid announce for <redacted> 1 hops away, received via <redacted> on openCom XL[HIGHDATARATE] [RSSI 10dBm, SNR 0.0dB]
[2024-10-22 15:49:31] [Debug] Destination <redacted> is now 1 hops away via <redacted> on openCom XL[HIGHDATARATE]
[2024-10-22 15:49:31] [Extra] Valid announce for <redacted> 1 hops away, received via <redacted> on openCom XL[LOWDATARATE] [RSSI 20dBm, SNR 0.25dB]

The high data rate interface is hardcoded to have an RSSI of 20dBm in the firmware, with a raw SNR of 1. The low data rate interface is hardcoded to have an RSSI of 10dBm, with a raw SNR of 0. As you can see, the first packet has the correct SNR and RSSI (but the low data rate SNR and RSSI is not shown for some reason), and thereafter they are mixed up. Once they are mixed up, they are never printed correctly again.

I have checked the hex values which are being returned by the RNode, and the RSSI and SNR values are in the correct order, so that only leaves an error in the RNS python interface. I will look into this soon and provide a PR to fix.