core: Growatt integration broken

Hi All,

I submitted the PR last night for the fix on top of @coffeedave’s original settings update. Once the fix is included and people update their HA instances it’ll automatically update anyone using the old URL to use the new one, no further changes required. For those of you that have used the settings tweak described above to switch over to the new URL it will not change it, as that’s the desired end-goal. The change also changes the old URL to the new one for users configuring the integration for the first time (or re-configuring after removing it).

For those of you that are interested, I’ve also worked out why my system wasn’t being affected by it. My HA configuration for Growatt predates when we had the option to specify a URL, therefore there was nothing in my “core.config_entries”. In that scenario it defaults to whatever the upstream PyPi_GrowattServer library uses which is the correct URL (it turns out this was updated months ago and we should have updated the HA integration at the same time).

Anyway, the fix is imminent (you can follow it here if you’re interested), in the meantime you have the workaround.

Hi Everyone,

Thanks for the continued updates and workarounds etc. I’m now back from my weekend away and able to look at this again. Whilst I’m still unable to re-create this issue myself I am able to confirm that the shinephone app (which this library is reverse engineered from) has changed it’s endpoint to https://server.growatt.com/ as described above by @coffeedave.

@coffeedave has kindly submitted the PR to update the module, and after one more refinement it will be ready to merge. The final refinement will mean that when the version of HA is released containing the fix you won’t need to make any changes, the configuration will automatically update.

In the meantime, the fix to update your core.config_entries as described above to change the URL from whatever is currently there to https://server-api.growatt.com/ will work around the issue.

There is no need to email growatt via their support channels as there is no official support for this integration, or the library that Indy & I support, all we do is spoof being the android app in order to pull information.

I fully acknowledge that this particular issue has been a real pain for people and apologise for how disruptive it’s been, especially considering the problem is so intermittent for people. I know there are other options available (I’ve seen grott mentioned in this chain) and don’t blame people for trying alternative methods. I will continue to maintain this library so long as it’s viable and possible to do so, it just helps when I can actually reproduce the issues other people are having 😛 !

The fix will come soon, in the meantime the workaround is described above for people.

@mjooris - While this issue does seem to be fixed for yourself, can I please as you to re-open this bug as it’s clearly affecting people and we shouldn’t mark it as resolved until the official fix is out there.

Belatedly, changing the server URL fixed it for me too. However, it’s essential that the url entry in core.config_entries includes the forward slash too.

Before my entry was: “url”: “https://server.growatt.com”,

Which I had to change to: “url”: “https://server-api.growatt.com/”,

Without the last forward slash I was getting the ‘Failed to establish a new connection: [Errno -2] Name does not resolve’ error.

Hope it helps others.

I had the same issue, same error, until yesterday morning: I Just changed /config/.storage/core.config_entries Look for the GroWatt part and changed: From: server.growatt.com To: server-api.growatt.com Both are reachable from the browser, but evidently the top one not via Home Assistant, for a to me unclear reason. (Via: home-assistant/home-assistant.io#23705)

this works for me to! (for now, hopefully it stays that way)

@muppet3000 is it a possibility to integrate this in the integration. Maybe set a picklist in the settings to choose from different servers?

This change in the config file solved it for me: I Just changed /config/.storage/core.config_entries Look for the GroWatt part and changed: From: server.growatt.com To: server-api.growatt.com

I had the same issue, same error, until yesterday morning:

I Just changed /config/.storage/core.config_entries Look for the GroWatt part and changed: From: server.growatt.com To: server-api.growatt.com

Both are reachable from the browser, but evidently the top one not via Home Assistant, for a to me unclear reason. (Via: https://github.com/home-assistant/home-assistant.io/issues/23705)

Growatt no longer works after the latest Home Assistant update

Growatt application is back to old server settings server.growatt.com when updating Home Assistant. The correct settings are server-api.growatt.com If you want to solve this you can run the following command in SSH

Go to:

Settings Add-ons Install SSH & Web Terminal

Open SSH terminal and run the following command:

sed -i ‘s/server.growatt.com/server-api.growatt.com/g’ /config/.storage/core.config_entries

Restart your Home Assistant and Growatt is working again.

https://github.com/home-assistant/home-assistant.io/issues/23705#issuecomment-1214799146

@Edem123456

I followed these simple steps to change the file. For me it worked

Go to:

Settings Add-ons Install SSH & Web Terminal

Open SSH terminal and run the following command:

sed -i ‘s/server.growatt.com/server-api.growatt.com/g’ /config/.storage/core.config_entries

please note. The line above is one single line. Not three!

Restart your Home Assistant and Growatt is working again.

In the meantime, the fix to update your core.config_entries as described above to change the URL from whatever is currently there to https://server-api.growatt.com/ will work around the issue.

Mine got back working with this change (at least for now) ssh -> config > .storage

nano core.config_entries

This has also fixed my issue. @muppet3000 big thumbs up for your continued efforts with this. Anyone offering their own time and knowledge to an open source platform is doing the rest of us huge favours. Thank you.

This might also be why the app is working, if the app is polling the server-api address.

If you’re talking about the ShinePhone app, I can see it’s hitting oss.growatt.com according to my DNS server.

I had the same issue, same error, until yesterday morning:

I Just changed /config/.storage/core.config_entries Look for the GroWatt part and changed: From: server.growatt.com To: server-api.growatt.com

Both are reachable from the browser, but evidently the top one not via Home Assistant, for a to me unclear reason. (Via: home-assistant/home-assistant.io#23705)

this works for me to! (for now, hopefully it stays that way)

@muppet3000 is it a possibility to integrate this in the integration. Maybe set a picklist in the settings to choose from different servers?

How to use the workaround when you are adding a new integration? I don’t have the entry in my “core.config_entries” so I can’t change it there.

Same here. Also if I try to add it, ignore the errormessage, and look again. The entry in the “core.config_entries” doesn’t come.

Probably doesn’t help you, but mine would suddenly add, and I could then change the server. Now mine is working.

@Edem123456 the change that @coffeedave made to this has been approved and tagged for release in 2022.8.6 which I believe has just come out so you should be able to upgrade and not fiddle with the backend stuff.

Not sure why you think this has been merged or released but the PR still hasn’t been merged by the maintainers yet: https://github.com/home-assistant/core/pull/76824

So it’s not in any release yet. Once it’s merged it will be in the next dev/nightly release though.

@Edem123456 the change that @coffeedave made to this has been approved and tagged for release in 2022.8.6 which I believe has just come out so you should be able to upgrade and not fiddle with the backend stuff.

As another alternative this could be used for a local solution. It is based on a ESP8266 and Modbus. Additional information can be found on: https://youtu.be/krCdt2nv3BM

Thanks for the update and feedback @muppet3000.

So I am not sure if this is helping, but my integration stopped working completely the last 2 days. I ended up removing Growatt, and now I cannot add it back. I am getting the following in my logs when trying to add my Growatt integration:

2022-08-16 09:07:46.527 ERROR (MainThread) [aiohttp.server] Error handling request Traceback (most recent call last): File "/usr/local/lib/python3.10/site-packages/aiohttp/web_protocol.py", line 435, in _handle_request resp = await request_handler(request) File "/usr/local/lib/python3.10/site-packages/aiohttp/web_app.py", line 504, in _handle resp = await handler(request) File "/usr/local/lib/python3.10/site-packages/aiohttp/web_middlewares.py", line 117, in impl return await handler(request) File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 60, in security_filter_middleware return await handler(request) File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 222, in forwarded_middleware return await handler(request) File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 28, in request_context_middleware return await handler(request) File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 82, in ban_middleware return await handler(request) File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 236, in auth_middleware return await handler(request) File "/usr/src/homeassistant/homeassistant/components/http/view.py", line 136, in handle result = await result File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 177, in post return await super().post(request, flow_id) File "/usr/src/homeassistant/homeassistant/components/http/data_validator.py", line 73, in wrapper result = await method(view, request, data, *args, **kwargs) File "/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py", line 109, in post result = await self._flow_mgr.async_configure(flow_id, data) File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 277, in async_configure result = await self._async_handle_step( File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 359, in _async_handle_step result: FlowResult = await getattr(flow, method)(user_input) File "/usr/src/homeassistant/homeassistant/components/growatt_server/config_flow.py", line 50, in async_step_user login_response = await self.hass.async_add_executor_job( File "/usr/local/lib/python3.10/concurrent/futures/thread.py", line 58, in run result = self.fn(*self.args, **self.kwargs) File "/usr/local/lib/python3.10/site-packages/growattServer/__init__.py", line 119, in login data = json.loads(response.content.decode('utf-8'))['back'] File "/usr/local/lib/python3.10/json/__init__.py", line 346, in loads return _default_decoder.decode(s) File "/usr/local/lib/python3.10/json/decoder.py", line 337, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) File "/usr/local/lib/python3.10/json/decoder.py", line 355, in raw_decode raise JSONDecodeError("Expecting value", s, err.value) from None json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

Sorry for the quick reply after my previous message… I managed to figure it out. Before adding the new integration, I edited the const.py file in the homeassistant container (/usr/src/homeassistant/homeassistant/components/growatt_server/) and changed from:

https://server.growatt.com to https://server-api.growatt.com.

I then restarted and re-added the Growatt integration. All seems to be up and running for now.

I had the same issue, same error, until yesterday morning:

I Just changed /config/.storage/core.config_entries Look for the GroWatt part and changed: From: server.growatt.com To: server-api.growatt.com

Both are reachable from the browser, but evidently the top one not via Home Assistant, for a to me unclear reason. (Via: home-assistant/home-assistant.io#23705)

I just tried this as well, and i agree, my integration started to work. I have no idea if it will be stable, but it was not working before, and 3 restarts did not do anything.

This might also be why the app is working, if the app is polling the server-api address.

Aside from the “normal” “Server timeout” that i have been getting on the app for some time, that will go away if i refresh, the app has always shown the right data, even when the HA integration refused to show anything.

Just reporting initial results from changing to grott (https://github.com/johanmeijer/grott) to get rid of server.growatt.com: Grott is installed and running. Data goes directly from shineWifi to a windows computer running the grott python script, which publishes the data on MQTT which I then use in HA. Grott relays to Growatt so the shinePhone app is still useful.

@mahmoud-os93: according to the docs Grott can handle two inverters - I don’t have two inverters to test.

I will run this for a couple of days to see if it’s stable in my setup and report back.

it stop working after update HA this morning