Skip to content

Beacon

v0.5.2-tunnel-homeassistant Feature

This release adds 2 notable features for engineering teams evaluating rollout.

✓ No known CVEs patched
Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Topics

home-lab home-lab-dashboard home-security hosting-deployment iot iot-application
+3 more
monitoring monitoring-automation self-hosted

Summary

AI summary

Beacon adds tunneling support to expose Home Assistant remotely.

Full changelog

🚀 Beacon Release — Tunnels for Home Assistant

This release introduces one of the biggest steps yet for Beacon: tunneling support.

You can now use Beacon to expose local services like Home Assistant securely through a managed tunnel, without manually opening ports or building a separate remote-access setup around your homelab.


✨ Highlights

🌐 Tunnel support

Beacon can now run and manage tunnels for local services, making them reachable remotely in a much simpler way.

This is especially useful for self-hosted apps running on:

  • Raspberry Pi
  • mini PCs
  • homelab servers
  • home networks behind NAT

Instead of stitching together multiple tools yourself, Beacon can become the place where deployment, monitoring, and remote access meet.

🏠 Home Assistant integration

The main use case for this release is Home Assistant.

You can now tunnel your local Home Assistant instance through Beacon, making it accessible remotely while keeping the setup aligned with Beacon’s local-first, self-hosted approach. You can install Beacon as a Home Assistant app (formerly addon), or if you run Home Assistant in a docker container, just point Beacon to it.

This makes Beacon more than a deploy agent — it starts becoming a real control point for home infrastructure.

🔌 A strong foundation for Beacon Home

This release is also an important step toward a broader vision: using Beacon as the agent that powers services running at home.

Home Assistant is the first natural fit here, but the same tunnel model can later support other local services too.


Why this matters

Remote access to self-hosted services is usually annoying:

  • router configuration
  • port forwarding
  • dynamic DNS
  • reverse proxies
  • certificate setup
  • keeping everything stable over time

Beacon now starts to remove that complexity.

With tunnels, the path becomes much simpler:

  1. Run your service locally
  2. Register or configure the tunnel in Beacon
  3. Access it remotely through Beacon’s managed setup

For Home Assistant in particular, this makes remote access much more approachable for users who want control without unnecessary infrastructure overhead.


🛠️ What’s included

  • support for Beacon-managed tunnels
  • Home Assistant as the first clear tunnel use case
  • groundwork for exposing more local services through Beacon
  • another step toward Beacon as a true self-hosted infrastructure agent for the home

❤️ Vision

Beacon started as a deployment and monitoring agent for self-hosted infrastructure.

With this release, it moves further toward something bigger:

A single agent for running, monitoring, and securely accessing services in your home environment.

Home Assistant is just the beginning.

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Track Beacon

Get notified when new releases ship.

Sign up free

About Beacon

All releases →

Related context

Earlier breaking changes

Beta — feedback welcome: [email protected]