# SNMP msg.payload changed between versions

**URL:** <https://discourse.nodered.org/t/snmp-msg-payload-changed-between-versions/84434>\
**Category:** General\
**Created:** [9 January 2024 20:27 UTC](https://discourse.nodered.org/t/snmp-msg-payload-changed-between-versions/84434 "2024-01-09T20:27:32Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [9 January 2024 20:41 UTC](https://discourse.nodered.org/t/snmp-msg-payload-changed-between-versions/84434/2 "2024-01-09T20:41:06Z")

</div>

> [@Snmp data visualization](https://discourse.nodered.org/t/snmp-data-visualization/83147/34):
>
> snmp data type 4 is an OctetString (also shown as the tstr property). so just bytes as a string. So in theory it's safe to turn into a string... BUT when I did that it caused other (real power) snmp users to have problems and so I "fixed" it to send what they expect and let them handle it.

Use `.toString()` on the `value`

---

_[View the full topic](https://discourse.nodered.org/t/snmp-msg-payload-changed-between-versions/84434)._