Skip to content
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

21.20.2 seems to have broken it again #18

Open
Gerynant24 opened this issue Jun 28, 2021 · 7 comments
Open

21.20.2 seems to have broken it again #18

Gerynant24 opened this issue Jun 28, 2021 · 7 comments

Comments

@Gerynant24
Copy link

Looks like my powerwall was update this afternoon and now the cookie approach doesn't seem to work any more.

Any suggestions welcome?

@ssossam
Copy link

ssossam commented Jul 2, 2021

My Powerwall 2 was upgraded today at midnight and now the dashboard is blank. I concur 21.20.2 busted things again.
Let me know if you want me to test and I will. Thanks

@ssossam
Copy link

ssossam commented Jul 2, 2021

My Powerwall 2 was upgraded today at midnight and now the dashboard is blank. I concur 21.20.2 busted things again.
Let me know if you want me to test and I will. Thanks

Wanted to post a CORRECTION !!! The Powerwall IP address changed. I changed the IP address in the yml file and did a docker-compose with the new version. The just to be safe, I did the Influxdb commands to query the system. I also changed my /etc/hosts file on my Macbook and restarted the containers and I am now getting data. Sorry for the confusion.

@Gerynant24
Copy link
Author

I’ve made a discovery too, my method was looking for an error an updating the cookie, but the error has changed. Updated the cookie and all is good.
Sorry for the false alarm!

@nwhobart
Copy link

nwhobart commented Jul 4, 2021

I’ve made a discovery too, my method was looking for an error an updating the cookie, but the error has changed. Updated the cookie and all is good.
Sorry for the false alarm!

Which image are you seeing an error? I can't seem to figure out where I'm erroring out as nothing has changed for me (IP is static).

@Gerynant24
Copy link
Author

I test the link to the PW periodically to see if it is accessible. My code was looking for the word “error” in the response and the rebuilding the config file with a new cookie. (The full message was something like “error you don’t have sufficient rights”.) Since the new FW update it looks like the PW just no longer responds with anything. I haven’t had much time to look at the detail but I’m going to switch from looking for an error to looking a correct response.

@nwhobart
Copy link

nwhobart commented Jul 4, 2021

My code was looking for the word “error” in the response and the rebuilding the config file with a new cookie

I missed the whole cookieproxy image somehow. tailed the logs of that and noticed the IP was wrong. I have no idea how that got changed/updated in the powerwall.yaml file but it's fixed now. weird. thanks for the help. :)

@nswfugitive
Copy link

My implementation hasn't broken it. Have you considered expanding the capability to send data to pvoutput.org? This implementation seems to be the most reliable and would love having something that is reliable to send to pvoutput.org. Help :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants