- The target platform for HASS / HASS.IO is a raspberry pi, yet if you use the defaults the History and log book functions grind to a halt after a week of data collection. Speed of SD card is a factor yet it is still often very bad if you try and collect more than maybe 3 days on a PI.
- Authentication and action logging have been added but can’t be seen in the logbook
- why are there no filter options for sensor type etc in the history? graphing is very weak in general it becomes un-usable very fast once you have a moderate number of sensors, even if you are excluding many.
You can exclude items from being recorded (hence, removed from history display) by setting up the recorder.
But yes, if the target is a RPi, then the defaults should be optimized for use on that platform. But a lot of people find that they outgrow the Pi and move on to more powerful hardware.
1 Like
Hass IO doesn’t really run well on any virtualization platforms (too picky about devices) yet so I am suck waiting…
I already exclude things in recorder… still bogs down easily if I let it store more than 3 days to a week as some sensors are noisy.
I’ve never done it but I know there are ways to install hassio in docker. Do a search and you should be able to find threads about it.
I personally don’t really like the “hassio” concept.
I like the snapshot functions, they make rolling back screwed up releases and configs a lot easier than handling them independently with docker.
I also don’t like having to deal with the python configs etc so it makes it a nice package.
I can’t even run the docker on synology because there is no access to the USB ports on that platform from docker… I can however run a VM with USB support so that is my plan, to run a hassos vm once it is compatible… the early betas now have virtIO drivers but have problems mapping devices.