Installing on an Unraid Server

[ThePnuts]

I am new to all of this and basically learning as I take each step.

I currently have an Unraid server with several docker containers including Influxdb and Grafana. As I understand it, if I install Docker Compose, it would be lost after a restart due to the way Unraid functions. It looks like there is a beta plugin I could use though.

Is it likely something I could do, to have this functional without Docker Compose, using the Unraid docker manager?

Would a Ubuntu VM doing the non influx\grafana stuff probably be a better option for me?

---

I think I may be over thinking all this...

Being new to github as well (first time here really), I think I understand this all a little better as I am digging in while making this post.

Powerwall-Dashboard is basically a all in one approach making it easy to set everything up? Its creating multiple dockers for each piece and tying it all together very nicely for someone to get rolling instantly.

pypowerwall is what is getting the data and putting it into influx.

---

Maybe my best approach is learning how to get pypowerwall functioning in docker (using Unraids manager) and then I can come here and pull out the dashboard information that all looks amazing and tweak it as I want.

I think this last option seems like the best path forward. I guess I'm not really asking a question and kind of just typed my train of thoughts as I read through this. If anyone has any good info that would be helpful for me in my learning experience, feel free to point me. Or even just confirmation of my sillyness and maybe a different approach I didn't think of.

Thanks!

[jasonacox]

Hi @ThePnuts ! Welcome!

Am I over thinking all of this?

Absolutely not. 😉 You have thought through several good options. Since you are already running InfluxDB and grafana, you would likely have problems setting up the docker-ompose version (since they probably use the same ports).

how to get pypowerwall functioning in docker

Yes, and telegraf, some some other adjustments. The reason for this project is that the setup is a bit involved, but you can do it. I'll do a quick top-of-mind list of things you should think about (and yes, I'm probably missing some things 😁 ):

using Unraids manager

Here are the parameters you will need to set:

pypowerwall

See https://github.com/jasonacox/pypowerwall/tree/main/proxy and you will find the docker run comand that you could translate into Unraids manager (of course replacing with your password, etc):

docker run \
-d \
-p 8675:8675 \
-e PW_PORT='8675' \
-e PW_PASSWORD='password' \
-e PW_EMAIL='email@example.com' \
-e PW_HOST='IP_of_Powerwall_Gateway' \
-e PW_TIMEZONE='America/Los_Angeles' \
-e TZ='America/Los_Angeles' \
-e PW_CACHE_EXPIRE='5' \
-e PW_DEBUG='no' \
-e PW_HTTPS='no' \
--name pypowerwall \
--restart unless-stopped \
jasonacox/pypowerwall

After you have it running, you can test it by going to to this address http://localhost:8675/stats and http://localhost:8675/example.html (replace localhost with the address of your Unraid server).

Telegraf

This is a little more complicated because it will require telegraf to access a local configuration file (telegraf.conf). First, create the file by pulling it from here: https://github.com/jasonacox/Powerwall-Dashboard/blob/main/telegraf.conf and you will need to edit some of the lines - the key lines are below. Replace http://influxdb and http://pypowerwall with the IP address of your Unraid server but leave the rest of the URL alone.

[[outputs.influxdb]]
	urls = ["http://influxdb:8086"]
	database = "powerwall"
	skip_database_creation = false
	retention_policy = "raw"

[[inputs.http]]
	urls = [
		"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"
	]
	method = "GET"
	insecure_skip_verify = true
	timeout = "4s"
	data_format = "json"

[[processors.date]]
	tag_key = "month"
	date_format = "Jan"
	timezone = "America/Los_Angeles"

[[processors.date]]
	tag_key = "year"
	date_format = "2006"
	timezone = "America/Los_Angeles"

# Alert Data
[[inputs.http]]
	urls = [
		"http://pypowerwall:8675/alerts/pw"
	]
	name_override = "alerts"
	method = "GET"
	insecure_skip_verify = true
	timeout = "4s"
	data_format = "json"

After you save that, set up telegraf in Unraid manager with details like below. Notice it is mapping the telegraf.conf flie you created into the container (change $PWD to the path where telegraf.conf lives):

docker run \
-d \
 -v $PWD/telegraf.conf:/etc/telegraf/telegraf.conf:ro \
--name pypowerwall \
--restart unless-stopped \
telegraf

InfluxdB

There are still setup things you will need to do for InfluxDB to support the dashboard. If you have the ability to execute a shell inside your InfluxDB, you will want to run the influx tool and paste the contents from https://github.com/jasonacox/Powerwall-Dashboard/blob/main/influxdb/influxdb.sql

docker exec -it influxdb influx

Grafana

We use several plugins for Grafana. You may have these already setup, but if not, you can use the list here: https://github.com/jasonacox/Powerwall-Dashboard/blob/main/grafana.env.sample#L3

Now inside of Grafana, you will still follow some of the setup here: https://github.com/jasonacox/Powerwall-Dashboard#grafana-setup

Key difference is that you will edit the URL to represent the address of your Unraid server instead of http::/influxdb.

Weather411 (optional)

This is optional, but if you want local weather data on your graph, you will set up the weather411.conf file (see https://github.com/jasonacox/Powerwall-Dashboard/tree/main/weather#quick-start) and then run that container:

docker run \
-d \
-p 8676:8676 \
-e WEATHERCONF='/var/lib/weather/weather411.conf' \
-v ${PWD}:/var/lib/weather \
--name weather411 \
--restart unless-stopped \
jasonacox/weather411

If you decided to go down this path, it would be great if you could note all of your steps and share with others who might have the same Unraid setup.

[ThePnuts]

Perfect, thank you, something else to learn as I go :)

So far I have weather411 functioning (influx part disabled for now) and I can query it or visit the simple web page. Wasn't to bad converting your docker run commands into the xml format for unraid. Only tricky thing was getting the variable setup in the way I wanted (basically adopting it to the way all my other containers defaulted to for unraid)

I figured Weather411 would be easier to start with since its up on dockerhub and is pretty self contained.

For pyPowerwall, I need to go figure out: This module requires that you (or your installer) have set up Customer Login credentials on your Powerwall Gateway

[jasonacox]

Nice! You will find pypowerwall also on dockerhub: https://hub.docker.com/r/jasonacox/pypowerwall

Tesla instructions on getting access to your Powerwall: https://www.tesla.com/support/energy/powerwall/own/connecting-network

If your installer didn't help you set up a customer login, you can log in as the Installer and set one up. It requires you to toggle the power switch on the Powerwall when prompted.

[ThePnuts]

Well, that took longer then expected... Light was out in garage, turns out it was actually the fixture. Bought 2 fixtures since I needed more light anyways and installed them only to find out the outlet was wired backwards... Fixed that and I have light!

My Tesla WiFi didn't match my sticker, and no surprise the password on the sticker didn't work either. Sad to admit but it took me a few to figure it out. I have a Powerwall+ and a Backup Gateway 2. Backup Gateway 2 had a different sticker\wifi\password and I was in. Also checked out the installer view.

So many variables for pyPowerwall, but I have that done and working now as well. You really did make this easy for me.

I assumed PW_TIMEZONE is the time zone of where the PW is installed?
and TZ is the time zone you want the data in?
I can update the xml, but I used that for the description of each since I wasn't 100% sure

For anyone looking at this later, I am attaching the 2 xml files for these containers in unraid. So long as the variables do not change, these should continue to work.
weather411.xml.txt
pyPowerwall.xml.txt

[jasonacox]

Light was out in garage, turns out it was actually the fixture.

Haha! Doesn't every project always turn into 10 more? 😂

So many variables for pyPowerwall

I should have told you this before, but you really only need PW_PASSWORD and PW_HOST to get it to work. The rest are optional and will default. But having them in your xml file will help if you want to customize later. And yes, PW_TIMEZONE is to localize time to where you are located (and should be one of these).

Congrats on getting them running! Are you able to get data and the flow animation from pypowerwall?

• http://localhost:8675/example.html
• http://localhost:8675/vitals

Thanks for sharing the XML files!!! I'm going to change the title of the discussion so that anyone else with Unraid system can find your helpful work.

[ThePnuts]

Ooh, good thinking on the rename.

Yes to both, flow animation working and I am getting data. I played around with a few of the links in the tips and tricks here: https://github.com/jasonacox/Powerwall-Dashboard

I was just looking at your comments above on influx 2.0. I only ever messed with MySQL and its been a long time since I have.

It looks like you are capturing the PW data with a 3 day retention and using the continuous query's to take that data and downsample it with no retention on the downsampled data?

Im going to go read up on v2 and tasks, then see about converting the continuous query's before I start capturing with Telegraph. On the Telegraph side, I think for now, Ill use a 2nd container, I wasn't able to find info on using 2 conf files that I could to semi quick, so ill just do that part later or keep it separate.

[ThePnuts]

Debating spinning up a influx 1.8 db

I might be a bit in over my head on the constant query converted to task front.

Also for weather411, I have been using api tokens to grant access for telegraf, guessing I cant do that and need to look into how to add a user, or not if I do setup a 1.8 db just for this.

Hmmmmmm

[jasonacox]

Thanks for helping test!!!

I know this is cliche, but it worked in my InfluxDB2... 😂

looks like it is not working.

Keep in mind it only updates every 10 minutes. Also, if you still have telegraf running, Influx will merge the data since they have the same timestamp. Or when you say "not work" did you get some errors in the logs?

The code that writes to InfluxDB is here:

Powerwall-Dashboard/weather/server.py

Lines 269 to 292 in ef438a1

	if ITOKEN == "":
	# Influx 1.8
	client = InfluxDBClient(
	url="http://%s:%s" % (IHOST,IPORT),
	username=IUSER,
	password=IPASS,
	database=IDB)
	else :
	# Influx 2.x
	client = InfluxDBClient(
	url=IURL,
	token=ITOKEN,
	org=IORG)
	output = [{}]
	output[0]["measurement"] = IFIELD
	output[0]["time"] = datetime.utcfromtimestamp(weather["dt"])
	output[0]["fields"] = {}
	for i in weather:
	output[0]["fields"][i] = weather[i]
	# print(output)
	write_api = client.write_api(write_options=SYNCHRONOUS)
	write_api.write(IDB,IORG,output)
	serverstats['influxdb'] += 1
	client.close()

Line 440 is just startup information output (you would see it in the container logs), not used for InfluxDB.

I'm going to keep testing with my InfluxDB v2 installation so see if I can reproduce a problem.

Thanks again!

[ThePnuts]

Oh man, every 10 minutes!
I didn't realize the delay was that long, I might have given it 5 minutes if Im lucky.... I'm going to swap back and let it roll overnight.

Oops....

[ThePnuts]

Ok, I am at a loss. Still not working for me, with debug on, here is the log

DEBUG:Weather data loaded
DEBUG:Writing to InfluxDB
DEBUG:Error writing to InfluxDB

Here is my conf file with private data obfuscated

[Weather411]
DEBUG = yes

[API]
# Port to listen on for requests (default 8676)
ENABLE = yes
PORT = 8676

[OpenWeatherMap]
# Register and get APIKEY from OpenWeatherMap.org
APIKEY = supersecretweatherapikeyhereandworkingfine
# Enter your location in latitude and longitude 
LAT = 12.3456789
LON = -123.456789
WAIT = 10
TIMEOUT = 10
# standard, metric or imperial 
UNITS = imperial

[InfluxDB]
# Record data in InfluxDB server 
ENABLE = yes
HOST = 255.255.255.0 also tried this as default influxdb
PORT = 8086
DB = powerwall
FIELD = weather
# Leave blank if not used
USERNAME =
PASSWORD =
# Influx 2.x - Leave blank if not used
TOKEN = "topsecretapikey, I also tried without quotes"
ORG = "moresecretorg, also tried without quotes"
URL = "255.255.255.0:8086" also tried with http:// and without quotes

Just incase it was the API key, I also tried a known working one without success. Going to just try force updating to current docker container.
Edit: reloading the docker from scratch did not work either.

[jasonacox]

Thanks @ThePnuts - I appreciate you trying. This is helpful:

DEBUG:Error writing to InfluxDB

Do you see anything else in the logs, something like this?:

* Starting threads
 + fetchWeather thread
 + apiServer thread - Listening on http://localhost:8676
Weather411 Server [0.2.0beta]
* Configuration Loaded [/var/lib/weather/weather411.conf]
 + Weather411 - Debug: False, Activate API: True, API Port: 8676

Some notes:

• You should be able to leave URL blank (otherwise needs to be full http://localhost:8086 without quotes). It will auto-generate from HOST and PORT if URL is empty. It sounds like you already tried this.
• Remove all the quotes symbols (") - config just wants plain text. You said you tried both, but just so you know.

I created a version that removes the try/except catch in the code to force it to produce an error exception stack trace. Can you try this version to see if we can get more details on why the write is failing?

jasonacox/weather411:0.2.0beta

Also just to make sure I mirror you setup for my testing, when I look at InfluxDB 2 data explorer, I see the data come in to the powerwall bucket like this:

[ThePnuts]

Ok, info before I try the beta.

For the powerwall bucket, my data does look different because I am using Telegraf with http, so I have the additional normal telegraf fields:

I wonder if that is why there is a problem...

Surprise, that was the problem... I changed the conf file to use weathertest for the _measurement instead and everything is working as expected...

So my workaround before influxdb 2+ was supported caused all of my problems... Doh. I should have tested that too...

Now just to test the Beta to see if it gives more info:

Weather411 Server [0.2.0beta]
* Configuration Loaded [/var/lib/weather/weather411.conf]
 + Weather411 - Debug: True, Activate API: True, API Port: 8676
 + OpenWeatherMap - Key: myAPI, Wait: 10, Units: imperial
 + OpenWeatherMap - Lat: 123456789, Lon: -123456789, Timeout: 10
 + InfluxDB - Enable: True, Host: influxdb, Port: 8086, DB: powerwall, Field: weather
 + InfluxDB - URL: http://serverIP:8086, Org: myORG, Token: myTOKEN
* Starting threads
 + fetchWeather thread
 + apiServer thread - Listening on http://localhost:8676
DEBUG:Starting new HTTPS connection (1): api.openweathermap.org:443
DEBUG:https://api.openweathermap.org:443 "GET /data/2.5/weather?lat=123456789&lon=-123456789&units=imperial&appid=myAPI HTTP/1.1" 200 497
DEBUG:Weather data loaded
DEBUG:Writing to InfluxDB
Exception in thread Thread-1:
Traceback (most recent call last):
  File "/usr/local/lib/python3.8/threading.py", line 932, in _bootstrap_inner
    self.run()
  File "/usr/local/lib/python3.8/threading.py", line 870, in run
    self._target(*self._args, **self._kwargs)
  File "server.py", line 290, in fetchWeather
    write_api.write(IDB,IORG,output)
  File "/usr/local/lib/python3.8/site-packages/influxdb_client/client/write_api.py", line 378, in write
    results = list(map(write_payload, payloads.items()))
  File "/usr/local/lib/python3.8/site-packages/influxdb_client/client/write_api.py", line 376, in write_payload
    return self._post_write(_async_req, bucket, org, final_string, payload[0])
  File "/usr/local/lib/python3.8/site-packages/influxdb_client/client/write_api.py", line 509, in _post_write
    return self._write_service.post_write(org=org, bucket=bucket, body=body, precision=precision,
  File "/usr/local/lib/python3.8/site-packages/influxdb_client/service/write_service.py", line 60, in post_write
    (data) = self.post_write_with_http_info(org, bucket, body, **kwargs)  # noqa: E501
  File "/usr/local/lib/python3.8/site-packages/influxdb_client/service/write_service.py", line 90, in post_write_with_http_info
    return self.api_client.call_api(
  File "/usr/local/lib/python3.8/site-packages/influxdb_client/_sync/api_client.py", line 343, in call_api
    return self.__call_api(resource_path, method,
  File "/usr/local/lib/python3.8/site-packages/influxdb_client/_sync/api_client.py", line 173, in __call_api
    response_data = self.request(
  File "/usr/local/lib/python3.8/site-packages/influxdb_client/_sync/api_client.py", line 388, in request
    return self.rest_client.POST(url,
  File "/usr/local/lib/python3.8/site-packages/influxdb_client/_sync/rest.py", line 311, in POST
    return self.request("POST", url,
  File "/usr/local/lib/python3.8/site-packages/influxdb_client/_sync/rest.py", line 261, in request
    raise ApiException(http_resp=r)
influxdb_client.rest.ApiException: (422)
Reason: Unprocessable Entity
HTTP response headers: HTTPHeaderDict({'Content-Type': 'application/json; charset=utf-8', 'X-Influxdb-Build': 'OSS', 'X-Influxdb-Version': 'v2.6.1', 'X-Platform-Error-Code': 'unprocessable entity', 'Date': 'Wed, 01 Mar 2023 16:39:17 GMT', 'Content-Length': '221'})
HTTP response body: {"code":"unprocessable entity","message":"failure writing points to database: partial write: field type conflict: input field \"clouds\" on measurement \"weather\" is type integer, already exists as type float dropped=1"}

So I guess that answers that, a field data type issue goofed it all.
Now I just need to go learn how to drop some tables so its working in the official sense.

Thank you so much for your help and time with this @jasonacox !

minor edit, I wasnt able to revert back, from this thread it looks like you pulled it due to another issue, but I was able to use 0.2.1 (also from that thread and I am functional again

[ThePnuts]

Follow up here with docker setup steps in Unraid (or use XML files here: #191 (reply in thread))

• Not sure if needed

  • Docker Settings (Must turn off Docker)
    • Template Authoring Mode: Yes
  • Community Applications
    • Enable developer mode: Yes

• Installing pyPowerwall

  • Install docker images
    • Search for pyPowerwall in community apps
    • Click link to search on DockerHub
    • Click Install
    • Clink No for determine configuration
  • Add Docker Container
    • Docker Tab, click Add Container
    • Settings
      • Template: pypowerwall
      • Name: pypowerwall
      • Repository: jasonacox/pypowerwall
      • WebUI: http://[ip]:[port:8676]/
      • Network Type: Bridge
      • Console shell command: Shell
      • Add the following:
        • Port
          • Name: Host Port 1
          • Container Port: 8675
          • Host Port: 8675
          • Default Value: 8675
          • Connection Type: TCP
          • Display: Always
          • Required: Yes
        • Variable1
          • Name: PW_PORT
          • Key: PW_PORT
          • Value: 8675
          • Default Value: 8675
          • Description: Variable for Powerwall Port
          • Display: Always
          • Required: Yes
        • Variable2
          • Name: PW_PASSWORD
          • Key: PW_PASSWORD
          • Value: your powerwall password
          • Default Value: your powerwall password
          • Description: Variable for your powerwall password
          • Display: Always
          • Required: Yes
        • Variable3
          • Name: PW_EMAIL
          • Key: PW_EMAIL
          • Value: email@example.com
          • Default Value: email@example.com
          • Description: Variable for your powerwall login (email)
          • Display: Always
          • Required: Yes
        • Variable4
          • Name: PW_HOST
          • Key: PW_HOST
          • Value: IP of your Powerwall Gateway
          • Default Value: IP of your Powerwall Gateway
          • Description: Variable for IP of your Powerwall Gateway
          • Display: Always
          • Required: Yes
        • Variable5
          • Name: PW_TIMEZONE
          • Key: PW_TIMEZONE
          • Value: America/Los_Angeles
          • Default Value: America/Los_Angeles
          • Description: Variable for your powerwall timezone
          • Display: Always
          • Required: Yes
        • Variable6
          • Name: TZ
          • Key: TZ
          • Value: America/Los_Angeles
          • Default Value: America/Los_Angeles
          • Description: Variable for local timezone
          • Display: Always
          • Required: Yes
        • Variable7
          • Name: PW_CACHE_EXPIRE
          • Key: PW_CACHE_EXPIRE
          • Value: 5
          • Default Value: 5
          • Description: Variable for Powerwall Cache Expiration
          • Display: Always
          • Required: Yes
        • Variable8
          • Name: PW_DEBUG
          • Key: PW_DEBUG
          • Value: no
          • Default Value: no
          • Description: Enable Debug
          • Display: Always
          • Required: Yes
        • Variable9
          • Name: PW_HTTPS
          • Key: PW_HTTPS
          • Value: no
          • Default Value: no
          • Description: Powerwall HTTPS Support enabled
          • Display: Always
          • Required: Yes

• Installing Weather411

  • Install docker images
    • Search for weather411 in community apps
    • Click link to search on DockerHub
    • Click Install
    • Clink No for determine configuration
  • Add configuration file
    • Create directory
      • mkdir /mnt/user/appdata/weather411
    • Set owner
      • Chown nobody:users /mnt/user/appdata/weather411
    • Create conf file
      • Nano /mnt/user/appdata/weather411/weather.conf
        • Copy details from: https://github.com/jasonacox/Powerwall-Dashboard/blob/main/weather/weather411.conf.sample
        • Change
          • Apikey
          • LAT
          • LON
          • Influxdb info
    • Set permissions
      • Chmod 755 /mnt/user/appdata/weather411/weather.conf
  • Add Docker Container
    • Docker Tab, click Add Container
    • Settings
      • Template: weather411
      • Name: weather411
      • Repository: jasonacox/weather411
      • WebUI: http://[ip]:[port:8676]/
      • Network Type: Bridge
      • Console shell command: Shell
      • Add the following:
        • Port
          • Name: Host Port 1
          • Container Port: 8676
          • Host Port: 8676
          • Default Value: 8676
          • Connection Type: TCP
          • Display: Always
          • Required: Yes
        • Path
          • Name: Host Path 1
          • Container Path: /var/lib/weather/weather411.conf
          • Host Path: /mnt/user/appdata/weather411/weather411.conf
          • Default Value: /mnt/user/appdata/weather411/weather411.conf
          • Access Mode: Read/Write
          • Description: Location of weather411.conf
          • Display: Always
          • Required: Yes
        • Variable
          • Name: WEATHERCONF
          • Key: WEATHERCONF
          • Value: /var/lib/weather/weather411.conf
          • Default Value: /var/lib/weather/weather411.conf
          • Description: Variable for weather411.conf location within Docker
          • Display: Always
          • Required: Yes

[mmunsch]

I wanted to say thank y'all to @ThePnuts and @jasonacox for the work y'all did here outlining these steps. They weren't the easiest to follow but they were clear enough that I now have my docker containers working on my Unraid machine and can stop running them on a separate computer/VMs.

For others that may find this here are the steps I took:

1. Followed ThePnuts steps for setting up pypowerwall and weather411 in Unraid. (NOTE that there is a typo in his instructions, the config file needs to be named weather411.conf in the /mnt/user/appdata/weather411/weather411.conf in order for it to work properly.) I also originally missed changing the influx db info for weather411.conf from host: influxdb to host: UNRAID IP but now I have weather411 working pulling into the dashboard.
2. Installed Influxdb-1.8 from community apps with the base template and followed jason's instructions. I think I may have screwed up here and used the wrong port so I had to update my grafana setup later but it worked

InfluxdB

There are still setup things you will need to do for InfluxDB to support the dashboard. If you have the ability to execute a shell inside your InfluxDB, you will want to run the influx tool and paste the contents from https://github.com/jasonacox/Powerwall-Dashboard/blob/main/influxdb/influxdb.sql

docker exec -it influxdb influx

3. Install telegraf docker from community apps. This was probably the most confusing as instructions weren't great and the community app default template tries to setup telegraf for monitoring your unraid machine.

I had to create the telegraf.conf file in /mnt/user/appdate/telegraf/telegraf.conf and used Jason's instructions and updated the IP directions for the IP of my unraid server.

Telegraf

This is a little more complicated because it will require telegraf to access a local configuration file (telegraf.conf). First, create the file by pulling it from here: https://github.com/jasonacox/Powerwall-Dashboard/blob/main/telegraf.conf and you will need to edit some of the lines - the key lines are below. Replace http://influxdb and http://pypowerwall with the IP address of your Unraid server but leave the rest of the URL alone.

[[outputs.influxdb]]
	urls = ["http://influxdb:8086"]
	database = "powerwall"
	skip_database_creation = false
	retention_policy = "raw"

[[inputs.http]]
	urls = [
		"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"
	]
	method = "GET"
	insecure_skip_verify = true
	timeout = "4s"
	data_format = "json"

[[processors.date]]
	tag_key = "month"
	date_format = "Jan"
	timezone = "America/Los_Angeles"

[[processors.date]]
	tag_key = "year"
	date_format = "2006"
	timezone = "America/Los_Angeles"

# Alert Data
[[inputs.http]]
	urls = [
		"http://pypowerwall:8675/alerts/pw"
	]
	name_override = "alerts"
	method = "GET"
	insecure_skip_verify = true
	timeout = "4s"
	data_format = "json"

4. After that I installed the Grafana container from community apps. Follow the Grafana setup instructions, import dashboard.json and voila... Powerwall Dashboard on Unraid!
5. Most of the dashboard just works but one of the plugins (Boom Table) is now deprecated and uses Angular and I couldn't get the iframe animation working originally.
6. The powerwall dashboard is using an older version of Grafana vs the unraid version is 11+. I had to add a variable GF_PANELS_DISABLE_SANITIZE_HTML=true as a docker parameter to get the iframe working.
   7. I had to add a variable GF_SECURITY_ANGULAR_SUPPORT_ENABLED=true as a docker parameter to get the Boom Table plugin working, althought this is a temp fix as it won't work past Grafana 12.