# Quick note if you're a) reading multiple ds18b20's with a raspberry pi and b) struggling with flow stalls

**URL:** https://discourse.nodered.org/t/quick-note-if-youre-a-reading-multiple-ds18b20s-with-a-raspberry-pi-and-b-struggling-with-flow-stalls/25747
**Category:** Hardware
**Created:** [29 April 2020 14:02 UTC](https://discourse.nodered.org/t/quick-note-if-youre-a-reading-multiple-ds18b20s-with-a-raspberry-pi-and-b-struggling-with-flow-stalls/25747 "2020-04-29T14:02:07Z")
**Posts on this page:** 1
**Showing post:** 8

<div class="post-metadata">

### Author: ![snafu](https://avatars.discourse-cdn.com/v4/letter/s/8edcca/32.png) [@snafu](https://discourse.nodered.org/u/snafu)
#### Post date: [27 May 2020 19:43 UTC](https://discourse.nodered.org/t/quick-note-if-youre-a-reading-multiple-ds18b20s-with-a-raspberry-pi-and-b-struggling-with-flow-stalls/25747/8 "2020-05-27T19:43:03Z")

</div>

I'll bump this, because it helped me solve a seemingly difficult problem with random errors.  
Node-red started to throw the error "EINTR: interrupted system call, read". At first I didn't find the cause, because it started some time after I had included the ds18b20 node. Apparently it was caused by the way the ds18b20-node was handling requests.

@nrbrt Great small scipt!

The service has been running flawlessly ever since I implemented it.

---

_[View the full topic](https://discourse.nodered.org/t/quick-note-if-youre-a-reading-multiple-ds18b20s-with-a-raspberry-pi-and-b-struggling-with-flow-stalls/25747)._