Huawei EI 5720 dBm sensor Problem

Hello, so i added huawe ei 5720 switch to librenms, sensor for temperature, voltage and current are OK, but sensor for dBm is not correct. When I added switch I get 0.0 dBm values. So I made snmpwalk

there is examplevalues for TX from snmpwalk.

> iso.3.6.1.4.1.2011.5.25.31.1.1.3.1.9.67403854 = INTEGER: -1
> iso.3.6.1.4.1.2011.5.25.31.1.1.3.1.9.67436622 = INTEGER: -732
> iso.3.6.1.4.1.2011.5.25.31.1.1.3.1.9.67436686 = INTEGER: -620

Then I looked to /opt/librenms/includes/definitions/discovery/vrp.yaml
there was

 dbm:
            data:
                -
                    oid: hwOpticalModuleInfoTable
                    value: hwEntityOpticalRxPower
                    num_oid: .1.3.6.1.4.1.2011.5.25.31.1.1.3.1.8.
                    descr: '{{ $entPhysicalName }} Rx'
                    index: 'rx-{{ $index }}'
                    skip_values: -1
                    user_func: 'uw_to_dbm'
                -
                    oid: hwOpticalModuleInfoTable
                    value: hwEntityOpticalTxPower
                    num_oid: .1.3.6.1.4.1.2011.5.25.31.1.1.3.1.9.
                    descr: '{{ $entPhysicalName }} Tx'
                    index: 'tx-{{ $index }}'
                    skip_values: -1
                    user_func: 'uw_to_dbm'

when i deleted user_func: 'uw_to_dbm' and did ./poller.php -h hostaname -d then i can get values for dbm but in this format.

After this I tried to add divisor: 100 but whet i did this than ./discovery.php -h hostaname -d is not working.

Please help me what can I do with this ?

there is version of my switch

Huawei Versatile Routing Platform Software
VRP (R) software, Version 5.170 (S5720 V200R010C00SPC600)
Copyright (C) 2000-2016 HUAWEI TECH CO., LTD
HUAWEI S5720-32X-EI-24S-AC Routing Switch uptime is 1 week, 1 day, 7 hours, 50 minutes

Hello

This is actually a bug in the Switch code. You can upgrade to the last patch of your firmware and it should solve this issue. At least it did for me ( I’m running S5720EI-V200R010C00SPC600.010 now). Running standard LibreNms code (so you would have to revert any change you did to the YAML files).

It also solved an issue with VLANs not beeing properly seen by librenms (because the code in the handling of QBRIDGE MIB was wrong).

Bye