the API is sometimes delivering a negative value for load, which makes no sense. Converting it to an absolute value seems the only sensible solution. Never fronius firmware might fix this bug.
BrainDoctor committed
Jul 7, 2017 at 13:55 UTC
ad9ed133c4e6af1c96f610c9ac84f4df2f1dfafe
1 file changed
+1
-5
node.d/fronius.node.js
+1
-5
@@ -222,12 +222,8 @@ var fronius = {
222
service.end();
223
224
// Site Consumption Chart
225
- var consumption = site.P_Load;
226
- if (consumption === null) consumption = 0;
227
- consumption *= -1;
228
-
225
service.begin(fronius.getSiteConsumptionChart(service, 'fronius_' + service.name + '.consumption'));
230
- service.set(fronius.consumptionLoadId, Math.round(consumption));
226
+ service.set(fronius.consumptionLoadId, Math.round(Math.abs(site.P_Load)));
227
service.end();
228
229
// Site Autonomy Chart