Skip to content

BabyBuddy, wrapped into a Home Assistant addon

Notifications You must be signed in to change notification settings

jeroenterheerdt/addon-babybuddy

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 

Repository files navigation

addon-babybuddy

BabyBuddy, wrapped into a Home Assistant addon!

Source for Baby Buddy is here: https://github.com/babybuddy/babybuddy

This repo just takes the code from baby buddy and puts it in addon form.

Installation (basic)

Add this addon-repo to your home assistant by going to to Settings -> Add-ons -> Add-on Store and add this URL as an additional repository:

https://github.com/OttPeterR/addon-babybuddy

Additional setup for HTTPS

Follow these additional instructions if your Home Assistant instance is set up so that it can only be accessed via HTTPS (e.g., using the DuckDNS add-on. For example, you access your Home Assistant instance at https://example.duckdns.org:8123.

  1. Install the Nginx Proxy Manager available from the Home Assistant Add-on Store. Closely follow the installation instructions. We will use this add-on the set up a reverse proxy so that you can access BabyBuddy via HTTPS externally.

  2. From a machine on the same local network as your Home Assistant instance, identify the local IP address of the Home Assistant machine (e.g., 192.168.1.100). Then, direct your browser to http:https://192.168.1.100:81 to access the Nginx Proxy Manager admin page. (Note, even though Home Assistant is set up to only be accessed on your domain via HTTPS, you can access Nginx Proxy Manager locally because it is an add-on running in a separate Docker container. The Nginx Proxy Manager admin page will only ever be accessible via your local network for security reasons, assuming your router does not forward port 81 to your Home Assistant machine)

  3. Forward port 80 and 443 on your router to your Home Assistant machine. These ports will be sent to the Nginx Proxy Manager add-on, and not directly to Home Assistant Core. This will allow you to access Baby Buddy via HTTPS on your domain.

  4. On the Nginx Proxy Manager admin dashboard, navigate to Hosts -> Proxy Hosts -> Add Proxy Host. Enter the domain you want to use to access Baby Budy (e.g., babybuddy.example.duckdns.org). Use http as the scheme (i.e., how Baby Buddy is accessed locally). Enter the Home Assistant local IP address as the Forward IP (e.g. 192.168.1.100). Enter 8000 as the forward port (or whatever you have set up in the Baby Buddy add-on configuration as the port.) Under the SSL tab, select Request a new SSL certificate and check Force SSL and agree.

  5. In the Baby Budy add-on configuration, under CSRF_TRUSTED_ORIGINS enter your domain for Baby Buddy (e.g., https://babybuddy.example.duckdns.org).

You should now be able to acess Baby Buddy via your domain (e.g., [https://babybuddy.example.duckdns.org]). You may want to use a Markdown card or a Button set up to your domain.

About

BabyBuddy, wrapped into a Home Assistant addon

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • Dockerfile 61.6%
  • Shell 31.5%
  • Groovy 6.9%