You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: