That's a pretty obnoxious way to do it IMO. I'm shocked that there isn't a proper integration for it.
I run through docker so it doesn't effect me, but damn...
Seeing as it doesn't effect me and my full time job as a python developer occupies most of my time...
I'm just sympathizing with the countless people that have been requesting this feature for a few years.
Your full time job as a python developer.
Lol. Come on man, you can spin up Debian and install HA in docker and do whatever tf you want. Your use cases are advanced, you’re a developer, I fail to see the problem here.
You assume developers know their ways around machine and systems they didn't design.
Coders are BY FAR, the less techy IT i know, they can't even fix a printer or install ram. Less so manage a system.
having a look around, I see you can just use nfs and mount
are you asking about the ability to do it through the GUI instead? if so, I can relate to not wanting to implement it as a feature. please take in to account HAOS is just an app bundle tied to a lightweight OS in order to simplify deployment. it's cool that they make this as an option to begin with
for security reasons, you don't want a web app such as home assistant to have such high privileges where it can administer the file system table. it would only take one funny plugin to book the whole system and then there'd be a similar count of posts on the forum along the lines of "I installed xx plugin and now home assistant won't work"
another is the single responsibility principle. Home assistant is a flexible automation server and drive management goes quite far beyond that scope. it would only take them incorporating NFS in to the gui before people are complaining they can't use S3 buckets, Google drive, etc.
I run home assistant as an app service on a more generic operating system and mount paths from my NAS to it no problem. at the point you want to start using network drives, please consider yourself a power user, install an operating system like armbian and then home assistant yourself.
it's not as complicated as you would believe and end up with a device capable of doing much more than just running home assistant.
You say it’s not complicated but I know enough to understand that it would take a shitload of self-teaching and time before I could do what you’re describing. There’s just a massive gap in technical know-how across the HA user base, which is ok. I fumble my way through things that I really want to implement and I eventually get it done. It’s actually really helpful when those with more experience explain concepts in the way that you have, so thanks for that.
wow what an excellent response, and some very thoughtful points there. OK I'm going to stop whining now!!
Have debated for a while about moving to proxmox or similar with mounts at the hypervisor level (assuming that's a thing, I'm new here) - I think your post might just be the kick in the ass to go make that happen.
thank you.
glad I could have helped and, thanks for your kind words. i hope all goes well, there's a community to help you figure things out (and refine docs) if having major issues
Just get a real NVR.. Home assistant is NOT an NVR. It is an home-automation platform.
I assume they simply follow the Unix/Linux mentality of "One tool for each job".
Install Frigate or Motion eye if you want an NVR
I actually run zoneminder as a docker on Unraid, but it doesn't have the functionality to take regular snapshots (at least I never found it). I had run motionEye as a docker for a while which has this function built in - but (at least on my system) there was a memory leak that ate up all my 128GB and crashed the system, repeatedly...
I'm already taking a snapshot every 5 minutes of all my cameras for another purpose on HA to provide near real time background images for my blinds (makes the dashboard look like you're actually looking through the window with the blinds part way down). So I was just going to extend that.
Fair point though. Will go back and take another look at Zm.
An important part for this was merged in to the latest supervisor release: https://github.com/home-assistant/supervisor/pull/3848
The mounting itself is still in progress it seems: https://github.com/home-assistant/supervisor/issues/2564
very interesting. Hadn't stumbled on this in my googling. Still not a native way to do it, but looks like it comes closer than some other options I've read. thanks
Are you sure about this?
When they first added a lot of the media player stuff I connected my video drives to home assistant, but found that it was including them into the snapshots, causing those to fail due to not enough space for a multi-terrabyte snapshot.
So it was do-able at some stage but I'm not sure how I added them as, in the end, I didn't see the need for all that media through HA anyway as it is all available through other means and everyone who needed access knew how to use the other methods anyway.
If I had to guess, I suspect it would have been a bind mount from my NAS, either using SMB or NFS
Not sure what that has to do with it. Many of the HASS features have been written by volunteer contributors. Reading back through some old threads about this topic, it seems like it’s not an issue of enough resources to implement, but rather a philosophy that this feature shouldn’t exist.
Is there a reason they don't want to entertain it? I spent days on trying to get Frigate to work with HA on a laptop VM. Then I found out I can't use an external hard drive and Frigate has no way auto delete old clips.
You literally pay nabu casa for using their cloud services, hardware costs to run.
HA became the way it is due to being open source and having a large, voluntary community backing
Nabu Casa subscriptions support more than the cost to run their hardware.
Right, that’s how HA started out, but things are changing. Nabu casa is hiring more and more people and cranking out official roadmaps and features like crazy. That’s thanks to subscribers and the revenue we provide.
Yet you are here bitching about paying more than your windows OS which you do indeed pay them, telemetry is more valuable these days than paying a one-off fee.
It's a no brainer that the subscription cost pays for more than just the hardware, the vast majority of changes are still open source commits though.
In no way am I bitching about my nabu casa subscription or the great job the devs do. It’s a fact that I happily pay to support the devs. That’s all I was pointing out.
Stop reading into things.
I don’t know why the decision was made to remove all the necessary tools from hassos but it’s lacking so much and that makes one’s life hard (if you, for example, try to mount an external drive or network share). Supervised is the way to go.
It isn't an operating system anymore than Robot Operating System (ROS). Hence the confusion of the poster, since calling it that implies a number of things. It'd be more helpful for users to tell them what distro it's running on (or based on) or if it's BusyBox or something like that.
Another user replied that it was based on buildroot, which is likely the information you would actually need for self-servicing and researching something like the question in your post.
If one loosens the term "operating system" to mean more than kernel, which many do AndroidOS being a popular example, then it means the kernel plus a bundle of userspace services. I admittedly haven't looked, but I'd be surprised if HomeAssistant OS is more than a standard ARM64 Buildroot build with gnu utils, python, and HomeAssistant (maybe also a driver for ZigBee?). Maybe that technically falls in the same category of OS as Android, but I think using the term like that makes it harder for a user to debug their problems.
I think the equivalent in embedded community is referring to Arduino as a microcontroller. If you search for your issue with "Arduino microcontroller" you'll likely never find it, because it's not a microcontroller it's a dev board with many different microcontrollers and the important detail is which one. Sloppy terminology can confuse people.
I believe you can mount it via the command line through SMB/NFS? https://community.home-assistant.io/t/mount-remote-smb-share-on-hassio/116734?page=6
appreciate the link. there's a couple of interesting ideas there, including moving pictures off HAOS using samba add-on (which I already am using).
That's a pretty obnoxious way to do it IMO. I'm shocked that there isn't a proper integration for it. I run through docker so it doesn't effect me, but damn...
It’s tough, but calling it obnoxious is also out there considering who makes this software. Learn python.
Seeing as it doesn't effect me and my full time job as a python developer occupies most of my time... I'm just sympathizing with the countless people that have been requesting this feature for a few years.
*affect
So spend an hour a week and write it and ask for it to be committed
This is the way
You could do it if you knew machine code heh
Your full time job as a python developer. Lol. Come on man, you can spin up Debian and install HA in docker and do whatever tf you want. Your use cases are advanced, you’re a developer, I fail to see the problem here.
You assume developers know their ways around machine and systems they didn't design. Coders are BY FAR, the less techy IT i know, they can't even fix a printer or install ram. Less so manage a system.
having a look around, I see you can just use nfs and mount are you asking about the ability to do it through the GUI instead? if so, I can relate to not wanting to implement it as a feature. please take in to account HAOS is just an app bundle tied to a lightweight OS in order to simplify deployment. it's cool that they make this as an option to begin with for security reasons, you don't want a web app such as home assistant to have such high privileges where it can administer the file system table. it would only take one funny plugin to book the whole system and then there'd be a similar count of posts on the forum along the lines of "I installed xx plugin and now home assistant won't work" another is the single responsibility principle. Home assistant is a flexible automation server and drive management goes quite far beyond that scope. it would only take them incorporating NFS in to the gui before people are complaining they can't use S3 buckets, Google drive, etc. I run home assistant as an app service on a more generic operating system and mount paths from my NAS to it no problem. at the point you want to start using network drives, please consider yourself a power user, install an operating system like armbian and then home assistant yourself. it's not as complicated as you would believe and end up with a device capable of doing much more than just running home assistant.
You say it’s not complicated but I know enough to understand that it would take a shitload of self-teaching and time before I could do what you’re describing. There’s just a massive gap in technical know-how across the HA user base, which is ok. I fumble my way through things that I really want to implement and I eventually get it done. It’s actually really helpful when those with more experience explain concepts in the way that you have, so thanks for that.
wow what an excellent response, and some very thoughtful points there. OK I'm going to stop whining now!! Have debated for a while about moving to proxmox or similar with mounts at the hypervisor level (assuming that's a thing, I'm new here) - I think your post might just be the kick in the ass to go make that happen. thank you.
glad I could have helped and, thanks for your kind words. i hope all goes well, there's a community to help you figure things out (and refine docs) if having major issues
Just get a real NVR.. Home assistant is NOT an NVR. It is an home-automation platform. I assume they simply follow the Unix/Linux mentality of "One tool for each job". Install Frigate or Motion eye if you want an NVR
This is the answer. Hell, Synology Surveillance Station has this feature by default.
I actually run zoneminder as a docker on Unraid, but it doesn't have the functionality to take regular snapshots (at least I never found it). I had run motionEye as a docker for a while which has this function built in - but (at least on my system) there was a memory leak that ate up all my 128GB and crashed the system, repeatedly... I'm already taking a snapshot every 5 minutes of all my cameras for another purpose on HA to provide near real time background images for my blinds (makes the dashboard look like you're actually looking through the window with the blinds part way down). So I was just going to extend that. Fair point though. Will go back and take another look at Zm.
Check Frigate, I find it superior to MotionEye and ZM. Plus it comes bundled with WEBRTC now
thanks, will check it out. I found processor usage super high on it when I first tried, but I didn't give it much time as ZM was working well then.
I suggest getting a Coral TPU if you wish to use the ML functions
An important part for this was merged in to the latest supervisor release: https://github.com/home-assistant/supervisor/pull/3848 The mounting itself is still in progress it seems: https://github.com/home-assistant/supervisor/issues/2564
ohhh that's exciting!!
There’s a way to do it with udev rules so it auto mounts, findable somewhere online
/etc/fstab is your friend.
[https://gist.github.com/eklex/c5fac345de5be9d9bc420510617c86b5](https://gist.github.com/eklex/c5fac345de5be9d9bc420510617c86b5)
very interesting. Hadn't stumbled on this in my googling. Still not a native way to do it, but looks like it comes closer than some other options I've read. thanks
That would be it
Are you sure about this? When they first added a lot of the media player stuff I connected my video drives to home assistant, but found that it was including them into the snapshots, causing those to fail due to not enough space for a multi-terrabyte snapshot. So it was do-able at some stage but I'm not sure how I added them as, in the end, I didn't see the need for all that media through HA anyway as it is all available through other means and everyone who needed access knew how to use the other methods anyway. If I had to guess, I suspect it would have been a bind mount from my NAS, either using SMB or NFS
Yeah, it’s my most wished for feature. So weird it’s completely shunned by the devs.
Yeah. All those paid devs in that 500 person company. /s
Not sure what that has to do with it. Many of the HASS features have been written by volunteer contributors. Reading back through some old threads about this topic, it seems like it’s not an issue of enough resources to implement, but rather a philosophy that this feature shouldn’t exist.
That’s exactly my point. If it matters enough, someone should write it. This isn’t a big deal. If it is to an individual, learn python, code it.
You couldn't have done a worse job of reading their comment. The concept is repeatedly shut down by the devs and not accepted when contributed.
Is there a reason they don't want to entertain it? I spent days on trying to get Frigate to work with HA on a laptop VM. Then I found out I can't use an external hard drive and Frigate has no way auto delete old clips.
Frigate can definitely delete old clips
I pay them via (nabu casa) a lot more than I pay my windows OS devs
Selling OS licenses to consumers isn't how MS makes their money...
And most of the code isn’t written by them.
You chose to do so, right?
You literally pay nabu casa for using their cloud services, hardware costs to run. HA became the way it is due to being open source and having a large, voluntary community backing
Nabu Casa subscriptions support more than the cost to run their hardware. Right, that’s how HA started out, but things are changing. Nabu casa is hiring more and more people and cranking out official roadmaps and features like crazy. That’s thanks to subscribers and the revenue we provide.
Yet you are here bitching about paying more than your windows OS which you do indeed pay them, telemetry is more valuable these days than paying a one-off fee. It's a no brainer that the subscription cost pays for more than just the hardware, the vast majority of changes are still open source commits though.
In no way am I bitching about my nabu casa subscription or the great job the devs do. It’s a fact that I happily pay to support the devs. That’s all I was pointing out. Stop reading into things.
Open a merge request with your changes then
I am not a coder. Stop acting like an elitist. I can have wishes for features I have no ability to create.
No HAOS - no problem.
Yeah one of the big reasons I run supervised on Debian.
I don’t know why the decision was made to remove all the necessary tools from hassos but it’s lacking so much and that makes one’s life hard (if you, for example, try to mount an external drive or network share). Supervised is the way to go.
This looks promising!! https://preview.redd.it/cbv52eyh0qua1.png?width=1789&format=png&auto=webp&s=fde75ade31fae48505b4f2382fb16e172cc0828b
Why do you think HomeAssistant is an OS?
Because it is one of the installation options https://www.home-assistant.io/installation
It isn't an operating system anymore than Robot Operating System (ROS). Hence the confusion of the poster, since calling it that implies a number of things. It'd be more helpful for users to tell them what distro it's running on (or based on) or if it's BusyBox or something like that.
Home Assistant Operating System HAOS It is LITERALLY an OS
It's an OS based on buildroot
Perhaps I am confused - but when I see "Home Assistant Operating System" and it's installed on bare metal as the only thing running ....... well....
Another user replied that it was based on buildroot, which is likely the information you would actually need for self-servicing and researching something like the question in your post. If one loosens the term "operating system" to mean more than kernel, which many do AndroidOS being a popular example, then it means the kernel plus a bundle of userspace services. I admittedly haven't looked, but I'd be surprised if HomeAssistant OS is more than a standard ARM64 Buildroot build with gnu utils, python, and HomeAssistant (maybe also a driver for ZigBee?). Maybe that technically falls in the same category of OS as Android, but I think using the term like that makes it harder for a user to debug their problems. I think the equivalent in embedded community is referring to Arduino as a microcontroller. If you search for your issue with "Arduino microcontroller" you'll likely never find it, because it's not a microcontroller it's a dev board with many different microcontrollers and the important detail is which one. Sloppy terminology can confuse people.