Victor
Then there will be no measurement history. For recording, all unnecessary and uninteresting entities, such as reception levels and others, are disabled. Store depth limitation for one month and data...
This still does not allow Home Assistant to work for a long time on eMMC and especially on SD cards. Only on SSD or HDD. With SSDs, it is additionally...
> I don't think it's physical "parking" since it doesn't have moving parts, so what's the problem? Failure due to loss of markings or programs due to a power failure....
@ffries Only HA is installed on the SSD.  `/var/lib/bluetooth/ ` :  eMMC (system) and NVMe (Home Assistant), All logs are written to RAMdisk ``` UUID=xxxxxx-xxxx-xxxx-xxxx-xxxxxxxx / ext4 defaults,noatime,commit=600,errors=remount-ro,x-gvfs-hide...
Home Assistant is very slow on an SD card. It's the same on an SSD drive via ATA. It takes a very long time for the graphs to be drawn...
@ffries - what are you talking about? 1. `commit=600` 2. The record count data shown in the graph comes from the NNME controller, not the OS. Study the subject before...
> The BLE devices do update quite often. Zigbee Tyua:  WiFi:  Result:  Step - this HA rewrites the database every day  NanoPi-R5S, RAM: 4GB, 16GB eMMC,...
> I do not need so detailed history (only maybe for week, then its okay to have average value for lets say 1 hour period, is there an easy way...
> about 90MB for a month (it is three sensors 90MB per month / three sensors = 30MB per sensor? I have 89 or more devices in one of the...
> On Debian(Armbian tested) you can bypass the option to write the BlueZ cache to disk in two ways: **First one:** recompile BlueZ with the modified STORAGEDIR option in a...