nswfugitive
Member
I see the TEG-XXX but it is on it's own network and I do not have the password. Anyway, thanks. I will try to figure it out.
The password is your serial number on the inside door of your gateway.
You can install our site as a web app on your iOS device by utilizing the Add to Home Screen feature in Safari. Please see this thread for more details on this.
Note: This feature may not be available in some browsers.
I see the TEG-XXX but it is on it's own network and I do not have the password. Anyway, thanks. I will try to figure it out.
I see the TEG-XXX but it is on it's own network and I do not have the password. Anyway, thanks. I will try to figure it out.
This is really perplexing me. I am assuming the gateway is connected by Wi-fi. But I cannot see it connected I tried to view DCHP leases using ipconfig and also by typing the router ip address in my browser. I only have 9 wireless devices connected to my router but non of them are the powerwall. It's not connected by Ethernet. So I have no idea.You're not looking at DHCP leases, you're looking at W-Fi networks. How is your gateway connected to your network? Wi-Fi or Ethernet or not at all?
This is really perplexing me. I am assuming the gateway is connected by Wi-fi. But I cannot see it connected I tried to view DCHP leases using ipconfig and also by typing the router ip address in my browser. I only have 9 wireless devices connected to my router but non of them are the powerwall. It's not connected by Ethernet. So I have no idea.
Works! thank you. I tried logging into the TEC-xxx but I did not put the letter S before the serial number. Once I did that I was able to log in. I used the arp-a command to find the ip address. So now I am up and running.Tesla doesn't like to use Wi-Fi because spotty connectivity becomes a support issue, so they prefer Ethernet or LTE. There's a good chance they just connected it using LTE. If there's a strong Wi-Fi signal from your house where the gateway is located, you can reconfigure it to use Wi-Fi. Or alternatively (and probably a better idea), you can connect a computer to that TEG-xxxx network using Wi-Fi. You won't have Internet access (maybe use two Wi-Fi adapters at once if you need that), but you'll be able to access the API. The password for the TEG network is the gateway serial number. It looks something like ST17G#######. Once you've connected to that network, you can connect a browser to the gateway's IP address. I don't recall what that is off-hand, but hopefully someone else can chime in with it, or I can explain how you can figure it out. (Hint: It will be in your arp table right after you connect, and it might also be your computer's gateway address.)
Thanks. I have found the gateway ip address so now I can check out PVOutput.I am using PVOutput to log the house load, PW SoC, solar and grid. I am using an old laptop to poll the Backup Gateway, using the monitor service from PVOutput. You will need IP address of the Backup Gateway.
Besides WiFi and Ethernet, PW can also connect to internet via cellular service. If that is the case, you won't find the Backup Gateway on your LAN.
We should form a team. Is there a TMC team on PVOutput?Thanks. I have found the gateway ip address so now I can check out PVOutput.
We should form a team. Is there a TMC team on PVOutput?[/QUdOTE]
Good idea. There's no team that I know of. I am trying to produce the field test data required by SGIP when/if they come to do a field test inspection for the final ICF documentation. It may be unnecessary if Tesla plays nice and supplies it for us. But even so it is really cool to view detailed Powerwall stats.
It wasn't developed when I started to use it. If it was available, I'd have considered it strongly. Now, it would take me more time to learn than just using my own system.I'm a bit amused that people continue to develop a way to monitor their PW2 when it has been developed and refined on pvoutput.org. I guess it boils down to the ownership of the data, it really is the only explanation I can come up with - feedback though about the subject is appreciated.
Yes, I noticed that a few weeks ago. I didn't have time to investigate.Others reported that their reserve percentage changed when they were upgraded to 1.10.2; This also happened to me. I had the reserve at 25% and it was knocked down to 21% if my memory serves correctly. I adjusted it back to 25% and it's remained there.
I decided to write some software this evening to scrape data from the Gateway's API and stuff it into InfluxDB, and before I even got started, I noticed that the API shows "SOE" is 27.45%, yet the phone app shows 24%. The Gateway itself shows 27%. Anyone else seeing this?
It's as if they decided to start reserving some of the PW2 capacity.
I noticed something similar. As many of you, I moved the cutoff point after Tesla's change. Right now I have it set to 34% (in the app), and last night it stopped at 36% (from the pack reading). The numbers I recorded are:After testing for a few days, I can confirm that 33.50% is consistently the point at which my Powerwalls stop discharging when the reserve is set to 30%.
Thank you. That is a great instruction manual.
One way to do this is look at how the PowerWalls are plugged in, and then find a computer in your home that is also attached the same way, and then look at the computer's IP# (could be any device that tells its own IP: computer, smartphone, television, etc.), and then just try every IP# around that IP#. Such as if your IP# is:Thanks. I have found the gateway ip address so now I can check out PVOutput.
Thank you. That is a great instruction manual.
However, it doesn't say how to do it for homes who do not pay Bill Gates tax.
If you investigate a little further, you'll find that the pvoutput integration service is written in java. Presumably it could run on whatever system you're using instead.
https://${pwGateWayLANhost}/api/system_status/soe
COALESCE(percentage, (percentage_charged*.96)+4, ((CAST(energy_left AS FLOAT)/total_pack_energy)*96)+4)
percentage_charged = ((CAST(energy_left AS FLOAT)/total_pack_energy)