Home Assistant Core -- TrueNAS CORE Community Plugin

[troy]

@jkhii Thank you for your feedback

@jkhii

Maintain a Manual Install Guide along side of the plugin. This will allow those of us that need to adjust some things to our specific situation. For example: I don’t use DHCP for server jails and I have multiple VLANs in my jail. This guide could also provide a good starting point for someone that needed to install on raw FreeBSD or in a jail not managed by iocage.

I’m already working on this

3 years ago, my first guide was a manual guide and shortly there after I made the first version of this plugin but having the usual concerns about “plugins” on FreeNAS, I quickly backed away from that in favor of a “scripted install” for a standard-jail for FreeNAS 11.2. When FN 11.3 was released with the community plugins page, and I realized I could still have full control of the artifact repo, I figured I would re-release this as a “plugin”

@jkhii

Provide instructions for use with the plugin and the Manual Guide to keeping the Home Assistant configuration and data in datasets outside of the jail.

This was already in my 11.2 guide but I never updated anything as far as a manual guide for the 11.3 release. ( the previous guide is really only outed in terminology and screenshots more than anything else ) We can talk about my excuses for that delay another time… Anyways for TrueNAS Core, my goal is finally bring everything back together once and for all. Hopefully the new service script mentioned on the temp wiki page is going to be the start. –

This already, is not the typical “plugin” you may expect or be used to. I think in general, it’s easy for FreeNAS user’s to have bad taste for “plugins” dating back to the old warden days. With iocage, at least in the case of this plugin, things are different. For instance, this plugin always installs the current version HA Core available at the time and you can mange maintain a version or update as you see fit. Also there is no need to wait for any kind of “plugin update” in order to update HA.

I think this is very much a hybrid-plugin - meaning you still have almost full control ( currently it’s just very fragmented if you want to change some things ) Typically a plugin would manage everything for you. I’m only using the “plugin” as a way to provide an install button from the FN UI and provide easy updates for a few files, like the console menu script and the rc service scripts. There are a few considerations I really do need to document but basically you can about 98% percent treat this “plugin” like a “manual install” – This is also why, in this plugin you will sometimes see “manual intervention required” – It is not something extra because your using this “plugin” – It is a step that would still be required in a manual installation anyways.

Which brings me to the updated service script on the temp wiki page and finally bringing everything back together. My hope is that by the time TrueNAS Core is released, I’ll have mostly refactored this plugin ( in this case I mean the virtualenv services ) to be configurable using sysrc. The idea is to use the RC Service Guide ( temporary wiki page ) as the configuration guide for the plugin – Then in the RC Service Guide I’ll break down each service command into the manual steps that are being preformed.

@jkhii

Consider creating a FreeBSD port with your scripts. This would mean that the Plugin only had to create the correct jail environment and install the package created from your port and it would make Home Assistant available to a lot of FreeBSD users that are not using FreeNAS

I really like this idea. I think the new service script will really go along way to make this happen. In fact, if you installed the requirements and created the user first, I see no reason to prevent the new service script from working on a vanilla FreeBSD system, outside of iocage right now! I think ( after I get things cleaned up ) the only thing missing is creating a port.