New Install-Web UI Credentials?

[Damclarkd]

Just finished a 3rd party install of solar and 2 PW's here in AZ. Do not have PTO yet so only have tested at end of install. My question is; I have installed the Tesla app (IOS), set password, logged in and everything looks fine. I have both wi-fi and wired ethernet to the TEG. Today I tried to login to the Web UI and it reports my credentials are incorrect.
Are there different credentials for a customer login on Web UI?

Thanks!

 

[mnsweeps]

The TEG password is on the inside. Open the TEG door and you would see. The TEG password is different from you app password. Apologize if I misunderstood your question.

 

[Damclarkd]

The TEG password is on the inside. Open the TEG door and you would see. The TEG password is different from you app password. Apologize if I misunderstood your question.

No, you understood and that makes sense. Now I another issue but it is going back to the installer. He lined out the original PW and wrote a separate one in. Neither worked. Off to contact the installer.

Thanks very much for your quick reply.

Dennis

 

[cwied]

The password the installer wrote down might be for the installer login, not the customer login. There isn't really a lot you can do with a customer login, apart from reconfiguring the network. Is there something specific you're looking for in the web UI? For me, the most useful part is what you see without logging in at all.

Edit: Here is Tesla's instruction page for connecting to the local UI, in case you haven't seen it: Connecting to Tesla Gateway | Tesla Support

 

[Damclarkd]

The password the installer wrote down might be for the installer login, not the customer login. There isn't really a lot you can do with a customer login, apart from reconfiguring the network. Is there something specific you're looking for in the web UI? For me, the most useful part is what you see without logging in at all.

Edit: Here is Tesla's instruction page for connecting to the local UI, in case you haven't seen it: Connecting to Tesla Gateway | Tesla Support

This is purely preemptive on my part. Trying to make sure all is correct and I have any access I might need going forward. Thinking about advanced data collection through the API and from I read I would need to enter credentials there.

Thanks for the link. Reading now.

Cheers!

 

[Damclarkd]

The password the installer wrote down might be for the installer login, not the customer login. There isn't really a lot you can do with a customer login, apart from reconfiguring the network. Is there something specific you're looking for in the web UI? For me, the most useful part is what you see without logging in at all.

Edit: Here is Tesla's instruction page for connecting to the local UI, in case you haven't seen it: Connecting to Tesla Gateway | Tesla Support

LAST FIVE OF THE PW is what did the trick!
All looks good now.

Cheers!

 

[cwied]

For data collection, you don't need to log in. The main reason to log in used to be for automation, and it appears in the newest software version they don't allow changes to the settings (other than netwrok) without first physically toggling the switch on one of the Powerwalls (to avoid remote attacks).

The most useful data are available at https://<powerwall-ip>/api/meters/aggregates and https://<powerwall-ip>/api/system_status/soe - these are the REST endpoints used by the page you see before logging in. These are what I log to influxdb to drive historical graphs such as this:

 

[zƬesla]

@cwied what are you using to get the temp in the chart?

 

[Damclarkd]

For data collection, you don't need to log in. The main reason to log in used to be for automation, and it appears in the newest software version they don't allow changes to the settings (other than netwrok) without first physically toggling the switch on one of the Powerwalls (to avoid remote attacks).

The most useful data are available at https://<powerwall-ip>/api/meters/aggregates and https://<powerwall-ip>/api/system_status/soe - these are the REST endpoints used by the page you see before logging in. These are what I log to influxdb to drive historical graphs such as this:
View attachment 610288

Data is beautiful! Thanks for sharing.

Cheers

 

[cwied]

@cwied what are you using to get the temp in the chart?

That's actually coming from a PurpleAir monitor on the back of my house - it's ambient temperature. I'm also logging the data from the nearest Weather Underground personal weather station for cross-referencing.

 

[mnsweeps]

For data collection, you don't need to log in. The main reason to log in used to be for automation, and it appears in the newest software version they don't allow changes to the settings (other than netwrok) without first physically toggling the switch on one of the Powerwalls (to avoid remote attacks).

The most useful data are available at https://<powerwall-ip>/api/meters/aggregates and https://<powerwall-ip>/api/system_status/soe - these are the REST endpoints used by the page you see before logging in. These are what I log to influxdb to drive historical graphs such as this:
View attachment 610288

Good info. I am just curious about Powerwall charging and its usage. The green line dipping represents your home using stored energy instead of grid?

 

[blueice89]

You can use 2 types of credentials one is
Installer mode, for me I have to go flip power on a powerwall and thats pretty much authentication.

Customer mode: email your email:
Password, for me its last 5 digits of serial number at the bottom of your app, (case senstive).

If you do , do installer mode, I believe if you run wizard or just even logging in installer may stop your powerwall system.
Just make sure to press turn on when you are done with everything.
Turn on can be clicked by customer too.

Tesla has more directions on this if you look it up:
Connecting to Tesla Gateway | Tesla Support

 

[Damclarkd]

You can use 2 types of credentials one is
Installer mode, for me I have to go flip power on a powerwall and thats pretty much authentication.

Customer mode: email your email:
Password, for me its last 5 digits of serial number at the bottom of your app, (case senstive).

If you do , do installer mode, I believe if you run wizard or just even logging in installer may stop your powerwall system.
Just make sure to press turn on when you are done with everything.
Turn on can be clicked by customer too.

Tesla has more directions on this if you look it up:
Connecting to Tesla Gateway | Tesla Support

Thanks!

 

[cwied]

Good info. I am just curious about Powerwall charging and its usage. The green line dipping represents your home using stored energy instead of grid?

I'm in backup-only mode right now. The green line dipping represents the Powerwalls charging in order to replace the "vampire drain" for the previous day or two. I prefer this direction because it is easier to compare the Powerwalls' discharge to the load when they are supplying power.

 

[h2ofun]

That's actually coming from a PurpleAir monitor on the back of my house - it's ambient temperature. I'm also logging the data from the nearest Weather Underground personal weather station for cross-referencing.

I have both a purple air and weather link sensor for air quality. Since we have so many fires here, many use to determine things like will our schools open or our pool

Real-time air quality map | PurpleAir

WeatherLink Home

How did you get that graph out of purple air?

 

[jboy210]

I have both a purple air and weather link sensor for air quality. Since we have so many fires here, many use to determine things like will our schools open or our pool

Real-time air quality map | PurpleAir

WeatherLink Home

How did you get that graph out of purple air?

If you zoom in on a link on the map you can get a link URL by viewing the page source. Mine looks like (API key 111222333 is bogus):
https://api.thingspeak.com/channels/1126654/fields/8.json?start=2020-11-15 10:46:48&offset=0&round=2&average=10&api_key=111222333

This returns a json structure that can be parsed to get the latest series of 10 minute (the 10 above) average readings.

If someone has better documentation please post a link.

 

[cwied]

I have both a purple air and weather link sensor for air quality. Since we have so many fires here, many use to determine things like will our schools open or our pool

Real-time air quality map | PurpleAir

WeatherLink Home

How did you get that graph out of purple air?

I'm using the same technique with the PurpleAir sensor as I am with the Powerwall - logging the data directly from the sensor to influxdb using telegraf. For the PurpleAir sensor, the url is simply http://<ip>/json?live=true. Note that the PurpleAir Wifi radio gets warm, so I had to subtract 7 degrees to get it to track with the Weather Underground sensor. This right offset probably varies depending on how strong the Wifi connection is.

 

[Damclarkd]

For data collection, you don't need to log in. The main reason to log in used to be for automation, and it appears in the newest software version they don't allow changes to the settings (other than netwrok) without first physically toggling the switch on one of the Powerwalls (to avoid remote attacks).

The most useful data are available at https://<powerwall-ip>/api/meters/aggregates and https://<powerwall-ip>/api/system_status/soe - these are the REST endpoints used by the page you see before logging in. These are what I log to influxdb to drive historical graphs such as this:
View attachment 610288

cwied,
I now have a related/unrelated question about Telegraf. Got things set up but Telegraf throws a certificate error. Along the lines of “Certificate is valid for 192.168.90.1, 192.168.90.2.” While my ip range for the gateway is 10.1.xx.xx.

Did you have a similar certificate issue and if so, how did you bypass it?

Thanks!

 

[cwied]

cwied,
I now have a related/unrelated question about Telegraf. Got things set up but Telegraf throws a certificate error. Along the lines of “Certificate is valid for 192.168.90.1, 192.168.90.2.” While my ip range for the gateway is 10.1.xx.xx.

Did you have a similar certificate issue and if so, how did you bypass it?

Thanks!

Yes - just add "insecure_skip_verify = true" to the configuration to get around it.

This is my configuration:

[[outputs.influxdb]]
        urls = ["http://localhost:8086"]
        database = "powerwall"
        skip_database_creation = false
        retention_policy = "raw"

[[inputs.http]]
        urls = [
                "https://192.168.1.x/api/meters/aggregates",
                "https://192.168.1.x/api/system_status/soe"
        ]
        method = "GET"
        insecure_skip_verify = true
        interval = "5s"
        timeout = "4s"
        data_format = "json"

[[processors.date]]
        tag_key = "month"
        date_format = "Jan"

[[processors.date]]
        tag_key = "year"
        date_format = "2006"

 

[Damclarkd]

Yes - just add "insecure_skip_verify = true" to the configuration to get around it.

This is my configuration:

[[outputs.influxdb]]
        urls = ["http://localhost:8086"]
        database = "powerwall"
        skip_database_creation = false
        retention_policy = "raw"

[[inputs.http]]
        urls = [
                "https://192.168.1.x/api/meters/aggregates",
                "https://192.168.1.x/api/system_status/soe"
        ]
        method = "GET"
        insecure_skip_verify = true
        interval = "5s"
        timeout = "4s"
        data_format = "json"

[[processors.date]]
        tag_key = "month"
        date_format = "Jan"

[[processors.date]]
        tag_key = "year"
        date_format = "2006"

Thanks again. Got it up and running.
Cheers!