2025 09 bug fixes (#285 )

Three bug fixes. 1. Fixed a bug where templates failed to display in toggle menu items (at least on some devices). 2. Fixed a bug where a menu item requesting to exit on completion appeared to indicate failure when using Wi-Fi or LTE. The fix uses a delay in exiting the application modelled as sufficient for a Venu 2 device, so this might need tweaking for other devices. Closes #283. 3. Attempt to fixed an "Out of Memory" bug caused by v3.3 by making automatic checking for menu updates both optional and automatically turned off when insufficient memory is available. This last bug is device dependent and may require another attempt. Closes #284.
Cosmetic change to docs
2025-09-15 13:31:31 +00:00 · 2025-09-13 20:09:26 +01:00 · 2025-09-13 20:06:10 +01:00 · 2025-09-13 12:05:49 +01:00 · 2025-09-13 11:06:29 +01:00 · 2025-09-12 14:34:16 +01:00
51 changed files with 287 additions and 103 deletions
--- a/HISTORY.md
+++ b/HISTORY.md
@@ -9,14 +9,14 @@
 |   1.2   | Do not crash on zero items to update. Report unreachable URLs. Verify API URL does not have a trailing slash '/'. Increased HTTP response diagnosis. Reduced minimum API Level required from 3.3.0 to 3.1.0 to allow more device "part numbers" to be satisfied. |
 |   1.3   | Tap for scripts was working in emulation but not on some phones. Decision is to make the 'service' field in the JSON compulsory for 'tap' menu items. This is a breaking change, but for many might be a fix for something not working correctly. Improve language support, we can now accept language corrections and prevent the automated translation of strings from clobbering manually refined entries. Thank you to two new contributors. |
 |   1.4   | New lean user Interface with thanks to [Someone0nEarth](https://github.com/Someone0nEarth) for their contribution which is now the default. If you prefer the old style you can still select it in the settings. The provision of a 'service' tag is now not just heavily suggested by the JSON schema, it is enforced in code. With apologies to anyone suffering a breakage as a result. |
-|   1.5   | <img src="images/confirmation_view.png" width="200" title="Confirmation View"/><br/>Added an optional confirmation dialogue view to prevent accidental execution of actions on mistaken tap. This also brings a change in the JSON schema to allow an optional field to specify that the confirmation should be used for a menu item. As we are now maturing and adding features we have decided to mitigate breaking changes to the JSON schema by being more careful to adopt the Home Assistant schema (noting there is a 1:1 mapping between YAML and JSON). This change does deprecate the top level `service` tag in favour of `tag_action` containing multiple fields including `service` & `confirm`. Users should migrate to the new format for the new functionality, but the timescale for actual deprecation are long and undecided. |
+|   1.5   | <img src="images/confirmation_view.png" width="200" title="Confirmation View"/><br/>Added an optional confirmation dialogue view to prevent accidental execution of actions on mistaken tap. This also brings a change in the JSON schema to allow an optional field to specify that the confirmation should be used for a menu item. As we are now maturing and adding features we have decided to mitigate breaking changes to the JSON schema by being more careful to adopt the HomeAssistant schema (noting there is a 1:1 mapping between YAML and JSON). This change does deprecate the top level `service` tag in favour of `tag_action` containing multiple fields including `service` & `confirm`. Users should migrate to the new format for the new functionality, but the timescale for actual deprecation are long and undecided. |
 |   1.6   | Added a user configurable 'timeout' in seconds so that when no action is taken the application automatically closes, stopping the continuous polling for changes of status and hence saving the drain on the battery. This can be disabled with timeout=0. |
 |   1.7   | Added timeout to confirmation views so that when used for security devices it does not linger when left unconfirmed. Thanks to [Jan Schneider](https://github.com/j-a-n) for the contribution. Known bug for devices not supporting [`WatchUi.getCurrentView()`](https://developer.garmin.com/connect-iq/api-docs/Toybox/WatchUi.html#getCurrentView-instance_function) API call which is only available on API Level 3.4.0, e.g. Vivoactive 4S. |
 |   2.0   | A significant code base change to enable both a 'widget' version for older devices, e.g. Venu (1), and an application with a glance, e.g. Venu2. These two versions must now be distributed under separate application IDs, but they have the same code base. A further 20 more devices are now supported, the settings have been internationalised, and there's a bug fix for older devices when trying to display a helpful error message but instead the application crashed. This version has come from a significant collaboration with [Someone0nEarth](https://github.com/Someone0nEarth). |
-|   2.1   | Deployment of an idea to provide Home Assistant with access to the watch battery level. Using this requires [significant setup](BackgroundService.md) on the Home Assistant configuration and hence is detailed separately. Due to this, the default state for this battery option is _off_. Changed the application settings user interface to be more intuitive, and hence amended the way settings are managed in the background. |
+|   2.1   | Deployment of an idea to provide HomeAssistant with access to the watch battery level. Using this requires [significant setup](BackgroundService.md) on the HomeAssistant configuration and hence is detailed separately. Due to this, the default state for this battery option is _off_. Changed the application settings user interface to be more intuitive, and hence amended the way settings are managed in the background. |
 |   2.2   | Adds a feature to cache the menu configuration and save the time taken for an HTTP request to fetch it. You as the user are responsible for managing the cache by clearing it when you update your configuration. Improvement to widget root display updates. Bug fix for battery level reporting when in the glance carousel. Fixed an uninternationalised string, "Execute". Unfixed issue with battery level updates when the user is not an administrator. |
-|   2.3   | Fix for battery level updates where previously the function only worked for administrator accounts. The new solution is based on Webhooks and is simpler to implement on Home Assistant. Language support fix where an automatic translation produced an inappropriate word, possibly in more than one language. |
-|   2.4   | Sensor status reporting via Home Assistant 'templates'. This provides a generalised way of viewing the status of any entity as long as the result can be rendered as text, e.g. 'uncovered', 'open', '76%', '21 °C'. Removal of the menu style option. The original style was kept after the introduction of the icon style solely to keep the code for a possible re-use for sensor statuses. This version delivers that new feature, hence the style option has been removed. The new JSON configuration file format allows for the old style to be replicated if you are desperate! Added a feature to provide parameters to actions (`tap` or `template`). Added a feature to confirm `toggle` menu items. |
+|   2.3   | Fix for battery level updates where previously the function only worked for administrator accounts. The new solution is based on Webhooks and is simpler to implement on HomeAssistant. Language support fix where an automatic translation produced an inappropriate word, possibly in more than one language. |
+|   2.4   | Sensor status reporting via HomeAssistant 'templates'. This provides a generalised way of viewing the status of any entity as long as the result can be rendered as text, e.g. 'uncovered', 'open', '76%', '21 °C'. Removal of the menu style option. The original style was kept after the introduction of the icon style solely to keep the code for a possible re-use for sensor statuses. This version delivers that new feature, hence the style option has been removed. The new JSON configuration file format allows for the old style to be replicated if you are desperate! Added a feature to provide parameters to actions (`tap` or `template`). Added a feature to confirm `toggle` menu items. |
 |   2.5   | A small memory efficiency of about 1kB by removing `RezStrings.mc`. This will aid widgets on old watches that only have 60kB available to an application and are using about 45kB before the menu is fetched, hence 1kB is more significant to those devices. |
 |   2.6   | Added more information reporting to the background service, in addition to the device battery level and charging status, we now include location, location accuracy, and (if supported by your device) the activity information. Note the updates are sent periodically and are not event driven. |
 |   2.7   | Bug fix release: 1. Handling a settings change, 2. Avoid caching a bad menu, 3. Managing bad JSON in menu definitions. |
@@ -46,6 +46,7 @@
 |   2.31  | Adding [two new options](./examples/Actions.md#exit-on-tap) to the menu items: 1) The ability to disable a menu item, e.g. temporarily for seasonal changes, 2) The option to exit after a menu item has been select. |
 |   2.32  | Bug fix for a breaking change extracting options caused by the need to rearrange function parameters for an [annoying compiler error](https://github.com/house-of-abbey/GarminHomeAssistant/issues/253). |
 |   3.0   | First version with the ability to use [Wi-Fi or LTE](Wi-Fi.md) instead of Bluetooth but with limited functionality, thanks to [@vincentezw](https://github.com/vincentezw). |
-|   3.1   | Added the ability for users to provide [custom HTTP headers](HTTP_Headers.md) for their Home Assistant server. Improved German language translations. Thanks to [@tispokes](https://github.com/tispokes) for assisting with both of those. Removed all groups in settings as the SDK is buggy. Fixed a bug with templates in glances causing application crash on startup. |
-|   3.2   | Only enable or disable sensors on Home Assistant when the background service options is changed, i.e. do not call the API to enable on start up every time. |
+|   3.1   | Added the ability for users to provide [custom HTTP headers](HTTP_Headers.md) for their HomeAssistant server. Improved German language translations. Thanks to [@tispokes](https://github.com/tispokes) for assisting with both of those. Removed all groups in settings as the SDK is buggy. Fixed a bug with templates in glances causing application crash on startup. |
+|   3.2   | Only enable or disable sensors on HomeAssistant when the background service options is changed, i.e. do not call the API to enable on start up every time. |
 |   3.3   | Providing automatic detection for menu definition updates, but still requires an application restart. |
+|   3.4   | Fixed a bug where templates failed to display in toggle menu items (at least on some devices). Fixed a bug where a menu item requesting to exit on completion appeared to indicate failure when using Wi-Fi or LTE. The fix uses a delay in exiting the application modelled as sufficient for a Venu 2 device, so this might need tweaking for other devices. Attempt to fixed an "Out of Memory" bug caused by v3.3 by making automatic checking for menu updates both optional and automatically turned off when insufficient memory is available. This last bug is device dependent and may require another attempt. |
--- a/README.md
+++ b/README.md
@@ -4,24 +4,24 @@

 <img src="images/Actual_Venu2_Theme.jpg" width="200" title="Venu 2"/>

-A Garmin application to provide a "dashboard" to control your devices via [Home Assistant](https://www.home-assistant.io/). The application will never be as fully fledged as a Home Assistant dashboard, so it is designed to be good enough for the simple and essential things. Those things that can be activated via an on/off toggle or a tap. That should cover lights, switches, and anything requiring a single press such as an automation. For anything more complicated, e.g. thermostat, it would always be quicker and simpler to reach for your phone or tablet... or the device's own remote control!
+A Garmin application to provide a "dashboard" to control your devices via [HomeAssistant](https://www.home-assistant.io/). The application will never be as fully fledged as a HomeAssistant dashboard, so it is designed to be good enough for the simple and essential things. Those things that can be activated via an on/off toggle or a tap. That should cover lights, switches, and anything requiring a single press such as an automation. For anything more complicated, e.g. thermostat, it would always be quicker and simpler to reach for your phone or tablet... or the device's own remote control!

-The application is designed around a simple scrollable menu where menu items have been extended to interface with the [Home Assistant API](https://developers.home-assistant.io/docs/api/rest/), e.g. to get the status of switches or lights for display on the `toggle` menu item, or a text status for an entity (`info` item). It is possible to nest menus, so there is a menu item to open a sub-menu. This can be arbitrarily deep and nested in the format of a tree of items, although you need to consider if reaching for your phone becomes quicker to select the device what you want to control.
+The application is designed around a simple scrollable menu where menu items have been extended to interface with the [HomeAssistant API](https://developers.home-assistant.io/docs/api/rest/), e.g. to get the status of switches or lights for display on the `toggle` menu item, or a text status for an entity (`info` item). It is possible to nest menus, so there is a menu item to open a sub-menu. This can be arbitrarily deep and nested in the format of a tree of items, although you need to consider if reaching for your phone becomes quicker to select the device what you want to control.

-**The intended audience for this application are those comfortable with configuring a Home Assistant** (e.g. editing the YAML configuration files) and debugging why URLs don't work. It does not require programming skills, but the menu is configured via JSON which feels like "coding" (more like "describing"). If you are not comfortable with this relatively low level of configuration, you may like to try other Garmin applications instead.
+**The intended audience for this application are those comfortable with configuring a HomeAssistant** (e.g. editing the YAML configuration files) and debugging why URLs don't work. It does not require programming skills, but the menu is configured via JSON which feels like "coding" (more like "describing"). If you are not comfortable with this relatively low level of configuration, you may like to try other Garmin applications instead.

 **If you are struggling with getting the application to work, please consult the [troubleshooting guide](TroubleShooting.md#menu-configuration-url) first.**

 ## No HTTPS?

 > [!IMPORTANT]
-> The Garmin SDK allows HTTP requests only to a limited number of domains specified in their app. Therefore, for your Garmin to communicate with your Home Assistant instance, your Home Assistant instance must be accessible via HTTPS (with a public certificate!) or through a local DNS server that overrides one of the whitelisted domains to communicate using HTTP.
+> The Garmin SDK allows HTTP requests only to a limited number of domains specified in their app. Therefore, for your Garmin to communicate with your HomeAssistant instance, your HomeAssistant instance must be accessible via HTTPS (with a public certificate!) or through a local DNS server that overrides one of the whitelisted domains to communicate using HTTP.
 >
 >New with version 3.1, you can use [Cloudflared](https://github.com/brenner-tobias/addon-cloudflared) plug-in in combination with a [custom HTTP header](HTTP_Headers.md) and do not need a public certificate for HTTPS.
 >
-> To make your Home Assistant instance accessible via HTTPS, you will need a public certificate. You can get one for free from [Let's Encrypt](https://letsencrypt.org/) or you can pay for [Home Assistant cloud](https://www.nabucasa.com/). (You can install a local [Nginx proxy server](https://my.home-assistant.io/redirect/supervisor_addon/?addon=a0d7b954_nginxproxymanager) to manage Let's Encrypt certificates.)
+> To make your HomeAssistant instance accessible via HTTPS, you will need a public certificate. You can get one for free from [Let's Encrypt](https://letsencrypt.org/) or you can pay for [HomeAssistant cloud](https://www.nabucasa.com/). (You can install a local [Nginx proxy server](https://my.home-assistant.io/redirect/supervisor_addon/?addon=a0d7b954_nginxproxymanager) to manage Let's Encrypt certificates.)
 >
-> If you use a local DNS server (like [Pi-Hole](https://pi-hole.net/)), you can create a local DNS record for the domain `garmincdn.com` (which is allowed for HTTP in the Garmin SDK) and map it to your Home Assistant instance's IP. "_[About Communication Between Garmin SDK and a Raspberry Pi](https://www.instructables.com/About-Communication-Between-Garmin-SDK-and-a-Raspb/)_" provides additional workarounds for HTTP request restrictions in the Garmin SDK.
+> If you use a local DNS server (like [Pi-Hole](https://pi-hole.net/)), you can create a local DNS record for the domain `garmincdn.com` (which is allowed for HTTP in the Garmin SDK) and map it to your HomeAssistant instance's IP. "_[About Communication Between Garmin SDK and a Raspberry Pi](https://www.instructables.com/About-Communication-Between-Garmin-SDK-and-a-Raspb/)_" provides additional workarounds for HTTP request restrictions in the Garmin SDK.
 >
 > **No support is offered to those circumventing the HTTPS restriction of the Connect IQ SDK.** You are supporting yourself!

@@ -56,13 +56,13 @@ The following table lists the differences in functionality between the two. The

 ## Dashboard Definition

-Setup for this menu is more complicated than the Connect IQ settings menu really allows you to specify. In order to make the dashboard easily configurable and easy to change, we have provided an external mechanism for specifying the menu layout, a JSON file you write, retrieved from a URL you specify. JSON was chosen over YAML because Garmin can parse JSON HTTP GET responses into its own internal dictionary, it cannot parse YAML, hence a choice of one really. Note that JSON and YAML are essentially a 1:1 format mapping except JSON does not have comments. We recommend you take advantage of [Home Assistant's own web server](https://www.home-assistant.io/integrations/http/#hosting-files) to provide the JSON definition. The advantages of this are:
+Setup for this menu is more complicated than the Connect IQ settings menu really allows you to specify. In order to make the dashboard easily configurable and easy to change, we have provided an external mechanism for specifying the menu layout, a JSON file you write, retrieved from a URL you specify. JSON was chosen over YAML because Garmin can parse JSON HTTP GET responses into its own internal dictionary, it cannot parse YAML, hence a choice of one really. Note that JSON and YAML are essentially a 1:1 format mapping except JSON does not have comments. We recommend you take advantage of [HomeAssistant's own web server](https://www.home-assistant.io/integrations/http/#hosting-files) to provide the JSON definition. The advantages of this are:

-1. the file is as public as you make your Home Assistant,
-2. the file is editable within Home Assistant via "[Studio Code Server](https://my.home-assistant.io/redirect/supervisor_addon/?addon=a0d7b954_vscode)", and
+1. the file is as public as you make your HomeAssistant,
+2. the file is editable within HomeAssistant via "[Studio Code Server](https://my.home-assistant.io/redirect/supervisor_addon/?addon=a0d7b954_vscode)", and
 3. the schema is verifiable using [JSON Schema](https://json-schema.org/overview/what-is-jsonschema).

-We have used `/config/www/garmin/<something>.json` on our home brew Home Assistant's file system. That equates to a URL of `https://homeassistant.local/local/garmin/<something>.json`.
+We have used `/config/www/garmin/<something>.json` on our home brew HomeAssistant's file system. That equates to a URL of `https://homeassistant.local/local/garmin/<something>.json`.

 > [!IMPORTANT]
 > However [recent reports](https://community.home-assistant.io/t/www-folder-location-for-local-documents/24903/16) suggest this path may no longer work on [Nabu Casa](https://www.nabucasa.com/) and you should use `/homeassistant/www/` instead of `/config/www/`. We are unable to verify this since our free trial of Nabu Casa has expired.
@@ -160,7 +160,7 @@ The example above illustrates how to configure:
 * You can also display the status of devices (`info`) which is essentially a `tap` with no action
 * All menu items can display the results of evaluating [templates](examples/Templates.md).

-The following table indicates how Home Assistant entity types can map to the Garmin applications menu types. Presently, an automation is the only one that can be either a `tap` or a `toggle`.
+The following table indicates how HomeAssistant entity types can map to the Garmin applications menu types. Presently, an automation is the only one that can be either a `tap` or a `toggle`.

 | HA Entity Type   | Tap | Toggle | Info (status)|
 |------------------|:---:|:------:|:------------:|
@@ -178,7 +178,7 @@ Multiple templates are evaluated in a single HTTP request to update their status

 You can now specify alternative texts to use instead of "On" and "Off", e.g. "Locked" and "Unlocked" or "Open" and "Closed" through the use of a [template menu item](examples/Templates.md). But wouldn't having locks operated from your watch be a security concern ;-) ?

-The [schema](https://raw.githubusercontent.com/house-of-abbey/GarminHomeAssistant/main/config.schema.json) is checked by using a URL directly back to this GitHub source repository, so you do not need to install that file. You can just copy & paste your entity names from the YAML configuration files used to configure Home Assistant. With a submenu, there's a difference between `title` and `name`. The `name` goes on the menu item, and the `title` at the head of the submenu. If your dashboard definition fails to meet the schema, the application will simply drop items with the wrong field names without warning to protect itself.
+The [schema](https://raw.githubusercontent.com/house-of-abbey/GarminHomeAssistant/main/config.schema.json) is checked by using a URL directly back to this GitHub source repository, so you do not need to install that file. You can just copy & paste your entity names from the YAML configuration files used to configure HomeAssistant. With a submenu, there's a difference between `title` and `name`. The `name` goes on the menu item, and the `title` at the head of the submenu. If your dashboard definition fails to meet the schema, the application will simply drop items with the wrong field names without warning to protect itself.

 ### Old deprecated format

@@ -206,7 +206,7 @@ The above should be replaced by the following:
    }
 ```

-This allows the `confirm` and `pin` fields to be accommodated in the `tap_action` along side the `service` tag, and follows the Home Assistant YAML format more closely.
+This allows the `confirm` and `pin` fields to be accommodated in the `tap_action` along side the `service` tag, and follows the HomeAssistant YAML format more closely.

 ### More Examples

@@ -217,8 +217,8 @@ This allows the `confirm` and `pin` fields to be accommodated in the `tap_action
 ## Editing the JSON file

 You have options. The first is what we use.
-1. **Best!**  Use the GarminHomeAssistant [Web-based Editor](https://house-of-abbey.github.io/GarminHomeAssistant/web/) which includes `entity` and `service` name completion and validation by fetching data from your own Home Assistant instance. _Pretty  nifty eh?_ The other method listed below do not add this convenience and checking.
-2. Use the [Studio Code Server](https://community.home-assistant.io/t/home-assistant-community-add-on-visual-studio-code/107863) addon for Home Assistant. You can then edit your JSON file in place.
+1. **Best!**  Use the GarminHomeAssistant [Web-based Editor](https://house-of-abbey.github.io/GarminHomeAssistant/web/) which includes `entity` and `service` name completion and validation by fetching data from your own HomeAssistant instance. _Pretty  nifty eh?_ The other method listed below do not add this convenience and checking.
+2. Use the [Studio Code Server](https://community.home-assistant.io/t/home-assistant-community-add-on-visual-studio-code/107863) addon for HomeAssistant. You can then edit your JSON file in place.
 3. Locally installed VSCode, or if not installed, try
 4. The on-line version at https://vscode.dev/, which works really well.

@@ -232,7 +232,7 @@ Make sure you can browse to the URL of your JSON file in a standard web browser

 ## API Key Creation

-Having created your JSON definition for your dashboard, you need to create an API key for your personal account on Home Assistant. You will need a [Long-Lived Access Token](https://developers.home-assistant.io/docs/auth_api/#long-lived-access-token). This is not obvious to find and is bound to your own Home Assistant account. Follow the menu sequence: `HA -> User Profile -> "Security" tab -> Long-lived access tokens`. Make sure you save the generated token before dismissing it.
+Having created your JSON definition for your dashboard, you need to create an API key for your personal account on HomeAssistant. You will need a [Long-Lived Access Token](https://developers.home-assistant.io/docs/auth_api/#long-lived-access-token). This is not obvious to find and is bound to your own HomeAssistant account. Follow the menu sequence: `HA -> User Profile -> "Security" tab -> Long-lived access tokens`. Make sure you save the generated token before dismissing it.

 ![Long-Lived Access Token](images/Long_Lived_Access_Tokens.png)

@@ -240,7 +240,7 @@ Having created that token, before you dismiss the dialogue box with the value yo

 ## API URL

-If you are using [Nabu Casa](https://www.nabucasa.com/) then your Cloud API URL can be found by looking up your URL via `HA -> Settings -> Home Assistant Cloud -> Remote Control -> Nabu Casa URL` and don't forget to add `/api` to the end of the copied string.
+If you are using [Nabu Casa](https://www.nabucasa.com/) then your Cloud API URL can be found by looking up your URL via `HA -> Settings -> HomeAssistant Cloud -> Remote Control -> Nabu Casa URL` and don't forget to add `/api` to the end of the copied string.

 ![Nabu Casa Remote Control](images/Nabu_Casa_Remote_Control.png)

@@ -255,19 +255,34 @@ Unfortunately the Settings dialogue box in the Garmin IQ application "times out"
 <img src="images/GarminHomeAssistantSettings.png" width="400" title="Application Settings"/>

 1. Copy and paste your API key you've just created into the top field.
-2. Add the URL for your Home Assistant API, e.g. `https://<homeassistant>/api`. (No trailing slash `/`` character as one gets appended when creating the URL and you do not want two.)
+2. Add the URL for your HomeAssistant API, e.g. `https://<homeassistant>/api`. (No trailing slash `/`` character as one gets appended when creating the URL and you do not want two.)
 3. Add the URL of your JSON file, e.g. `https://<homeassistant>/local/garmin/<something>.json`.

-You should now have a working application on your watch and be able to operate your Home Assistant devices for as long as your watch is within Bluetooth range of your phone.
+You should now have a working application on your watch and be able to operate your HomeAssistant devices for as long as your watch is within Bluetooth range of your phone.

-You may choose to cache your menu definition on your device in order to reduce the delay in showing the menu (as it saves waiting for an HTTP GET request). If you use this option you need to be aware of hwo updates to the menu are managed. You may either:
+### Changes to the (JSON) Dashboard Definition & Caching
+
+Without caching enabled, when you change the JSON file defining your dashboard, you must exit the application and the reopen it. It only takes a matter of a few seconds to pick up the new definition.
+
+You may choose to cache your menu definition on your device in order to reduce the delay in showing the menu (as it saves waiting for an HTTP GET request). If you use this option you need to be aware of how updates to the menu are managed. You may either:

 1. **Choose to have the cache cleared.** The toggle option below the cache option allows you to choose to refresh the cache the next time the application starts. Once the cache has been cleared, the application will reset this toggle for you, so you do not need to return to the settings to amend it.
-2. **Let the application retrieve the menu after starting and setting up the switch states** (including evaluating [templates](examples/Templates.md)), and then verify you have the latest menu. If a newer menu is retrieved you will be notified via a 'toast' or blue screen for devices without a toast in their API. You will be prompted to restart the application in order to build the menu from this latest menu definition. There are no plans to make the menu definition update recreate the rendered menu items because it could change the selected item just as you action it, and because restarting is simple for the user and simpler for the code.
+2. **Let the application retrieve the menu after starting and setting up the switch states** (including evaluating [templates](examples/Templates.md)), and then verify you have the latest menu. If a newer menu is retrieved you will be notified via a 'toast' or blue screen for devices without a toast in their API. You will be prompted to restart the application in order to build the menu from this latest menu definition. **This method has proven tricky in older devices with less memory.** Hence it can be turned off to avoid "Out of Memory" crashes. The application tries to protect against crashes by detecting insufficient memory and disabling the option (but note that this may require some tuning). Hence this option is off by default in case it causes a crash and new users are unaware of the potential cause.
+
+**Summary:** The two cache options are therefore distinct, the **first is a manual** forced refresh (the old way). The menu is refreshed on start up and no restart is required. The **second enables automatic checking** after starting and after presenting a usable menu with no extra delay but then any detected changes require a restart.
+
+Whilst it would be a smoother experience, there are no plans to make the menu definition update dynamically recreate the rendered menu items without a restart because:
+1. Re-rendering the menu could change the selected item just as you action it.
+2. V3.3 proved that older devices are now reaching their memory limits. If you have an old device with limited memory to spare you will probably find the App disables the automatic method for you. If your device crashes with this option turned on, best turn it off manually and let me know via a [Github issue](https://github.com/house-of-abbey/GarminHomeAssistant/issues). This will allow us to fine tune the conditions for insufficient memory. We will then ask you to perform a [small task to retrieve the debug information](https://developer.garmin.com/connect-iq/core-topics/debugging/) we need about memory usage.
+3. Restarting is simple for the user and simpler for the code.
+
+### Vibration

 The application uses vibration to confirm the action has been requested, which is different to the 'toast' that appears to show the action has been successfully executed. This is enabled by default but may be turned off if you do not desire this behaviour.

-The application timeout prevents the HomeAssistant App running on your watch when you have forgotten to close it. It prevents the refreshing of the menu statuses and therefore excessive wear on your battery level. For those users who prefer to keep the application open all the time for continuous use, they can reduce the battery wear by increasing the "poll delay". This inserts a user configurable number of seconds between each round of item update checks, hence reducing the API access activity. This also reduces the responsive of the statuses displayed when HA devices are switched externally, i.e. by another Home Assistant client, then the watch menu display will not update as quickly. Therefore if you only use the HomeAssistant App briefly now and then, keep this setting at the default 0 seconds. NB. To be clear, all items are updated then a configurable delay is inserted before the next round of all item updates. If your poll delay is greater than zero, then your application timeout should be set to zero, otherwise you will exit the application and negate the value of the poll delay function.
+### Power Management
+
+The application timeout prevents the HomeAssistant App running on your watch when you have forgotten to close it. It prevents the refreshing of the menu statuses and therefore excessive wear on your battery level. For those users who prefer to keep the application open all the time for continuous use, they can reduce the battery wear by increasing the "poll delay". This inserts a user configurable number of seconds between each round of item update checks, hence reducing the API access activity. This also reduces the responsive of the statuses displayed when HA devices are switched externally, i.e. by another HomeAssistant client, then the watch menu display will not update as quickly. Therefore if you only use the HomeAssistant App briefly now and then, keep this setting at the default 0 seconds. NB. To be clear, all items are updated then a configurable delay is inserted before the next round of all item updates. If your poll delay is greater than zero, then your application timeout should be set to zero, otherwise you will exit the application and negate the value of the poll delay function.

 | Application Timeout | Poll Delay | Comment |
 |:-------------------:|:----------:|:--------|
@@ -280,9 +295,13 @@ There is a second timeout value for confirmation views. This is intended for use

 The confirmation timeout is also used for the maximum time between clicks in the PIN confirmation dialog. The PIN confirmation provides a more secure alternative for toggling security-sensitive actions.

+### Text Alignment
+
 There is a toggle setting for "text alignment" that provides finer adjustment for right-to-left languages. Perhaps this could be made automatic based on device language?

-The application and widget both include a background service to report your watch's battery level and charging status. You may enable a background service to report the battery level to your Home Assistant. This is not available over your Bluetooth connection like with other Bluetooth devices as Garmin did not implement it. This no longer requires any setup, and we offer this [trouble shooting](TroubleShooting.md#watch-battery-level-reporting) guide. The last field here is readonly and allows the user to copy & paste the Webhook ID setup by the application when required for this trouble shooting guide.
+### Background Service
+
+The application and widget both include a background service to report your watch's battery level and charging status. You may enable a background service to report the battery level to your HomeAssistant. This is not available over your Bluetooth connection like with other Bluetooth devices as Garmin did not implement it. This no longer requires any setup, and we offer this [trouble shooting](TroubleShooting.md#watch-battery-level-reporting) guide. The last field here is readonly and allows the user to copy & paste the Webhook ID setup by the application when required for this trouble shooting guide.

 ## Tap Item Response

@@ -290,11 +309,11 @@ Its obvious that a toggle menu item has been triggered as the visible switch cha

 <img src="images/SimTapResponse.png" width="400" title="Tap Triggered"/>

-The application will display a 'toast' showing Home Assistant's friendly name of the triggered item. The toast will disappear after a short while if not dismissed by the user. N.B. There are reports that on the Forerunner 55 device, the toasts do not dissapear without manual intervention. On other devices like the Venu 2 the toast can take 15 seconds to dissappear if not dismissed. Unfortunately, there is no API call to change this behaviour.
+The application will display a 'toast' showing HomeAssistant's friendly name of the triggered item. The toast will disappear after a short while if not dismissed by the user. N.B. There are reports that on the Forerunner 55 device, the toasts do not dissapear without manual intervention. On other devices like the Venu 2 the toast can take 15 seconds to dissappear if not dismissed. Unfortunately, there is no API call to change this behaviour.

 ## External Device Changes

-Home Assistant will inevitably change the state of devices you are also controlling via your Garmin. The Garmin application does not maintain a web socket to listen for changes. Instead it must poll the Home Assistant API with your key. Therefore the application is not that responsive to changes. Instead there will be a delay of multiples of 100 ms per item whose status needs to be checked and amended.
+HomeAssistant will inevitably change the state of devices you are also controlling via your Garmin. The Garmin application does not maintain a web socket to listen for changes. Instead it must poll the HomeAssistant API with your key. Therefore the application is not that responsive to changes. Instead there will be a delay of multiples of 100 ms per item whose status needs to be checked and amended.

 The per toggle item delay is caused by a queue of responses to web requests. The responses fill up a buffer and in early testing we observed [`Communications.BLE_QUEUE_FULL`](https://developer.garmin.com/connect-iq/api-docs/Toybox/Communications.html) response codes.  For a Venu 2 Garmin watch an API call delay of 600 ms was found to be sustainable (500 ms was still too fast). The code now chains a sequence of updates, so as one finishes it invokes the next item's update. **The more items requiring a status update that you pack into your dashboard, the slower each individual item will be updated!**

@@ -302,10 +321,6 @@ The thinking here is that the watch application will only ever be open briefly n

 To prevent excessive battery usage, set the application timeout in the settings. This will prevent you from leaving the application open and forgotten when not being used, and the polling mechanism will then cease, saving battery life. Again, the thinking here is that the watch application will only ever be open briefly not persistently, and hence not be a constant source of battery usage unless the [background service](BackgroundService.md) for sending any watch status is used aggressively fast.

-## Changes to the (JSON) Dashboard Definition
-
-When you change the JSON file defining your dashboard, you must exit the application and the reopen it. It only takes a matter of a few seconds to pick up the new definition, but it is not automatic. *Don't forget* you may explicitly choose to clear your cached menu, or wait the application to discover your definition has changed and prompt you to restart. The application check only happens once after startup, rendering menu items and setting the menu item states.
-
 ## Submitting Corrections for Translations

 Initially all text has been created in English, and a [Python script](https://github.com/house-of-abbey/GarminHomeAssistant/blob/main/translate.py) (Google Translate under the hood) has been used to create the first version of all translations. We have been pleased to accept better translations from native language speakers, *thank you*. If you would like to submit improved translations, our preference is you do so via a [Git pull request](https://github.com/house-of-abbey/GarminHomeAssistant/pulls). If you are not comfortable doing this, then just raise an issue and someone will eventually pick the request up.
@@ -331,7 +346,7 @@ Check the latest unresolved [issues](https://github.com/house-of-abbey/GarminHom

 1. There are some cases where the file format may be valid JSON, but invalid against the schema, and the failure to catch this error could cause the application to crash. Whilst we have taken care to manage many issues, there may still be cases that are uncaught. Please verify your JSON schema, see the [trouble shooting guide](TroubleShooting.md).

-2. On some (old) devices (e.g. Vivoactive 3, Fenix 5s & Edge 520+), the menu does not update correctly to reflect changes in state effected by an external Home Assistant control. E.g. when the phone application changes the toggle status of a switch, the Garmin application does not reflect that change until the menu is touched or scrolled a little. This is a [known issue](https://forums.garmin.com/developer/connect-iq/i/bug-reports/menu2-doesn-t-allow-live-updates) already reported without a suggested software fix.
+2. On some (old) devices (e.g. Vivoactive 3, Fenix 5s & Edge 520+), the menu does not update correctly to reflect changes in state effected by an external HomeAssistant control. E.g. when the phone application changes the toggle status of a switch, the Garmin application does not reflect that change until the menu is touched or scrolled a little. This is a [known issue](https://forums.garmin.com/developer/connect-iq/i/bug-reports/menu2-doesn-t-allow-live-updates) already reported without a suggested software fix.

 3. The iPhone Connect IQ application has a bug in it we cannot be responsible for. Thanks to user [a_smart_hoome](https://community.home-assistant.io/u/a_smart_hoome) who worked the problem with the dropped Internet connection, see his explanation at https://community.home-assistant.io/t/home-assistant-app-for-garmin/637348/61 for details. Please complain to the Connect IQ application developers rather than us!

@@ -343,10 +358,12 @@ Check the latest unresolved [issues](https://github.com/house-of-abbey/GarminHom

 7. We are unable to support HTTP natively (without the workaround specified earlier). This is a limitation placed upon us by the Connect IQ API which for security reasons refuses to work with HTTP requests. There is nothing developers can do about this limitation. See the [Trouble Shooting](TroubleShooting.md#do-it-yourself-setup) guide for an example setup. We would appreciate it if users did not leave poor reviews for the lack of this feature which is beyond our control to fix.

-8. There is a [bug in Garmin Express so that when you use that software to amend the application's settings](https://github.com/house-of-abbey/GarminHomeAssistant/issues/194), the page appears in a random language not of your choice. I would like to thank user [heviiguy](https://github.com/heviiguy) for his work researching the issue, leading to these references that indicate the authors of Garmin Home Assistant cannot resolve this issue as its a bug in Garmin Express that Garmin are refusing to believe exists! See these pages for details:
+8. There is a [bug in Garmin Express so that when you use that software to amend the application's settings](https://github.com/house-of-abbey/GarminHomeAssistant/issues/194), the page appears in a random language not of your choice. I would like to thank user [heviiguy](https://github.com/heviiguy) for his work researching the issue, leading to these references that indicate the authors of Garmin HomeAssistant cannot resolve this issue as its a bug in Garmin Express that Garmin are refusing to believe exists! See these pages for details:
   - [Garmin Express - Wrong Language](https://forums.garmin.com/developer/connect-iq/i/bug-reports/garmin-express---wrong-language)
   - [Incorrect language displayed for custom data fields](https://forums.garmin.com/developer/connect-iq/f/discussion/388137/incorrect-language-displayed-for-custom-data-fields)

+9. When using Wi-Fi or LTE to toggle a light, the `toggle` will fail when the default or current state of the application's menu does not match the state of the light. The same applies to a cover or other thing that can be toggled. This is because the application is unable to initialise the menu with the current state without Bluetooth. Hence the Wi-Fi/LTE functionality is best used with `tap` items only.
+
 # Authors & Contributors

 For an up to date list of all authors and contributors, please check the [contributor's page](https://github.com/house-of-abbey/GarminHomeAssistant/graphs/contributors). Thank you all for improving this application.
--- a/TroubleShooting.md
+++ b/TroubleShooting.md
@@ -6,8 +6,8 @@

 Before [raising an issue](https://github.com/house-of-abbey/GarminHomeAssistant/issues) about a possible bug, _please, please_ check your JSON is compliant with both the JSON format and our schema. To do this you have options. The first is what we use.

-1. **Best!**  Use the GarminHomeAssistant [Web-based Editor](https://house-of-abbey.github.io/GarminHomeAssistant/web/) which includes `entity` and `service` name completion and validation by fetching data from your own Home Assistant instance. _Pretty  nifty eh?_ The other methods listed below do not add this convenience and checking.
-2. Use the [Studio Code Server](https://community.home-assistant.io/t/home-assistant-community-add-on-visual-studio-code/107863) addon for Home Assistant. You can then edit your JSON file in place.
+1. **Best!**  Use the GarminHomeAssistant [Web-based Editor](https://house-of-abbey.github.io/GarminHomeAssistant/web/) which includes `entity` and `service` name completion and validation by fetching data from your own HomeAssistant instance. _Pretty  nifty eh?_ The other methods listed below do not add this convenience and checking.
+2. Use the [Studio Code Server](https://community.home-assistant.io/t/home-assistant-community-add-on-visual-studio-code/107863) addon for HomeAssistant. You can then edit your JSON file in place.
 3. Locally installed VSCode, or if not installed, try
 4. The on-line version at https://vscode.dev/, which works really well. Paste in your JSON (and change the file type to JSON if not saving), it will then verify your file format and schema for you, highlighting any errors for you to fix.

@@ -23,7 +23,7 @@ With either of the following setups, there are inevitably some problems along th

 ### Nabu Casa Setup

-You can purchase cloud-based access to your Home Assistant from [Nabu Casa](https://www.nabucasa.com/), and then your setup will look something like this.
+You can purchase cloud-based access to your HomeAssistant from [Nabu Casa](https://www.nabucasa.com/), and then your setup will look something like this.

 ![Nabu Casa Setup](images/nabu_casa_setup.png)

@@ -67,9 +67,9 @@ This URL is very simple, you should be able to read the contents returned in a s

 The browser page should then display the JSON string you saved to the file on the web server. The point is this is a simple HTTP GET request with no bells and whistles.

-The menu configuration can be hosted anywhere, it does not have to be on the Home Assistant web server. Just as long as it is reachable from your phone from which you Bluetooth connect to your watch, or you watch if it has direct Internet access.
+The menu configuration can be hosted anywhere, it does not have to be on the HomeAssistant web server. Just as long as it is reachable from your phone from which you Bluetooth connect to your watch, or you watch if it has direct Internet access.

-### Home Assistant API URL
+### HomeAssistant API URL

 This is slightly trickier owning to the need to supply the API key. Here are three ways you can test your API URL is correctly configured. If successful, each of these should produce a JSON string output looking like:

@@ -124,8 +124,8 @@ There's an online way of testing the API URL too, thanks to [REQBIN](https://req

 With thanks to [@ziceva](https://github.com/ziceva) for solving this problem. The symptoms are:
 1. Using an API URL with SSL (HTTPS), the [web-based editor](https://house-of-abbey.github.io/GarminHomeAssistant/web/) running in a browser on the same phone running Garmin Connect works well.
-2. The exact same configuration is set in the Garmin Home Assistant application.
-3. The Garmin Home Assistant application reports:
+2. The exact same configuration is set in the Garmin HomeAssistant application.
+3. The Garmin HomeAssistant application reports:
 ```
 API: not available
 Menu: not available
@@ -153,7 +153,7 @@ To verify if you have this issue you can use a tool like [SSL Shoppers's SSL Che

 ## Watch Battery Level Reporting

-For this you will need to have already got the main application or widget working with a menu in order to prove that the API calls are successful. We have proven this works with both our home brew infrastructure as well as Nabu Casa. Now with a script similar to one of the following two, you should be able to fake the watch API call and verify receipt by Home Assistant.
+For this you will need to have already got the main application or widget working with a menu in order to prove that the API calls are successful. We have proven this works with both our home brew infrastructure as well as Nabu Casa. Now with a script similar to one of the following two, you should be able to fake the watch API call and verify receipt by HomeAssistant.

 #### Battery: Linux, MacOS, UNIX, Cygwin etc

@@ -315,7 +315,7 @@ JSON for copy & paste:

 ![No JSON](images/NoJson.png)

-When the application persists in reporting "No JSON returned from HTTP request." this might be due to a mismatch between the Webhook ID and the device settings on the Home Assistant server. We have discovered that the Webhook ID is required for Home Assistant API calls with templates in order to work in a non-privileged account. The application options include the ability to clear the Webhook ID in the application forcing a new one to be set up. This should prevent the above error being shown on startup.
+When the application persists in reporting "No JSON returned from HTTP request." this might be due to a mismatch between the Webhook ID and the device settings on the HomeAssistant server. We have discovered that the Webhook ID is required for HomeAssistant API calls with templates in order to work in a non-privileged account. The application options include the ability to clear the Webhook ID in the application forcing a new one to be set up. This should prevent the above error being shown on startup.

 Look for this option in the application settings:

@@ -323,7 +323,7 @@ Look for this option in the application settings:

 # Debug Logs

-As a desperate measure to assist with debugging the Home Assistant Application, you might be asked to send the authors a debug log.
+As a desperate measure to assist with debugging the HomeAssistant Application, you might be asked to send the authors a debug log.

 ![How to find the debug log file](images/debug_log_location.png)

--- a/Wi-Fi.md
+++ b/Wi-Fi.md
@@ -2,7 +2,7 @@

 # Wi-Fi & LTE

-Many watches now include the ability to synchronise data over Wi-Fi or event LTE in addition to Bluetooth. This gives users of this application the expectation that they should be able to operate Home Assistant devices from their watch without Bluetooth and hence their phone (that they left out of contact distance). The whole point of Bluetooth after all is that it is [low power](https://en.wikipedia.org/wiki/Bluetooth#Uses). Using Wi-Fi and LTE are power hungry and therefore not something that can be left on continuously in a small device. The watch function that uses Wi-Fi & LTE is the ability to 'synchronise', e.g. activity data (FIT files) and application updates. This function then has a limited period of time for which radio is active. Neither Wi-Fi nor LTE are "always on" like Bluetooth.
+Many watches now include the ability to synchronise data over Wi-Fi or event LTE in addition to Bluetooth. This gives users of this application the expectation that they should be able to operate HomeAssistant devices from their watch without Bluetooth and hence their phone (that they left out of contact distance). The whole point of Bluetooth after all is that it is [low power](https://en.wikipedia.org/wiki/Bluetooth#Uses). Using Wi-Fi and LTE are power hungry and therefore not something that can be left on continuously in a small device. The watch function that uses Wi-Fi & LTE is the ability to 'synchronise', e.g. activity data (FIT files) and application updates. This function then has a limited period of time for which radio is active. Neither Wi-Fi nor LTE are "always on" like Bluetooth.

 With version 3.0 onwards the application now includes the ability to temporarily turn on Wi-Fi or LTE in order to perform a task on the watch. To do this, the "synchronise" function of the Connect IQ SDK has been cleverly hijacked. This appears to be a highly sought after solution from several users as **it allows the watch to operate when out of range of the associated phone**.

--- a/compile_sim.cmd
+++ b/compile_sim.cmd
@@ -93,7 +93,7 @@ if not exist %DEST% (
 )

 echo.
-echo Starting compilation for simulation on %DEVICE%.
+echo Starting compilation for simulation on '%DEVICE%'.
 echo.

 rem call %SDK_PATH%\connectiq.bat
@@ -109,8 +109,9 @@ rem Compile PRG for a single device for side loading
  --jungles %SRC%\%JUNGLE% ^
  --private-key %SRC%\..\developer_key ^
  --device %DEVICE%_sim ^
-  --warn ^
-  --release
+  --warn
+
+rem  --release

 if %ERRORLEVEL% equ 0 (
  %SDK_PATH%\monkeydo.bat %SRC%\bin\HomeAssistant.prg %DEVICE%
--- a/examples/Actions.md
+++ b/examples/Actions.md
@@ -75,7 +75,7 @@ Note that for notify events, you _must_ not supply an `entity_id` or the API cal
 > [!IMPORTANT]
 > Be careful with the value of the `service` field.

-Note that the `service` field will need to be a locally custom `script.<something>` as soon as any `data` fields are populated and not something more generic like `script.turn_on`. If the `service` field is wrong, the application will fail with a [`Communications.INVALID_HTTP_BODY_IN_NETWORK_RESPONSE`](https://developer.garmin.com/connect-iq/api-docs/Toybox/Communications.html) error in the response from your Home Assistant and show the error message as _"No JSON returned from HTTP request"_ on your device. In the [web-based editor](https://house-of-abbey.github.io/GarminHomeAssistant/web/) you can use the standard developer tools to observe an `HTTP 400` error which the application does not see. Here we are limited by the [Garmin Connect IQ](https://developer.garmin.com/connect-iq/overview/) software development kit (SDK). We do not have enough information at the point of execution in the application to determine the cause of the error. Nor is there an immediately obvious way of identifying this issue using the JSON schema checks.
+Note that the `service` field will need to be a locally custom `script.<something>` as soon as any `data` fields are populated and not something more generic like `script.turn_on`. If the `service` field is wrong, the application will fail with a [`Communications.INVALID_HTTP_BODY_IN_NETWORK_RESPONSE`](https://developer.garmin.com/connect-iq/api-docs/Toybox/Communications.html) error in the response from your HomeAssistant and show the error message as _"No JSON returned from HTTP request"_ on your device. In the [web-based editor](https://house-of-abbey.github.io/GarminHomeAssistant/web/) you can use the standard developer tools to observe an `HTTP 400` error which the application does not see. Here we are limited by the [Garmin Connect IQ](https://developer.garmin.com/connect-iq/overview/) software development kit (SDK). We do not have enough information at the point of execution in the application to determine the cause of the error. Nor is there an immediately obvious way of identifying this issue using the JSON schema checks.

 ## Exit on Tap

--- a/examples/Templates.md
+++ b/examples/Templates.md
@@ -5,7 +5,7 @@
 In order to provide the most functionality possible the content of the menu item comes from a user-defined template (i.e. you generate your own text). This allows you to do some pretty cool things. It also makes the configuration a bit more complicated. This page will help you understand how to use templates.

 - In this file anything between `<` and `>` is a placeholder. Replace it with the appropriate value.
- [Jinja2](https://palletsprojects.com/p/jinja/) syntax is used by Home Assistant [Templates](https://www.home-assistant.io/docs/configuration/templating/). Templates are used to dynamically insert values into the content. The syntax includes:
+- [Jinja2](https://palletsprojects.com/p/jinja/) syntax is used by HomeAssistant [Templates](https://www.home-assistant.io/docs/configuration/templating/). Templates are used to dynamically insert values into the content. The syntax includes:
  - `{%` ... `%}` for Statements
  - `{{` ... `}}` for Expressions to print to the template output
  - `{#` ... `#}` for Comments not included in the template output
--- a/images/GarminHomeAssistantSettings.png
+++ b/images/GarminHomeAssistantSettings.png
--- a/resources-ara/strings/strings.xml
+++ b/resources-ara/strings/strings.xml
@@ -32,6 +32,7 @@
  <string id="GlanceMenu" scope="glance">قائمة طعام</string>
  <string id="Memory" scope="glance">ذاكرة</string>
  <string id="MenuUpdated">محدثة القائمة ، إعادة التشغيل.</string>
+  <string id="MenuCheckDisabled">تحديثات القائمة معطل.</string>
  <string id="NoAPIKey" scope="glance">لا مفتاح API في إعدادات التطبيق.</string>
  <string id="NoApiUrl" scope="glance">لا عنوان URL API في إعدادات التطبيق.</string>
  <string id="NoConfigUrl" scope="glance">لا يوجد عنوان URL للتكوين في إعدادات التطبيق.</string>
@@ -63,6 +64,7 @@
  <string id="SettingsConfigUrl">عنوان URL لتكوين القائمة (JSON).</string>
  <string id="SettingsCacheConfig">هل يجب أن يقوم تطبيق ذاكرة التخزين المؤقت لتكوين القائمة؟</string>
  <string id="SettingsClearCache">هل يجب على التطبيق مسح ذاكرة التخزين المؤقت الموجودة في المرة القادمة التي يتم فيها بدء تشغيلها؟</string>
+  <string id="SettingsEnableMenuUpdateCheck">تحقق من تحديثات القائمة عند بدء التطبيق؟ ملاحظة: يجب تمكين تخزين المؤقت القائمة. قد يتسبب هذا الإعداد في تعطل الأجهزة القديمة ذات الذاكرة الأقل.</string>
  <string id="SettingsWifiLteExecutionEnable">تمكين تنفيذ الأوامر على Wi-Fi/LTE.</string>
  <string id="SettingsVibration">هل يجب أن يقدم التطبيق ملاحظات عبر الاهتزازات؟</string>
  <string id="SettingsAppTimeout">مهلة في ثوان. الخروج من التطبيق بعد هذه الفترة من عدم النشاط لحفظ بطارية الجهاز.</string>
--- a/resources-bul/strings/strings.xml
+++ b/resources-bul/strings/strings.xml
@@ -32,6 +32,7 @@
  <string id="GlanceMenu" scope="glance">Меню</string>
  <string id="Memory" scope="glance">Памет</string>
  <string id="MenuUpdated">Менюто актуализирано, рестартиране.</string>
+  <string id="MenuCheckDisabled">Актуализации на менюто деактивирани.</string>
  <string id="NoAPIKey" scope="glance">Няма ключ за API в настройките на приложението.</string>
  <string id="NoApiUrl" scope="glance">Няма URL адрес на API в настройките на приложението.</string>
  <string id="NoConfigUrl" scope="glance">Няма URL адрес на конфигурация в настройките на приложението.</string>
@@ -63,6 +64,7 @@
  <string id="SettingsConfigUrl">URL за конфигуриране на менюто (JSON).</string>
  <string id="SettingsCacheConfig">Трябва ли приложението да кешира конфигурацията на менюто?</string>
  <string id="SettingsClearCache">Трябва ли приложението да изчисти съществуващия кеш следващия път, когато е стартиран?</string>
+  <string id="SettingsEnableMenuUpdateCheck">Проверете за актуализации на менюто за стартиране на приложението? ЗАБЕЛЕЖКА: кеширането на менюто трябва да бъде активирано. Тази настройка може да доведе до сриване на по -старите устройства с по -малко памет.</string>
  <string id="SettingsWifiLteExecutionEnable">Активиране на изпълнение на команди над Wi-Fi/LTE.</string>
  <string id="SettingsVibration">Трябва ли приложението да предоставя обратна връзка чрез вибрации?</string>
  <string id="SettingsAppTimeout">Време за изчакване за секунди. Излезте от приложението след този период на бездействие, за да запазите батерията на устройството.</string>
--- a/resources-ces/strings/strings.xml
+++ b/resources-ces/strings/strings.xml
@@ -32,6 +32,7 @@
  <string id="GlanceMenu" scope="glance">Menu</string>
  <string id="Memory" scope="glance">Paměť</string>
  <string id="MenuUpdated">Aktualizováno nabídka, restartujte.</string>
+  <string id="MenuCheckDisabled">Aktualizace nabídky zakázáno.</string>
  <string id="NoAPIKey" scope="glance">Žádný klíč API v nastavení aplikace.</string>
  <string id="NoApiUrl" scope="glance">Žádná URL API v nastavení aplikace.</string>
  <string id="NoConfigUrl" scope="glance">V nastavení aplikace není žádná konfigurační adresa URL.</string>
@@ -63,6 +64,7 @@
  <string id="SettingsConfigUrl">URL pro konfiguraci nabídky (JSON).</string>
  <string id="SettingsCacheConfig">Měla by aplikace ukládat konfiguraci nabídky?</string>
  <string id="SettingsClearCache">Měla by aplikace vymazat stávající mezipaměť příště, až bude spuštěna?</string>
+  <string id="SettingsEnableMenuUpdateCheck">Zkontrolujte aktualizace nabídky při zahájení aplikace? POZNÁMKA: Musí být povoleno ukládání do mezipaměti nabídky. Toto nastavení může způsobit, že starší zařízení s menší pamětí dojde.</string>
  <string id="SettingsWifiLteExecutionEnable">Povolit provádění příkazů přes Wi-Fi/LTE.</string>
  <string id="SettingsVibration">Měla by aplikace poskytovat zpětnou vazbu prostřednictvím vibrací?</string>
  <string id="SettingsAppTimeout">Timeout během několika sekund. Po tomto období nečinnosti uložte aplikaci k uložení baterie zařízení.</string>
--- a/resources-dan/strings/strings.xml
+++ b/resources-dan/strings/strings.xml
@@ -32,6 +32,7 @@
  <string id="GlanceMenu" scope="glance">Menu</string>
  <string id="Memory" scope="glance">Hukommelse</string>
  <string id="MenuUpdated">Menu opdateret, genstart.</string>
+  <string id="MenuCheckDisabled">Menuopdateringer deaktiveret.</string>
  <string id="NoAPIKey" scope="glance">Ingen API -nøgle i applikationsindstillingerne.</string>
  <string id="NoApiUrl" scope="glance">Ingen API -URL i applikationsindstillingerne.</string>
  <string id="NoConfigUrl" scope="glance">Ingen konfigurations -URL i applikationsindstillingerne.</string>
@@ -63,6 +64,7 @@
  <string id="SettingsConfigUrl">URL til menukonfiguration (JSON).</string>
  <string id="SettingsCacheConfig">Skal applikationscache menuen Konfiguration?</string>
  <string id="SettingsClearCache">Bør applikationen rydde den eksisterende cache næste gang den startes?</string>
+  <string id="SettingsEnableMenuUpdateCheck">Kontroller for menuopdateringer på applikationsstart? Bemærk: Menu Cache skal være aktiveret. Denne indstilling kan forårsage, at ældre enheder med mindre hukommelse går ned.</string>
  <string id="SettingsWifiLteExecutionEnable">Aktivér udførelse af kommandoer over Wi-Fi/LTE.</string>
  <string id="SettingsVibration">Bør applikationen give feedback via vibrationer?</string>
  <string id="SettingsAppTimeout">Timeout på få sekunder. Afslut applikationen efter denne periode med inaktivitet for at gemme enhedsbatteriet.</string>
--- a/resources-deu/strings/strings.xml
+++ b/resources-deu/strings/strings.xml
@@ -32,6 +32,7 @@
  <string id="GlanceMenu" scope="glance">Menü</string>
  <string id="Memory" scope="glance">Speicher</string>
  <string id="MenuUpdated">Menü aktualisiert, neu starten.</string>
+  <string id="MenuCheckDisabled">Menü -Updates deaktiviert.</string>
  <string id="NoAPIKey" scope="glance">Kein API-Schlüssel in den App-Einstellungen hinterlegt.</string>
  <string id="NoApiUrl" scope="glance">Keine API-URL in den App-Einstellungen hinterlegt.</string>
  <string id="NoConfigUrl" scope="glance">Keine Menükonfigurations-URL (JSON) in den App-Einstellungen hinterlegt.</string>
@@ -63,6 +64,7 @@
  <string id="SettingsConfigUrl">URL für die Menükonfiguration (JSON).</string>
  <string id="SettingsCacheConfig">Soll die App die Menükonfiguration cachen?</string>
  <string id="SettingsClearCache">Soll die Anwendung beim nächsten Start den vorhandenen Cache löschen?</string>
+  <string id="SettingsEnableMenuUpdateCheck">Überprüfen Sie die Menü -Updates für Anwendungsstart? HINWEIS: Das Menü Caching muss aktiviert sein. Diese Einstellung kann dazu führen, dass ältere Geräte mit weniger Speicher abstürzen.</string>
  <string id="SettingsWifiLteExecutionEnable">Befehlsausführung über WLAN/LTE aktivieren.</string>
  <string id="SettingsVibration">Soll die App Rückmeldung per Vibration geben?</string>
  <string id="SettingsAppTimeout">Timeout in Sekunden. Beendet die App nach dieser Inaktivitätszeit, um Akku zu sparen.</string>
--- a/resources-dut/strings/strings.xml
+++ b/resources-dut/strings/strings.xml
@@ -32,6 +32,7 @@
  <string id="GlanceMenu" scope="glance">Menu</string>
  <string id="Memory" scope="glance">Geheugen</string>
  <string id="MenuUpdated">Menu bijgewerkt, opnieuw opstarten.</string>
+  <string id="MenuCheckDisabled">Menu -updates uitgeschakeld.</string>
  <string id="NoAPIKey" scope="glance">Geen API -toets in de toepassingsinstellingen.</string>
  <string id="NoApiUrl" scope="glance">Geen API -URL in de toepassingsinstellingen.</string>
  <string id="NoConfigUrl" scope="glance">Geen configuratie -URL in de toepassingsinstellingen.</string>
@@ -63,6 +64,7 @@
  <string id="SettingsConfigUrl">URL voor menuconfiguratie (JSON).</string>
  <string id="SettingsCacheConfig">Moet de toepassingscache de menu -configuratie?</string>
  <string id="SettingsClearCache">Moet de toepassing de bestaande cache wissen de volgende keer dat deze wordt gestart?</string>
+  <string id="SettingsEnableMenuUpdateCheck">Controleer op menu -updates over het starten van de applicatie? Opmerking: menu Caching moet worden ingeschakeld. Deze instelling kan ervoor zorgen dat oudere apparaten met minder geheugen crashen.</string>
  <string id="SettingsWifiLteExecutionEnable">Schakel opdrachten uit via Wi-Fi/LTE.</string>
  <string id="SettingsVibration">Moet de applicatie feedback geven via trillingen?</string>
  <string id="SettingsAppTimeout">Time -out in seconden. Verlaat de toepassing na deze periode van inactiviteit om de apparaatbatterij op te slaan.</string>
--- a/resources-est/strings/strings.xml
+++ b/resources-est/strings/strings.xml
@@ -32,6 +32,7 @@
  <string id="GlanceMenu" scope="glance">Menüü</string>
  <string id="Memory" scope="glance">Mälu</string>
  <string id="MenuUpdated">Menüü värskendatud, taaskäivitage.</string>
+  <string id="MenuCheckDisabled">Menüüvärskendused on keelatud.</string>
  <string id="NoAPIKey" scope="glance">Rakenduse seadetes pole API -klahvi.</string>
  <string id="NoApiUrl" scope="glance">Rakenduse seadetes pole API URL -i.</string>
  <string id="NoConfigUrl" scope="glance">Rakenduse sätetes pole konfiguratsiooni URL -i.</string>
@@ -63,6 +64,7 @@
  <string id="SettingsConfigUrl">URL menüü konfiguratsiooni jaoks (JSON).</string>
  <string id="SettingsCacheConfig">Kas rakenduse vahemälu peaks menüü konfiguratsiooni vahemälu vahemälu vahemälu vahemälu vahemälu vahemälu vahemälu vahemälu</string>
  <string id="SettingsClearCache">Kas rakendus peaks olemasoleva vahemälu järgmine kord alustama?</string>
+  <string id="SettingsEnableMenuUpdateCheck">Kontrollige rakenduse käivitamise menüüuuendusi? MÄRKUS. Menüü vahemällu salvestamine peab olema lubatud. See säte võib põhjustada vanemate seadmete, mille mälu on vähem.</string>
  <string id="SettingsWifiLteExecutionEnable">Luba käskude täitmine Wi-Fi/LTE kaudu.</string>
  <string id="SettingsVibration">Kas rakendus peaks vibratsiooni kaudu tagasisidet andma?</string>
  <string id="SettingsAppTimeout">Aegumine sekunditega. Pärast seda tegevusetuse perioodi seade aku salvestamiseks väljuge rakendusest.</string>
--- a/resources-fin/strings/strings.xml
+++ b/resources-fin/strings/strings.xml
@@ -32,6 +32,7 @@
  <string id="GlanceMenu" scope="glance">Valikko</string>
  <string id="Memory" scope="glance">Muisti</string>
  <string id="MenuUpdated">Valikko päivitetty, käynnistä uudelleen.</string>
+  <string id="MenuCheckDisabled">Valikkopäivitykset poistettu käytöstä.</string>
  <string id="NoAPIKey" scope="glance">Ei sovellusliittymää avainta sovellusasetuksissa.</string>
  <string id="NoApiUrl" scope="glance">Ei sovellus -URL -osoitetta sovellusasetuksissa.</string>
  <string id="NoConfigUrl" scope="glance">Ei määritys -URL -osoitetta sovellusasetuksissa.</string>
@@ -63,6 +64,7 @@
  <string id="SettingsConfigUrl">Valikkokokoonpanon URL (JSON).</string>
  <string id="SettingsCacheConfig">Pitäisikö sovelluksen välimuistiin valikon kokoonpano?</string>
  <string id="SettingsClearCache">Pitäisikö sovelluksen tyhjentää olemassa oleva välimuisti seuraavalla kerralla?</string>
+  <string id="SettingsEnableMenuUpdateCheck">Tarkista valikkopäivitykset sovelluksen käynnistyksestä? HUOMAUTUS: Valikon välimuisti on otettava käyttöön. Tämä asetus voi aiheuttaa vanhempia laitteita, joissa on vähemmän muistia kaatumiseen.</string>
  <string id="SettingsWifiLteExecutionEnable">Ota komentojen suorittaminen käyttöön Wi-Fi/LTE: n kautta.</string>
  <string id="SettingsVibration">Pitäisikö sovelluksen antaa palautetta värähtelyjen kautta?</string>
  <string id="SettingsAppTimeout">Aikakatkaisu sekunneissa. Poistu sovelluksesta tämän toimettomuuden jälkeen laitteen akun tallentamiseksi.</string>
--- a/resources-fre/strings/strings.xml
+++ b/resources-fre/strings/strings.xml
@@ -32,6 +32,7 @@
  <string id="GlanceMenu" scope="glance">Menu</string>
  <string id="Memory" scope="glance">Mémoire</string>
  <string id="MenuUpdated">Menu mis à jour, redémarrer.</string>
+  <string id="MenuCheckDisabled">MENU MISE À JOUR Désactivé.</string>
  <string id="NoAPIKey" scope="glance">Aucune clé API dans les paramètres de l'application.</string>
  <string id="NoApiUrl" scope="glance">Aucune URL de l'API dans les paramètres de l'application.</string>
  <string id="NoConfigUrl" scope="glance">Aucune URL de configuration dans les paramètres de l'application.</string>
@@ -63,6 +64,7 @@
  <string id="SettingsConfigUrl">URL pour la configuration du menu (JSON).</string>
  <string id="SettingsCacheConfig">L'application devrait-elle mettre en cache la configuration du menu?</string>
  <string id="SettingsClearCache">L'application devrait-elle effacer le cache existant la prochaine fois qu'il sera démarré?</string>
+  <string id="SettingsEnableMenuUpdateCheck">Vérifiez les mises à jour du menu au démarrage de l'application? Remarque: la mise en cache de menu doit être activée. Ce paramètre peut entraîner un écrasement des appareils plus anciens avec moins de mémoire.</string>
  <string id="SettingsWifiLteExecutionEnable">Activer l'exécution des commandes sur Wi-Fi / LTE.</string>
  <string id="SettingsVibration">L'application devrait-elle fournir des commentaires via des vibrations?</string>
  <string id="SettingsAppTimeout">Timeout en quelques secondes. Quittez l'application après cette période d'inactivité pour enregistrer la batterie de l'appareil.</string>
--- a/resources-gre/strings/strings.xml
+++ b/resources-gre/strings/strings.xml
@@ -32,6 +32,7 @@
  <string id="GlanceMenu" scope="glance">Μενού</string>
  <string id="Memory" scope="glance">Μνήμη</string>
  <string id="MenuUpdated">Ενημερώθηκε μενού, επανεκκίνηση.</string>
+  <string id="MenuCheckDisabled">Οι ενημερώσεις μενού απενεργοποιούνται.</string>
  <string id="NoAPIKey" scope="glance">Δεν υπάρχει κλειδί API στις ρυθμίσεις εφαρμογής.</string>
  <string id="NoApiUrl" scope="glance">Δεν υπάρχει διεύθυνση URL API στις ρυθμίσεις εφαρμογής.</string>
  <string id="NoConfigUrl" scope="glance">Χωρίς διευθύνσεις διαμόρφωσης στις ρυθμίσεις εφαρμογής.</string>
@@ -63,6 +64,7 @@
  <string id="SettingsConfigUrl">URL για διαμόρφωση μενού (JSON).</string>
  <string id="SettingsCacheConfig">Πρέπει η προσωρινή μνήμη εφαρμογής τη διαμόρφωση μενού;</string>
  <string id="SettingsClearCache">Πρέπει η εφαρμογή να διαγράψει την υπάρχουσα μνήμη cache την επόμενη φορά που θα ξεκινήσει;</string>
+  <string id="SettingsEnableMenuUpdateCheck">Ελέγξτε για ενημερώσεις μενού κατά την έναρξη της εφαρμογής; ΣΗΜΕΙΩΣΗ: Η προσωρινή αποθήκευση μενού πρέπει να είναι ενεργοποιημένη. Αυτή η ρύθμιση μπορεί να προκαλέσει παλαιότερες συσκευές με λιγότερη μνήμη για συντριβή.</string>
  <string id="SettingsWifiLteExecutionEnable">Ενεργοποιήστε τις εντολές εκτέλεσης μέσω Wi-Fi/LTE.</string>
  <string id="SettingsVibration">Πρέπει η εφαρμογή να παρέχει ανατροφοδότηση μέσω δονήσεων;</string>
  <string id="SettingsAppTimeout">Χρονικό όριο σε δευτερόλεπτα. Βγείτε από την εφαρμογή μετά από αυτήν την περίοδο αδράνειας για να αποθηκεύσετε τη μπαταρία της συσκευής.</string>
--- a/resources-heb/strings/strings.xml
+++ b/resources-heb/strings/strings.xml
@@ -32,6 +32,7 @@
  <string id="GlanceMenu" scope="glance">תַפרִיט</string>
  <string id="Memory" scope="glance">זֵכֶר</string>
  <string id="MenuUpdated">מעודכן בתפריט, הפעל מחדש.</string>
+  <string id="MenuCheckDisabled">עדכוני תפריט מושבתים.</string>
  <string id="NoAPIKey" scope="glance">אין מפתח API בהגדרות היישום.</string>
  <string id="NoApiUrl" scope="glance">אין כתובת URL בהגדרות היישום.</string>
  <string id="NoConfigUrl" scope="glance">אין כתובת אתר תצורה בהגדרות היישום.</string>
@@ -63,6 +64,7 @@
  <string id="SettingsConfigUrl">כתובת אתר לתצורת תפריט (JSON).</string>
  <string id="SettingsCacheConfig">האם על היישום למנוע את תצורת התפריט?</string>
  <string id="SettingsClearCache">האם על היישום לנקות את המטמון הקיים בפעם הבאה שהוא מתחיל?</string>
+  <string id="SettingsEnableMenuUpdateCheck">בדוק אם יש עדכוני תפריט על התחלת היישום? הערה: יש לאפשר מטמון בתפריט. הגדרה זו עלולה לגרום למכשירים ישנים עם פחות זיכרון להתרסק.</string>
  <string id="SettingsWifiLteExecutionEnable">אפשר לבצע פקודות דרך Wi-Fi/LTE.</string>
  <string id="SettingsVibration">האם על היישום לספק משוב באמצעות תנודות?</string>
  <string id="SettingsAppTimeout">פסק זמן בשניות. צא מהיישום לאחר תקופת חוסר פעילות זו כדי לחסוך את סוללת ההתקן.</string>
--- a/resources-hrv/strings/strings.xml
+++ b/resources-hrv/strings/strings.xml
@@ -32,6 +32,7 @@
  <string id="GlanceMenu" scope="glance">Jelovnik</string>
  <string id="Memory" scope="glance">Memorija</string>
  <string id="MenuUpdated">Izbornik Ažurirano, ponovno pokrenite.</string>
+  <string id="MenuCheckDisabled">Ažuriranja izbornika onemogućena.</string>
  <string id="NoAPIKey" scope="glance">Nema API ključa u postavkama aplikacije.</string>
  <string id="NoApiUrl" scope="glance">Nema URL -a API -ja u postavkama aplikacije.</string>
  <string id="NoConfigUrl" scope="glance">Nema URL -a konfiguracije u postavkama aplikacije.</string>
@@ -55,7 +56,7 @@
  <string id="WifiLtePrompt">Izvršite preko Wi-Fi/LTE?</string>
  <string id="WifiLteExecutionTitle">Slanje kod kuće pomoćnika.</string>
  <string id="WifiLteExecutionDataError">Nema primljenih podataka.</string>
-  <!-- Za postavke GUI, žice bi trebale biti u redoslijedu koji se koriste. -->
+  <!-- Za postavke GUI, nizovi bi trebali biti u redoslijedu koji se koriste. -->
  <string id="SettingsSelect">Odaberite ...</string>
  <string id="SettingsApiKey">Ključ API -ja za HomeAssistant.</string>
  <string id="SettingsApiKeyPrompt">Dugotrajni pristupni token.</string>
@@ -63,6 +64,7 @@
  <string id="SettingsConfigUrl">URL za konfiguraciju izbornika (JSON).</string>
  <string id="SettingsCacheConfig">Treba li aplikacija predmemorirati konfiguraciju izbornika?</string>
  <string id="SettingsClearCache">Treba li aplikacija očistiti postojeću predmemoriju sljedeći put kad se pokrene?</string>
+  <string id="SettingsEnableMenuUpdateCheck">Provjerite ažuriranja izbornika o pokretanju aplikacije? Napomena: Mora biti omogućeno predmemoriranje izbornika. Ova postavka može uzrokovati da se stariji uređaji s manje memorije sruše.</string>
  <string id="SettingsWifiLteExecutionEnable">Omogući izvršavanje naredbi preko Wi-Fi/LTE.</string>
  <string id="SettingsVibration">Treba li aplikacija davati povratne informacije putem vibracija?</string>
  <string id="SettingsAppTimeout">Timeout u sekundi. Izađite iz aplikacije nakon ovog razdoblja neaktivnosti kako biste uštedjeli bateriju uređaja.</string>
--- a/resources-hun/strings/strings.xml
+++ b/resources-hun/strings/strings.xml
@@ -32,6 +32,7 @@
  <string id="GlanceMenu" scope="glance">Menü</string>
  <string id="Memory" scope="glance">Emlékezet</string>
  <string id="MenuUpdated">A menü frissítve, indítsa újra.</string>
+  <string id="MenuCheckDisabled">A menüfrissítések letiltva.</string>
  <string id="NoAPIKey" scope="glance">Nincs API -kulcs az alkalmazásbeállításokban.</string>
  <string id="NoApiUrl" scope="glance">Nincs API URL az alkalmazás beállításaiban.</string>
  <string id="NoConfigUrl" scope="glance">Nincs konfigurációs URL az alkalmazásbeállításokban.</string>
@@ -63,6 +64,7 @@
  <string id="SettingsConfigUrl">URL a menükonfigurációhoz (JSON).</string>
  <string id="SettingsCacheConfig">Az alkalmazásnak gyorsítótáraznia kell a menükonfigurációt?</string>
  <string id="SettingsClearCache">Az alkalmazásnak törölnie kell -e a meglévő gyorsítótárat a következő indításkor?</string>
+  <string id="SettingsEnableMenuUpdateCheck">Ellenőrizze a menüfrissítéseket az alkalmazás indításakor? MEGJEGYZÉS: A menü gyorsítótárazását engedélyezni kell. Ez a beállítás a kevesebb memóriával rendelkező régebbi eszközök összeomlását okozhatja.</string>
  <string id="SettingsWifiLteExecutionEnable">Engedélyezze a parancsok végrehajtási végrehajtását a Wi-Fi/LTE-n keresztül.</string>
  <string id="SettingsVibration">Az alkalmazásnak visszacsatolást kell adnia a rezgések révén?</string>
  <string id="SettingsAppTimeout">Időtúllépés másodpercek alatt. Az eszköz akkumulátorának mentése érdekében kilépjen az alkalmazásból az inaktivitás után.</string>
--- a/resources-ind/strings/strings.xml
+++ b/resources-ind/strings/strings.xml
@@ -32,6 +32,7 @@
  <string id="GlanceMenu" scope="glance">Menu</string>
  <string id="Memory" scope="glance">Ingatan</string>
  <string id="MenuUpdated">Menu diperbarui, restart.</string>
+  <string id="MenuCheckDisabled">Pembaruan menu dinonaktifkan.</string>
  <string id="NoAPIKey" scope="glance">Tidak ada kunci API di pengaturan aplikasi.</string>
  <string id="NoApiUrl" scope="glance">Tidak ada URL API di pengaturan aplikasi.</string>
  <string id="NoConfigUrl" scope="glance">Tidak ada URL konfigurasi di pengaturan aplikasi.</string>
@@ -63,6 +64,7 @@
  <string id="SettingsConfigUrl">URL untuk Konfigurasi Menu (JSON).</string>
  <string id="SettingsCacheConfig">Haruskah Aplikasi Menyimpan Konfigurasi Menu?</string>
  <string id="SettingsClearCache">Haruskah aplikasi menghapus cache yang ada lain kali dimulai?</string>
+  <string id="SettingsEnableMenuUpdateCheck">Periksa pembaruan menu pada aplikasi mulai? Catatan: Caching menu harus diaktifkan. Pengaturan ini dapat menyebabkan perangkat yang lebih tua dengan lebih sedikit memori untuk macet.</string>
  <string id="SettingsWifiLteExecutionEnable">Aktifkan Perintah yang Mengeksekusi melalui Wi-Fi/LTE.</string>
  <string id="SettingsVibration">Haruskah aplikasi memberikan umpan balik melalui getaran?</string>
  <string id="SettingsAppTimeout">Batas waktu dalam hitungan detik. Keluar dari aplikasi setelah periode tidak aktif ini untuk menyimpan baterai perangkat.</string>
--- a/resources-ita/strings/strings.xml
+++ b/resources-ita/strings/strings.xml
@@ -32,6 +32,7 @@
  <string id="GlanceMenu" scope="glance">Menu</string>
  <string id="Memory" scope="glance">Memoria</string>
  <string id="MenuUpdated">Menu aggiornato, riavvio.</string>
+  <string id="MenuCheckDisabled">Aggiornamenti di menu disabilitati.</string>
  <string id="NoAPIKey" scope="glance">Nessuna chiave API nelle impostazioni dell'applicazione.</string>
  <string id="NoApiUrl" scope="glance">Nessun URL API nelle impostazioni dell'applicazione.</string>
  <string id="NoConfigUrl" scope="glance">Nessun URL di configurazione nelle impostazioni dell'applicazione.</string>
@@ -63,6 +64,7 @@
  <string id="SettingsConfigUrl">URL per la configurazione del menu (JSON).</string>
  <string id="SettingsCacheConfig">L'applicazione dovrebbe memorizzare la cache della configurazione del menu?</string>
  <string id="SettingsClearCache">L'applicazione dovrebbe cancellare la cache esistente la prossima volta che viene avviata?</string>
+  <string id="SettingsEnableMenuUpdateCheck">Controllare gli aggiornamenti del menu all'inizio dell'applicazione? NOTA: la memorizzazione della memorizzazione nella cache dei menu deve essere abilitata. Questa impostazione può causare crash di dispositivi più vecchi con meno memoria.</string>
  <string id="SettingsWifiLteExecutionEnable">Abilita l'esecuzione dei comandi su Wi-Fi/LTE.</string>
  <string id="SettingsVibration">L'applicazione dovrebbe fornire feedback tramite vibrazioni?</string>
  <string id="SettingsAppTimeout">Timeout in secondi. Esci dall'applicazione dopo questo periodo di inattività per salvare la batteria del dispositivo.</string>
--- a/resources-jpn/strings/strings.xml
+++ b/resources-jpn/strings/strings.xml
@@ -32,6 +32,7 @@
  <string id="GlanceMenu" scope="glance">メニュー</string>
  <string id="Memory" scope="glance">メモリ</string>
  <string id="MenuUpdated">メニューの更新、再起動。</string>
+  <string id="MenuCheckDisabled">メニューの更新は無効です。</string>
  <string id="NoAPIKey" scope="glance">アプリケーション設定にAPIキーはありません。</string>
  <string id="NoApiUrl" scope="glance">アプリケーション設定にAPI URLはありません。</string>
  <string id="NoConfigUrl" scope="glance">アプリケーション設定に構成URLはありません。</string>
@@ -63,6 +64,7 @@
  <string id="SettingsConfigUrl">メニュー構成用のURL（JSON）。</string>
  <string id="SettingsCacheConfig">アプリケーションはメニュー構成をキャッシュする必要がありますか？</string>
  <string id="SettingsClearCache">次回開始時にアプリケーションが既存のキャッシュをクリアする必要がありますか？</string>
+  <string id="SettingsEnableMenuUpdateCheck">アプリケーションの開始に関するメニューの更新を確認しますか？注：メニューキャッシングを有効にする必要があります。この設定により、メモリが少ない古いデバイスがクラッシュする可能性があります。</string>
  <string id="SettingsWifiLteExecutionEnable">Wi-Fi/LTEを介してコマンドを実行できるようにします。</string>
  <string id="SettingsVibration">アプリケーションは振動を介してフィードバックを提供する必要がありますか？</string>
  <string id="SettingsAppTimeout">数秒でタイムアウト。デバイスバッテリーを保存するために、この不活性期間の後にアプリケーションを終了します。</string>
--- a/resources-kor/strings/strings.xml
+++ b/resources-kor/strings/strings.xml
@@ -32,6 +32,7 @@
  <string id="GlanceMenu" scope="glance">메뉴</string>
  <string id="Memory" scope="glance">메모리</string>
  <string id="MenuUpdated">메뉴가 업데이트되고 다시 시작됩니다.</string>
+  <string id="MenuCheckDisabled">메뉴 업데이트가 비활성화됩니다.</string>
  <string id="NoAPIKey" scope="glance">응용 프로그램 설정에 API 키가 없습니다.</string>
  <string id="NoApiUrl" scope="glance">응용 프로그램 설정에 API URL이 없습니다.</string>
  <string id="NoConfigUrl" scope="glance">응용 프로그램 설정에 구성 URL이 없습니다.</string>
@@ -63,6 +64,7 @@
  <string id="SettingsConfigUrl">메뉴 구성 (JSON) 용 URL.</string>
  <string id="SettingsCacheConfig">응용 프로그램이 메뉴 구성을 캐시해야합니까?</string>
  <string id="SettingsClearCache">다음에 시작될 때 응용 프로그램이 기존 캐시를 지우려면?</string>
+  <string id="SettingsEnableMenuUpdateCheck">애플리케이션 시작에서 메뉴 업데이트를 확인 하시겠습니까? 참고 : 메뉴 캐싱이 활성화되어야합니다.이 설정으로 인해 메모리가 적은 기존 장치가 충돌 할 수 있습니다.</string>
  <string id="SettingsWifiLteExecutionEnable">Wi-Fi/LTE를 통해 명령을 실행할 수 있습니다.</string>
  <string id="SettingsVibration">응용 프로그램이 진동을 통해 피드백을 제공해야합니까?</string>
  <string id="SettingsAppTimeout">시간 초과 시간 초과. 장치 배터리를 저장하기 위해이 비활성 기간 후에 응용 프로그램을 종료하십시오.</string>
--- a/resources-lav/strings/strings.xml
+++ b/resources-lav/strings/strings.xml
@@ -32,6 +32,7 @@
  <string id="GlanceMenu" scope="glance">Ēdienkarte</string>
  <string id="Memory" scope="glance">Atmiņa</string>
  <string id="MenuUpdated">Atjaunināta izvēlne, restartējiet.</string>
+  <string id="MenuCheckDisabled">Izvēlnes atjauninājumi ir atspējoti.</string>
  <string id="NoAPIKey" scope="glance">Lietojumprogrammas iestatījumos nav API atslēgas.</string>
  <string id="NoApiUrl" scope="glance">Lietojumprogrammu iestatījumos nav API URL.</string>
  <string id="NoConfigUrl" scope="glance">Lietojumprogrammas iestatījumos nav konfigurācijas URL.</string>
@@ -63,6 +64,7 @@
  <string id="SettingsConfigUrl">URL izvēlnes konfigurācijai (JSON).</string>
  <string id="SettingsCacheConfig">Vai lietojumprogrammai vajadzētu kešatmiņā izvēlnes konfigurāciju?</string>
  <string id="SettingsClearCache">Vai lietojumprogrammai vajadzētu notīrīt esošo kešatmiņu nākamreiz, kad tā tiks sākta?</string>
+  <string id="SettingsEnableMenuUpdateCheck">Pārbaudiet izvēlnes atjauninājumus lietojumprogrammas sākumā? PIEZĪME: jābūt iespējotai izvēlnei kešatmiņā. Šis iestatījums var izraisīt vecākām ierīcēm ar mazāku atmiņu avāriju.</string>
  <string id="SettingsWifiLteExecutionEnable">Iespējot izpildīt komandas, izmantojot Wi-Fi/LTE.</string>
  <string id="SettingsVibration">Vai lietojumprogrammai vajadzētu sniegt atgriezenisko saiti, izmantojot vibrācijas?</string>
  <string id="SettingsAppTimeout">Noildze sekundēs. Izejiet no lietojumprogrammas pēc šī bezdarbības perioda, lai saglabātu ierīces akumulatoru.</string>
--- a/resources-lit/strings/strings.xml
+++ b/resources-lit/strings/strings.xml
@@ -32,6 +32,7 @@
  <string id="GlanceMenu" scope="glance">Meniu</string>
  <string id="Memory" scope="glance">Atmintis</string>
  <string id="MenuUpdated">Meniu Atnaujinta, paleiskite iš naujo.</string>
+  <string id="MenuCheckDisabled">Meniu atnaujinimai išjungti.</string>
  <string id="NoAPIKey" scope="glance">Nėra API rakto programos nustatymuose.</string>
  <string id="NoApiUrl" scope="glance">Nėra API URL programos nustatymuose.</string>
  <string id="NoConfigUrl" scope="glance">Nėra konfigūracijos URL programos nustatymuose.</string>
@@ -63,6 +64,7 @@
  <string id="SettingsConfigUrl">URL meniu konfigūracijai (JSON).</string>
  <string id="SettingsCacheConfig">Ar programos talpykla turėtų talpinti meniu konfigūraciją?</string>
  <string id="SettingsClearCache">Ar programa turėtų išvalyti esamą talpyklą kitą kartą, kai ji bus paleista?</string>
+  <string id="SettingsEnableMenuUpdateCheck">Patikrinkite, ar nėra meniu atnaujinimų, pradedant programą? PASTABA: Turi būti įjungtas meniu talpyklos talpykla. Šis nustatymas gali sukelti senesnius įrenginius, turinčius mažiau atminties.</string>
  <string id="SettingsWifiLteExecutionEnable">Įgalinti komandas vykdant „Wi-Fi“/LTE.</string>
  <string id="SettingsVibration">Ar programa turėtų pateikti grįžtamąjį ryšį per vibracijas?</string>
  <string id="SettingsAppTimeout">Laikas per kelias sekundes. Išeikite iš programos po šio neveiklumo laikotarpio, kad išsaugotumėte įrenginio akumuliatorių.</string>
--- a/resources-nob/strings/strings.xml
+++ b/resources-nob/strings/strings.xml
@@ -32,6 +32,7 @@
  <string id="GlanceMenu" scope="glance">Meny</string>
  <string id="Memory" scope="glance">Hukommelse</string>
  <string id="MenuUpdated">Meny oppdatert, omstart.</string>
+  <string id="MenuCheckDisabled">Menyoppdateringer deaktivert.</string>
  <string id="NoAPIKey" scope="glance">Ingen API -nøkkel i applikasjonsinnstillingene.</string>
  <string id="NoApiUrl" scope="glance">Ingen API -URL i applikasjonsinnstillingene.</string>
  <string id="NoConfigUrl" scope="glance">Ingen konfigurasjons -URL i applikasjonsinnstillingene.</string>
@@ -63,6 +64,7 @@
  <string id="SettingsConfigUrl">URL for menykonfigurasjon (JSON).</string>
  <string id="SettingsCacheConfig">Bør applikasjonsbufferen menykonfigurasjonen?</string>
  <string id="SettingsClearCache">Bør applikasjonen fjerne den eksisterende cachen neste gang den startes?</string>
+  <string id="SettingsEnableMenuUpdateCheck">Se etter menyoppdateringer på applikasjonsstart? MERKNAD: MENU -hurtigbufring må være aktivert. Denne innstillingen kan føre til at eldre enheter med mindre minne krasjer.</string>
  <string id="SettingsWifiLteExecutionEnable">Aktiver utførende kommandoer over Wi-Fi/LTE.</string>
  <string id="SettingsVibration">Bør applikasjonen gi tilbakemelding via vibrasjoner?</string>
  <string id="SettingsAppTimeout">Tidsavbrudd på sekunder. Gå ut av applikasjonen etter denne perioden med inaktivitet for å lagre enhetsbatteriet.</string>
--- a/resources-pol/strings/strings.xml
+++ b/resources-pol/strings/strings.xml
@@ -32,6 +32,7 @@
  <string id="GlanceMenu" scope="glance">Menu</string>
  <string id="Memory" scope="glance">Pamięć</string>
  <string id="MenuUpdated">Zaktualizowano menu, uruchom ponownie.</string>
+  <string id="MenuCheckDisabled">Zakładania menu wyłączone.</string>
  <string id="NoAPIKey" scope="glance">Brak klucza API w ustawieniach aplikacji.</string>
  <string id="NoApiUrl" scope="glance">Brak adresu URL API w ustawieniach aplikacji.</string>
  <string id="NoConfigUrl" scope="glance">Brak adresu URL konfiguracji w ustawieniach aplikacji.</string>
@@ -63,6 +64,7 @@
  <string id="SettingsConfigUrl">URL dla konfiguracji menu (JSON).</string>
  <string id="SettingsCacheConfig">Czy aplikacja powinna buforować konfigurację menu?</string>
  <string id="SettingsClearCache">Czy aplikacja powinna wyczyścić istniejącą pamięć podręczną następnym razem, gdy zostanie uruchomiona?</string>
+  <string id="SettingsEnableMenuUpdateCheck">Sprawdź aktualizacje menu na temat uruchomienia aplikacji? Uwaga: Buforowanie menu musi być włączone. To ustawienie może spowodować awarię starszych urządzeń o mniejszej pamięci.</string>
  <string id="SettingsWifiLteExecutionEnable">Włącz wykonywanie poleceń przez Wi-Fi/LTE.</string>
  <string id="SettingsVibration">Czy aplikacja powinna przekazywać informacje zwrotne za pośrednictwem wibracji?</string>
  <string id="SettingsAppTimeout">Limit czasu w sekundach. Wyjdź z aplikacji po tym okresie bezczynności, aby zapisać akumulator urządzenia.</string>
--- a/resources-por/strings/strings.xml
+++ b/resources-por/strings/strings.xml
@@ -32,6 +32,7 @@
  <string id="GlanceMenu" scope="glance">Menu</string>
  <string id="Memory" scope="glance">Memória</string>
  <string id="MenuUpdated">Menu Atualizado, reinicie.</string>
+  <string id="MenuCheckDisabled">Atualizações de menu desativadas.</string>
  <string id="NoAPIKey" scope="glance">Nenhuma chave da API nas configurações do aplicativo.</string>
  <string id="NoApiUrl" scope="glance">Nenhum URL da API nas configurações do aplicativo.</string>
  <string id="NoConfigUrl" scope="glance">Nenhum URL de configuração nas configurações do aplicativo.</string>
@@ -63,6 +64,7 @@
  <string id="SettingsConfigUrl">URL para configuração de menu (JSON).</string>
  <string id="SettingsCacheConfig">O aplicativo deve cache a configuração do menu?</string>
  <string id="SettingsClearCache">O aplicativo deve limpar o cache existente na próxima vez que for iniciado?</string>
+  <string id="SettingsEnableMenuUpdateCheck">Verifique se há atualizações de menu no aplicativo Start? NOTA: O cache do menu deve ser ativado. Essa configuração pode causar dispositivos mais antigos com menos memória falha.</string>
  <string id="SettingsWifiLteExecutionEnable">Habilite os comandos de execução sobre Wi-Fi/LTE.</string>
  <string id="SettingsVibration">O aplicativo deve fornecer feedback por meio de vibrações?</string>
  <string id="SettingsAppTimeout">Tempo limite em segundos. Saia do aplicativo após esse período de inatividade para salvar a bateria do dispositivo.</string>
--- a/resources-ron/strings/strings.xml
+++ b/resources-ron/strings/strings.xml
@@ -32,6 +32,7 @@
  <string id="GlanceMenu" scope="glance">Meniu</string>
  <string id="Memory" scope="glance">Memorie</string>
  <string id="MenuUpdated">Meniu actualizat, reporniți.</string>
+  <string id="MenuCheckDisabled">Actualizări de meniu dezactivate.</string>
  <string id="NoAPIKey" scope="glance">Nici o cheie API în setările aplicației.</string>
  <string id="NoApiUrl" scope="glance">Fără URL API în setările aplicației.</string>
  <string id="NoConfigUrl" scope="glance">Fără URL de configurare în setările aplicației.</string>
@@ -63,6 +64,7 @@
  <string id="SettingsConfigUrl">URL pentru configurația meniului (JSON).</string>
  <string id="SettingsCacheConfig">Aplicația cache ar trebui să fie configurația meniului?</string>
  <string id="SettingsClearCache">Aplicația ar trebui să șterge cache -ul existent data viitoare când va fi pornită?</string>
+  <string id="SettingsEnableMenuUpdateCheck">Verificați actualizările meniului la pornirea aplicației? NOTĂ: Cachingul de meniu trebuie activat. Această setare poate provoca prăbușirea dispozitivelor mai vechi cu mai puțină memorie.</string>
  <string id="SettingsWifiLteExecutionEnable">Activați executarea comenzilor prin Wi-Fi/LTE.</string>
  <string id="SettingsVibration">Aplicația ar trebui să ofere feedback prin vibrații?</string>
  <string id="SettingsAppTimeout">Timeout în câteva secunde. Ieșiți din aplicație după această perioadă de inactivitate pentru a economisi bateria dispozitivului.</string>
--- a/resources-slo/strings/strings.xml
+++ b/resources-slo/strings/strings.xml
@@ -32,6 +32,7 @@
  <string id="GlanceMenu" scope="glance">Ponuka</string>
  <string id="Memory" scope="glance">Pamiatka</string>
  <string id="MenuUpdated">Aktualizované menu, reštart.</string>
+  <string id="MenuCheckDisabled">Aktualizácie ponuky zakázané.</string>
  <string id="NoAPIKey" scope="glance">V nastaveniach aplikácie chýba kľúč API</string>
  <string id="NoApiUrl" scope="glance">V nastaveniach aplikácie chýba adresa URL rozhrania API</string>
  <string id="NoConfigUrl" scope="glance">V nastaveniach aplikácie chýba konfiguračná adresa URL</string>
@@ -63,6 +64,7 @@
  <string id="SettingsConfigUrl">URL pre konfiguráciu ponuky (JSON).</string>
  <string id="SettingsCacheConfig">Mala by sa aplikácia vyrovnávať konfiguráciu ponuky?</string>
  <string id="SettingsClearCache">Mala by aplikácia vymazať existujúcu vyrovnávaciu pamäť nabudúce, keď sa začne?</string>
+  <string id="SettingsEnableMenuUpdateCheck">Skontrolujte aktualizácie ponuky na spustení aplikácie? Poznámka: Musí sa povoliť ukladanie do vyrovnávacej pamäte ponuky. Toto nastavenie môže spôsobiť staršie zariadenia s menšou pamäťou.</string>
  <string id="SettingsWifiLteExecutionEnable">Povoliť vykonávanie príkazov cez Wi-Fi/LTE.</string>
  <string id="SettingsVibration">Mala by aplikácia poskytovať spätnú väzbu prostredníctvom vibrácií?</string>
  <string id="SettingsAppTimeout">Časový limit v sekundách. Opustite aplikáciu po tomto období nečinnosti, aby ste uložili batériu zariadenia.</string>
--- a/resources-slv/strings/strings.xml
+++ b/resources-slv/strings/strings.xml
@@ -32,6 +32,7 @@
  <string id="GlanceMenu" scope="glance">Meni</string>
  <string id="Memory" scope="glance">Spomin</string>
  <string id="MenuUpdated">Meni posodobljen, znova zaženite.</string>
+  <string id="MenuCheckDisabled">Posodobitve menija onemogočene.</string>
  <string id="NoAPIKey" scope="glance">V nastavitvah aplikacije ni ključa API -ja.</string>
  <string id="NoApiUrl" scope="glance">V nastavitvah aplikacije ni URL API -ja.</string>
  <string id="NoConfigUrl" scope="glance">V nastavitvah aplikacije ni URL konfiguracije.</string>
@@ -63,6 +64,7 @@
  <string id="SettingsConfigUrl">URL za konfiguracijo menija (JSON).</string>
  <string id="SettingsCacheConfig">Ali naj aplikacija predpomni konfiguracija menija?</string>
  <string id="SettingsClearCache">Ali bi morala aplikacija očistiti obstoječi predpomnilnik naslednjič, ko se začne?</string>
+  <string id="SettingsEnableMenuUpdateCheck">Preverite, ali posodobitve menijev pri zagonu aplikacije? OPOMBA: Omogoči mora biti predpomnjenje menija. Ta nastavitev lahko povzroči, da se starejše naprave z manj pomnilnika zrušijo.</string>
  <string id="SettingsWifiLteExecutionEnable">Omogoči izvajanje ukazov prek Wi-Fi/LTE.</string>
  <string id="SettingsVibration">Ali bi morala aplikacija posredovati povratne informacije z vibracijami?</string>
  <string id="SettingsAppTimeout">Časovna omejitev v nekaj sekundah. Po tem obdobju neaktivnosti zapustite aplikacijo, da shranite baterijo naprave.</string>
--- a/resources-spa/strings/strings.xml
+++ b/resources-spa/strings/strings.xml
@@ -32,6 +32,7 @@
  <string id="GlanceMenu" scope="glance">Menú</string>
  <string id="Memory" scope="glance">Memoria</string>
  <string id="MenuUpdated">Menú actualizado, reiniciar.</string>
+  <string id="MenuCheckDisabled">Actualizaciones de menú deshabilitadas.</string>
  <string id="NoAPIKey" scope="glance">No hay clave API en la configuración de la aplicación.</string>
  <string id="NoApiUrl" scope="glance">No hay URL de API en la configuración de la aplicación.</string>
  <string id="NoConfigUrl" scope="glance">No hay URL de configuración en la configuración de la aplicación.</string>
@@ -63,6 +64,7 @@
  <string id="SettingsConfigUrl">URL para la configuración del menú (JSON).</string>
  <string id="SettingsCacheConfig">¿Debería la aplicación almacenar en caché la configuración del menú?</string>
  <string id="SettingsClearCache">¿Debería la aplicación borrar el caché existente la próxima vez que se inicie?</string>
+  <string id="SettingsEnableMenuUpdateCheck">¿Verifica las actualizaciones de menú en la aplicación Inicio? Nota: El almacenamiento en caché del menú debe estar habilitado. Esta configuración puede hacer que los dispositivos más antiguos con menos memoria se bloqueen.</string>
  <string id="SettingsWifiLteExecutionEnable">Habilite la ejecución de comandos sobre Wi-Fi/LTE.</string>
  <string id="SettingsVibration">¿Debería la aplicación proporcionar comentarios a través de vibraciones?</string>
  <string id="SettingsAppTimeout">Tiempo de espera en segundos. Salga de la aplicación después de este período de inactividad para guardar la batería del dispositivo.</string>
--- a/resources-swe/strings/strings.xml
+++ b/resources-swe/strings/strings.xml
@@ -32,6 +32,7 @@
  <string id="GlanceMenu" scope="glance">Meny</string>
  <string id="Memory" scope="glance">Minne</string>
  <string id="MenuUpdated">Meny Uppdaterad, omstart.</string>
+  <string id="MenuCheckDisabled">Menyuppdateringar inaktiverade.</string>
  <string id="NoAPIKey" scope="glance">Ingen API -nyckel i applikationsinställningarna.</string>
  <string id="NoApiUrl" scope="glance">Ingen API -URL i applikationsinställningarna.</string>
  <string id="NoConfigUrl" scope="glance">Ingen konfigurations -URL i applikationsinställningarna.</string>
@@ -63,6 +64,7 @@
  <string id="SettingsConfigUrl">URL för menykonfiguration (JSON).</string>
  <string id="SettingsCacheConfig">Bör applikationen cache menykonfigurationen?</string>
  <string id="SettingsClearCache">Bör applikationen rensa den befintliga cachen nästa gång den startas?</string>
+  <string id="SettingsEnableMenuUpdateCheck">Kontrollera om menyuppdateringar vid applikationsstart? Obs: Meny Caching måste vara aktiverad. Denna inställning kan orsaka äldre enheter med mindre minne att krascha.</string>
  <string id="SettingsWifiLteExecutionEnable">Aktivera körkommandon över Wi-Fi/LTE.</string>
  <string id="SettingsVibration">Bör applikationen ge feedback via vibrationer?</string>
  <string id="SettingsAppTimeout">Timeout på några sekunder. Exit the application after this period of inactivity to save the device battery.</string>
--- a/resources-tha/strings/strings.xml
+++ b/resources-tha/strings/strings.xml
@@ -32,6 +32,7 @@
  <string id="GlanceMenu" scope="glance">เมนู</string>
  <string id="Memory" scope="glance">หน่วยความจำ</string>
  <string id="MenuUpdated">อัปเดตเมนูรีสตาร์ท</string>
+  <string id="MenuCheckDisabled">การอัปเดตเมนูปิดใช้งาน</string>
  <string id="NoAPIKey" scope="glance">ไม่มีคีย์ API ในการตั้งค่าแอปพลิเคชัน</string>
  <string id="NoApiUrl" scope="glance">ไม่มี URL API ในการตั้งค่าแอปพลิเคชัน</string>
  <string id="NoConfigUrl" scope="glance">ไม่มี URL การกำหนดค่าในการตั้งค่าแอปพลิเคชัน</string>
@@ -63,6 +64,7 @@
  <string id="SettingsConfigUrl">URL สำหรับการกำหนดค่าเมนู (JSON)</string>
  <string id="SettingsCacheConfig">แอปพลิเคชันควรแคชการกำหนดค่าเมนูหรือไม่?</string>
  <string id="SettingsClearCache">แอปพลิเคชันควรล้างแคชที่มีอยู่ครั้งต่อไปในครั้งต่อไปหรือไม่</string>
+  <string id="SettingsEnableMenuUpdateCheck">ตรวจสอบการอัปเดตเมนูบนแอปพลิเคชันเริ่มต้นหรือไม่ หมายเหตุ: การแคชเมนูจะต้องเปิดใช้งานการตั้งค่านี้อาจทำให้อุปกรณ์เก่าที่มีหน่วยความจำน้อยลง</string>
  <string id="SettingsWifiLteExecutionEnable">เปิดใช้งานการดำเนินการคำสั่งผ่าน Wi-Fi/LTE</string>
  <string id="SettingsVibration">แอปพลิเคชันควรให้ข้อเสนอแนะผ่านการสั่นสะเทือนหรือไม่?</string>
  <string id="SettingsAppTimeout">หมดเวลาในไม่กี่วินาที ออกจากแอปพลิเคชันหลังจากช่วงเวลาที่ไม่มีการใช้งานเพื่อประหยัดแบตเตอรี่อุปกรณ์</string>
--- a/resources-tur/strings/strings.xml
+++ b/resources-tur/strings/strings.xml
@@ -32,6 +32,7 @@
  <string id="GlanceMenu" scope="glance">Menü</string>
  <string id="Memory" scope="glance">Hafıza</string>
  <string id="MenuUpdated">Menü güncellendi, yeniden başlat.</string>
+  <string id="MenuCheckDisabled">Menü güncellemeleri devre dışı.</string>
  <string id="NoAPIKey" scope="glance">Uygulama ayarlarında API anahtarı yok.</string>
  <string id="NoApiUrl" scope="glance">Uygulama ayarlarında API URL'si yok.</string>
  <string id="NoConfigUrl" scope="glance">Uygulama ayarlarında yapılandırma URL'si yok.</string>
@@ -63,6 +64,7 @@
  <string id="SettingsConfigUrl">Menü yapılandırması için URL (JSON).</string>
  <string id="SettingsCacheConfig">Uygulama menü yapılandırmasını önbelleğe almalı mı?</string>
  <string id="SettingsClearCache">Uygulama bir dahaki sefere başladığında mevcut önbelleği temizlemeli mi?</string>
+  <string id="SettingsEnableMenuUpdateCheck">Uygulama başlangıcında menü güncellemelerini kontrol edin? Not: Menü önbellekleme etkinleştirilmelidir. Bu ayar daha az belleğe sahip eski cihazların çökmesine neden olabilir.</string>
  <string id="SettingsWifiLteExecutionEnable">Wi-Fi/LTE üzerinden komutların yürütülmesini etkinleştirin.</string>
  <string id="SettingsVibration">Uygulama titreşimlerle geri bildirim sağlamalı mı?</string>
  <string id="SettingsAppTimeout">Saniyeler içinde zaman aşımı. Cihaz bataryasını kaydetmek için bu hareketsizlik döneminden sonra uygulamadan çıkın.</string>
--- a/resources-ukr/strings/strings.xml
+++ b/resources-ukr/strings/strings.xml
@@ -32,6 +32,7 @@
  <string id="GlanceMenu" scope="glance">Меню</string>
  <string id="Memory" scope="glance">Пам'ять</string>
  <string id="MenuUpdated">Меню оновлено, перезапустіть.</string>
+  <string id="MenuCheckDisabled">Оновлення меню вимкнено.</string>
  <string id="NoAPIKey" scope="glance">Немає ключа API в налаштуваннях програми.</string>
  <string id="NoApiUrl" scope="glance">Немає URL -адреси API в налаштуваннях програми.</string>
  <string id="NoConfigUrl" scope="glance">Немає URL -адреси конфігурації в налаштуваннях програми.</string>
@@ -63,6 +64,7 @@
  <string id="SettingsConfigUrl">URL -адреса для конфігурації меню (JSON).</string>
  <string id="SettingsCacheConfig">Чи повинен додатковий кеш конфігурації меню?</string>
  <string id="SettingsClearCache">Чи повинен програма очистити існуючий кеш наступного разу, коли він буде запущений?</string>
+  <string id="SettingsEnableMenuUpdateCheck">Перевірте наявність оновлень меню щодо запуску програми? ПРИМІТКА: Меню кешування необхідно увімкнути. Це налаштування може спричинити аварію старіші пристрої з меншою пам'яттю.</string>
  <string id="SettingsWifiLteExecutionEnable">Увімкнути виконання команд над Wi-Fi/LTE.</string>
  <string id="SettingsVibration">Чи повинен програма надавати зворотній зв'язок через вібрації?</string>
  <string id="SettingsAppTimeout">Тайм -аут за лічені секунди. Вийдіть із програми після цього періоду бездіяльності, щоб зберегти акумулятор пристрою.</string>
--- a/resources-vie/strings/strings.xml
+++ b/resources-vie/strings/strings.xml
@@ -32,6 +32,7 @@
  <string id="GlanceMenu" scope="glance">Menu</string>
  <string id="Memory" scope="glance">Ký ức</string>
  <string id="MenuUpdated">Menu được cập nhật, khởi động lại.</string>
+  <string id="MenuCheckDisabled">Cập nhật menu bị vô hiệu hóa.</string>
  <string id="NoAPIKey" scope="glance">Không có khóa API trong cài đặt ứng dụng.</string>
  <string id="NoApiUrl" scope="glance">Không có URL API trong cài đặt ứng dụng.</string>
  <string id="NoConfigUrl" scope="glance">Không có URL cấu hình trong cài đặt ứng dụng.</string>
@@ -63,6 +64,7 @@
  <string id="SettingsConfigUrl">URL cho cấu hình menu (JSON).</string>
  <string id="SettingsCacheConfig">Bộ đệm ứng dụng có nên cấu hình menu không?</string>
  <string id="SettingsClearCache">Ứng dụng có nên xóa bộ đệm hiện tại vào lần tới khi nó được bắt đầu không?</string>
+  <string id="SettingsEnableMenuUpdateCheck">Kiểm tra cập nhật menu khi bắt đầu ứng dụng? Lưu ý: Bộ nhớ đệm menu phải được bật. Cài đặt này có thể khiến các thiết bị cũ hơn có ít bộ nhớ gặp sự cố.</string>
  <string id="SettingsWifiLteExecutionEnable">Bật các lệnh thực thi qua Wi-Fi/LTE.</string>
  <string id="SettingsVibration">Ứng dụng có nên cung cấp phản hồi thông qua các rung động?</string>
  <string id="SettingsAppTimeout">Thời gian chờ trong giây. Thoát khỏi ứng dụng sau khoảng thời gian không hoạt động để lưu pin thiết bị.</string>
--- a/resources-zhs/strings/strings.xml
+++ b/resources-zhs/strings/strings.xml
@@ -32,6 +32,7 @@
  <string id="GlanceMenu" scope="glance">菜单</string>
  <string id="Memory" scope="glance">记忆</string>
  <string id="MenuUpdated">菜单更新，重新启动。</string>
+  <string id="MenuCheckDisabled">菜单更新禁用。</string>
  <string id="NoAPIKey" scope="glance">应用程序设置中没有API密钥。</string>
  <string id="NoApiUrl" scope="glance">应用程序设置中没有API URL。</string>
  <string id="NoConfigUrl" scope="glance">应用程序设置中没有配置URL。</string>
@@ -63,6 +64,7 @@
  <string id="SettingsConfigUrl">菜单配置的URL（JSON）。</string>
  <string id="SettingsCacheConfig">应用程序缓存菜单配置应该缓存吗？</string>
  <string id="SettingsClearCache">应用程序下次启动时是否应该清除现有的高速缓存？</string>
+  <string id="SettingsEnableMenuUpdateCheck">检查应用程序启动时的菜单更新吗？注意：必须启用菜单缓存。此设置可能会导致较旧的设备，而内存较小。</string>
  <string id="SettingsWifiLteExecutionEnable">在Wi-Fi/LTE上启用执行命令。</string>
  <string id="SettingsVibration">应用程序是否应该通过振动提供反馈？</string>
  <string id="SettingsAppTimeout">超时几秒钟。在此不活动期间退出应用程序以节省设备电池。</string>
--- a/resources-zht/strings/strings.xml
+++ b/resources-zht/strings/strings.xml
@@ -32,6 +32,7 @@
  <string id="GlanceMenu" scope="glance">菜單</string>
  <string id="Memory" scope="glance">記憶</string>
  <string id="MenuUpdated">菜單更新，重新啟動。</string>
+  <string id="MenuCheckDisabled">菜單更新禁用。</string>
  <string id="NoAPIKey" scope="glance">應用程序設置中沒有API密鑰。</string>
  <string id="NoApiUrl" scope="glance">應用程序設置中沒有API URL。</string>
  <string id="NoConfigUrl" scope="glance">應用程序設置中沒有配置URL。</string>
@@ -63,6 +64,7 @@
  <string id="SettingsConfigUrl">菜單配置的URL（JSON）。</string>
  <string id="SettingsCacheConfig">應用程序緩存菜單配置應該緩存嗎？</string>
  <string id="SettingsClearCache">應用程序下次啟動時是否應該清除現有的高速緩存？</string>
+  <string id="SettingsEnableMenuUpdateCheck">檢查應用程序啟動時的菜單更新嗎？注意：必須啟用菜單緩存。此設置可能會導致較舊的設備，而內存較小。</string>
  <string id="SettingsWifiLteExecutionEnable">在Wi-Fi/LTE上啟用執行命令。</string>
  <string id="SettingsVibration">應用程序是否應該通過振動提供反饋？</string>
  <string id="SettingsAppTimeout">超時幾秒鐘。在此不活動期間退出應用程序以節省設備電池。</string>
--- a/resources-zsm/strings/strings.xml
+++ b/resources-zsm/strings/strings.xml
@@ -32,6 +32,7 @@
  <string id="GlanceMenu" scope="glance">Menu</string>
  <string id="Memory" scope="glance">Ingatan</string>
  <string id="MenuUpdated">Menu dikemas kini, mulakan semula.</string>
+  <string id="MenuCheckDisabled">Kemas kini menu dilumpuhkan.</string>
  <string id="NoAPIKey" scope="glance">Tiada kunci API dalam tetapan aplikasi.</string>
  <string id="NoApiUrl" scope="glance">Tiada URL API dalam tetapan aplikasi.</string>
  <string id="NoConfigUrl" scope="glance">Tiada URL Konfigurasi dalam Tetapan Aplikasi.</string>
@@ -63,6 +64,7 @@
  <string id="SettingsConfigUrl">URL untuk Konfigurasi Menu (JSON).</string>
  <string id="SettingsCacheConfig">Sekiranya aplikasi cache konfigurasi menu?</string>
  <string id="SettingsClearCache">Sekiranya permohonan membersihkan cache yang sedia ada pada masa akan datang, ia bermula?</string>
+  <string id="SettingsEnableMenuUpdateCheck">Semak kemas kini menu pada permulaan aplikasi? Nota: Caching menu mesti diaktifkan. Tetapan ini boleh menyebabkan peranti yang lebih lama dengan memori yang kurang untuk kemalangan.</string>
  <string id="SettingsWifiLteExecutionEnable">Dayakan perintah melaksanakan melalui Wi-Fi/LTE.</string>
  <string id="SettingsVibration">Sekiranya permohonan memberikan maklum balas melalui getaran?</string>
  <string id="SettingsAppTimeout">Tamat masa dalam beberapa saat. Keluar dari permohonan selepas tempoh tidak aktif ini untuk menyimpan bateri peranti.</string>
--- a/resources/settings/properties.xml
+++ b/resources/settings/properties.xml
@@ -38,6 +38,22 @@
  -->
  <property id="clear_cache" type="boolean">false</property>

+  <!--
+    Enables checking of the menu definition URL for updates each time the
+    application is started. Only if menu caching is enabled, then if a menu
+    update is detected, the new menu definition is downloaded and cached ready
+    for an application restart. This menu item will be disabled by the application
+    if:
+      1. The menu caching is disabled or,
+      2. if a `Communications.INVALID_HTTP_BODY_IN_NETWORK_RESPONSE` API response
+         is encountered indicating that the Garmin device is short of memory, or
+      3. The device has < 10% memory left prior to calling the API.
+
+    Off by default due to the chance an old device will crash by default with an
+    "Out of Memory" error. At least let the application work before enabling.
+  -->
+  <property id="enable_menu_update_check" type="boolean">false</property>
+
  <!--
    Enables the SyncDelegate and prompt to send a command over Wi-Fi/LTE.
    This will only show when not connected to the user's phone.
--- a/resources/settings/settings.xml
+++ b/resources/settings/settings.xml
@@ -51,6 +51,13 @@
    <settingConfig type="boolean" />
  </setting>

+  <setting
+    propertyKey="@Properties.enable_menu_update_check"
+    title="@Strings.SettingsEnableMenuUpdateCheck"
+  >
+    <settingConfig type="boolean" />
+  </setting>
+
  <setting
    propertyKey="@Properties.wifi_lte_execution"
    title="@Strings.SettingsWifiLteExecutionEnable"
--- a/resources/strings/strings.xml
+++ b/resources/strings/strings.xml
@@ -26,6 +26,7 @@
  <string id="GlanceMenu" scope="glance">Menu</string>
  <string id="Memory" scope="glance">Memory</string>
  <string id="MenuUpdated">Menu updated, restart.</string>
+  <string id="MenuCheckDisabled">Menu updates disabled.</string>
  <string id="NoAPIKey" scope="glance">No API key in the application settings.</string>
  <string id="NoApiUrl" scope="glance">No API URL in the application settings.</string>
  <string id="NoConfigUrl" scope="glance">No configuration URL in the application settings.</string>
@@ -58,6 +59,7 @@
  <string id="SettingsConfigUrl">URL for menu configuration (JSON).</string>
  <string id="SettingsCacheConfig">Should the application cache the menu configuration?</string>
  <string id="SettingsClearCache">Should the application clear the existing cache next time it is started?</string>
+  <string id="SettingsEnableMenuUpdateCheck">Check for menu updates on application start? Note: Menu caching must be enabled.This setting may cause older devices with less memory to crash.</string>
  <string id="SettingsWifiLteExecutionEnable">Enable executing commands over Wi-Fi/LTE.</string>
  <string id="SettingsVibration">Should the application provide feedback via vibrations?</string>
  <string id="SettingsAppTimeout">Timeout in seconds. Exit the application after this period of inactivity to save the device battery.</string>
--- a/source/Globals.mc
+++ b/source/Globals.mc
@@ -31,8 +31,9 @@ class Globals {
    //! an ErrorView.
    static const scApiResumeMs          = 200;  // ms

-    //! Warn the user after fetching the menu if their watch is low on memory before the device crashes.
-    static const scLowMem               = 0.90; // percent as a fraction.
+    //! Threshold of memory usage (guessed) to consider a device unable to automatically check
+    //! for a more recent menu due to insufficient memory.
+    static const scLowMem               = 0.85;  // Fraction of total memory used.

    //! Constant for PIN confirmation dialog.<br>
    //! Maximum number of failed PIN confirmation attempts allowed in `scPinMaxFailureMinutes`.
@@ -49,4 +50,9 @@ class Globals {
    //! After running a task by Wi-Fi/LTE synchronisation the periodic updates need to resume. This
    //! is the delay between synchronisation completion and resumption of updates.
    static const wifiPollResumeDelayMs  = 2000; // ms
+
+    //! After running a task by Wi-Fi/LTE synchronisation the if the menu item requests to quit the
+    //! application, this is the delay to wait after synchronisation completion before quitting.
+    //! Failure to wait causes the transfer to indicate a failure.
+    static const wifiQuitDelayMs        = 5000; // ms
 }
--- a/source/HomeAssistantApp.mc
+++ b/source/HomeAssistantApp.mc
@@ -302,9 +302,8 @@ class HomeAssistantApp extends Application.AppBase {
        )
    ) {
        // System.println("HomeAssistantApp fetchMenuConfigBasic(): Fetching JSON menu.");
-        var phoneConnected    = System.getDeviceSettings().phoneConnected;
        var internetAvailable = System.getDeviceSettings().connectionAvailable;
-        if (! phoneConnected or ! internetAvailable) {
+        if (! System.getDeviceSettings().phoneConnected or ! internetAvailable) {
            // System.println("HomeAssistantApp fetchMenuConfigBasic(): No Phone connection, skipping API call.");
            var errorRez = $.Rez.Strings.NoPhone;
            if (Settings.getWifiLteExecutionEnabled()) {
@@ -447,6 +446,28 @@ class HomeAssistantApp extends Application.AppBase {
        return true;
    }

+    //! Takes the actions required to disable the check for an updated menu and notify the user.
+    //
+    function disableMenuCheck() as Void {
+        // As we're out of memory, pretend we've checked and don't try again.
+        mIsCacheChecked = true;
+        // Prevent the menu check happening in future.
+        Settings.unsetMenuCheck();
+        // Tell the user
+        var toast = WatchUi.loadResource($.Rez.Strings.MenuCheckDisabled) as Lang.String;
+        if (mHasToast) {
+            WatchUi.showToast(toast, null);
+        } else {
+            new Alert({
+                :timeout => Globals.scAlertTimeoutMs,
+                :font    => Graphics.FONT_MEDIUM,
+                :text    => toast,
+                :fgcolor => Graphics.COLOR_WHITE,
+                :bgcolor => Graphics.COLOR_BLACK
+            }).pushView(WatchUi.SLIDE_IMMEDIATE);
+        }
+    }
+
    //! Callback function for the menu check GET request.
    //!
    //! @param responseCode Response code.
@@ -483,8 +504,8 @@ class HomeAssistantApp extends Application.AppBase {

            case Communications.NETWORK_RESPONSE_OUT_OF_MEMORY:
                // System.println("HomeAssistantApp onReturnCheckMenuConfig() Response Code: NETWORK_RESPONSE_OUT_OF_MEMORY, are we going too fast?");
+                disableMenuCheck();
                var myTimer = new Timer.Timer();
-                // Now this feels very "closely coupled" to the application, but it is the most reliable method instead of using a timer.
                myTimer.start(method(:updateMenuItems), Globals.scApiBackoffMs, false);
                break;

@@ -576,7 +597,6 @@ class HomeAssistantApp extends Application.AppBase {
            case Communications.NETWORK_RESPONSE_OUT_OF_MEMORY:
                // System.println("HomeAssistantApp onReturnUpdateMenuItems() Response Code: NETWORK_RESPONSE_OUT_OF_MEMORY, are we going too fast?");
                var myTimer = new Timer.Timer();
-                // Now this feels very "closely coupled" to the application, but it is the most reliable method instead of using a timer.
                myTimer.start(method(:updateMenuItems), Globals.scApiBackoffMs, false);
                // Revert status
                status = getApiStatus();
@@ -610,9 +630,19 @@ class HomeAssistantApp extends Application.AppBase {
                                (item as HomeAssistantToggleMenuItem).updateToggleState(data[i.toString() + "t"]);
                            }
                        }
-                        if (Settings.getCacheConfig() && !mIsCacheChecked) {
+                        if (Settings.getMenuCheck() && Settings.getCacheConfig() && !mIsCacheChecked) {
                            // We are caching the menu configuration, so let's fetch it and check if its been updated.
-                            fetchMenuConfigBasic(method(:onReturnCheckMenuConfig));
+                            var stats   = System.getSystemStats(); // stats.* values in bytes
+                            // https://developer.garmin.com/connect-iq/core-topics/debugging/, see "Basic Debugging"
+                            // Create a file on the device called /GARMIN/APPS/LOGS/HOMEASSISTANT.TXT in order to log the values here.
+                            System.println("Memory: total=" + stats.totalMemory + ", used=" + stats.usedMemory + ", free=" + stats.freeMemory);
+                            if (stats.usedMemory > (Globals.scLowMem * stats.totalMemory)) {
+                                // Assume insufficient memory
+                                disableMenuCheck();
+                            } else {
+                                // Assume sufficient memory, but the response code might still turn the automatic check off.
+                                fetchMenuConfigBasic(method(:onReturnCheckMenuConfig));
+                            }
                        } else {
                            var delay = Settings.getPollDelay();
                            if (delay > 0) {
@@ -638,9 +668,9 @@ class HomeAssistantApp extends Application.AppBase {
        if (mUpdating) {
            var phoneConnected      = System.getDeviceSettings().phoneConnected;
            var connectionAvailable = System.getDeviceSettings().connectionAvailable;
-
            // In Wi-Fi/LTE execution mode, we should not show an error page but use a toast instead.
-            if (Settings.getWifiLteExecutionEnabled() && (! phoneConnected || ! connectionAvailable)) {
+            if (Settings.getWifiLteExecutionEnabled() &&
+                (! phoneConnected || ! connectionAvailable)) {
                // Notify only once per disconnection cycle
                if (!mNotifiedNoBle) {
                    var toast = WatchUi.loadResource($.Rez.Strings.NoPhone);
@@ -660,12 +690,10 @@ class HomeAssistantApp extends Application.AppBase {
                        }).pushView(WatchUi.SLIDE_IMMEDIATE);
                    }
                }
-
                mNotifiedNoBle = true;
+                mUpdating      = false;
                setApiStatus(WatchUi.loadResource($.Rez.Strings.Unavailable) as Lang.String);
                mUpdateTimer.start(method(:startUpdates), Globals.wifiPollResumeDelayMs, false);
-
-                mUpdating = false;
                return;
            }

@@ -679,7 +707,6 @@ class HomeAssistantApp extends Application.AppBase {
                setApiStatus(WatchUi.loadResource($.Rez.Strings.Unavailable) as Lang.String);
            } else {
                mNotifiedNoBle = false;
-
                if (mItemsToUpdate == null or mTemplates == null) {
                    mItemsToUpdate = mHaMenu.getItemsToUpdate();
                    mTemplates = {};
@@ -799,7 +826,7 @@ class HomeAssistantApp extends Application.AppBase {
            mApiStatus = WatchUi.loadResource($.Rez.Strings.Unconfigured) as Lang.String;
            WatchUi.requestUpdate();
        } else {
-            if ( mIsApp && Settings.getWifiLteExecutionEnabled() && (! phoneConnected || ! connectionAvailable)) {
+            if (mIsApp && Settings.getWifiLteExecutionEnabled() && (! phoneConnected || ! connectionAvailable)) {
                // System.println("HomeAssistantApp fetchApiStatus(): In-app Wifi mode (No Phone and Internet connection), early return.");
                return;
            } else if (! phoneConnected) {
--- a/source/HomeAssistantSyncDelegate.mc
+++ b/source/HomeAssistantSyncDelegate.mc
@@ -21,7 +21,7 @@ using Toybox.Lang;
 //
 class HomeAssistantSyncDelegate extends Communications.SyncDelegate {
    //! Retain the last synchronisation error.
-    private static var syncError as Lang.String?;
+    private static var mSyncError as Lang.String?;

    //! Class Constructor
    //
@@ -38,9 +38,9 @@ class HomeAssistantSyncDelegate extends Communications.SyncDelegate {
    //! Called by the system when starting a bulk synchronisation.
    //
    public function onStartSync() as Void {
-        syncError = null;
+        mSyncError = null;
        if (WifiLteExecutionConfirmDelegate.mCommandData == null) {
-            syncError = WatchUi.loadResource($.Rez.Strings.WifiLteExecutionDataError) as Lang.String;
+            mSyncError = WatchUi.loadResource($.Rez.Strings.WifiLteExecutionDataError) as Lang.String;
            onStopSync();
            return;
        }
@@ -98,42 +98,48 @@ class HomeAssistantSyncDelegate extends Communications.SyncDelegate {
    //
    public function haCallback(code as Lang.Number, data as Lang.Dictionary?) as Void {
        Communications.notifySyncProgress(100);
-        if (code == 200) {
-            syncError = null;
-            if (WifiLteExecutionConfirmDelegate.mCommandData[:type].equals("entity")) {
-                var callbackMethod = WifiLteExecutionConfirmDelegate.mCommandData[:callback];
-                if (callbackMethod != null) {
-                    var d = data as Lang.Array;
-                    callbackMethod.invoke(d);
-                }
-            }
-            onStopSync();
-            return;
-        }
-
        switch(code) {
            case Communications.NETWORK_REQUEST_TIMED_OUT:
-                syncError = WatchUi.loadResource($.Rez.Strings.TimedOut) as Lang.String;
+                mSyncError = WatchUi.loadResource($.Rez.Strings.TimedOut);
                break;
+            case Communications.NETWORK_RESPONSE_OUT_OF_MEMORY:
            case Communications.INVALID_HTTP_BODY_IN_NETWORK_RESPONSE:
-                syncError = WatchUi.loadResource($.Rez.Strings.NoJson) as Lang.String;
-                syncError = "";
+                mSyncError = WatchUi.loadResource($.Rez.Strings.PotentialError);
+                break;
+            case 404:
+                mSyncError = WatchUi.loadResource($.Rez.Strings.ApiUrlNotFound);
+                break;
+            case 200:
+                mSyncError = null;
+                if (WifiLteExecutionConfirmDelegate.mCommandData[:type].equals("entity")) {
+                    var callbackMethod = WifiLteExecutionConfirmDelegate.mCommandData[:callback];
+                    if (callbackMethod != null) {
+                        callbackMethod.invoke(data as Lang.Array);
+                    }
+                }
+                break;
            default:
-                var codeMsg = WatchUi.loadResource($.Rez.Strings.UnhandledHttpErr) as Lang.String;
-                syncError = codeMsg + code;
+                mSyncError = WatchUi.loadResource($.Rez.Strings.UnhandledHttpErr) + code;
                break;
        }
-
        onStopSync();
    }

    //! Clean up
    //
    public function onStopSync() as Void {
-        if (WifiLteExecutionConfirmDelegate.mCommandData[:exit]) {
-            System.exit();
-        }
+        Communications.notifySyncComplete(mSyncError);
        Communications.cancelAllRequests();
-        Communications.notifySyncComplete(syncError);
+        // Need to delay the exit here or the transfer shows as failed (and it might not be).
+        if (WifiLteExecutionConfirmDelegate.mCommandData[:exit]) {
+            var myTimer = new Timer.Timer();
+            myTimer.start(method(:exit), Globals.wifiQuitDelayMs, false);
+        }
+    }
+
+    //! Required for `method(:exit)` to be able to find a method at all.
+    //
+    public function exit() as Void {
+        System.exit();
    }
 }
--- a/source/HomeAssistantTapMenuItem.mc
+++ b/source/HomeAssistantTapMenuItem.mc
@@ -92,9 +92,9 @@ class HomeAssistantTapMenuItem extends HomeAssistantMenuItem {
                );
            }
        } else if (mConfirm) {
-            var phoneConnected    = System.getDeviceSettings().phoneConnected;
-            var internetAvailable = System.getDeviceSettings().connectionAvailable;
-            if ((! phoneConnected || ! internetAvailable) && Settings.getWifiLteExecutionEnabled()) {
+            if ((! System.getDeviceSettings().phoneConnected ||
+                 ! System.getDeviceSettings().connectionAvailable) &&
+                Settings.getWifiLteExecutionEnabled()) {
                var dialogMsg = WatchUi.loadResource($.Rez.Strings.WifiLtePrompt) as Lang.String;
                var dialog = new WatchUi.Confirmation(dialogMsg);
                WatchUi.pushView(
--- a/source/HomeAssistantToggleMenuItem.mc
+++ b/source/HomeAssistantToggleMenuItem.mc
@@ -104,7 +104,11 @@ class HomeAssistantToggleMenuItem extends WatchUi.ToggleMenuItem {
        if (data == null) {
            setSubLabel(null);
        } else if(data instanceof Lang.String) {
-            setSubLabel(data);
+            // Need to set both labels, you can't just 'setSubLabel(data)' or nothing displays.
+            setSubLabel({
+                :enabled  => data,
+                :disabled => data
+            });
        } else if(data instanceof Lang.Number) {
            var d = data as Lang.Number;
            setSubLabel(d.format("%d"));
@@ -315,10 +319,9 @@ class HomeAssistantToggleMenuItem extends WatchUi.ToggleMenuItem {
        } else if (mConfirm) {
            // Undo the toggle
            setEnabled(!isEnabled());
-
-            var phoneConnected = System.getDeviceSettings().phoneConnected;
-            var internetAvailable = System.getDeviceSettings().connectionAvailable;
-            if ((! phoneConnected || ! internetAvailable) && Settings.getWifiLteExecutionEnabled()) {
+            if ((! System.getDeviceSettings().phoneConnected ||
+                 ! System.getDeviceSettings().connectionAvailable) &&
+                Settings.getWifiLteExecutionEnabled()) {
                wifiPrompt(b);
            } else {
                var confirmationView = new HomeAssistantConfirmation();
--- a/source/Settings.mc
+++ b/source/Settings.mc
@@ -35,6 +35,7 @@ class Settings {
    private static var mConfigUrl             as Lang.String  = "";
    private static var mCacheConfig           as Lang.Boolean = false;
    private static var mClearCache            as Lang.Boolean = false;
+    private static var mMenuCheck             as Lang.Boolean = false;
    private static var mVibrate               as Lang.Boolean = false;
    private static var mWifiLteExecution      as Lang.Boolean = false;
    //! seconds
@@ -68,6 +69,7 @@ class Settings {
        mConfigUrl             = Properties.getValue("config_url");
        mCacheConfig           = Properties.getValue("cache_config");
        mClearCache            = Properties.getValue("clear_cache");
+        mMenuCheck             = Properties.getValue("enable_menu_update_check");
        mWifiLteExecution      = Properties.getValue("wifi_lte_execution");
        mVibrate               = Properties.getValue("enable_vibration");
        mAppTimeout            = Properties.getValue("app_timeout");
@@ -80,6 +82,16 @@ class Settings {
        mUserHeaderName        = Properties.getValue("user_http_header_name");
        mUserHeaderValue       = Properties.getValue("user_http_header_value");
        mClearWebhookId        = Properties.getValue("clear_webhook_id");
+
+        if (mIsApp && mMenuCheck && !mCacheConfig) {
+            unsetMenuCheck();
+            // Tell the user
+            if (WatchUi has :showToast) {
+                WatchUi.showToast(WatchUi.loadResource($.Rez.Strings.MenuCheckDisabled) as Lang.String, null);
+            //} else {
+                // NB. Cannot show an Alert() here.
+            }
+        }
    }

    //! A webhook is required for non-privileged API calls.
@@ -225,6 +237,24 @@ class Settings {
        Properties.setValue("clear_cache", mClearCache);
    }

+    //! Get the menu check Boolean option supplied as part of the Settings.
+    //!
+    //! @return Boolean for whether the menu should be checked for updates when
+    //!         the application is started, and the cache updated ready for the
+    //!         next time the application is restarted.
+    //
+    static function getMenuCheck() as Lang.Boolean {
+        return mMenuCheck;
+    }
+
+    //! Unset the menu check Boolean option supplied as part of the Settings. This
+    //! option should only be set when the menu definition is cached too.
+    //
+    static function unsetMenuCheck() {
+        mMenuCheck = false;
+        Properties.setValue("enable_menu_update_check", mMenuCheck);
+    }
+
    //! Get the value of the Wi-Fi/LTE toggle in settings.
    //!
    //! @return The state of the toggle.
Author	SHA1	Message	Date
Philip Abbey	acdd44564b	2025 09 bug fixes (#285 ) Three bug fixes. 1. Fixed a bug where templates failed to display in toggle menu items (at least on some devices). 2. Fixed a bug where a menu item requesting to exit on completion appeared to indicate failure when using Wi-Fi or LTE. The fix uses a delay in exiting the application modelled as sufficient for a Venu 2 device, so this might need tweaking for other devices. Closes #283. 3. Attempt to fixed an "Out of Memory" bug caused by v3.3 by making automatic checking for menu updates both optional and automatically turned off when insufficient memory is available. This last bug is device dependent and may require another attempt. Closes #284.	2025-09-13 20:09:26 +01:00
Philip Abbey	8db9820ffa	Cosmetic change to docs "Home Assistant" -> "HomeAssistant"	2025-09-13 20:06:10 +01:00
Philip Abbey	3566920114	Documentation update New settings.	2025-09-13 12:05:49 +01:00
Philip Abbey	7ba0d76bf6	Added option to turn off automatic menu update checking This is because it uses additional memory than can cause some older devices to crash unless they have smaller menus.	2025-09-13 11:06:29 +01:00
Philip Abbey	e284cd2d4a	2 Bug fixes 1. Fixed a bug where templates failed to display in toggle menu items (at least on some devices). 2. Fixed a bug where a menu item requesting to exit on completion appeared to indicate failure when using Wi-Fi or LTE. The fix uses a delay in exiting the application modelled as sufficient for a Venu 2 device, so this might need tweaking for other devices.	2025-09-12 14:34:16 +01:00