Is this still working? #112
Comments
Firstly, the owner/maintainer of this repository (@MickMake) has not been active since 2023 so that explains why nothing on the repository has changed recently. I do not know why MickMake has not been active. I also have no knowledge of when, or if, that situation is likely to change. If anyone else has any insights into this, they have yet to share their knowledge. We're all in the dark. Secondly, although the foregoing explains why the first two images have not been updated, to the best of my knowledge the remaining images are the product of GoSungrow and Home Assistant, so there would seem to be no good reason why those would be affected by changes to the iSolarCloud app UI.
GoSungrow still works. Some people report problems such as you'll see being explored in #111. The working hypothesis at the moment is that the people having trouble are more likely to have either multiple inverters, or have replaced an inverter and their existing iSolarCloud account holds both historical and current data. A comment on issue 111 earlier today reported success deleting bogus plant data. I have no idea about the relative proportions of users who have no trouble with GoSungrow in its current form, vs those who can't get it to work. I'm in the former group.
Please read this gist. At least one of the four use cases summarised at the top probably covers what you want to do. The gist includes the new API key ( Someone else also posted a comment to issue 101 which included I'm using the A lot of what is in the gist I mentioned above may seem overly-complicated at first glance and it probably is. However, it's the product of what various contributors have the skills, time and willingness to do. In an ideal world we (the community of users) would know what is behind MickMake's inactivity and then be in a better position to decide whether to fork the repository. But that would also depend on someone wanting to step up and take ownership of processing pull requests, debugging problems, building release artifacts, distributing Docker images for Home Assistant, and so on. That's a big commitment and nobody has yet put up his/her hand to accept that responsibility. In short, the situation now is the best we can do. |
|
Thank you for the answer :-)
biggest problem now is to get the API key
cant get in contact with the right people that can actually send it to me
from Sungrow :-/
ill test to get it working when i finally get the key
\\Thomas
Den ons. 24. apr. 2024 kl. 09.22 skrev Phill ***@***.***>:
… I see that all the pictures are from the "old" interface from Sungrow
Firstly, the owner/maintainer of this repository ***@***.***
<https://github.com/MickMake>) has not been active since 2023 so that
explains why nothing on the repository has changed recently. I do not know
why MickMake has not been active. I also have no knowledge of when, or if,
that situation is likely to change. If anyone else has any insights into
this, they have yet to share their knowledge. We're all in the dark.
Secondly, although the foregoing explains why the first two images have
not been updated, to the best of my knowledge the remaining images are the
product of GoSungrow and Home Assistant, so there would seem to be no good
reason why those would be affected by changes to the iSolarCloud app UI.
is this still working with the new version they have released "isolarcloud"
GoSungrow still works. Some people report problems such as you'll see
being explored in #111 <#111>.
The working hypothesis at the moment is that the people having trouble are
more likely to have either multiple inverters, or have replaced an inverter
and their existing iSolarCloud account holds both historical and current
data. A comment on issue 111
<#111 (comment)>
earlier today reported success deleting bogus plant data.
I have no idea about the relative proportions of users who have no trouble
with GoSungrow in its current form, vs those who can't get it to work. I'm
in the former group.
also i can not find anywhere to download the api key
Please read this gist
<https://gist.github.com/Paraphraser/cad3b0aa6428c58ee87bc835ac12ed37>.
At least one of the four use cases summarised at the top probably covers
what you want to do. The gist includes the new API key (
B0455FBE7AA0328DB57B59AA729F05D8).
Someone else also posted a comment to issue 101
<#101 (comment)>
which included ANDROIDE13EC118BD7892FE7AB5A3F20 and said it worked.
I'm using the B0… key. I have not tested the ANDROID… key.
------------------------------
A lot of what is in the gist I mentioned above may seem overly-complicated
at first glance and it probably is. However, it's the product of what
various contributors have the skills, time and willingness to do.
In an ideal world we (the community of users) would know what is behind
MickMake's inactivity and then be in a better position to decide whether to
fork the repository. But that would also depend on someone wanting to step
up and take ownership of processing pull requests, debugging problems,
building release artifacts, distributing Docker images for Home Assistant,
and so on. That's a big commitment and nobody has yet put up his/her hand
to accept that responsibility.
In short, the situation now is the best we can do.
—
Reply to this email directly, view it on GitHub
<#112 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AVMLI3ZTMCABG5FSRHNXRMLY65MSBAVCNFSM6AAAAABGWHLDRWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANZUGI2TCMJYGM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
The API key is As I said, it's in the gist. |
|
Yes i see :-). Still dont work.
Will not connect.:-/
|
|
You are going to have to provide more information. How are you trying to run GoSungrow? Are you doing it as the "add-on" in Home Assistant, or are you running the standalone binary? If you are using the add-on, have you followed Part 2 of the gist? What do you see in the log inside Home Assistant? If you are running it standalone, what is it saying when you try to run it? Did you recompile it yourself (gist part 1) or did you download a patched binary (gist part 3)? Either way it's a good idea to sanitise your email address, iSolarCloud username and password before you post anything here. And, when you post log messages here, please remember to put the text inside triple-back-ticks (known as "code fences"), like this: ``` Putting stuff between triple-back-ticks means it appears "as is" and doesn't wrap the lines of text. It makes it much easier for someone else (like me) to see what is going on. |
|
So yes i use the "plugin" in HomeAssistant. i get the error i have also tried with the .com adr so there is more life in the .com but i cant get rid of the "secure" error problem is that i am running on the european server. \Thomas |
|
Assuming you're in the EU, you need to set the gateway to: Compare the correct URL (above) with the incorrect URL you have been using, below: I am pretty sure it's that "au" after the "//" that is your problem. I only know of two valid URLs. There's the EU one above and |
|
yes it tries to connect but same problem. f.... i give up :-( |
|
"Request is not encrypted" is the direct result of not having performed all of the steps in gist part 2. If you firmly believe you have done that then, please do this:
Paste the output into your reply between triple-back-ticks. |
|
Ill try again. Might have gotten something wrong following the guide
Den fre 26 apr. 2024 11:55Phill ***@***.***> skrev:
… "Request is not encrypted" is the direct result of not having performed
all of the steps in gist part 2
<https://gist.github.com/Paraphraser/cad3b0aa6428c58ee87bc835ac12ed37#encryptionhack>
.
If you firmly believe you have done that then, please do this:
1. Connect to Home Assistant.
2. Go into the Advanced SSH & Web Terminal.
3. Type the command:
docker images
Paste the output into your reply between triple-back-ticks.
—
Reply to this email directly, view it on GitHub
<#112 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AVMLI34WIAEYOXV2VVEO2DDY7IQCBAVCNFSM6AAAAABGWHLDRWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANZZGA2DGNRVG4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
yeah so i might have messed up something last time. Sungrow API EndPoint not yet implemented |
|
WT..... after 5 restarts and trying different options on the server connection it suddently connected ! ?? i have no idea what i did |
|
A couple of people have reported "EndPoint not yet implemented". See #19 and this gist comment. The following search suggests the message is probably coming from GoSungrow rather than iSolarCloud: At a guess, it likely means the iSolarCloud API has returned an endpoint (a metric) that GoSungrow doesn't know how to handle. As to why it has gone away, your guess is as good as mine. The lack of ongoing complaints in those two hits I mentioned above suggests it is transient rather than persistent. Will it come back? No idea. However, if it does, I will only be able to give you the same answer which boils down to "no idea". Sorry I can't be more help. |
|
And again.. Hello @ALL ! use GoSungrow config write --appkey ANDROIDE13EC118BD7892FE7AB5A3F20 and it works ;-) Greetings :) |
That was the solution for me!!! |
|
I had done the docker image swap fix a few months back. And for the record, I'm using the key |
|
Hmmm. So now we have @stniemin giving us a classic case of the exception proving the rule. My hypothesis of a 1:1 relationship between an AppKey and an iSolarCloud server goes straight out the window. There must be another explanation. Every time I look at the New hypothesis: There is a relationship between the AppKey each person needs to use and the platform that person employed when first setting up the iSolarCloud account (or, perhaps, registering the most-recent inverter). In my own case, after my (first and only) Sungrow inverter was set up, I used the iSolarCloud app on my iPad to do all the setup steps. In other words, I used iOS (or, if you're an Apple purist, iPadOS) and the What's the story with anyone (eg @jangoetz @Sn0w3y @grechi-diego) who has found they need to use the |
I can confirm that I did my first Setup on an Android device... |
|
i used all still working :-) |
|
@BlueScreenTT and did you do your original setup with an iOS device or an Android device? |
|
So. The Electrician responsible for the installation did the config in his app on an Android Phone and then shared the installation with me. |
|
L'ho configurato con un dispositivo Android
Il gio 2 mag 2024, 12:17 Phill ***@***.***> ha scritto:
… @BlueScreenTT <https://github.com/BlueScreenTT> and did you do your
original setup with an iOS device or an Android device?
—
Reply to this email directly, view it on GitHub
<#112 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AO6MNOFJ7DISX2JP4TIZUATZAIHFBAVCNFSM6AAAAABGWHLDRWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJQGEYDANRYGU>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
To throw a further spanner into the hypothesis works: I set up my iSolarCloud environment originally with my iPhone, and have never involved an Android device in the process. However, I've just returned to tinkering with this after a while of leaving it be, and in reading through solutions for the API error I've tested the ANDROID api with the augateway.isolarcloud.com host, and it successfully connects. So I'm totally not sure what significance that name has to the end user. Maybe it was involved in the creation of the api at the other end? |
Hi
I see that all the pictures are from the "old" interface from Sungrow
is this still working with the new version they have released "isolarcloud"
also i can not find anywhere to download the api key
\Thomas
The text was updated successfully, but these errors were encountered: