Hi @Terdious !
I’ll take this opportunity to post this message here:
However, I think we should keep these topics separate; the DuckDB part is quite technical and it’s a long-term change that has impacts far beyond the graphical side. I think I’ll get started on it once I’ve finished my current developments 
Regarding your development, it’s really cool!
On the other hand, I think there’s a real need to think about this outside of Gladys before even talking about development. I know it’s always more fun to dive headfirst into development, but first we need to know what we want 
What exactly will this feature be used for and who will use it?
Example:
- « I want to know my home’s consumption during the week of January 12 when I was on vacation to see my consumption when my house is empty ».
- … ?
Then, you need to make mockups (I personally use whimsical), and ensure that the mockups answer our questions.
For now the « History » tab you just copy-pasted the dashboard tab, and so in my opinion it doesn’t really meet the need. I understand that you went as fast as possible to do tests, but in this case it would have been even faster to just make a mockup 
Because now you’re going to end up coding the feature six times, it’s a shame ^^
Do you want to have a call to formalize the development?