Database Primary Issue

[dandwhelan]

Describe the bug
Unable to get_history when enabling db_primary: true

Expected behaviour
I'm wanting to move away from Homeassistant storing all the data and I'd like Predbat DB Manager storing all the data. I've moved to GE Cloud Data but still using HA GivTCP to control the invertor. Am I missing something or not understanding the feature correctly? I've tried this a few times over the past month but go back to the 'normal' setup due to lack of time to troubleshoot. If an entity in the app.yaml is in HA, then feature wont work?

Predbat version

v8.29.13
Environment details
Standalone Docker
HA Docker

predbat_debug.yaml
Thanks in advance and I love seeing Predbat constantly evolve over the years!

[dandwhelan]

predbat.txt

[dandwhelan]

I've managed to fix this.
Deleted the predbat.db from the predbat folder. Turned off the mirror from HA, enabled gathering data from GeCloud and made the internal DB the primary, and it works. Then I added predbat to the exclusion list to record data in HA. I'm not interested in the HA graphs; the Web app is good enough. The only reason I want Predbat to store the data instead of HA, is that predbat seems to use a lot of space, and every few months, my HA would crash and wipe all the databases. Hopefully, this will resolve the issue. Predheat might not work, but it doesn't matter too much, as the predictions don't affect the upcoming schedule.

[gcoan]

The only reason I want Predbat to store the data instead of HA, is that predbat seems to use a lot of space

Yes Predbat can use a lot of HA database space if untamed. I have done some work on this and plan to document configuration changes that will dramatically reduce the amount of HA database space that Predbat uses.

Glad you got it sorted

[dandwhelan]

database indexing fix resolves this issue. It came back 4 times after closing this issue. #3114