The status does not detect errors on the read/write nodes...
By using catch and a function, I'll manage to do what I need: a status bit for all the communication nodes.
You said that it shows connecting, which means that it is not working.
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.
But presumably the status of the write node is showing that it is not working.
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)
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.
Hello @UnborN
Thank you very much for this good news.
I will perform the update as soon as possible.
All the best.
Jean-Luc
