Feature Request: Frequency Measurement

[dcj]

In https://community.home-assistant.io/t/integration-with-span/370645/543 @turtle2472 asks:

Does Panel provide the current frequency for each leg?
I regularly go off grid in the morning hours and noticed my LEDs flickering.
Now I’m certain it is frequency shifting of the Tesla Gateway but would like to know so I can log it somewhere and be able to see what the frequency is.
I found a way to view it from the Tesla API, but would love it to come from Span if it is a sensor already we just don’t see right now.

[turtle2472]

To support this, the Tesla Energy Gateway provides details in a diagnostic view I'm accessing via paid service of an app that uses the Fleet APIs.

    "esCan": {
      "bus": {
        "ISLANDER": {
          "ISLAND_AcMeasurements": {
            "ISLAND_FreqL1_Load": 61.879999999999995,
            "ISLAND_FreqL1_Main": 60.03,
            "ISLAND_FreqL2_Load": 61.879999999999995,
            "ISLAND_FreqL2_Main": 60.03,
            "ISLAND_FreqL3_Load": 0,
            "ISLAND_FreqL3_Main": 0,
            "ISLAND_GridState": "ISLAND_GridState_Grid_Compliant",
            "ISLAND_VL1N_Load": 121,
            "ISLAND_VL1N_Main": 126,
            "ISLAND_VL2N_Load": 120,
            "ISLAND_VL2N_Main": 125.5,
            "ISLAND_VL3N_Load": 0,
            "ISLAND_VL3N_Main": 0,
            "isComplete": true,
            "isMIA": false,
            "lastRxTime": "2026-04-04T00:06:00-04:00"

Second area is:

            "PINV_Status": {
              "PINV_Fout": 61.913,
              "PINV_GridState": "Grid_Compliant",
              "PINV_Pout": 1.04,
              "PINV_State": "PINV_GridForming",
              "PINV_Vout": 239.4,
              "isMIA": false
            },

Monitoring this through Span Panel would mean verification of source stability would be available regardless of specific source. (Grid, inverter, generator, etc...)

[dcj]

@turtle2472 GTK that the Telsa Fleet API provides this data.
IMO the Tesla gateway/system-controller should provide all this information via a local API, ideally adopting eBus, but I'm not holding my breath...

Speaking from direct personal experiece, and not for SPAN, my recent experience with the Tesla Fleet integration for Home Assistant is less than ideal, I seem to get prompted to re-authenticate every few days, given all the hoops I had to jump thorough to set this up the first time, including hosting a key on a public HTTP server Tesla can acccess, this is a pretty poor user experience.

Given that, again speaking personally, I would not propose that SPAN implement any sort of panel-based integration to Tesla Fleet...

[turtle2472]

This is why I stopped trying to make it work in HA with Tesla directly. I have enough to deal with that adding that to my fight wasn't it. I use Netzero and pay their subscription to have automation again. That app allows Powerwall pairing and I can even go off-grid again via the developer API Netzero provides (https://docs.netzero.energy/docs/tesla/API). So I have HA taking me off-grid, through Netzero's APIs...

I'm not a fan of many things Tesla has done lately, this is just one more way to get a workaround in.

To bring this all back to my request, Span Panel is my one solid platform that all my home loads run off of. Using it as my basis of data related to my home's power (flow, consumption, etc...) makes more sense than the TEG. More so with my planning to build another off-grid system that will power my Panel instead of TEG.

It would also aid in troubleshooting why lights are acting weird, or the microwave "sounds funny". So many things we assume are good and frequency of our power isn't always clean.

[dcj]

@turtle2472
Is there any evidence that the incessant "re-authenticate with Tesla Fleet" messages from the Fleet-HASS integration are the fault of the integration itself, and not Tesla?
I had just assumed that this was a problem with Tesla Fleet, not the integration, but if the latter, that might motivate me to consider a SPAN panel integration for Fleet, but I'd like to make it crystal clear that were I to consider such a thing, that is is no way a commitment by me or SPAN that it would ever happen.

[turtle2472]

I don't know for the Fleet-HASS part because I never moved to it. When the old local API stopped working with most of the controls I just walked away from it. I've never done the Fleet API personally, only through Netzero.

That said, I never/rarely re-authenticate through Netzero. New installs or random occasions and that is it. I open Netzero's app and have my data. I send a number of API calls through the Netzero API daily and don't have issues. If I were to compare that to what you're describing, it is the HASS integration instead of Tesla's API. It is also VERY possible that Netzero hides the authentication issues from us since our token is still valid.

[dcj]

@turtle2472

It is also VERY possible that Netzero hides the authentication issues from us since our token is still valid

I speculate with no knowledge or evidence whatsoever that this is exactly what is happening.
Netzero has made a business of "proxying" the Tesla Fleet API, so Netzero is motivated to fix the the reauth problem, and presumably they have figured out how to do so, and since you are authed to Netzero who has apparently figured out how to run a service without making their clients/subscribers reauth every few days (snarking at you, Tesla!), this is all invisible to you.

[dcj]

AFAICT the HASS Tesla Fleet Integration was stable for a relatively long time, "something changed" and it started flaking, but apparently this has been fixed and will roll out soon-ish...

• Tesla Fleet Integration Keep requiring re-authentication home-assistant/core#166167
• Fix Tesla Fleet token refresh handling for expired tokens home-assistant/core#165354