After upgrading to v3.50 I experienced that Node-Red accessed via VRM became very unstable and in practise useless. It lost connection after seconds.
I also lost some of the data point I to pull from the VRM API, i.e forecast values. I assume that issue is related to the issue i mentioned in this Topic, but I haven’t checked.
[VRM API - ID number change because of VRM update?]
Anyone else with a similar experience?
Reinstalling v3.41 solved the issue, it also brought back the VRM API data
This small calculation is made based on these VRM APID Forecast data.
Good evening,
After looking into your system with your approval by email, I do believe that the NodeRED issues you’re experiencing are due to the fact that you reboot the NodeRed service when the CPU is higher than 60%, as you told me in your email.
I would suggest to disable this or optimize your NodeRed code.
I do not see anything else strange in your system that would explain those issues.