Replies: 4 comments 6 replies
-
Anything further will require you to use custom firmware for your ShineWifi stick. |
Beta Was this translation helpful? Give feedback.
-
@bjkiting can we close this one? |
Beta Was this translation helpful? Give feedback.
-
@johanmeijer @bjkiting |
Beta Was this translation helpful? Give feedback.
-
Be aware if you do not use grottserver changing the interval time might give strange values while the Growatt server does not really like short intervals (lower then 5 minutes). They have to serve a lot of inverters sending the data. This will produce a lot more of data they have to process. |
Beta Was this translation helpful? Give feedback.
-
Hi All
Firstly thanks to all the devs that contributed to this great project!
I recently managed to get everything up and running, I have grott running in a docker container which is communicating with MQTT broker on my Home Assistant.
One of the first things I tested was comparing the minute interval data set to that of the Growat API (obtained using the HA Growatt cloud API integration). This data has 10 min intervals. It is very interesting to see how it is not averaged values but appears to be instantaneous values at the start of each interval, rather than the more accurate average of the entire time frame.
Having this increased to minute intervals is already a massive improvement, as can be seen in the image below.
Since then I tried to increase it even further by setting the update interval to 0.1 minutes on the ShineWifi-F router settings. This lead to an increased number of logs that looks like the following:
- Growatt packet received: <socket.socket fd=5, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=0, laddr=('172.18.0.2', 5279), raddr=('192.168.1.20', 3840)> - Data less then minimum record length, data not processed
Is it possible to change any parameters such that the updating interval can be further increases?
Beta Was this translation helpful? Give feedback.
All reactions