From 1ad5cb32630bc067ad89d0f29c1543b349ad3c04 Mon Sep 17 00:00:00 2001 From: Philip Abbey Date: Thu, 24 Jul 2025 11:01:01 +0100 Subject: [PATCH] Update Wi-Fi.md Co-authored-by: Vincent <59287019+vincentezw@users.noreply.github.com> Signed-off-by: Philip Abbey --- Wi-Fi.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Wi-Fi.md b/Wi-Fi.md index 1ce4b51..5628a43 100644 --- a/Wi-Fi.md +++ b/Wi-Fi.md @@ -8,7 +8,7 @@ With version 3.0 onwards the application now includes the ability to temporarily ## Limits of Use -1. An API request issued over Wi-Fi requires the watch to open up an IP connection to your Wi-Fi access point. This means setting up a secure channel with WPA and being allocated an IP address. Establishing the communication channel takes a short while. _You will see that this adds a noticeable delay to useability._ +1. An API request issued over Wi-Fi requires the watch to open up an IP connection to your Wi-Fi access point. This means setting up a secure channel with WPA and being allocated an IP address. Establishing the communication channel takes a short while. _You will see that this adds a noticeable delay to usability._ 2. **This new function can only be used when the menu is already cached.** _The watch will not perform an HTTPS GET request to retrieve the JSON menu file_. You will not be able to turn on the Wi-Fi/LTE connection option in the application settings if the menu is not cached (or at least set to be cached in due course).