"Unexpected response: 403 User does not have adequate access rights"

[eoddc5]

I haven't seen this happen before, and nothing has changed. But all of a sudden, I am getting this error about access rights.

Nothing seems to be changed or not working correctly, so I'm not sure if this is a random error or something that needs remediation.

I'm not sure what to change, though. Any thoughts?

[eoddc5]

@datMaffin - hi just wanted to see if you had any ideas here?

[11/15/2022, 10:14:57 AM] [Tesla Powerwall] Login successful [11/15/2022, 10:14:57 AM] [Tesla Powerwall] Unexpected response: 403 User does not have adequate access rights [11/15/2022, 10:14:57 AM] [Tesla Powerwall] Unexpected response: 403 User does not have adequate access rights [11/15/2022, 10:14:57 AM] [Tesla Powerwall] Unexpected response: 403 User does not have adequate access rights [11/15/2022, 10:14:57 AM] [Tesla Powerwall] Unexpected response: 403 User does not have adequate access rights [11/15/2022, 10:14:57 AM] [Tesla Powerwall] Unexpected response: 403 User does not have adequate access rights [11/15/2022, 10:14:57 AM] [Tesla Powerwall] Unexpected response: 403 User does not have adequate access rights [11/15/2022, 10:14:57 AM] [Tesla Powerwall] Unexpected response: 403 User does not have adequate access rights [11/15/2022, 10:14:57 AM] [Tesla Powerwall] Unexpected response: 403 User does not have adequate access rights [11/15/2022, 10:14:57 AM] [Tesla Powerwall] Unexpected response: 403 User does not have adequate access rights [11/15/2022, 10:14:57 AM] [Tesla Powerwall] Unexpected response: 403 User does not have adequate access rights [11/15/2022, 10:14:57 AM] [Tesla Powerwall] Unexpected response: 403 User does not have adequate access rights

[datMaffin]

Sorry, I have not seen this.

https://github.com/vloschiavo/powerwall2/issues/45 seems kind a similar, though.

[langabi]

I have similar issues:

• sometimes powerwall seems to entirely forget its local customer password, and I have to do password reset on the local gateway web interface (including toggling the power switch on the powerwall)
• sometimes it seems the powerwall temporarily starts giving 403 errors. If I stop the homebridge connection, it will sometimes start working after several hours, suggesting one of random chance, some sort of anti-DoS protection, or just capacity issues in the powerwall's server.

No cause I've been able to isolate, though losing grid power (ie going to backup mode) seems sometimes to be a possible trigger (but not always). Tesla support have not been able to understand the issue, they think it's a Tesla app login issue (which it clearly isn't)

[pponce]

I noticed i'm getting the same error "Unexpected response: 403 User does not have adequate access rights" I also see the "Login successful" message.

[rob0101]

Lots of these for me too:

[12/14/2022, 1:37:18 PM] [Tesla Powerwall] Unexpected response: 403 User does not have adequate access rights

[datMaffin]

I do not like seeing this...

I also do find it kind of weird that it only seems to be an issue here... When looking at the other places, like the home-assistent integration, there seem to be no complains.

[ravisab]

I was running into this error too, and the plugin was not able to connect at all. I connected to the powerwall IP, selected the option to log in as customer, then selected the option to reset the password. Then I added the newly set password into the config. The plugin was able to connect after this even though I still get the "Tesla Powerwall] Unexpected response: 403 User does not have adequate access rights" messages at start up. They are followed by "[Tesla Powerwall] Login successful". I am able to see the solar production, home usage etc in accessories, so the errors might be coming from some other misconfiguration in my config

[ravisab]

Further - I went to the config described in the readme.md - "Using only Home.app supported services (all the visualization services)" and the errors about "adequate access rights" have all gone away.

[ravisab]

Pasting my config with the hope it will help someone -

        {
            "platform": "TeslaPowerwall",
            "name": "Tesla Powerwall",
            "ip": "<IP of your powerwall>",
            "password": "<PASSWORD FOR customer set using web interface at above IP, NOT your tesla app password>",
            "username": "customer",
            "email": "",
            "loginInterval": 39600000,
            "pollingInterval": 60000,
            "lowBattery": 15,
            "additionalServices": {
                "powerwall": {
                    "eveHistory": false
                },
                "solar": {
                    "evePowerMeter": false,
                    "eveHistory": false
                },
                "grid": {
                    "positiveEvePowerMeter": false,
                    "negativeEvePowerMeter": false,
                    "eveHistory": false
                },
                "battery": {
                    "positiveEvePowerMeter": false,
                    "negativeEvePowerMeter": false,
                    "eveHistory": false
                },
                "home": {
                    "evePowerMeter": false,
                    "eveHistory": false
                },
                "gridstatus": {
                    "gridIsDownSwitch": false,
                    "gridIsUpSwitch": false,
                    "gridIsNotYetInSyncSwitch": false,
                    "gridIsDownSensor": true,
                    "gridIsUpSensor": true
                }
            }
        }

[davemacaulay]

I get a similar error, and I believe it's because I have a Powerwall 3, instead of a Powerwall 2.