Fix Noise Floor "0" bug #60

Closed
opened 2026-10-27 09:30:48 +01:00 by adam · 0 comments
Owner

Hey Guys,

I'm hoping this is a simple one. Every now and again the noise floor in the UI shows "0" which can be a bit misleading to users.

As I understand it, it's because the noise floor readings are paused during transmit, and I guess the UI is polling it and there's no reading for the API to serve up, so it serves up a zero? (I haven't dug into it too much).

Can we fix this so that if there's no new value to display it retains the last known value?

Thanks,
Josh

Hey Guys, I'm hoping this is a simple one. Every now and again the noise floor in the UI shows "0" which can be a bit misleading to users. As I understand it, it's because the noise floor readings are paused during transmit, and I guess the UI is polling it and there's no reading for the API to serve up, so it serves up a zero? (I haven't dug into it too much). Can we fix this so that if there's no new value to display it retains the last known value? Thanks, Josh <!-- github-sync-id:4075437230 -->
adam closed this issue 2026-10-27 09:30:48 +01:00
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/pyMC_Repeater#60