# Problem with node-red-contrib-buffer-parser after upgrading node-RED

**URL:** <https://discourse.nodered.org/t/problem-with-node-red-contrib-buffer-parser-after-upgrading-node-red/55907>\
**Category:** General\
**Created:** [30 December 2021 21:09 UTC](https://discourse.nodered.org/t/problem-with-node-red-contrib-buffer-parser-after-upgrading-node-red/55907 "2021-12-30T21:09:56Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![sad\_cyrano](https://avatars.discourse-cdn.com/v4/letter/s/ebca7d/32.png) [@sad\_cyrano](https://discourse.nodered.org/u/sad_cyrano)\
**Post date:** [30 December 2021 21:09 UTC](https://discourse.nodered.org/t/problem-with-node-red-contrib-buffer-parser-after-upgrading-node-red/55907/1 "2021-12-30T21:09:56Z")

</div>

I work with the really ingenious buffer-parser-node but after changing Node-RED to version 2.1.4 I get a strange error. I have tried it on several platforms (Raspberry Pi and Windows PC) but the result is always the same:

 ![screenshot](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/9/9/994d0ba2cf6bf90e8cd5c921eb105ed6b154fd46.jpeg)

The "Output" fields can no longer be selected. It appears, but when I click on it, only a blue frame is drawn, but no selection options are displayed as usual. Can anyone help me find a way to use it again?

I have to update this post. It depends not only on the upgrade process. I have updated Node-RED to 2.1.4 on a third system (also a Windows machine) and here it works fine.

And another addendum: I have uninstalled the buffer-parser-node on this third system and reinstalled it and now I am facing the same issue. So it seems only to appear if one installs the node on an existing 2.1.4 installation.

---

<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:** [31 December 2021 00:09 UTC](https://discourse.nodered.org/t/problem-with-node-red-contrib-buffer-parser-after-upgrading-node-red/55907/2 "2021-12-31T00:09:21Z")

</div>

Hi. I have seen this and there is an open issue on the GitHub repository. I am working to fix and release an update soon (tomorrow?)

I have hesitated in sending out an update as it may be something that needs fixing in the core of node-red - however I have not had time to debug this.

I do know the issues are not present in 2.1.3. I also know it affects another of my nodes (node-red-contrib-omron-fins)

Short version - hold tight, a workaround will be published soon.

Ps, thanks for the compliments (disclosure, I am the author of buffer-parser)

---

<div class="post-metadata">

**Author:** ![sad\_cyrano](https://avatars.discourse-cdn.com/v4/letter/s/ebca7d/32.png) [@sad\_cyrano](https://discourse.nodered.org/u/sad_cyrano)\
**Post date:** [31 December 2021 12:02 UTC](https://discourse.nodered.org/t/problem-with-node-red-contrib-buffer-parser-after-upgrading-node-red/55907/3 "2021-12-31T12:02:17Z")

</div>

Dear Steve,  
thank you very much for your quick reply and even more for this perfect tool, it definitely makes 50% of the benefit of Node-Red for me 😉 I have reset Node-Red to 2.1.3 for now and everything works great again. Thanks again and all the best for the new year.  
Best regards,  
Werner

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [1 March 2022 12:03 UTC](https://discourse.nodered.org/t/problem-with-node-red-contrib-buffer-parser-after-upgrading-node-red/55907/4 "2022-03-01T12:03:08Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.