core: Growatt integration sensors unavailable

A few responses to some of the chat in this thread.

1. To anyone still trying to make this work by just arbitrarily changing the URL to something else - it won’t fix it.
2. Unless Growatt revert whatever change they made this integration won’t magically start working (regardless of what version you use)
3. This integration is dependent on a python library that myself and Indy reverse engineered from the Android API, it has nothing to do with the web page UI, or the other API doc that was posted here earlier
4. If the upstream library gets a fix (you can follow that chat on it here: https://github.com/indykoning/PyPi_GrowattServer/issues/74 then I’ll bump the version in my HACS release and people can use it from here. But so far nobody has had any luck.
5. The API doc that was posted here earlier is for installers and you have to have an installer account and it doesn’t provide all of the info that the shinephone app does (from the reading I did on it about 6 months ago)
6. Those of you having struggles with Grott, I’ve said it before and I’ll say it again, go post something in the integration I support and I’ll help out there, this isn’t the thread for that. (here)
7. I’ll try and find some time to update my documentation this week to make it more user friendly, I think people are finding it more complicated than it needs to be.

Got the following reply from NL support

`Our global servers have had some problems since this Tuesday, causing app logins to be affected as well. Our engineers are working hard to repair it, so please be patient for a few days, and check the system and the app later this week. We hope the problem will be solved later this week. If it still has problems later, please email me.

Met vriendelijke groet/Kind regards,

Yalin Wang

Growatt New Energy B.V.`

For what it’s worth, for anyone being a bit overwhelmed by the many options and alternatives to this integration (all having been mentioned many times in this thread), I tried to give an overview on what’s available, what I picked and why, and how it was configured here: https://www.splitbrain.org/blog/2023-11/03-growatt_and_home_assistant

Hi Everyone (fwiw I’m the original maintainer of this integration),

Sorry for the delay in replying to all these comments/bugs. I see people have been trying all sorts to work around the various issues with Growatt. To be clear, I haven’t had the time to read through all these comments etc so apologies if I repeat anything that has been said before.

Here’s where I stand on things:

1. About 8 months ago I stopped maintaining this plugin as part of HA-Core and moved it all into HACS as it was easier to maintain. For anyone interested here’s a link (as well as installation instructions): growatt_server_api
2. I never got around to removing this version from HA Core, but I need to add people are clearly still using it despite the lack of support from me (see points below)
3. About 6/7 months ago Growatt started doing all sorts of weird things and having all sorts of stability problems at which point I decided to give up on anything related to API integration (see notes below)
4. I have invested a lot of effort in writing an Integration that works with Grott (grott) and this can be found here: homeassistant-grott-integration. There is even examples of how to make template sensors to map onto the same values that this integration uses so you don’t lose any history.
5. Grott is not a perfect solution as it’s default implementation relies on publishing data to the Growatt servers (which are up and down like a yo-yo at the minute), however you can run ‘grottserver’ to cut out the Growatt Servers altogether.
6. I plan to contribute some functionality to the Grott codebase which will allow Grott to choose what to use based on what’s available but I have to get around to writing it first.

Some extra notes/detail:

• Yes, it’s stupid that Growatt don’t have any official API support
• Yes, it’s annoying that Growatt’s servers are very flaky and keep becoming unavailable
• Yes, it’s frustrating that Growatt seem to be trying anything and everything to stop the reverse engineered API from working
• But… they have no obligation to provide any of the above, beyond the original point of sale of their kit they don’t make any more money from us, nothing to use the API and hammer their servers every 5 minutes for information, nothing to handle the storage of the data published to their servers. While it’s frustrating, from a business perspective there is no reason to provide these features. It would be entirely different if we were paying a subscription for it.

My current setup:

• Grott in proxy mode forwarding data to the Growatt servers (which suffers whenever the Growatt servers start blocking stuff) and MQTT which I then have my HA integration pointing at

My planned setup:

• The same as above but with the following additions:
  • Test grottserver works in isolation
  • Write additional python code to choose between the Growatt servers and the Grottserver depending on what’s available

Like I said, I really need to pull this integration from Core to avoid the pain everyone has been suffering here. Grott has been working really well for me and if I can get the last bit working with it pivoting based on what’s available I think it’s a great (free) solution. (Grottserver even has a primitive feature for pushing configuration to the inverter as well).

I’m sorry if I haven’t answered people’s questions, there are about 15 different chains going on around this and I’m trying to divert them all to this one as it’s the biggest.

Hopefully this has been useful information at least.

Hi Everyone,

As the submitter of this defect I will now close this topic. Thanks for all your contributions. As muppet3000 clearly explained, the changes made by Growatt to it’s server requires extensive rework which is much more then just updating some server urls: https://github.com/home-assistant/core/issues/100874#issuecomment-1739911377

There are at least two alternative solutions mentioned in this thread:

1. Go with Grott, which requires setting up some additional services see: https://github.com/muppet3000/homeassistant-grott

2. Read out your Growatt locally using some ESP device and read out the UART bus using a RS485 https://esphome.io/components/sensor/growatt_solar.html

I walked that second route: rspring/Esphome-Growatt

Thanks

Grott is WAY to complicated for me - perhaps rather than close this issue we can keep it open whilst a solution is looked for???

This solution will remain open until I remove the integration from HA Core. At which point the conversation can continue over on the HACS repo I posted above, but I don’t maintain that either anymore because the API is impossible to work with. One of my missions is to try and work with the maintainer of grott to make it more human-friendly!

Anyone tried Grott already? How did that go? https://github.com/muppet3000/homeassistant-grott This looks the way to go for the future anyway, I prefer to be not dependent on Growatt’s servers. Thx

Works flawlessly Edit: Oh wait, i use this: https://github.com/johanmeijer/grott

Just to respond to this comment specifically - This Integration: https://github.com/muppet3000/homeassistant-grott depends on you having grott (https://github.com/johanmeijer/grott) running. The Integration for home assistant handles all the nice stuff like mapping ‘proper’ data values from MQTT into the nice format that HA provides including specifying the correct energy types etc.

Does this option allow the user to automate the charge times and dump times etc or is it just read only?

Take a read of my overview/comment above: https://github.com/home-assistant/core/issues/100874#issuecomment-1739911377

grottserver has the option to do this, but you have to know precisely what you’re doing e.g. what registers etc. to write to. I’m planning on taking a look at implementing that functionality as part of the HA integration next (after I’ve implemented the dual system I was describing above)

This chain has been impossible for me to follow, so I’ve pretty much given up on trying to follow it.

For anyone wanting help getting Grott setup with (or without for that matter) my integration, then I’ll happily do it in individual requests/issues in my github for the grott-homeassistant integration here: https://github.com/muppet3000/homeassistant-grott

Here a new (?) API documentation: https://www.showdoc.com.cn/262556420217021/1494053950115877

Just to add my 2 pennies… it’s an issue with Growatt’s API server. They seem to have issues with their AWS setup and the WAF is causing issues thinking every request is suspicious. My guess is they have been messing about with their backend and fluffed something up.

https://server.growatt.com/ is even having various issues with 500 server errors and plants cant be found. The shinephone phone app will not even login. I have raised a support call with their UK support team.

There is nothing we can do while ever the integration uses the http://server-api.growatt.com/ address and have to wait for Growatt to sort it.

How can change this in the Intergration for all users?

I have problems too. I just sent an email to Growatt to find out the reason for the block on https://server-api.growatt.com/.

If you want to get nicely formatted output rather than the stock MQTT stuff including stat names and correct entity types you can use my Grott integration for that as well: https://github.com/muppet3000/homeassistant-grott

It still needs to have Grott running and pushing the data to MQTT it just means you get nicely formatted data.

Ok, I have the “grott” addon installed , works , quite easy… But, in MQTT, it seems not to create all sensors… (some output is missing live PV2 watt) I see these sensors created… But, I see MQTT broker is receiving this: Can anyone explain why not all sensors are created ?

Had the same problem, check my comment here #100874 (comment)

I did, but the restarts did not help for me…

I found my issue with not all the values showing from the inverter / MQTT that were showing in Shine.

Originally I used ‘default’ but not all the entities were published to MQTT. I had a look on the side of my inverter for the model and its an SPH, changed the grot.ini to SPH inverter type, restarted Grot, deleted the Grot Integration I had configured and re-added it, then once the Inveter published again, 5 mins later, all 66 entities were published 😃

Now I have 66 entitites rather than 32 entities , including Battery and export to grid.

Well, this thread becomes quite long, so long that I’m lost to be honest. One basic question:

Is this issue going to be solved or not ? (and can we declare this integration dead and I have to look for other options like workarounds given here) I’m willing to wait but if this is never ever going to be solved then well…

All these comments about switching to the other api service or whether they’re going to re-instate the old api ‘service’ is pointless in the context of this thread. It was never an officially supported API, we just spoofed as if we were the android app, and they’ve found a way to stop that happening, because it was never supported.

So, I received the following message

If you have your own monitoring platform and want to obtain the data from Growatt, please use openapi.growatt.com.

On Mon, Oct 2, 2023, 12:42 PM Sweenylein @.***> wrote:

Growatt has just released a ShineApp update for the iPhone. Optimise Login Logic

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/100874#issuecomment-1742786153, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAERSLBJRODJEKDFMOFAFATX5KLCPANCNFSM6AAAAAA5GQ3I2U . You are receiving this because you were mentioned.Message ID: @.***>

Growatt has just released a ShineApp update for the iPhone. Optimise Login Logic

That makes the app working back again but the HA integration is still having issues connecting

They definitely have some sort of IP restriction in place. I couldn’t access with the app today, yet changing to mobile data or using a VPN it would load instantly.

Latest response from Growatt Netherlands this morning:

**_There is still a problem with the Growatt servers at the moment. Growatt is aware of this and is working hard on a solution. This nuisance is expected to continue until the weekend.

During this period it may happen that logging in is not possible, data is not displayed or not fully displayed in the app or on the website, or that data loggers lose their connection.

We thank you for your understanding._**

* But....... they have no obligation to provide any of the above, beyond the original point of sale of their kit they don't make any more money from us, nothing to use the API and hammer their servers every 5 minutes for information, nothing to handle the storage of the data published to their servers. While it's frustrating, from a business perspective there is no reason to provide these features. It would be entirely different if we were paying a subscription for it.

They could also just expose a local API on their dataloggers so HA wont hit their servers…

I have the same issue as @frankiep. Copied growatt_server to this folder: /config/custom_components/growatt_server. Changed the suggested files

/config/custom_components/growatt_server/const.py

SERVER_URLS = [ “https://server-api.growatt.com/”, “https://server-us.growatt.com/”, “http://server.smten.com/”, “https://server.growatt.com/”, ]

DEPRECATED_URLS = [

]

/config/custom_components/growatt_server/manifest.json

{ “domain”: “growatt_server”, “name”: “Growatt”, “codeowners”: [“@muppet3000”], “config_flow”: true, “documentation”: “https://www.home-assistant.io/integrations/growatt_server”, “iot_class”: “cloud_polling”, “loggers”: [“growattServer”], “requirements”: [“growattServer==1.3.0”], “Version”: 1.0 }

Removed Growatt integration, Restarted HA, when I try to add the Growatt integration, no new icon for local, only the cloud.

Try to remove the “,” at your Last entry at your server_urls section

The old API worked fine Yesterday, today there is Just 0,1kwh, although in reality there are 10kwh (i am tracking the growatt with a Shelly 1pm plus). Since 9 o clock there are no solar values anymore at the old API.

Seeing the same problem here. Too bad we can’t directly communicate with the inverter rather than relying on the cloud.

It is possible - https://github.com/johanmeijer/grott

Well I’ll be darned! I thought might be the case, but given that this integration is a native hacs integration, that it would be the most complete and effective solution, but ideally, the HA inclusion needs to ask the user for an online/offline deployment choice is made, then tumbles out into GROTT or growatt_server relevantly,

Right? I need to get a few thoughts from users before trying to make that happen though…

How can change this in the Intergration for all users?

Indeed, who can update the Integration, such that the new URL is recognized?

Use samba share to make changes, this files is hidden

If i do it, i only see config or addons or media etc, nothing looks like “growatt_server” 😦

I had the same issue, i also dont run HA on a Pi. Thanks to all the replies above, I combined the two solutions and got it working like this.

1. Used github desktop and cloned the Home Assistant Core using URL ‘https://github.com/home-assistant/core.git’
2. Once its cloned locally , copy the ‘growatt_server’ folder

1. connect from a mac/pc to your HA using Samba , copy the growatt_server contents into config -> custom_components ->

1. Open const.py in VS Code , add “https://server.growatt.com/”, to SERVER_URLS and remove “https://server.growatt.com/” from DEPRECATED_URLS , save the file

1. Edit the manifest.json and add a version number e.g.

save it.

1. restart HA

2. Now re-add the Growatt Integration, except this time you should see a cloud icon and the local integration icon

This shows your local integration has been recognised

1. Now the new URL should be selectable

1. Login using your Shine Tool Creds

2. Growatt works again.

Thanks everyone for commenting above to work out this solution.

The same issue persists, but https://server.growatt.com/ works fine. The problem lies with the Growatt integration; it doesn’t load data, and the ShinePhone application has the same issue - I cannot log in. However, when I log in via a mobile network, it works without any problems on my mobile phone. I suspect there might be a limitation on the number of login attempts from a specific IP address.

I have no experience with developing integrations, but is it not possible to create an integration that reads the inverter locally?

I have made a modbus controller for this myself, which works, but cannot yet be used because my dashboard is not fully completed. This is my choice not to fully use this controller yet. This will happen next month.

That’s exactly what’s done here: https://github.com/muppet3000/homeassistant-grott However it requires extra steps to set up.

This is driving me nuts, I simply can not get it work no matter what I try. What I really don’t understand, homewizzard was down, but they fixed it in the app and now it’s working as it should and stable as a rock. Why does it have to be this complex in home assistant? Why not update the integration? It should not be that hard… I’m running home assistant on a synology virual machine.

Just use modbus and all is happy, then also all your data stays local 😃

For anyone still clinging on to this thread hoping that the old integration may one day work again, I’ve been informed of a URL that seems to work (but I have no idea for how long). I’ve released a new version of my HACS version of the integration here: https://github.com/muppet3000/homeassistant-growatt_server_api which seems to work (for now).

Thank you! it works again now. Appreciate your effort on this. However, would that be possible to have option for user to type custom URL as well apart from selecting from the list (should the existing URL changed again) ?

Please log it as a request over in that repo - sounds like a good idea (although I’m not actually sure how easy it would be to implement)

done and thanks! https://community.home-assistant.io/t/growatt-custom-url/634999

That’s not what I meant - Log it in the github for my hacs version of the integration here: https://github.com/muppet3000/homeassistant-growatt_server_api/issues

For anyone still clinging on to this thread hoping that the old integration may one day work again, I’ve been informed of a URL that seems to work (but I have no idea for how long). I’ve released a new version of my HACS version of the integration here: https://github.com/muppet3000/homeassistant-growatt_server_api which seems to work (for now).

Thank you for author and all support from github.

Now instalation is very easy and its working fine. I will recomend grott in the Poland (on fb group)

@yvesdemoerloose do you also not see these entries in the logs of grott? The list I sent is from grott. I guess it’s everything it gets from the inverter.

That’s the thing, here’s the list, I don 't see it.

But in Growatt app I do have Load consumption daily/total and import from grid daily/total and data is proxied through Grott, so it must be available somewhere, lol EDIT: eacDischarge today looks like load consumption today I just noticed, This could be the import from grid values. Still I miss them as well as in the mqtt device as in muppet3000’s integration.

Any missing values that appear in the grott logs but aren’t shown by my integration, just log a ticket over here: https://github.com/muppet3000/homeassistant-grott/issues

Key is growatt+date e.g.: growatt20200702 (formaly datalog+date)

Today date?

And second question For what is this second addon

This is the newly packaged adddon. There is a 2.7 branch aka stable and the 2.8 branch who is the develop branch.

The one you are using is going to become the 2.8 series. The difference is there is support for the spa and min series of inverter.

@yvesdemoerloose not sure what you mean, but also try to enable the last option and you should also have another mqtt device from grott/mqtt. Maybe you have your entities there. I guess not all inverters show the same information.

Integration showing the entities above Device entities above. What I’m missing is my consumption (total&today) and import from grid (total&today) I do have the entity how much total kw batteries got charged from grid (34.3kw), but no total or daily grid import data.

pendragon1

@yvesdemoerloose did you enable the top option in de grott addon called: Enable grott Mqtt?

This is needed for the integration to find the ‘device’. After installing the integration click on Add Item leave it empty (it will show a + sign). After a few minutes it will find the device.

Thx, that did it. But still missing import-from-grid daily/total and consumption-daily/total entities. Inverter is Growatt SPF-5000es

@yvesdemoerloose did you enable the top option in de grott addon called: Enable grott Mqtt?

This is needed for the integration to find the ‘device’. After installing the integration click on Add Item leave it empty (it will show a + sign). After a few minutes it will find the device.

Hi,

If you are using hassos (The native version of HA) you can use the addons. I have packaged grott with autoconfiguration of MQTT (using the mqtt addon in HA). You can find the repo at this address: https://github.com/egguy/grott-home-assistant-add-on/ It is compatible with @muppet3000 integration.

@muppet3000 I’ll start with reading your tutorial again and let you know if anything can be improved. Love this community 😃

If you want to get nicely formatted output rather than the stock MQTT stuff including stat names and correct entity types you can use my Grott integration for that as well: https://github.com/muppet3000/homeassistant-grott It still needs to have Grott running and pushing the data to MQTT it just means you get nicely formatted data.

If there is a video manual step by step, lot of questions will not be asked. By the way is port used in HA can be indicated open/working in UI?

I’m not very good in creating video’s like that, but let’s see if I can make a tutorial this weekend. Maybe a video, maybe a document.

If you do make a video, please let me know and I’ll add it to the documentation. If you want to help improve the documentation, I’ll happily accept changes & PRs to my repo which seems to be the best ‘tutorial’ so far: https://github.com/muppet3000/homeassistant-grott/blob/main/docs/prerequisites.md

If you want to get nicely formatted output rather than the stock MQTT stuff including stat names and correct entity types you can use my Grott integration for that as well: https://github.com/muppet3000/homeassistant-grott It still needs to have Grott running and pushing the data to MQTT it just means you get nicely formatted data.

Added that as well, to have both, good job! For anyone who wants to use this: You have to make sure to enable this in the grott add-on to get the datalogger automatically:

Enable grott MQTT Allow grott to send MQTT messages. If your are using the grott_ha extension, you don’t need this. If you are using the grott integration, you need to enable it.

This is the bit I need to update the documentation to reflect. It’s on my list!

If you want to get nicely formatted output rather than the stock MQTT stuff including stat names and correct entity types you can use my Grott integration for that as well: https://github.com/muppet3000/homeassistant-grott

It still needs to have Grott running and pushing the data to MQTT it just means you get nicely formatted data.

Added that as well, to have both, good job! For anyone who wants to use this: You have to make sure to enable this in the grott add-on to get the datalogger automatically:

Enable grott MQTT Allow grott to send MQTT messages. If your are using the grott_ha extension, you don’t need this. If you are using the grott integration, you need to enable it.

Ok so it means this is all for today 😄 I have night. Thanks

@pendragon1 did you have better/easier instruction? Or only this from gitgub

Use this addon, https://github.com/egguy/grott-home-assistant-add-on

Exactly the one I used.

@pendragon1 did you have better/easier instruction? Or only this from gitgub

Use this addon, https://github.com/egguy/grott-home-assistant-add-on

Lol 😃, here in Australia we are forced to get an electrcian to install the physical hardware 😃

That ain’t nothing, In Europe we were almost forced to take covid shots 😉 LOL

Sorry, but can someone moderate this topic? Its not helpful to find a diffrent solution instead of fixing this issue in the current integration.

After reading (most) of this thread, I am so glad I switched to local monitoring (ESP-32 + MAX-485 + ESPHome). I have the ESPHome code available to anyone who wants to go that route. Based on: https://esphome.io/components/sensor/growatt_solar.html

Can anyone explain why not all sensors are created ?

Had the same problem, check my comment here #100874 (comment)

I did, but the restarts did not help for me…

I have the same issue, I cant see my Battery % or Export to Grid. I’ll keep reading the comments above incase I have missed something. But @muppet3000 this is awesome , thanks for Grot, I’ll be ‘buying you a beer’

That’s very kind, thank you. To be clear, I didn’t make grott, that was another developer. My integration just nicely visualises all the data from grott in Home Assistant for people.

If it’s the same as in the web interface, the password is growatt + today’s date in the format YYYYMMDD

so today would be

growatt20231004

@okortepu, obrigado por compartilhar a solução, mas para uma situação como a abaixo, onde o servidor HA fica distante do inversor físico, qual seria a melhor sugestão para fazer isso funcionar?"

Não verifique se o dongle pode usar outros domínios além dos pré-definidos. Se o dongle puder lidar com outros domínios, talvez o tipo de serviço DNS dinâmico e o encaminhamento de porta possam funcionar. Não tenho ideia de quão seguro isso é ou se existem soluções melhores.

O dongle Wi-Fi Shine não possui servidores DNS codificados, ele os recupera do roteador via DHCP. Encaminhei “server.growatt.com” para um IP local para não precisar alterar as configurações de estoque do USB 😃.

Hello @Myrenic, thanks mate! So… now it raised more questions for me! 😃 Should this forwarding configuration for “serv er.growatt.com” to a local IP be done on my router where HA is located, or on the router where the Growatt Inverter is located?

If i were you, i would just call the ISP to port forward the Grott server to the internet:

so it should look something like this

A lot of different setup could be put in place but I guess this is the simplest solution. i would suggest setting up some firewall rules on the Grott server to only allow data from LAN and the external wan address of your off-site inverter, just in case.

Hello @Myrenic, thank you for your feedback. So, I have a lot of questions about this… I’ll need to set up a mini server at my power plant to configure Tailscale and send the data to my HA system, which is 270km away from where I am now.

I assumed there was already a server/router or anything on site. if not, things indeed get more complicated. Perhaps forwarding the grott port could work. Renting a cheap VPS for this could allow you to bypass the ISP shenanigans. Good luck 👍🏻

Thanks @muppet3000 for your continued support and patience on this much appreciated.

It seems from all the comments above the simplest solution of you don’t want to change the out of the box configuration i.e. Inverter reporting directly to Growatt without impacting any support and warrantee issues with your installers (if you have them).

1. Purchase a ShineLanBox https://thesolarstore.co.uk/products/growatt-shine-link-wireless-monitoring-device-s
2. Setup GROTT
3. configure the ShineLanBox to report locally to GROTT

That way you have two interfaces one reporting to the Cloud and another Locally

Or consider Shelly EM and two power monitoring clamps

The shinelanbox part of this isn’t necessary, in fact it would replace whatever you’re currently using e.g. the wifi stick. All you need to do is configure your existing device to point to grott.

Has anyone established from Growatt if they are going to reinstate the Server-API.growatt.com option, as all other options seem to be a load of work with potential to break the link to the official reporting.

Hopefully it’s ok for me to post this. For all of us that now have missing Kwh, there is a easy way to ‘repair’ this. You don’t even have to use SQL for this to insert the data but use the UI. Make sure to make a backup before you start doing this and check the outcome after you fixed 1 day. do this at your own risk 😃 You do need to put all the missing Kwh on the last day you have received data. I’ll post screenshots to make it very simple. First make sure you don’t delete Growatt in the dashboard!!!

Quick question, do you run this on an RPI? Mine is pretty loaded already, does grott take a lot of resources? Thx The opportunities you missed, the streets you did not walk , the people you didn’t talk and the dreams you never dreamt, will be the fate of others, not yours. … On Fri, Sep 29, 2023, 22:08 Chris Straffon @.> wrote: But, here’s your answer anyway: https://community.home-assistant.io/t/growatt-server-integration-interval/207840/9?u=muppet3000 Hi! Thanks for all your work 😃 I saw that, but was hoping to not have to get the ladder out to climb to where that stick is to put it in AP mode so I hoped that maybe someone would know which register to set to “1”, because I can do that from the growatt server. Did the IP address change work for you? I changed it, but nothing hits Grott server, still going to Growatt only. @J4CE2 https://github.com/J4CE2 yes it worked. Did you input the IP into the “IP” field (it’s not for the device IP, it’s the IP it’s querying) and did you save with the correct passphrase entered? The passphrase (bottom row next to the save button) is “growatt” plus the date as YYYYMMDD, so growatt20230929 for today. Also make sure to enter the host IP of the docker host that has the image, not the internal docker IP (sorry if this is common knowledge, but in a thread that reaches so many different levels of knowledge I shouldn’t assume) I’m clutching at straws here, but a bit of digging around in the grottserver documentation and I’ve found this: https://github.com/johanmeijer/grott/wiki/Grottserver datalogger register 4 => update interval in seconds (e.g 5 or 1 or 0.5) Don’t blame me if it’s wrong though! — Reply to this email directly, view it on GitHub <#100874 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASQLJUDUMULHXWT66TQLNSLX44TEVANCNFSM6AAAAAA5GQ3I2U . You are receiving this because you commented.Message ID: @.>

I’m running Grott on an old raspberry pi (rp 1 model b). Doesn’t seem to use too much at all.

I am now able to navigate to https://server-api.growatt.com on the browser on my mobile, login is also fine, this server seems to be back online now. From my laptop however I still get the 405 error: “Sorry, your request has been blocked as it may cause potential threats to the server’s security.” That puzzles me as I cannot find a reason that the same url can be reached from one device and not from another device while both are on the same WiFi network. Ping to the servers also works from all devices including HA. Perhaps I need to be more patient and wait for everything to start working as normal again

It works differently depending on whether you’re viewing it from a browser vs android app vs python client the server responds differently

I tried the Grott integration, but I discovered that this integration is missing of some sensors like “power export to grid”. I think that only the inverter data has been considered, but not the meter data too. Also, changing the the integration into HA, I changed all sensors as well. Do you know the right way to change the sensor into the energy panel without to lose historical data? Thx

Log a ticket in the https://github.com/muppet3000/homeassistant-grott repo and I’ll assist you there.

Just to respond to a few comments I’ve seen/direct emails I’ve had.

I did not want to give up on this integration, I spent a load of effort on it at the beginning of the year moving it into HACS so I could support it better. The decision has been taken out of my hands though, Growatt do not have a supported API. The work that Indy and I did to make the python library was entirely through reverse engineering and that is prone to being changed without any notice/support from Growatt. Therefore, I moved to the alternative - remove the growatt servers from the loop.

I appreciate that for the many grott seems daunting and complicated and the documentation isn’t great, however, it does work and I’m doing my best to assist the developer to improve it and to provide additional documentation myself on my integration’s page as to how to set it up. That is a far better & more productive use of my time than fighting against the ever-changing Growatt api.

I hope people can understand that. I’d love to support this method, it’s simple, it worked and I even had plans to add configuration, but it has been taken out of my hands.

Grott is WAY to complicated for me - perhaps rather than close this issue we can keep it open whilst a solution is looked for???

Now, even server.growatt.com stop working here. That’s really terrible.

Anyone tried Grott already? How did that go? https://github.com/muppet3000/homeassistant-grott This looks the way to go for the future anyway, I prefer to be not dependent on Growatt’s servers. Thx

Works flawlessly Edit: Oh wait, i use this: https://github.com/johanmeijer/grott

Just to respond to this comment specifically - This Integration: https://github.com/muppet3000/homeassistant-grott depends on you having grott (https://github.com/johanmeijer/grott) running. The Integration for home assistant handles all the nice stuff like mapping ‘proper’ data values from MQTT into the nice format that HA provides including specifying the correct energy types etc.

Anyone tried Grott already? How did that go? https://github.com/muppet3000/homeassistant-grott This looks the way to go for the future anyway, I prefer to be not dependent on Growatt’s servers.

Thx

Works flawlessly Edit: Oh wait, i use this: https://github.com/johanmeijer/grott

Funny thing… the Growatt integration for Tibber works still fine.

Not as soon as it needs to log in again. If you remove it from Tibber and try to add it again you get an error

Funny thing… the Growatt integration for Tibber works still fine.

I like when Github bug reports generate this much interest. I have nothing new to report, 9.3 with no settings changed has not connected in the past three days.

So to sum up, the options right now seem to be:

• Do nothing and wait until this situation resolves at Growatt, assuming that this is an internal issue that was not planned (e.g. server troubles) Pro: might start working again miraculously, not touching anything does not endanger the accumulated energy data Con: might not start working again miraculously, only pushing the problem further back, timescale “within the week” according to support (see below)

EDIT: @saurjk got a response from Growatt customer support further down in the comments, quoting from them:

Got the following reply from NL support

`Our global servers have had some problems since this Tuesday, causing app logins to be affected as well. Our engineers are working hard to repair it, so please be patient for a few days, and check the system and the app later this week. We hope the problem will be solved later this week. If it still has problems later, please email me.

So I will definitely be waiting this out for now

• Do nothing and wait until the integration is updated to include more or different server addresses Pro: project maintainer will be aware of the issue and might have mitigation strategies we can not assess from here, does not endanger accumulated energy data if dataset provided by Growatt remains the same - there are reports that changing the server URL also changes the names of sensors because the other API url reports back different sensor names Con: no timescale, several possible points of failure (Growatt and integration)

• Do something: fork integration to custom integration, change variables for server URL there Pro: might be fastest way to mitigate issue and get data back Con: needs somewhat solid knowledge of how to fork and edit files; if custom integration is not replaced by “regular” integration after fix is deployed, custom integration will not pick up changes and improvements to baseline plugin; accumulated energy data might be lost if sensor names change because of different data provided

• Do something: edit files in HASSIO core Pro: you’re living in the fast lane Con: I seriously wouldn’t

Me, personally, having forked a different custom component to “fix a bug” in another integration and losing all the gathered data associated with that integration I will accept that my HA-related knowledge of forking and fixing is not sufficient and I will sit this out waiting for either option 1 (Growatt gets their stuff in order) or option 2 (integration gets updated) to come to pass.

Other options, unrelated to this integration and not possible in every use case:

• Assuming you’re running a low kW (the famous “Balkonkraftwerk”) that plugs into Schuko, you could put a wifi plug with power output/input reading where your Growatt meets your power circuits and use that value as the wattage output sensor (might need to flip the negative value). Pro: you’re no longer beholden to the whims of Growatt Con: you only get 1 reading (the wattage) and you have to invest in a wifi plug and you have to have the required infrastructure in place

• If all else fails, try and read the data stick locally without going through the cloud. Might need reflashing, might need some sort of local proxying, have not yet looked into this because 1. you will likely lose your accumulated energy data and 2. I’d rather not.

Seeing the same problem here. Too bad we can’t directly communicate with the inverter rather than relying on the cloud.

It is possible - https://github.com/johanmeijer/grott

Use samba share to make changes, this files is hidden

If i do it, i only see config or addons or media etc, nothing looks like “growatt_server” 😦

I had the same issue, i also dont run HA on a Pi. Thanks to all the replies above, I combined the two solutions and got it working like this.

1. Used github desktop and cloned the Home Assistant Core using URL ‘https://github.com/home-assistant/core.git’
2. Once its cloned locally , copy the ‘growatt_server’ folder

3. connect from a mac/pc to your HA using Samba , copy the growatt_server contents into config -> custom_components -> 4. Open const.py in VS Code , add "https://server.growatt.com/", to SERVER_URLS and remove "https://server.growatt.com/" from DEPRECATED_URLS , save the file 5. Edit the manifest.json and add a version number e.g. save it.

1. restart HA
2. Now re-add the Growatt Integration, except this time you should see a cloud icon and the local integration icon

This shows your local integration has been recognised

1. Now the new URL should be selectable

1. Login using your Shine Tool Creds
2. Growatt works again.

Thanks everyone for commenting above to work out this solution.

I only performed till step 6 and after that the integration worked with the new (deprecated) url again. When you remove your existing integration and add it again, you will lose your sensors and also your database history. Therefore a empty Energy Dashboard of your Growatt Inverter.

My problem is solved to, only needed to delete te existing intregratie, added again, only i got net Indenty’s… But a lot more then before.

your manifest.json is missing a comma You have a missing comma in your manifest.json At the end of the “requirements” line, add a comma and restart HA Be sure to remove the existing Growatt integration first

Thank you that was the Problem. Now it works fine for me again 😃

your manifest.json is missing a comma You have a missing comma in your manifest.json At the end of the “requirements” line, add a comma and restart HA Be sure to remove the existing Growatt integration first

Thanks everyone for commenting above to work out this solution.

Thank you for your clear instructions on the solution. I have zero experience with code and could follow the step-by-step guide you created

I will only mention why removing ‘https://server.growatt.com/’ from DEPRECATED_URLS is required.

1. api.server_url = “https://server.growatt.com/”

In my case, this change helped, what I did exactly: in the file - /usr/src/homeassistant/homeassistant/components/growatt_server/sensor.py

api.server_url = "https://server.growatt.com/"
#api.server_url = url

in the file - /usr/src/homeassistant/homeassistant/components/growatt_server/const.py

SERVER_URLS = [
"https://server-api.growatt.com/",
"https://server-us.growatt.com/",
"http://server.smten.com/",
"https://server.growatt.com/",
]

DEPRECATED_URLS = [

]

DEFAULT_URL = SERVER_URLS[0]"

and restart homeassistant, growatt integration

Confirmed. Changing the URL seems to work! (The question is for how long?).

When I connect my Growatt inverter to my Domoticz server (HTTP / HTTPS), I immediately have all the information available and it works.

This integration looks at server.growatt.com.

There are only problems in combination with HA.