Replies: 2 comments
-
Same here, quite annoying. Best wishes, |
Beta Was this translation helpful? Give feedback.
0 replies
-
See also: #542 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi *,
This morning I was some kind of wondering why the Growatt does not have any Voltage on PV in my monitoring. So system was working normal and also the ShinePhone or web based server.growatt.com show everything running fine.
Just found out after looking at my second Growatt, where I blocked all commands cause not necessary, that Growatt sends a command since this morning and got blocked: "Grott: Record blocked: 0118".
So my 1st Growatt - not blocked - was forced since received the command 0118 to send metrics to Growatt directly and no longer through grott. I was able to set the local grott IP back in the WebUI, but that works only for some minutes and again the command 0118 set the offical IP. Now grott is configured to block all commands and everything is working again. Monitoring an Metrics are produced.
Anybody else seen this behavior?
And I got a question: I have two parameters in the config file:
blockcmd = True
#noipf = True
Is it possible to block ONLY changing the IP from outside like that:
blockcmd = False
noipf = False
So allowing change of parameters except of changing the IP address. That would re-enable configure stuff from the ShinePhone App without getting cut off to my internal network again.
Regards
Björn
Beta Was this translation helpful? Give feedback.
All reactions