Replies: 26 comments 190 replies
-
|
I'm working on a protobuf decode and encode tool to help with the investigation. I have the decode.py tool started here: https://github.com/jasonacox/pypowerwall/tree/main/tools/tedapi # Download code
git clone https://github.com/jasonacox/pypowerwall.git
cd pypowerwall/tools/tedapi
# Build python bindings for protobuf schema - tedapi_pb2.py
protoc --python_out=. tedapi.proto
# Decode payload
python decode.py <filename>I'm not a protobuf expert, so I'm pretty sure my work could be improved. I welcome any gurus who want to contribute... 😁 |
Beta Was this translation helpful? Give feedback.
-
|
How was the existing tesla.proto file generated? The messages here seem to be an extension of those proto definitions, e.g.: |
Beta Was this translation helpful? Give feedback.
-
|
Great discovery @zigam ! The tesla.proto was created to unpack the device vitals ( The tedapi.proto should incorporate If I have time today, I planned to create an encode function and a test python script to allow users to fetch their config. |
Beta Was this translation helpful? Give feedback.
-
|
Sounds good. Looks like the gateway web ui |
Beta Was this translation helpful? Give feedback.
-
|
I made some minor updates to use the same language. The payloads in 15 and 16 are still TBD (I picked them) and are missing from tesla.proto. I'll look at that JS to see if it now has any clues. |
Beta Was this translation helpful? Give feedback.
-
|
@zigam that is exactly how I did it before. I can pull them out. |
Beta Was this translation helpful? Give feedback.
-
Tools for tedapi API TestingI created test.py and decode.py scripts to help research tedapi. Both require that you are connected to your Powerwall Gateway WiFi. See here. test.pyThis script (test.py) will prompt you for your Gateway password (on the QR sticker) and will proceed to:
decode.pyThis script (decode.py) is a simple decoder for tedapi probotbuf binary payloads. It will decode the file you specify. This is useful when using curl to download the payloads. Install# Download
git clone https://github.com/jasonacox/pypowerwall.git
cd pypowerwall/tools/tedapi
# Test Script
python test.py
# Decode Script
python decode.py response.bin |
Beta Was this translation helpful? Give feedback.
-
|
I think I was the original provider of the protocol buffer definitions. I pulled them from the compiled JavaScript for the powerwall portal. I can probably help decode these as well. |
Beta Was this translation helpful? Give feedback.
-
|
Yes you were! That has been incredibly useful. Unfortunately, it looks like the device vitals payload will be sunset. Additionally, on this Tesla Pros API, we don't have any JS to reference this time. My attempt is rather basic but with some hints from your original work. My intent on this effort was to find a way to read the same data we were getting with vitals before. |
Beta Was this translation helpful? Give feedback.
-
|
Based on my investigation, I suspect the updated proto files might still be making their way into the gateway JS files. If it's not too much work for @brianhealey, it might be useful to try and extract updated proto files. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the work so far. I noticed something interesting in the "config" output "strategy": {
"control": "lps",
"forecast_method": "exm1dmc",
"forecast_range": 2,
"forecast_output": { "to_cloud": true },
"pv_forecast_method": "exmMaax",
"TOU_mode": "economic"
},Since I'm on Time-Based Control (technically the Tesla Energy VPP in Australia), I think this is the first instance I've seen where the "forecasting" aspect is exposed anywhere. I'm not sure |
Beta Was this translation helpful? Give feedback.
-
|
Do I need to configure my raspberry pi to log into my gateway access point or do the scripts do that for me? I’m guessing |
Beta Was this translation helpful? Give feedback.
-
|
You likely need to install the protobuf module: # Install required dependencies
pip install protobuf requestsAlso, I believe the protobuf was outdated so make sure you Keep in mind, this simulates the Tesla Pros app and requires that you connect to the local access point. It does show some vital data (alerts, etc) but not everything we had in the device vitals payload (it's missing PW temps for example). Because of the odd WiFi access point requirement, I suspect it may not be practical for many. Still, very interesting. As a reminder, for PW 3 owners (and Tesla Solar only owners), you can now get basic metrics working in the dashboard (including the power flow animation), using the new |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
You need to |
Beta Was this translation helpful? Give feedback.
-
|
how to git pull protocolbuffers? eric@raspberrypi:~/Downloads $ git clone https://github.com/protocolbuffers/protobuf.git and then what? got a better, well perhaps, wifi addapter that works with RPi, BrosTrend AX1800. was easy to install drivers. my old addapter seemed to crash after a while, don't know if it was caused by TEG or not. |
Beta Was this translation helpful? Give feedback.
-
|
No, run |
Beta Was this translation helpful? Give feedback.
-
|
finally got test.py to run, don't really know what i did... python test.py``` eric@raspberrypi:~/Downloads/pypowerwall/tools/tedapi $ python test.py Tesla Powerwall Gateway API DecoderConnect to your Powerwall Gateway WiFi. Fetching Configuration from Powerwall... Fetching Current Status from Powerwall... |
Beta Was this translation helpful? Give feedback.
-
|
That's great! Test isn't pulling the full status. You would need to run status.py instead. |
Beta Was this translation helpful? Give feedback.
-
|
i see my neurio data at bottom: Tesla Powerwall Gateway API Decoder |
Beta Was this translation helpful? Give feedback.
-
|
i did notice that neurio solar data needs to be doubled if used to display data. 290w s/b 580w and 7226w s/b 14432w. |
Beta Was this translation helpful? Give feedback.
-
|
That's interesting. It doesn't align with the current or voltage (Power = Current * Voltage ). It wouldn't make sense for it to be half. Your output show two dataRead arrays. Do you have 8 strings? |
Beta Was this translation helpful? Give feedback.
-
|
In my case those are the Neurio RGMs in the inverters. I also have two inverters and 8 strings, and two (it is currently night here) |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, @thekev ! That makes sense. |
Beta Was this translation helpful? Give feedback.
-
|
i have enphase system and tesla inverter measured individually. |
Beta Was this translation helpful? Give feedback.
-
|
can we add a switch in the config file for local "192.168.91.1" and start mining neurio data from the TEG locally? :) |
Beta Was this translation helpful? Give feedback.
-
|
I have my internal tesla wireless connected to the wired network, and can confirm seems to be fully working. This is a backup switch + 2 powerwall+'s, and can see the expected: and obviously much more. this is all on Firmware: 23.44.3-msa. Seems to match to what I see in the pros app. Looks like backup switch/individual neurio data is there too, so really promising. with the network setup, makes it a bit easier to debug. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @ygelfand - Thanks for this. Can you confirm, are you using the TEG-xxx WiFi access point and using the status.py script to pull this data on firmware 23.44.3? Also, are you using a Raspberry Pi (Wired + WiFi) to make this connection? I would be interested to hear from the community on this: How many of you are interested in setting up a dual-homed (LAN + TEG WiFi) box to get this extended data, especially if it was an optional feature for Powerwall Dashboard? |
Beta Was this translation helpful? Give feedback.
-
|
I am using the teg- wifi, and yes the status.py. I have an additional wireless adapter on my proxmox host, and am using pfsense to route 192.168.91.0/24 to it, so my entire lan has access to the Powerwall+ private lan that way. I do run pypowerall/etc a little different, inside k8s, so would need lan-wide access. |
Beta Was this translation helpful? Give feedback.
-
|
Count me in - i have spare PIs @home and am planning to set this up to restore missing string statistics, but just haven’t gotten around to it yet. |
Beta Was this translation helpful? Give feedback.
-
|
Yes please! I miss the vitals api, and this gets back almost all that was being charted. I’m only missing |
Beta Was this translation helpful? Give feedback.
-
|
On RPi, doesn’t seem it matters how you set up the two networks, either wired and wireless; or both wireless. |
Beta Was this translation helpful? Give feedback.
-
|
Very early, but I have string data again! Still working on the rest. Pulled a bunch of stuff from the android tesla one app, as well as definitely lots of great insight here. Does require some way to access that internal wireless from the proxy. https://github.com/ygelfand/go-powerwall and similarly named docker hub image. Listens on :8080 and attempts to emulate the /strings endpoint at /api/v1/strings, so in theory should only need to add to your telegraf config to test. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks @ygelfand ! The docker build is odd... My RPI 4 said it couldn't find a compatible build with arm64 (I see that with pypowerwall too) so I needed to include arm/v8 but arm/v7 means it would also work for 32bit RPi 3's as well. Good call. Related, I couldn't find a definitive list of the build architectures... so I made my own first pass at it https://gist.github.com/jasonacox/ee4402266fc813e7c4c5f1e8a312221c. If anyone finds a good list, let me know. :) |
Beta Was this translation helpful? Give feedback.
-
|
maybe it depends on your cri? I believe normally arm64 is just normalized to arm/v8, but possibly not. I've added endpoints for the remaining of the pypowerwall endpoints to my builds, docker images are up for (tagged this brings back per-string metrics, per-inverter totals, as well as frequency/voltage/etc per inverter/island/msa metrics. No sign of inverter temperature ofcourse, so those are still MIA. |
Beta Was this translation helpful? Give feedback.
-
|
This is great, @ygelfand! I was able to get it running and data started showing up again. I did it using https://go.dev/dl/go1.22.0.linux-armv6l.tar.gz on an extra RPi 4 I had laying around with an extra wifi, so it could connect to both the TEG and my local network. I pointed the telegraf conf to the new URLs for that device and the dashboards updated. When I get some more time, I'll experiment with the docker container and get a more permanent setup going, but the quick test was successful! |
Beta Was this translation helpful? Give feedback.
-
|
I had tried ARM64, but got some "check_for_64_bit_pointer" error. I checked and the OS was 32-bit, so I used this version and it worked fine. I haven't touched go since grad school, so it was fun poking around. |
Beta Was this translation helpful? Give feedback.
-
|
@DerickJohnson great! I don't think I have a spare pi4, my only one runs 64bit. I think I have a spare pi3 somewhere though, will check. I was considering doing pre-built arm binaries if there's interest. I've been running for a couple of weeks here, seems stable for me. |
Beta Was this translation helpful? Give feedback.
-
|
Potential addition to pypowerwall library to help support this investigation: jasonacox/pypowerwall#73 It would be interesting if this works for Powerwall 3 owners and could be a path to get local data access as well as the extended vitals data lost by the recent firmware upgrade for Powerwall 2/+ owners. This would be a "high degree of difficulty / effort" add-on for the project as it would require someone setting up a multi-homed server (RPi, etc.) that connects to Gateway WiFi as well as your LAN. Thanks to @ygelfand's great work, there is good indication that this API is stable. |
Beta Was this translation helpful? Give feedback.
-
|
Can the fleet api code run ont the same RPi as powerwall dashboard? |
Beta Was this translation helpful? Give feedback.
-
No, these are temporary and reset on reboot. I haven't decided how best to handle the setup. Unless someone knows of a way to add the route via a container (for a container, specifically pypowerwall) I assume we would have
|
Beta Was this translation helpful? Give feedback.
-
Based on that it might be easier to direct power users to setup the static route in their router. You could query 192.168.91.1 to ensure it's listening and then direct users how to setup the static route instead of trying to have |
Beta Was this translation helpful? Give feedback.
-
Just to clarify, it doesn't need to be Unifi, any router that a TEG and Client both use capable of adding a static route should be sufficient. The wireless portion of it was simply so I could use Tesla One or Netzero while I was on my couch instead of standing next to the TEG. It's completely unnecessary for any other reasons. I'd be happy to help anyone that is getting stuck with the routing portion along. |
Beta Was this translation helpful? Give feedback.
-
That might be handy! |
Beta Was this translation helpful? Give feedback.
-
I am also away for work at the moment, but I routed that network over a VPN and can access the TEG via the Tesla One app from here (some thousand miles away or so). The same trick also works for the 192.168.90.2 IP that's referenced in the documentation, just needs another route. Could cover both with 192.168.90.0/23 and have all of the bases covered. |
Beta Was this translation helpful? Give feedback.
-
|
I tried
on my Raspberry Pi 4, but received "Error: Nexthop has invalid gateway". It appears this is because my PWD host is on 192.168.0.x and my TEG is on my IOT network at 192.168.2.x. I'm running OpenWRT, so I'm going to try the router-based option that was suggested above, but I wanted to post this in case anyone has a Linux-based solution or failing that, to make sure the others are aware the host-based solution may not work with the TEG on a different subnet. EDIT: I had to add a route on the PI using "sudo ip route add 192.168.91.0/24 via 192.168.0.1" and add static routing on my router to get it to connect from the PI. EDIT 2: I just realized why I needed the extra route on the device. For whatever reason, my PWD stack's "powerwall-dashboard-default" network was using IP subnet 192.168.80.0/20, which includes 192.168.91.x. I shut down the stack, deleted the network, then recreated the stack. The new network was created on 172.18.0.0/16 which doesn't conflict with the gateway IP. All of my other docker networks are in 172.x. I'm not sure what accident of history had PWD using 192.168.80.0/20 In OpenWRT:
As with the example @BJReplay posted, I didn't need to enter a gateway in the last field, but I had to select my IOT network as the interface in the first field. |
Beta Was this translation helpful? Give feedback.
-
|
@jasonacox -- Thank you! I was excited and plopped the gateway password on the PW_PASSWORD line. I added a line for PW_GW_PWD and moved the gateway password there. Logs show the TEDAPI line (yay), but it gets a recurring Exception right after. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks @aristobrat ! Just to make sure, the Thanks for the error! That is actionable. I'm moving this into the PR to track and fix. |
Beta Was this translation helpful? Give feedback.
-
|
Updated: jasonacox/pypowerwall:0.10.1t58-beta4 |
Beta Was this translation helpful? Give feedback.
-
@jasonacox, thanks for the quick fix. It's so great to see string data from both PW+ start to populate! 
|
Beta Was this translation helpful? Give feedback.
-
|
Awesome! Looks great @aristobrat ! |
Beta Was this translation helpful? Give feedback.
-
v4.4.0 Released - Local Vitals and TEDAPII have pushed v4.4.0. Here are the steps to onboard the new version:
Please report any issues (open issue if you can). |
Beta Was this translation helpful? Give feedback.
-
|
@jasonacox - this is awesome. Forgive me if I missed it but do I have to access 192.168.91.1 through the gateways Wi-Fi connection or can I set my pfSense router to use the Ethernet connection to route this IP through? |
Beta Was this translation helpful? Give feedback.
-
@BJReplay the person I was replying to has two TEGs and for the tedapi access to work, the request needs to be passed to 192.168.91.1. They also have a Verizon router which isn't desirable but is working well enough on one gateway. The problem is, each gateway needs to be a next hop for their specific tedapi instance, but the router can't do policy based routing and wouldn't be able to since all of the requests from a docker host would come from the same IP (unless you're attaching the container to the host network) and each host would need its own route. If docker could be configured with a policy based routing system that could differentiate between containers reliably and pass the route through the hypervisor. Are you aware of a way to do that? |
Beta Was this translation helpful? Give feedback.
-
You're attaching the docker host to the host network - covered in the instructions - and each container can be allocated a specific IP if you pre-define a network allowing for some specific network configuration - for example, I'm running HA and Caddy, and I need HA to know which IP to trust as a proxy, so I have Caddy running on a specific IP You can allocate more than one IP to the host, and thus to specific containers via pre-defined networks. That's what I'm doing for caddy, via a pre-defined external network |
Beta Was this translation helpful? Give feedback.
-
|
Trying to get out of this jam.. I am on vacation for a week so won't have an answer for sure but was wondering if I should just use my wifi adapter to connect to the other gateway while keeping the Ethernet connection for everything else? I can even add extra Ethernet adapters if needed. |
Beta Was this translation helpful? Give feedback.
-
@fasternfaster Well, seems like you have a couple of options. You could give either a shot. I could help out with figuring out a second Hyper-V VM and it would be pretty straight forward. Sounds like @BJReplay could help you out with a pure docker solution. Personally, I would do the Hyper-V VM but I am way more comfortable in that world and not a docker expert. |
Beta Was this translation helpful? Give feedback.
-
|
So i connected my WiFi to the second TEG-* gateway and its ip is to no surprise 192.168.91.1 ! Thats for the gateway and DNS on that wifi network. Since i already have that IP setup as a route on my ethernet network i have no way to differentiate. Making requests to that IP, my computer seems to prefer the ethernet and uses the already configured route. Although i can change my own computer's assigned IP i don't have a way to change the "other device's"/ gateway's IP. How can you differentiate the different gateways? |
Beta Was this translation helpful? Give feedback.
-
|
Just wanted to chime in - this is working like a champ!!(PW2 with non-Tesla solar) Thank you so much to Jason and everyone else who has put so much time into this project! |
Beta Was this translation helpful? Give feedback.
-
|
I'm attempting to add Powerwall 3 local API support for pypowerwall. I'm looking for Powerwall 3 owners who want to test: You can also test the docker container (should be compatible with all systems) standalone or in the Dashboard. As mentioned, to see |
Beta Was this translation helpful? Give feedback.
-
How to add New Vitals
Option 1 - SetupRe-run Option 2 - ManualMake the changes that setup would do, manually: Edit PW_EMAIL=
PW_PASSWORD=
PW_HOST=192.168.91.1
PW_TIMEZONE=America/Los_Angeles
TZ=America/Los_Angeles
PW_DEBUG=no
PW_STYLE=grafana-dark
PW_GW_PWD=XXXXXXXXXXXRestart the dashboard stack: ./compose-dash.sh up -d |
Beta Was this translation helpful? Give feedback.
-
|
I have a Powerwall3 and finally got time to spin this up. Running this all on W11 with WLS running Ubuntu. My PW3 is hardwired. My experience is as follows:
So we know I'm getting data and able to connect, but then I hit various excedptions and api rate limits: Let me know if this helps or if you would like some more debugs from anything. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks @pavandave ! I created an issue to track: #492 - If you can, please take a look and let me know if that fixes it. Summary: It looks like your pypowerwall setup is running in TEDAPI |
Beta Was this translation helpful? Give feedback.
-
|
New user here. Just had a system installed with 3 PW3’s. All running OK in cloud API mode (running on a Ubuntu VM under Proxmox) but I’d like to get the detailed data and I’m willing to help test out PW3 support. One question, with 3 PW3s will I just connect to the primary unit (which I believe acts as the master) or do I have to connect to all of them separately? I have the IPs and passwords for all of them. |
Beta Was this translation helpful? Give feedback.
-
|
Great question, @lignumaqua ! I have PW2 and PW+ and they connect through the same gateway. Hopefully the PW3 does the same. Give it a try and see what happens. Thanks for helping test! |
Beta Was this translation helpful? Give feedback.
-
|
Will do, thanks! |
Beta Was this translation helpful? Give feedback.
-
|
Success - I think. Set up a new VM so it was a clean install. Added a static route to 192.168.9.1 and installed selecting option 4 in setup. System connected and asked for the password, so that all seems good. I now see the Frequency and Voltages graphs populated as well as some extra 'Alerts'. However, 'No data' in Powerwall Capacity, String Voltage, String Current, String Power, or Inverter Power sections. Is this as expected? Or is it just because it's night time and dark! :-) Is there any raw data I can provide to assist? The /help page is as follows: ` pyPowerwall [0.10.6] Proxy [t63]
|
Beta Was this translation helpful? Give feedback.
-
|
Following on... Other items possibly of interest:
Just about every other field in the data shows 0. This all begs the question; does the installer app give access to individual string data or not? You would think so as a diagnostic aid. If so, where is it? My installer will be here this morning, I'll ask him. EDIT: Installer showed me his app when he was connected via WiFi to the 'leader' PW3 and it does have access to all the string and inverter data. That data is there, somewhere, just need the right endpoint... PS - My installer would really like his customers to have access to string/inverter data as it makes his job easier. He is lobbying Tesla about it. |
Beta Was this translation helpful? Give feedback.
-
|
I believe this is expected behavior as I see the same. The APIs for the Powerwall3 may be different. My installer told me that in prior installations the Gateway was the "brains" of the operation, but with the Powerwall 3, it becomes the brains. With that, I noted when logging into the Tesla One app, my IP address is 192.168.90.2 along with expected the default gateway (ex:10.0.0.1/24) being picked up for DHCP. There is an option to modify the IP if anyone is feeling adventurous. But this is odd as the PW is accessible on 192.168.91.1 network. |
Beta Was this translation helpful? Give feedback.
-
|
@lignumaqua thanks for this great info! Yes, if you can use intercept tools to do the packet capture, perhaps we can find out how to get the additional API data. My suspicion is that it is one of these:
I love that! I appreciate that Tesla has been generally accommodating (tollertant?) to enthusiast list us, where other companies may not. However, if they were to continue and extend the support of the PW2 APIs to the PW3, there is a growing population of PW owners that would really appreciate it and as your installer mentioned, make their jobs easier. |
Beta Was this translation helpful? Give feedback.
-
|
This installer sells both Tesla and Enphase, and he says his customers really like the data they get from Enphase on each panel/micro inverter. The least Tesla could do is to provide that same data on each inverter. If the customer can give him that information on the phone before he heads out for a service call, it really helps him. (He's tech savvy and has a number of customers that have dashboards and access the API.) |
Beta Was this translation helpful? Give feedback.
-
|
@pavandave At least on PW+ units with a Gateway 2, the Gateway will respond on 192.168.91.1, 192.168.90.2, or any DHCP assigned address. |
Beta Was this translation helpful? Give feedback.
-
|
Did some packet sniffing while using the Tesla One app and it looks like it makes individual POST calls to endpoints on each PW3 with this format:
The JSON data sent back from these calls contains individual string voltages and currents. For example. One packet I captured contained: |
Beta Was this translation helpful? Give feedback.
-
|
HI @lignumaqua - the /tedapi/1 is what we are using to hae pypowerwall pull the config data (see https://github.com/jasonacox/pypowerwall/blob/6f0dbd1ad54aafcb264a1cdda67040b7b464eac6/pypowerwall/tedapi/__init__.py#L150-L249). It is needed to get some of the basics of the system so it makes sense that you would see that as well as the call to the individual PW3's. Thanks for your updates! Hopefully we will be able to unlock and use these. |
Beta Was this translation helpful? Give feedback.
-
|
Right - but I believe this returns different data from that same /tedapi/v1 endpoint by using a different protobuf. By using the "ComponentsQuery" query protobuf we get all the string and inverter data rather than the basic system data. I'll email you the files. |
Beta Was this translation helpful? Give feedback.
-
|
I see what you mean. All 6 strings are returned. |
Beta Was this translation helpful? Give feedback.
-
|
For those following along - unfortunately as feared this was a red-herring. A "ComponentsQuery" call on the /tedapi/v1 endpoint works, but only for the 'leader' PW3. It won't retrieve data for any 'Follower' PW3. |
Beta Was this translation helpful? Give feedback.
-
|
Here is the ComponentsQuery request.bin payload thanks to @lignumaqua . This is clearly a query set up for PW3 but as mentioned, the data isn't helpful if you have multiple PW3's. Once this payload was converted to a protobuf bin (e.g. request.bin), you would query it with: I created a script that creates the protobuf payload to test Components Query here: https://github.com/jasonacox/pypowerwall/blob/main/tools/tedapi/ComponentsQuery.py The query is for a PW3 so for a PW2, the output you will see: Note: The POST payload has both Ok, moving on... I'm working on the protobuf for the |
Beta Was this translation helpful? Give feedback.
-
|
Just as an FYI, I got this working in the first place by adding a route to 192.168.91.1 in the Linux VM where I was running the Docker. Today, instead, I added a static route in my router running OPNSense so all machines on the network can see the PW3, and it seems to works fine. Also don’t have to worry about the route getting lost. |
Beta Was this translation helpful? Give feedback.
-
|
I do this with my router setup as well and it works great. The only point of note is to make sure that there is no possibility for asynchronous routing. If you’re on the same subnet and add this route the powerwall may respond directly, which will potentially cause issues with the router and connection tracking, or cause the response packet to be sent from the lan address rather than the WiFi address.. If you’re on a different subnet this shouldn’t matter, providing it would go via that router at least. but for same subnet I’d suggest doing some form of source nat, be that a masquerade to the ip of the router, or a different ip (different subnet is best!). |
Beta Was this translation helpful? Give feedback.
-
The only time I have ever seen asynchronous routing causing issues is when there are firewalls in the path. If the hosts are on the same subnet, then it's never been an issue in my experience. |
Beta Was this translation helpful? Give feedback.
-
|
If theres a device with a access-list/firewall, with connection tracking, or a device that's applying more strict return path filtering, then theres a chance that this will happen - hence the potentialy cause issues, its going to depend on many different factors, but its something that I've come across many times in various different situations or environments - and wherever possible to reduce the chance of it occuring, a recommendation to source nat (especially in this case where true source identity doesn't matter) means that theres no possibility of it occurring |
Beta Was this translation helpful? Give feedback.
-
|
Small update. I've noticed that the backend has lost contact to the tedapi 192.168.91.1 address a couple of times. The route is apparently still there but the dashboard can't connect and a manual ping also fails. I have to ping the route gateway (the DHCP address of the host PW3) to wake it up again. Once I've pinged the gateway, then the direct ping to 192.168.91.1 works again. Strange... This happens both with direct routes in the Linux host, and with a static route set up on the router. Coud be something in my system, or could be something in the PW3 - not sure which. |
Beta Was this translation helpful? Give feedback.
-
|
It's more likely my problem than something generic - just trying to figure it out! |
Beta Was this translation helpful? Give feedback.
-
|
Next time it happens, it might be useful to see what the machine that's having issues accessing it has for the arp table ( |
Beta Was this translation helpful? Give feedback.
-
|
I wasn’t clear. It’s the same problem from anywhere on the network. My Apple desktop can’t ping it until I ping the gateway first! :) |
Beta Was this translation helpful? Give feedback.
-
Just curious, do you have the connection to the PW3 via wireless by chance? Some devices will go into a low power mode over wifi to extend battery life or quiet down chatter when not necessary. When this does happen, do any of the pings to the PW3 fail? I am lazy, so I'd probably just make a cron job that pings the host every 5 minutes to keep it awake and be done with it, but there may be a better solution. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, it's a WiFi connection. I asked the install tech about that when the PW3s were installed as I could easily have run a LAN cable, but he recommended against it. He had no definite proof as they hadn't installed many PW3s at this point but they'd had connectivity problems with the ones that were LAN connected but not with WiFi. As I have an outdoor access point 10 ft away it was simpler to stick with the WiFi.
That's what I was tempted to do too! :-) It's only happened twice so far. |
Beta Was this translation helpful? Give feedback.
-
|
What's the status of getting PW3 String Data and displaying it on the dashboard? Is there anything I can do to help get this working? |
Beta Was this translation helpful? Give feedback.
-
|
Awesome!! Thanks @lignumaqua The Warnings are expected (the TEDAPI doesn't have those APIs but they are needed for the Powerflow animation). However, the Error is not. Did that occur when you tried to http://localhost:8675/tedapi/battery ? I think I have an bug in the get_battery_block() function. It isn't used for any of the data flowing into the dashboard. Can you try these and note any errors in the log:
The mapping looks right based on your setup. I will need to add some CQs to InfluxDB to handle E & F strings, but you don't have those so it wouldn't apply to you. Thanks for testing and thanks for the screenshot! It's encouraging. 😁 |
Beta Was this translation helpful? Give feedback.
-
{
"PW1_name": "TEPOD--1707000-11-J--TG12xxxxxx2Z7X",
"PW1_POD_ActiveHeating": 0,
"PW1_POD_ChargeComplete": 0,
"PW1_POD_ChargeRequest": 0,
"PW1_POD_DischargeComplete": 0,
"PW1_POD_PermanentlyFaulted": 0,
"PW1_POD_PersistentlyFaulted": 0,
"PW1_POD_enable_line": 0,
"PW1_POD_available_charge_power": null,
"PW1_POD_available_dischg_power": null,
"PW1_POD_nom_energy_remaining": 11830,
"PW1_POD_nom_energy_to_be_charged": 2550,
"PW1_POD_nom_full_pack_energy": 14380,
"PW2_name": "TEPOD--1707000-11-J--TG12xxxxxx2Z6V",
"PW2_POD_ActiveHeating": 0,
"PW2_POD_ChargeComplete": 0,
"PW2_POD_ChargeRequest": 0,
"PW2_POD_DischargeComplete": 0,
"PW2_POD_PermanentlyFaulted": 0,
"PW2_POD_PersistentlyFaulted": 0,
"PW2_POD_enable_line": 0,
"PW2_POD_available_charge_power": null,
"PW2_POD_available_dischg_power": null,
"PW2_POD_nom_energy_remaining": 11660,
"PW2_POD_nom_energy_to_be_charged": 2550,
"PW2_POD_nom_full_pack_energy": 14210,
"PW3_name": "TEPOD--1707000-11-J--TG12xxxxxx2T64",
"PW3_POD_ActiveHeating": 0,
"PW3_POD_ChargeComplete": 0,
"PW3_POD_ChargeRequest": 0,
"PW3_POD_DischargeComplete": 0,
"PW3_POD_PermanentlyFaulted": 0,
"PW3_POD_PersistentlyFaulted": 0,
"PW3_POD_enable_line": 0,
"PW3_POD_available_charge_power": null,
"PW3_POD_available_dischg_power": null,
"PW3_POD_nom_energy_remaining": 11960,
"PW3_POD_nom_energy_to_be_charged": 2420,
"PW3_POD_nom_full_pack_energy": 14380,
"nominal_full_pack_energy": 42970,
"nominal_energy_remaining": 35450,
"time_remaining_hours": 6.69815777042985,
"backup_reserve_percent": 80
}
{
"ISLAND_FreqL1_Load": 59.97,
"ISLAND_FreqL1_Main": 59.97,
"ISLAND_FreqL2_Load": 59.97,
"ISLAND_FreqL2_Main": 59.97,
"ISLAND_FreqL3_Load": 0,
"ISLAND_FreqL3_Main": 0,
"ISLAND_GridConnected": "ISLAND_GridConnected_Connected",
"ISLAND_GridState": "ISLAND_GridState_Grid_Compliant",
"ISLAND_L1L2PhaseDelta": null,
"ISLAND_L1L3PhaseDelta": null,
"ISLAND_L1MicrogridOk": null,
"ISLAND_L2L3PhaseDelta": null,
"ISLAND_L2MicrogridOk": null,
"ISLAND_L3MicrogridOk": null,
"ISLAND_PhaseL1_Main_Load": null,
"ISLAND_PhaseL2_Main_Load": null,
"ISLAND_PhaseL3_Main_Load": null,
"ISLAND_ReadyForSynchronization": null,
"ISLAND_VL1N_Load": 119.5,
"ISLAND_VL1N_Main": 119.5,
"ISLAND_VL2N_Load": 119.5,
"ISLAND_VL2N_Main": 119.5,
"ISLAND_VL3N_Load": 0,
"ISLAND_VL3N_Main": 0,
"METER_X_CTA_I": 8.532,
"METER_X_CTA_InstReactivePower": 307,
"METER_X_CTA_InstRealPower": -288,
"METER_X_CTB_I": 7.032,
"METER_X_CTB_InstReactivePower": -33,
"METER_X_CTB_InstRealPower": 406,
"METER_X_CTC_I": 0,
"METER_X_CTC_InstReactivePower": 0,
"METER_X_CTC_InstRealPower": 0,
"METER_X_LifetimeEnergyExport": null,
"METER_X_LifetimeEnergyImport": null,
"METER_X_VL1N": 118.56,
"METER_X_VL2N": 118.62,
"METER_X_VL3N": 0,
"METER_Y_CTA_I": 0,
"METER_Y_CTA_InstReactivePower": 0,
"METER_Y_CTA_InstRealPower": 0,
"METER_Y_CTB_I": 0,
"METER_Y_CTB_InstReactivePower": 0,
"METER_Y_CTB_InstRealPower": 0,
"METER_Y_CTC_I": 0,
"METER_Y_CTC_InstReactivePower": 0,
"METER_Y_CTC_InstRealPower": 0,
"METER_Y_LifetimeEnergyExport": null,
"METER_Y_LifetimeEnergyImport": null,
"METER_Y_VL1N": 118.56,
"METER_Y_VL2N": 118.63,
"METER_Y_VL3N": 0,
"grid_status": 1
} |
Beta Was this translation helpful? Give feedback.
-
|
Thanks!!! Oops, I'm missing the TEPINV block which feed the /freq API. I added that and released a new beta. It shoudl fix the /freq call as well as the /tedapi/battery call. jasonacox/pypowerwall:0.11.0t64-beta3 If you get a chance, please give it a try and let me know how it looks. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, /battery call now good: [
{
"vin": "1707000-11-J--TG12xxxxxx2Z7X",
"min_soe": 0,
"max_soe": 100,
"type": "Powerwall3",
"can_connection": "can1",
"pvi_power_status": "on",
"battery_power_status": "on",
"enable_inverter_battery_meter": true,
"enable_inverter_solar_meter": true
},
{
"vin": "1707000-11-J--TG12xxxxxx2Z6V",
"min_soe": 0,
"max_soe": 100,
"type": "Powerwall3Follower",
"battery_power_status": "on",
"enable_inverter_battery_meter": true
},
{
"vin": "1707000-11-J--TG12xxxxxx2T64",
"min_soe": 0,
"max_soe": 100,
"type": "Powerwall3Follower",
"battery_power_status": "on",
"enable_inverter_battery_meter": true
}
] |
Beta Was this translation helpful? Give feedback.
-
|
I have included the new PW3 vitals updates in the recent Powerwall Dashboard Release v4.5.1. Use |
Beta Was this translation helpful? Give feedback.
-
|
The specific individual string voltage and current data for all 6 inverters is retrievable through the "ComponentsQuery" call. This is a one PW3 at a time call with the din in the POST request. It isn’t in the call above as that has a max of 4 sets of data. PW3 has 6 inverters so uses a new call. Unfortunately you can’t get it all at once, you have to query each PW3 separately. |
Beta Was this translation helpful? Give feedback.
-
|
Question: In An other question: |
Beta Was this translation helpful? Give feedback.
-
|
Hi @Tho-Mat , the correct one is pypowerwall/tools/tedapi/ComponentsQuery.py - the other one was developed during research. I should fix it, but it works as well. I'm not understanding the other question. Do you have a code sample? |
Beta Was this translation helpful? Give feedback.
-
|
finally got a little more time to look into this, still testing, but have powerwall temps back in my proxy. only tested so far on my powerwall2+ running 24.36.2, but in theory should work on other versions, though may require some tweaks. need a sunny day to see if it really provides accurate readings. |
Beta Was this translation helpful? Give feedback.
-
|
I upgraded to the 4.6.0 release and unfortunately I am not getting any temperature readings from my PW3. Dashboard says "No data" and http://pypowerwall:8675/temps returns "{}". Seems like maybe something is different with PW3. Is there anything I can do to help debug? |
Beta Was this translation helpful? Give feedback.
-
|
I created a new issue for this - #550 |
Beta Was this translation helpful? Give feedback.
-
|
@ygelfand where in the Tesla One app do you navigate to see temperature information? I connected to my PW3 and couldn't see anything other than basic info and String/Inverter current/voltage |
Beta Was this translation helpful? Give feedback.
-
|
@jplewis2 no idea if its in the actual app (and don't actually use the app), was from the app source. |
Beta Was this translation helpful? Give feedback.
-
|
@ygelfand oh, interesting. I'm trying to help debug getting temperature readings from PW3 over in another thread (#550). I don't suppose you've noticed anything in the source code that might indicate a different query for PW3? |
Beta Was this translation helpful? Give feedback.
and others
-
With recent Firmware Upgrades (e.g. 23.28.1) the Tesla Gateway portal now instructs the user to install and use the Tesla Pros app to manage the system. As discussed in 367 there are ways to bypass these screens to get to the classic portal interface. The new Powerwall 3's do not appear to have a user web portal and instead use only the Tesla Pros app (see PW3 support issue #387).
So far, I have discovered the following:
GET /api/status
This works with Powerwall2/+ systems but may not work for Powerwall 3.
GET /api/status HTTP/1.1 Host: 192.168.91.1 Accept: */* Cookie: ak_bmsc=xxx; bm_sv=xxx User-Agent: TeslaPros/2316 CFNetwork/1474 Darwin/23.0.0 Accept-Language: en-US,en;q=0.9 Accept-Encoding: gzip, deflate, br Connection: keep-alive HTTP/1.1 200 OK Cache-Control: no-cache, no-store Content-Encoding: gzip Content-Type: application/json Date: Tue, 21 Nov 2023 21:10:02 GMT Content-Length: 268 { "din": "1232100-00-E--TG123456789012", "start_time": "2023-10-13 04:01:45 +0800", "up_time_seconds": "946h8m17.0612373s", "is_new": false, "version": "23.28.2 27626f98", "git_hash": "27626f98a66cad5c665bbe1d4d788cdb3e94fd33", "commission_count": 0, "device_type": "teg", "teg_type": "unknown", "sync_type": "v2.1", "cellular_disabled": false, "can_reboot": true}Cookies - not sure if these are needed but they show up:
Curl Simulation
GET /tedapi/din
This is similar to the above but did not show up in the packet captures I conducted. It uses basic auth that appears to be: Tesla_Energy_Device:GW_PWD where the GW_PWD is the password near the QR code on the Powerwall that you scan with the Tesla Pros app.
curl -v -k -u "Tesla_Energy_Device:GW_PWD"" https://192.168.91.1/tedapi/dinIt only returns a simple string that contains the DIN:
POST /tedapi/v1
This appears to be the workhorse function. It uses basic auth that appears to be:
Tesla_Energy_Device:GW_PWDwhere the GW_PWD is the password near the QR code on the Powerwall that you scan with the Tesla Pros app.Payloads are binary Protocol Buffers (protobufs) but we don't yet have a schema definition file. You can use
protoc --decode_raw < v1_requestto decode the raw response.Sample transaction
There are different types of request sent. One is for
configwhich gets a payload that contains the configuration of the Powerwall. Another is forquerythat gets current data (e.g. systemStatus, realPowerW, voltages, frequencies, etc.).CONFIG Example
Raw File
v1_requestused for the POST that appears to be asking for config details. This is theprotoc --decode_raw < v1_requestoutput:1 { 1: 1 2 { 3: 1 } 3 { 1: "1232100-00-E--TG123456789012" } 15 { 1 { 1: 1 2: "config.json" } } } 2 { 1: 1 }Curl Simulation
An example response (
v1.json) payload from the one above (protoc --decode_raw < v1.json) - Showing system config data which comes through in JSON blob (removed to protect the innocent):1 { 1: 1 2 { 1: "1232100-00-E--TG123456789012" } 3 { 3: 1 } 16 { 2 { 1: 1 2: ** JSON Payload - removed ** " } } } 2 { 1: 1 }QUERY Example
Raw File
v1_request.largeused for the POST that appears to be asking for query details. This is theprotoc --decode_raw < v1_request.largeoutput:1 { 1: 1 2 { 3: 1 } 3 { 1: "1232100-00-E--TG123456789012" } 16 { 1 { 1: 2 2 { 1: 1 2: " query DeviceControllerQuery {\n control {\n systemStatus {\n nominalFullPackEnergyWh\n nominalEnergyRemainingWh\n }\n islanding {\n customerIslandMode\n contactorClosed\n microGridOK\n gridOK\n }\n meterAggregates {\n location\n realPowerW\n }\n alerts {\n active\n },\n siteShutdown {\n isShutDown\n reasons\n }\n batteryBlocks {\n din\n disableReasons\n }\n pvInverters {\n din\n disableReasons\n }\n }\n system {\n time\n sitemanagerStatus {\n isRunning\n }\n updateUrgencyCheck {\n urgency\n version {\n version\n gitHash\n }\n timestamp\n }\n }\n neurio {\n isDetectingWiredMeters\n readings {\n serial\n dataRead {\n voltageV\n realPowerW\n reactivePowerVAR\n currentA\n }\n timestamp\n }\n pairings {\n serial\n shortId\n status\n errors\n macAddress\n isWired\n modbusPort\n modbusId\n lastUpdateTimestamp\n }\n }\n pw3Can {\n firmwareUpdate {\n isUpdating\n progress {\n updating\n numSteps\n currentStep\n currentStepProgress\n progress\n }\n }\n }\n esCan {\n bus {\n PVAC {\n packagePartNumber\n packageSerialNumber\n subPackagePartNumber\n subPackageSerialNumber\n PVAC_Status {\n isMIA\n PVAC_Pout\n PVAC_State\n PVAC_Vout\n PVAC_Fout\n }\n PVAC_InfoMsg {\n PVAC_appGitHash\n }\n PVAC_Logging {\n isMIA\n PVAC_PVCurrent_A\n PVAC_PVCurrent_B\n PVAC_PVCurrent_C\n PVAC_PVCurrent_D\n PVAC_PVMeasuredVoltage_A\n PVAC_PVMeasuredVoltage_B\n PVAC_PVMeasuredVoltage_C\n PVAC_PVMeasuredVoltage_D\n PVAC_VL1Ground\n PVAC_VL2Ground\n }\n alerts {\n isComplete\n isMIA\n active\n }\n }\n PINV {\n PINV_Status {\n isMIA\n PINV_Fout\n PINV_Pout\n PINV_Vout\n PINV_State\n PINV_GridState\n }\n PINV_AcMeasurements {\n isMIA\n PINV_VSplit1\n PINV_VSplit2\n }\n PINV_PowerCapability {\n isComplete\n isMIA\n PINV_Pnom\n }\n alerts {\n isComplete\n isMIA\n active\n }\n }\n PVS {\n PVS_Status {\n isMIA\n PVS_State\n PVS_vLL\n PVS_StringA_Connected\n PVS_StringB_Connected\n PVS_StringC_Connected\n PVS_StringD_Connected\n PVS_SelfTestState\n }\n alerts {\n isComplete\n isMIA\n active\n }\n }\n THC {\n packagePartNumber\n packageSerialNumber\n THC_InfoMsg {\n isComplete\n isMIA\n THC_appGitHash\n }\n THC_Logging {\n THC_LOG_PW_2_0_EnableLineState\n }\n }\n POD {\n POD_EnergyStatus {\n isMIA\n POD_nom_energy_remaining\n POD_nom_full_pack_energy\n }\n POD_InfoMsg {\n POD_appGitHash\n }\n }\n MSA {\n packagePartNumber\n packageSerialNumber\n MSA_InfoMsg {\n isMIA\n MSA_appGitHash\n MSA_assemblyId\n }\n METER_Z_AcMeasurements {\n isMIA\n lastRxTime\n METER_Z_CTA_InstRealPower\n METER_Z_CTA_InstReactivePower\n METER_Z_CTA_I\n METER_Z_VL1G\n METER_Z_CTB_InstRealPower\n METER_Z_CTB_InstReactivePower\n METER_Z_CTB_I\n METER_Z_VL2G\n }\n MSA_Status {\n lastRxTime\n }\n }\n SYNC {\n packagePartNumber\n packageSerialNumber\n SYNC_InfoMsg {\n isMIA\n SYNC_appGitHash\n }\n METER_X_AcMeasurements {\n isMIA\n isComplete\n lastRxTime\n METER_X_CTA_InstRealPower\n METER_X_CTA_InstReactivePower\n METER_X_CTA_I\n METER_X_VL1N\n METER_X_CTB_InstRealPower\n METER_X_CTB_InstReactivePower\n METER_X_CTB_I\n METER_X_VL2N\n METER_X_CTC_InstRealPower\n METER_X_CTC_InstReactivePower\n METER_X_CTC_I\n METER_X_VL3N\n }\n METER_Y_AcMeasurements {\n isMIA\n isComplete\n lastRxTime\n METER_Y_CTA_InstRealPower\n METER_Y_CTA_InstReactivePower\n METER_Y_CTA_I\n METER_Y_VL1N\n METER_Y_CTB_InstRealPower\n METER_Y_CTB_InstReactivePower\n METER_Y_CTB_I\n METER_Y_VL2N\n METER_Y_CTC_InstRealPower\n METER_Y_CTC_InstReactivePower\n METER_Y_CTC_I\n METER_Y_VL3N\n }\n SYNC_Status {\n lastRxTime\n }\n }\n ISLANDER {\n ISLAND_GridConnection {\n ISLAND_GridConnected\n isComplete\n }\n ISLAND_AcMeasurements {\n ISLAND_VL1N_Main\n ISLAND_FreqL1_Main\n ISLAND_VL2N_Main\n ISLAND_FreqL2_Main\n ISLAND_VL3N_Main\n ISLAND_FreqL3_Main\n ISLAND_VL1N_Load\n ISLAND_FreqL1_Load\n ISLAND_VL2N_Load\n ISLAND_FreqL2_Load\n ISLAND_VL3N_Load\n ISLAND_FreqL3_Load\n ISLAND_GridState\n lastRxTime\n isComplete\n isMIA\n }\n }\n }\n enumeration {\n inProgress\n numACPW\n numPVI\n }\n firmwareUpdate {\n isUpdating\n powerwalls {\n updating\n numSteps\n currentStep\n currentStepProgress\n progress\n }\n msa {\n updating\n numSteps\n currentStep\n currentStepProgress\n progress\n }\n sync {\n updating\n numSteps\n currentStep\n currentStepProgress\n progress\n }\n pvInverters {\n updating\n numSteps\n currentStep\n currentStepProgress\n progress\n }\n }\n phaseDetection {\n inProgress\n lastUpdateTimestamp\n powerwalls {\n din\n progress\n phase\n }\n }\n inverterSelfTests {\n isRunning\n isCanceled\n pinvSelfTestsResults {\n din\n overall {\n status\n test\n summary\n setMagnitude\n setTime\n tripMagnitude\n tripTime\n accuracyMagnitude\n accuracyTime\n currentMagnitude\n timestamp\n lastError\n }\n testResults {\n status\n test\n summary\n setMagnitude\n setTime\n tripMagnitude\n tripTime\n accuracyMagnitude\n accuracyTime\n currentMagnitude\n timestamp\n lastError\n }\n }\n }\n }\n}\n" } 3: "0\201\210\002B\000\370\364\003\261H\255\211/\355W)@\326\254\220\006\360\346\353\020N\\\266\026\201pw\034\353\302\271\322\312]\342a\032I\245P\020#\206\2146a3h\300\216[\320\035O\376md\336\0019\371\231\264\255\026\002B\001\354\235\240\037F.\325Y0\376\376\244\313{\235\207\260\373\033\340\337\340\226\335T\310\027\'\232\342\027\032h\376ZR\306\030\037\331\200_?\244\013 \235\010\322\265\0315>\363`_\267\003\241\323#\t\342\317\201" 4 { 1: "{}" } } } } 2 { 1: 1 }An example response (
v1.json) payload from the one above (protoc --decode_raw < v1.json):1 { 1: 1 2 { 1: "1232100-00-E--TG123456789012" } 3 { 3: 1 } 16 { 2 { 1: 1 2: "{\"control\":{\"alerts\":{\"active\":[\"SystemConnectedToGrid\",\"FWUpdateSucceeded\",\"GridCodesWrite\",\"PodCommissionTime\"]},\"batteryBlocks\":[{\"din\":\"2012170-25-E#TG123456789012\",\"disableReasons\":null},{\"din\":\"3012170-05-B#TG123456789012\",\"disableReasons\":null}],\"islanding\":{\"contactorClosed\":true,\"customerIslandMode\":\"BACKUP\",\"gridOK\":true,\"microGridOK\":true},\"meterAggregates\":[{\"location\":\"BATTERY\",\"realPowerW\":-1720},{\"location\":\"SITE\",\"realPowerW\":34},{\"location\":\"LOAD\",\"realPowerW\":1018},{\"location\":\"SOLAR\",\"realPowerW\":2690},{\"location\":\"SOLAR_RGM\",\"realPowerW\":2713.139892578125},{\"location\":\"GENERATOR\",\"realPowerW\":0},{\"location\":\"CONDUCTOR\",\"realPowerW\":0}],\"pvInverters\":[],\"siteShutdown\":{\"isShutDown\":false,\"reasons\":[]},\"systemStatus\":{\"nominalEnergyRemainingWh\":21532,\"nominalFullPackEnergyWh\":26223}},\"esCan\":{\"bus\":{\"ISLANDER\":{\"ISLAND_AcMeasurements\":{\"ISLAND_FreqL1_Load\":60.010000000000005,\"ISLAND_FreqL1_Main\":60.010000000000005,\"ISLAND_FreqL2_Load\":60.010000000000005,\"ISLAND_FreqL2_Main\":60.010000000000005,\"ISLAND_FreqL3_Load\":0,\"ISLAND_FreqL3_Main\":0,\"ISLAND_GridState\":\"ISLAND_GridState_Grid_Compliant\",\"ISLAND_VL1N_Load\":122,\"ISLAND_VL1N_Main\":122,\"ISLAND_VL2N_Load\":122,\"ISLAND_VL2N_Main\":122,\"ISLAND_VL3N_Load\":0,\"ISLAND_VL3N_Main\":0,\"isComplete\":true,\"isMIA\":false,\"lastRxTime\":\"2023-11-21T13:10:29-08:00\"},\"ISLAND_GridConnection\":{\"ISLAND_GridConnected\":\"ISLAND_GridConnected_Connected\",\"isComplete\":true}},\"MSA\":{\"METER_Z_AcMeasurements\":{\"METER_Z_CTA_I\":0,\"METER_Z_CTA_InstReactivePower\":0,\"METER_Z_CTA_InstRealPower\":0,\"METER_Z_CTB_I\":0,\"METER_Z_CTB_InstReactivePower\":0,\"METER_Z_CTB_InstRealPower\":0,\"METER_Z_VL1G\":0,\"METER_Z_VL2G\":0,\"isMIA\":true,\"lastRxTime\":\"0001-01-01T00:00:00Z\"},\"MSA_InfoMsg\":{\"MSA_appGitHash\":[0,0,0,0,0,0,0],\"MSA_assemblyId\":0,\"isMIA\":true},\"MSA_Status\":{\"lastRxTime\":\"0001-01-01T00:00:00Z\"},\"packagePartNumber\":\"\",\"packageSerialNumber\":\"\"},\"PINV\":[{\"PINV_AcMeasurements\":{\"PINV_VSplit1\":121.80000000000001,\"PINV_VSplit2\":121.60000000000001,\"isMIA\":false},\"PINV_PowerCapability\":{\"PINV_Pnom\":5800,\"isComplete\":true,\"isMIA\":false},\"PINV_Status\":{\"PINV_Fout\":60.004000000000005,\"PINV_GridState\":\"Grid_Compliant\",\"PINV_Pout\":-0.87,\"PINV_State\":\"PINV_GridFollowing\",\"PINV_Vout\":243.8,\"isMIA\":false},\"alerts\":{\"active\":[\"PINV_a067_overvoltageNeutralChassis\"],\"isComplete\":true,\"isMIA\":false}},{\"PINV_AcMeasurements\":{\"PINV_VSplit1\":121.7,\"PINV_VSplit2\":121.5,\"isMIA\":false},\"PINV_PowerCapability\":{\"PINV_Pnom\":5800,\"isComplete\":true,\"isMIA\":false},\"PINV_Status\":{\"PINV_Fout\":60.003,\"PINV_GridState\":\"Grid_Compliant\",\"PINV_Pout\":-0.81,\"PINV_State\":\"PINV_GridFollowing\",\"PINV_Vout\":243.70000000000002,\"isMIA\":false},\"alerts\":{\"active\":[\"PINV_a067_overvoltageNeutralChassis\"],\"isComplete\":true,\"isMIA\":false}},{\"PINV_AcMeasurements\":{\"PINV_VSplit1\":0,\"PINV_VSplit2\":0,\"isMIA\":true},\"PINV_PowerCapability\":{\"PINV_Pnom\":0,\"isComplete\":false,\"isMIA\":true},\"PINV_Status\":{\"PINV_Fout\":0,\"PINV_GridState\":\"Grid_Uncompliant\",\"PINV_Pout\":0,\"PINV_State\":\"PINV_Off\",\"PINV_Vout\":0,\"isMIA\":true},\"alerts\":{\"active\":[],\"isComplete\":false,\"isMIA\":true}},{\"PINV_AcMeasurements\":{\"PINV_VSplit1\":0,\"PINV_VSplit2\":0,\"isMIA\":true},\"PINV_PowerCapability\":{\"PINV_Pnom\":0,\"isComplete\":false,\"isMIA\":true},\"PINV_Status\":{\"PINV_Fout\":0,\"PINV_GridState\":\"Grid_Uncompliant\",\"PINV_Pout\":0,\"PINV_State\":\"PINV_Off\",\"PINV_Vout\":0,\"isMIA\":true},\"alerts\":{\"active\":[],\"isComplete\":false,\"isMIA\":true}},{\"PINV_AcMeasurements\":{\"PINV_VSplit1\":0,\"PINV_VSplit2\":0,\"isMIA\":true},\"PINV_PowerCapability\":{\"PINV_Pnom\":0,\"isComplete\":false,\"isMIA\":true},\"PINV_Status\":{\"PINV_Fout\":0,\"PINV_GridState\":\"Grid_Uncompliant\",\"PINV_Pout\":0,\"PINV_State\":\"PINV_Off\",\"PINV_Vout\":0,\"isMIA\":true},\"alerts\":{\"active\":[],\"isComplete\":false,\"isMIA\":true}},{\"PINV_AcMeasurements\":{\"PINV_VSplit1\":0,\"PINV_VSplit2\":0,\"isMIA\":true},\"PINV_PowerCapability\":{\"PINV_Pnom\":0,\"isComplete\":false,\"isMIA\":true},\"PINV_Status\":{\"PINV_Fout\":0,\"PINV_GridState\":\"Grid_Uncompliant\",\"PINV_Pout\":0,\"PINV_State\":\"PINV_Off\",\"PINV_Vout\":0,\"isMIA\":true},\"alerts\":{\"active\":[],\"isComplete\":false,\"isMIA\":true}},{\"PINV_AcMeasurements\":{\"PINV_VSplit1\":0,\"PINV_VSplit2\":0,\"isMIA\":true},\"PINV_PowerCapability\":{\"PINV_Pnom\":0,\"isComplete\":false,\"isMIA\":true},\"PINV_Status\":{\"PINV_Fout\":0,\"PINV_GridState\":\"Grid_Uncompliant\",\"PINV_Pout\":0,\"PINV_State\":\"PINV_Off\",\"PINV_Vout\":0,\"isMIA\":true},\"alerts\":{\"active\":[],\"isComplete\":false,\"isMIA\":true}},{\"PINV_AcMeasurements\":{\"PINV_VSplit1\":0,\"PINV_VSplit2\":0,\"isMIA\":true},\"PINV_PowerCapability\":{\"PINV_Pnom\":0,\"isComplete\":false,\"isMIA\":true},\"PINV_Status\":{\"PINV_Fout\":0,\"PINV_GridState\":\"Grid_Uncompliant\",\"PINV_Pout\":0,\"PINV_State\":\"PINV_Off\",\"PINV_Vout\":0,\"isMIA\":true},\"alerts\":{\"active\":[],\"isComplete\":false,\"isMIA\":true}},{\"PINV_AcMeasurements\":{\"PINV_VSplit1\":0,\"PINV_VSplit2\":0,\"isMIA\":true},\"PINV_PowerCapability\":{\"PINV_Pnom\":0,\"isComplete\":false,\"isMIA\":true},\"PINV_Status\":{\"PINV_Fout\":0,\"PINV_GridState\":\"Grid_Uncompliant\",\"PINV_Pout\":0,\"PINV_State\":\"PINV_Off\",\"PINV_Vout\":0,\"isMIA\":true},\"alerts\":{\"active\":[],\"isComplete\":false,\"isMIA\":true}},{\"PINV_AcMeasurements\":{\"PINV_VSplit1\":0,\"PINV_VSplit2\":0,\"isMIA\":true},\"PINV_PowerCapability\":{\"PINV_Pnom\":0,\"isComplete\":false,\"isMIA\":true},\"PINV_Status\":{\"PINV_Fout\":0,\"PINV_GridState\":\"Grid_Uncompliant\",\"PINV_Pout\":0,\"PINV_State\":\"PINV_Off\",\"PINV_Vout\":0,\"isMIA\":true},\"alerts\":{\"active\":[],\"isComplete\":false,\"isMIA\":true}}],\"POD\":[{\"POD_EnergyStatus\":{\"POD_nom_energy_remaining\":10984,\"POD_nom_full_pack_energy\":13396,\"isMIA\":false},\"POD_InfoMsg\":{\"POD_appGitHash\":[39,98,111,152,166,108,173]}},{\"POD_EnergyStatus\":{\"POD_nom_energy_remaining\":10548,\"POD_nom_full_pack_energy\":12827,\"isMIA\":false},\"POD_InfoMsg\":{\"POD_appGitHash\":[39,98,111,152,166,108,173]}},{\"POD_EnergyStatus\":{\"POD_nom_energy_remaining\":0,\"POD_nom_full_pack_energy\":0,\"isMIA\":true},\"POD_InfoMsg\":{\"POD_appGitHash\":[0,0,0,0,0,0,0]}},{\"POD_EnergyStatus\":{\"POD_nom_energy_remaining\":0,\"POD_nom_full_pack_energy\":0,\"isMIA\":true},\"POD_InfoMsg\":{\"POD_appGitHash\":[0,0,0,0,0,0,0]}},{\"POD_EnergyStatus\":{\"POD_nom_energy_remaining\":0,\"POD_nom_full_pack_energy\":0,\"isMIA\":true},\"POD_InfoMsg\":{\"POD_appGitHash\":[0,0,0,0,0,0,0]}},{\"POD_EnergyStatus\":{\"POD_nom_energy_remaining\":0,\"POD_nom_full_pack_energy\":0,\"isMIA\":true},\"POD_InfoMsg\":{\"POD_appGitHash\":[0,0,0,0,0,0,0]}},{\"POD_EnergyStatus\":{\"POD_nom_energy_remaining\":0,\"POD_nom_full_pack_energy\":0,\"isMIA\":true},\"POD_InfoMsg\":{\"POD_appGitHash\":[0,0,0,0,0,0,0]}},{\"POD_EnergyStatus\":{\"POD_nom_energy_remaining\":0,\"POD_nom_full_pack_energy\":0,\"isMIA\":true},\"POD_InfoMsg\":{\"POD_appGitHash\":[0,0,0,0,0,0,0]}},{\"POD_EnergyStatus\":{\"POD_nom_energy_remaining\":0,\"POD_nom_full_pack_energy\":0,\"isMIA\":true},\"POD_InfoMsg\":{\"POD_appGitHash\":[0,0,0,0,0,0,0]}},{\"POD_EnergyStatus\":{\"POD_nom_energy_remaining\":0,\"POD_nom_full_pack_energy\":0,\"isMIA\":true},\"POD_InfoMsg\":{\"POD_appGitHash\":[0,0,0,0,0,0,0]}}],\"PVAC\":[{\"PVAC_InfoMsg\":{\"PVAC_appGitHash\":[39,98,111,152,166,108,173]},\"PVAC_Logging\":{\"PVAC_PVCurrent_A\":2.21,\"PVAC_PVCurrent_B\":0,\"PVAC_PVCurrent_C\":5.11,\"PVAC_PVCurrent_D\":5.04,\"PVAC_PVMeasuredVoltage_A\":239,\"PVAC_PVMeasuredVoltage_B\":-2.5999999999999996,\"PVAC_PVMeasuredVoltage_C\":204.8,\"PVAC_PVMeasuredVoltage_D\":204.70000000000002,\"PVAC_VL1Ground\":121.19999999999999,\"PVAC_VL2Ground\":121.5,\"isMIA\":false},\"PVAC_Status\":{\"PVAC_Fout\":60.007999999999996,\"PVAC_Pout\":2760,\"PVAC_State\":\"PVAC_Active\",\"PVAC_Vout\":242.8,\"isMIA\":false},\"alerts\":{\"active\":[],\"isComplete\":true,\"isMIA\":false},\"packagePartNumber\":\"1538100-00-F\",\"packageSerialNumber\":\"CN123456789012\",\"subPackagePartNumber\":\"\",\"subPackageSerialNumber\":\"\"},{\"PVAC_InfoMsg\":{\"PVAC_appGitHash\":[0,0,0,0,0,0,0]},\"PVAC_Logging\":{\"PVAC_PVCurrent_A\":0,\"PVAC_PVCurrent_B\":0,\"PVAC_PVCurrent_C\":0,\"PVAC_PVCurrent_D\":0,\"PVAC_PVMeasuredVoltage_A\":0,\"PVAC_PVMeasuredVoltage_B\":0,\"PVAC_PVMeasuredVoltage_C\":0,\"PVAC_PVMeasuredVoltage_D\":0,\"PVAC_VL1Ground\":0,\"PVAC_VL2Ground\":0,\"isMIA\":true},\"PVAC_Status\":{\"PVAC_Fout\":0,\"PVAC_Pout\":0,\"PVAC_State\":\"PVAC_Init\",\"PVAC_Vout\":0,\"isMIA\":true},\"alerts\":{\"active\":[],\"isComplete\":false,\"isMIA\":true},\"packagePartNumber\":\"\",\"packageSerialNumber\":\"\",\"subPackagePartNumber\":\"\",\"subPackageSerialNumber\":\"\"},{\"PVAC_InfoMsg\":{\"PVAC_appGitHash\":[0,0,0,0,0,0,0]},\"PVAC_Logging\":{\"PVAC_PVCurrent_A\":0,\"PVAC_PVCurrent_B\":0,\"PVAC_PVCurrent_C\":0,\"PVAC_PVCurrent_D\":0,\"PVAC_PVMeasuredVoltage_A\":0,\"PVAC_PVMeasuredVoltage_B\":0,\"PVAC_PVMeasuredVoltage_C\":0,\"PVAC_PVMeasuredVoltage_D\":0,\"PVAC_VL1Ground\":0,\"PVAC_VL2Ground\":0,\"isMIA\":true},\"PVAC_Status\":{\"PVAC_Fout\":0,\"PVAC_Pout\":0,\"PVAC_State\":\"PVAC_Init\",\"PVAC_Vout\":0,\"isMIA\":true},\"alerts\":{\"active\":[],\"isComplete\":false,\"isMIA\":true},\"packagePartNumber\":\"\",\"packageSerialNumber\":\"\",\"subPackagePartNumber\":\"\",\"subPackageSerialNumber\":\"\"},{\"PVAC_InfoMsg\":{\"PVAC_appGitHash\":[0,0,0,0,0,0,0]},\"PVAC_Logging\":{\"PVAC_PVCurrent_A\":0,\"PVAC_PVCurrent_B\":0,\"PVAC_PVCurrent_C\":0,\"PVAC_PVCurrent_D\":0,\"PVAC_PVMeasuredVoltage_A\":0,\"PVAC_PVMeasuredVoltage_B\":0,\"PVAC_PVMeasuredVoltage_C\":0,\"PVAC_PVMeasuredVoltage_D\":0,\"PVAC_VL1Ground\":0,\"PVAC_VL2Ground\":0,\"isMIA\":true},\"PVAC_Status\":{\"PVAC_Fout\":0,\"PVAC_Pout\":0,\"PVAC_State\":\"PVAC_Init\",\"PVAC_Vout\":0,\"isMIA\":true},\"alerts\":{\"active\":[],\"isComplete\":false,\"isMIA\":true},\"packagePartNumber\":\"\",\"packageSerialNumber\":\"\",\"subPackagePartNumber\":\"\",\"subPackageSerialNumber\":\"\"},{\"PVAC_InfoMsg\":{\"PVAC_appGitHash\":[0,0,0,0,0,0,0]},\"PVAC_Logging\":{\"PVAC_PVCurrent_A\":0,\"PVAC_PVCurrent_B\":0,\"PVAC_PVCurrent_C\":0,\"PVAC_PVCurrent_D\":0,\"PVAC_PVMeasuredVoltage_A\":0,\"PVAC_PVMeasuredVoltage_B\":0,\"PVAC_PVMeasuredVoltage_C\":0,\"PVAC_PVMeasuredVoltage_D\":0,\"PVAC_VL1Ground\":0,\"PVAC_VL2Ground\":0,\"isMIA\":true},\"PVAC_Status\":{\"PVAC_Fout\":0,\"PVAC_Pout\":0,\"PVAC_State\":\"PVAC_Init\",\"PVAC_Vout\":0,\"isMIA\":true},\"alerts\":{\"active\":[],\"isComplete\":false,\"isMIA\":true},\"packagePartNumber\":\"\",\"packageSerialNumber\":\"\",\"subPackagePartNumber\":\"\",\"subPackageSerialNumber\":\"\"},{\"PVAC_InfoMsg\":{\"PVAC_appGitHash\":[0,0,0,0,0,0,0]},\"PVAC_Logging\":{\"PVAC_PVCurrent_A\":0,\"PVAC_PVCurrent_B\":0,\"PVAC_PVCurrent_C\":0,\"PVAC_PVCurrent_D\":0,\"PVAC_PVMeasuredVoltage_A\":0,\"PVAC_PVMeasuredVoltage_B\":0,\"PVAC_PVMeasuredVoltage_C\":0,\"PVAC_PVMeasuredVoltage_D\":0,\"PVAC_VL1Ground\":0,\"PVAC_VL2Ground\":0,\"isMIA\":true},\"PVAC_Status\":{\"PVAC_Fout\":0,\"PVAC_Pout\":0,\"PVAC_State\":\"PVAC_Init\",\"PVAC_Vout\":0,\"isMIA\":true},\"alerts\":{\"active\":[],\"isComplete\":false,\"isMIA\":true},\"packagePartNumber\":\"\",\"packageSerialNumber\":\"\",\"subPackagePartNumber\":\"\",\"subPackageSerialNumber\":\"\"},{\"PVAC_InfoMsg\":{\"PVAC_appGitHash\":[0,0,0,0,0,0,0]},\"PVAC_Logging\":{\"PVAC_PVCurrent_A\":0,\"PVAC_PVCurrent_B\":0,\"PVAC_PVCurrent_C\":0,\"PVAC_PVCurrent_D\":0,\"PVAC_PVMeasuredVoltage_A\":0,\"PVAC_PVMeasuredVoltage_B\":0,\"PVAC_PVMeasuredVoltage_C\":0,\"PVAC_PVMeasuredVoltage_D\":0,\"PVAC_VL1Ground\":0,\"PVAC_VL2Ground\":0,\"isMIA\":true},\"PVAC_Status\":{\"PVAC_Fout\":0,\"PVAC_Pout\":0,\"PVAC_State\":\"PVAC_Init\",\"PVAC_Vout\":0,\"isMIA\":true},\"alerts\":{\"active\":[],\"isComplete\":false,\"isMIA\":true},\"packagePartNumber\":\"\",\"packageSerialNumber\":\"\",\"subPackagePartNumber\":\"\",\"subPackageSerialNumber\":\"\"},{\"PVAC_InfoMsg\":{\"PVAC_appGitHash\":[0,0,0,0,0,0,0]},\"PVAC_Logging\":{\"PVAC_PVCurrent_A\":0,\"PVAC_PVCurrent_B\":0,\"PVAC_PVCurrent_C\":0,\"PVAC_PVCurrent_D\":0,\"PVAC_PVMeasuredVoltage_A\":0,\"PVAC_PVMeasuredVoltage_B\":0,\"PVAC_PVMeasuredVoltage_C\":0,\"PVAC_PVMeasuredVoltage_D\":0,\"PVAC_VL1Ground\":0,\"PVAC_VL2Ground\":0,\"isMIA\":true},\"PVAC_Status\":{\"PVAC_Fout\":0,\"PVAC_Pout\":0,\"PVAC_State\":\"PVAC_Init\",\"PVAC_Vout\":0,\"isMIA\":true},\"alerts\":{\"active\":[],\"isComplete\":false,\"isMIA\":true},\"packagePartNumber\":\"\",\"packageSerialNumber\":\"\",\"subPackagePartNumber\":\"\",\"subPackageSerialNumber\":\"\"}],\"PVS\":[{\"PVS_Status\":{\"PVS_SelfTestState\":\"PVS_SelfTestOff\",\"PVS_State\":\"PVS_Active\",\"PVS_StringA_Connected\":true,\"PVS_StringB_Connected\":false,\"PVS_StringC_Connected\":true,\"PVS_StringD_Connected\":true,\"PVS_vLL\":243.60000000000002,\"isMIA\":false},\"alerts\":{\"active\":[\"PVS_a018_MciStringB\",\"PVS_a060_MciClose\"],\"isComplete\":true,\"isMIA\":false}},{\"PVS_Status\":{\"PVS_SelfTestState\":\"PVS_SelfTestOff\",\"PVS_State\":\"PVS_Off\",\"PVS_StringA_Connected\":false,\"PVS_StringB_Connected\":false,\"PVS_StringC_Connected\":false,\"PVS_StringD_Connected\":false,\"PVS_vLL\":0,\"isMIA\":true},\"alerts\":{\"active\":[],\"isComplete\":false,\"isMIA\":true}},{\"PVS_Status\":{\"PVS_SelfTestState\":\"PVS_SelfTestOff\",\"PVS_State\":\"PVS_Off\",\"PVS_StringA_Connected\":false,\"PVS_StringB_Connected\":false,\"PVS_StringC_Connected\":false,\"PVS_StringD_Connected\":false,\"PVS_vLL\":0,\"isMIA\":true},\"alerts\":{\"active\":[],\"isComplete\":false,\"isMIA\":true}},{\"PVS_Status\":{\"PVS_SelfTestState\":\"PVS_SelfTestOff\",\"PVS_State\":\"PVS_Off\",\"PVS_StringA_Connected\":false,\"PVS_StringB_Connected\":false,\"PVS_StringC_Connected\":false,\"PVS_StringD_Connected\":false,\"PVS_vLL\":0,\"isMIA\":true},\"alerts\":{\"active\":[],\"isComplete\":false,\"isMIA\":true}},{\"PVS_Status\":{\"PVS_SelfTestState\":\"PVS_SelfTestOff\",\"PVS_State\":\"PVS_Off\",\"PVS_StringA_Connected\":false,\"PVS_StringB_Connected\":false,\"PVS_StringC_Connected\":false,\"PVS_StringD_Connected\":false,\"PVS_vLL\":0,\"isMIA\":true},\"alerts\":{\"active\":[],\"isComplete\":false,\"isMIA\":true}},{\"PVS_Status\":{\"PVS_SelfTestState\":\"PVS_SelfTestOff\",\"PVS_State\":\"PVS_Off\",\"PVS_StringA_Connected\":false,\"PVS_StringB_Connected\":false,\"PVS_StringC_Connected\":false,\"PVS_StringD_Connected\":false,\"PVS_vLL\":0,\"isMIA\":true},\"alerts\":{\"active\":[],\"isComplete\":false,\"isMIA\":true}},{\"PVS_Status\":{\"PVS_SelfTestState\":\"PVS_SelfTestOff\",\"PVS_State\":\"PVS_Off\",\"PVS_StringA_Connected\":false,\"PVS_StringB_Connected\":false,\"PVS_StringC_Connected\":false,\"PVS_StringD_Connected\":false,\"PVS_vLL\":0,\"isMIA\":true},\"alerts\":{\"active\":[],\"isComplete\":false,\"isMIA\":true}},{\"PVS_Status\":{\"PVS_SelfTestState\":\"PVS_SelfTestOff\",\"PVS_State\":\"PVS_Off\",\"PVS_StringA_Connected\":false,\"PVS_StringB_Connected\":false,\"PVS_StringC_Connected\":false,\"PVS_StringD_Connected\":false,\"PVS_vLL\":0,\"isMIA\":true},\"alerts\":{\"active\":[],\"isComplete\":false,\"isMIA\":true}}],\"SYNC\":{\"METER_X_AcMeasurements\":{\"METER_X_CTA_I\":3.3365,\"METER_X_CTA_InstReactivePower\":-163,\"METER_X_CTA_InstRealPower\":262,\"METER_X_CTB_I\":2.6390000000000002,\"METER_X_CTB_InstReactivePower\":-80,\"METER_X_CTB_InstRealPower\":-289,\"METER_X_CTC_I\":0,\"METER_X_CTC_InstReactivePower\":0,\"METER_X_CTC_InstRealPower\":0,\"METER_X_VL1N\":121.69,\"METER_X_VL2N\":121.76,\"METER_X_VL3N\":0,\"isComplete\":true,\"isMIA\":false,\"lastRxTime\":\"2023-11-21T13:10:29-08:00\"},\"METER_Y_AcMeasurements\":{\"METER_Y_CTA_I\":0,\"METER_Y_CTA_InstReactivePower\":0,\"METER_Y_CTA_InstRealPower\":0,\"METER_Y_CTB_I\":0,\"METER_Y_CTB_InstReactivePower\":0,\"METER_Y_CTB_InstRealPower\":0,\"METER_Y_CTC_I\":0,\"METER_Y_CTC_InstReactivePower\":0,\"METER_Y_CTC_InstRealPower\":0,\"METER_Y_VL1N\":121.69,\"METER_Y_VL2N\":121.76,\"METER_Y_VL3N\":0,\"isComplete\":true,\"isMIA\":false,\"lastRxTime\":\"2023-11-21T13:10:29-08:00\"},\"SYNC_InfoMsg\":{\"SYNC_appGitHash\":[39,98,111,152,166,108,173],\"isMIA\":false},\"SYNC_Status\":{\"lastRxTime\":\"2023-11-21T13:10:29-08:00\"},\"packagePartNumber\":\"1493315-01-F\",\"packageSerialNumber\":\"JBL23456789012\"},\"THC\":[{\"THC_InfoMsg\":{\"THC_appGitHash\":[39,98,111,152,166,108,173],\"isComplete\":true,\"isMIA\":false},\"THC_Logging\":{\"THC_LOG_PW_2_0_EnableLineState\":\"ENABLE_LINE_HIGH\"},\"packagePartNumber\":\"2012170-25-E\",\"packageSerialNumber\":\"TG123456789012\"},{\"THC_InfoMsg\":{\"THC_appGitHash\":[39,98,111,152,166,108,173],\"isComplete\":true,\"isMIA\":false},\"THC_Logging\":{\"THC_LOG_PW_2_0_EnableLineState\":\"ENABLE_LINE_HIGH\"},\"packagePartNumber\":\"3012170-05-B\",\"packageSerialNumber\":\"TG123456789012\"},{\"THC_InfoMsg\":{\"THC_appGitHash\":[0,0,0,0,0,0,0],\"isComplete\":false,\"isMIA\":true},\"THC_Logging\":{\"THC_LOG_PW_2_0_EnableLineState\":\"ENABLE_LINE_LOW\"},\"packagePartNumber\":\"\",\"packageSerialNumber\":\"\"},{\"THC_InfoMsg\":{\"THC_appGitHash\":[0,0,0,0,0,0,0],\"isComplete\":false,\"isMIA\":true},\"THC_Logging\":{\"THC_LOG_PW_2_0_EnableLineState\":\"ENABLE_LINE_LOW\"},\"packagePartNumber\":\"\",\"packageSerialNumber\":\"\"},{\"THC_InfoMsg\":{\"THC_appGitHash\":[0,0,0,0,0,0,0],\"isComplete\":false,\"isMIA\":true},\"THC_Logging\":{\"THC_LOG_PW_2_0_EnableLineState\":\"ENABLE_LINE_LOW\"},\"packagePartNumber\":\"\",\"packageSerialNumber\":\"\"},{\"THC_InfoMsg\":{\"THC_appGitHash\":[0,0,0,0,0,0,0],\"isComplete\":false,\"isMIA\":true},\"THC_Logging\":{\"THC_LOG_PW_2_0_EnableLineState\":\"ENABLE_LINE_LOW\"},\"packagePartNumber\":\"\",\"packageSerialNumber\":\"\"},{\"THC_InfoMsg\":{\"THC_appGitHash\":[0,0,0,0,0,0,0],\"isComplete\":false,\"isMIA\":true},\"THC_Logging\":{\"THC_LOG_PW_2_0_EnableLineState\":\"ENABLE_LINE_LOW\"},\"packagePartNumber\":\"\",\"packageSerialNumber\":\"\"},{\"THC_InfoMsg\":{\"THC_appGitHash\":[0,0,0,0,0,0,0],\"isComplete\":false,\"isMIA\":true},\"THC_Logging\":{\"THC_LOG_PW_2_0_EnableLineState\":\"ENABLE_LINE_LOW\"},\"packagePartNumber\":\"\",\"packageSerialNumber\":\"\"},{\"THC_InfoMsg\":{\"THC_appGitHash\":[0,0,0,0,0,0,0],\"isComplete\":false,\"isMIA\":true},\"THC_Logging\":{\"THC_LOG_PW_2_0_EnableLineState\":\"ENABLE_LINE_LOW\"},\"packagePartNumber\":\"\",\"packageSerialNumber\":\"\"},{\"THC_InfoMsg\":{\"THC_appGitHash\":[0,0,0,0,0,0,0],\"isComplete\":false,\"isMIA\":true},\"THC_Logging\":{\"THC_LOG_PW_2_0_EnableLineState\":\"ENABLE_LINE_LOW\"},\"packagePartNumber\":\"\",\"packageSerialNumber\":\"\"}]},\"enumeration\":null,\"firmwareUpdate\":{\"isUpdating\":false,\"msa\":null,\"powerwalls\":[null,null],\"pvInverters\":null,\"sync\":null},\"inverterSelfTests\":null,\"phaseDetection\":null},\"neurio\":{\"isDetectingWiredMeters\":false,\"pairings\":[],\"readings\":[{\"dataRead\":[{\"currentA\":11.140000343322754,\"reactivePowerVAR\":-11.130000114440918,\"realPowerW\":1356.5699462890625,\"voltageV\":121.95999908447266},{\"currentA\":0.009999999776482582,\"reactivePowerVAR\":-0.029999999329447746,\"realPowerW\":-0.029999999329447746,\"voltageV\":122.05999755859375},{\"currentA\":0.009999999776482582,\"reactivePowerVAR\":-0.029999999329447746,\"realPowerW\":-0.029999999329447746,\"voltageV\":122.0999984741211},{\"currentA\":0.009999999776482582,\"reactivePowerVAR\":-0.05999999865889549,\"realPowerW\":-0.12999999523162842,\"voltageV\":121.95999908447266}],\"serial\":\"VAH1234567890\",\"timestamp\":\"2023-11-21T13:10:29-08:00\"}]},\"pw3Can\":{\"firmwareUpdate\":{\"isUpdating\":false,\"progress\":null}},\"system\":{\"sitemanagerStatus\":{\"isRunning\":true},\"time\":\"2023-11-21T13:10:29-08:00\",\"updateUrgencyCheck\":null}}" } } } 2 { 1: 1 }Researchers and Credit
Beta Was this translation helpful? Give feedback.
All reactions