-
|
Some weeks ago I changed the settings in grott.ini to run the application from proxy to server. So no communication with the internet. I had in mind that the application runs oke. I got data in Domoticz and uploads to PVoutput.org. But for some unknown reason the application stopped running... The situation: The settings of the ini-file (some parts wiped because of privacy): It seems to me that the dongle (ShineWifi-X) on the inverter did not send any data. Settings of this dongle: The led on the dongle flashes blue. So I think there is connection with Grott. Part from the log: I do not read errors for output to MQTT, PVoutput.org for example. There is one error: Any help is appreciated. Thanks in advance Pieter |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 3 replies
-
|
Addition: Pretty sure there is communication between dongle and the applition in Docker: So I think that dongle and Grott Server in Docker are on speaking terms... |
Beta Was this translation helpful? Give feedback.
-
|
Did a clean install of Grott (Proxy) version 2.7.8 on a Raspberry Pi 4 and changed the networksettings on te ShineLan-X to the IP of the RPI and port 5279. And there it goes!!! As second test I changed in grott.ini in section Growatt the IP-setting to local ip and port to 5279 In the CommandLineInterface of the Pi I read this message: Grott proxy mode started Is that number 1026 a portnumber? If so that port is not opened in the container of Docker and could be a cause of malfunction. Can someone confirm? |
Beta Was this translation helpful? Give feedback.
-
|
Oops you created a network loop ;) (Grott is listen to port 5781 and writes to port 5781. Your datalogger is writing to 5279 and nothing is listening to that port I think. The grottserver docker container runs both grott and grottserver. A picture:
Do not change Grott basic ip settings (Listen + port). Grott will still listen at port 5279 and de IP address of the host (in your case the synology). But not specifying or changing this is ok! What you have to do is change the address of the growatt server where grott is sending it's data. So normally it is the growatt server. In this case it should be grottserver running in the the docker container. In default grott.ini for the grottserver I specified: |
![https://i.ibb.co/BgYHKfS/Growatt-Shine-Lan-X.jpg[/img][/url]](https://i.ibb.co/BgYHKfS/Growatt-Shine-Lan-X.jpg%5B/img%5D%5B/url%5D){kind=link}
Beta Was this translation helpful? Give feedback.
-
|
@johanmeijer : Thnx for your reply! So I disabled IP and Port in the Generic section and configured the Growatt section as stated in your reply here above. That was the trick. At this moment everything works oke! Many thanks. I will make a suggestion in the other discussion to improve the explanation in the grott.ini at these sections and their relation according to their functionality. Maybe better naming could prevent this? Or deliver 2 different versions of grott.ini? One for Grott proxy and Grott Server? |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
@ZonPV do you use the same ini file for both proxy and server? |
Beta Was this translation helpful? Give feedback.
-
|
@anoppe Sorry, I deleted the reply to Johan before I saw your message. As I wrote to him that there was still a conflict in ports.... Thnx for your attention and reply anyway. |
Beta Was this translation helpful? Give feedback.
@johanmeijer : Thnx for your reply!
Later on this morning I realised that errormessage about the "port is in use" is my mistake in the ini-file. The Generic section is for the Proxy-configuration. The Growatt section is for the configuration of my own Grott server!!
So I disabled IP and Port in the Generic section and configured the Growatt section as stated in your reply here above.
That was the trick.
At this moment everything works oke! Many thanks.
And again: Very happy with this application and solution to run my own Growattserver!
I will make a suggestion in the other discussion to improve the explanation in the grott.ini at these sections and their relation according to their funct…