diff --git a/source/_posts/2022-04-06-release-20224.markdown b/source/_posts/2022-04-06-release-20224.markdown
index edba0d88493..27556d0b8ff 100644
--- a/source/_posts/2022-04-06-release-20224.markdown
+++ b/source/_posts/2022-04-06-release-20224.markdown
@@ -248,18 +248,23 @@ You can find the backup dashboard in the configuration menu.
## Testing your automation conditions
-Last release we added a small feature to see if the automation you are
-creating, triggers correctly. During the release livestream of that release
-we got questions: Can this be done for conditions too?
+In our previous release we [added a feature][triggered] to see if the automation
+you create triggers correctly. During the release party live stream,
+we got questions: _"Can this be done for conditions too?"_; Sure we can!
-Sure we can!
+
+
+Every condition now has a little test button, testing if the condition passes right now.
+
-TODO: Insert screenrecording.
+Additionally, the “triggered” bar got an additional feature too! You can click
+on it to get a raw view of all trigger variable data if it shows. This data
+can be helpful in case you want to create an advanced condition or template
+using that information.
-Additionally, the "triggered" bar got an additional feature to! If it shows,
-you can click on it, to get a raw view of all trigger data.
+
-TODO: Insert screenshot
+[triggered]: /blog/2022/03/02/release-20223/#triggered
## Zones now have a state!
diff --git a/source/images/blog/2022-04/test-condition.gif b/source/images/blog/2022-04/test-condition.gif
new file mode 100644
index 00000000000..ba0fce9cadb
Binary files /dev/null and b/source/images/blog/2022-04/test-condition.gif differ
diff --git a/source/images/blog/2022-04/triggered-variables.png b/source/images/blog/2022-04/triggered-variables.png
new file mode 100644
index 00000000000..eabb4988613
Binary files /dev/null and b/source/images/blog/2022-04/triggered-variables.png differ