diff --git a/docs/device_automation_action.md b/docs/device_automation_action.md
index 393befb5f..bb09d79e5 100644
--- a/docs/device_automation_action.md
+++ b/docs/device_automation_action.md
@@ -3,6 +3,10 @@ title: "Device actions"
 sidebar_label: Actions
 ---
 
+:::warning
+We are currently exploring alternatives to device automations. Existing device automations will continue to work but new device automations won't be accepted.
+:::
+
 Device actions allow a user to have a device do something. Examples are to turn a light on or open a door.
 
 Device actions are defined as dictionaries. These dictionaries are created by your integration and are passed to your integration to create a function that performs the action.
diff --git a/docs/device_automation_condition.md b/docs/device_automation_condition.md
index f183ee15a..92e87a5ce 100644
--- a/docs/device_automation_condition.md
+++ b/docs/device_automation_condition.md
@@ -3,6 +3,10 @@ title: "Device conditions"
 sidebar_label: Conditions
 ---
 
+:::warning
+We are currently exploring alternatives to device automations. Existing device automations will continue to work but new device automations won't be accepted.
+:::
+
 Device conditions allow a user to check if a certain condition is met. Examples are is a light on or is the floor wet.
 
 Device conditions are defined as dictionaries. These dictionaries are created by your integration and are passed to your integration to create a function that checks the condition.
diff --git a/docs/device_automation_index.md b/docs/device_automation_index.md
index 67b592a3d..a63b89720 100644
--- a/docs/device_automation_index.md
+++ b/docs/device_automation_index.md
@@ -3,6 +3,10 @@ title: "Device automations"
 sidebar_label: Introduction
 ---
 
+:::warning
+We are currently exploring alternatives to device automations. Existing device automations will continue to work but new device automations won't be accepted.
+:::
+
 Device Automations provide users with a device-centric layer on top of the core concepts of Home Assistant. When creating automations, users no longer have to deal with core concepts like states and events. Instead, they will be able to pick a device and then pick from a list of pre-defined triggers, conditions and actions.
 
 Integrations can hook into this system by exposing functions to generate the pre-defined triggers, conditions, actions and having functions that can listen for the triggers, check the condition and execute the action.
diff --git a/docs/device_automation_trigger.md b/docs/device_automation_trigger.md
index 0ff1f6531..ae49ea5b0 100644
--- a/docs/device_automation_trigger.md
+++ b/docs/device_automation_trigger.md
@@ -3,6 +3,10 @@ title: "Device triggers"
 sidebar_label: Triggers
 ---
 
+:::warning
+We are currently exploring alternatives to device automations. Existing device automations will continue to work but new device automations won't be accepted.
+:::
+
 Device triggers are automation triggers that are tied to a specific device and an event or state change. Examples are "light turned on" or "water detected".
 
 Device triggers can be provided by the integration that provides the device (e.g. ZHA, deCONZ) or the entity integrations that the device has entities with (e.g. light, switch). An example of the former is events not tied to an entity e.g. key press on a remote control or touch panel, while an example of the latter could be that a light has been turned on.