REST sensor and comma delimited data

Hi all

I have TIGO optimisers on my solar panels and would like to pull panel data in to Home Assistant. They provide an API, however it returns the data in a tab delimited format, which is less than ideal. Please see an example below:

2021/06/01 16:43:00.000,206,209,208,209,177,209,212,230,232
2021/06/01 16:44:00.000,205,208,207,208,177,208,211,230,232
2021/06/01 16:45:00.000,204,207,206,207,175,207,209,227,229
2021/06/01 16:46:00.000,204,206,205,206,175,206,209,221,228
2021/06/01 16:47:00.000,202,204,204,204,173,205,207,220,228
2021/06/01 16:48:00.000,198,202,202,202,171,203,206,224,227
2021/06/01 16:49:00.000,199,202,201,201,170,202,204,223,225
2021/06/01 16:50:00.000,198,201,201,201,169,201,204,222,224
2021/06/01 16:51:00.000,197,200,199,200,168,200,203,220,223
2021/06/01 16:52:00.000,195,198,198,199,167,199,201,215,222

Ideally, what i’d like to do is capture only the last line (most recent) in my REST sensor, then I could set up a template sensors to pull back each individual number as a sensor (Everything after the time is a wattage output from a solar panel. I have 9 in total).


Could you use a command-line sensor instead?

  - platform: command_line
    command: "curl YOUR_REST_URL | tail -n 1"
    name: "TIGO data"
    scan_interval: 120

That’s a really good idea. I hadn’t considered using the command line sensor

Marking as solution. This seems to work well enough for me.

1 Like

Could you please share more info, how did you implemented this sollution?

@mehstg please could you post the curl command? thank you

Sorry I totally forgot to reply to this, we had a bank holiday weekend in the UK and I switched off completely! Are you the same person who contacted me about this through Twitter too?

So, what I did was kind of janky, but it works OK for me. A proper HA addon would be better.

I wrote a simple script to curl the data from the API. You will have to add your System ID to this, and an authorisation bearer token (The Tigo API docs will help you with this).


curl --location --request GET "<redacted>&start=$(date +"%Y-%m-%dT00:00:01")&end=$(date +"%Y-%m-%dT%H:%M:%S")&level=min&header=key" --header "Authorization: Bearer <REDACTED>" --silent | tail -1 | cut -d',' -f2-

Then, set up a command line sensor to run this script periodically. In your configuration.yaml add something like this:

  # Pull in granular panel wattage from Tigo API
  - platform: command_line
    command: "bash /config/tigo/"
    name: "Solar Panels"
    scan_interval: 120

This will get the data in to HA as sensor.solar_panels. At this point you should be able to check this in Developer Tools in HA. Note: If you see "message":"Premium required.","code":0,"status":402} it’s because you are using the free account, API access requires a premium Tigo account.

Then it’s just a case of stripping out the necessary data in to separate sensors. I have 9 panels, so have done it like this:

  # Template solar panels out nicely
  - platform: template
        friendly_name: "Solar Panel 1 - South"
        unit_of_measurement: "W"
        value_template: "{{ states.sensor.solar_panels.state.split(',')[0] }}"
        friendly_name: "Solar Panel 2 - South"
        unit_of_measurement: "W"
        value_template: "{{ states.sensor.solar_panels.state.split(',')[1] }}"
        friendly_name: "Solar Panel 3 - South"
        unit_of_measurement: "W"
        value_template: "{{ states.sensor.solar_panels.state.split(',')[2] }}"
        friendly_name: "Solar Panel 4 - South"
        unit_of_measurement: "W"
        value_template: "{{ states.sensor.solar_panels.state.split(',')[3] }}"
        friendly_name: "Solar Panel 5 - South"
        unit_of_measurement: "W"
        value_template: "{{ states.sensor.solar_panels.state.split(',')[4] }}"
        friendly_name: "Solar Panel 6 - South"
        unit_of_measurement: "W"
        value_template: "{{ states.sensor.solar_panels.state.split(',')[5] }}"
        friendly_name: "Solar Panel 7 - South"
        unit_of_measurement: "W"
        value_template: "{{ states.sensor.solar_panels.state.split(',')[6] }}"
        friendly_name: "Solar Panel 8 - West"
        unit_of_measurement: "W"
        value_template: "{{ states.sensor.solar_panels.state.split(',')[7] }}"
        friendly_name: "Solar Panel 9 - West"
        unit_of_measurement: "W"
        value_template: "{{ states.sensor.solar_panels.state.split(',')[8] }}"

Hope that helps!

Thank you for your fast reply. I didn’t write to you on twitter.

I get my system id and auth token. When I run curl command the “premium required” appear.

So, it isn’t possible to get power from panels without paying for a premium account?

Exactly that unfortunately. API access is a “premium” feature.

1 Like


I tried the api, and it returns a token that lasts for six months. Did you automate the token refresh in some way?


Iirc, I am manually updating it. It wouldn’t be hard to automate though, Curl the authorization bearer out to a file, then edit the script to read the token in from a file rather than have it hard coded.

did they change this?
in the table it shows W is available for “free” in 15min steps (ridiculous enough, that you have to pull your own data from the cloud):

The comparison chart (below), lists the features that are available within the Free and Premium (subscription) packages

Features Free Premium
Module-level data Energy (Wh)
Power (W)
Reclaimed Power (W)
Energy (Wh)
Power (W)
Reclaimed Power (W)
Voltage (V)
Current (A)
Module-level granularity 15-minutes 1-minute