No data with Neo Gateway #437
Comments
|
First let's make sure pypowerwall is getting data from the cloud: Go to http://localhost:8675/example.html (change localhost to the address of your dashboard, as you did to get stats above) - it should load the power flow animation with power data, etc.
It is odd that the Firmware version is missing. As with the error message you posted, it seems you can get some of the APIs but not all of them? Try these different URI's on pypowerwall directly to see which load, like: http://localhost:8675/aggregates and these others as you saw ins tats: URI: /soe | 110 |
|
Example.html
SOE:
TEMPS: Freq: Strings: Alerts/pw Pod Stats Edit: Adding /vitals output: { |
|
Ok, I'm sorry, it took me a while to clue in that you do not have a Powerwall. This is a Solar only system, correct? The data shown is correct for that since those APIs are about Powerwall metrics. Can you please test http://localhost:8675/aggregates and http://localhost:8675/csv ? The "broken" image for the powerflow animation will show up if a browser refuses to render an IFrame. You should see the animation outside an iFrame using http://localhost:8675/ by itself. |
|
Solar Only, correct: {
|
The good news is that you are getting power data! I assume http://10.1.200.19:8675/csv also works? This could be a bug in the code where it is throwing an uncaught exception. The page not loading is puzzling. Can you run I could also use your help to find out what is blowing up inside of pypowerwall during those renders. Can you edit the Then Thanks for your help! |
|
I missed the screenshot for csv, but nothing returns 'curl: (52) Empty reply from server' Debug when going to csv or root Exception occurred during processing of request from ('10.1.100.9', 61562)
|
|
Here is startup logs: 2024-02-25T23:39:44.341130532Z 02/25/2024 03:39:44 PM [proxy] [INFO] pyPowerwall Proxy Server - Cloud Mode |
|
Ok, I see the bug in the code. Version is expected but we are getting none back for your installation. Additionally, the csv code is likely getting a null back for battery so I can catch that as well. I can make the change. You mention you are running a custom setup. I'll upload a test pypowerwall container to try if you are willing. |
|
Absolutely willing to assist. |
|
Ok, I have a test image that hopefully has the right fixes: jasonacox/pypowerwall:0.7.7t41 If you are using the |
|
So far so good: CSV output: Debug output: 2024-02-26T01:22:43.194570281Z 02/25/2024 05:22:43 PM [pypowerwall.cloud] [DEBUG] -- cloud: Returning cached SITE_CONFIG data Waiting on dashboard data to populate |
|
That's great news! You can turn off the DEBUG mode so you don't fill your disk with those. :) When you see some data, can you paste a screenshot? Would love to see your custom dashboard if you don't mind sharing. I'm going to queue up a release since you are probably not alone. Thanks for helping find this bug! |
How is looking? Is telegraf transferring the data? |
|
Upon checking, it looks like the following is populating:
I'm sure I'm reading a metric wrong. When I'm back in front of my PC, I'll output the tables telegraf made. But the data is coming in. |
|
Happy to report no issues. Here's a sample (from an overview dash I'm making) Here's the field key's populating as well: fieldKey fieldType battery_energy_exported float |
|
That's great news @Nordictrack ! Thanks for confirming and nice dashboard!! If you don't mind helping, you may not want to add the power flow animation to your dashboard (you could if you wanted) but could you check it as well? URL http://10.1.200.19:8675/example.html ? The one you posted earlier showed "grid offline" and numbers that didn't add up. I would like to confirm if we still have an issue with some of the data we are creating for the animation. 
Thanks for your help! |
|
I did notice yesterday that the grid shows no data on that, but the site_instant_power data does have the correct number when I compare it to the Tesla & Tidbyt app. Right now, it's showing this when it should be pulling from the grid: 
edit: changed load_instant_power to site_instant_power 
|
|
Thanks @Nordictrack ! This is helpful. I believe I have the wrong mapping on the grid status for Solar only systems. Can you provide the results of these calls? Replace localhost with the host running pypowerwall: http://localhost:8675/api/site_info I'm also going to see if I can either remove the Powerwall icon in the power flow animation, or at least remove the kW and % values. |
|
Site Info {
"max_system_energy_kWh": 0,
"max_system_power_kW": 0,
"site_name": "Vault 21",
"timezone": null,
"max_site_meter_power_kW": null,
"min_site_meter_power_kW": null,
"nominal_system_energy_kWh": 0,
"nominal_system_power_kW": 0,
"panel_max_current": null,
"grid_code": {
"grid_code": null,
"grid_voltage_setting": null,
"grid_freq_setting": null,
"grid_phase_setting": null,
"country": null,
"state": null,
"utility": "NV Energy"
}
}Sitemaster {
"status": "StatusUp",
"running": true,
"connected_to_tesla": true,
"power_supply_mode": false,
"can_reboot": "Yes"
}system_status/soe {
"percentage": 0
}system_status/grid_status {
"grid_status": "SystemIslandedActive",
"grid_services_active": false
}powerwalls {
"enumerating": false,
"updating": false,
"checking_if_offgrid": false,
"running_phase_detection": false,
"phase_detection_last_error": "no phase information",
"bubble_shedding": false,
"on_grid_check_error": "on grid check not run",
"grid_qualifying": false,
"grid_code_validating": false,
"phase_detection_not_available": true,
"powerwalls": [
{
"Type": "",
"PackagePartNumber": "2012170-25-E",
"PackageSerialNumber": "TG1234567890G1",
"type": "SolarPowerwall",
"grid_state": "Grid_Uncompliant",
"grid_reconnection_time_seconds": 0,
"under_phase_detection": false,
"updating": false,
"commissioning_diagnostic": {
"name": "Commissioning",
"category": "InternalComms",
"disruptive": false,
"inputs": null,
"checks": [
{
"name": "CAN connectivity",
"status": "fail",
"start_time": "2023-12-16T08:34:17.3068631-08:00",
"end_time": "2023-12-16T08:34:17.3068696-08:00",
"message": "Cannot perform this action with site controller running. From landing page, either \"STOP SYSTEM\" or \"RUN WIZARD\" to proceed.",
"results": {},
"debug": {},
"checks": null
},
{
"name": "Enable switch",
"status": "fail",
"start_time": "2023-12-16T08:34:17.306875474-08:00",
"end_time": "2023-12-16T08:34:17.306880724-08:00",
"message": "Cannot perform this action with site controller running. From landing page, either \"STOP SYSTEM\" or \"RUN WIZARD\" to proceed.",
"results": {},
"debug": {},
"checks": null
},
{
"name": "Internal communications",
"status": "fail",
"start_time": "2023-12-16T08:34:17.306886099-08:00",
"end_time": "2023-12-16T08:34:17.306891223-08:00",
"message": "Cannot perform this action with site controller running. From landing page, either \"STOP SYSTEM\" or \"RUN WIZARD\" to proceed.",
"results": {},
"debug": {},
"checks": null
},
{
"name": "Firmware up-to-date",
"status": "fail",
"start_time": "2023-12-16T08:34:17.306896598-08:00",
"end_time": "2023-12-16T08:34:17.306901723-08:00",
"message": "Cannot perform this action with site controller running. From landing page, either \"STOP SYSTEM\" or \"RUN WIZARD\" to proceed.",
"results": {},
"debug": {},
"checks": null
}
],
"alert": false
},
"update_diagnostic": {
"name": "Firmware Update",
"category": "InternalComms",
"disruptive": true,
"inputs": null,
"checks": [
{
"name": "Solar Inverter firmware",
"status": "not_run",
"start_time": null,
"end_time": null,
"progress": 0,
"results": null,
"debug": null,
"checks": null
},
{
"name": "Solar Safety firmware",
"status": "not_run",
"start_time": null,
"end_time": null,
"progress": 0,
"results": null,
"debug": null,
"checks": null
},
{
"name": "Grid code",
"status": "not_run",
"start_time": null,
"end_time": null,
"progress": 0,
"results": null,
"debug": null,
"checks": null
},
{
"name": "Powerwall firmware",
"status": "not_run",
"start_time": null,
"end_time": null,
"progress": 0,
"results": null,
"debug": null,
"checks": null
},
{
"name": "Battery firmware",
"status": "not_run",
"start_time": null,
"end_time": null,
"progress": 0,
"results": null,
"debug": null,
"checks": null
},
{
"name": "Inverter firmware",
"status": "not_run",
"start_time": null,
"end_time": null,
"progress": 0,
"results": null,
"debug": null,
"checks": null
},
{
"name": "Grid code",
"status": "not_run",
"start_time": null,
"end_time": null,
"progress": 0,
"results": null,
"debug": null,
"checks": null
}
],
"alert": false
},
"bc_type": null,
"in_config": true
},
{
"Type": "",
"PackagePartNumber": "3012170-05-B",
"PackageSerialNumber": "TG1234567890G1",
"type": "ACPW",
"grid_state": "Grid_Uncompliant",
"grid_reconnection_time_seconds": 0,
"under_phase_detection": false,
"updating": false,
"commissioning_diagnostic": {
"name": "Commissioning",
"category": "InternalComms",
"disruptive": false,
"inputs": null,
"checks": [
{
"name": "CAN connectivity",
"status": "fail",
"start_time": "2023-12-16T08:34:17.320856307-08:00",
"end_time": "2023-12-16T08:34:17.320940302-08:00",
"message": "Cannot perform this action with site controller running. From landing page, either \"STOP SYSTEM\" or \"RUN WIZARD\" to proceed.",
"results": {},
"debug": {},
"checks": null
},
{
"name": "Enable switch",
"status": "fail",
"start_time": "2023-12-16T08:34:17.320949301-08:00",
"end_time": "2023-12-16T08:34:17.320955301-08:00",
"message": "Cannot perform this action with site controller running. From landing page, either \"STOP SYSTEM\" or \"RUN WIZARD\" to proceed.",
"results": {},
"debug": {},
"checks": null
},
{
"name": "Internal communications",
"status": "fail",
"start_time": "2023-12-16T08:34:17.320960676-08:00",
"end_time": "2023-12-16T08:34:17.320966176-08:00",
"message": "Cannot perform this action with site controller running. From landing page, either \"STOP SYSTEM\" or \"RUN WIZARD\" to proceed.",
"results": {},
"debug": {},
"checks": null
},
{
"name": "Firmware up-to-date",
"status": "fail",
"start_time": "2023-12-16T08:34:17.32097155-08:00",
"end_time": "2023-12-16T08:34:17.3209768-08:00",
"message": "Cannot perform this action with site controller running. From landing page, either \"STOP SYSTEM\" or \"RUN WIZARD\" to proceed.",
"results": {},
"debug": {},
"checks": null
}
],
"alert": false
},
"update_diagnostic": {
"name": "Firmware Update",
"category": "InternalComms",
"disruptive": true,
"inputs": null,
"checks": [
{
"name": "Powerwall firmware",
"status": "not_run",
"start_time": null,
"end_time": null,
"progress": 0,
"results": null,
"debug": null,
"checks": null
},
{
"name": "Battery firmware",
"status": "not_run",
"start_time": null,
"end_time": null,
"progress": 0,
"results": null,
"debug": null,
"checks": null
},
{
"name": "Inverter firmware",
"status": "not_run",
"start_time": null,
"end_time": null,
"progress": 0,
"results": null,
"debug": null,
"checks": null
},
{
"name": "Grid code",
"status": "not_run",
"start_time": null,
"end_time": null,
"progress": 0,
"results": null,
"debug": null,
"checks": null
}
],
"alert": false
},
"bc_type": null,
"in_config": true
}
],
"gateway_din": "1232100-00-E--TG1234567890G1",
"sync": {
"updating": false,
"commissioning_diagnostic": {
"name": "Commissioning",
"category": "InternalComms",
"disruptive": false,
"inputs": null,
"checks": [
{
"name": "CAN connectivity",
"status": "fail",
"start_time": "2023-12-16T08:34:17.321101293-08:00",
"end_time": "2023-12-16T08:34:17.321107918-08:00",
"message": "Cannot perform this action with site controller running. From landing page, either \"STOP SYSTEM\" or \"RUN WIZARD\" to proceed.",
"results": {},
"debug": {},
"checks": null
},
{
"name": "Firmware up-to-date",
"status": "fail",
"start_time": "2023-12-16T08:34:17.321113792-08:00",
"end_time": "2023-12-16T08:34:17.321118917-08:00",
"message": "Cannot perform this action with site controller running. From landing page, either \"STOP SYSTEM\" or \"RUN WIZARD\" to proceed.",
"results": {},
"debug": {},
"checks": null
}
],
"alert": false
},
"update_diagnostic": {
"name": "Firmware Update",
"category": "InternalComms",
"disruptive": true,
"inputs": null,
"checks": [
{
"name": "Synchronizer firmware",
"status": "not_run",
"start_time": null,
"end_time": null,
"progress": 0,
"results": null,
"debug": null,
"checks": null
},
{
"name": "Islanding configuration",
"status": "not_run",
"start_time": null,
"end_time": null,
"progress": 0,
"results": null,
"debug": null,
"checks": null
},
{
"name": "Grid code",
"status": "not_run",
"start_time": null,
"end_time": null,
"progress": 0,
"results": null,
"debug": null,
"checks": null
}
],
"alert": false
}
},
"msa": null,
"states": null
}troubleshooting/problems {
"problems": []
} |
|
Thanks! This is a bug - I'll work on a fix...
{
"grid_status": "SystemIslandedActive",
"grid_services_active": false
} |
|
If it's worth anything, this is a pre-tesla solarcity install (tesla installed it but gave me solar city gear) and those use a "power blaster" to sense grid usage. |
|
Hi @Nordictrack - I made an update to better handles the grid status data for cloud-mode configurations. If you update, it would be interesting to see if the power flow animation now shows the grid data correctly. If you are using the powerwall.yml file (or simliar) with docker-compose, you can edit that file and change the image for pypowerwall to |
|
Success on the Power flow!
|
|
That's great news!! Thanks for the help. I think we could create a Something like... 
Also, nice looking dashboard! Thanks for sharing that. |
|
Ok, I have another update. I created a solar.js file to update the animation for solar-only: 
How to set it up:
|
|
Test was successful. 
|
|
That's great! If you ever build a dashboard that includes that, I would love to see it. 😁 Thank for all your help. This means that any Tesla Solar-only customers can use our dashboards, including the power flow animation. |
Problem Description
No data in any dashboard. All null. No data in db.
System Details
Describe the host system you are trying to use for the Dashboard:
Verify Tool Output
Checking pypowerwall
Checking telegraf
(Note, I have a separate grafana instance and don't use the other containers, all data is feeding properly to my central influxdb)
I also keep seeing this in the pypowerwall container logs
2024-02-25T19:08:25.097889627Z 02/25/2024 11:08:25 AM [pypowerwall.cloud] [ERROR] Failed to retrieve ENERGY_SITE_BACKUP_TIME_REMAINING - HTTPError('400 Client Error: https://powergate.prd.sn.tesla.services:443/api/v4/energy_site/backup_time_remaining => {:Message=>"Error getting backup time remaining", :Status=>400} for url: https://owner-api.teslamotors.com/api/1/energy_sites/2640038/backup_time_remaining?language=en')
Telegraf shows no errors and pypowerwall shows this:
pypowerwall | 0.7.7 Proxy t40
gets | 782
errors | 0
timeout | 2
ts | 1708888639
start | 1708888087
clear | 1708888087
uptime | 0:09:12
mem | 35356
site_name | Vault 21
cloudmode | True
siteid | 2640038
counter | 63
authmode | cookie
URI: /aggregates | 112
URI: /soe | 110
URI: /temps/pw | 110
URI: /freq | 110
URI: /strings | 110
URI: /alerts/pw | 110
URI: /pod | 110
URI: /stats | 6
I know the neo sends data because my Tidbyt shows the same data as the tesla app ( at this time: 4kW gen, 2.9kW to home, 1.1kW back to the grid)
Can't think of where I didn't configure something as it's working, just not getting anything.
The text was updated successfully, but these errors were encountered: