Adding entry for update config (#5374)

* Adding entry for update config * ✏️ Minor typo tweak
2025-07-13 04:16:48 +00:00 · 2018-05-16 19:12:17 +01:00 · 2018-05-16 19:12:17 +01:00 · 6e1b48dd7b
commit 6e1b48dd7b
parent 1b3b6a1cae
1 changed files with 1 additions and 0 deletions
--- a/source/_docs/z-wave/services.markdown
+++ b/source/_docs/z-wave/services.markdown
@ -35,6 +35,7 @@ The `zwave` component exposes multiple services to help maintain the network. Al
 | stop_network           | Stops the Z-Wave network.                                                                                                                    |
 | test_network           | Tells the controller to send no-op commands to each node and measure the time for a response. In theory, this can also bring back nodes which have been marked "presumed dead."             |
 | test_node              | Tells the controller to send no-op command(s) to a specific node. Requires `node_id` field. You can specify amount of test_messages to send by specifying it with `messages` field. In theory, this could bring back nodes marked as "presumed dead"
+| update_config          | Attempt to update OZW configuration files from git to support newer devices |

 The `soft_reset` and `heal_network` commands can be used as part of an automation script to help keep a Z-Wave network running reliably as shown in the example below. By default, Home Assistant will run a `heal_network` at midnight. This is a configuration option for the `zwave` component. The option defaults to `true` but can be disabled by setting `autoheal` to false. If you're having issues with your Z-Wave network, try disabling this automation.