diff --git a/source/_docs/blueprint/tutorial.markdown b/source/_docs/blueprint/tutorial.markdown
index 3af7bb7954e..512efe3d262 100644
--- a/source/_docs/blueprint/tutorial.markdown
+++ b/source/_docs/blueprint/tutorial.markdown
@@ -177,15 +177,17 @@ blueprint:
       description: This sensor will be synchronized with the light.
       selector:
         entity:
-          domain: binary_sensor
-          device_class: motion
+          filter:
+            - domain: binary_sensor
+            - device_class: motion
     target_light:
       name: Lights
       description: The lights to keep in sync.
       selector:
         target:
           entity:
-            domain: light
+            filter:
+              - domain: light
 ```
 
 By limiting our blueprint to working with lights and motion sensors, we unlock a couple of benefits: the UI will be able to limit suggested values to lights and motion sensors instead of all devices. It will also allow the user to pick an area to control the lights in.
@@ -207,15 +209,17 @@ blueprint:
       description: This sensor will be synchronized with the light.
       selector:
         entity:
-          domain: binary_sensor
-          device_class: motion
+          filter:
+            - domain: binary_sensor
+            - device_class: motion
     target_light:
       name: Lights
       description: The lights to keep in sync.
       selector:
         target:
           entity:
-            domain: light
+            filter:
+              - domain: light
 
 trigger:
   - platform: state
@@ -282,4 +286,4 @@ If you follow the [Rules and format for posting](/get-blueprints), you can share
 - [Blueprint selectors](/docs/blueprint/selectors/)
 - [Blueprint schema](/docs/blueprint/schema/)
 - [About blueprints](/docs/blueprint/)
-- [Using automation blueprints](/docs/automation/using_blueprints/)
\ No newline at end of file
+- [Using automation blueprints](/docs/automation/using_blueprints/)