Repository navigation
Tesla Powerwall 3 setup - Database Manager - Shows unhealthy at all times #3203
|
I love this add-on for HA and currently have set it up with Tesla Powerwall 3 and 1 expansion pack giving 28.3kWh max storage. All of this ties in with my Home Assistant nicely and the generated plans are about 80% accurate as I get Charge Freeze when battery is full and tariff is a little high. Any suggestions on tailoring the settings welcomed here. My biggest question is that the Database Manager component show red at all times despite it being turned on or off. Thanks in advance and will raise an issue if nothing heard. |
Replies: 2 comments
|
You shouldn't need the database manager for your setup, and nothing needs to be configured for it in apps.yaml. By default it will be disabled: remove db_enable line from your apps.yaml |
|
Well I did try that a couple of times but still showed Unhealthy.
But all is now perfect as I must have missed the enable in the config piece.
Great bit of software.
…________________________________
From: Geoffrey Coan ***@***.***>
Sent: 09 January 2026 9:26 AM
To: springfall2008/batpred ***@***.***>
Cc: Alan Sullivan ***@***.***>; Author ***@***.***>
Subject: Re: [springfall2008/batpred] Tesla Powerwall 3 setup - Database Manager - Shows unhealthy at all times (Discussion #3203)
You shouldn't need the database manager for your setup, and nothing needs to be configured for it in apps.yaml.
By default it will be disabled:
image.png (view on web)<https://github.com/user-attachments/assets/de650fd9-37e3-449b-8cb5-9a8f4a27e697>
remove db_enable line from your apps.yaml
—
Reply to this email directly, view it on GitHub<#3203 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AJZI6W2EMX6Y7BT4LYXSXDL4F5X37AVCNFSM6AAAAACRE3FR6SVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKNBVGI4TCNQ>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
You shouldn't need the database manager for your setup, and nothing needs to be configured for it in apps.yaml.
By default it will be disabled:
remove db_enable line from your apps.yaml