# How Can I Catch Error "serial port /dev/rfcomm0 closed unexpectedly"

**URL:** <https://discourse.nodered.org/t/how-can-i-catch-error-serial-port-dev-rfcomm0-closed-unexpectedly/15038>\
**Category:** General\
**Created:** [3 September 2019 00:03 UTC](https://discourse.nodered.org/t/how-can-i-catch-error-serial-port-dev-rfcomm0-closed-unexpectedly/15038 "2019-09-03T00:03:50Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![marcpouliot](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/marcpouliot/32/4326_2.png) [@marcpouliot](https://discourse.nodered.org/u/marcpouliot)\
**Post date:** [4 September 2019 18:40 UTC](https://discourse.nodered.org/t/how-can-i-catch-error-serial-port-dev-rfcomm0-closed-unexpectedly/15038/7 "2019-09-04T18:40:09Z")

</div>

The error has a red vertical bar attached to it and does not refer to a node.  
When the temporary bluetooth device is disconnected, the error occurs and repeats itself every 14-20 seconds. Once this error occurs, the status node changes from connected to not connected although it is not connected.  
If I could catch this error message in a flow, I could then release the device. This would have the effect of stopping the invalid toggling of the status by giving only one error message (file not found).  
I hope this is a bit clearer.

---

_[View the full topic](https://discourse.nodered.org/t/how-can-i-catch-error-serial-port-dev-rfcomm0-closed-unexpectedly/15038)._