SNMP Voltage monitor bug on 4.11 and 4.13 - RB433AH

Hi,
I have a problem accessing voltage monitor on RB433AH board.
I read the voltage value trought SNMP, using OID .1.3.6.1.4.1.14988.1.1.3.8.0

Well, using RouterOS 4.13, the voltage reading is fixed to 28 V.
I then downgraded to 4.11 version. Now I can read the correct value (11.8 V) but there is another bug:
After a reboot, the SNMP answer is always wrong UNTIL a send a request for OID .1.3.6.1.4.1.14988.1.1.3.9.0 (please note 9 digit instead of :sunglasses:.
After that, I can query Reading OID .1.3.6.1.4.1.14988.1.1.3.8.0 succesfully.

Please look at the following test:
2 readings using OID .1.3.6.1.4.1.14988.1.1.3.8.0 (failed)
1 reading using OID .1.3.6.1.4.1.14988.1.1.3.9.0
1 reading using OID .1.3.6.1.4.1.14988.1.1.3.8.0 (success!!!)

----------------------- New Test -----------------------
Paessler SNMP Tester 3.2
Device: 10.20.0.205
Reading OID .1.3.6.1.4.1.14988.1.1.3.8.0

05/12/2010 19.11.05 (1 ms) : Start using SNMP V2c
05/12/2010 19.11.05 (175 ms) : -------
05/12/2010 19.11.05 (175 ms) : Value: No Such Name (SNMP error # 2)
05/12/2010 19.11.05 (175 ms) : Done


----------------------- New Test -----------------------
Paessler SNMP Tester 3.2
Device: 10.20.0.205
Reading OID .1.3.6.1.4.1.14988.1.1.3.8.0

05/12/2010 19.11.08 (1 ms) : Start using SNMP V2c
05/12/2010 19.11.08 (166 ms) : -------
05/12/2010 19.11.08 (167 ms) : Value: No Such Name (SNMP error # 2)
05/12/2010 19.11.08 (167 ms) : Done


----------------------- New Test -----------------------
Paessler SNMP Tester 3.2
Device: 10.20.0.205
Reading OID .1.3.6.1.4.1.14988.1.1.3.9.0
05/12/2010 19.11.16 (2 ms) : Start using SNMP V2c
05/12/2010 19.11.16 (54 ms) : -------
05/12/2010 19.11.16 (55 ms) : Value: none
05/12/2010 19.11.16 (55 ms) : Done


----------------------- New Test -----------------------
Paessler SNMP Tester 3.2
Device: 10.20.0.205
Reading OID .1.3.6.1.4.1.14988.1.1.3.8.0

05/12/2010 19.11.21 (2 ms) : Start using SNMP V2c
05/12/2010 19.11.22 (820 ms) : -------
05/12/2010 19.11.22 (821 ms) : Value: 118
05/12/2010 19.11.22 (822 ms) : Done

nobody can confirm the issue?

I confirm this bug still present on release 4.15 :frowning: