# RPi CPU Temperature monitoring - simple but informative

**URL:** <https://discourse.nodered.org/t/rpi-cpu-temperature-monitoring-simple-but-informative/28540>\
**Category:** Share Your Projects\
**Created:** [18 June 2020 10:15 UTC](https://discourse.nodered.org/t/rpi-cpu-temperature-monitoring-simple-but-informative/28540 "2020-06-18T10:15:32Z")\
**Posts on this page:** 17\
**Page:** 2

<div class="post-metadata">

**Author:** ![cymplecy](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/cymplecy/32/2773_2.png) [@cymplecy](https://discourse.nodered.org/u/cymplecy)\
**Post date:** [23 June 2020 21:40 UTC](https://discourse.nodered.org/t/rpi-cpu-temperature-monitoring-simple-but-informative/28540/21 "2020-06-23T21:40:40Z")

</div>

> [@alphaOri](#):
>
> Just an idea, if you want to reduce cost and overkill you could try using arduino's instead of RPi's when you just need to turn something on/off. I use a central RPi and several arduino nano's around the house. They talk using MQTT. You can get wifi or ethernet shields - I think there are some arduino's with the wifi built-in. I feel like this setup is also easier to maintain code-wise.

I've got plenty of PiZero (most are $5 originals with a WiFi dongle hacked onto them)

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/7/3/737470c636333653fa276c6295f2ebf3a9a30b84.jpeg)

I do use a couple of Wemos D1 minis as well to just receive MQTT generated by the Pi computers

I generally use the Pi for when I want a bit more than just switching stuff on or off

I find it MUCH easier to maintain, understand and change Node-RED code than Arduino C++ stuff 🙂

---

<div class="post-metadata">

**Author:** ![alphaOri](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/alphaori/32/18507_2.png) [@alphaOri](https://discourse.nodered.org/u/alphaOri)\
**Post date:** [24 June 2020 00:50 UTC](https://discourse.nodered.org/t/rpi-cpu-temperature-monitoring-simple-but-informative/28540/22 "2020-06-24T00:50:15Z")

</div>

That's a good point about getting power to the arduino's - although you'll have the same problem with the RPi's.

In a couple instances, I've had to pull wire and install another outlet (i.e. for a sensor in the attic, water monitor in the crawspace, or temp/humidity sensor over my porch), but I understand that's inconvenient or dangerous for DIY...

---

<div class="post-metadata">

**Author:** ![alphaOri](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/alphaori/32/18507_2.png) [@alphaOri](https://discourse.nodered.org/u/alphaOri)\
**Post date:** [24 June 2020 00:54 UTC](https://discourse.nodered.org/t/rpi-cpu-temperature-monitoring-simple-but-informative/28540/23 "2020-06-24T00:54:03Z")

</div>

Wow, that's a great deal. I see wifi zero's are $15 now but still that beats a nano with wifi shield. Having said that, I still love a chance to do some C coding - something about programming a microcontroller in C is awesome fun... I used to be a PIC guy till arduino spoiled me 🙂

---

<div class="post-metadata">

**Author:** ![jguillod](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/jguillod/32/240_2.png) [@jguillod](https://discourse.nodered.org/u/jguillod)\
**Post date:** [25 June 2020 10:44 UTC](https://discourse.nodered.org/t/rpi-cpu-temperature-monitoring-simple-but-informative/28540/24 "2020-06-25T10:44:55Z")

</div>

@edje11 : Is your RPi monitoring system available?

---

<div class="post-metadata">

**Author:** ![Nodi.Rubrum](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/nodi.rubrum/32/107482_2.png) [@Nodi.Rubrum](https://discourse.nodered.org/u/Nodi.Rubrum)\
**Post date:** [25 June 2020 14:08 UTC](https://discourse.nodered.org/t/rpi-cpu-temperature-monitoring-simple-but-informative/28540/26 "2020-06-25T14:08:41Z")

</div>

Well, after thinking about it... I have decided to retire as much of my python scripting as possible over time, as I move things into node-red. Ignore the grown man crying behind the curtain... All the python I have was a real time investment... oh well. LOL.

---

<div class="post-metadata">

**Author:** ![grumpazoid](https://avatars.discourse-cdn.com/v4/letter/g/4da419/32.png) [@grumpazoid](https://discourse.nodered.org/u/grumpazoid)\
**Post date:** [25 June 2020 19:26 UTC](https://discourse.nodered.org/t/rpi-cpu-temperature-monitoring-simple-but-informative/28540/27 "2020-06-25T19:26:26Z")

</div>

I've just this minute (OK about 15mins) installed Node Red onto my Pi zero W. Just got to think of some uses for it now. Probably ideal for experimenting away from my production version.

---

<div class="post-metadata">

**Author:** ![zenofmud](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/zenofmud/32/316_2.png) [@zenofmud](https://discourse.nodered.org/u/zenofmud)\
**Post date:** [25 June 2020 19:43 UTC](https://discourse.nodered.org/t/rpi-cpu-temperature-monitoring-simple-but-informative/28540/28 "2020-06-25T19:43:48Z")

</div>

I use a pizerow as my mqtt broker and in no I have it checking on my Wemos’s telling me who’s alive and what version of espeasy is installed on them

---

<div class="post-metadata">

**Author:** ![Nodi.Rubrum](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/nodi.rubrum/32/107482_2.png) [@Nodi.Rubrum](https://discourse.nodered.org/u/Nodi.Rubrum)\
**Post date:** [26 June 2020 02:00 UTC](https://discourse.nodered.org/t/rpi-cpu-temperature-monitoring-simple-but-informative/28540/29 "2020-06-26T02:00:33Z")

</div>

I found one odd ball issue, I put a image built on a Pi4 on my PiZero, node-red fails to start. The issue is nodejs for ARM v7 can't handle ARM v6 based Pi devices. I had to uninstall nodejs manually and then let the node-red install script reinstall nodejs to fix the issue. Unfortunately, I lost all my flows in the process, not sure why that happened, but it did. Maybe the way I did the sequence of steps caused the loss of the flows.

---

<div class="post-metadata">

**Author:** ![Bobo](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bobo/32/8401_2.png) [@Bobo](https://discourse.nodered.org/u/Bobo)\
**Post date:** [26 June 2020 04:25 UTC](https://discourse.nodered.org/t/rpi-cpu-temperature-monitoring-simple-but-informative/28540/30 "2020-06-26T04:25:38Z")

</div>

> [@Nodi.Rubrum](#):
>
> I put a image built on a Pi4 on my PiZero

The answer is [Node-Red Starts on RPi3+ but not on RPi Zero W](https://discourse.nodered.org/t/node-red-starts-on-rpi3-but-not-on-rpi-zero-w/1838)

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [26 June 2020 08:15 UTC](https://discourse.nodered.org/t/rpi-cpu-temperature-monitoring-simple-but-informative/28540/31 "2020-06-26T08:15:13Z")

</div>

> [@Nodi.Rubrum](#):
>
> Unfortunately, I lost all my flows in the process

That will not have deleted the flows file, but it might be that node-red cannot find it for some reason. If the flows were important then immediately make a copy of your .node-red folder (so you do not accidentally delete anything) and show us what is in the .node-red folder by running  
`ls -l ~/.node-red`  
and show us the startup log you see from running  
`node-red-stop && node-red-start`  
Copy/paste please rather than a screenshot if possible.

---

<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:** [26 June 2020 08:28 UTC](https://discourse.nodered.org/t/rpi-cpu-temperature-monitoring-simple-but-informative/28540/32 "2020-06-26T08:28:51Z")

</div>

by default they use flows\_{hostname}.json - so if the pi0 has a different name it will start with a different file... the old one may indeed still be there and can be copied/renamed etc.

---

<div class="post-metadata">

**Author:** ![Nodi.Rubrum](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/nodi.rubrum/32/107482_2.png) [@Nodi.Rubrum](https://discourse.nodered.org/u/Nodi.Rubrum)\
**Post date:** [26 June 2020 14:56 UTC](https://discourse.nodered.org/t/rpi-cpu-temperature-monitoring-simple-but-informative/28540/33 "2020-06-26T14:56:36Z")

</div>

@dceejay  
That is likely the issue, I do change the host names, via DHCP provided name, when a new image boots for the first time.

Binding an installation, in this case create flows, to a static host name seems odd to me. I have a long history with engineering enterprise deployment of operating system images, to virtual machines, containers, etc. So when solutions are bound to something that can change like in this case, we encouraged solution provides to avoid it.

Is this something that can be changed in the future?

---

<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:** [26 June 2020 15:11 UTC](https://discourse.nodered.org/t/rpi-cpu-temperature-monitoring-simple-but-informative/28540/34 "2020-06-26T15:11:59Z")

</div>

> [@Nodi.Rubrum](#):
>
> Is this something that can be changed in the future

Not sure if it will be changed but you can handle this yourself by providing a flow file name on the command line that starts node-red.

I think it may also be possible in settings.js (I forget)

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [26 June 2020 15:46 UTC](https://discourse.nodered.org/t/rpi-cpu-temperature-monitoring-simple-but-informative/28540/35 "2020-06-26T15:46:31Z")

</div>

> [@Steve-Mcl](#):
>
> I think it may also be possible in settings.js

Yes, the name of the flow file can be configured in settings.js, it is documented in the file, or you can set it in the command line.

---

<div class="post-metadata">

**Author:** ![zenofmud](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/zenofmud/32/316_2.png) [@zenofmud](https://discourse.nodered.org/u/zenofmud)\
**Post date:** [26 June 2020 16:10 UTC](https://discourse.nodered.org/t/rpi-cpu-temperature-monitoring-simple-but-informative/28540/36 "2020-06-26T16:10:13Z")

</div>

It gets lots easier if you enable projects because you will name the flow when starting a project.

---

<div class="post-metadata">

**Author:** ![Nodi.Rubrum](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/nodi.rubrum/32/107482_2.png) [@Nodi.Rubrum](https://discourse.nodered.org/u/Nodi.Rubrum)\
**Post date:** [26 June 2020 21:31 UTC](https://discourse.nodered.org/t/rpi-cpu-temperature-monitoring-simple-but-informative/28540/37 "2020-06-26T21:31:14Z")

</div>

Settings.js file will be the preferred method, since I am going to use ansible to install node-red and validate nodejs, etc.

---

<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:** [17 August 2020 10:15 UTC](https://discourse.nodered.org/t/rpi-cpu-temperature-monitoring-simple-but-informative/28540/38 "2020-08-17T10:15:37Z")

</div>

Closed on 17 August 2020 10:15 UTC

This topic was automatically closed after 60 days. New replies are no longer allowed.

[Previous page](https://discourse.nodered.org/t/rpi-cpu-temperature-monitoring-simple-but-informative/28540.md?page=1)