From 17f39b267ac2817e03c6cb4927b6f8dd7f8a13fa Mon Sep 17 00:00:00 2001 From: Klaas Schoute Date: Tue, 23 Apr 2024 08:46:32 +0200 Subject: [PATCH] Fix the blueprint community link (#32417) --- source/_docs/blueprint.markdown | 2 ++ 1 file changed, 2 insertions(+) diff --git a/source/_docs/blueprint.markdown b/source/_docs/blueprint.markdown index 7fe1eb1de7d..eb07e05191c 100644 --- a/source/_docs/blueprint.markdown +++ b/source/_docs/blueprint.markdown @@ -23,3 +23,5 @@ A blueprint is a {% term script %} or {% term automation %} configuration with c Imagine you want to control lights based on motion. A blueprint provides the generic {% term automation %} framework, while letting you select one specific motion sensor as a {% term trigger %}, and the exact light to control. This blueprint makes it possible to create two automations. Each automation has their own configuration and act completely independently. Yet, they share some basic automation configuration so that you do not have to set this up every time. Blueprints are shared by the community in the [blueprint community forum][blueprint-forums]. + +[blueprint-forums]: /get-blueprints