Repository: Community Hass.io Add-ons

Installation Home Assistant OS
3

I voted for options that are not covered by other repos.

I use openvpn AS, I recommend it for the admin UI.
There is docker image(s) already available:
https://hub.docker.com/r/linuxserver/openvpn-as/

4

Yeah, I have to go with the options not supported by other repos too. I already have a working InfluxDB and Grafana instance, but would really like to see the pi-hole and openVPN implemented.

Thanks,

5

Yeah, the UI is great and all, but the whole thing is limited to 2 connections.
You’ll have to pay if you want more ($15 a year per connection).
In my case; a couple of iPhones, iPads and a laptop… $$$

Next issue: Closed source (or am I missing something?)

6

You’re right - I forgot about the concurrent connection limit.
For me at home its not a problem. I won’t generally be logged in on more than one device at a time, and no one else is using VPN.
So the tradeoff between simplicity to deploy and create users, certs etc vs low connections limit was good (for me).
I think it was less that 30 mins from deploying the OVPN AS VM from their ovf to a fully working system including google authenticator support.

7

How about something like Pritunl?

1 Like
8

11 posts were merged into an existing topic: Community Hass.io Add-on: Terminal

9

Looks nice… but I dont have any experience of it.

10

Tellstick would be lovely to have. I have a lot of Nexa controllers and a Tellstick Duo. I used this guide on hassbian but I don’t know how to make it into an addon for hassio.

17

83 posts were merged into an existing topic: Add-on: Homebridge

20

:tada: Major repository updates.

Sorry, it took a long time, but this involved a lot of testing and searching the Hassio codebase in order to find its possibilities and boundaries.

I’ve released three plugins in relatively a short time frame and quickly discovered that the whole Hassio repository thingy did not work for me, regarding flexibility, maintainability, and testability.

Finally, I’ve found a more useable setup. Things changed:

  • Every add-on now has its own GitHub repository
    This makes separation of concerns is very useful in a lot of ways. It gives me separation of GitHub issues, allows me to use GitHub releases, makes setting up tests a breeze, and a lot of other stuff.

  • The Hassio repository maintains a working state
    The Hassio repository https://github.com/hassio-addons/repository, will still be the main entry point. So for you guys, nothing changes. The repository itself does not contain any actual add-on code, but merely stub to point your Hass.io in the right direction.

  • Each add-on is easily forkable and locally buildable
    Since each add-on now has its own repository on GitHub, we are given the possibility to add each add-on to the Hassio installation separatly. This makes it easy to fork the repository on GitHub, add the forked repository to your Hassio instance, test build it, and open a PR with the original repository.

WARNING: Doing this will build the add-on locally on your device using the latest version found in the repository.

  • Incubator
    This new setup allows me to create an add-on and put them out into public testing. I’ve added a new Hassio repository, that will contain alpha/beta releases of unreleased plugins.
    At the time of writing, this repository is empty but will be filled with some cool stuff soon. Check it out: https://github.com/hassio-addons/incubator

Everything has already been restructured; you can see the result of this on:

I want to thank @pvizeli for answering the mountains of questions I’ve fired at him on Discord; for fixing some of my issues and implementing some new features with/in the Hassio codebase. :+1:

I hope you can understand why I was holding back on fixing open issues.

Thank you for your patience.

…/Frenck

4 Likes
22

For better security: fail2ban

1 Like
23

I like your idea @Cent, but as far as I know, that won’t be possible via add-ons :thinking:

24

Home Assistant supports that native: https://home-assistant.io/components/http/

ip_ban_enabled Flag indicating whether additional IP filtering is enabled. Defaults to False.
login_attempts_threshold Number of failed login attemt from single IP after which it will be automatically banned if ip_ban_enabled is True. Defaults to -1, meaning that no new automatic bans will be added.

I got mine set to true and 4.

1 Like
27

True… but this is only limited to the web interface of Home Assistant. This does not protect other add-ons or installed services.

36

For as far as I can see that only applies to the web interface and not to eg. SSH. So there is little protection, and you have to login as root with SSH also (although due to the partition of the SD card not everythign is exposed).

37

Dasher …

I loaded it manually on my hassio, but an official add-on would be extremely helpful for many users.
Dasher is an excellent addition to home assistant.

1 Like
39

Hi,
I think it would be better to use this vpn tool. It also includes openvpn:

https://hub.docker.com/r/siomiz/softethervpn/

Daranto

40

There is already a great working add-on for dasher: https://github.com/james-fry/hassio-addons/tree/master/dasher

1 Like
42

Hey, would it be possible to add minidlna and transmission?
Thanks!
B

43

Thanks for the suggestions. I will add them to the poll as soon as one of the current add-ons in the poll has been created.