jes i created a data point making flow, never doing that again i think.
i also tought about deleting an reinstalling but i don’t want to set up al my dashboard again.
a ability to delete data when there is a new data point for that flow should be enoug. but next time i wil explore how to make a script i think
I installed this test version and RAM usage went from a stable 49MB to 79MB 
.
… But how… I literally only reduced data that was stored in memory.
Well, that’s why this is a test version 
. Maybe it will reduce again over time. I’ll keep an eye out on my apps memory consumption as well and I hope to add some more improvements over time.
If anyone else likes to try 1.4.0 and share their experience with RAM consumption over time, please do.
Haha, yes strange. I went back to v1.3.5 and it’s still hovering around 80MB (even after a restart). Must be coincidental and related to something else then.
Version 1.3.5. I did change some Widgets in december due to app update. With one I added a third line graph. Can‘t recall any other change.
Will test the update.
After Installation of 1.4.0 memory usage dropped for a few minutes to rise to 87 MB from 83 MB with 1.3.5.
Funny in the app display homey says usage 92MB
just another smal idea if you have time.
by the linechart you a small lettertype available is that also posible by the progresbar so that i have a uniform sight if i look to the screen.
i gave up with deleating al the data from my flow, the app crashes every 10 points i remove so after a houre of clicking and no visible progress i quit.
The increase in RAM usage seems to have normalized again, looking at the last 24 hours graph and RAM usage is currently even a little less than before 
:
DataVista v1.5.0 is now available in the test channel!
This version includes new App settings page with a bulk cleanup option that allows you to remove outdated/unused data. Further more, this change includes some maintenance changes (internal app refactoring).
@qawsedrf57 For your situation, I’d recommend updating all the identifiers you want to keep on a daily basis. Then use the bulk cleanup function to remove everything older than a day; this way you’ll clear out the unused entries while preserving the ones you need.
Thanks i wil instal it right away and when i am back at home i wil check it out
i managed to delete al 14000+ file’s so that is nice. it took about 3 houres. now i can make widged again without app crashes
thanks a lot for the fast responses!
@qawsedrf57 / @Erikvl87: Can you explain what this large number entails?
I have approx 70 gauges / progress bars / status bars / ranges defines, of which half are in use. These update constantly through flows or directly by the device’s capability (e.g. changes in power consumption, CO2 levels). This does not change the number of gauges, ranges, etc.
My flows also made a lot of new one’s i had made a flow to represend my home battery status from -9000 til +9000w and that generated a lot of data!
Just to be clear, representing a range with DataVista, no mather how long, is not creating additional data entries. What in fact happened here is that the identifier was misconfigured to hold a dynamic value, hence it created lots of unique entries (identifiers). It should’ve been configured with a fixed identifier instead, like battery status.
Ah yes, that makes sense. I now also see it in the screenshots posted above 
.
Oof… Sorry for that! I’ve seen this one once on my own dashboard as well… I’ll make sure to fix it in an upcoming release.
