<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>HA on Margrop Blog</title>
    <link>https://blog.margrop.net/en/tag/ha/</link>
    <description>Recent content in HA on Margrop Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-US</language>
    <lastBuildDate>Sat, 23 May 2026 12:46:00 +0800</lastBuildDate>
    <atom:link href="https://blog.margrop.net/en/tag/ha/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Proxmox VE 9.2 Is Out: Not Just a New Kernel, but a Cluster That Can Start Balancing Itself</title>
      <link>https://blog.margrop.net/en/post/proxmox-ve-9-2-dynamic-load-balancer-release/</link>
      <pubDate>Sat, 23 May 2026 12:46:00 +0800</pubDate>
      <guid>https://blog.margrop.net/en/post/proxmox-ve-9-2-dynamic-load-balancer-release/</guid>
      <description>&lt;blockquote&gt;&#xA;&lt;p&gt;&lt;strong&gt;Short version&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;Proxmox VE 9.2 was officially released on May 21, 2026. On the surface it is a platform refresh: Debian 13.5 Trixie, Linux kernel 7.0, QEMU 11.0, LXC 7.0, ZFS 2.4, and updated Ceph options. The more interesting story is operational: dynamic load balancing through CRS, safer HA maintenance with arm/disarm, a much stronger SDN fabric story, web-based custom CPU model management, and many smaller fixes around guests, storage, security, and automation.&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;p&gt;If you run a single-node homelab, Proxmox VE 9.2 may not feel dramatic on day one. If you operate a multi-node cluster with HA resources, Ceph, software-defined networking, custom CPU compatibility requirements, Windows secure boot, external automation, or strict maintenance windows, this release deserves a careful read.&lt;/p&gt;&#xA;&lt;p&gt;This article summarizes the official Proxmox VE 9.2 release and adds an operator’s view: what changed, what problem each change addresses, what to test before upgrading, and when it is reasonable to wait. All hostnames, addresses, cluster names, accounts, and command outputs are placeholders. No private environment details are included.&lt;/p&gt;</description>
    </item>
    <item>
      <title>HomeAssistant Configuration: Auto-Reminder When Security Door is Left Open for Extended Period</title>
      <link>https://blog.margrop.net/en/post/homeassistant-attation-master-when-door-is-open-too/</link>
      <pubDate>Tue, 09 Mar 2021 18:18:37 +0800</pubDate>
      <guid>https://blog.margrop.net/en/post/homeassistant-attation-master-when-door-is-open-too/</guid>
      <description>Required devices: 小米门窗传感器, 小米Aqara网关, 小米触屏音箱&#xA;When the door remains open for 1 minute and for 2 minutes, the speaker will automatically give a voice reminder to close the door&#xA;description: &amp;#39;&amp;#39; trigger: - type: opened platform: device device_id: 000000f29088665d7b820e7d4000000 entity_id: binary_sensor.door_window_sensor_158d0002000000 domain: binary_sensor for: hours: 0 minutes: 1 seconds: 0 milliseconds: 0 - type: opened platform: device device_id: 000000f29088665d7b820e7d4000000 entity_id: binary_sensor.door_window_sensor_158d0002000000 domain: binary_sensor for: hours: 0 minutes: 2 seconds: 0 milliseconds: 0 condition: [] action: - service: zhimsg.</description>
    </item>
  </channel>
</rss>
