Git Product home page Git Product logo

pimatic-solarview's Introduction

pimatic-solarview

npm version Build Status

A pimatic Plugin for SolarView (SV), a data logger for PV systems:

SV is capable of gathering data from up to 9 inverters and additional meter points which may be used to monitor the in-house consumption of solar energy, for example. SV is a vendor-neutral solution which supports a large number of inverter models from various vendors. It is available for Fritz!Box, Raspberry PI, and Windows.

Screenshots

Example of the device display as provided by the SolarViewInverterSimple

screenshot

Example of the customizable graph utility provided by the pimatic frontend

screenshot

Configuration

To be able to read the SV data records with pimatic-solarview, the TCP-Server option must be enabled by adding the -TCP <port> option to the SV start script. See section TCP-Server of the SV Installation Manual.

You can load the plugin by editing your config.json to include the following in the plugins section. The properties host and port denote the hostname (or IP address) and port of the SV TCP server. The property interval specifies the time interval in seconds for updating the data set. For debugging purposes you may set property debug to true. This will write additional debug messages to the pimatic log.

{ 
   "plugin": "solarview"
   "host": "fritz.box"
   "port": 15000
   "interval": 10
}

Then you need to add a device in the devices section. The plugin offers three device types:

  • SolarViewInverterSimple: This type of device provides status data on the accumulated energy earnings (today, this month, this year, total) and the current power produced.
  • SolarViewInverter: This type of device additionally provides you with data on AC voltage, amperage and inverter temperature readings.
  • SolarViewInverterWithMPPTracker: This type of device is for PV systems with a MPP tracking system. It additionally provides you with data on voltage and amperage for up to three DC strings.

As part of the device definition you need to provide the inverterId which is a digit [0-9] to identify the number of the inverter attached to the SV logger (see example below). The digit 0 depicts the sum of all inverters attached to the SV logger.

{
    "id": "sv1",
    "class": "SolarViewInverterSimple",
    "name": "PV System",
    "inverterId": 0
}

Hints: If you wish to hide some attributes this is possible with pimatic v0.8.68 and higher using the xAttributeOptions property as shown in the following example. Using the xLink property you can also add a hyperlink to the device display.

{
    "id": "sv1",
    "class": "SolarViewInverterSimple",
    "name": "PV System",
    "inverterId": 0,
    "xLink": "http://fritz.box:88",
    "xAttributeOptions": [
        {
          "name": "currentPower",
          "hidden": true
        }
    ]
}

TODO

There are a few things I am planning to add in the short term:

  • Add support for additional meter points, for example, for an additional power meter to monitoring the in-house consumption of solar energy.
  • Currently, the update cycles also run at night. This could be limited to daylight hours even though the load caused by the update cycles should be fairly low.
  • Possibly add localized names for attributes if this is supported by pimatic.

History

See Release History.

License

Copyright (c) 2015-2016, Marcus Wittig All rights reserved.

GPL-2.0

pimatic-solarview's People

Contributors

greenkeeperio-bot avatar mwittig avatar

Watchers

 avatar  avatar

pimatic-solarview's Issues

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
  • The new Node.js version is in-range for the engines in 1 of your package.json files, so that was left alone

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 🌴

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.