# Issue with node-red-contrib-modbus

**URL:** <https://discourse.nodered.org/t/issue-with-node-red-contrib-modbus/101637>\
**Category:** General\
**Created:** [14 August 2026 11:54 UTC](https://discourse.nodered.org/t/issue-with-node-red-contrib-modbus/101637 "2026-08-14T11:54:35Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Switchblade2](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/switchblade2/32/60655_2.png) [@Switchblade2](https://discourse.nodered.org/u/Switchblade2)\
**Post date:** [14 August 2026 11:54 UTC](https://discourse.nodered.org/t/issue-with-node-red-contrib-modbus/101637/1 "2026-08-14T11:54:35Z")

</div>

I update node.js to v24 and NodeRed to v5.0.4 and after this upgrade my flow with 3 modbus nodes (1 modbus-read and 2 modbus-getter) worked fine.  
After upgrading the node-red-contrib-modbus from 5.45.2 to 5.60.1 my modbus-read and modbus-getter stopped sending data. The nodes enter in a cycle of disconnection & reconnecting. Sometime it would come alive, often, but not always if I opened one of the nodes or edited the Modbus Server config in the node.  
I solved the issue be rolling back to 5.45.2 so can't debug further.  
Any ideas of what could be cause the issue?

---

<div class="post-metadata">

**Author:** ![UnborN](https://avatars.discourse-cdn.com/v4/letter/u/4491bb/32.png) [@UnborN](https://discourse.nodered.org/u/UnborN)\
**Post date:** [14 August 2026 19:57 UTC](https://discourse.nodered.org/t/issue-with-node-red-contrib-modbus/101637/2 "2026-08-14T19:57:15Z")

</div>

> **[Release v5.60.2 — reconnect recovery (#569) ·...](https://github.com/BiancoRoyal/node-red-contrib-modbus/releases/tag/v5.60.2)**
>
> Summary
> LTS patch on support/v5.60 for faster, clearer recovery after the 5.60.1 timeout/DNS honesty path (#569; related #564).
> Bug Fixes
> 
> Connect immediately after the reconnect wait (no stacked s...

Version `5.60.2` was just released fixing some reconnection issues.

---

<div class="post-metadata">

**Author:** ![Switchblade2](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/switchblade2/32/60655_2.png) [@Switchblade2](https://discourse.nodered.org/u/Switchblade2)\
**Post date:** [15 August 2026 07:12 UTC](https://discourse.nodered.org/t/issue-with-node-red-contrib-modbus/101637/3 "2026-08-15T07:12:38Z")

</div>

Upgraded to 5.60.2 and the issue remains. it seems to be the modbus-read node that is not giving any data. The modbus-getter node I have works fine.  
Solved it by changing my only modbus-read node to a modbus-getter node triggered by an inject node. Actually better for me as I now have better control of the exact time when it is triggered

---

<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:** [29 August 2026 07:13 UTC](https://discourse.nodered.org/t/issue-with-node-red-contrib-modbus/101637/4 "2026-08-29T07:13:21Z")

</div>

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