-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ShineLanBox reverts to factory configuration #85
Comments
I seem to have the same issue - nothing updated since 28/3/2024 .. seems like system got updated. What is your workaround? - I am about to try and login and change the settings back. Blocking internet for the box is not an option as I use it to allow demand management by my utility. |
Workaround is capture dns requests to 8.8.8.8 and in the name resolution of the Growatt server, point it to the IP of your own server. A bit involved. |
Experiencing same issue, ShineLanBox randomly reverts to its default settings, sometimes within a minute other times after few hours. |
I started experiencing the same issue a few weeks ago on Shinewifi-x logger. I only receive data in HA for a couple of minutes before it reverts to the Growatt server IP. Appreciate any suggestions how to prevent it from reverting |
I found a quick fix here johanmeijer/grott#542 (comment) |
Appreciated thanks, this fixed the problem
From: anuadu ***@***.***>
Sent: Wednesday, 10 April 2024 12:06 PM
To: muppet3000/homeassistant-grott ***@***.***>
Cc: carlosandtheo ***@***.***>; Comment ***@***.***>
Subject: Re: [muppet3000/homeassistant-grott] ShineLanBox reverts to factory configuration (Issue #85)
I found a quick fix here johanmeijer/grott#542 (comment)
Go to the Growatt Add-on->Configuration , toggle on 'Show unused optional configuration options' and type in 47.91.92.81 in the 'ggrowattip' field. This resolved the issue for me and it has been working ok for the last 18hrs.
—
Reply to this email directly, view it on GitHub <#85 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/BAYI74HY7TQTUVZE2BJH5M3Y4SM7JAVCNFSM6AAAAABFWU34Q6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBWGMZDSMZYGY> .
You are receiving this because you commented. <https://github.com/notifications/beacon/BAYI74HOCLFSGJZXISFHH7DY4SM7JA5CNFSM6AAAAABFWU34Q6WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTZ7CBCU.gif> Message ID: ***@***.*** ***@***.***> >
|
I can't find where this setting is. Is this on the ShineLanBox mini website? Is it in the growatt webpage where I can access my solar panel details, or is it on the ShinePhone app? |
It's in the grott.ini file Nothing to do with your inverter / or shinewifi config It may help to know how you have installed GROTT? |
Thank you. I see where my confusion comes from, I don't have grott as an add-on. I run it as an integration. In this case I need to update the grott.ini file as follows:
|
this started happening to me this morning for no reason that i can think, i have tried adding in the ip Adress 47.91.92.81, but with this added to the Grott config the Shinelink shows as offline. What excatly is the ip adress refering to? changing the setting does stop my shinelink from going back to factory default all the time however it still does not allow Grott to get any data. Any help would be greatfully excepted. |
Same on the system of a friend and on mine. Stopped working today morning. Setting the IP for the data forward to the grottserver in the grott.ini didn‘t solve the issue. It would be great if somebody has an idea to solve it. Thx. |
Mine reset this morning also, and found the datalogger had set itself to send to 8.209.71.240 |
At the time of writing that solution, it referred to this server's IP address "https://server-au.growatt.com/" Please note, 47.91.92.81 is no longer available at all - as Growatt moved to AWS servers 3 weeks ago, and as such this IP should not be used in the config. My current solution is to use DNS entry instead of IP in the config file, e.g. ip = server-au.growatt.com Additional comments here: |
is that in th grott.ini file or the configuration of Grott as have added the name in the Configuration and it does not seem to pick it up when Grott is restarted |
For EU it‘s server.growatt.com |
Yes grott.ini |
I noted that the MQTT packet was always the same one from 07:45 this morning, but not until lunchtime did I see this. If I went into HA and MQTT and listened on energy/growatt it would always immediately show that same packet from 07:45 and nothing afterwards. I went through the normal diagnostics of resetting my ShineWifi-S, setup again the Wi-Fi on the logger, and even did a clear data of the logger from the Growatt website, all to no avail. I did not reset the grott.ini and for my installation in the UK I have left the entries for IP and Port not configured as they default to server.growatt.com as I understand it. I finally did a reconfigure on the data logged to repoint to the IP address of my HA/MQTT setup, and after a while that seemed to fix this. There was no new firmware applied or available for the ShineWIFI-S logger, so this must be something Growatt reset centrally and pushed out to all loggers connected. There are no logs nor information anywhere via the Growatt interface or website that tells us they did this, but it does look like that was the cause. If that happens again, putting the IP address back into the logger will be my first port of call rather than waste a couple of hours trying all the other things I tried. The reason I didn't think to check the logger IP target address was that the Growatt site was showing all the correct data about solar and consumption etc, so that meant it was sending it still to Growatt. I should have put 2-and-2 together to realise that meant if Growatt had the data but I did not, that must mean the proxy element of Grott wasn't being applied. |
I tried everything above, but so far nothing seems to work. I updated the IP address via the growatt website several times (datalogger settings --> Set IP) to my internal HA IP address, restarted the integration, tried the grott.ini option, restarted the datalogger, but nothing works. After I restart mqtt it comes back with the old information from this morning and after 10 minutes or so, no data available. Weird move from Growatt to reset everything :( |
this will be my last growatt inverter! i'm very happy with how it works. but they keep fucking us with the data. their servers were crap, the growatt intergration from @muppet3000 was amazing. untill growatt fucket that up too. now grott was working amazing for months. now they fuck this up to. just let us be, OR GIVE US A API TO CONNECT TO FOR FREE. so we do not need to make all these workarounds. but. for me it seems to be ok with entering the server.growatt.com ip in the grott.ini file (in my case it is (belgium) 47.254.130.145) nslookup also gives me 8.209.1.240 but entered the first one. in my shinelink datalogger disabled the resolv domain and entered the ip of my grott container. is working again now. |
For me it works again after I entered the right HA ip address right in the datalogger. Via the website and datalogger this did not work somehow, even though it showed the right ip address. After entering the IP address in the datalogger via LAN and a restart of the datalogger the data started showing again. Hopefully it stays that way. |
I had to put in the IP of HA again today, after doing it yesterday as well, after which it worked yesterday. On to today, didn't work. Re-entered the IP to HA in the wifi stick, and works again. Are they remote resetting the stick daily? Hope not! |
Resetting through the website didn't work for me the first time as well, got no UI notification that settings where send. Retried it the exact same way and the UI said "successfully send" or something in the bottom left corner. |
Having had loads of issues yesterday, I now find myself not being able to pair the RF dongle to my Shinelink Lanbox, I have read the doc’s on how to get this to link but no joy.
Anyone have any advice.
Spence
On 17 Jul 2024, at 07:50, 87Vortex87 ***@***.***> wrote:
For me it works again after I entered the right HA ip address right in the datalogger. Via the website and datalogger this did not work somehow, even though it showed the right ip address. After entering the IP address in the datalogger via LAN and a restart of the datalogger the data started showing again. Hopefully it stays that way.
Resetting through the website didn't work for me the first time as well, got no UI notification that settings where send. Retried it the exact same way and the UI said "successfully send" or something in the bottom left corner.
—
Reply to this email directly, view it on GitHub<#85 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A5BXNOT7SAVXGNEMSPYZHR3ZMYH3LAVCNFSM6AAAAABFWU34Q6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMZSGU2TOMBUHA>.
You are receiving this because you commented.Message ID: ***@***.***>
|
I've had this problem in the past, you'll find that it is actually paired but if the ShineLan Box can't speak to the upstream server (Grott or Growatt) then it looks like it's not connected. Sometimes you have to leave it for an hour and it just sort of fixes itself. Recently I switched to a Wifi Dongle and the connection has been so much more stable! |
If I look in the lanbox web interface there is no device connected, hense saying the system is not paired. I had to reset the lanbox yesterday as it kept hanging when I added the IP address’s in my Grott config file, but I just don’t seem to be able to get it paired again.
On 17 Jul 2024, at 08:25, Chris Straffon ***@***.***> wrote:
Having had loads of issues yesterday, I now find myself not being able to pair the RF dongle to my Shinelink Lanbox, I have read the doc’s on how to get this to link but no joy. Anyone have any advice. Spence On 17 Jul 2024, at 07:50, 87Vortex87 @.> wrote: For me it works again after I entered the right HA ip address right in the datalogger. Via the website and datalogger this did not work somehow, even though it showed the right ip address. After entering the IP address in the datalogger via LAN and a restart of the datalogger the data started showing again. Hopefully it stays that way. Resetting through the website didn't work for me the first time as well, got no UI notification that settings where send. Retried it the exact same way and the UI said "successfully send" or something in the bottom left corner. — Reply to this email directly, view it on GitHub<#85 (comment)<#85 (comment)>>, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A5BXNOT7SAVXGNEMSPYZHR3ZMYH3LAVCNFSM6AAAAABFWU34Q6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMZSGU2TOMBUHA. You are receiving this because you commented.Message ID: @.>
I've had this problem in the past, you'll find that it is actually paired but if the ShineLan Box can't speak to the upstream server (Grott or Growatt) then it looks like it's not connected. Sometimes you have to leave it for an hour and it just sort of fixes itself.
Recently I switched to a Wifi Dongle and the connection has been so much more stable!
—
Reply to this email directly, view it on GitHub<#85 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A5BXNOT72ZILNYEYQMWVP4TZMYMADAVCNFSM6AAAAABFWU34Q6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMZSGYYTIMZSGM>.
You are receiving this because you commented.Message ID: ***@***.***>
|
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. |
after a week of issue with my Shine Lanbox once i have changed to selecting an IP addreess in Grott Config (the box kept hanging and not responding to Pings) Growatt have sent me a ShineWIFI-S dongle, which i have configured however i dont seem to be able to find a webinterface to set the target IP address to point it at my HA system, anyone know if its possible and how to change the config on them to allow it to work with GROTT. |
web inteface mode probably only works when in AP mode, same as mine. So you need to put in AP mode, change the IP, then it will restart and connect back to your actual wifi. |
AP Mode? |
The instructions for the Growatt ShineWIFI-S dongle should have been in the box. But if not, you can read them online via the Growatt link below. But if you already have it configured to your Wi-Fi, the way you change the IP address to send to (as in change it to Grott) is done within the Web Interface from Growatt. You can get to this via All Devices, then you select the Data Logger, then you can change "Set IP(Caution IP transfer with)" to point to your local IP for Grott. |
thank for that would the Password be the Growatt standard, or the pawword for the DataLogger |
Password will be the normal Growatt standard, which is either YYYYMMDD for the web interface or growattYYYYMMDD for the App. |
One final question when i try and join the AP network the system asks for a password for the AP network i dont see that listed in the doc's |
Assuming it hasn't changed, the password is 12345678 to connect in AP mode to the network (which is named to match the serial number of the data logger). |
password for my shine link was admin/admin. after firmware update the username is still admin but the password is the check code written on the shine link. |
Hi everyone. 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. i did not change the blockcmd back to true afterwards. i am from BE and was mailing with [email protected] hope this helps some of you! |
Not an issue with grott, but asking here in case someone else encountered this same issue.
About a week ago, my ShineLabBox started reverting to the factory configuration pointing to Growatt's server automatically.
I went back into the config and changed it to point to my home server and a few hours later I found it was again pointing to Growatt's server.
I have a work around, but I wanted to see anyone else was having this issue.
Thank you
The text was updated successfully, but these errors were encountered: