WAN Traffic Graph with Inverse In/Out

[DeFlanko]

The best way to describe it is to show you what pfSense is doing:

looking to find a way to replicate this in mini-graph where the WAN traffic In and Out or inversed to each other.

Is this possible now or is this a feature?

[DeFlanko]

Currently what i have:

type: custom:mini-graph-card
show:
  labels: true
  name_adaptive_color: true
  icon_adaptive_color: true
  average: true
  extrema: true
height: 150
hours_to_show: 0.25
points_per_hour: 360
line_width: 2
animate: true
value_factor: -2.108
lower_bound: ~0
color_thresholds:
  - value: 10000
    color: '#8FCE00'
  - value: 4000
    color: '#008fce'
  - value: 500
    color: '#ce008f'
entities:
  - entity: >-
      sensor.protectli_pfsense_1930networks_com_interface_wan_inbytes_kilobytes_per_second
    unit: Mbit/s
    name: Download
  - entity: >-
      sensor.protectli_pfsense_1930networks_com_interface_wan_outbytes_kilobytes_per_second
    unit: Mbit/s
    name: Upload
name: Active Internet (Last 15 Mins)

(The value factor took a bit of trial and error, that too should use a "if this then convert to that" feature... in this case i needed to convert kilobytes/s to MegaBits/s)

[ildar170975]

Not related to the main issue - but I personally do not suggest to show "extrema" & "average" values when more than 1 entity displayed with graphs since these "extrema" & "average" values are shown for the 1st entity only.
One of exclusions: card contains 2 or more entities, the 2nd & 3rd entities are with "show_state=true" & "show_graph=false"; then a user is less confused - for the "main" entity a graph, a state and "extrema" & "average" values are displayed, for other entities only states are displayed.

[DeFlanko]

I was using value_factor: -2.108 becasue the data on the pfsense is not in mBit/s -- this logic is no longer in the graph per the latest update i did. i made a calculated sensor to fix that.

Im reviewing your second update to see if works for me too .

[ildar170975]

this logic is no longer in the graph per the latest update i did

What update are you talking about?

[DeFlanko]

#861 (comment)

[DeFlanko]

Update.

type: custom:mini-graph-card
show:
  labels: true
  name_adaptive_color: true
  icon_adaptive_color: true
  average: true
  extrema: true
height: 150
hours_to_show: 0.25
points_per_hour: 360
line_width: 2
animate: true
lower_bound: ~0
color_thresholds:
  - value: 100
    color: '#8FCE00'
  - value: 40
    color: '#008fce'
  - value: 10
    color: '#ce008f'
  - value: 0
    color: '#000000'
  - value: -10
    color: '#008fce'
  - value: -40
    color: '#8FCE00'
entities:
  - entity: sensor.pfsense_download_mbps_speed
    unit: Mbit/s
    name: Download
  - entity: sensor.pfsense_upload_mbps_speed
    unit: Mbit/s
    name: Upload
name: Active Internet (Last 15 mins)

Where i had to add the following in configuration.yaml

      - name: "pfSense_Upload_Mbps_speed"
        state_class: measurement
        #Replace by MB/s if you want to use bytes/sec instead of bits/sec
        unit_of_measurement: Mb/s
        icon: mdi:upload
        state: >
          {% set WAN = states('sensor.protectli_pfsense_1930networks_com_interface_wan_outbytes_kilobytes_per_second') | float(0) %}
          {{ (0-(WAN)*8/1024) }}

      - name: "pfSense_Download_Mbps_speed"
        state_class: measurement
        #Replace by MB/s if you want to use bytes/sec instead of bits/sec
        unit_of_measurement: Mb/s
        icon: mdi:download
        state: >
          {% set WAN = states('sensor.protectli_pfsense_1930networks_com_interface_wan_inbytes_kilobytes_per_second') | float(0) %}
          {{ (WAN)*8/1024 }}

[ildar170975]

The main idea was to show 1st graph on the top, the 2nd graph on the bottom.
Currently it is only possible by card-mod.
What you achieved by using value_factor is not correct (and you know how this option is supposed to be used).
Go to Community card-mod thread -> 1st post -> link at the bottom -> mini-graph-card.

[DeFlanko]

this? https://community.home-assistant.io/t/lovelace-mini-graph-card/71385/1936

[ildar170975]

Yes