Open bensuthers-au opened 2 years ago
Thanks for reporting an issue!
The behavior described by you does sound kind of weird. However, I can not find similar reports. Especially https://github.com/vloschiavo/powerwall2/issues was always fast to have a discussion about breaking changes, and they do not (yet?) seem to have similar issues.
If you figure anything out or the behavior just seems to correct itself, please report back to this issue.
I might close this issue in the future if there does not seem to be any update/development regarding this issue.
No problem. I have adjusted the login interval to see if it has an impact and am just watching.
Thanks for the reply.
Ben
Sent from my iPhone
On 10 Nov 2021, at 10:00 am, Marvin Dostal @.***> wrote:
Thanks for reporting an issue!
The behavior described by you does sound kind of weird. However, I can not find similar reports. Especially https://github.com/vloschiavo/powerwall2/issues was always fast to have a discussion about breaking changes, and they do not (yet?) seem to have similar issues.
If you figure anything out or the behavior just seems to correct itself, please report back to this issue.
I might close this issue in the future if there does not seem to be any update/development regarding this issue.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.
Hi there. I just tried installing this and am actually running into the same issue.
@bensuthers-au did you figure anything out from this?
The plugin was working for me but now I'm getting the same 403 error.
After a little bit of debugging I found that adding the optional email line to the config fixed the issue.
Wow - sorry for the lack of reply - I’ve been away.
I will give this a shot and see what happens!
On 30 Dec 2021, at 7:12 pm, Felipe Salum @.***> wrote:
After a little bit of debugging I found that adding the optional email line to the config fixed the issue.
— Reply to this email directly, view it on GitHub https://github.com/datMaffin/homebridge-tesla-powerwall/issues/33#issuecomment-1002918612, or unsubscribe https://github.com/notifications/unsubscribe-auth/AT46RJZJLNXAQVOIHJROH3DUTQIATANCNFSM5HORXALA. Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you were mentioned.
I also get this issue. It seems to self-correct after a while, and anecdotally it seems to be most common right after a HB restart.
I am experiencing this issue. I am on Powerwall firmware 22.18.3
and have tried with email
set and not set. I have updated the password on my Powerwall and in my Homebridge config, but the error persists.
Hello,
After a few months of working fine, we're now on power wall build 21.35.0 and I am having to login to the powerwall via web browser on the PI in order to enable the connection.
The log shows
06/11/2021, 6:31:01 am] [Tesla Powerwall] error: null [06/11/2021, 6:31:01 am] [Tesla Powerwall] status code: 403 [06/11/2021, 6:31:01 am] [Tesla Powerwall] body: {"code":403,"error":"Unable to GET to resource","message":"User does not have adequate access rights"}
but once I log in on the homebridge machine to the power wall the plugin can login again.