Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature: Option in settings to set network throughput unit #108

Open
MaxVRAM opened this issue Sep 9, 2021 · 1 comment
Open

Feature: Option in settings to set network throughput unit #108

MaxVRAM opened this issue Sep 9, 2021 · 1 comment

Comments

@MaxVRAM
Copy link
Contributor

MaxVRAM commented Sep 9, 2021

kbps (kilobits) feels a little outdated as a human-readable unit of measuring network throughput. I understand bits have always been a standard in networking, but I personally find MB/s (megabytes per second) far easier to process in my head when I'm quickly scanning a page full of numbers. Bytes are also the standard format of most browser download speed monitors.

Having the option to choose your own unit of measure makes sense to me.

I considered if having a shifting unit (KB/MB) depending on throughput value would work - but I realised it wouldn't gel well with Home Assistant's data logging and Lovelace card graphing displays. In HA it's possible to make a template or Node Red flow to grab the values and process it, but that would mean another HA device would need to exist with the modified values. If anyone else can think of a solution to that particular issue, feel free to chime in.

Otherwise, I'm happy to implement this feature when I've got time in the next couple of days. Just popping the feature idea here so I remember or if anyone else wants to have a crack before I get around to it.

@Sennevds
Copy link
Owner

Maybe add a attribute with a display value. With the real value send and be logged to the database and the display value being used in the frontend.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants