mwittig/node-fronius-solar

Access PV live logs using the Fronius Solar API

node-fronius-solar

Access PV live logs using the Fronius Solar API V0 and V1.

Usage Example

var fronius = require('node-fronius-solar'),
    util = require('util'),
    options = {
        host: 'localhost',
        port: 8001,
        deviceId: 1
        version: 0
    },
    x = Date.now();

// This is the Solar API V0 call which should work with Fronius Datalogger Web v2.0.4.1 (and higher) and
// Fronius Data Manager v3.0.3-1 (and higher)
fronius.GetInverterRealtimeData(options).then(function (json) {
    console.log(util.inspect(json, { depth: 4, colors : true }));
    console.log(Date.now() - x, "milliseconds elapsed")
}).catch(function(e) {console.log(e)});

// This is the Solar API V1
options.version = 1;
fronius.GetInverterRealtimeData(options).then(function (json) {
    console.log(util.inspect(json, { depth: 4, colors : true }));
    console.log(Date.now() - x, "milliseconds elapsed")
}).catch(function(e) {console.log(e)});

// GetComponentsData is provided to use an undocumented API service of the Fronius Data Manager
// provided with the Symo inverters. See https://forum.fhem.de/index.php/topic,24614.msg214011.html#msg214011
// In contrast to the regular Solar API Calls which do not require authentication, you may need to provide
// username and password properties to the options dictionary (if authentication has been enabled 
// for Fronius Data Manager.
fronius.GetComponentsData(options).then(function (json) {
    console.log(util.inspect(json, { depth: 4, colors : true }));
    console.log(Date.now() - x, "milliseconds elapsed")
}).catch(function(e) {console.log(e)});

// This is a Solar API V1 call which should work with Fronius Data Manager v3.4.2-1 (and higher)
fronius.GetPowerFlowRealtimeDataData(options).then(function (json) {
    console.log(util.inspect(json, { depth: 4, colors : true }));
    console.log(Date.now() - x, "milliseconds elapsed")
}).catch(function(e) {console.log(e)});

Release History

See Release History.

License

Copyright (c) 2015-2019, Marcus Wittig and contributors. All rights reserved.

MIT License.

node-fronius-solar's Issues

andere abfrage

hi,

wie groß wäre der Aufwand "ip-adresse/components/5/0/?print=names" als abfrage einzupflegen?
b.z.w. was müsste alles geändert werden?
damit würde man auch den Eigenverbrauch und die Einspeisung ermitteln können, vorrausgesetzt man hat einen Smartmeter.

lg M

Timeouts

Hi,
when I run example i'm getting request timeouts. When I'm trying curl sometimes I'm getting 404. I provided device ID, checking your code I assume that port doesn't matter and I provided found in settings. Any Idea what I'm doing wrong?

How to find the inverter's IP?

Hi @mwittig, thank you very much for the code. I was looking for some information regarding the connection to a Fronius inverter and stumbled across your repo.
I do have 2 questions though:
1 - I can imagine the IP has to be changed, from localhost to the IP of the inverter, right? Is there a way of knowing this IP?
2 - Is there a way of testing this API without having an inverter at home?

Thank you!

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

• Added the new Node.js version to your .travis.yml

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

• engines was only updated if it defined a single version, not a range.
• .nvmrc was updated to Node.js 10
• .travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖

---

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

2020 example.js

I had two fronius inverters installed recently and I got example.js working with the following config:

var fronius = require('./index'),
    util = require('util'),
    options = {
        username: "admin",
        password: "admin",
        host: '192.168.86.47',
        port: 80,
        deviceId: 1,
        version: 1
    },

I discovered the host IP from Google Wifi app -- annoyingly the fronius inverter/datamapper does not give itself a name so it appears as "Unnamed device". Fortunately, it was one of very few unnamed devices and I found it quickly.

I needed to set version: 1.

The primary inverter listens on port: 80.

I have two inverters that are connected so I can run the node example.js with deviceId: 1 or deviceId: 2