# Intercept Modbus errors

**URL:** <https://discourse.nodered.org/t/intercept-modbus-errors/101461>\
**Category:** Industrial\
**Created:** [12 July 2026 17:09 UTC](https://discourse.nodered.org/t/intercept-modbus-errors/101461 "2026-07-12T17:09:05Z")\
**Posts on this page:** 8\
**Page:** 2

<div class="post-metadata">

**Author:** ![jlt57](https://avatars.discourse-cdn.com/v4/letter/j/3bc359/32.png) [@jlt57](https://discourse.nodered.org/u/jlt57)\
**Post date:** [14 July 2026 09:24 UTC](https://discourse.nodered.org/t/intercept-modbus-errors/101461/21 "2026-07-14T09:24:06Z")

</div>

The status does not detect errors on the read/write nodes...

---

<div class="post-metadata">

**Author:** ![jlt57](https://avatars.discourse-cdn.com/v4/letter/j/3bc359/32.png) [@jlt57](https://discourse.nodered.org/u/jlt57)\
**Post date:** [14 July 2026 09:26 UTC](https://discourse.nodered.org/t/intercept-modbus-errors/101461/22 "2026-07-14T09:26:07Z")

</div>

By using `catch` and a function, I'll manage to do what I need: a status bit for all the communication nodes.

---

<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:** [14 July 2026 09:28 UTC](https://discourse.nodered.org/t/intercept-modbus-errors/101461/24 "2026-07-14T09:28:18Z")

</div>

> [@jlt57](#):
>
> The status does not detect errors on the read/write nodes...

You said that it shows connecting, which means that it is not working.

---

<div class="post-metadata">

**Author:** ![jlt57](https://avatars.discourse-cdn.com/v4/letter/j/3bc359/32.png) [@jlt57](https://discourse.nodered.org/u/jlt57)\
**Post date:** [14 July 2026 09:33 UTC](https://discourse.nodered.org/t/intercept-modbus-errors/101461/25 "2026-07-14T09:33:25Z")

</div>

I was referring to the status node I added for testing purposes.  
Once again, a message appears in the status node when a read node is used.  
If the read node is disabled and a write operation is performed, no error is reported in the status node; however, the error is reported in the Catch node.

---

<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:** [14 July 2026 10:29 UTC](https://discourse.nodered.org/t/intercept-modbus-errors/101461/26 "2026-07-14T10:29:19Z")

</div>

> [@jlt57](#):
>
> If the read node is disabled and a write operation is performed, no error is reported in the status node

But presumably the status of the write node is showing that it is not working.

---

<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:** [30 July 2026 09:15 UTC](https://discourse.nodered.org/t/intercept-modbus-errors/101461/27 "2026-07-30T09:15:25Z")

</div>

Hello @jlt57

Update your **node-red-contrib-modbus** nodes to the latest version `5.60.1` because some fixes where included recently and now you can handle errors from your Modbus requests by using the **Empty msg on Modbus fail** option. ([link](https://github.com/BiancoRoyal/node-red-contrib-modbus/pull/578))

![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/3/9/3915327df34f6340a891223c1bf8f6b0d50a6941.png)

By enabling this option you will now get an error on the same flow line without relying on Catch and Status nodes that complicate flows and dont always reliably catch errors especially when the device was in Reconnect / re-initializing state (as you have noticed)

Example of an error msg .. that can later be handled in your flow by checking for the `error` property in the msg.

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/f/7/f72bd82ce689644fd65e9fa96caebb962ee98ece.png)

---

<div class="post-metadata">

**Author:** ![jlt57](https://avatars.discourse-cdn.com/v4/letter/j/3bc359/32.png) [@jlt57](https://discourse.nodered.org/u/jlt57)\
**Post date:** [3 August 2026 09:47 UTC](https://discourse.nodered.org/t/intercept-modbus-errors/101461/28 "2026-08-03T09:47:55Z")

</div>

Hello @UnborN

Thank you very much for this good news.  
I will perform the update as soon as possible.

All the best.  
Jean-Luc

---

<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:** [2 October 2026 09:48 UTC](https://discourse.nodered.org/t/intercept-modbus-errors/101461/29 "2026-10-02T09:48:19Z")

</div>

Closed on 2 October 2026 09:48 UTC

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

[Previous page](https://discourse.nodered.org/t/intercept-modbus-errors/101461.md?page=1)
