zboss/nwk/nwk_main.c:2166 (ZBOSS v3.11.3.0) should be the first step in the data path which deals with RSSI values. Even there, the RSSI values are odd. Until that point, the packet data seems to be taken unchanged from the lower layers.
After some research, I found this commit in Zephyr: github.com/.../b224a099fd3d56d068f22e825a9c4cd835590878
It changes the interpretation of the lower layer RSSI value to being in the range of -174 dBm (value 0) to 80 dBm (value 254). Reverting that commit fixes the issue.
The RSSI/power variables are uint8_t in Zephyr but are interpreted as int8_t in ZBOSS which results in the changing sign of the value.
I suggest adapting the ZBOSS methods to correctly converting the RSSI value before storing it in the metadata.
Hi Patrick,
Thank you for sharing your findings.
I have created a ticket internally for this. I will keep you posted on any updates.
Best regards,
Maria
Hello,
The fix for this issue can be found here: https://github.com/nrfconnect/sdk-nrf/pull/15502.
Best regards,
Maria
Hello,
The fix for this issue can be found here: https://github.com/nrfconnect/sdk-nrf/pull/15502.
Best regards,
Maria