-
Notifications
You must be signed in to change notification settings - Fork 109
Home
This file is deleted from the grott default directory to simply github installation (not overwrite your settings). It is advised to copy this file into the Grott default directory (and customise it) during first time installation
Introduce possibility to add extensions for additional (personalized) processing.
see: https://github.com/johanmeijer/grott/wiki/Extensions
Direct output to inlfuxdb (v1 and v2)
see: https://github.com/johanmeijer/grott/wiki/InfluxDB-Support
Mulitiple inverter (multiple system id's) support in PVOutput.org
see: https://github.com/johanmeijer/grott/wiki/PVOutput.org-support
Limited .ini configuration needed (inverterid, encryption, offset and record layout is automaticially detected)
Specify pvoutput = True and apikey and systemid in .ini file to enable it.
2 docker containers are created ledidobe/grottrpi (specific old RPI with ARM32) and ledidobe/grott (generic one, tested on synology NAS and Ubuntu). See https://hub.docker.com/search?q=ledidobe&type=image. See issue 4 and 15 on how to use it (wiki will be updated soon)
with blockcmd = True specified in .ini (configure/reboot) commands from outside to the inverter are blocked. This protects the inverter from beeing controlled from the outside while data exchange with server.growatt.com for reporting is still active.
If date/time is available in the data (inserted by the inverter) this will be used. In this way buffered records will be sent with the original creation time (in the past). If date/time is not available in the data record the server time will be used (as it was originally). In the mqtt message the key buffered is added (yes/no) which indicates that the message is from the buffer (past) or actual.
The growatt inverter with Shine wifi adapter sends log data to the growatt website at the internet. At this website you can see detailed information on how the inverter is performing.
I was looking for a way to intercept this information and use it within my home domotica environment.
Searching at the internet I find some sites where people managed to intercept the data and send this information to the pvoutput website. See:
https://github.com/sciurius/Growatt-WiFi-Tools
http://123zonne-energie.ning.com/profiles/blogs/growatt-wifi-module-via-raspberry-pi-automatische-upload-naar (link not available anymore)
Inspired by this solutions, I decided that I want a more generic solution. So I used the ideas and created an own solution based on routing the data via a Raspberry Pi (or any other Linux device) and process the Growatt log data with a python program that sends a JSON message with status information to a MQTT broker (eg MOSQUITTO).
MQTT can be used to distribute the data to the applications who need it (eg node red, home assistant, domoticz).
I use node red to consume the MQTT data, create dashboards and sent it to other receivers like PVoutput or Domoticz. Node red can also enable the use of other tooling like influxDB/Grafana to capature and analyse the data.
Grott (version 2+) has to modes: sniff and proxy.
In sniff mode (default and compatable with older Grott versions) IP sniffering technology is used (based on: https://github.com/buckyroberts/Python-Packet-Sniffer). In this mode the data needs to be "re-routed" using linux IP forwarding on the device Grott is running. In this mode Grott "sees" every IP package and when a Growatt TCP packages passes it will be processed and a MQTT will be sent if inverter status information is detected.
With the new proxy mode Grott is listening on a IP port (default 5279), processes the data (sent MQTT message) and routes the original packet to the growatt website.
The new mode functionality can be enabled by:
- mode = proxy in the conf.ini file
- -m proxy parameter during startup
sniff mode
+ Data will also be routed to the growatt server if Grott is not active
- All TCP packages (also not growatt) need to be processed by Grott.
This is more resource (processor) intesive and can have a negative impact on the device performance.
- Configure IP forwarding can be complex if a lot of other network routing is configured (e.g. by Docker).
- Sudo rights necessary to allow network sniffering
proxy mode:
+ Simple configuration
+ Only Growatt IP records are being analysed and processed by Grott
+ Less resource intensive
+ No sudo rights needed
+ Blocking / Filtering of commands from the outside is possible
- If Grott is not running no data will be sent to the Growatt server
The program is written in python and can be started from the command line or linux services. In sniff mode it is necessary to run Grott with SUDO rights.
Docker images are also available to run Grott in a docker conatiner. See the wike page on docker for more information.
Copy grott.service in /etc/systemd/system directory for running grott as a deamon (see wiki how to use services for both Linux and Windows)
Be aware the assumption is that Grott is installed in /home/pi/growatt.
grott.service Needs to be modified if an other directory is used.
The following modules are needed the use Grott:
- grott.py
- grott.ini
- grottconf.py
- grottdata.py
- grottproxy.py
- grottsniffer.py
The Grott monitor is tested on Raspian (Raspberry PI), ubuntu and windows 10 (proxy only) , with
- 1000-S (ShineWiFi)
- 1500-S (ShineWiFi)
- 3000-S (Shinelan)
- 2500-MTL-S (ShineWiFi)
- 4200-MTL-S (Shinelan)
- 5000TL-X (ShineWifi-X)
- 3600TL-XE (ShineLink-X)
- 3600TL-XE (ShineLan)
Docker is tested with RPI(arm32), Ubuntu and Synology NAS