<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Home_assistant on MekOps</title>
    <link>https://mekops.com/tags/home_assistant/</link>
    <description>Recent content in Home_assistant on MekOps</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>© CC-BY-4.0 by MekOps</copyright>
    <lastBuildDate>Mon, 30 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://mekops.com/tags/home_assistant/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Siphon: Building a Zero-Trust Edge Gateway for Home Assistant</title>
      <link>https://mekops.com/post/2026-03-30_siphon_intro/</link>
      <pubDate>Mon, 30 Mar 2026 00:00:00 +0000</pubDate>
      
      <guid>https://mekops.com/post/2026-03-30_siphon_intro/</guid>
      <description>
        
          
            If you are exposing your Home Assistant instance directly to the Internet, you are playing Russian roulette with your
local network. It only takes one zero-day vulnerability in a custom integration to give a botnet full access to your
smart home and everything else on your LAN. But we live in a connected world. You still need a way for external
services—like a GPS tracker on your car, a webhook from a Garmin watch, or a custom script running on a remote
VPS to push data into your home.

          
          
        
      </description>
    </item>
    
  </channel>
</rss>