Sounds great! Any chance to tie into more granular data, e.g. microinverters?
All the best,
BG
-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
Netzero App
- Thread starter offandonagain
- Start date
All the best,
BG
Yes, that would likely follow as part of the Enphase integration. That integration is currently on hold because of some issues I found with their API. But once they resolve those issues, I'll return to it.
That should be possible with a Powerwall+ at least, but may require a direct wifi connection. Do you have a gateway and are able to connect to it directly? What do you currently see in diagnostics?
We have a gateway 1 with two powerwall 2’s. We get the following under Diagnostics:
Attachments
jgleigh
Member
Does Netzero have support for the tedapi (Tesla One/Tesla Pros)? The normal local API only shows the first PW+ (I have two) every since FW 23.44.x.
Yes, tedapi is supported. You have to connect to the built-in wifi however, using the Scan QR Code option in the app.
You could try the Scan QR Code option, or use the Tesla One app to connect to your gateway or directly to your standalone inverters. But I believe string diagnostics require a Powerwall+.
jgleigh
Member
I'll have to try again. I was only seeing one of my two PW+ when connected to the Gateway WiFi like it was using the old local API and not the tedapi. Not sure if I'm doing something wrong on my end or not. I can see the strings on both PW+ when connected through Tesla One.
Oh, maybe I misunderstood. Does tedapi only work when using Scan QR Code and not when logging into the Gateway via a password?
Last edited:
Exactly, tedapi only works over the internal 192.168.91.1 network and requires the TEG wifi (via the QR code). The wifi hopping makes it inconvenient and has some reliability issues, but should work.
jgleigh
Member
I understand why it needs 192.168.91.1, but why does it require the QR code? Shouldn't connecting to the Gateway WiFi and using that IP address work the same way? Or is that just how the logic is coded in the app?
jgleigh
Member
I got it working. Looks like your app makes the decision to use local api or tedapi based on the QR Code button. Someone posted an online QR Code generator so I didn't have to go outside. Created the QR Code, printed it out, scanned it with Netzero and it pulled the tedapi data. Finally able to see strings on both my PW+ again. Thanks!!!
Glad you got it working! The reason the app wants you to go through that flow is that you don't have internet access on the TEG wifi. So if you connect to that wifi manually and then start the Netzero app, it might not be able to load. Once you successfully scan the QR code from the app, it should remember the credentials and give you an option to reconnect to the wifi without scanning the code. You just have to be near the gateway, of course.
It's all pretty convoluted, really unfortunate how Tesla locked this down.
jgleigh
Member
Yeah they clearly don't want people actually finding out when their systems go down! Or were never installed properly in the first place. I've become an expert troubleshooter with my system. Easier and faster than trying to get Tesla to a) understand the issue, b) send someone out, c) explain the issue again to the tech who wasn't told anything, d) hope it's a quick fix and they know what they're doing.
I clearly need more sleep, because you're the one who posted the QR Code link over on Reddit. I just couldn't remember where I found it after I bookmarked it.
It did glitch trying to jump back onto my home WiFi, but that's a very minor thing to deal with.
Yeah they clearly don't want people actually finding out when their systems go down! Or were never installed properly in the first place. I've become an expert troubleshooter with my system. Easier and faster than trying to get Tesla to a) understand the issue, b) send someone out, c) explain the issue again to the tech who wasn't told anything, d) hope it's a quick fix and they know what they're doing.
I clearly need more sleep, because you're the one who posted the QR Code link over on Reddit. I just couldn't remember where I found it after I bookmarked it.
It did glitch trying to jump back onto my home WiFi, but that's a very minor thing to deal with.
I have a slightly different perspective. For a device that is connected to the internet, Tesla has gone to quite a bit of effort to make sure that our Powerwalls aren't easily accessed by anyone other than the owner and Tesla. To me, that is above average for an Internet of Things device, and appropriate for a device that could cause both local and not so local issue if it were reconfigured by a bad actor.
I'm thankful.
All the best,
BG
I'm all for improved security, but I think this is a generous interpretation of the changes that were made recently. For PW3, the system is effectively not accessible by the owner other than using the Tesla app -- the built-in wifi credentials are hidden behind a cover that the owner should not be removing, and the system is not accessible from the home network. In the case of a Tesla outage or internet/cellular outage, you would not be able to monitor or control your PW3 system at all. I worry PW+/PW2 systems are moving in that direction too.
The changes seem more about streamlining support than improving security. They're moving to a world where Tesla app is for customers, and Tesla One for installers. In the process customers will lose offline access, and power users are locked out. Some other recent changes like removing the vitals endpoint from gateway API, or removing battery capacity from the Fleet API seem like deliberate choices to lock out power users (they do nothing to improve security).
There's a way to design systems to be secure, available offline, and power-user friendly, but it takes some effort. This is one of the (rare) examples where Enphase engineering did better: Accessing IQ Gateway.
jgleigh
Member
PW3 seem more secure since they hide the password, but with PW+ the password is printed on the cover and it's only five characters anyway. A lot of the devices are located outside and easily accessible. You certainly can lock the covers, but most people aren't going to do that.
OCJeff
Active Member
@offandonagain
Can there be an option in NetZero to disable all automations during VPP events? During these events the Powerwall is more or less under the control of Tesla, and will discharge to the grid during the event.
I noticed today when my Powerwall was on self powered mode with a 23% charge (reserve set to 10%) but it was not draining the batteries (VPP event was active for 12 hours later 7pm-9pm). It was putting solar into the house and pulling the excess drain from the grid. Allowing the Powerwall to maintain it's charge (waiting for the sun to rise essentially).
I'm not sure what would happen if NetZero started throwing all sorts of config changes at the Powerwall while it's under a VPP (would it optout/cancel the VPP automatically?
Can there be an option in NetZero to disable all automations during VPP events? During these events the Powerwall is more or less under the control of Tesla, and will discharge to the grid during the event.
I noticed today when my Powerwall was on self powered mode with a 23% charge (reserve set to 10%) but it was not draining the batteries (VPP event was active for 12 hours later 7pm-9pm). It was putting solar into the house and pulling the excess drain from the grid. Allowing the Powerwall to maintain it's charge (waiting for the sun to rise essentially).
I'm not sure what would happen if NetZero started throwing all sorts of config changes at the Powerwall while it's under a VPP (would it optout/cancel the VPP automatically?
I can add that, although I'd be surprised if configuration changes have any impact. VPP takes precedence over other settings and maintains its own backup reserve.
For peace of mind, you can pause any automations during tonight's event. I'm also participating in the event and will in fact schedule a few changes during that time to confirm no impact.
OCJeff
Active Member
Thanks! I did pause all of my automations. I would expect that only Self-Power or Time Based Controls could impact how it operates, but I agree that all settings may be disregarded. I don't see the reserve settings having an impact.
Similar threads
