Need some help, suddenly sensor unavailable

[thoompje]

Hello All,

I am using for a long time now the integration (add-on) but suddenly my sensors getting unavailable. What can cause this issue? First it was just a few times and after a restart of home assistant it was working again, but now I can't get it working again. See screenshots,

I restarted the inverter also to check if that helped with the issue, but no succes. So hopefully someone can help with the troubleshoot. Many thanks in advance!

[muppet3000]

There have been a lot of comments on #85 today suggesting that people's wifi sticks got a factory reset overnight.
Perhaps the same has happened for you and you need to reconfigure the IP for it to point at Grott?

[mjooris]

mine stopped working to. thx @muppet3000 for the reply. i am going to check this.

[thoompje]

There have been a lot of comments on #85 today suggesting that people's wifi sticks got a factory reset overnight.
Perhaps the same has happened for you and you need to reconfigure the IP for it to point at Grott?

Hi, many thanks for the answer en the link to the different threat. It's strange because sometimes it's getting back... But if I configure it now, will it automatically reset again then overnight? Because the inverter is on a difficult place to visit 😅 Or can I configure this on growat.com?

[muppet3000]

I believe that's what's being discussed over on the other thread.
The only way to guarantee that great won't push config to your Wi-Fi stick/dongle is to block incoming traffic from the growatt servers, but then you're unable to push configuration yourself.

A while back I cut out Growatt completely and started using grottserver instead, but I haven't got round to writing a nice python library and HA integration for it yet in order to be able to push config

[thoompje]

I believe that's what's being discussed over on the other thread. The only way to guarantee that great won't push config to your Wi-Fi stick/dongle is to block incoming traffic from the growatt servers, but then you're unable to push configuration yourself.

A while back I cut out Growatt completely and started using grottserver instead, but I haven't got round to writing a nice python library and HA integration for it yet in order to be able to push config

Many thanks again for the answer. If I change the IP on the growat site as before then its all working again... Not happy with them that they change it back to factory. Somebody already contacted the developers or product team?

[mjooris]

Growatt does not want us to do these things, so no use in contacting them.. they'll do anything to keep us from doing this sh*t
with me it is working by changing the server.growatt.com back to my grott ip address. but i did notice, when i take the power out of my shine link, the settings go back to growatt.com. thankfully i'm running a pihole dns server in my home so i guess i'll just make a static DNS entry in my dns server that makes server.growatt.com resolve to my internal grott ip address.

[87Vortex87]

Got the exact same problem today. Really annoying. These are my settings, not for them to be tampering with, but what can we do right. The date you're using, is that de password we need to fill in? My normal growatt password doesn't seem to work, but get no errors if i use today's date? Weird...

Solved using this method, now to block inbound traffic to the wifi dongle.

[MSavisoft]

I also had this same problem this morning at about 8am. Bloody annoying.

I can see from my PiHole logs that the only DSN lookup the DataLogger made since I got it all working with HA and Grott in March was a CNAME lookup this morning for server.growatt.com at 07:43 ... which is probably the cause of the problem.

NsLookup of server.growatt.com shows...
Name: nlb-nbtf7vlspietfgd3ro.eu-central-1.nlb.aliyuncs.com
Addresses: 47.254.130.145, 8.209.71.240
Aliases: server.growatt.com

Tomorrow I will try and decipher the info on this thread and the other and try and set it back.
My best option may be to get PiHole to change the lookup.

[daath]

Mine did the same at around 7 am UTC (9 CEST) - was confused until later in the evening, when I decided to input the IP of the Grott instance. It gets data one time and then it stops working again?!

[thoompje]

I just created an A record in my DNS server.

A Record: server.growatt.com
IP: x.x.x.x (Internal IP of Home Assistant / Grot).

Now it looks like its working again, lets wait for a few hours to see if it is really working. It's a really ugly solution because there will be no data in the shine phone app. But if this works it works.. Lets wait and see.

[87Vortex87]

Update. Looks like the sensors agaim aren't working. I'll try to put the IP adres of HA in the dongle again and monitor. I hope they aren't resetting the dongle daily.

[87Vortex87]

I just created an A record in my DNS server.

A Record: server.growatt.com IP: x.x.x.x (Internal IP of Home Assistant / Grot).

Now it looks like its working again, lets wait for a few hours to see if it is really working. It's a really ugly solution because there will be no data in the shine phone app. But if this works it works.. Lets wait and see.

This may be the solution if it turns out they reset the dongle daily.

[87Vortex87]

Ok, update again: turns out i had to put in the IP adressen of HA again as endpoint in the wifi stick/dongle. Looks like they're sabotaging the configuration. It's called CONFIGURATION, I want control over that. This is the last Growatt product i ever bought.

[87Vortex87]

Growatt does not want us to do these things, so no use in contacting them.. they'll do anything to keep us from doing this sh*t
with me it is working by changing the server.growatt.com back to my grott ip address. but i did notice, when i take the power out of my shine link, the settings go back to growatt.com. thankfully i'm running a pihole dns server in my home so i guess i'll just make a static DNS entry in my dns server that makes server.growatt.com resolve to my internal grott ip address.

I have Pihole as well, I'll keep this solution in my back pocket if they decide to do this on a regular basis. I need the converter data in HA because my lights are controlled using the solar panel prodction as a sensor to determine is it's dark enough to turn on the lights in the house when presence is detected.

[thoompje]

I also tried to block incoming internet traffic to it and outgoing as well, but it is still resetting. I don't know if they pushed a script on it with some firmware or so which reset the device every few minutes. But the dirty solution I have now with the DNS manipulation is working fine, data is still getting into Home Assistant.

[szemod]

The dongle is not reset every day, but every 5 minutes! It can only be solved by rewriting DNA.

[87Vortex87]

I've made a complaint at the Dutch ACM, which is a government agency which is involved with protection consumer right. Most likely nothing will happen, and if something happens it will take years, but better than nothing.

[mjooris]

it was working yesterday but it was only for a while.

the stupid thing does not let me change the dns server. it always goes back to 8.8.8.8 this is so frustrating. how did you do the dns manipulation if you cannot change the dns server to your internal dns?

[87Vortex87]

The dongle is not reset every day, but every 5 minutes! It can only be solved by rewriting DNA.

Can you explain? what do you mean by rewriting DNA?

[87Vortex87]

Growatt does not want us to do these things, so no use in contacting them.. they'll do anything to keep us from doing this sh*t
with me it is working by changing the server.growatt.com back to my grott ip address. but i did notice, when i take the power out of my shine link, the settings go back to growatt.com. thankfully i'm running a pihole dns server in my home so i guess i'll just make a static DNS entry in my dns server that makes server.growatt.com resolve to my internal grott ip address.

I have Pihole as well, I'll keep this solution in my back pocket if they decide to do this on a regular basis. I need the converter data in HA because my lights are controlled using the solar panel prodction as a sensor to determine is it's dark enough to turn on the lights in the house when presence is detected.

Now that i'm thinking about it, we probably also need to block all incoming traffic to the wifi dongle, because if they push new settings where they decide their endpoint changes, from server.growatt.com to something else, that pihole rule won't work that long. So, probably:

1. change setting of the wifi stick or intercept traffic and reroute using Pihole for example;
2. block all incoming traffic to the IP-adress of the Wifi stick.

[szemod]

Of course. The Domain Name Address is written back to server.growatt.com every 5 minutes, so it must be rewritten elsewhere. The DNS address of the dongle must be changed to an internal DNS server (Adguard in my case), where server.growatt.com must be redirected to the address that was previously set in the dongle.

[mjooris]

Of course. The Domain Name Address is written back to server.growatt.com every 5 minutes, so it must be rewritten elsewhere. The DNS address of the dongle must be changed to an internal DNS server (Adguard in my case), where server.growatt.com must be redirected to the address that was previously set in the dongle.

can you change the dns server? i cannot. whenever i change the dns server, hit save. it always goes back to 8.8.8.8 :(

[thoompje]

You can rewrite 8.8.8.8 in your network pointing to your own dns server 😄 But that's more dirty then the solution before. I think my shine x dongle just use my own DNS server, because after changing A record on my own DNS server its working like a charm.

[mjooris]

yeah dont really want to do that... it will break other things.... i just found online documentation for a API. i did not know they had one. @muppet3000 https://growatt.pl/wp-content/uploads/2020/01/Growatt-Server-API-Guide.pdf did you already take a look at this? i prefer to keep my data local but, if they have an api that works. is the second best thing i guess..

[muppet3000]

Has anyone tried setting these values in the grott.ini file?

# To blocks commands from outside (to channge inverter and shine devices settings) specify blockcmd = True,
# specify noipf = True if you still want be able to dest ip addres from growatt server
# Specify noipf = True if you still want be able to dest ip addres from growatt server (advice only to use
# this for a short time)
#blockcmd = True
#noipf = True

I'm using grottserver so nothing is going to Growatt at all.

If you don't block incoming requests from growatt then regardless of what DNS etc. you're using they will still be able to push config to your dongle. The downside of blocking this though is that you also can't configure SoC & AC charge etc. from the website yourself, you'd have to temporarily change the setting to 'False' in order to allow pushing of configuration that you actually want.

[thoompje]

yeah dont really want to do that... it will break other things.... i just found online documentation for a API. i did not know they had one. @muppet3000 https://growatt.pl/wp-content/uploads/2020/01/Growatt-Server-API-Guide.pdf did you already take a look at this? i prefer to keep my data local but, if they have an api that works. is the second best thing i guess..

I know you don't want that, but man what a sh*t hole is this with Growat.

[dg362]

Like many, I need to maintain the Growatt server, plus the ability to use web interface (or App) to configure SoC or adjust the timing of Battery Charge, etc. This is because the tariff I am on needs to be managed when I'm charging my EV otherwise the battery will drain. Whilst I could consider grott-server that would lose the entire Growatt web and App interface and I'm not confident I can reproduce all the data points in HA the way I want.

My ShineWIFI-S reset this morning too. This was around 08:10 which is a little later than it was yesterday which was 07:45.

Growatt is making some changes as the web interface has had a few updates in terms of things like Battery now showing as Charging and Discharging on the main Energy Trend graph (but only on the Hour view, not the summarised Day/Month/Year views as that shows as Battery). They've also made the dialog page for the data logger bigger. I'm sure there are other updates as well.

I'm in the UK, and stating this in case the reset of the data logger is different between regions.

I have been trying to set up Notification automation in Home Assistant to notify me if the value of Solar Generation doesn't change for say 10 minutes. I've not yet gotten that to work because I'm confused between last_updated, last_changed, and last_reported as the states and how that affects the actual value of the sensor. This would at least allow a notification that between sunrise and sunset if the generation doesn't change the value for say 10 minutes then it is likely the data logger has been reset again.

[87Vortex87]

Ok, yea, it has changed again after a few hours, they keep pushing the settings to the stick. This is becoming an ugly fight with Growatt. I think the only option is to block incoming traffic to the stick after changing the endpoint on the stick.

Edit: i've re-entered the IP i want into the stick and blocked all incoming traffic to the IP adres of the stick in my router. Let's see if this works.

[Ryanmt2]

Not sure if its related but I am unable to access the web ui of my stick in any fashion now. not when it was connected to my wifi but I also hard reset it and when connecting via the hotspot I cant access http://192.168.10.100 either. Are you guys having any similar issues accessing the sticks config web ui?

[87Vortex87]

Not sure if its related but I am unable to access the web ui of my stick in any fashion now. not when it was connected to my wifi but I also hard reset it and when connecting via the hotspot I cant access http://192.168.10.100 either. Are you guys having any similar issues accessing the sticks config web ui?

Yes, i have issues reaching the local web-ui of the stick as well, straight from the LAN to the stick. I can only push settings through server.growatt.com, where in the past i was able to reach the web-ui locally. But maybe i'm doing something wrong...

[Mappenhei]

I'm failing with different methods.
Before, I was using that integration for a long time without any issues.

My first try was to change the DNS record, which was possible. The logger was forwarded to my home assistant instance and Growatt server stated that the logger disappeared. So far so good. But after some minutes, the device in MQTT is again unavailable, even though the logger is still pointing to home assistant and growatt says "not connected". When I restart MQTT the device appears but disappears again after some minutes.

Second I disabled the DNS record, changed the IP in the logger through the portal. After the device appeared in home assistant, I added this to my grott.ini
blockcmd = True
noipf = False
After some minutes, the device disappears from home assistant. But the IP is still present in the logger settings. And when I restart MQTT the device appears.

In order to provide a full picture and avoid misconfiguration, I list my setup in home assistant:
(to be honest, since all that changes, the configuration process is even more cumbersome)

1. MQTT and Grott are installed
2. pointed from logger to home assistant
3. device is appering in MQTT

4. grott is configurated but doesn't show any device

5. grott.ini
   blockcmd = True noipf = False

Any ideas?

[dg362]

Remember that Grott is itself another component, whereas this repo is for the HA element.

Looking at the main Grott repo on GitHub, two referenced issues may be helpful for people to read through if they're still having issues. They are stating the same as here but with more rationale on why this issue occurs in the first place.

johanmeijer/grott#563
and
johanmeijer/grott#567

Based on the detail within those issues, it looks like if you connect to the old IP address this forces Growatt to send the new IP address to the data logger.

So the change in grott.ini to specify the IP address plus enable the blockcmd option should be the fix after changing the IP on the data logger to point to the local IP of Grott and a restart of Grott fully (e.g. restart the Docker container for Grott if you're using that or the Grott service, as just a restart of Home Assistant will not be enough).

[daath]

Am I understanding this correctly? If we somehow change the growattip from 47.91.67.66 to the new IP 8.209.71.240 - in grott_ha then we should be able to specify our local grott-ip on the datalogger and blockcmd should not be necessary? I rather like being able to change settings ;P

Is this the one to change in the UI?

[larrybml]

I've managed to fix the problem by only adding a DNS record with server.growatt.com in my router, and pointed Shine to my router DNS, witch will redirect it to my local HA IP. Everything works like before , even web monitoring is working on growatt servers.

[dg362]

Am I understanding this correctly? If we somehow change the growattip from 47.91.67.66 to the new IP 8.209.71.240 - in grott_ha then we should be able to specify our local grott-ip on the datalogger and blockcmd should not be necessary? I rather like being able to change settings ;P

That is what is suggested as the reason why the data logger was getting overridden.

It could also explain why this wasn't consistent because the DNS record for server.growatt.com is a CNAME with two equal priority results. Meaning it would randomly pick either address when you do a DNS lookup or when DNS cache expires. If it picked the 'wrong' one then it would update your data logger with the new IP address. It's worth stating the TTL for the DNS entry is low at 60 seconds so this could happen quite quickly.

; <<>> DiG 9.18.24-1-Debian <<>> server.growatt.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 18904
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;server.growatt.com.		IN	A

;; ANSWER SECTION:
server.growatt.com.	50	IN	CNAME	nlb-nbtf7vlspietfgd3ro.eu-central-1.nlb.aliyuncs.com.
nlb-nbtf7vlspietfgd3ro.eu-central-1.nlb.aliyuncs.com. 50 IN A 8.209.71.240
nlb-nbtf7vlspietfgd3ro.eu-central-1.nlb.aliyuncs.com. 50 IN A 47.254.130.145

;; Query time: 4 msec
;; SERVER: 1.1.1.1#53(1.1.1.1) (UDP)
;; WHEN: Thu Jul 18 08:46:45 BST 2024
;; MSG SIZE  rcvd: 142

In terms of the blockcmd I am not personally convinced that code is fully working, at least for me using HACS with Grott and grott_ha. My grott.ini was changed to blockcmd=true and the Grott Docker container restarted and yet I am still able to go in and set the schedules or adjust AC or battery etc on the inverter.

In theory just setting the IP should be sufficient to stop Growatt updating the address in the data logger. But across the posts from the last couple of days that isn't necessarily the case although timing of changes could be relevant.

[thoompje]

I've managed to fix the problem by only adding a DNS record with server.growatt.com in my router, and pointed Shine to my router DNS, witch will redirect it to my local HA IP. Everything works like before , even web monitoring is working on growatt servers.

Same here, not that happy that my data is also going to the growatt servers, but well its working now again.

[Green-M3rcury]

Am I understanding this correctly? If we somehow change the growattip from 47.91.67.66 to the new IP 8.209.71.240 - in grott_ha then we should be able to specify our local grott-ip on the datalogger and blockcmd should not be necessary? I rather like being able to change settings ;P

Is this the one to change in the UI?

This worked for me. But instead of the IP I used the serverdns: server.growatt.com (for Netherlands in my case).

Also, I have enabled gblockcmd. For the time being it works.

[Pierre331]

Adding those two lines in the grott.ini
ip = 8.209.71.240
port = 5279
then restarting HA and then pushing your HA ip into the Growatt web interface seems to do the trick.
Thank you all :)

[mjooris]

i created a ticket with the notification that my shinelink box resets to default settings every few minuts. this is the reply i am getting.
he cannot update my device (because i block it with blockcmd = True
noipf = False
so no i dont know what to do. let it like this now it is working. or let him update the firmware and see if it acts differently... suggestions? @muppet3000

[muppet3000]

Maybe just get him to send you the firmware and you can update it yourself?
No ideas other than that.

[thoompje]

i created a ticket with the notification that my shinelink box resets to default settings every few minuts. this is the reply i am getting.

he cannot update my device (because i block it with blockcmd = True

noipf = False

so no i dont know what to do. let it like this now it is working. or let him update the firmware and see if it acts differently... suggestions? @muppet3000

• Permit FTP for what? An firmware upgrade indeed? I really don't understand what the developers are doing at Growatt. They f*cked the whole thing up, and what Chris is saying, ask for a firmware fix. If they have it, that would be awesome! Don't think they have and would share but we can try at least.

[ChimorinNL]

I've managed to fix the problem by only adding a DNS record with server.growatt.com in my router, and pointed Shine to my router DNS, witch will redirect it to my local HA IP. Everything works like before , even web monitoring is working on growatt servers.

Could you maybe give some more information on how you set this up? Also what router do you use?

[daath]

Update: A few hours ago, I modified my grott_ha as I described above - I went to configuration, unused settings, then set growattip to 8.209.71.240 then deactivated blockcmd - and restarted the add-on - it still works in HA and now I can adjust settings on server.growatt.com again :) So now it seems I am "back to normal" again! :)

#91 (comment)

[larrybml]

I've managed to fix the problem by only adding a DNS record with server.growatt.com in my router, and pointed Shine to my router DNS, witch will redirect it to my local HA IP. Everything works like before , even web monitoring is working on growatt servers.

Could you maybe give some more information on how you set this up? Also what router do you use?

I'm using an Mikrotik router for internet connection.
Just added an A record in statis DNS of router , that points server.growatt.com to my local HP IP , and in my Shine Lan adapter, just set DNS address to my router IP.

[henkedejong]

In my Zyxel router I added a DNS-item with server.growatt.com pointing to my LAN address of the HA/Grott server. When I did a ping to server.growatt.com I got the internal HA/Grott LAN adress. Yesterday it started working again, and also this morning the Growatt converters delivered their data to the HA/Grott server and server.growatt.com. Don't forget to use the internet address 47.91.67.66 instead of server.growatt.com to contact the Growatt website.

[ronaltibruno]

Hello, has anyone using a mikrotik or Pi-hole router been able to "fix" the problem? If anyone can inform and show the steps it would be of great help. Thank you and sorry for the translator's English.

[larrybml]

Just added an A record in statis DNS of router , that points server.growatt.com to my local HP IP , and in my Shine Lan adapter, just set DNS address to my router IP.

Just added an A record in statis DNS of router , that points server.growatt.com to your local HA IP , and in Shine adapter, just set DNS address to your router IP.

[beped]

Growatt does not want us to do these things, so no use in contacting them.. they'll do anything to keep us from doing this sh*t
with me it is working by changing the server.growatt.com back to my grott ip address. but i did notice, when i take the power out of my shine link, the settings go back to growatt.com. thankfully i'm running a pihole dns server in my home so i guess i'll just make a static DNS entry in my dns server that makes server.growatt.com resolve to my internal grott ip address.

I have Pihole as well, I'll keep this solution in my back pocket if they decide to do this on a regular basis. I need the converter data in HA because my lights are controlled using the solar panel prodction as a sensor to determine is it's dark enough to turn on the lights in the house when presence is detected.

I also have a pihole here, can you help me configure that? Where in the pihole i need to put this settings?

[beped]

Found:

[ronaltibruno]

Encontrado:

Does this way work for you? It didn't work for me.

[mjooris]

Hi everyone.
i have created a ticket for Growatt and they did a firmware update on my shinelink (i asked for the file to do it myself but we are not able to upgrade it ourselves he told me).
also confirmation that these commands work:
blockcmd = True
noipf = False

because he was not able to do the update. (i was asked to allow ftp traffic) but i changed the blockcmd to false and he was able to preform the update.

Now the firmware is updated. i have changed the server ip to my internal grott instance. did a power cycle of the shine link. it has been more then 15 hours now and still working fine.
it appears the update solves our problem.

i did not change the blockcmd back to true afterwards.

i am from BE and was mailing with service.nl@ginverter.com

hope this helps some of you!

[thoompje]

Hi everyone. i have created a ticket for Growatt and they did a firmware update on my shinelink (i asked for the file to do it myself but we are not able to upgrade it ourselves he told me). also confirmation that these commands work: blockcmd = True noipf = False

because he was not able to do the update. (i was asked to allow ftp traffic) but i changed the blockcmd to false and he was able to preform the update.

Now the firmware is updated. i have changed the server ip to my internal grott instance. did a power cycle of the shine link. it has been more then 15 hours now and still working fine. it appears the update solves our problem.

i did not change the blockcmd back to true afterwards.

i am from BE and was mailing with service.nl@ginverter.com

hope this helps some of you!

That is really good news, but I am surprised why they not pushing it already to all the devices... Somehow we need to sniff the firmware if someone got the update so we can apply it our selfs. Many thanks for the comment!

[larrybml]

Someone has Shine X LAN? and cand share what firmware it has?

[mjooris]

Hi everyone. i have created a ticket for Growatt and they did a firmware update on my shinelink (i asked for the file to do it myself but we are not able to upgrade it ourselves he told me). also confirmation that these commands work: blockcmd = True noipf = False
because he was not able to do the update. (i was asked to allow ftp traffic) but i changed the blockcmd to false and he was able to preform the update.
Now the firmware is updated. i have changed the server ip to my internal grott instance. did a power cycle of the shine link. it has been more then 15 hours now and still working fine. it appears the update solves our problem.
i did not change the blockcmd back to true afterwards.
i am from BE and was mailing with service.nl@ginverter.com
hope this helps some of you!

That is really good news, but I am surprised why they not pushing it already to all the devices... Somehow we need to sniff the firmware if someone got the update so we can apply it our selfs. Many thanks for the comment!

I guess it is a bit: if it is working, don't touch it...

ha also wanted to update the inverter firmware while he was at it. but he saw i had a battery connected that is not supported anymore.
i have pylontech batteries. when i bought this setup, this was supported. now Growatt has their own batteries and dont support pylontech anymore. So if he was to update my inverter firmware, there was a possibility the communication between my inverter and batteries is not going to work anymore.
So with that in mind. i understand they do not just push all updates automatically.

however. our issues started all around the same time so i they had to do something to break everything... no idea what they are doing at growatt but i'm not liking it.
i also have a Goodwe inverter. it integrates into HA without any issues. works for years. not ever 1 problem!
so, if i ever need to replace my growatt inverter. it will NOT be a growatt again, i will probably take a goodwe again since that always just works!

success to you all!

[luc684]

Hi all,

Looks like Growatt is changing it's IP for the upload off the data from your inverter.
Grott also failed in my setup, but after changing the forward IP in the grott config all works again.
Config option= ggrowattip and I am using 8.209.71.240 now.

So probably you get a new setup pushed if you use the old (hardcoded) forward IP for your growatt data.
And then your information will go directly to server.growatt.com instead of your local grott IP.

This works for me, so hopefully it will keep working for some time again.

[gaustabl]

Hello. I am trying to fix this problem, but cannot find the grott config anywhere.this is my grott version;


Pls help.) best regards Lars

[typxxi]

I am running a growatt inverter farm of 8 inverter from 3 different (min, mic and sph) like mic 600 / 2000 / 3000 and min 4600 and sph 4600.

I have struggled a lot in the past days cause I was not aware about these changes while I had been working on the farm setup, got a new second AC distribution box, new LAN and also WLAN repeaters and a complete new AC wiring for the inverters.

And after all of that nothing had been working as before so I had to look for the error and thought the power outage for a few days had killed the settings in the sticks which seemed to be true but in the evening I had the issues again.

SOLUTION:

#1
I have opened grott in HA and opened the advanced and unused settings among which you can find the switch
gblockcmd which I used first but blocked me from changing any sph inverter settings like charging plans and so on.

I have then added the ip 8.209.71.240 in ggrowattip

#2
Finally I changed the wifi stick IP again to my local grott server (ha running grott as addon)

Now it seems that mqtt is delivering the data again to the HA grott integration aka sensor, my 400 sensors !
And I can still edit and change SPH inverter settings via APP and browser.

Hats off
for all those who had been working on that solution which can be done easily if you simply know the steps.

Now my string plan shows the current production per String
Watt / String
Watt / kWp installed for each string
kWh / String
kWh / kWp installed for each string
Just an excerpt of over 15 strings in total

MISSING FIGURES are caused by an ongoing maintenance where we are replacing DC cables after a marder / marten attack.

[thompy93]

I am running a growatt inverter farm of 8 inverter from 3 different (min, mic and sph) like mic 600 / 2000 / 3000 and min 4600 and sph 4600.

I have struggled a lot in the past days cause I was not aware about these changes while I had been working on the farm setup, got a new second AC distribution box, new LAN and also WLAN repeaters and a complete new AC wiring for the inverters.

And after all of that nothing had been working as before so I had to look for the error and thought the power outage for a few days had killed the settings in the sticks which seemed to be true but in the evening I had the issues again.

SOLUTION:

#1 I have opened grott in HA and opened the advanced and unused settings among which you can find the switch gblockcmd which I used first but blocked me from changing any sph inverter settings like charging plans and so on.

I have then added the ip 8.209.71.240 in ggrowattip

#2 Finally I changed the wifi stick IP again to my local grott server (ha running grott as addon)

Now it seems that mqtt is delivering the data again to the HA grott integration aka sensor, my 400 sensors ! And I can still edit and change SPH inverter settings via APP and browser.

Hats off for all those who had been working on that solution which can be done easily if you simply know the steps.

Now my string plan shows the current production per String Watt / String Watt / kWp installed for each string kWh / String kWh / kWp installed for each string Just an excerpt of over 15 strings in total

MISSING FIGURES are caused by an ongoing maintenance where we are replacing DC cables after a marder / marten attack.

This should be marked as solution. Quick fix that seems to be working for now.