glad to hear it helped you.
keep in mind when comparing this to whatever you use to verify against that what ever you are comparing to is probably doing the same thing but at a different Δt so they might not be the same but booth values can be true. (because they are essentially average transfer rates over different times.)
Yeah for sure.
I was using the erx’s built in monitoring for comparison, it has a 2 sec updating bar graph that has about 80 seconds of history visible. Comparing this to my previous sensor ( averaged over a minute) the old sensor was obviously reading up to10x too high. Your version of the sensor is spot on compared to the erx’s monitor.
Thanks, the derivative method has been giving me more accurate readings. Except every once in a while, it was resulting up with a really large negative numbers (which screws up the graph view). Not sure what’s causing it (possibly my router misreporting…), but added a max function to ignore those results.
- platform: snmp
name: wan_in
baseoid: 1.3.6.1.2.1.2.2.1.10.4
host: !secret zeus_hostname
version: !secret zeus_snmp_version
accept_errors: true
scan_interval: 10
- platform: snmp
name: wan_out
baseoid: 1.3.6.1.2.1.2.2.1.16.4
host: !secret zeus_hostname
version: !secret zeus_snmp_version
accept_errors: true
scan_interval: 10
- platform: derivative
name: wan_in_der
source: sensor.wan_in
unit_time: s
unit: B
- platform: derivative
name: wan_out_der
source: sensor.wan_out
unit_time: s
unit: B
- platform: template
sensors:
wan_in_mbps:
value_template: "{{ [((states('sensor.wan_in_der')|float*8)/1000000)|round(2),0]|max }}"
unit_of_measurement: 'Mbps'
entity_id: sensor.wan_in_der
friendly_name: "WAN In"
wan_out_mbps:
value_template: "{{ [((states('sensor.wan_out_der')|float*8)/1000000)|round(2),0]|max }}"
unit_of_measurement: 'Mbps'
entity_id: sensor.wan_out_der
friendly_name: "WAN Out"
2 Likes
I’m wondering if with this data I can create a new template sensor or something like that to view the total traffic by day and month, would be possible?
Sure just use the wan in and wan out sensors (not the derivative sensors) in the utility meter.
1 Like
Thanks! I tried to to use the utility meter but when I put the sensor on a History Graph Card Configuration I’m getting strange results:
sensor:
- platform: snmp
name: 'ERX WAN In'
host: 192.168.1.1
baseoid: 1.3.6.1.2.1.31.1.1.1.6.4
community: 'public'
version: '2c'
scan_interval: 10
- platform: snmp
name: 'ERX WAN Out'
host: 192.168.1.1
baseoid: 1.3.6.1.2.1.31.1.1.1.10.4
community: 'public'
version: '2c'
scan_interval: 10
- platform: derivative
source: sensor.erx_wan_in
unit_time: s
unit: B
name: erx_wan_in_derivative
- platform: derivative
source: sensor.erx_wan_out
unit_time: s
unit: B
name: erx_wan_out_derivative
- platform: template
sensors:
erx_wan_in_mbps:
value_template: "{{ ((states('sensor.erx_wan_in_derivative')|float*8)/1000000)|round(2) }}"
unit_of_measurement: 'Mbps'
entity_id: sensor.erx_wan_in_derivative
friendly_name: Internet in Dev
erx_wan_out_mbps:
value_template: "{{ ((states('sensor.erx_wan_in_derivative')|float*8)/1000000)|round(2) }}"
unit_of_measurement: 'Mbps'
entity_id: sensor.erx_wan_out_derivative
friendly_name: Internet out Dev
utility_meter:
wan_in_monthly:
source: sensor.erx_wan_in
cycle: monthly
wan_in_daily:
source: sensor.erx_wan_in
cycle: daily
wan_out_monthly:
source: sensor.erx_wan_out
cycle: monthly
wan_out_daily:
source: sensor.erx_wan_out
cycle: daily
What I did wrong?
I cant see your image. The host is blocked here. Just drag your image file into the post on the forum.
EDIT: ok that is because the sensors do not have a unit. You will probably want to change that from bytes to MB anyway. Also you have a few errors in your templates (using the in sensor for the out template).
If you are on version 0.117.x this should work:
sensor:
- platform: snmp
name: 'ERX WAN In'
host: 192.168.1.1
baseoid: 1.3.6.1.2.1.31.1.1.1.6.4
community: 'public'
version: '2c'
scan_interval: 10
- platform: snmp
name: 'ERX WAN Out'
host: 192.168.1.1
baseoid: 1.3.6.1.2.1.31.1.1.1.10.4
community: 'public'
version: '2c'
scan_interval: 10
- platform: derivative
source: sensor.erx_wan_in
unit_time: s
unit: B
name: erx_wan_in_derivative
- platform: derivative
source: sensor.erx_wan_out
unit_time: s
unit: B
name: erx_wan_out_derivative
- platform: template
sensors:
erx_wan_in_mbps:
value_template: "{{ (states('sensor.erx_wan_in_derivative')|float*8/1000000)|round(2) }}"
unit_of_measurement: 'Mbps'
friendly_name: Internet in Dev
erx_wan_out_mbps:
value_template: "{{ (states('sensor.erx_wan_out_derivative')|float*8/1000000)|round(2) }}"
unit_of_measurement: 'Mbps'
friendly_name: Internet out Dev
erx_wan_download_mib:
value_template: "{{ (states('sensor.erx_wan_in')|float/1000000)|round(2) }}"
unit_of_measurement: 'MiB'
friendly_name: Internet in Dev
erx_wan_upload_mib:
value_template: "{{ (states('sensor.erx_wan_out')|float/1000000)|round(2) }}"
unit_of_measurement: 'MiB'
friendly_name: Internet out Dev
utility_meter:
wan_in_monthly:
source: sensor.erx_wan_download_mib
cycle: monthly
wan_in_daily:
source: sensor.erx_wan_download_mib
cycle: daily
wan_out_monthly:
source: sensor.erx_wan_upload_mib
cycle: monthly
wan_out_daily:
source: sensor.erx_wan_upload_mib
cycle: daily
1 Like
Thanks! Now the graph is looking right!
Now I’m going to wait an see how to improve the visualization of this data.
1 Like
I think there is something wrong with your template. There’s no way you are using 6 petabytes (10 to the power of 15) in 20 minutes.
GiB would probably be a better unit for general WAN use anyway (I used MiB as I took the template from my 4G cellular connection). Try this:
erx_wan_download_gib:
value_template: "{{ (states('sensor.erx_wan_in')|float/1000000000)|round(2) }}"
unit_of_measurement: 'GiB'
friendly_name: Internet in Dev
erx_wan_upload_gib:
value_template: "{{ (states('sensor.erx_wan_out')|float/1000000000)|round(2) }}"
unit_of_measurement: 'GiB'
friendly_name: Internet out Dev
utility_meter:
wan_in_monthly:
source: sensor.erx_wan_download_gib
cycle: monthly
wan_in_daily:
source: sensor.erx_wan_download_gib
cycle: daily
wan_out_monthly:
source: sensor.erx_wan_upload_gib
cycle: monthly
wan_out_daily:
source: sensor.erx_wan_upload_gib
cycle: daily
1 Like
Much better. If you still want to get rid of those extra zeros the template in my post above will measure in GiB.
1 Like
One minor correction. I got my units back to front. It should be MB or GB, not MiB or GiB.
MiB is a power of 2, MB is a power of 10.
2 Likes
Hi @japie101 I have the same switch and would like to see the trafic on the ports. Where did you find the baseoid addresses for the ports?
I used an SNMP discovery tool back then, but not sure which program that was anymore.
For your reference:
I am using port 1 of my US-8-60W.
- platform: snmp
name: 'Internet incoming'
host: x.x.x.x
baseoid: 1.3.6.1.2.1.31.1.1.1.6.1
community: 'public'
version: '2c'
scan_interval: 5
- platform: snmp
name: 'Internet outgoing'
host: x.x.x.x
baseoid: 1.3.6.1.2.1.31.1.1.1.10.1
community: 'public'
version: '2c'
scan_interval: 5
1 Like
I found one called snmpB the most useful.
This is awesome! Thanks for sharing it, I’ve just implement SNMP on my setup and this gives very accurate results. 
hi,
shall you share the lovelace code of this graph?
Tnx
if someone have the same problem with pppoe interface on a Ubiquiti USG, that change the OID randomly every time it restart, I created an appdaemon app to retrieve the data via SNMP and put on 2 HA entities
You can find at: https://github.com/twproject/homeassistant/tree/main/appdaemon/snmp%20query/hassio_unifi_internet_interface