Shinewifi-x problem - URL resetting to default - data not flowing through GROTT #542

J4CE2 · 2024-03-28T23:58:23Z

This is possibly not a GROTT issue. But I need help and there's no other place really.

As of yesterday it appears my shinewifi-x dongle keeps resetting back to the default growatt server URL and not utilising the custom IP address I had entered... thus bypassing the GROTT local server I have setup.

I've tried re-updating the dongle via the Growatt website, it works once and then stops. I've tried doing it via AP hot spot, I can see it has reset to default value, again it works once and then stops.

Any one had anything similar??

J4CE2 · 2024-03-29T00:16:27Z

Actually I noticed something new in the GROTT Logs after the message is received. It tells me my dongle IP has disconnected. This never used to happen from what I can tell in the logs.

ar 29 08:10:35 rpi-monitor grott[1162]: - Grott MQTT topic used : energy/growatt
Mar 29 08:10:36 rpi-monitor grott[1162]: - MQTT message message sent
Mar 29 08:10:36 rpi-monitor grott[1162]: - Grott Send data to PVOutput disabled
Mar 29 08:10:36 rpi-monitor grott[1162]: - Grott Send data to Influx disabled
Mar 29 08:10:36 rpi-monitor grott[1162]: - Grott extension processing disabled
Mar 29 08:10:36 rpi-monitor grott[1162]: - Growatt packet received:
Mar 29 08:10:36 rpi-monitor grott[1162]: <socket.socket fd=7, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=0, la
Mar 29 08:10:36 rpi-monitor grott[1162]: - Data less then minimum record length, data not processed
Mar 29 08:10:36 rpi-monitor grott[1162]: - Growatt packet received:
Mar 29 08:10:36 rpi-monitor grott[1162]: <socket.socket fd=6, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=0, la
Mar 29 08:10:36 rpi-monitor grott[1162]: - Data less then minimum record length, data not processed

Mar 29 08:11:05 rpi-monitor grott[1162]: - ('192.168.1.30', 31980) has disconnected

J4CE2 · 2024-03-29T01:11:10Z

Will try run GROTT on a different device to test.

Edit: Different device/ip made no difference.

J4CE2 · 2024-03-29T03:21:25Z

POSSIBLE SOLUTION

I updated the IP field in the grott.ini file to be 47.91.92.81 (server-au.growatt.com) as opposed to the default 47.91.67.66.

It now appears to be running, I also changed update frequency to 2mins - so far so good.

Not really clear why this has helped yet.

I suspect that when they receive my message, if it went to server.growatt.com (i.e. the default grott IP address 47.91.67.66) , they update my dongle to server-au.growatt.com everytime. Very sneaky IF SO! It's possible server-au.growatt.com is new ... I had not seen this before from memory.

lmdc45 · 2024-03-29T05:29:54Z

Thanks a lot for posting this, it seems to solve the same issue I had as well since yesterday

pimisen · 2024-03-29T09:02:32Z

Same here. I drove me crazy this morning on Good Friday. Thanks for saving my day!

bryceIT · 2024-03-30T00:22:27Z

absolute lifesaver! Thanks for sharing.
For anyone else using docker, just add the environment variable ggrowattip = 47.91.92.81 then go back into https://server.growatt.com/index and readd in your domain/port in the datalogger section to get information back into grott

edit: actually - even when setting the ip to 47.91.92.81 dongle is still resetting itself to the default url

J4CE2 · 2024-03-30T01:50:27Z

edit: actually - even when setting the ip to 47.91.92.81 dongle is still resetting itself to the default url

At this stage not really sure what they are doing. Only for me and a few others since changing to the aussie IP it hasn't reset it self.

I thought this morning when the inverter powered on I may have issues, but so far all so good

I also am not seeing any of these in the Grott logs (when verbose is true) anymore
Mar 29 08:11:05 rpi-monitor grott[1162]: - ('192.168.1.30', 31980) has disconnected

I've been tailing the logs for every update coming in and no disconnect msg.

journalctl -u grott -f -n 150

FreemanJD · 2024-03-30T02:07:11Z

POSSIBLE SOLUTION

I updated the IP field in the grott.ini file to be 47.91.92.81 (server-au.growatt.com) as opposed to the default 47.91.67.66.

It now appears to be running, I also changed update frequency to 2mins - so far so good.

Not really clear why this has helped yet.

I suspect that when they receive my message, if it went to server.growatt.com (i.e. the default grott IP address 47.91.67.66) , they update my dongle to server-au.growatt.com everytime. Very sneaky IF SO! It's possible server-au.growatt.com is new ... I had not seen this before from memory.

Sorry. I tried to go into my grott.ini but the files is blank.
what have I done wrong ? I’ve got the same issue where the dongle keeps getting reset to the Australian Server.

J4CE2 · 2024-03-30T02:09:27Z

POSSIBLE SOLUTION
I updated the IP field in the grott.ini file to be 47.91.92.81 (server-au.growatt.com) as opposed to the default 47.91.67.66.
It now appears to be running, I also changed update frequency to 2mins - so far so good.
Not really clear why this has helped yet.
I suspect that when they receive my message, if it went to server.growatt.com (i.e. the default grott IP address 47.91.67.66) , they update my dongle to server-au.growatt.com everytime. Very sneaky IF SO! It's possible server-au.growatt.com is new ... I had not seen this before from memory.

Sorry. I tried to go into my grott.ini but the files is blank. what have I done wrong ? I’ve got the same issue where the dongle keeps getting reset to the Australian Server.

How are you running GROTT? Docker? HA add on?

FreemanJD · 2024-03-30T03:26:24Z

POSSIBLE SOLUTION
I updated the IP field in the grott.ini file to be 47.91.92.81 (server-au.growatt.com) as opposed to the default 47.91.67.66.
It now appears to be running, I also changed update frequency to 2mins - so far so good.
Not really clear why this has helped yet.
I suspect that when they receive my message, if it went to server.growatt.com (i.e. the default grott IP address 47.91.67.66) , they update my dongle to server-au.growatt.com everytime. Very sneaky IF SO! It's possible server-au.growatt.com is new ... I had not seen this before from memory.

Sorry. I tried to go into my grott.ini but the files is blank. what have I done wrong ? I’ve got the same issue where the dongle keeps getting reset to the Australian Server.

How are you running GROTT? Docker? HA add on?

Sorry. I’m running Grott as a HA add on.

Neflardio · 2024-03-30T04:47:42Z

POSSIBLE SOLUTION
I updated the IP field in the grott.ini file to be 47.91.92.81 (server-au.growatt.com) as opposed to the default 47.91.67.66.
It now appears to be running, I also changed update frequency to 2mins - so far so good.
Not really clear why this has helped yet.
I suspect that when they receive my message, if it went to server.growatt.com (i.e. the default grott IP address 47.91.67.66) , they update my dongle to server-au.growatt.com everytime. Very sneaky IF SO! It's possible server-au.growatt.com is new ... I had not seen this before from memory.

Sorry. I tried to go into my grott.ini but the files is blank. what have I done wrong ? I’ve got the same issue where the dongle keeps getting reset to the Australian Server.

How are you running GROTT? Docker? HA add on?

Sorry. I’m running Grott as a HA add on.

If your add-on is the same as mine, you should be able to expose config entries by enabling "Show unused optional configuration options". Then it's a matter of adding the ip in the ggrowattip field.

KasperEdw · 2024-03-31T14:15:22Z

solution at least running grott on Windows, I dont know of the same applies to the HA version.

I changed the IP back to the grott server and set blockcmd = True in the grott.ini configuration file
It has been running fine since I did it a couple of hours ago.

Best wishes,
Kasper

J4CE2 · 2024-03-31T15:22:46Z

Good to know that's an option too. So far mines still going strong after changing the IP field only

Neflardio · 2024-03-31T17:34:33Z

Also have no issues after changing ggrowattip to growatt au. I also left refresh rate at 1 min.

danielschwab · 2024-03-31T19:24:37Z

Same issue here. Setting blockcmd = True in the grott.ini file seems to prevent the datalogger to switch back to the growatt server and disconnect from grott.
This raises the question why the growatt backend wants the datalogger to use a different api server and if ignoring this request will have a negative effect.

faaarmer · 2024-04-01T01:45:59Z

Same issue here - did what J4CE2 did and it seems to be working so far.

DonStone2188 · 2024-04-01T02:21:35Z

J4CE2’s solution worked for me so far.

J4CE2 · 2024-04-02T03:10:15Z

Closing this issue

2 solutions

update the IP field in the grott.ini file to be 47.91.92.81 (this is the AU Growatt server) OR
Setting blockcmd = True in the grott.ini file

johanmeijer · 2024-04-04T19:35:04Z

Nice you find a solution. I know there is also a request for allowing an URL in stead of a IP address for the growatt server. Maybe that will solve the problem also. I am working on a new version of Grott/Grottserver and that is at the wish list. But it a bigger project then I expected and finishing it might take a while.

Be aware the blockcmd = True will block all commands (expect set time) from the growatt server. This is save if you do not want Growatt to control your inverter/datalogger. But if you want to use the growatt website or phone app to make changes to your config (and update firmware) it will not work anymore.

tabascoz · 2024-04-04T19:52:29Z

Nice you find a solution. I know there is also a request for allowing an URL in stead of a IP address for the growatt server. Maybe that will solve the problem also. I am working on a new version of Grott/Grottserver and that is at the wish list. But it a bigger project then I expected and finishing it might take a while.

Be aware the blockcmd = True will block all commands (expect set time) from the growatt server. This is save if you do not want Growatt to control your inverter/datalogger. But if you want to use the growatt website or phone app to make changes to your config (and update firmware) it will not work anymore.

I confirm the blockcmd=True is able to prevent this change pushed by Growatt, as i have had a "good" Good friday :)

J4CE2 · 2024-04-05T05:06:28Z

Nice you find a solution. I know there is also a request for allowing an URL in stead of a IP address for the growatt server. Maybe that will solve the problem also. I am working on a new version of Grott/Grottserver and that is at the wish list. But it a bigger project then I expected and finishing it might take a while.

Be aware the blockcmd = True will block all commands (expect set time) from the growatt server. This is save if you do not want Growatt to control your inverter/datalogger. But if you want to use the growatt website or phone app to make changes to your config (and update firmware) it will not work anymore.

Good point about blockcmd

For me the simple ip change was sufficient and still going strong.

RichardRamshaw · 2024-04-10T14:54:06Z

Thanks so much for this, been running round trying to find this answer for days.

PaddyCube · 2024-04-13T18:07:58Z

Just to comment, this issue is not only true for Australia. It happend to me in Germany as well.

J4CE2 · 2024-04-14T02:47:52Z

Just to comment, this issue is not only true for Australia. It happend to me in Germany as well.

Good to know.

Did you use a german IP / growatt server as a solution?

pimisen · 2024-06-22T08:51:47Z

The Issue is back.
I (from Germany) had to change to this IP now:
Server-au.growatt.com, with hostname set to Ec2-3-24-103-55.ap-southeast-2.compute.amazonaws.com, is assigned a AU server IP 3.24.103.55.
But those aws host change randomly.
I think it would be really cool, if hostnames in the grott.ini were allowed @johanmeijer :
Is there by the way anything know, when the docker image:latest will be the 2.8.3 Version?
(For smooth inplace upgrade, i don't want to set up the docker from scratch 😁)

pimisen · 2024-06-22T09:56:14Z

That are the possible IPs (currently):
3.24.103.55 >> ec2-3-24-103-55.ap-southeast-2.compute.amazonaws.com

54.253.11.203 >> ec2-54-253-11-203.ap-southeast-2.compute.amazonaws.com

13.239.127.14 >> ec2-13-239-127-14.ap-southeast-2.compute.amazonaws.com

J4CE2 · 2024-06-22T10:35:05Z

The Issue is back. I (from Germany) had to change to this IP now: Server-au.growatt.com, with hostname set to Ec2-3-24-103-55.ap-southeast-2.compute.amazonaws.com, is assigned a AU server IP 3.24.103.55. But those aws host change randomly. I think it would be really cool, if hostnames in the grott.ini were allowed @johanmeijer : Is there by the way anything know, when the docker image:latest will be the 2.8.3 Version? (For smooth inplace upgrade, i don't want to set up the docker from scratch 😁)

They have changed all of their IP Addresses.

I changed grott.ini to use server-au.growatt.com rather than IP and I am back online. Host names do work for me.

lmdc45 · 2024-06-22T15:48:15Z

Thanks again.

pimisen · 2024-06-24T10:47:39Z

The Issue is back. I (from Germany) had to change to this IP now: Server-au.growatt.com, with hostname set to Ec2-3-24-103-55.ap-southeast-2.compute.amazonaws.com, is assigned a AU server IP 3.24.103.55. But those aws host change randomly. I think it would be really cool, if hostnames in the grott.ini were allowed @johanmeijer : Is there by the way anything know, when the docker image:latest will be the 2.8.3 Version? (For smooth inplace upgrade, i don't want to set up the docker from scratch 😁)

They have changed all of their IP Addresses.

I changed grott.ini to use server-au.growatt.com rather than IP and I am back online. Host names do work for me.

Not working here. If i use the DNS Name, it is not working.

J4CE2 · 2024-06-24T11:09:53Z

The Issue is back. I (from Germany) had to change to this IP now: Server-au.growatt.com, with hostname set to Ec2-3-24-103-55.ap-southeast-2.compute.amazonaws.com, is assigned a AU server IP 3.24.103.55. But those aws host change randomly. I think it would be really cool, if hostnames in the grott.ini were allowed @johanmeijer : Is there by the way anything know, when the docker image:latest will be the 2.8.3 Version? (For smooth inplace upgrade, i don't want to set up the docker from scratch 😁)

They have changed all of their IP Addresses.
I changed grott.ini to use server-au.growatt.com rather than IP and I am back online. Host names do work for me.

Not working here. If i use the DNS Name, it is not working.

What DNS name are you using?

pimisen · 2024-06-24T15:04:25Z

server-au.growatt.com

Unfortunately it is not fixed with setting dns option for docker.
DNS resolution is working inside the docker, but i still have to use one of the IP-Addresses

Neflardio · 2024-06-24T15:43:35Z

The domain name wasn't resolving for me either (using HA addon veresion)

Using one of the new ip addresses worked fine though.

J4CE2 · 2024-06-24T23:05:55Z

ok, I am on version 2.7.8 it looks and run standalone version on a raspberry pi.
it resolves server-au.growatt.com no problem

PedroKTFC · 2024-06-25T08:02:04Z

I use grottserver and haven't connected to the Growatt servers for months!

r4tt4 · 2024-06-26T16:29:55Z

Well also got this problem again. First didn't recognize cause blockcmd=true 😉
But also after using server-au.growatt.com the re-configure tries are not gone.
Grott: Record blocked: 0118
Is there another DNS entry needed in Germany?
--> Edit: Just tried server.growatt.com - It's working. So for Germany it seems you can't use the server-au.growatt.com anymore.

pimisen · 2024-07-03T10:21:00Z

I still have the issue that my docker (Docker Desktop on Debian 12) can't resolve the DNS names. Now they changed to dynamic IPs for server.growatt.com also use a cloud provider here also. currently it's a pain in the shoulder using it. No idea, why DNS resolving is not working for my docker setup

J4CE2 changed the title ~~Shinewifi-x problem - URL resetting to default~~ Shinewifi-x problem - URL resetting to default - data not flowing through GROTT Mar 29, 2024

J4CE2 closed this as completed Apr 2, 2024

anuadu mentioned this issue Apr 10, 2024

ShineLanBox reverts to factory configuration muppet3000/homeassistant-grott#85

Open

splitbrain mentioned this issue Jul 16, 2024

Data-Logger resets back to growatt servers #557

Open

Shinewifi-x problem - URL resetting to default - data not flowing through GROTT #542

Shinewifi-x problem - URL resetting to default - data not flowing through GROTT #542

Comments

J4CE2 commented Mar 28, 2024 • edited Loading

J4CE2 commented Mar 29, 2024

J4CE2 commented Mar 29, 2024 • edited Loading

J4CE2 commented Mar 29, 2024 • edited Loading

lmdc45 commented Mar 29, 2024

pimisen commented Mar 29, 2024

bryceIT commented Mar 30, 2024 • edited Loading

J4CE2 commented Mar 30, 2024 • edited Loading

FreemanJD commented Mar 30, 2024

J4CE2 commented Mar 30, 2024

FreemanJD commented Mar 30, 2024

Neflardio commented Mar 30, 2024 • edited Loading

KasperEdw commented Mar 31, 2024

J4CE2 commented Mar 31, 2024

Neflardio commented Mar 31, 2024

danielschwab commented Mar 31, 2024

faaarmer commented Apr 1, 2024

DonStone2188 commented Apr 1, 2024

J4CE2 commented Apr 2, 2024

johanmeijer commented Apr 4, 2024

tabascoz commented Apr 4, 2024

J4CE2 commented Apr 5, 2024

RichardRamshaw commented Apr 10, 2024

PaddyCube commented Apr 13, 2024

J4CE2 commented Apr 14, 2024

pimisen commented Jun 22, 2024

pimisen commented Jun 22, 2024

J4CE2 commented Jun 22, 2024 • edited Loading

lmdc45 commented Jun 22, 2024

pimisen commented Jun 24, 2024

J4CE2 commented Jun 24, 2024

pimisen commented Jun 24, 2024 • edited Loading

Neflardio commented Jun 24, 2024

J4CE2 commented Jun 24, 2024

PedroKTFC commented Jun 25, 2024

r4tt4 commented Jun 26, 2024 • edited Loading

pimisen commented Jul 3, 2024

J4CE2 commented Mar 28, 2024 •

edited

Loading

J4CE2 commented Mar 29, 2024 •

edited

Loading

J4CE2 commented Mar 29, 2024 •

edited

Loading

bryceIT commented Mar 30, 2024 •

edited

Loading

J4CE2 commented Mar 30, 2024 •

edited

Loading

Neflardio commented Mar 30, 2024 •

edited

Loading

J4CE2 commented Jun 22, 2024 •

edited

Loading

pimisen commented Jun 24, 2024 •

edited

Loading

r4tt4 commented Jun 26, 2024 •

edited

Loading