# 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:** 5

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [3 September 2019 15:41 UTC](https://discourse.nodered.org/t/how-can-i-catch-error-serial-port-dev-rfcomm0-closed-unexpectedly/15038/5 "2019-09-03T15:41:54Z")

</div>

Or maybe the status node will catch it. (But basically you are saying it would be better if the error was only reported the first time?)

---

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