It is important health value of repeater.
Also i think it would be better to swap % in txrx airtime and average rxtx/min between for more solid design (alignment of bold text info)
It is important health value of repeater.
Also i think it would be better to swap % in txrx airtime and average rxtx/min between for more solid design (alignment of bold text info)
<img width="621" height="808" alt="Image" src="https://github.com/user-attachments/assets/2ea6870f-3dda-4bf3-b3c0-60bfd7f742a8" />
<!-- github-sync-id:4310053643 -->
Yeah good idea! I'm not going to change the styling now but repeater errors are definitely necessary. In this case, we're limited by our upstream interface library. I've opened a PR to add this functionality to the repeater transport: https://github.com/meshcore-dev/meshcore_py/pull/82
Work stashed in repeater-error-count.
Yeah good idea! I'm not going to change the styling now but repeater errors are definitely necessary. In this case, we're limited by our upstream interface library. I've opened a PR to add this functionality to the repeater transport: https://github.com/meshcore-dev/meshcore_py/pull/82
Work stashed in repeater-error-count.
<!-- github-comment-id:4300860399 -->
Instead of the count, which will just go up with the uptime, can we plot the error% so we can see the trend over time?
Instead of the count, which will just go up with the uptime, can we plot the error% so we can see the trend over time?
<img width="1155" height="452" alt="Image" src="https://github.com/user-attachments/assets/934fd912-8641-414d-9abf-093f90ccc562" />
<!-- github-comment-id:4329329650 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
It is important health value of repeater.
Also i think it would be better to swap % in txrx airtime and average rxtx/min between for more solid design (alignment of bold text info)
i don't like idea with swapping, but Error count is must-have
Yeah good idea! I'm not going to change the styling now but repeater errors are definitely necessary. In this case, we're limited by our upstream interface library. I've opened a PR to add this functionality to the repeater transport: https://github.com/meshcore-dev/meshcore_py/pull/82
Work stashed in repeater-error-count.
Okay error counts are added, and I'm adding percentage of rx packets that were errored now.
okay and with percentage
Instead of the count, which will just go up with the uptime, can we plot the error% so we can see the trend over time?
done.