Flow to get CPU die temperature from EPIC PR1

[pbg]

Hi Beno,

I found this information very useful.

I am trying to get more information from my Epic. What would be the path to both internal temperatures 1 and 2? I tried with “…/thermal_zone1” without success.

[torchard]

After some digging around, I think the easiest way to get all three would be with an (unsupported) REST API call.

The endpoint is https://<hostname>/manage/api/v1/system/temperature

And it will return all three in JSON format:

{
  "cpu": 44.344,
  "thermistor1": 47.661572868124495,
  "thermistor2": 48.03976944777736
}

---

Disclaimer: I say “unsupported” because while this endpoint works on the current firmware, it is not documented in the REST API swagger, so is subject to change or revision with any other versions of firmware, so I cannot guarantee that it will work 100% of the time for every PR1/PR2 for the rest of their lifetime.

[pbg]

Thank you, but I am new using Node-red, I haven´t gone to the API calls yet. Is there an easier way to do it in Node-red?

[torchard]

It really is the easiest way to get all three at once, I’ve broken down exactly how to use the API in another thread:

Authenticating Opto API calls with HTTP request

Here are some tips to using Opto API’s like groov Manage, groov View, and PAC Control with the standard HTTP request core node. In this post I’ll go over how to set the apiKey header object and how to enable SSL/TLS in the request node. Note that this doesn’t and shouldn’t replace the groov IO nodes, groov View,or the PAC Control nodes – it just provides a way to use API endpoints that are not exposed through those nodes. For example there is no way to use a node to unmount an installed USB dri…

[pbg]

Thank you, I read the post you recommended and managed to apply it to my Node-red editor and it works! I sent all of them to the float scratchpad then.