# Node-Red Freezes

**URL:** <https://discourse.nodered.org/t/node-red-freezes/26035>\
**Category:** General\
**Created:** [3 May 2020 23:34 UTC](https://discourse.nodered.org/t/node-red-freezes/26035 "2020-05-03T23:34:00Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![n61ab](https://avatars.discourse-cdn.com/v4/letter/n/cc9497/32.png) [@n61ab](https://discourse.nodered.org/u/n61ab)\
**Post date:** [3 May 2020 23:34 UTC](https://discourse.nodered.org/t/node-red-freezes/26035/1 "2020-05-03T23:34:00Z")

</div>

I am trying to use an “ina-sensor” node to read the volts/amps from an INA219 sensor from ada-fruit. This sensor works on the I2C bus. When I add the sensor, my Node-Red fails after a few hours.

I re-booted the Raspberry Pi 4 and started Node-Red from the console. Following text is what I see on the console, the last trhee lines keep repeating up to the Node-Red freezing. When I remove the INA219 Sensors from the circuit, I no longer get the repeating lines:

==========================================

_Start Node-RED_

- 
  - 

_Once Node-RED has started, point a browser at [http://192.168.50.192:1880](http://192.168.50.192:1880)_  
_On Pi Node-RED works better with the Firefox or Chrome browser_

- 
  - 

_Use node-red-stop to stop Node-RED_  
_Use node-red-start to start Node-RED again_  
_Use node-red-log to view the recent log output_  
_Use sudo systemctl enable nodered.service to autostart Node-RED at every boot_  
_Use sudo systemctl disable nodered.service to disable autostart on boot_

- 
  - 

_To find more nodes and example flows - go to [http://flows.nodered.org](http://flows.nodered.org)_

- 
  - 

_Starting as a systemd service._  
_0.01_  
_false_  
_initing!_  
_0.01_  
_false_  
_initing!_  
_0.01_

=================================================

I have tried every everything to isolate the problem. New Raspian load, new Node-Red load, new SD Card, new Raspberry Pi.

I also tried four separate INA219 boards. I tried changing the address of the board, some with 0X40 and some with 0X41. I get the same result.

I have reduced to flow to two nodes, a “ina-sensor” node and a “debug” node. No other nodes are running.

I need any help or suggestions. Clearly, something is causing the repeating lines, “false”, "initing" and “0.01” that leads up the Node-Red freezing up.

Alan

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [3 May 2020 23:41 UTC](https://discourse.nodered.org/t/node-red-freezes/26035/2 "2020-05-03T23:41:57Z")

</div>

Perhaps raise an issue on the [GitHub repo](https://github.com/easybotics/node-red-contrib-easybotics-ina219)

Edit...

When you say you tried everything, did you try different nodejs versions? What version are you running? Perhaps that node doesn't like particular versions?

---

<div class="post-metadata">

**Author:** ![n61ab](https://avatars.discourse-cdn.com/v4/letter/n/cc9497/32.png) [@n61ab](https://discourse.nodered.org/u/n61ab)\
**Post date:** [3 May 2020 23:58 UTC](https://discourse.nodered.org/t/node-red-freezes/26035/3 "2020-05-03T23:58:31Z")

</div>

Steve

No, I did not try other nodejs versions.

Where do I get my nodejs version? Can you point me to something to read on how do change the nodejs?

Alan

---

<div class="post-metadata">

**Author:** ![n61ab](https://avatars.discourse-cdn.com/v4/letter/n/cc9497/32.png) [@n61ab](https://discourse.nodered.org/u/n61ab)\
**Post date:** [4 May 2020 00:08 UTC](https://discourse.nodered.org/t/node-red-freezes/26035/4 "2020-05-04T00:08:58Z")

</div>

I did run the install script from the [Node-Red.org](http://Node-Red.org) web site for the Raspberry Pi.

The Web site says the script will:

- install the current Node.js LTS release using the [NodeSource ([https://github.com/nodesource/distributions/blob/master/README.md](https://github.com/nodesource/distributions/blob/master/README.md)). If it detects Node.js is already installed from NodeSource, it will ensure it is at least Node 8, but otherwise leave it alone

So, I assume I have Node 8.

Alan

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [4 May 2020 00:11 UTC](https://discourse.nodered.org/t/node-red-freezes/26035/5 "2020-05-04T00:11:40Z")

</div>

In a terminal, type `node -v` followed by enter key

I would personally install V10 or 12

---

<div class="post-metadata">

**Author:** ![n61ab](https://avatars.discourse-cdn.com/v4/letter/n/cc9497/32.png) [@n61ab](https://discourse.nodered.org/u/n61ab)\
**Post date:** [4 May 2020 00:35 UTC](https://discourse.nodered.org/t/node-red-freezes/26035/6 "2020-05-04T00:35:27Z")

</div>

I have. v10.16.3

How do I install V12?

---

<div class="post-metadata">

**Author:** ![n61ab](https://avatars.discourse-cdn.com/v4/letter/n/cc9497/32.png) [@n61ab](https://discourse.nodered.org/u/n61ab)\
**Post date:** [4 May 2020 00:52 UTC](https://discourse.nodered.org/t/node-red-freezes/26035/7 "2020-05-04T00:52:45Z")

</div>

OK, I found several articles on how to update NodeJS.

How should I proceeded to match the "ina-sensor" node with the correct NodeJS version?

Alan

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [4 May 2020 00:54 UTC](https://discourse.nodered.org/t/node-red-freezes/26035/8 "2020-05-04T00:54:12Z")

</div>

No idea, was just a suggestion. My guess, from the date on the last published update, V12 was out. As you're having no success with several different hardware, try something else.

---

<div class="post-metadata">

**Author:** ![n61ab](https://avatars.discourse-cdn.com/v4/letter/n/cc9497/32.png) [@n61ab](https://discourse.nodered.org/u/n61ab)\
**Post date:** [6 May 2020 21:21 UTC](https://discourse.nodered.org/t/node-red-freezes/26035/9 "2020-05-06T21:21:36Z")

</div>

Well, I found the problem.

After trying all combinations of operating systems, Node-Red and node.js, none fixed the problem of Node-Red freezing up after about an hour.

So, I pulled the Raspberry board and the INA-219 board and built it up on my bench using a breadboard. It worked just fine!

I put the Raspberry board and the INA-219 board back into my cabinet, and again, after about and hour, Node-Red froze up again.

Th "failure" hardware configuration includes a common , 10 foot length of RJ50 cable for both the I2C bus devices (INA-219) and the One Wire devices (Temperature). I found these two data buses could not "co-exist" on the same ten foot length of cable.

I ran each data bus on separate cables and.....problem solved!

Alan

---

<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:** [20 May 2020 21:21 UTC](https://discourse.nodered.org/t/node-red-freezes/26035/10 "2020-05-20T21:21:37Z")

</div>

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