From e90744910612750e1d98d86e42e265dfaf06878d Mon Sep 17 00:00:00 2001 From: HomeSpan Date: Mon, 14 Jun 2021 05:34:04 -0500 Subject: [PATCH] Update CLI.md --- docs/CLI.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/CLI.md b/docs/CLI.md index 9460cdb..5510d42 100644 --- a/docs/CLI.md +++ b/docs/CLI.md @@ -59,8 +59,8 @@ In addition to listening for incoming HAP requests, HomeSpan also continuously p * **A** - start the HomeSpan Setup Access Point * This command starts HomeSpan's temporary Access Point, which provides users with an alternate methods for configuring a device's WiFi Credentials and HomeKit Setup Code. Starting the Access Point with this command is identical to starting it via the Control Button. See the [HomeSpan User Guide](UserGuide.md) for complete details. -* **V** - delete value settings for all saved Characteristics - * The state of Characteristics can be saved in the device's NVS for restoration if the power cycles. This command is used to delete all saved data and is useful to run in the event saved Characteristics become out-of-sync with their stored values during the development phase of your sketch when you are adding new Accessories, Services, and Characteristics. +* **V** - erases the values of any saved Characteristics + * As Characteristics are updated via the Home App, their latest values can be (optionally) saved in the device's non-volatile storage (NVS). If the device should ever lose power this allows HomeSpan to restore the latest values of saved Characteristic upon the next start-up. Typing 'V' from the CLI deletes all previously-saved Characteristic values from the NVS, though it does not alter the current values of those Characteristics. This is useful in the event that saved Characteristics become out-of-sync with their stored values during the development phase of your sketch when adding, deleting, and changing the configuration of new Accessories, Services, and Characteristics. * **U** - unpair device by deleting all Controller data * This deletes all data stored about Controllers that have been paired with the device, which forces HomeSpan to reset its internal state to unpaired. Normally, unpairing is done by HomeKit at the direction of an end-user via the Home App on an iPhone. However, HomeKit requests to unpair a device are not subject to any confirmation from that device. HomeKit simply assumes that once it requests a device to unpair, the device has received the message and has reset its pairing state accordingly. In the event that HomeKit unpairs a HomeSpan device, but the device does not receive or properly process the request, its pairing status will be out of sync with HomeKit. Forcing HomeKit to reset its internal state to unpaired using this command resolves the issue and allows HomeSpan to be re-paired with HomeKit.