# Node-red-contrib-modbus Version 5.2.0 vs V4.1.3

**URL:** <https://discourse.nodered.org/t/node-red-contrib-modbus-version-5-2-0-vs-v4-1-3/19428>\
**Category:** General\
**Created:** [21 December 2019 16:44 UTC](https://discourse.nodered.org/t/node-red-contrib-modbus-version-5-2-0-vs-v4-1-3/19428 "2019-12-21T16:44:29Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![JoseGodinho](https://avatars.discourse-cdn.com/v4/letter/j/f4b2a3/32.png) [@JoseGodinho](https://discourse.nodered.org/u/JoseGodinho)\
**Post date:** [21 December 2019 16:44 UTC](https://discourse.nodered.org/t/node-red-contrib-modbus-version-5-2-0-vs-v4-1-3/19428/1 "2019-12-21T16:44:29Z")

</div>

Hello All

I have two node red instances, after upgrading the modbus node to the latest version, i got the this error

"FSM Reset On State {"value":"failed","actions":,"changed":true}"

albeit with the same configuration and hardware it works in the modbus V4.1.3

Any sugestion?

---

<div class="post-metadata">

**Author:** ![jpillman](https://avatars.discourse-cdn.com/v4/letter/j/c89c15/32.png) [@jpillman](https://discourse.nodered.org/u/jpillman)\
**Post date:** [26 December 2019 17:41 UTC](https://discourse.nodered.org/t/node-red-contrib-modbus-version-5-2-0-vs-v4-1-3/19428/2 "2019-12-26T17:41:13Z")

</div>

Very similar issue for me as well.

---

<div class="post-metadata">

**Author:** ![JoseGodinho](https://avatars.discourse-cdn.com/v4/letter/j/f4b2a3/32.png) [@JoseGodinho](https://discourse.nodered.org/u/JoseGodinho)\
**Post date:** [26 December 2019 17:50 UTC](https://discourse.nodered.org/t/node-red-contrib-modbus-version-5-2-0-vs-v4-1-3/19428/3 "2019-12-26T17:50:18Z")

</div>

for now I manage to downgrade the version ...

---

<div class="post-metadata">

**Author:** ![tamzrod](https://avatars.discourse-cdn.com/v4/letter/t/858c86/32.png) [@tamzrod](https://discourse.nodered.org/u/tamzrod)\
**Post date:** [26 December 2019 23:16 UTC](https://discourse.nodered.org/t/node-red-contrib-modbus-version-5-2-0-vs-v4-1-3/19428/4 "2019-12-26T23:16:23Z")

</div>

same issue here...

---

<div class="post-metadata">

**Author:** ![h2oil](https://avatars.discourse-cdn.com/v4/letter/h/96bed5/32.png) [@h2oil](https://discourse.nodered.org/u/h2oil)\
**Post date:** [23 January 2020 22:59 UTC](https://discourse.nodered.org/t/node-red-contrib-modbus-version-5-2-0-vs-v4-1-3/19428/5 "2020-01-23T22:59:59Z")

</div>

same issue here, anyone fix this?!

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [24 January 2020 07:16 UTC](https://discourse.nodered.org/t/node-red-contrib-modbus-version-5-2-0-vs-v4-1-3/19428/6 "2020-01-24T07:16:54Z")

</div>

Has an issue been posted against the node on GitHub?

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [1 February 2020 07:17 UTC](https://discourse.nodered.org/t/node-red-contrib-modbus-version-5-2-0-vs-v4-1-3/19428/8 "2020-02-01T07:17:39Z")

</div>

@gdallaire have you checked to see whether an issue has been raised against the node? There is no point telling us about it here, it is the node author that needs to do something about it.