ran ./upgrade.sh how to switch to tedapi

[anderep]

ok i ran upgrade, kind of expected it to prompt for setup dialog but it didn't. what files to i need to edit to switch to tedapi?

i'm logged into gateway with second wifi adapter and have access to 192.168.91.1.

do i want configuration mode 1 [Local Access (Powerwall 1, 2, or + using the Tesla Gateway on LAN) - Default] or 4 [4 - Powerwall 3 (Powerwall 3 using the local Tesla Gateway)]????

[jasonacox]

Upgrade doesn't change your setup, it just upgrades the software.

Run setup.sh and select 4 - Powerwall 3 and it will force it to only use TEDAPI. The option 1 will attempt both and will use both. I'm thinking about removing that to make it easier for people.

[anderep]

found this:
#392 (comment)

[anderep]

./setup.sh ... got to the section "current credentials:" do i want to "update these credentials"???
I'm assuming yes and edit PW_HOST to 192.168.91.1
anything else?

[jasonacox]

Yes, you will need to update credentials. You're doing fine! You can do this.

[jasonacox]

Powerwall Dashboard (v4.6.0) - SETUP
-----------------------------------------
Select configuration mode:

Current: Local Access

 1 - Local Access   (Powerwall 1, 2, or + using the Tesla Gateway on LAN) - Default
 2 - Tesla Cloud    (Solar-only systems or Powerwalls without LAN access)
 3 - FleetAPI Cloud (Powerwall systems using Official Telsa API)
 4 - Powerwall 3    (Powerwall 3 using the local Tesla Gateway)

Select mode: [1] 4

Timezone (leave blank for America/Los_Angeles)
Enter Timezone: 

Current Credentials:

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=XXXXXXXXXX

Update these credentials? [y/N] y

Setting credentials for Powerwall 3...
Found Powerwall Gateway at 192.168.91.1
Use this IP? [Y/n] y

Congratulations!
Extended Device Metrics (vitals) are available on this endpoint via TEDAPI.
However, you will need the Gateway password to access them.
This password is often found on a QR code on the Powerwall.

Enter Gateway Password or leave blank to disable: XXXXXXXXXX   

[anderep]

ok it prompted ..91.1
is my password the same. it works when logging in thru browser to 192.168.92.1
also, weather do i need to setup weather data? it was setup before. can i say no and it wll be as before???

[jasonacox]

That gateway password is the one for the WiFi access point, not the portal login (browser). It is often on the QR sticker on the gateway or, if you have PW3's, on the Powerwall itself.

You can say no to weather. It will not change your current setup.

[anderep]

`Waiting for InfluxDB to start...
up!
Setup InfluxDB Data...
2025/02/01 18:36:08 error: continuous query already exists
Fetching local weather...
weather411
------------------[ Final Setup Instructions ]-----------------

Open Grafana at http://localhost:9000/ ... use admin/admin for login.

To complete Grafana Setup:

• From 'Dashboard\Browse', select 'New/Import', browse to /home/eric/Powerwall-Dashboard/dashboards
  and upload 'dashboard.json'.

NOTE: The datasources for InfluxDB and SunAndMoon are already configured.
If you need to modify them via Configuration\Data Sources:

• InfluxDB

  • URL: 'http://influxdb:8086'
  • Database: 'powerwall'
  • Min time interval: '5s'
  • Click "Save & test" button

• Sun and Moon

  • Enter your latitude and longitude (tool here: https://bit.ly/3wYNaI1 )
  • Click "Save & test" button
    `

got error "error: continuous query already exists" i assume ignore.

do i need to setup my dashboard again? my old dashboard isn't working. perhaps i need to reboot? (edit: no need to modify dashboard)

[jasonacox]

got error "error: continuous query already exists" i assume ignore.

Yes, this is setup ensuring the CQ's are in place. I debated over masking them but it would also mask any real errors.

do i need to setup my dashboard again? my old dashboard isn't working. perhaps i need to reboot?

Importing the dashboard.json is optional if you already have one.

[anderep]

OK, powerflow is back. any hope to mining data from nerrio's again???

[anderep]

my enphase power is back!!! but tesla power isn't...

[jasonacox]

OK, powerflow is back. any hope to mining data from nerrio's again???

I don't know what this would be. It looks like you have a custom dashboard. How were you pulling this data before?

You can see the data that is being pulled from TEDAPI here (replace pypowerwall with the host running your dashboard):

	"http://pypowerwall:8675/aggregates",
	"http://pypowerwall:8675/soe",
	"http://pypowerwall:8675/strings",
	"http://pypowerwall:8675/temps/pw",
	"http://pypowerwall:8675/freq",
	"http://pypowerwall:8675/pod"
	"http://pypowerwall:8675/alerts/pw"

And the raw data from TEDAPI that creates the above is here:

	http://pypowerwall:8675/tedapi/status
	http://pypowerwall:8675/tedapi/config
	http://pypowerwall:8675/tedapi/components

[anderep]

i see the neurio data in tedapi/status:

        "serial": "VAH5037AB3569",
        "timestamp": "2025-02-02T08:30:51-06:00"
      },
      {
        "dataRead": [
          {
            "currentA": 0.639999985694885,
            "reactivePowerVAR": -13.210000038147,
            "realPowerW": 64.8099975585938,
            "voltageV": 126.129997253418
          },
          {
            "currentA": 0.00999999977648258,
            "reactivePowerVAR": -0.0299999993294477,
            "realPowerW": 0.0199999995529652,
            "voltageV": 126.330001831055
          },
          {
            "currentA": 0.00999999977648258,
            "reactivePowerVAR": -0.100000001490116,
            "realPowerW": -0.0500000007450581,
            "voltageV": 126.339996337891
          },
          {
            "currentA": 24.3400001525879,
            "reactivePowerVAR": 607.599975585938,
            "realPowerW": 2994.82006835938,
            "voltageV": 126.129997253418
          }
        ],
        "serial": "VAH4635AB1496",
        "timestamp": "2025-02-02T08:30:51-06:00"
      }
    ]
  },

edit: replaced with active solar production.

was when it was work before, from my old thread #254:

"NEURIO--VAH4635AB1496": {
        "NEURIO_CT0_InstRealPower": 2373.679931640625,
        "NEURIO_CT0_Location": "solar",
        "NEURIO_CT3_InstRealPower": 11851.8203125,
        "NEURIO_CT3_Location": "solar",
        "componentParentDin": "STSTSM--1232100-00-H--GF22227000014F",
        "firmwareVersion": "1.7.2-Tesla",
        "lastCommunicationTime": 1682369955,
        "manufacturer": "NEURIO",
        "meterAttributes": {
            "meterLocation": [
                4,
                4
            ]
        },
        "serialNumber": "VAH4635AB1496"
    },

[jasonacox]

It looks like you put the polling for those in the telegraf.local file and were using this url:

http://pypowerwall:8675/vitals

Do you see a NEURIO section in vitals?

[anderep]

Vitals is missing CT0, Would that be on our interpretation of the data? yeah, vitals says it is generated from tedapi... so we just need to fix tedapi...

{
    "NEURIO--VAH4635AB1496": {
        "NEURIO_CT3_InstCurrent": 32.79999923706055,
        "NEURIO_CT3_InstReactivePower": 603.4500122070312,
        "NEURIO_CT3_InstRealPower": 8124.52001953125,
        "NEURIO_CT3_InstVoltage": 125.7699966430664,
        "NEURIO_CT3_Location": "solar",
        "componentParentDin": "1232100-00-H--GF22227000014F",
        "firmwareVersion": null,
        "lastCommunicationTime": "2025-02-02T09:05:14-06:00",
        "manufacturer": "NEURIO",
        "meterAttributes": {
            "meterLocation": []
        },
        "serialNumber": "VAH4635AB1496"
    },
    "NEURIO--VAH5037AB3569": {
        "NEURIO_CT0_InstCurrent": 0.029999999329447746,
        "NEURIO_CT0_InstReactivePower": -0.3199999928474426,
        "NEURIO_CT0_InstRealPower": 2.7699999809265137,
        "NEURIO_CT0_InstVoltage": 126.26000213623047,
        "NEURIO_CT0_Location": "site",
        "NEURIO_CT1_InstCurrent": 0.019999999552965164,
        "NEURIO_CT1_InstReactivePower": 0.05999999865889549,
        "NEURIO_CT1_InstRealPower": 2.3299999237060547,
        "NEURIO_CT1_InstVoltage": 126.54000091552734,
        "NEURIO_CT1_Location": "site",
        "componentParentDin": "1232100-00-H--GF22227000014F",
        "firmwareVersion": null,
        "lastCommunicationTime": "2025-02-02T09:05:14-06:00",
        "manufacturer": "NEURIO",
        "meterAttributes": {
            "meterLocation": []
        },
        "serialNumber": "VAH5037AB3569"
    },

[anderep]

config list that there are two solar meters, doesn't identify the channels of the neurio that i see.
edit: "cts" lists the channels in the false/true data.... CT0 and CT3

/tedapi/config:

    {
      "location": "solar",
      "type": "neurio_w2_tcp",
      "cts": [true, false, false, false],
      "inverted": [false, false, false, false],
      "connection": {
        "ip_address": "PWRview-63848",
        "port": 443,
        "short_id": "63848",
        "device_serial": "VAH4635AB1496",
        "neurio_connected": true,
        "https_conf": {
          "client_cert": "/var/lib/neurio/neurio.crt",
          "client_key": "/var/lib/neurio/neurio.key",
          "server_ca_cert": "/etc/neurio-ca.crt",
          "server_name": "04-71-4b-03-cc-b9",
          "max_idle_conns_per_host": 1
        }
      },
      "real_power_scale_factor": 2
    },
    {
      "location": "solar",
      "type": "neurio_w2_tcp",
      "cts": [false, false, false, true],
      "inverted": [false, false, false, false],
      "connection": {
        "ip_address": "PWRview-63848",
        "port": 443,
        "short_id": "63848",
        "device_serial": "VAH4635AB1496",
        "neurio_connected": true,
        "https_conf": {
          "client_cert": "/var/lib/neurio/neurio.crt",
          "client_key": "/var/lib/neurio/neurio.key",
          "server_ca_cert": "/etc/neurio-ca.crt",
          "server_name": "04-71-4b-03-cc-b9",
          "max_idle_conns_per_host": 1
        }
      },
      "real_power_scale_factor": 2
    },

[jasonacox]

Thanks @anderep Would you be able to save and send me the full /tedapi/config and /tedapi/status files? At a minimum, I need to see the full payload related to the Neurio's (e.g. meters section of config)

[anderep]

how do i post them here in a scrollable list?? i've seen you do it...
sent email to @jasoncox.com

[anderep]

do you see how config list the CT address "cts": [true, false, false, false] would be CTO; "cts": [false, false, false, true] would be CT3...
so we just need to pull the data and put it in vitals.
:D
thank you for being so responsive... that is a very admirable trait in a human.

[jasonacox]

Yes, I see that and that is how the vitals logic determines the CT number. But, I think I found the problem. The logic expects that the meter entries in config always combine the same Neurio device measurements in the same payload. In other words, your one for "site" has a cts value of [true, true, false, false] which indicates that Neurio serial number device has two measurements (CT0 and CT1). However, in your setup, for some reason, you have two separate meters listed for "solar" but with the same serial number. The logic is only selecting one of them (CT3). I will need to change the code to add logic to merge the cts values if it sees colliding serial numbers.

[anderep]

don't merge CT0 and CT3 for "solar". keep them separate please, one is a Tesla inverter and the other is a enphase system. this is my only way of seeing the data in one spot...
for "site", L1 and L2 are merged, which is fine.

[jasonacox]

We can make them separate Neurio blocks in vitals by creating a fake serial number, but it seems like it was merged before and working:

"NEURIO--VAH4635AB1496": {
        "NEURIO_CT0_InstRealPower": 2373.679931640625,
        "NEURIO_CT0_Location": "solar",
        "NEURIO_CT3_InstRealPower": 11851.8203125,
        "NEURIO_CT3_Location": "solar",
        "componentParentDin": "STSTSM--1232100-00-H--GF22227000014F",
        "firmwareVersion": "1.7.2-Tesla",
        "lastCommunicationTime": 1682369955,
        "manufacturer": "NEURIO",
        "meterAttributes": {
            "meterLocation": [
                4,
                4
            ]
        },
        "serialNumber": "VAH4635AB1496"
    },

[anderep]

does merged mean added to gather? perhaps not.. just want the data separate...

[anderep]

like this, in vitals, i think will work:

{
"NEURIO--VAH4635AB1496": {
"NEURIO_CT0_InstCurrent": xxx,
"NEURIO_CT0_InstReactivePower": xxx,
"NEURIO_CT0_InstRealPower": xxx,
"NEURIO_CT0_InstVoltage": xxx,
"NEURIO_CT0_Location": "solar",
"NEURIO_CT3_InstCurrent": 39.6800003051758,
"NEURIO_CT3_InstReactivePower": 624.630004882813,
"NEURIO_CT3_InstRealPower": 9871.7001953125,
"NEURIO_CT3_InstVoltage": 125.459999084473,
"NEURIO_CT3_Location": "solar",
"componentParentDin": "1232100-00-H--GF22227000014F",
"firmwareVersion": null,
"lastCommunicationTime": "2025-02-02T09:46:36-06:00",
"manufacturer": "NEURIO",
"meterAttributes": {
"meterLocation": []
},
"serialNumber": "VAH4635AB1496"
},

[anderep]

this is/was what the dashboard was looking for before. the enphase is plotting as well as the non backed up loads, just missing tesla solar (neurio0, neurio_1

solar was neurio0
enphase:
(InfluxDB)
SELECT last("neurio_2") FROM "neurio"."neurio0" WHERE $timeFilter

tesla:
(InfluxDB)
SELECT last("neurio_1") FROM "neurio"."neurio0" WHERE $timeFilter

non backed up loads:
neurio1
(InfluxDB)
SELECT integral("neurio_3")/1000/3600 + integral("neurio_4")/1000/3600 FROM "neurio"."neurio1" WHERE $timeFilter

[jasonacox]

I created an issue (jasonacox/pypowerwall#136) for the fix in pypowerwall for this and I have a beta version for you to try: jasonacox/pypowerwall:0.12.4t68-beta

Edit your powerwall.yml file and locate and change this:

    pypowerwall:
        image: jasonacox/pypowerwall:0.12.0t66

to this

    pypowerwall:
        image: jasonacox/pypowerwall:0.12.4t68-beta

Save and run these to pull the new beta image:

# Load new image and restart
./compose-dash.sh up -d

# Check logs to ensure a good start
docker logs pypowerwall -f

Check the vitals to see if NEURIO is showing up like it did before (e.g. http://localhost:8675/vitals)

[anderep]

Tesla data is now populated!
any idea how to fix the display data for loads graph for "last"?

[jasonacox]

I think it has to do with the sample rate for your query in your dashboard. They are probably out of sync (one is more frequent than the other).

[anderep]

vitals looks correct: :)

    "NEURIO--VAH4635AB1496": {
        "NEURIO_CT0_InstCurrent": 1.4800000190734863,
        "NEURIO_CT0_InstReactivePower": -11.279999732971191,
        "NEURIO_CT0_InstRealPower": 350.9200134277344,
        "NEURIO_CT0_InstVoltage": 126.83999633789062,
        "NEURIO_CT0_Location": "solar",
        "NEURIO_CT3_InstCurrent": 49.119998931884766,
        "NEURIO_CT3_InstReactivePower": 617.5499877929688,
        "NEURIO_CT3_InstRealPower": 12358.48046875,
        "NEURIO_CT3_InstVoltage": 126.83999633789062,
        "NEURIO_CT3_Location": "solar",
        "componentParentDin": "1232100-00-H--GF22227000014F",
        "firmwareVersion": null,
        "lastCommunicationTime": "2025-02-02T13:34:01-06:00",
        "manufacturer": "NEURIO",
        "meterAttributes": {
            "meterLocation": []
        },
        "serialNumber": "VAH4635AB1496"
    },
    "NEURIO--VAH5037AB3569": {
        "NEURIO_CT0_InstCurrent": 0.029999999329447746,
        "NEURIO_CT0_InstReactivePower": -0.23000000417232513,
        "NEURIO_CT0_InstRealPower": 2.7799999713897705,
        "NEURIO_CT0_InstVoltage": 127.08000183105469,
        "NEURIO_CT0_Location": "site",
        "NEURIO_CT1_InstCurrent": 0.019999999552965164,
        "NEURIO_CT1_InstReactivePower": 0,
        "NEURIO_CT1_InstRealPower": 2.25,
        "NEURIO_CT1_InstVoltage": 126.97000122070312,
        "NEURIO_CT1_Location": "site",
        "componentParentDin": "1232100-00-H--GF22227000014F",
        "firmwareVersion": null,
        "lastCommunicationTime": "2025-02-02T13:34:01-06:00",
        "manufacturer": "NEURIO",
        "meterAttributes": {
            "meterLocation": []
        },
        "serialNumber": "VAH5037AB3569"
    },

[jasonacox]

Excellent! I'll run some test and release it as an upgrade.

[jasonacox]

v4.6.1 has been released. You can run upgrade.sh to get it, but technically you are already running the upgraded code by using the beta container.