SNMP sensor not processing float values (correctly) #2767

fanaticDavid · 2016-08-09T08:46:10Z

Make sure you are running the latest version of Home Assistant before reporting an issue.

You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:

Home Assistant release (hass --version):
0.25.2 (installed using AiO installer)

Python release (python3 --version):
3.4.2

Component/platform:
SNMP sensor, used on a Raspberry Pi 3 (with Raspbian Jessie Lite)

Description of problem:
I use SNMP sensors to track the status and some statistics of the APC UPS connected to my Synology NAS. The result of that looks like this:

The bottom 2 sensors work just fine. The top 4 sensors, however, return unusual results.

Expected:
Expecting float values, but getting unusual string values instead

Problem-relevant configuration.yaml entries and steps to reproduce:
The sensors in my HASS config are defined as follows:

- platform: snmp
  name: "UPS Battery Charge"
  host: xxx.xxx.xxx.x
  community: home
  baseoid: 1.3.6.1.4.1.6574.4.3.1.1.0

- platform: snmp
  name: "UPS Battery Voltage"
  host: xxx.xxx.xxx.x
  community: home
  baseoid: 1.3.6.1.4.1.6574.4.3.2.1.0

- platform: snmp
  name: "UPS Input Voltage"
  host: xxx.xxx.xxx.x
  community: home
  baseoid: 1.3.6.1.4.1.6574.4.4.1.1.0

- platform: snmp
  name: "UPS Load"
  host: xxx.xxx.xxx.x
  community: home
  baseoid: 1.3.6.1.4.1.6574.4.2.12.1.0

- platform: snmp
  name: "UPS Runtime"
  host: xxx.xxx.xxx.x
  community: home
  baseoid: 1.3.6.1.4.1.6574.4.3.6.1.0

- platform: snmp
  name: "UPS Status"
  host: xxx.xxx.xxx.x
  community: home
  baseoid: 1.3.6.1.4.1.6574.4.2.1.0

- platform: template
  sensors:
    ups_runtime_templated:
      value_template: >
        {% if states.sensor.ups_runtime %}
          {% set minutes = states.sensor.ups_runtime.state | multiply(0.016666666666667) | round(0) %}
          {% if minutes == 1 %}
            1 minute
          {% else %}
            {{ minutes }} minutes
          {% endif %}
        {% else %}
          unknown
        {% endif %}
    ups_status_templated:
      value_template: >
        {% if states.sensor.ups_status %}
          {% if states.sensor.ups_status.state == 'OL' %}
            On power
          {% elif states.sensor.ups_status.state == 'OB' %}
            On battery
          {% endif %}
        {% else %}
          unknown
        {% endif %}

Using snmpwalk on my MacBook, I was able to determine that this issue occurs when a float value is returned.

Testing the top 4 broken sensors:
snmpwalk -Os -c home -v 2c xxx.xxx.xxx.x 1.3.6.1.4.1.6574.4.3.1.1.0 enterprises.6574.4.3.1.1.0 = Opaque: Float: 100.000000
snmpwalk -Os -c home -v 2c xxx.xxx.xxx.x 1.3.6.1.4.1.6574.4.3.2.1.0 enterprises.6574.4.3.2.1.0 = Opaque: Float: 27.200001
snmpwalk -Os -c home -v 2c xxx.xxx.xxx.x 1.3.6.1.4.1.6574.4.4.1.1.0 enterprises.6574.4.4.1.1.0 = Opaque: Float: 231.00000
snmpwalk -Os -c home -v 2c xxx.xxx.xxx.x 1.3.6.1.4.1.6574.4.2.12.1.0 enterprises.6574.4.2.12.1.0 = Opaque: Float: 3.000000

Testing the bottom 2 working sensors:
snmpwalk -Os -c home -v 2c xxx.xxx.xxx.x 1.3.6.1.4.1.6574.4.3.6.1.0 enterprises.6574.4.3.6.1.0 = INTEGER: 9375
snmpwalk -Os -c home -v 2c xxx.xxx.xxx.x 1.3.6.1.4.1.6574.4.2.1.0 enterprises.6574.4.2.1.0 = STRING: "OL"

Traceback (if applicable):
none

Additional info:
Using templates to change the values to floats doesn't work, not that I was expecting it to

The text was updated successfully, but these errors were encountered:

fabaff · 2016-08-11T11:56:30Z

I've tested the SNMP sensor and it works with the following types:

String
Integer
Gauge32
Counter32
Timeticks
OID

This seems to confirm your observation. Unfortunately I can't get my hands on an OID that returns a float at the moment.

fabaff · 2016-08-11T12:01:45Z

Can you please test #2788 for your setup? Thanks.

fanaticDavid · 2016-08-11T20:34:03Z

@fabaff I hate to sound stupid but...how would I go about that? I'm currently running the release version of HASS installed with the AiO installer. If you could give me a nudge in the right direction, I'd be more than happy to test it for you. I am by no means a developer, though.

I did try it a "dirty" way by simply renaming the original snmp.py file and creating a new snmp.py file with the new code. Unfortunately, even after restarting HASS, the result is the same as before. On the contrary, I have another SNMP sensor for a different OID which now returns "100.0" instead of "100": it turned a Gauge32 value into a Float value.

Spartan-II-117 · 2017-03-14T20:08:15Z

has any progress been made on this?

fanaticDavid · 2017-05-03T05:35:33Z

Nope. I'm running Home Assistant 0.43.2 and this issue still exists.

balloobbot · 2017-07-17T16:25:53Z

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍

fanaticDavid · 2017-07-17T17:25:15Z

This is still an issue...

balloobbot · 2017-10-20T17:29:06Z

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍

fanaticDavid · 2017-10-20T20:54:41Z

Still relevant with 0.55.x:

ChristianKuehnel · 2017-12-19T23:09:51Z

Hey @fanaticDavid,

I had a look at the issue I added support for decoding of "Opaque" types, as long as they are supported by the unerlying pyasn1 library (https://github.com/etingof/pyasn1). I'm not sure if that solves your problem, as pyasn1 does not list the type "Float". It does offer type "Real".

You can give it a try:
#11239

If that does not solve the problem, you probably need to request the Float data type in the pyasn1 project.

keithmichael · 2018-02-05T20:40:34Z

Hoping this get fixed soon, I can't monitor UPS battery input voltage because type is opaque

fanaticDavid · 2018-02-05T21:11:08Z

The code from #11239 already works, it just needs to be finalized and merged 🙂

keithmichael · 2018-02-05T21:23:29Z

awesome!!! thank you!

…

On Mon, Feb 5, 2018 at 4:11 PM, David ***@***.***> wrote: The code from #11239 <#11239> already works, it just needs to be finalized and merged 🙂 — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#2767 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AUPcdf5PU8acjwRbFCes7u8h0dp2IDdFks5tR26AgaJpZM4Jf2N9> .

balloobbot · 2018-05-29T14:03:17Z

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍

fanaticDavid · 2018-05-31T00:17:15Z

This is still a bug as #11239 by @ChristianKuehnel was never finished.

Personally, I switched from using SNMP to using NUT to monitor my NAS' UPS. However, since I'm not the only user who is/was affected by this bug, I would like this issue to remain open until it has been fixed.

keithmichael · 2018-05-31T00:24:12Z

I would like to see this bug fixed too. Because volts is Opaque, I monitor battery up time instead. I feel the voltage is a better way to monitor plus if this is fixed we may be able to monitor other things/devices and not have to worry about this problem.

…

On Wed, May 30, 2018 at 8:17 PM, David ***@***.***> wrote: This is still a bug as #11239 <#11239> by @ChristianKuehnel <https://github.com/ChristianKuehnel> was never finished. Personally, I switched from using SNMP to using NUT to monitor my NAS' UPS. However, since I'm not the only user who is/was affected by this bug, I would like this issue to remain open until it has been fixed. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#2767 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AUPcda8_2EpFP5bJM17h2bBN3BUzOz7Fks5t3zangaJpZM4Jf2N9> .

balloobbot · 2018-10-26T10:28:36Z

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍

fanaticDavid · 2018-11-03T14:34:49Z

Can anyone confirm this issue still exists? I suspect it does since #11239 was closed without being merged.

For my use case, I've switched from the SNMP component to the NUT component so I cannot test this at the moment.

bagobones · 2018-11-13T08:04:46Z

I don't recall which version it started working in but I have been able to pull SNMP network info from my Gigabit router now for some time where it did not work previously. I Think it is fixed, or at least I can get accurate network traffic from a EdgeRouter Now.

cgarwood · 2018-12-14T18:11:01Z

Closing based on @bagobones report and the age of the issue. Please open a new issue if this problem still persists.

cartwrightian · 2021-10-22T15:09:18Z

sorry to comment on such an old issue, let me know if should open new issue.

Opaque float ends up as a hex number, tried adding value template to cast value to a float but yields 0.0

The config:

platform: snmp
name: Real Power Nominal
host: 192.168.0.4
baseoid: 1.3.6.1.4.1.6574.4.2.21.2.0
unit_of_measurement: "W"

In dev panel:
Entity: sensor.real_power_nominal = 0x9f780444584000

Actual value via snmpget:
% snmpget -v1 -c public nas.jazz iso.3.6.1.4.1.6574.4.2.21.2.0
iso.3.6.1.4.1.6574.4.2.21.2.0 = Opaque: Float: 865.000000

System Health

version	core-2021.8.6
installation_type	Home Assistant Container
dev	false
hassio	false
docker	true
user	root
virtualenv	false
python_version	3.9.6
os_name	Linux
os_version	5.10.52-v7l+
arch	armv7l
timezone	Europe/London

Home Assistant Cloud

logged_in	true
subscription_expiration	6 November 2021, 00:00
relayer_connected	true
remote_enabled	true
remote_connected	true
alexa_enabled	true
google_enabled	true
can_reach_cert_server	ok
can_reach_cloud_auth	ok
can_reach_cloud	ok

Lovelace

dashboards	1
resources	0
views	5
mode	storage

lextm · 2024-03-16T19:45:34Z

@cartwrightian you actually hit the same issue.

We finally have a patch to submit to HA. Hope it can make into the next release.

fabaff mentioned this issue Aug 11, 2016

Convert numerical values to float (fixes #2767) #2788

Closed

5 tasks

balloobbot added the waiting-for-reply label Jul 17, 2017

balloobbot removed the waiting-for-reply label Aug 12, 2017

balloobbot added the waiting-for-reply label Oct 20, 2017

balloobbot removed the waiting-for-reply label Dec 11, 2017

ChristianKuehnel mentioned this issue Dec 19, 2017

sensor.snmp added decoding of "Opaque" types. #11239

Closed

2 tasks

balloobbot added the waiting-for-reply label May 29, 2018

balloobbot removed the waiting-for-reply label Jul 26, 2018

balloobbot added the waiting-for-reply label Oct 26, 2018

balloobbot removed the waiting-for-reply label Dec 14, 2018

cgarwood closed this as completed Dec 14, 2018

Al-Dek mentioned this issue Mar 5, 2024

SNMP sensor and OPAQUE data type #112392

Closed

lextm mentioned this issue Mar 16, 2024

snmp: Better sensor support to resolve previous issues #113624

Merged

20 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

SNMP sensor not processing float values (correctly) #2767

SNMP sensor not processing float values (correctly) #2767

fanaticDavid commented Aug 9, 2016 •

edited

fabaff commented Aug 11, 2016 •

edited

fabaff commented Aug 11, 2016

fanaticDavid commented Aug 11, 2016 •

edited

Spartan-II-117 commented Mar 14, 2017

fanaticDavid commented May 3, 2017

balloobbot commented Jul 17, 2017

fanaticDavid commented Jul 17, 2017

balloobbot commented Oct 20, 2017

fanaticDavid commented Oct 20, 2017 •

edited

ChristianKuehnel commented Dec 19, 2017

keithmichael commented Feb 5, 2018

fanaticDavid commented Feb 5, 2018

keithmichael commented Feb 5, 2018 via email

balloobbot commented May 29, 2018

fanaticDavid commented May 31, 2018

keithmichael commented May 31, 2018 via email

balloobbot commented Oct 26, 2018

fanaticDavid commented Nov 3, 2018

bagobones commented Nov 13, 2018

cgarwood commented Dec 14, 2018

cartwrightian commented Oct 22, 2021

lextm commented Mar 16, 2024

SNMP sensor not processing float values (correctly) #2767

SNMP sensor not processing float values (correctly) #2767

Comments

fanaticDavid commented Aug 9, 2016 • edited

fabaff commented Aug 11, 2016 • edited

fabaff commented Aug 11, 2016

fanaticDavid commented Aug 11, 2016 • edited

Spartan-II-117 commented Mar 14, 2017

fanaticDavid commented May 3, 2017

balloobbot commented Jul 17, 2017

fanaticDavid commented Jul 17, 2017

balloobbot commented Oct 20, 2017

fanaticDavid commented Oct 20, 2017 • edited

ChristianKuehnel commented Dec 19, 2017

keithmichael commented Feb 5, 2018

fanaticDavid commented Feb 5, 2018

keithmichael commented Feb 5, 2018 via email

balloobbot commented May 29, 2018

fanaticDavid commented May 31, 2018

keithmichael commented May 31, 2018 via email

balloobbot commented Oct 26, 2018

fanaticDavid commented Nov 3, 2018

bagobones commented Nov 13, 2018

cgarwood commented Dec 14, 2018

cartwrightian commented Oct 22, 2021

System Health

lextm commented Mar 16, 2024

fanaticDavid commented Aug 9, 2016 •

edited

fabaff commented Aug 11, 2016 •

edited

fanaticDavid commented Aug 11, 2016 •

edited

fanaticDavid commented Oct 20, 2017 •

edited