Frickelalarm: New alarm system that runs on Home Assistant – MCP support
What started as a weekend project has become a full alarm system for Home Assistant: modes, delays, reactions, presence-based automation, its own Lovelace card – and, uniquely, configurable through services, so a langua…
以下正文同步自 Hacker News 最新,版权归原站所有,已转换为易读排版。
What started as a weekend project has become a full alarm system for Home Assistant: modes, delays, reactions, presence-based automation, its own Lovelace card – and, uniquely, configurable through services, so a language model can even set it up over the Home Assistant MCP server. Here's how.
A few days ago I announced Frickelalarm here – an alarm-system integration for Home Assistant that brings the whole alarm logic with it. Since then the scaffold has turned into a genuinely usable system. Time for a proper write-up: what can it do, and how do you set it up?
Code and releases are out in the open at github.com/ankaios76/frickelalarm.
You've got door and window contacts, motion sensors, a siren and a phone. Frickelalarm is the piece in between: a clean alarm_control_panel with its own state machine – arm, delay running, triggered, disarm again – set up entirely through the UI, no YAML.
Since Home Assistant 2026.11, HACS is built in as the Marketplace (Settings → Marketplace). Custom repositories still work.
The integration ships its own Lovelace card and registers it automatically – no need to add a resource by hand. Drop it on the dashboard as a manual card:
type: custom:frickelalarm-card entity: alarm_control_panel.haus_frickelalarm name: House keypad: collapsible # optional: false | true | collapsible
It shows the state in colour, a countdown during the delays, the trigger, open and bypassed sensors – and, if you like, a collapsible number keypad for the code.
Everything can be changed at any time via Configure (the gear on the entry) – menu-driven:
Tip: put the front door on "delayed", but not the motion sensors – that way you can disarm when you get home, while an intruder coming through a window triggers immediately.
The switches can also be flipped at runtime via the frickelalarm.set_automation service.
Frickelalarm can be configured entirely through services, not just through the UI. That sounds unremarkable, but it has a nice effect: via the Home Assistant MCP server, a language model (e.g. Claude) can set the system up and operate it – add sensors, set times, arm/disarm, panic. That's exactly what comparable solutions can't do.
It also fires events for the logbook and your own automations: frickelalarm_armed/arming/pending/triggered/disarmed and frickelalarm_tamper.
This is a hobby/learning project of the Frickelfabrik and explicitly a beta – for trying out, breaking and reporting back. There's Alarmo, a mature and very popular solution with a similar feature set; Frickelalarm is built from scratch on purpose (learning, full control, a few own touches – and that MCP twist).
Ideas, bug reports and testers are welcome – best via the issues on GitHub.
Screenshots are from a German Home Assistant; the UI follows your HA user's language.
正文由 探How 从来源站点 RSS 同步,内容未经改写;遇到排版缺失或需要图片、视频时请以原文为准。