Docs(schlage): Add door code management actions

Adds documentation for new actions to manage door codes on Schlage
locks.

Signed-off-by: Andrew Grimberg <[email protected]>

Author: tykeal

source/_integrations/schlage.markdown

@@ -69,6 +69,98 @@ Once you have enabled the Schlage integration, you should see the following swit
 - **1-Touch Locking** - When enabled, locks the lock with a press of the Schlage button.
 - **Keypress Beep** - Controls whether the lock will emit beeping tones on use.
 
+## Actions
+
+### Action schlage.get_codes
+
+You can use the `schlage.get_codes` action to retrieve the codes stored on the lock(s). The codes will be returned as a object with all codes under the lock entity_id.
+
+{% details "Create event action details" %}
+
+| Data attribute | Optional | Description | Example |
+| ---------------------- | -------- | ----------- | --------|
+| `entity_id` | no | Lock entity to use (one or more) | `lock.front_door` |
+
+{% raw %}
+
+```yaml
+# Example action
+action: schlage.get_codes
+data:
+  entity_id:
+    - lock.front_door
+```
+
+The returned codes will be in the following format:
+
+```yaml
+lock.test_lab:
+  93ab517c-0000-0000-0000-000000000000:
+    name: Example Person
+    code: "3333"
+  82958b77-0000-0000-0000-000000000000:
+    name: Example person 2
+    code: "2222"
+```
+
+{% endraw %}
+
+{% enddetails %}
+
+### Action schlage.add_code
+
+You can use the `schlage.add_code` action to add a new code to the lock(s). The code must be between 4 and 8 digits long. Calling `schlage.get_codes` may not immediately return the code as the lock coordinator must poll for updates.
+
+{% details "Create event action details" %}
+
+| Data attribute | Optional | Description | Example |
+| ---------------------- | -------- | ----------- | --------|
+| `entity_id` | no | Lock entity to use (one or more) | `lock.front_door` |
+| `name` | no | Name for the code | `Example Person` |
+| `code` | no | Code to add (4-8 digits) | `3333` |
+
+{% raw %}
+
+```yaml
+# Example action
+action: schlage.add_code
+data:
+  entity_id:
+    - lock.front_door
+  name: Example Person
+  code: "3333"
+```
+
+{% endraw %}
+
+{% enddetails %}
+
+### Action schlage.delete_code
+
+You can use the `schlage.delete_code` action to delete a code from the lock(s). Calling `schlage.get_codes` may not immediately reflect the deletion as the lock coordinator must poll for updates.
+
+{% details "Create event action details" %}
+
+| Data attribute | Optional | Description | Example |
+| ---------------------- | -------- | ----------- | --------|
+| `entity_id` | no | Lock entity to use (one or more) | `lock.front_door` |
+| `name` | no | Name for the code to delete. The name evaluation for deletion is case insensitive | `Example Person` |
+
+{% raw %}
+
+```yaml
+# Example action
+action: schlage.delete_code
+data:
+  entity_id:
+    - lock.front_door
+  name: Example Person
+```
+
+{% endraw %}
+
+{% enddetails %}
+
 ## Removing the integration
 
 This integration follows standard integration removal. No extra steps are required.