Internationalisation tidy up

Amended script and application history.

.github/ISSUE_TEMPLATE/blank-issue.md

@@ -0,0 +1,10 @@
+---
+name: Blank issue
+about: Describe this issue template's purpose here.
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,47 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: bug
+assignees: ''
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**IMPORTANT!**
+I have:
+
+- [ ] Used HTTPS to access HomeAssistant (with a public certificate)
+- [ ] Checked that my JSON Syntax is correct ([options 2, 3, or 4](https://github.com/house-of-abbey/GarminHomeAssistant#editing-the-json-file) or otherwise)
+- [ ] Checked that my JSON follows the schema ([options 2, 3, or 4](https://github.com/house-of-abbey/GarminHomeAssistant#editing-the-json-file))
+- [ ] Used the online editor to check my JSON against HomeAssistant ([option 1](https://github.com/house-of-abbey/GarminHomeAssistant#editing-the-json-file))
+- [ ] Checked the [Docs](https://github.com/house-of-abbey/GarminHomeAssistant)
+- [ ] Checked the [Troubleshooting Guide](https://github.com/house-of-abbey/GarminHomeAssistant/blob/main/TroubleShooting.md)
+
+**To Reproduce**
+Steps to reproduce the behavior:
+
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Garmin Device (please complete the following information):**
+
+- Model: [e.g. Venu 2]
+
+**Smartphone (please complete the following information):**
+
+- Device: [e.g. iPhone6]
+- OS: [e.g. iOS8.1]
+
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,20 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: enhancement
+assignees: ''
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

.github/restyled.yml

@@ -0,0 +1,5 @@
+exclude:
+  - '**/*.md'
+  - '**/pnpm-lock.yaml'
+  - 'manifest.xml'
+  - 'manifest-widget.xml'

.github/workflows/translate.yml

@@ -23,11 +23,11 @@ jobs:
         uses: actions/setup-python@v4.7.1
 
       - run: |
-          pip install beautifulsoup4
-          pip install deep-translator
-          pip install lxml
+          pip install google-genai beautifulsoup4 lxml
 
       - run: python translate.py
+        env:
+          GEMINI_API_KEY: ${{ secrets.GEMINI_API_KEY }}
 
       # Commit all changed files back to the repository
       - uses: stefanzweifel/git-auto-commit-action@v5

.gitignore

@@ -2,4 +2,8 @@ bin/
 export/
 **/Thumbs.db
 settings.txt
-export.cmd
+Thumbs.db
+# This file contain credentials, instead provide the empty file ClientId.mc.unpopulated
+source/ClientId.mc
+# Gemini API key for automated translations
+gemini_api_key.txt

.prettierrc

@@ -0,0 +1,10 @@
+{
+  "tabWidth": 2,
+  "useTabs": false,
+  "singleQuote": true,
+  "bracketSameLine": true,
+  "arrowParens": "always",
+  "experimentalTernaries": true,
+  "semi": true,
+  "trailingComma": "es5"
+}

.vscode/settings.json

@@ -2,5 +2,10 @@
   "cSpell.words": [
     "usbs",
     "Venu"
-  ]
+  ],
+  "files.exclude": {
+    "resources-*": true,
+    "bin": true,
+    "export": true
+  }
 }

BackgroundService.md

@@ -0,0 +1,172 @@
+[Home](README.md) | [Switches](examples/Switches.md) | [Actions](examples/Actions.md) | [Templates](examples/Templates.md) | [Glance](examples/Glance.md) | [Background Service](BackgroundService.md) | [Wi-Fi](Wi-Fi.md) | [HTTP Headers](HTTP_Headers.md) | [Trouble Shooting](TroubleShooting.md) | [Version History](HISTORY.md)
+
+# Background Service
+
+The background service can report the following statuses from your device to your Home Assistant:
+
+- Battery Level with charging status.
+- Location and location accuracy.
+- Activity information, but only if your device supports API level 3.2.0. If your device does not support this API level, this information is simply omitted. How do you know? Easiest way is to see if the data is reported.
+
+If your device does not support the background service, the application will clear this setting after you have enabled it. This tells you that you are unable to take advantage of the background reporting service for the functions below.
+
+## Limits
+
+The values are merely samples of your device's current status. They are sent by a single background service at the repetition frequency you chose in the settings. The samples are sent at that one rate only, they _do not vary_ for example on in activity, on charge, time of day. You get one refresh interval and that is it. If you want to change the refresh interval, you change your settings. We do appreciate that may not be what you would ideally like to trigger actions on Home Assistant. Messing with the repeat interval of the background service requires more code, more settings and more complexity. That means older devices using widgets would have to be taken out of support to achieve it.
+
+**Please do not ask for these to be made 'events'.** Garmin's [Connect IQ background service](https://developer.garmin.com/connect-iq/api-docs/Toybox/System/ServiceDelegate.html) is limited in that while it does provide an `onActivityCompleted()` method, it does not provide an `onActivityStarted()` method, so you would not have the complete activity life cycle anyway. So we're keeping this implementation simple, you just get a sampling at one refresh rate. This probably limits you to updating a status on a Home Assistant Dashboard only.
+
+## Battery Reporting
+
+From version 2.1 the application includes a background service to report the current device battery level and charging status back to Home Assistant. This is a feature that Garmin omitted to include with the Bluetooth connection.
+
+## Location Reporting
+
+From version 2.6 the application includes reporting your location. The location data reported includes:
+
+- Location (latitude and longitude)
+- Location accuracy
+- Speed
+- Direction
+- Altitude
+
+You get whatever your device provides at the moment, i.e. at the accuracy the device currently provides. If your watch is not calibrated you get poor data. It might mean that you get more accurate location data when you are in a location tracking activity (i.e. not swimming pool lengths). The device [indicates an accuracy](https://developer.garmin.com/connect-iq/api-docs/Toybox/Position.html#Quality-module) in units of:
+
+- `Position.QUALITY_NOT_AVAILABLE` - No update provided
+- `Position.QUALITY_LAST_KNOWN` - No update provided
+- `Position.QUALITY_POOR` - We translate that to 500 m arbitrarily
+- `Position.QUALITY_USABLE` - We translate that to 100 m arbitrarily
+- `Position.QUALITY_GOOD` - We translate that to 10 m arbitrarily
+
+**You cannot rely on the radius of the circle of accuracy in any resulting maps as any meaningful indication of error.**
+
+## Activity Reporting
+
+From version 2.6 the application includes reporting your activity. The activity data includes:
+
+- Activity - This is an integer as defined by [Toybox.Activity `SPORT`](https://developer.garmin.com/connect-iq/api-docs/Toybox/Activity.html#Sport-module)
+- Sub-activity - This is an integer as defined by [Toybox.Activity `SUB_SPORT`](https://developer.garmin.com/connect-iq/api-docs/Toybox/Activity.html#SubSport-module)
+
+The application only provides the integers without translation. When using the values in Home Assistant, you will need to provide you own mapping from the `Activity` enumerated type to the human readable text. As developers of the application we are pushing this translation to the server to keep the Garmin application code 'lean'. You will also need to add to both the list of activities (sports) and sub-activities (sub-sports) an interpretation of integer `-1` for no activity/sub-activity at present.
+
+## Start Reporting
+
+The main drawback of this solution is that the Garmin application must be run once with the feature enabled in the settings before reporting will start. Reporting continues after you have exited the application. This is a limit we cannot code around.
+
+It should be as simple as starting the application (or widget). There should be a new device in the mobile app integration called `Garmin Watch` with the battery level and charging status.
+
+[![Open your Home Assistant instance and show an integration.](https://my.home-assistant.io/badges/integration.svg)](https://my.home-assistant.io/redirect/integration/?domain=mobile_app)
+
+If this is not the case, head over to the [troubleshooting page](Troubleshooting.md#watch-battery-level-reporting).
+
+## Stop Reporting
+
+To stop the reporting, the option must be turned off in the settings and then the application run once. Running the application then removes the background service. Both the enable and repeat time settings can be changed whilst the application is running (i.e. live) and the background service will be amended.
+
+## Renaming the device
+
+When the device is first created, it will be called `Garmin Watch`. This can be changed in the mobile app integration settings (button below).
+
+[![Open your Home Assistant instance and show an integration.](https://my.home-assistant.io/badges/integration.svg)](https://my.home-assistant.io/redirect/integration/?domain=mobile_app)
+
+Select the device called `Garmin Watch` and then click on the edit icon in the top right corner. You can then change the name of the device to whatever you like, then press `UPDATE` and then `RENAME`.
+
+![Rename device](images/rename_device.png)
+
+![Rename entity ids](images/rename_device_2.png)
+
+## Fixing the icon
+
+In `configuration.yaml`:
+
+```yaml
+template:
+  - sensor:
+      - name: "<device-name> Battery Level"
+        unique_id: "<unique-id>"
+        device_class: "battery"
+        unit_of_measurement: "%"
+        state_class: "measurement"
+        state: "{{ states('sensor.<device>_battery_level') }}"
+        icon: "mdi:battery{% if is_state('binary_sensor.<device>_battery_is_charging', 'on') %}-charging{% endif %}{% if 0 < (states('sensor.<device>_battery_level') | float / 10 ) | round(0) * 10 < 100 %}-{{ (states('sensor.<device>_battery_level') | float / 10 ) | round(0) * 10 }}{% else %}{% if (states('sensor.<device>_battery_level') | float / 10 ) | round(0) * 10 == 0 %}-outline{% else %}{% if is_state('binary_sensor.<device>_battery_is_charging', 'on') %}-100{% endif %}{% endif %}{% endif %}"
+```
+
+## Adding a sample Home Assistant UI widget
+
+A gauge for battery level with a charging icon making use of [mushroom cards](https://github.com/piitaya/lovelace-mushroom), [card_mod](https://github.com/thomasloven/lovelace-card-mod) and [stack-in-card](https://github.com/custom-cards/stack-in-card):
+
+<img src="images/Battery_Guage_Screenshot.png" width="120" title="Battery Gauge"/>
+
+In lovelace:
+
+```yaml
+type: custom:stack-in-card
+direction: vertical
+cards:
+  - type: custom:mushroom-chips-card
+    card_mod:
+      style: |
+        ha-card {
+          height: 0.25rem;
+        }
+    chips:
+      - type: conditional
+        conditions:
+          - condition: state
+            entity: binary_sensor.<device>_battery_is_charging
+            state: "on"
+        chip:
+          type: entity
+          icon_color: yellow
+          entity: sensor.<device>_battery_level
+          content_info: none
+          use_entity_picture: false
+          card_mod:
+            style: |
+              ha-card {
+                border: none !important;
+              }
+      - type: conditional
+        conditions:
+          - condition: state
+            entity: binary_sensor.<device>_battery_is_charging
+            state: "off"
+        chip:
+          type: entity
+          entity: sensor.<device>_battery_level
+          content_info: none
+          use_entity_picture: false
+          card_mod:
+            style: |
+              ha-card {
+                border: none !important;
+              }
+  - type: gauge
+    entity: sensor.<device>_battery_level
+    unit: "%"
+    name: Watch
+    needle: false
+    severity:
+      green: 50
+      yellow: 20
+      red: 0
+    card_mod:
+      style: |
+        ha-card {
+          border: none !important;
+        }
+```
+
+N.B. `sensor.<device>_battery_level` will likely need to be changed to `sensor.<device>_battery_level_2` if you have fixed the icon as above.
+
+## Migrating
+
+You should remove your old template sensors before migrating to the new integration. You can do this by removing the `sensor.<device>_battery_level` and `binary_sensor.<device>_battery_is_charging` entities from `configuration.yaml` and then restarting Home Assistant or reloading the YAML.
+
+[Here is the old configuration method for reference.](https://github.com/house-of-abbey/GarminHomeAssistant/blob/b51e2aa2a4afbc58ad466f3b81667d1cd252d091/BatteryReporting.md)
+
+## Deletion
+
+While all of the entries have the same name, you can identify which to delete by clicking through to its device which should have a changed name from when it was set up.
+
+![Battery Device Deletion](images/Battery_Device_Deletion.png)

HISTORY.md

@@ -0,0 +1,52 @@
+[Home](README.md) | [Switches](examples/Switches.md) | [Actions](examples/Actions.md) | [Templates](examples/Templates.md) | [Glance](examples/Glance.md) | [Background Service](BackgroundService.md) | [Wi-Fi](Wi-Fi.md) | [HTTP Headers](HTTP_Headers.md) | [Trouble Shooting](TroubleShooting.md) | [Version History](HISTORY.md)
+
+# Version History
+
+| Version | Comment |
+|:-------:|---------|
+|   1.0   | Initial release for 26 devices. |
+|   1.1   | Updated for 54 more devices, 80 in total. Scene support. Added vibrate acknowledgement for tap-based menu items. Falls back to a custom visual confirmation in the absence of 'toast' and vibrate support. Bug fix for large menus needing status updates. |
+|   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 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 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 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. |
+|   2.8   | Separation release. The application and widget are no longer joined and now have separate source code repositories. The widget version is now in "maintenance only mode" hence will not receive new features, whilst the application version can now take advantage of not being constrained by the widget's memory limitation, which should allow new features to be added in the future. |
+|   2.9   | Added an option to enable confirmation vibration so it can be turned off by request of a user. Removed a redundant setting for the alternative Widget version that was not removed previously, and fixed a bug with dereferencing Null. |
+|   2.10  | Added a user requested feature to slow down the rate of API calls in order to reduce battery wear for a situation where the application is kept open permanently on the device for convenience. Added 4 new devices. |
+|   2.11  | Bug fix release for menu caching being turned off and language corrections (Czech & Slovenian). |
+|   2.12  | Re-enabled Edge 540 and Edge 840 devices which we are unable to support due to simulator issues, but the Edge 840 device has been confirmed as working by a [Petucky](https://github.com/Petucky). |
+|   2.13  | Moved the template status queries to Webhooks in order to fix the situation where an account is a non-privileged user. Added telemetry update on activity completion to make automations more timely at the end of an activity. When using a polling delay, there is no longer a startup delay for status updates and an action will trigger an immediate round of updates. |
+|   2.14  | Cautionary bug fix for the background service code where refactorisation spoilt some API level guard clauses. |
+|   2.15  | Better support for templates by isolating erroneous returns and marking the menu item. |
+|   2.16  | Bug fix for lack of phone connection when starting the application. Includes new activity reporting features from [KPWhiver](https://github.com/KPWhiver) covering steps, heart rate, floors climbed and descended, and respiration rate. |
+|   2.17  | Bug fix for reporting activity metrics that are not found on some devices. |
+|   2.18  | Bug fix for reporting activity metrics that might be `null` sometimes. This is unsimulatable situation, so this version is a change based on an informed guess. |
+|   2.19  | A template to evaluate is now optionally allowed on both `group` and `toggle` menu items. The template to evaluate is non-optional on a `template` menu item. All updates are performed in a single HTTP GET request for efficiency. Bug fix for negative heading values. Vibration now (optionally) confirms toggle menu items being tapped. |
+|   2.20  | Simplified the code base now that templates have been requested in all menu items. This means the `template` menu item became a superset of `tap`. Therefore the `tap` code has been has been upgraded to include `template` and the latter deprecated. JSON menu definitions continue to support `template` items by instantiating a `tap` menu item, but the schema marks them as deprecated and users should migrate their menu definitions now. Use the [web editor](https://house-of-abbey.github.io/GarminHomeAssistant/web/) for assistance with changes. |
+|   2.21  | Added 7 new devices (`edge1050`, `enduro3`, `fenix843mm`, `fenix847mm`, `fenix8solar47mm`, `fenix8solar51mm`, `fenixe`) and upgraded the SDK to 7.3.0. Fix for a bug on Edge devices introduced by v2.16 activity reporting improvements. |
+|   2.22  | <img src="images/pin_view.png" width="200" title="PIN Entry View"/><br/>Major feature release adding an optional PIN to menu items. This significant new feature has been provided by [moesterheld](https://github.com/moesterheld). Please do not rely on this application for security. Use at your own risk! |
+|   2.23  | Added "info" menu item for displaying information via a template without a tap or toggle. Essentially like the old 'template' type that was deprecated when all items were amended to display evaluated templates. That action removed the display only items too hastily. Added 5 new devices in the model range Instinct 3 and Instinct E. |
+|   2.24  | Experiment to prevent new Webhook IDs being created unnecessarily. Reduced the latency for the first menu update. Added 4 new devices: approachs50, descentg2, descentmk1, and gpsmap66. |
+|   2.25  | 2 Bug fixes. First time startup issues caused by v2.24 change and a fix for pure numbers in returned templates. |
+|   2.26  | Retry responsive menu fix failed in v2.24. Cosmetic internal class changes. |
+|   2.27  | Trivial bug fix for the glance view to prevent the "Unconfigured" result being erroneously displayed because the settings were not yet pulled from persistent storage. |
+|   2.28  | Added support for Vivoactive 6 device which also required an SDK update to 8.1.0. |
+|   2.29  | Added support for three new devices, Forerunners 570 42mm & 47mm and 970. |
+|   2.30  | <img src="images/Venu2_glance_default.png" width="200" title="Default Glance"/><br/>Extensive re-work of the [Glance](examples/Glance.md) view, including the ability to customise it with a user supplied template. |
+|   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 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. Internationalisation improvements with thanks to @krzys_h for a new automated translations script. |

HTTP_Headers.md

@@ -0,0 +1,37 @@
+[Home](README.md) | [Switches](examples/Switches.md) | [Actions](examples/Actions.md) | [Templates](examples/Templates.md) | [Glance](examples/Glance.md) | [Background Service](BackgroundService.md) | [Wi-Fi](Wi-Fi.md) | [HTTP Headers](HTTP_Headers.md) | [Trouble Shooting](TroubleShooting.md) | [Version History](HISTORY.md)
+
+# User Specified Custom HTTP Headers
+
+Principally for those who use HomeAssistant add-on [Cloudflared](https://github.com/brenner-tobias/addon-cloudflared) in order to provide additional security via Cloudflare's Web Application Firewall (WAF). But Garmin does not support certificates in requests. And the solution is generic enough for other use cases.
+
+Please let us know if this solution is found to be useful for other situations.
+
+## Setup
+
+The settings contain two options for users to specify both the HTTP header name and the value as two free form strings.
+
+<img src="images/http_header_settings.png" width="400" title="Application Settings"/>
+
+If you don't know why you need these, leave them empty and ignore.
+
+### Cloudflare WAF rule example
+
+`(any(http.request.headers["your-header-name"][*] eq "your-header-key"))`
+
+Make the key strong enough!
+
+## Support
+
+**None!**
+
+The authors of the Garmin HomeAssistant application do not use, and hence do not know, the [Cloudflared](https://github.com/brenner-tobias/addon-cloudflared) add-on. While we have enabled the HTTP headers to support using this add-on, it does mean _you support yourself_. Please do not raise issues about this functionality unless you are supplying the answers for any required changes too!
+
+## Credits
+
+With thanks to Lars Pöpperl ([@tispokes](https://github.com/tispokes)) for contributing to this solution.
+
+
+## References
+
+* [Using Cloudflare ZeroTrust and mTLS to securely access HomeAssistant via the internet](https://kcore.org/2024/06/28/using-cloudflare-zerotrust-and-mtls-with-home-assistant-via-the-internet/)
+* [HomeAssistant Add-on: Cloudflared](https://github.com/brenner-tobias/addon-cloudflared)

HomeAssistant.code-workspace

@@ -4,5 +4,9 @@
 			"path": "."
 		}
 	],
-	"settings": {}
+	"settings": {
+		"cSpell.words": [
+			"Initialiser"
+		]
+	}
 }

README.md

@@ -1,30 +1,75 @@
+[Home](README.md) | [Switches](examples/Switches.md) | [Actions](examples/Actions.md) | [Templates](examples/Templates.md) | [Glance](examples/Glance.md) | [Background Service](BackgroundService.md) | [Wi-Fi](Wi-Fi.md) | [HTTP Headers](HTTP_Headers.md) | [Trouble Shooting](TroubleShooting.md) | [Version History](HISTORY.md)
+
 # GarminHomeAssistant
 
 <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. 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.
 
-It is important to note that your Home Assistant instance will need to be accessible via HTTPS with public SSL or all requests from the Garmin will not work. This cannot be a self-signed certificate, it must be 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/)).
+**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.
 
-## Application Installation
+**If you are struggling with getting the application to work, please consult the [troubleshooting guide](TroubleShooting.md#menu-configuration-url) first.**
 
-Head over to the [GarminHomeAssistant](https://apps.garmin.com/en-US/apps/61c91d28-ec5e-438d-9f83-39e9f45b199d) application page on the [Connect IQ application store](https://apps.garmin.com/en-US/) to download the application.
+## 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 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 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 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!
+
+## Widget or Application?
+
+As of version 2.0, there are now two installable versions. For older devices before applications supported 'glances', there is a now widget version. These two version must be downloaded separately due to the way the Connect IQ App Store requires them to have separate application IDs. Therefore you need to choose which you want up front. Here's how they compare.
+
+| Version                | Explanation |
+|------------------------|-------------|
+| Application (original) | For newer devices that allow glance views in their applications, e.g. Venu 2, the GarminHomeAssistant application can be started either from a glance or from the list of applications and activities. Head over to the [GarminHomeAssistant](https://apps.garmin.com/en-US/apps/61c91d28-ec5e-438d-9f83-39e9f45b199d) application page on the [Connect IQ application store](https://apps.garmin.com/en-US/) to download the application. The application can be started two different ways, either from the glance in the carousel, or as an application from the list of applications & activities. With the latter, it is worth marking the application as a favourite.<br/><img src="images/Venu2_app_start.png" width="200" title="Venu 2" style="margin:5px"/><img src="images/Vivoactive3_app_start.jpg" width="200" title="Vivoactive 3" style="margin:5px"/><br/>If you place the application on your list of favourites, and rearrange it to appear near the top, then the item is just one button press away from the watch face. This second picture here shows the application menu on a Vivoactive 3 watch.<br/><img src="images/Venu2_glance_default.png" width="200" title="Venu 2" style="margin:5px"/><br/>On newer watches, you can also start the application from the glance carousel. The glance view here typically displays some trackable status, so ours provides some early indication of availability. Older watches will still allow you to start this application from the list of applications and activities. |
+| Widget                 | **"Maintenance only mode"** so no new features will be added to this version.<br>For older devices that use widgets, e.g. Venu (1) as opposed to applications with "glances", the GarminHomeAssistant application can instead be started from the widget carousel. This is a separate item in the Connect IQ AppStore and with this installation, the application will no longer appear in the list of applications and activities. Head over to the [GarminHomeAssistant](https://apps.garmin.com/en-US/apps/) widget page on the [Connect IQ application store](https://apps.garmin.com/en-US/) to download the widget.<br/><img src="images/Venu_Widget_sim.png" width="200" title="Venu 2" style="margin:5px"/><br/>Typically the widget view implements something similar to the glance view, e.g. status, and exists in a widget carousel to allow you to select an application to launch.<br>**Please note that memory in widgets is more limited than applications. This means a large menu definition can crash the widget without the code catching the error.**<br> This version was born out of the application version and from Ver 2.0 shared the same source code repository until Ver 2.8 when they were [separated](https://github.com/house-of-abbey/GarminHomeAssistantWidget) to allow the application version to take advantage of its increase memory availability. |
+
+### Features
+
+The following table lists the differences in functionality between the two. The Widget version is more limited due to memory constraints. As such new features are only being added to the Application.
+
+| Feature | Application | Widget |
+|---------|-------------|--------|
+| Vibration | Optional setting | Always on |
+| "Always on" support | Slow refresh option to reduce batter demand | No available |
+| Metric reporting | Fuller, includes: activity, sub-activity, battery, charging, steps, heart rate, floors ascended and descended, respiration rate | Basic, includes: activity, sub-activity, battery only. |
+
+### Source Code Repositories
+
+* [Application](https://github.com/house-of-abbey/GarminHomeAssistant)
+* [Widget](https://github.com/house-of-abbey/GarminHomeAssistantWidget)
+
+### Connect IQ Store
+
+* [Application](https://apps.garmin.com/en-US/apps/61c91d28-ec5e-438d-9f83-39e9f45b199d)
+* [Widget](https://apps.garmin.com/en-US/apps/559f5174-177f-4f46-b170-f31c7e74dea3)
 
 ## 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 advantage here 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", 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 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`.
 
-Schema verification is a big part of this design choice. If the application cannot read your menu definition, there's a limited amount of debug it can reasonable provide on a small screen. That responsibility now falls to you and the schema checker for help.
+> [!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.
 
-Example schema as shown in the images:
+Schema verification is a big part of this design choice. If the application cannot read your menu definition, there's a limited amount of debug it can reasonably provide on a small screen. That responsibility now falls to you and the schema checker for help.
+
+Example schema:
 
 ```json
 {
@@ -35,7 +80,10 @@ Example schema as shown in the images:
       "entity": "script.food_on_table",
       "name": "Food is Ready!",
       "type": "tap",
-      "service" : "script.turn_on"
+      "tap_action": {
+        "service": "script.turn_on",
+        "confirm": true
+      }
     },
     {
       "entity": "light.bedside_light_switch",
@@ -48,7 +96,6 @@ Example schema as shown in the images:
       "type": "toggle"
     },
     {
-      "entity": "menu.each_lounge_light",
       "name": "Each Lounge Light",
       "title": "Lounge",
       "type": "group",
@@ -84,61 +131,177 @@ Example schema as shown in the images:
       "entity": "automation.turn_off_usb_chargers",
       "name": "Turn off USBs",
       "type": "tap",
-      "service" : "automation.trigger"
+      "tap_action": {
+        "service": "automation.trigger"
+      }
     },
+    {
+      "entity": "scene.tv_light",
+      "name": "TV Lights Scene",
+      "type": "tap",
+      "tap_action": {
+        "service": "scene.turn_on",
+        "pin": true
+      }
+    }
+  ]
+}
+```
+
+NB. Entity names are not real in case anyone's a hacker ;-).
+
+The example above illustrates how to configure:
+
+* Lights or switches (`toggle`), <img src="images/toggle_icon.png" height="20">
+* Enables for automations (`toggle`), <img src="images/toggle_icon.png" height="20">
+* Script invocation (`tap`)
+* Service invocation, e.g. Scene setting, (`tap`)
+* A sub-menu to open (`group`)
+* 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 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)|
+|------------------|:---:|:------:|:------------:|
+| Switch           | ❌ |   ✅  |      ✅      |
+| Light            | ❌ |   ✅  |      ✅      |
+| Automation       | ✅ |   ✅  |      ❌      |
+| Script           | ✅ |   ❌  |      ❌      |
+| Scene            | ✅ |   ❌  |      ❌      |
+| Sensor           | ❌ |   ❌  |      ✅      |
+| Binary Sensor    | ❌ |   ❌  |      ✅      |
+| Any other entity | ❌ |   ❌  |      ✅      |
+| Any service      | ✅ |   ❌  |      ❌      |
+
+Multiple templates are evaluated in a single HTTP request to update their status. Only the toggle items have the on/off <img src="images/toggle_icon.png" height="20"> icon. NB. All `tap` items must specify a `service` tag in the `tap_action` object (see example below).
+
+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 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
+
+Version 1.5 brought in a change to the JSON schema so the following old format remains useable but is no longer favoured. The schema now marks it as 'deprecated' to nudge people over.
+
+```json
     {
       "entity": "scene.tv_light",
       "name": "TV Lights Scene",
       "type": "tap",
       "service": "scene.turn_on"
     }
-  ]
-}
 ```
 
-NB. Entity names are not real in case anyone's a hacker.
+The above should be replaced by the following:
 
-The example above illustrates how to configure:
+```json
+    {
+      "entity": "scene.tv_light",
+      "name": "TV Lights Scene",
+      "type": "tap",
+      "tap_action": {
+        "service": "scene.turn_on"
+      }
+    }
+```
 
-* Light or switch toggles
-* Automation enable toggles
-* Script invocation (tap)
-* Service invocation, e.g. Scene setting, (tap)
-* A sub-menu to open (tap)
+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.
 
-The example JSON shows an example usage of each of these Home Assistance entity types. Presently, an automation is the only one that can be either a 'tap' or a 'toggle'.
+### More Examples
 
-| HA Type    | Tap | Toggle |
-|------------|:---:|:------:|
-| Switch     |  ❌ |   ✅  |
-| Light      |  ❌ |   ✅  |
-| Automation | ✅  |   ✅  |
-| Script     | ✅  |   ❌  |
-| Scene      | ✅  |   ❌  |
+* [Switches](examples/Switches.md)
+* [Actions](examples/Actions.md)
+* [Templates](examples/Templates.md)
 
-NB. All 'tap' items must specify a 'service' tag.
+## Editing the JSON file
 
-Possible future extensions might include specifying the alternative texts to use instead of "On" and "Off", e.g. "Locked" and "Unlocked" (but wouldn't having locks operated from your watch be a security concern ;-))
+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 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.
 
-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.
+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.
+
+A failure to get the file format right tends to mean that the response to the application errors with `INVALID_HTTP_BODY_IN_NETWORK_RESPONSE` (code of -400). This means the response did not contain JSON, it was probably an error message in plain text that could not be parsed by the Connect IQ API call. See [Toybox.Communications](https://developer.garmin.com/connect-iq/api-docs/Toybox/Communications.html) for the list of error code you might be presented with on your device.
+
+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.
+
+Make sure you can browse to the URL of your JSON file in a standard web browser to make sure it is accessible.
 
 ## 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.
+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)
 
-Having created that token, before you dismiss the dialogue box with the value you will never see again, copy it somewhere safe. You need to paste this into the Garmin Application's settings.
+Having created that token, before you dismiss the dialogue box with the value you will never see again, copy it somewhere safe. You need to paste this into the Garmin Application's settings. You may like to perform this task on your phone so that you can copy and paste it (and message yourself a copy too ;-)).
+
+## 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 -> 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)
+
+If you have built your own infrastructure, you really don't need any assistance with the API URL!
 
 ## Settings
 
+Unfortunately the Settings dialogue box in the Garmin IQ application "times out" in Android when you go to a different screen (a browser for example). When you go back to the Connect IQ application (select the view again) the settings dialogue box is broken and you have to open the Settings again, so you will need to save the settings every time before you switch applications to avoid losing the information you just put in. We recommend you can use an application like [Microsoft's "Phone Link"](https://apps.microsoft.com/detail/9NMPJ99VJBWV?hl=en-gb&gl=US) that allows you to *copy and paste* between your PC and your phone.
+
+**Please, please, please!** *Copy and paste* your API key and all URLs, do not retype them as they will be wrong.
+
 <img src="images/GarminHomeAssistantSettings.png" width="400" title="Application Settings"/>
 
-1. 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.)
+1. Copy and paste your API key you've just created into the top field.
+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.
+
+### 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. **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.
+
+### 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 |
+|:-------------------:|:----------:|:--------|
+|          0          |     0      | Permanently open, poll as fast as possible. This is the simple default, but could drain your battery |
+|         > 0         |     0      | Temporarily open, poll as fast as possible, responsive and limits battery drain by closing. |
+|          0          |    > 0     | Permanently open, but poll more gently to save battery. |
+|         > 0         |    > 0     | Temporarily open, poll more gently to save battery, but the application closes before the benefit is realised. Not recommended. |
+
+There is a second timeout value for confirmation views. This is intended for use with more sensitive toggles so that the confirmation view is not left open and forgotten and then confirmed accidentally without you noticing. **We cannot advise you this is safe, be careful what you toggle with the watch application!** _The developers will not be held responsible for any insecurities resulting from using this feature, including any inadvertent code changes that cause the PIN feature to not work._
+
+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?
+
+### 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
 
@@ -146,28 +309,61 @@ 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.
+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 filling up a queue and giving a [Communications](https://developer.garmin.com/connect-iq/api-docs/Toybox/Communications.html).`BLE_QUEUE_FULL` response code.  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!
+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!**
 
-The thinking here is that the watch application will only ever be open briefly not persistently, so the delay in picking up state changes won't be observed often for any race condition between two controllers.
+The thinking here is that the watch application will only ever be open briefly not persistently, so the delay in picking up state changes won't be observed often for any race condition between two controllers. As a consequence of this update mechanism, if you request changes too quickly you will be notified that your device cannot keep up with the rate of API responses and you will have to dismiss the error in order to continue. This is a _feature not a bug_! If the application reduces the rate of "round robin" status update requests it becomes less responsive to external changes.
 
-As a consequence of this update mechanism, if you request changes too quickly you will be notified that your device cannot keep up with the rate of API responses and you will have to dismiss the error in order to continue. The is a _feature not a bug_!
+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
+## Submitting Corrections for Translations
 
-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.
+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.
 
-## Version History
+In order to submit a language correction please create an XML file called `corrections.xml` in the same directory as your language containing the corrected text. The format of the XML file follows that of `strings.xml`. As an example here are some corrected French translations found in directory [`resources-fre/strings/corrections.xml`](https://github.com/house-of-abbey/GarminHomeAssistant/tree/main/resources-fre/strings/corrections.xml):
 
-| Version | Comment |
-|:-------:|---------|
-|   1.0   | Initial release for 26 devices. |
-|   1.1   | Updated for 54 more devices, 80 in total. Scene support. Added vibrate acknowledgement for tap-based menu items. Falls back to a custom visual confirmation in the absence of 'toast' and vibrate support. Bug fix for large menus needing status updates. |
-|   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 [SomeoneOnEarth](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 appologies to anyone suffering a breakage as a result. |
+```xml
+<strings>
+  <string id="MenuItemOn">Activé</string>
+  <string id="MenuItemTap">Clic</string>
+  <string id="ApiFlood">Appels API trop rapide. Veuillez signaler cette erreur avec les détails de l'appareil.</string>
+</strings>
+```
+
+The `id` attribute values are taken from the same names used in [`strings.xml`](https://github.com/house-of-abbey/GarminHomeAssistant/blob/main/resources-fre/strings/strings.xml). **Not all `id` values need to be specified as missing `id`s will then use automatic translations.** If the existing convention is followed then:
+
+* The Python script will use the corrections in preference to translating, and
+* Your pull request will be honoured without comment as we will take your corrections on trust.
+
+## Known Issues
+
+Check the latest unresolved [issues](https://github.com/house-of-abbey/GarminHomeAssistant/issues) on Github. Otherwise the following are persistent issues with no realistic resolution.
+
+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 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!
+
+4. Templates can require significant definition for highly customised text. Just remember, you have the ability to crash the application by creating an excessively long menu definition. Don't be silly.
+
+5. Parameters to tap menu items cannot have their parameter usage verified. If you get this wrong and crash the application, that's your fault not the application's. In this case, start by removing the parameters for the menu item causing the crash, and add them back one at a time until you find your fault. **Please don't give the application a poor review for your bad parameter definition!**
+
+6. We are unable to support Edge 540, Edge 840 and Edge 1050 devices at this time. The simulation of these devices has two unexpected errors when toggling or executing taps. We get both `Communications.NETWORK_RESPONSE_OUT_OF_MEMORY` and `Communications.BLE_QUEUE_FULL` even though the memory usage is about 6% of the available RAM. Based on a lead from user @Petucky, both devices are being re-enabled as testing on a real Edge 840 device has proven successful, however we remain unable to support either devices until the simulator is fixed.
+
+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 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.

TroubleShooting.md

@@ -0,0 +1,350 @@
+[Home](README.md) | [Switches](examples/Switches.md) | [Actions](examples/Actions.md) | [Templates](examples/Templates.md) | [Glance](examples/Glance.md) | [Background Service](BackgroundService.md) | [Wi-Fi](Wi-Fi.md) | [HTTP Headers](HTTP_Headers.md) | [Trouble Shooting](TroubleShooting.md) | [Version History](HISTORY.md)
+
+# Troubleshooting Guides
+
+## Check your JSON Schema
+
+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 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.
+
+A failure to get the file format right tends to mean that the response to the application errors with `INVALID_HTTP_BODY_IN_NETWORK_RESPONSE` (code of -400). This means the response did not contain JSON, it was probably an error message in plain text that could not be parsed by the Connect IQ API call. See [Toybox.Communications](https://developer.garmin.com/connect-iq/api-docs/Toybox/Communications.html) for the list of error code you might be presented with on your device.
+
+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.
+
+Make sure you can browse to the URL of your JSON file in a standard web browser to make sure it is accessible.
+
+## Watch Menu and API
+
+With either of the following setups, there are inevitably some problems along the way. GarminHomeAssistant is careful to rely only on having working URLs. Getting them working is the user's responsibility. However, we have developed some fault finding tools.
+
+### Nabu Casa Setup
+
+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)
+
+- Your API URL would be of the format `https://<id>.ui.nabu.casa/api`
+- Your Garmin Watch Menu would be of the format Menu: `https://<id>.ui.nabu.casa/local/garmin/menu.json`
+
+Where `<id>` is your personal Nabu Casa account ID.
+
+### Do It Yourself Setup
+
+Before Nabu Casa, or if you wanted to manage your own infrastructure, you might have something like the following:
+
+![Do It Yourself Setup](images/do_it_yourself_setup.png)
+
+Now you have to manage:
+
+- Dynamic DNS
+- Public access via router port forwarding
+- Security via HTTPS and URL forwarding
+- Certificates for HTTPS via say [Let's Encrypt](https://letsencrypt.org/) (an Nginx proxy web server helps here)
+- Proxy allow list in `configuration.yaml` as follows:
+
+```yaml
+http:
+  use_x_forwarded_for: true
+  trusted_proxies:
+    - 127.0.0.1
+    - 192.168.xx.xx  # Server IP - AMEND THIS
+    - 172.30.32.0/23 # Docker IPs for NGINX
+    - 172.30.33.0/24 # SSL proxy server
+    - 172.16.0.0/12  #
+```
+
+### Menu Configuration URL
+
+This URL is very simple, you should be able to read the contents returned in a standard web browser.
+
+![Browser Address Bar URL](images/menu_url.png)
+
+(Other browsers are available...)
+
+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 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.
+
+### 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:
+
+```json
+{ "message": "API running." }
+```
+
+#### API: Linux, MacOS, UNIX, Cygwin etc
+
+Save the following as a file called `api_test.sh`, edit to include your personal values for the variables, `chmod +x api_test.sh` and then execute with `./api_test.sh`.
+
+```shell
+#!/bin/bash
+
+API_KEY="<Your API key>"
+URL="https://<Your Domain>/api"
+
+curl -s -X GET \
+  -H "Authorization: Bearer ${API_KEY}" \
+  -H "Content-Type: application/json" \
+  ${URL}/
+```
+
+#### API: MS Windows
+
+Save the following as a file called `api_test.cmd`, edit to include your personal values for the variables and then double click.
+
+```cmd
+@echo off
+
+set API_KEY=<Your API key>
+set URL=https://<Your Domain>/api
+
+curl -s -X GET ^
+  -H "Authorization: Bearer %API_KEY%" ^
+  -H "Content-Type: application/json" ^
+  %URL%/
+
+echo.
+pause
+```
+
+![API Test MS-DOS Output](images/api_test_dos_output.png)
+
+#### API: On-line
+
+There's an online way of testing the API URL too, thanks to [REQBIN](https://reqbin.com/post-online). This has less setup and it can be saved if you log into the web site.
+
+![API Test REQBIN](images/api_test_online.png)
+
+#### SSL Certificate Chain
+
+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 HomeAssistant application.
+3. The Garmin HomeAssistant application reports:
+```
+API: not available
+Menu: not available
+```
+
+**Solution: Make sure you use a _full chain_ certificate in your HTTPS proxy as some watches might be unable to validate the site certificate alone.**
+
+Most web browsers and OSes probably have the latest Certificate Authorities (CAs) trusted out-of-the-box and so they do not need the full chain to verify the certificates. Garmin watches may not have the latest CAs and that is why the Troubleshooting web page does not catch this problem. E.g. It turns out some Garmin watches do not have the LetsEncrypt CA marked as trusted.
+
+To verify if you have this issue you can use a tool like [SSL Shoppers's SSL Checker](https://www.sslshopper.com/ssl-checker.html), which will catch this issue. The following two screen captures illustrate the difference between partial and full chain certificates respectively.
+
+##### Partial Chain Certificate
+
+![Partial Chain Certificate](images/HTTPS_partial_chain.png)
+
+##### Full Chain Certificate
+
+![Full Chain Certificate](images/HTTPS_full_chain.png)
+
+
+### Top Problems
+
+1. Failure to copy & paste keys and URLs leading to minor and hard to see errors in strings, even with protestations they are the same! (No they weren't...)
+2. Accessibility of URLs, hence the above help guide.
+
+## 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 HomeAssistant.
+
+#### Battery: Linux, MacOS, UNIX, Cygwin etc
+
+Assume a file called: `send_battery.bash`
+
+```shell
+#!/bin/bash
+#
+#               battery% charging {0|1}
+# ./send_battery.bash 19 0
+#
+
+WEBHOOK_ID="<Your Webhook ID>"
+URL="https://<Your Domain>/api"
+
+level=${1:-50}
+is_charging=${2:-0}
+echo "Battery Level = ${level}"
+if [ ${is_charging} -eq 1 ]; then
+  is_charging=true
+else
+  is_charging=false
+fi
+echo "Battery Charging? = ${is_charging}"
+echo ""
+
+curl -s -X POST \
+  -H "Content-Type: application/json" \
+  -d '{ "type": "update_sensor_states", "data": [ {"state": '${level}',"type": "sensor","unique_id": "battery_level"}, {"state": '${is_charging}',"type": "binary_sensor","unique_id": "battery_is_charging"} ] }' \
+  ${URL}/webhook/${WEBHOOK_ID}
+```
+
+Execute:
+
+```
+$ ./send_battery.bash 45 1
+```
+
+The output looks like this:
+
+```
+Battery Level = 45
+Battery Charging? = true
+
+{
+  "battery_level": {
+    "success": true
+  },
+  "battery_is_charging": {
+    "success": true
+  }
+}
+
+```
+
+NB. The device ID can be any string for the purposes of this testing. Your Garmin device will choose this ID for you when it submits the readings.
+
+#### Battery: MS Windows
+
+Assume a file called: `home_assistant_battery_level.cmd`
+
+```cmd
+@echo off
+rem               battery% charging {0|1}
+rem ./home_assistant_battery_level 19 0
+rem
+
+set WEBHOOK_ID=<Your Webhook ID>
+set URL=https://<Your Domain>/api
+
+if [%1] == [] (
+  set level=50
+) else (
+  set level=%1
+)
+
+if [%1] == [] (
+  set is_charging=0
+) else (
+  set is_charging=%2
+)
+echo "Battery Level = %level%"
+if "%is_charging%"=="1" (
+  set is_charging=true
+) else (
+  set is_charging=false
+)
+echo "Battery Charging? = %is_charging%"
+echo.
+
+curl -s -X POST ^
+  -H "Content-Type: application/json" ^
+  -d "{ \"type\": \"update_sensor_states\", \"data\": [ {\"state\": %level%,\"type\": \"sensor\",\"unique_id\": \"battery_level\"}, {\"state\": %is_charging%,\"type\": \"binary_sensor\",\"unique_id\": \"battery_is_charging\"} ] }" ^
+  %URL%/webhook/%WEBHOOK_ID%
+
+echo.
+pause
+```
+
+Execute:
+
+```
+> home_assistant_battery_level.cmd 41 1
+```
+
+The output looks like this:
+
+```
+"Battery Level = 41"
+"Battery Charging? = true"
+
+{
+  "battery_level": {
+    "success": true
+  },
+  "battery_is_charging": {
+    "success": true
+  }
+}
+
+Press any key to continue . . .
+```
+
+NB. The device ID can be any string for the purposes of this testing. Your Garmin device will choose this ID for you when it submits the readings.
+
+#### Battery: On-line
+
+There's an online way of testing the API URL too, thanks to [REQBIN](https://reqbin.com/post-online). This has less setup and it can be saved if you log into the web site.
+
+URL for copy & paste:
+
+```
+https://<Your Domain>/api/webhook/<Your Webhook ID>
+```
+
+![API Test REQBIN](images/api_test_online_battery.png)
+
+JSON for copy & paste:
+
+```json
+{
+  "type": "update_sensor_states",
+  "data": [
+    {
+      "state": 40,
+      "type": "sensor",
+      "unique_id": "battery_level"
+    },
+    {
+      "state": true,
+      "type": "binary_sensor",
+      "unique_id": "battery_is_charging"
+    }
+  ]
+}
+```
+
+# Failed API Calls
+
+![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 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:
+
+![Nabu Casa Setup](images/delete_webhook_id.png)
+
+# Debug Logs
+
+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)
+
+The figure above shows how to find the file on Windows by attaching your watch by USB cable. Inside the `CIQ_LOG.YML` file there are often multiple entries, each looking like this:
+
+```
+Error: Unexpected Type Error
+Details: 'Failed invoking <symbol>'
+Time: 2024-08-30T12:00:25Z
+Part-Number: 006-B3703-00
+Firmware-Version: '19.05'
+Language-Code: eng
+ConnectIQ-Version: 4.2.4
+Store-Id: 61c91d28-ec5e-438d-9f83-39e9f45b199d
+Store-Version: 30
+Filename: DCRL0437
+Appname: HomeAssistant
+Stack: 
+  - pc: 0x10003b5e
+```
+
+The only useful information we can glean from this log is the first line, `Error: Unexpected Type Error`. There is no useful mapping to a line of code unless someone can explain to us how to use the `pc` line. Being able to send us the error type does serve as a clue.
+
+More on [debugging Monkey C applications](https://developer.garmin.com/connect-iq/core-topics/debugging/#appcrashes). The filenames and line numbers must only be present for deployment of code instrumented for debug.

Wi-Fi.md

@@ -0,0 +1,43 @@
+[Home](README.md) | [Switches](examples/Switches.md) | [Actions](examples/Actions.md) | [Templates](examples/Templates.md) | [Glance](examples/Glance.md) | [Background Service](BackgroundService.md) | [Wi-Fi](Wi-Fi.md) | [HTTP Headers](HTTP_Headers.md) | [Trouble Shooting](TroubleShooting.md) | [Version History](HISTORY.md)
+
+# 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 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**.
+
+## Limits of Use
+
+1. An API request issued over Wi-Fi requires the watch to open up an IP connection to your Wi-Fi access point. This means setting up a secure channel with WPA and being allocated an IP address. Establishing the communication channel takes a short while. _You will see that this adds a noticeable delay to usability._
+
+2. **The Wi-Fi/LTE functionality can only be used when the menu is already cached.** _The watch will not perform an HTTPS GET request to retrieve the JSON menu file_. Therefore, to enable the Wifi/LTE functionality in the application settings, you must enable caching first.
+
+3. The menu item statuses will not be set correctly. Instead you will be warned about the lack of connectivity by a 'toast', i.e. message partially occupying the top of the screen temporarily. Fetching the menu item statuses, including rendered templates, requires its own API call, hence this not performed.
+
+4. Remember that you need to be within range of your watch's configured Wi-Fi access point to utilize this functionality. If supported by your device, LTE offers a longer range, but network charges may apply.
+
+5. On some Garmin devices, the HTTPS handshake is performed using **TLS 1.2**. If your server or proxy enforces a higher minimum (e.g., TLS 1.3), you will encounter an SSL handshake error with the message:  
+
+   ```
+   HTTP request returned error code = 0
+   ```
+
+   This limitation only affects **Wi-Fi/LTE connections**. When connected over **Bluetooth**, the watch routes requests through the paired phone, which handles the TLS handshake and supports newer TLS versions (such as 1.3) without issue.  
+
+   To fix this, lower the minimum TLS setting to allow TLS 1.2. For example, if you are using **Cloudflare Tunneling**, go to:  
+   `SSL/TLS → Edge Certificates → Minimum TLS Version`  
+   and set it to **at most TLS 1.2**. _Reducing below TLS 1.2 is not recommended due to security risks._
+
+## Video
+
+This video using will hopefully make it obvious how slow it is to use the Wi-Fi option and illustrate the cautionary notes above.
+
+https://github.com/user-attachments/assets/269981e9-12dc-44f2-a28f-b8e844b2b2f8
+
+### Please Note
+
+We emphasize that the Wi-Fi/LTE functionality should be viewed as a 'last resort' method for executing tasks when your phone is not available. It is not recommended as a continuous mode of operation.
+
+## Credits
+
+With thanks to Vincent, [@vincentezw](https://github.com/vincentezw) for contributing this solution, and to Ali Alaei, [@aalaei](https://github.com/aalaei) for the finer details on TLS.

_config.yml

@@ -0,0 +1,3 @@
+exclude:
+- examples
+- source

compile_sim.cmd

@@ -0,0 +1,121 @@
+@echo off
+rem -----------------------------------------------------------------------------------
+rem
+rem  Distributed under MIT Licence
+rem    See https://github.com/house-of-abbey/GarminHomeAssistant/blob/main/LICENSE.
+rem
+rem -----------------------------------------------------------------------------------
+rem
+rem  GarminHomeAssistant is a Garmin IQ application written in Monkey C and routinely
+rem  tested on a Venu 2 device. The source code is provided at:
+rem             https://github.com/house-of-abbey/GarminHomeAssistant.
+rem
+rem  J D Abbey & P A Abbey, 28 December 2022
+rem
+rem  For use when VS Code is misbehaving and failing to recompile before starting a simulation.
+rem
+rem  Reference:
+rem   * Using Monkey C from the Command Line
+rem     https://developer.garmin.com/connect-iq/reference-guides/monkey-c-command-line-setup/
+rem
+rem -----------------------------------------------------------------------------------
+
+rem Check this path is correct for your Java installation
+set JAVA_PATH=C:\Program Files\Java\jdk-22\bin
+rem SDK_PATH should work for all users
+set /p SDK_PATH=<"%USERPROFILE%\AppData\Roaming\Garmin\ConnectIQ\current-sdk.cfg"
+set SDK_PATH=%SDK_PATH:~0,-1%\bin
+rem Assume we can create and use this directory
+set DEST=bin
+
+rem Device for simulation
+set DEVICE=venu2
+set JUNGLE=monkey.jungle
+
+rem C:\>java -jar %SDK_PATH%\monkeybrains.jar -h
+rem usage: monkeyc [-a <arg>] [-b <arg>] [--build-stats <arg>] [-d <arg>]
+rem        [--debug-log-level <arg>] [--debug-log-output <arg>]
+rem        [--disable-api-has-check-removal] [--disable-v2-opcodes] [-e]
+rem        [--Eno-invalid-symbol] [-f <arg>] [-g] [-h] [-i <arg>] [-k] [-l <arg>]
+rem        [-m <arg>] [--no-gen-styles] [-o <arg>] [-O <arg>] [-p <arg>] [-r] [-t]
+rem        [-u <arg>] [-v] [-w] [-x <arg>] [-y <arg>] [-z <arg>]
+rem -a,--apidb <arg>                  API import file
+rem -b,--apimir <arg>                 API MIR file
+rem    --build-stats <arg>            Print build stats [0=basic]
+rem -d,--device <arg>                 Target device
+rem    --debug-log-level <arg>        Debug logging verbosity [0=errors, 1=basic,
+rem                                   2=intermediate, 3=verbose]
+rem    --debug-log-output <arg>       Output log zip file
+rem    --disable-api-has-check-removalDo not optimize out API has checks
+rem    --disable-v2-opcodes           Do not use the v2 opcodes
+rem -e,--package-app                  Create an application package.
+rem    --Eno-invalid-symbol           Do not error when a symbol is found to be
+rem                                   invalid
+rem -f,--jungles <arg>                Jungle files
+rem -g,--debug                        Print debug output
+rem -h,--help                         Prints help information
+rem -i,--import-dbg <arg>             Import api.debug.xml
+rem -k,--profile                      Enable profiling support
+rem -l,--typecheck <arg>              Type check [0=off, 1=gradual, 2=informative,
+rem                                   3=strict]
+rem -m,--manifest <arg>               Manifest file (deprecated)
+rem    --no-gen-styles                Do not generate Rez.Styles module
+rem -o,--output <arg>                 Output file to create
+rem -O,--optimization <arg>           Optimization level [0=none, 1=basic, 2=fast
+rem                                   optimizations, 3=slow optimizations]
+rem                                   [p=optimize performance, z=optimize code
+rem                                   space]
+rem -p,--project-info <arg>           projectInfo.xml file to use when compiling
+rem -r,--release                      Strip debug information
+rem -t,--unit-test                    Enables compilation of unit tests
+rem -u,--devices <arg>                devices.xml file to use when compiling
+rem                                   (deprecated)
+rem -v,--version                      Prints the compiler version
+rem -w,--warn                         Show compiler warnings
+rem -x,--excludes <arg>               Add annotations to the exclude list
+rem                                   (deprecated)
+rem -y,--private-key <arg>            Private key to sign builds with
+rem -z,--rez <arg>                    Resource files (deprecated)
+
+title Compiling for %DEVICE%
+
+rem Batch file's directory where the source code is
+set SRC=%~dp0
+rem drop last character '\'
+set SRC=%SRC:~0,-1%
+
+if exist %DEST% (
+  rmdir /s /q %DEST%
+)
+rem The above may not successfully delete the directory if there are locked files
+if not exist %DEST% (
+  mkdir %DEST%
+)
+
+echo.
+echo Starting compilation for simulation on '%DEVICE%'.
+echo.
+
+rem call %SDK_PATH%\connectiq.bat
+start "Simulator" "%SDK_PATH%\simulator.exe"
+
+rem Compile PRG for a single device for side loading
+"%JAVA_PATH%\java.exe" ^
+  -Xms1g ^
+  -Dfile.encoding=UTF-8 ^
+  -Dapple.awt.UIElement=true ^
+  -jar %SDK_PATH%\monkeybrains.jar ^
+  --output %SRC%\bin\HomeAssistant.prg ^
+  --jungles %SRC%\%JUNGLE% ^
+  --private-key %SRC%\..\developer_key ^
+  --device %DEVICE%_sim ^
+  --warn
+
+rem  --release
+
+if %ERRORLEVEL% equ 0 (
+  %SDK_PATH%\monkeydo.bat %SRC%\bin\HomeAssistant.prg %DEVICE%
+) else (
+  rem Wait to see errors
+  pause
+)

config.schema.json

@@ -2,58 +2,336 @@
   "$schema": "https://json-schema.org/draft/2020-12/schema",
   "type": "object",
   "properties": {
-    "title": { "type": "string" },
-    "items": { "$ref": "#/$defs/items" },
-    "required": ["title", "items"],
-    "additionalProperties": false
+    "$schema": {
+      "type": "string",
+      "description": "The schema will prevent JSON file errors."
     },
+    "title": {
+      "type": "string",
+      "description": "Top level menu title"
+    },
+    "glance": {
+      "$ref": "#/$defs/glance"
+    },
+    "items": {
+      "$ref": "#/$defs/items"
+    }
+  },
+  "required": ["title", "items"],
+  "additionalProperties": false,
   "$defs": {
     "toggle": {
       "type": "object",
       "properties": {
-        "entity": { "$ref": "#/$defs/entity" },
-        "name": { "type": "string" },
-        "type": { "const": "toggle" }
+        "entity": {
+          "$ref": "#/$defs/entity"
+        },
+        "name": {
+          "$ref": "#/$defs/name"
+        },
+        "type": {
+          "$ref": "#/$defs/type",
+          "const": "toggle"
+        },
+        "content": {
+          "$ref": "#/$defs/content"
+        },
+        "tap_action": {
+          "type": "object",
+          "properties": {
+            "confirm": {
+              "$ref": "#/$defs/confirm"
+            },
+            "pin": {
+              "$ref": "#/$defs/pin"
+            }
+          },
+          "additionalProperties": false
+        },
+        "enabled": {
+          "$ref": "#/$defs/enabled"
+        },
+        "exit": {
+          "$ref": "#/$defs/exit"
+        }
       },
       "required": ["entity", "name", "type"],
       "additionalProperties": false
     },
+    "template": {
+      "oneOf": [
+        {
+          "type": "object",
+          "properties": {
+            "entity": {
+              "$ref": "#/$defs/entity",
+              "deprecated": true,
+              "title": "Schema change:",
+              "description": "Use 'tap_action' instead to mirror Home Assistant."
+            },
+            "name": {
+              "$ref": "#/$defs/name"
+            },
+            "content": {
+              "$ref": "#/$defs/content"
+            },
+            "type": {
+              "$ref": "#/$defs/type",
+              "const": "template",
+              "deprecated": true,
+              "title": "Schema change:",
+              "description": "Use 'info' or 'tap' instead."
+            },
+            "enabled": {
+              "$ref": "#/$defs/enabled"
+            }
+          },
+          "required": ["name", "content", "type"],
+          "additionalProperties": false
+        },
+        {
+          "type": "object",
+          "properties": {
+            "entity": {
+              "$ref": "#/$defs/entity"
+            },
+            "name": {
+              "$ref": "#/$defs/name"
+            },
+            "content": {
+              "$ref": "#/$defs/content"
+            },
+            "type": {
+              "$ref": "#/$defs/type",
+              "const": "template",
+              "deprecated": true,
+              "title": "Schema change:",
+              "description": "Use 'info' or 'tap' instead."
+            },
+            "tap_action": {
+              "$ref": "#/$defs/tap_action"
+            },
+            "enabled": {
+              "$ref": "#/$defs/enabled"
+            },
+            "exit": {
+              "$ref": "#/$defs/exit"
+            }
+          },
+          "required": ["name", "content", "type", "tap_action"],
+          "additionalProperties": false
+        }
+      ]
+    },
+    "info": {
+      "type": "object",
+      "properties": {
+        "name": {
+          "$ref": "#/$defs/name"
+        },
+        "content": {
+          "$ref": "#/$defs/content"
+        },
+        "type": {
+          "$ref": "#/$defs/type",
+          "const": "info"
+        },
+        "enabled": {
+          "$ref": "#/$defs/enabled"
+        }
+      },
+      "required": ["name", "content", "type"],
+      "additionalProperties": false
+    },
     "tap": {
       "type": "object",
       "properties": {
-        "entity": { "$ref": "#/$defs/entity" },
-        "name": { "type": "string" },
-        "type": { "const": "tap" },
-        "service": { "$ref": "#/$defs/entity" }
+        "entity": {
+          "$ref": "#/$defs/entity"
         },
-      "required": ["entity", "name", "type", "service"],
+        "name": {
+          "$ref": "#/$defs/name"
+        },
+        "type": {
+          "$ref": "#/$defs/type",
+          "const": "tap"
+        },
+        "content": {
+          "$ref": "#/$defs/content"
+        },
+        "service": {
+          "$ref": "#/$defs/entity",
+          "deprecated": true,
+          "title": "Schema change:",
+          "description": "Use 'tap_action' instead to mirror Home Assistant."
+        },
+        "tap_action": {
+          "$ref": "#/$defs/tap_action"
+        },
+        "enabled": {
+          "$ref": "#/$defs/enabled"
+        },
+        "exit": {
+          "$ref": "#/$defs/exit"
+        }
+      },
+      "required": ["name", "type"],
       "additionalProperties": false
     },
-    "menu": {
+    "group": {
       "type": "object",
       "properties": {
-        "entity": { "$ref": "#/$defs/entity" },
-        "name": { "type": "string" },
-        "title": { "type": "string" },
-        "type": { "const": "group" },
-        "items": { "$ref": "#/$defs/items" }
+        "entity": {
+          "$ref": "#/$defs/entity",
+          "type": "string",
+          "deprecated": true,
+          "title": "Schema change:",
+          "description": "'entity' is no longer necessary and should now be removed."
         },
-      "required": ["entity", "name", "title", "type", "items"],
+        "name": {
+          "title": "Menu item's familiar name.",
+          "type": "string"
+        },
+        "title": {
+          "title": "Sub menu's title once displayed.",
+          "type": "string"
+        },
+        "type": {
+          "$ref": "#/$defs/type",
+          "const": "group"
+        },
+        "content": {
+          "$ref": "#/$defs/content"
+        },
+        "items": {
+          "$ref": "#/$defs/items"
+        },
+        "enabled": {
+          "$ref": "#/$defs/enabled"
+        }
+      },
+      "required": ["name", "title", "type", "items"],
       "additionalProperties": false
     },
+    "type": {
+      "title": "Menu item type",
+      "description": "One of 'info', 'tap', 'toggle' or 'group'."
+    },
     "items": {
       "type": "array",
       "items": {
         "oneOf": [
-          { "$ref": "#/$defs/toggle" },
-          { "$ref": "#/$defs/tap" },
-          { "$ref": "#/$defs/menu" }
+          {
+            "$ref": "#/$defs/toggle"
+          },
+          {
+            "$ref": "#/$defs/template"
+          },
+          {
+            "$ref": "#/$defs/tap"
+          },
+          {
+            "$ref": "#/$defs/info"
+          },
+          {
+            "$ref": "#/$defs/group"
+          }
         ]
       }
     },
+    "name": {
+      "title": "Your familiar name to display in the menu item",
+      "type": "string"
+    },
     "entity": {
       "type": "string",
+      "title": "Home Assistant entity name",
       "pattern": "^[^.]+\\.[^.]+$"
+    },
+    "service": {
+      "type": "string",
+      "title": "Home Assistant service name",
+      "pattern": "^[^.]+\\.[^.]+$"
+    },
+    "tap_action": {
+      "type": "object",
+      "title": "Action",
+      "description": "'confirm' field is optional.",
+      "properties": {
+        "service": {
+          "$ref": "#/$defs/service"
+        },
+        "confirm": {
+          "$ref": "#/$defs/confirm"
+        },
+        "pin": {
+          "$ref": "#/$defs/pin"
+        },
+        "data": {
+          "type": "object",
+          "title": "Your services's parameters",
+          "description": "The object containing the parameters and their values to be passed to the entity. No schema checking can be done here, you are on your own! On application crash, remove the parameters."
+        }
+      },
+      "required": ["service"]
+    },
+    "content": {
+      "title": "Home Assistant Template",
+      "description": "Jinja2 template defining the text to display. Must be included in an 'info'. Optional in a 'toggle', 'tap' and 'group'. Special characters may not render in the glance context.",
+      "type": "string"
+    },
+    "confirm": {
+      "type": "boolean",
+      "default": false,
+      "title": "Confirmation",
+      "description": "Optional confirmation of the action before execution as a precaution."
+    },
+    "pin": {
+      "type": "boolean",
+      "default": false,
+      "title": "PIN Confirmation",
+      "description": "Optional PIN confirmation of the action before execution as a precaution. Has precedence over 'confirm': true if both are set."
+    },
+    "glance": {
+      "type": "object",
+      "title": "Glance customisation",
+      "oneOf": [
+        {
+          "properties": {
+            "type": {
+              "title": "Glance type",
+              "description": "One of 'info' or 'status'. 'info' renders the template specified in the 'content' field inside the glance view. 'status' reverts to the default glance view and ignores the 'content' field. This allows for disabling the template temporarily.",
+              "const": "info"
+            },
+            "content": {
+              "$ref": "#/$defs/content"
+            }
+          },
+          "required": ["type", "content"]
+        },
+        {
+          "properties": {
+            "type": {
+              "title": "Glance type",
+              "description": "One of 'info' or 'status'.",
+              "const": "status"
+            }
+          },
+          "required": ["type"]
+        }
+      ]
+    },
+    "enabled": {
+      "type": "boolean",
+      "default": true,
+      "title": "Enable the menu item",
+      "description": "Typically used to temporarily disable a menu item, e.g. for seasonal variations. Enabled (true) by default."
+    },
+    "exit": {
+      "type": "boolean",
+      "default": false,
+      "title": "Exit on selection",
+      "description": "Choose to exit the application after this item has been selected. Disabled (false) by default. N.B. Only actionable menu items can have this field added."
     }
   }
 }

examples/Actions.md

@@ -0,0 +1,110 @@
+[Home](../README.md) | [Switches](Switches.md) | [Actions](Actions.md) | [Templates](Templates.md) | [Glance](Glance.md) | [Background Service](../BackgroundService.md) | [Wi-Fi](../Wi-Fi.md) | [HTTP Headers](../HTTP_Headers.md) | [Trouble Shooting](../TroubleShooting.md) | [Version History](../HISTORY.md)
+
+
+# Actions
+
+A simple example using a scene as a `tap` menu item.
+
+```json
+{
+  "entity": "scene.telly_watching",
+  "name": "Telly Scene",
+  "type": "tap",
+  "tap_action": {
+    "service": "scene.turn_on"
+  }
+},
+```
+
+Any menu item with an action (`tap`, `template`, or `toggle`), may have a confirmation view added. For consistency this is always done via the `tap_action` JSON object, even though for a `toggle` menu item there will only ever be a single field inside. For the `toggle` menu item, the confirmation is presented on both `on` and `off` directions. There is no option for asymmetry, i.e. only in one direction.
+
+```json
+  "tap_action": {
+    "confirm": true
+  }
+```
+
+<img src="../images/confirmation_view.png" width="200" title="Confirmation View"/>
+
+For example:
+
+```json
+{
+  "entity": "switch.garage_door",
+  "name": "Garage Door",
+  "type": "toggle",
+  "tap_action": {
+    "confirm": true
+  }
+}
+```
+
+**The authors do not advise the use of this application for security sensitive devices. But we suspect users are taking that risk anyway, hence a PIN confirmation is provided that can be used for additional menu item security.**
+
+This can be enabled by setting the `pin` field in the `tap_action`. The `pin` field overrides `confirm`. Explicitly setting `confirm` is not necessary.
+
+The 4-digit PIN is set globally for all actions in the app settings in Connect IQ.
+
+```json
+  "tap_action": {
+    "pin": true
+  }
+```
+
+When entering an invalid PIN for the fifth time within 2 minutes, the PIN dialog will be locked for all actions for the next 10 minutes. Entering a valid PIN will always reset the failure counter.
+
+<img src="../images/pin_view.png" width="200" title="Confirmation View"/>
+
+Note that for notify events, you _must_ not supply an `entity_id` or the API call will fail. There are other examples too.
+
+```json
+{
+  "name": "Message",
+  "type": "tap",
+  "tap_action": {
+    "service": "notify.mobile_app_on_phone",
+    "data": {
+      "title": "This is a title",
+      "message": "This is the message"
+    },
+    "confirm": true
+  }
+}
+```
+
+> [!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 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
+
+You can choose individual items that will quit after they have completed their action.
+
+```json
+{
+  "entity": "automation.turn_off_stuff",
+  "name": "Turn off Stuff",
+  "type": "tap",
+  "tap_action": {
+    "service": "automation.trigger"
+  },
+  "exit": true
+}
+```
+
+## Disable Menu Item
+
+If you would like to temporarily disable an item in your menu, e.g. for seasonal reasons like not needing to turn on the heating in summer, then rather than swapping menu definition files or deleting a section of the menu you can mark the item as 'disabled'. This field applies to all menu items.
+
+```json
+{
+  "entity": "automation.turn_off_stuff",
+  "name": "Turn off Stuff",
+  "type": "tap",
+  "tap_action": {
+    "service": "automation.trigger"
+  },
+  "enabled": false
+}
+```

examples/Glance.md

@@ -0,0 +1,80 @@
+[Home](../README.md) | [Switches](Switches.md) | [Actions](Actions.md) | [Templates](Templates.md) | [Glance](Glance.md) | [Background Service](../BackgroundService.md) | [Wi-Fi](../Wi-Fi.md) | [HTTP Headers](../HTTP_Headers.md) | [Trouble Shooting](../TroubleShooting.md) | [Version History](../HISTORY.md)
+
+# Glance
+
+Since [version 2.30](../History.md), it is possible to ovverride the text displayed on the Glance view. This page explains how to customise the text.
+
+
+## Default View
+
+The default view has always been to display the status of the menu and API availability to indicate if there's a problem. This view has now been updated to be more colourful.
+
+<img src="../images/Venu2_glance_default.png" width="200" title="Venu 2 Default Glance"/>
+
+When either the API or the menu file is inaccessible, the fields will turn red.
+
+
+## Customised View
+
+In order to customise the Glance view you need to add a `glance` field to the top level of the JSON menu file as illustrated here:
+
+```json
+{
+  "$schema": "https://raw.githubusercontent.com/house-of-abbey/GarminHomeAssistant/main/config.schema.json",
+  "title": "Home",
+  "glance": {
+    "type": "info",
+    "content": "Text: {% .. %}"
+  },
+  "items": [...]
+}
+```
+
+For example:
+
+<img src="../images/Venu2_glance_custom.png" width="200" title="Venu 2 Customised Glance"/>
+
+```json
+{
+  "$schema": "https://raw.githubusercontent.com/house-of-abbey/GarminHomeAssistant/main/config.schema.json",
+  "glance": {
+    "type": "info",
+    "content": "Solar Battery: {{ states('sensor.battery_capacity_charge') }}%"
+  },
+  :
+}
+```
+
+You may make this as complicated as you like! But you have limited space and only ASCII text characters. **It is best to turn on menu caching in order to speed up the display of the template**. The display is then nearly instantaneous.
+
+The default view will persist showing until the errors are resolved. In order to extract the custom glance template both the menu and the API are required. So it is logical that the two tests must pass first. The exception here is if the menu is cached, in which case only the API needs to pass.
+
+> [!IMPORTANT]
+> Sadly what you cannot do is use special characters like: 🌞🔋⛅🪫. Whilst these do display in menu items, they do not seem to work on the Glance view. We really like them, so have tried but failed. Only ASCII text appears to be supported by the Garmin Connect IQ SDK's Glance View. This is not something we have any control over, please do not request this to be "fixed".
+
+It is possible to revert to the default glance content without deleting the template by changing the `type` to `status`.
+
+```json
+{
+  "$schema": "https://raw.githubusercontent.com/house-of-abbey/GarminHomeAssistant/main/config.schema.json",
+  "title": "Home",
+  "glance": {
+    "type": "status",
+    "content": "Text: {% .. %}"
+  },
+  "items": [...]
+}
+```
+
+So the glance view object has a `type` field with two possible values: `info` and `status`. When the type is `status` the `content` field is not required.
+
+
+## Displayed Errors
+
+The following shows the default glance when the menu file is not available at the specified URL.
+
+<img src="../images/Venu2_glance_no_menu.png" width="200" title="Venu 2 Glance showing errors"/>
+
+Once the custom glance template has been retrieved and evaluated the display will change. Should the connectivity to your Home Assistant then be lost, e.g. you move out of range of your phone, the glance reflects this in the colour of the residual two rectangles. The top one remains an indicator for the API, and the bottom rectangle remains an indicator for the menu availability, reflecting the original placement in the default glance view that has now been replaced.
+
+<img src="../images/Venu2_glance_no_bt.png" width="200" title="Venu 2 Glance showing lost connectivity"/>

examples/Switches.md

@@ -0,0 +1,136 @@
+[Home](../README.md) | [Switches](Switches.md) | [Actions](Actions.md) | [Templates](Templates.md) | [Glance](Glance.md) | [Background Service](../BackgroundService.md) | [Wi-Fi](../Wi-Fi.md) | [HTTP Headers](../HTTP_Headers.md) | [Trouble Shooting](../TroubleShooting.md) | [Version History](../HISTORY.md)
+
+# Switches
+
+This is the simplest form:
+
+```json
+ {
+   "entity": "light.bedside_light_switch",
+   "name": "Bedroom Light",
+   "type": "toggle"
+ },
+```
+
+And with an optional confirmation:
+
+```json
+ {
+   "entity": "light.exterior",
+   "name": "Exterior Lights",
+   "type": "toggle",
+   "tap_action": {
+     "confirm": true
+   }
+ }
+```
+
+or an optional PIN confirmation:
+
+```json
+ {
+   "entity": "light.exterior",
+   "name": "Exterior Lights",
+   "type": "toggle",
+   "tap_action": {
+     "pin": true
+   }
+ }
+```
+
+To support a non-standard light, switch, or automation as a toggle menu item you may like to define a custom switch. In order to facilitate custom switches at this time, you must create a template switch in HomeAssistant.
+
+```yaml
+switch:
+  - platform: template
+    switches:
+      <switch-name>:
+        friendly_name: <name>
+        value_template: <value>
+        turn_on:
+          service: <service>
+          data:
+            entity_id: <entity>
+            <attribute>: <value>
+        turn_off:
+          service: <service>
+          data:
+            entity_id: <entity>
+            <attribute>: <value>
+```
+
+Then you can use the following in your config:
+
+```json
+{
+  "entity": "switch.<switch-name>",
+  "name": "<name>",
+  "type": "toggle"
+}
+```
+
+And you can optionally include a template to reflect some status. See [Templates](Templates.md) for details on hwo to use this JSON field.
+
+```json
+{
+  "entity": "switch.<switch-name>",
+  "name": "<name>",
+  "type": "toggle",
+  "content": "..."
+}
+```
+
+## Example - Covers
+
+```yaml
+switch:
+  - platform: template
+    switches:
+      cover:
+        friendly_name: Cover
+        value_template: "{{ is_state('cover.cover', 'open') }}"
+        turn_on:
+          service: cover.open_cover
+          data:
+            entity_id: cover.cover
+        turn_off:
+          service: cover.close_cover
+          data:
+            entity_id: cover.cover
+```
+
+Then you can use the following in your config:
+
+```json
+{
+  "entity": "switch.cover",
+  "name": "Cover",
+  "type": "toggle"
+}
+```
+
+## Exit On Toggle
+
+You can choose individual items that will quit after they have completed their action.
+
+```json
+{
+  "entity": "light.hall_light",
+  "name": "Hall Light & Quit",
+  "type": "toggle",
+  "exit": true
+}
+```
+
+## Disable Menu Item
+
+If you would like to temporarily disable an item in your menu, e.g. for seasonal reasons like not needing to turn on Christmas tree lights outside the festive season, then rather than swapping menu definition files or deleting a section of the menu you can mark the item as 'disabled'. This field applies to all menu items.
+
+```json
+{
+  "entity": "light.chrissmas_tree",
+  "name": "Christmas Lights",
+  "type": "toggle",
+  "enabled": false
+}
+```

examples/Templates.md

@@ -0,0 +1,236 @@
+[Home](../README.md) | [Switches](Switches.md) | [Actions](Actions.md) | [Templates](Templates.md) | [Glance](Glance.md) | [Background Service](../BackgroundService.md) | [Wi-Fi](../Wi-Fi.md) | [HTTP Headers](../HTTP_Headers.md) | [Trouble Shooting](../TroubleShooting.md) | [Version History](../HISTORY.md)
+
+# Templates
+
+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 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
+
+> [!IMPORTANT]
+> In order to avoid "Template Error" being displayed as the return value, make sure your Jinja2 template returns a `string`, not a number of some variety. _All numbers must be formatted to strings_ so the application does not need to distinguish an `integer` from a `float`.
+
+## States
+
+In this example we get the battery level of the device and add the percent sign. *Very simple*
+
+```json
+{
+  "name": "Phone",
+  "type": "info",
+  "content": "{{ states('sensor.<device>_battery_level') }}%"
+}
+```
+
+### Examples
+
+The first two keep to the simple proposal above. The last combines them into a single menu item. Now you can start to see the utility of this menu item, composing your own formatted text.
+
+```json
+{
+  "name": "Hall Temp",
+  "type": "info",
+  "content": "{{ states('sensor.hallway_temperature') }}°C"
+},
+{
+  "name": "Hall Humidity",
+  "type": "info",
+  "content": "{{ states('sensor.hallway_humidity') }}%"
+},
+{
+  "name": "Hallway",
+  "type": "info",
+  "content": "{{ states('sensor.hallway_temperature') }}°C {{ states('sensor.hallway_humidity') }}%"
+}
+```
+
+In order to keep the formatting of floating point numbers under control, you might also like to include a format string as follows. `states()` seems to return a `string` that needs converting to a `float` before the `format()` call can manage the conversion to the required number fo decimal places.
+
+```json
+{
+  "name": "Hallway",
+  "type": "info",
+  "content": "T:{{ '%.1f' | format(states('sensor.hallway_temperature') | float) }}°C, H:{{ '%.1f' | format(states('sensor.hallway_humidity') | float) }}%"
+},
+```
+
+Where your device supports unicode characters these example may work.
+
+```json
+{
+  "name": "Charge",
+  "type": "info",
+  "content": "☎ {{ states('sensor.my_phone_battery_level') }}%{% if is_state('binary_sensor.my_phone_is_charging', 'on') %}⚡{% endif %}, ⏳ {{ '%.0f'|format(states('sensor.my_watch_battery_level') | float) }}%{% if is_state('binary_binary_sensor.my_watch_battery_is_charging', 'on') %}⚡{% endif %}"
+},
+{
+  "name": "Hallway",
+  "type": "info",
+  "content": "🌡{% if is_state('sensor.hallway_temperature', 'unavailable') %}-{% else %}{{ '%.1f'|format(states('sensor.hallway_temperature')|float) }}°C{% if is_state_attr('climate.hallway', 'hvac_action', 'heating') or is_state_attr('climate.hallway', 'hvac_action', 'preheating') -%}🔥{%- endif %}{% endif %}, 💧{% if is_state('sensor.hallway_humidity', 'unavailable') %}-{% else %}{{ '%.1f'|format(states('sensor.hallway_humidity')|float) }}%{% endif %}"
+}
+```
+
+![Unicode Characters in a Template](../images/Unicode_Template.png)
+
+## Conditionals
+
+Anything between `{%` and `%}` is a directive (`if`, `else`, `elif`, `endif`, etc.). Conditionals are used to dynamically change the content based on the state of the entity.
+
+In this example we get the battery level of the device and add the percent sign. If the device is charging we add a plus sign.
+
+```json
+{
+  "name": "Phone",
+  "type": "info",
+  "content": "{{ states('sensor.<device>_battery_level') }}%{% if is_state('binary_sensor.<device>_is_charging', 'on') %}+{% endif %}"
+}
+```
+
+Here we also use the else clause as well to give proper text instead of just `on` or `off`.
+
+```json
+{
+  "name": "Garage Doors",
+  "type": "info",
+  "content": "{% if is_state('binary_sensor.<door-0>', 'on') %}Open{% else %}Closed{% endif %} {% if is_state('binary_sensor.<door-1>', 'on') %}Open{% else %}Closed{% endif %}"
+}
+```
+
+> [!IMPORTANT]
+> We advise users against adding security devices.
+
+However, for users doing this **against our advice**, we strongly recommend to secure confirmation of the action using our PIN confirmation dialog.
+This an example of toggling a garage door open and closed with a PIN confirmation. *Do this at your own risk*.
+
+The PIN confirmation is activated for actions with `"pin": true`. The PIN is configured globally in the application settings. The PIN needs to be a 4-digit number.
+The user has 5 attempts to provide a valid PIN within 2 minutes. If too many failures have been detected during this time, the PIN dialog will be locked for 10 minutes.
+
+Note: Only when you use the `tap_action` field do you also need to include the `entity` field. This is a change to a previous version of the application, hence the presence of the `entity` field will be ignored for backwards compatibility, and the schema will provide a warning only.
+
+```json
+{
+  "entity": "cover.garage_door",
+  "name": "Garage Door",
+  "type": "tap",
+  "content": "{% if is_state('binary_sensor.garage_connected', 'on') %}{{state_translated('cover.garage_door')}} - {{state_attr('cover.garage_door', 'current_position')}}%{%else%}Unconnected{% endif %}",
+  "tap_action": {
+    "service": "cover.toggle",
+    "pin": true
+  }
+}
+```
+
+## Group and Toggle Menu Items
+
+Both `group` and `toggle` menu items accept an optional `content` field as of v2.19. This allows the use of templates to present status information.
+
+```json
+    {
+      "name": "Each Lounge Light",
+      "title": "Lounge",
+      "type": "group",
+      "content": "{{'On: %d, Off: %d'|format(expand(state_attr('light.living_room_lights', 'entity_id'))|selectattr('state','eq','on')|map(attribute='entity_id')|list|count, expand(state_attr('light.living_room_lights', 'entity_id'))|selectattr('state','eq','off')|map(attribute='entity_id')|list|count)}}",
+      "items": [..]
+    }
+```
+
+## Advanced
+
+Here we generate a bar graph of the battery level. We use the following steps to do this:
+
+- Convert the state to a number.
+- Divide by 100 to get a fraction.
+- Multiply by the width to get the number of `#`s.
+- Multiply by the `#` char to make a string.
+- Subtract the width from the number of `#`s to get the number of `_`s.
+- Multiply by the `_` char to make a string.
+
+```json
+{
+  "name": "Phone",
+  "type": "info",
+  "content": "{{ states('sensor.<device>_battery_level') }}%{% if is_state('binary_sensor.<device>_is_charging', 'on') %}+{% endif %} {{ '#' * (((states('sensor.<device>_battery_level') | int) / 100 * <width>) | int) }}{{ '_' * (<width> - (((states('sensor.<device>_battery_level') | int) / 100 * <width>) | int)) }}"
+}
+```
+
+An example of a dimmer light with 4 brightness settings 0..3. Here our light worked on a percentage, so that had to be converted to the range 0..3.
+
+```json
+{
+  "$schema": "https://raw.githubusercontent.com/house-of-abbey/GarminHomeAssistant/main/config.schema.json",
+  "title": "Home",
+  "items": [
+    {
+      "name": "LEDs",
+      "type": "info",
+      "content": "{% if not (is_state('light.green_house', 'off') or is_state('light.green_house', 'unavailable')) %}{{ (((state_attr('light.green_house', 'brightness') | float) / 255 * 100) | round(0)) | int }}%{% else %}Off{% endif %}"
+    },
+    {
+      "entity": "light.green_house",
+      "name": "LEDs 0",
+      "type": "tap",
+      "content": "{% if not (is_state('light.green_house', 'off') or is_state('light.green_house', 'unavailable')) %}{{ (((state_attr('light.green_house', 'brightness') | float) / 255 * 100) | round(0)) | int }}%{% else %}Off{% endif %}",
+      "tap_action": {
+        "service": "light.turn_on",
+        "data": {
+          "brightness_pct": 12
+        }
+      }
+    },
+    {
+      "entity": "light.green_house",
+      "name": "LEDs 1",
+      "type": "tap",
+      "tap_action": {
+        "service": "light.turn_on",
+        "data": {
+          "brightness_pct": 37
+        }
+      }
+    },
+    {
+      "entity": "light.green_house",
+      "name": "LEDs 2",
+      "type": "tap",
+      "content": "{% if not (is_state('light.green_house', 'off') or is_state('light.green_house', 'unavailable')) %}{{ (((state_attr('light.green_house', 'brightness') | float) / 255 * 100) | round(0)) | int }}%{% else %}Off{% endif %}",
+      "tap_action": {
+        "service": "light.turn_on",
+        "data": {
+          "brightness_pct": 62
+        }
+      }
+    },
+    {
+      "entity": "light.green_house",
+      "name": "LEDs 3",
+      "type": "tap",
+      "content": "{% if not (is_state('light.green_house', 'off') or is_state('light.green_house', 'unavailable')) %}{{ (((state_attr('light.green_house', 'brightness') | float) / 255 * 100) | round(0))| int }}%{% else %}Off{% endif %}",
+      "tap_action": {
+        "service": "light.turn_on",
+        "data": {
+          "brightness_pct": 87
+        }
+      }
+    }
+  ]
+}
+```
+
+## Disable Menu Item
+
+If you would like to temporarily disable an item in your menu, then rather than swapping menu definition files or deleting a section of the menu you can mark the item as 'disabled'. This field applies to all menu items.
+
+```json
+{
+  "name": "Phone",
+  "type": "info",
+  "content": "{{ ... }}",
+  "enabled": false
+}
+```
+
+## Warnings
+
+Just remember, on older smaller memory devices **you have the ability to crash the application by creating an excessive menu definition**. Templates can require significant definition for highly customised text. Don't be silly.

export.cmd

@@ -0,0 +1,113 @@
+@echo off
+rem -----------------------------------------------------------------------------------
+rem
+rem  Distributed under MIT Licence
+rem    See https://github.com/house-of-abbey/GarminHomeAssistant/blob/main/LICENSE.
+rem
+rem -----------------------------------------------------------------------------------
+rem
+rem  GarminHomeAssistant is a Garmin IQ application written in Monkey C and routinely
+rem  tested on a Venu 2 device. The source code is provided at:
+rem             https://github.com/house-of-abbey/GarminHomeAssistant.
+rem
+rem  J D Abbey & P A Abbey, 28 December 2022
+rem
+rem  Export both the Application and the Widget IQ files for upload to Garmin's App Store.
+rem
+rem  Reference:
+rem   * Using Monkey C from the Command Line
+rem     https://developer.garmin.com/connect-iq/reference-guides/monkey-c-command-line-setup/
+rem
+rem -----------------------------------------------------------------------------------
+
+rem Check this path is correct for your Java installation
+set JAVA_PATH=C:\Program Files\Java\jdk-22\bin
+rem SDK_PATH should work for all users
+set /p SDK_PATH=<"%USERPROFILE%\AppData\Roaming\Garmin\ConnectIQ\current-sdk.cfg"
+set SDK_PATH=%SDK_PATH:~0,-1%\bin
+rem Assume we can create and use this directory
+set DEST=export
+set IQ=HomeAssistant-app.iq
+
+rem usage: monkeyc [-a <arg>] [-b <arg>] [--build-stats <arg>] [-d <arg>]
+rem        [--debug-log-level <arg>] [--debug-log-output <arg>]
+rem        [--disable-api-has-check-removal] [--disable-v2-opcodes] [-e]
+rem        [--Eno-invalid-symbol] [-f <arg>] [-g] [-h] [-i <arg>] [-k] [-l <arg>]
+rem        [-m <arg>] [--no-gen-styles] [-o <arg>] [-O <arg>] [-p <arg>] [-r] [-t]
+rem        [-u <arg>] [-v] [-w] [-x <arg>] [-y <arg>] [-z <arg>]
+rem -a,--apidb <arg>                  API import file
+rem -b,--apimir <arg>                 API MIR file
+rem    --build-stats <arg>            Print build stats [0=basic]
+rem -d,--device <arg>                 Target device
+rem    --debug-log-level <arg>        Debug logging verbosity [0=errors, 1=basic,
+rem                                   2=intermediate, 3=verbose]
+rem    --debug-log-output <arg>       Output log zip file
+rem    --disable-api-has-check-removalDo not optimize out API has checks
+rem    --disable-v2-opcodes           Do not use the v2 opcodes
+rem -e,--package-app                  Create an application package.
+rem    --Eno-invalid-symbol           Do not error when a symbol is found to be
+rem                                   invalid
+rem -f,--jungles <arg>                Jungle files
+rem -g,--debug                        Print debug output
+rem -h,--help                         Prints help information
+rem -i,--import-dbg <arg>             Import api.debug.xml
+rem -k,--profile                      Enable profiling support
+rem -l,--typecheck <arg>              Type check [0=off, 1=gradual, 2=informative,
+rem                                   3=strict]
+rem -m,--manifest <arg>               Manifest file (deprecated)
+rem    --no-gen-styles                Do not generate Rez.Styles module
+rem -o,--output <arg>                 Output file to create
+rem -O,--optimization <arg>           Optimization level [0=none, 1=basic, 2=fast
+rem                                   optimizations, 3=slow optimizations]
+rem                                   [p=optimize performance, z=optimize code
+rem                                   space]
+rem -p,--project-info <arg>           projectInfo.xml file to use when compiling
+rem -r,--release                      Strip debug information
+rem -t,--unit-test                    Enables compilation of unit tests
+rem -u,--devices <arg>                devices.xml file to use when compiling
+rem                                   (deprecated)
+rem -v,--version                      Prints the compiler version
+rem -w,--warn                         Show compiler warnings
+rem -x,--excludes <arg>               Add annotations to the exclude list
+rem                                   (deprecated)
+rem -y,--private-key <arg>            Private key to sign builds with
+rem -z,--rez <arg>                    Resource files (deprecated)
+
+title Exporting Garmin Home Assistant Application
+
+rem Batch file's directory where the source code is
+set SRC=%~dp0
+rem drop last character '\'
+set SRC=%SRC:~0,-1%
+set DEST=%SRC%\%DEST%
+set IQ=%DEST%\%IQ%
+
+if not exist %DEST% (
+  echo Creating %DEST%
+  md %DEST%
+)
+
+if exist %IQ% (
+  echo Deleting old %IQ%
+  del /f /q %IQ%
+)
+
+echo Starting export of HomeAssistant Application to %IQ%
+echo.
+
+"%JAVA_PATH%\java.exe" ^
+  -Xms1g ^
+  -Dfile.encoding=UTF-8 ^
+  -Dapple.awt.UIElement=true ^
+  -jar %SDK_PATH%\monkeybrains.jar ^
+  --output %IQ% ^
+  --jungles %SRC%\monkey.jungle ^
+  --private-key %SRC%\..\developer_key ^
+  --package-app ^
+  --release
+
+echo.
+echo Finished exporting HomeAssistant
+dir %IQ%
+
+pause

iconResize.py

@@ -91,7 +91,7 @@ for screen_size, icon_sizes in lookup.items():
           svg.attrs["width"]  = lookup[screen_size][Half]
           svg.attrs["height"] = lookup[screen_size][Half]
         with open(output_dir + "/" + entry, "wb") as o:
-          o.write(svg.encode("utf-8"))
+          o.write(svg.encode("utf-8") + b"\n")
     elif entry.endswith(".xml"):
       print("Create file:       ", entry.ljust(40) + " XML - Copy file")
       shutil.copyfile(input_dir + "/" + entry, output_dir + "/" + entry)

launcherIconResize.py

@@ -0,0 +1,70 @@
+####################################################################################
+#
+# Distributed under MIT Licence
+#   See https://github.com/house-of-abbey/GarminHomeAssistant/blob/main/LICENSE.
+#
+####################################################################################
+#
+# GarminHomeAssistant is a Garmin IQ application written in Monkey C and routinely
+# tested on a Venu 2 device. The source code is provided at:
+#            https://github.com/house-of-abbey/GarminHomeAssistant.
+#
+# J D Abbey & P A Abbey, 29 December 2023
+#
+#
+# Description:
+#
+# Python script to automatically resize the application launcher icon from the
+# original 70x70 pixel width to something more appropriate for different screen
+# sizes.
+#
+# Python installation:
+#   pip install BeautifulSoup
+# NB. For XML formatting:
+#   pip install lxml
+#
+# References:
+#  * https://www.crummy.com/software/BeautifulSoup/bs4/doc/
+#  * https://realpython.com/beautiful-soup-web-scraper-python/
+#  * https://www.crummy.com/software/BeautifulSoup/bs4/doc/#parsing-xml
+#  * https://www.crummy.com/software/BeautifulSoup/bs4/doc/#xml
+#
+####################################################################################
+
+from bs4 import BeautifulSoup, Comment
+import os
+import shutil
+
+output_dir_prefix = 'resources-launcher-'
+# Original icons for 416x416 screen size with 70x70 icons
+input_dir         = output_dir_prefix + '70-70'
+
+# Convert icons to different screen sizes by these parameters
+lookup = [26, 30, 33, 35, 36, 40, 54, 60, 61, 62, 65, 80]
+
+# Delete all but the original 48x48 icon directories
+for entry in os.listdir("."):
+  if entry.startswith(output_dir_prefix) and entry != input_dir:
+    shutil.rmtree(entry)
+
+# (Re-)Create the resized icon directories
+for icon_size in lookup:
+  output_dir = output_dir_prefix + str(icon_size) + "-" + str(icon_size)
+  print("\nCreate directory:", output_dir)
+  if os.path.exists(output_dir) and os.path.isdir(output_dir):
+    shutil.rmtree(output_dir)
+  os.makedirs(output_dir)
+  for entry in os.listdir(input_dir):
+    if entry.endswith(".svg"):
+      print("Create file:       ", entry.ljust(40) + " SVG - Change file")
+      with open(input_dir + "/" + entry, "r") as f:
+        soup = BeautifulSoup(f.read(), features="xml")
+        svg: BeautifulSoup = list(soup.children)[0]
+        h = int(svg.attrs["height"])
+        svg.attrs["width"]  = icon_size
+        svg.attrs["height"] = icon_size
+        with open(output_dir + "/" + entry, "wb") as o:
+          o.write(svg.encode("utf-8"))
+    elif entry.endswith(".xml"):
+      print("Create file:       ", entry.ljust(40) + " XML - Copy file")
+      shutil.copyfile(input_dir + "/" + entry, output_dir + "/" + entry)

manifest.xml

@@ -9,131 +9,129 @@
    tested on a Venu 2 device. The source code is provided at:
               https://github.com/house-of-abbey/GarminHomeAssistant.
 
-   P A Abbey & J D Abbey, 31 October 2023
+   P A Abbey & J D Abbey & Someone0nEarth, 31 October 2023
 
-  Test Application id="98c36259-498a-4458-9cef-74a273ad2bc3"
-  Live Application id="40131e87-31ff-454b-a8e2-92276ee399d6"
+  Device Information & References:
+  * https://developer.garmin.com/connect-iq/compatible-devices/
+  * https://developer.garmin.com/connect-iq/reference-guides/devices-reference/
+
+  philipabbey's Test App    id="98c36259-498a-4458-9cef-74a273ad2bc3" type="watch-app"
+  Live Application          id="40131e87-31ff-454b-a8e2-92276ee399d6" type="watch-app"
 
 -->
-
 <iq:manifest version="3" xmlns:iq="http://www.garmin.com/xml/connectiq">
   <!--
     Use "Monkey C: Edit Application" from the Visual Studio Code command palette
     to update the application attributes.
   -->
-  <iq:application id="40131e87-31ff-454b-a8e2-92276ee399d6" type="watch-app" name="@Strings.AppName" entry="HomeAssistantApp" launcherIcon="@Drawables.LauncherIcon" minApiLevel="3.1.0">
+  <iq:application id="98c36259-498a-4458-9cef-74a273ad2bc3" type="watch-app" name="@Strings.AppName" entry="HomeAssistantApp" launcherIcon="@Drawables.LauncherIcon" minApiLevel="3.1.0">
     <!--
-      Use the following from the Visual Studio Code comand palette to edit
+      Use the following from the Visual Studio Code command palette to edit
       the build targets:
       "Monkey C: Set Products by Product Category" - Lets you add all products
                                   that belong to the same product category
       "Monkey C: Edit Products" - Lets you add or remove any product
     -->
     <iq:products>
-      <!--
-        Device Information & References:
-        * https://developer.garmin.com/connect-iq/compatible-devices/
-        * https://developer.garmin.com/connect-iq/reference-guides/devices-reference/
-      -->
-
-      <!-- Screen Size 390x390 launcher icon size 70x70 -->
+      <iq:product id="approachs50"/>
       <iq:product id="approachs7042mm"/>
-      <!-- Screen Size 454x454 launcher icon size 80x80 -->
       <iq:product id="approachs7047mm"/>
-      <!-- Screen Size 176x176 launcher icon size 62x62 -->
-      <iq:product id="descentg1"/>
-      <!-- Screen Size 280x280 launcher icon size 40x40 -->
-      <iq:product id="descentmk2"/>
-      <!-- Screen Size 240x240 launcher icon size 40x40 -->
-      <iq:product id="descentmk2s"/>
-      <!-- Screen Size 416x416 launcher icon size 70x70 -->
+      <iq:product id="d2air"/>
       <iq:product id="d2airx10"/>
-      <!-- Screen Size 416x416 launcher icon size 60x60 -->
+      <iq:product id="d2delta"/>
+      <iq:product id="d2deltapx"/>
+      <iq:product id="d2deltas"/>
       <iq:product id="d2mach1"/>
-      <!-- Screen Size 282x470 launcher icon size 36x36 -->
+      <iq:product id="descentg1"/>
+      <iq:product id="descentg2"/>
+      <iq:product id="descentmk1"/>
+      <iq:product id="descentmk2"/>
+      <iq:product id="descentmk2s"/>
+      <iq:product id="descentmk343mm"/>
+      <iq:product id="descentmk351mm"/>
       <iq:product id="edge1030"/>
       <iq:product id="edge1030bontrager"/>
       <iq:product id="edge1030plus"/>
-      <!-- Screen Size 282x470 launcher icon size 40x40 -->
       <iq:product id="edge1040"/>
-      <!-- Screen Size 246x322 launcher icon size 35x35 -->
+      <iq:product id="edge1050"/>
+      <iq:product id="edge520plus"/>
       <iq:product id="edge530"/>
+      <iq:product id="edge540"/>
+      <iq:product id="edge820"/>
       <iq:product id="edge830"/>
-      <!-- Screen Size 240x400 launcher icon size 36x36 -->
+      <iq:product id="edge840"/>
+      <iq:product id="edgeexplore"/>
       <iq:product id="edgeexplore2"/>
-      <!-- Screen Size 280x280 launcher icon size 40x40 -->
       <iq:product id="enduro"/>
-      <!-- Screen Size 416x416 launcher icon size 60x60 -->
+      <iq:product id="enduro3"/>
       <iq:product id="epix2"/>
-      <!-- Screen Size 390x390 launcher icon size 60x60 -->
       <iq:product id="epix2pro42mm"/>
       <iq:product id="epix2pro47mm"/>
-      <!-- Screen Size 454x454 launcher icon size 60x60 -->
       <iq:product id="epix2pro51mm"/>
-      <!-- Screen Size 240x240 launcher icon size 40x40 -->
+      <iq:product id="fenix5"/>
       <iq:product id="fenix5plus"/>
+      <iq:product id="fenix5s"/>
       <iq:product id="fenix5splus"/>
+      <iq:product id="fenix5x"/>
       <iq:product id="fenix5xplus"/>
-      <!-- Screen Size 260x260 launcher icon size 40x40 -->
       <iq:product id="fenix6"/>
       <iq:product id="fenix6pro"/>
-      <!-- Screen Size 240x240 launcher icon size 40x40 -->
       <iq:product id="fenix6s"/>
       <iq:product id="fenix6spro"/>
-      <!-- Screen Size 280x280 launcher icon size 40x40 -->
       <iq:product id="fenix6xpro"/>
-      <!-- Screen Size 260x260 launcher icon size 40x40 -->
       <iq:product id="fenix7"/>
-      <!-- Screen Size 260x260 launcher icon size 40x40 -->
       <iq:product id="fenix7pro"/>
       <iq:product id="fenix7pronowifi"/>
-      <!-- Screen Size 240x240 launcher icon size 40x40 -->
       <iq:product id="fenix7s"/>
-      <!-- Screen Size 240x240 launcher icon size 40x40 -->
       <iq:product id="fenix7spro"/>
-      <!-- Screen Size 280x280 launcher icon size 40x40 -->
       <iq:product id="fenix7x"/>
-      <!-- Screen Size 280x280 launcher icon size 40x40 -->
       <iq:product id="fenix7xpro"/>
       <iq:product id="fenix7xpronowifi"/>
-      <!-- Screen Size 240x240 launcher icon size 40x40 -->
+      <iq:product id="fenix843mm"/>
+      <iq:product id="fenix847mm"/>
+      <iq:product id="fenix8solar47mm"/>
+      <iq:product id="fenix8solar51mm"/>
+      <iq:product id="fenixchronos"/>
+      <iq:product id="fenixe"/>
+      <iq:product id="fr165"/>
+      <iq:product id="fr165m"/>
       <iq:product id="fr245"/>
       <iq:product id="fr245m"/>
-      <!-- Screen Size 260x260 launcher icon size 40x40 -->
       <iq:product id="fr255"/>
       <iq:product id="fr255m"/>
-      <!-- Screen Size 218x218 launcher icon size 40x40 -->
       <iq:product id="fr255s"/>
       <iq:product id="fr255sm"/>
-      <!-- Screen Size 416x416 launcher icon size 60x60 -->
       <iq:product id="fr265"/>
       <iq:product id="fr265s"/>
-      <!-- Screen Size 208x208 launcher icon size 35x35 -->
       <iq:product id="fr55"/>
-      <!-- Screen Size 240x240 launcher icon size 40x40 -->
+      <iq:product id="fr57042mm"/>
+      <iq:product id="fr57047mm"/>
+      <iq:product id="fr645"/>
+      <iq:product id="fr645m"/>
       <iq:product id="fr745"/>
+      <iq:product id="fr935"/>
       <iq:product id="fr945"/>
       <iq:product id="fr945lte"/>
-      <!-- Screen Size 260x260 launcher icon size 40x40 -->
       <iq:product id="fr955"/>
-      <!-- Screen Size 454x454 launcher icon size 65x65 -->
       <iq:product id="fr965"/>
-      <!-- Screen Size 176x176 launcher icon size 62x62 -->
+      <iq:product id="fr970"/>
+      <iq:product id="gpsmap66"/>
+      <iq:product id="gpsmap67"/>
       <iq:product id="instinct2"/>
-      <!-- Screen Size 163x156 launcher icon size 54x54 -->
       <iq:product id="instinct2s"/>
-      <!-- Screen Size 176x176 launcher icon size 62x62 -->
       <iq:product id="instinct2x"/>
-      <!-- Screen Size 176x176 launcher icon size 26x26 -->
+      <iq:product id="instinct3amoled45mm"/>
+      <iq:product id="instinct3amoled50mm"/>
+      <iq:product id="instinct3solar45mm"/>
       <iq:product id="instinctcrossover"/>
-      <!-- Screen Size 218x218 launcher icon size 30x30 -->
+      <iq:product id="instincte40mm"/>
+      <iq:product id="instincte45mm"/>
       <iq:product id="legacyherocaptainmarvel"/>
-      <!-- Screen Size 260x260 launcher icon size 35x35 -->
       <iq:product id="legacyherofirstavenger"/>
       <iq:product id="legacysagadarthvader"/>
-      <!-- Screen Size 218x218 launcher icon size 30x30 -->
       <iq:product id="legacysagarey"/>
-      <!-- Screen Size 240x240 launcher icon size 40x40 -->
+      <iq:product id="marq2"/>
+      <iq:product id="marq2aviator"/>
       <iq:product id="marqadventurer"/>
       <iq:product id="marqathlete"/>
       <iq:product id="marqaviator"/>
@@ -142,40 +140,35 @@
       <iq:product id="marqdriver"/>
       <iq:product id="marqexpedition"/>
       <iq:product id="marqgolfer"/>
-      <!-- Screen Size 390x390 launcher icon size 60x60 -->
-      <iq:product id="marq2"/>
-      <iq:product id="marq2aviator"/>
-      <!-- Screen Size 390x390 launcher icon size 60x60 -->
+      <iq:product id="montana7xx"/>
       <iq:product id="venu"/>
-      <!-- Screen Size 416x416 launcher icon size 70x70 -->
       <iq:product id="venu2"/>
       <iq:product id="venu2plus"/>
-      <!-- Screen Size 360x360 launcher icon size 61x61 -->
       <iq:product id="venu2s"/>
-      <!-- Screen Size 240x240 launcher icon size 36x36 -->
+      <iq:product id="venu3"/>
+      <iq:product id="venu3s"/>
+      <iq:product id="venud"/>
       <iq:product id="venusq"/>
-      <iq:product id="venusqm"/>
-      <!-- Screen Size 320x360 launcher icon size 40x40 -->
       <iq:product id="venusq2"/>
       <iq:product id="venusq2m"/>
-      <!-- Screen Size 454x454 launcher icon size 70x70 -->
-      <iq:product id="venu3"/>
-      <!-- Screen Size 390x390 launcher icon size 70x70 -->
-      <iq:product id="venu3s"/>
-      <!-- Screen Size 260x260 launcher icon size 35x35 -->
+      <iq:product id="venusqm"/>
+      <iq:product id="vivoactive3"/>
+      <iq:product id="vivoactive3m"/>
+      <iq:product id="vivoactive3mlte"/>
       <iq:product id="vivoactive4"/>
-      <!-- Screen Size 218x218 launcher icon size 30x30 -->
       <iq:product id="vivoactive4s"/>
-      <!-- Screen Size 390x390 launcher icon size 70x70 -->
       <iq:product id="vivoactive5"/>
+      <iq:product id="vivoactive6"/>
     </iq:products>
     <!--
       Use "Monkey C: Edit Permissions" from the Visual Studio Code command
       palette to update permissions.
     -->
     <iq:permissions>
-      <iq:uses-permission id="Communications"/>
+      <iq:uses-permission id="Background"/>
       <iq:uses-permission id="BluetoothLowEnergy"/>
+      <iq:uses-permission id="Communications"/>
+      <iq:uses-permission id="Positioning"/>
     </iq:permissions>
     <!--
       Use "Monkey C: Edit Languages" from the Visual Studio Code command
@@ -184,19 +177,17 @@
     <iq:languages>
       <iq:language>ara</iq:language>
       <iq:language>bul</iq:language>
-      <iq:language>zhs</iq:language>
-      <iq:language>zht</iq:language>
-      <iq:language>hrv</iq:language>
       <iq:language>ces</iq:language>
       <iq:language>dan</iq:language>
-      <iq:language>dut</iq:language>
       <iq:language>deu</iq:language>
-      <iq:language>gre</iq:language>
+      <iq:language>dut</iq:language>
       <iq:language>eng</iq:language>
       <iq:language>est</iq:language>
       <iq:language>fin</iq:language>
       <iq:language>fre</iq:language>
+      <iq:language>gre</iq:language>
       <iq:language>heb</iq:language>
+      <iq:language>hrv</iq:language>
       <iq:language>hun</iq:language>
       <iq:language>ind</iq:language>
       <iq:language>ita</iq:language>
@@ -204,13 +195,12 @@
       <iq:language>kor</iq:language>
       <iq:language>lav</iq:language>
       <iq:language>lit</iq:language>
-      <iq:language>zsm</iq:language>
       <iq:language>nob</iq:language>
       <iq:language>pol</iq:language>
       <iq:language>por</iq:language>
-      <iq:language>slo</iq:language>
       <iq:language>ron</iq:language>
       <!-- <iq:language>rus</iq:language> -->
+      <iq:language>slo</iq:language>
       <iq:language>slv</iq:language>
       <iq:language>spa</iq:language>
       <iq:language>swe</iq:language>
@@ -218,6 +208,9 @@
       <iq:language>tur</iq:language>
       <iq:language>ukr</iq:language>
       <iq:language>vie</iq:language>
+      <iq:language>zhs</iq:language>
+      <iq:language>zht</iq:language>
+      <iq:language>zsm</iq:language>
     </iq:languages>
     <!--
       Use "Monkey C: Configure Monkey Barrel" from the Visual Studio Code

monkey.jungle

@@ -31,36 +31,63 @@ project.manifest = manifest.xml
 #
 # The icons need to scale as a ratio of screen size 48:416 pixels
 #
-# Icon     53   48   46   42   37   32   30   28   26   24   21   18
-# Screen  454  416  390  360  320  280  260  240  218  208  176  156
+# Icon     55  53   48   46   42   37   32   30   28   26   24   21   19  18
+# Screen  480 454  416  390  360  320  280  260  240  218  208  176  166 156
 
+# Screen Size 390x390 launcher icon size 56x56
+approachs50.resourcePath = $(approachs50.resourcePath);resources-launcher-56-56;resources-icons-46
 # Screen Size 390x390 launcher icon size 70x70
 approachs7042mm.resourcePath = $(approachs7042mm.resourcePath);resources-launcher-70-70;resources-icons-46
 # Screen Size 454x454 launcher icon size 80x80
 approachs7047mm.resourcePath = $(approachs7047mm.resourcePath);resources-launcher-80-80;resources-icons-53
+# Screen Size 390x390 launcher icon size 60x60
+d2air.resourcePath = $(d2air.resourcePath);resources-launcher-60-60;resources-icons-46
+# Screen Size 416x416 launcher icon size 70x70
+d2airx10.resourcePath = $(d2airx10.resourcePath);resources-launcher-70-70;resources-icons-48
+# Screen Size 240x240 launcher icon size 40x40
+d2delta.resourcePath = $(d2delta.resourcePath);resources-launcher-40-40;resources-icons-28
+d2deltapx.resourcePath = $(d2deltapx.resourcePath);resources-launcher-40-40;resources-icons-28
+d2deltas.resourcePath = $(d2deltas.resourcePath);resources-launcher-40-40;resources-icons-28
+# Screen Size 416x416 launcher icon size 60x60
+d2mach1.resourcePath = $(d2mach1.resourcePath);resources-launcher-60-60;resources-icons-48
 # Screen Size 176x176 launcher icon size 62x62
 descentg1.resourcePath = $(descentg1.resourcePath);resources-launcher-62-62;resources-icons-21
+# Screen Size 390x390 launcher icon size 60x60
+descentg2.resourcePath = $(descentg2.resourcePath);resources-launcher-60-60;resources-icons-46
+# Screen Size 240x240 launcher icon size 40x40
+descentmk1.resourcePath = $(descentmk1.resourcePath);resources-launcher-40-40;resources-icons-28
 # Screen Size 280x280 launcher icon size 40x40
 descentmk2.resourcePath = $(descentmk2.resourcePath);resources-launcher-40-40;resources-icons-32
 # Screen Size 240x240 launcher icon size 40x40
 descentmk2s.resourcePath = $(descentmk2s.resourcePath);resources-launcher-40-40;resources-icons-28
+# Screen Size 390 x 390 launcher icon size 60x60
+descentmk343mm.resourcePath = $(descentmk2s.resourcePath);resources-launcher-60-60;resources-icons-46
+# Screen Size 454 x 454 launcher icon size 60x60
+descentmk351mm.resourcePath = $(descentmk2s.resourcePath);resources-launcher-60-60;resources-icons-53
 # Screen Size 282x470 launcher icon size 36x36
 edge1030.resourcePath = $(descentmk2s.resourcePath);resources-launcher-36-36;resources-icons-32
 edge1030bontrager.resourcePath = $(edge1030bontrager.resourcePath);resources-launcher-36-36;resources-icons-32
 edge1030plus.resourcePath = $(edge1030plus.resourcePath);resources-launcher-36-36;resources-icons-32
 # Screen Size 282x470 launcher icon size 40x40
 edge1040.resourcePath = $(edge1040.resourcePath);resources-launcher-40-40;resources-icons-32
+# Screen Size 480x800 launcher icon size 68x68
+edge1050.resourcePath = $(edge1050.resourcePath);resources-launcher-68-68;resources-icons-55
+# Screen Size 200x265 launcher icon size 35x35
+edge520plus.resourcePath = $(edge520plus.resourcePath);resources-launcher-35-35;resources-icons-24
 # Screen Size 246x322 launcher icon size 35x35
 edge530.resourcePath = $(edge530.resourcePath);resources-launcher-35-35;resources-icons-28
+edge540.resourcePath = $(edge540.resourcePath);resources-launcher-35-35;resources-icons-28
+# Screen Size 200x265 launcher icon size 35x35
+edge820.resourcePath = $(edge820.resourcePath);resources-launcher-35-35;resources-icons-24
+# Screen Size 246x322 launcher icon size 35x35
 edge830.resourcePath = $(edge830.resourcePath);resources-launcher-35-35;resources-icons-28
+edge840.resourcePath = $(edge840.resourcePath);resources-launcher-35-35;resources-icons-28
 # Screen Size 240x400 launcher icon size 36x36
+edgeexplore.resourcePath = $(edgeexplore.resourcePath);resources-launcher-36-36;resources-icons-28
 edgeexplore2.resourcePath = $(edgeexplore2.resourcePath);resources-launcher-36-36;resources-icons-28
 # Screen Size 280x280 launcher icon size 40x40
 enduro.resourcePath = $(enduro.resourcePath);resources-launcher-40-40;resources-icons-32
-# Screen Size 416x416 launcher icon size 70x70
-d2airx10.resourcePath = $(d2airx10.resourcePath);resources-launcher-70-70;resources-icons-48
-# Screen Size 416x416 launcher icon size 60x60
-d2mach1.resourcePath = $(d2mach1.resourcePath);resources-launcher-60-60;resources-icons-48
+ enduro3.resourcePath = $(enduro3.resourcePath);resources-launcher-40-40;resources-icons-32
 # Screen Size 416x416 launcher icon size 60x60
 epix2.resourcePath = $(epix2.resourcePath);resources-launcher-60-60;resources-icons-48
 # Screen Size 390x390 launcher icon size 60x60
@@ -69,8 +96,13 @@ epix2pro47mm.resourcePath = $(epix2pro47mm.resourcePath);resources-launcher-60-6
 # Screen Size 454x454 launcher icon size 60x60
 epix2pro51mm.resourcePath = $(epix2pro51mm.resourcePath);resources-launcher-60-60;resources-icons-53
 # Screen Size 240x240 launcher icon size 40x40
+fenix5.resourcePath = $(fenix5.resourcePath);resources-launcher-40-40;resources-icons-28
 fenix5plus.resourcePath = $(fenix5plus.resourcePath);resources-launcher-40-40;resources-icons-28
+# Screen Size 218x218 launcher icon size 36x36
+fenix5s.resourcePath = $(fenix5s.resourcePath);resources-launcher-36-36;resources-icons-26
+# Screen Size 240x240 launcher icon size 40x40
 fenix5splus.resourcePath = $(fenix5splus.resourcePath);resources-launcher-40-40;resources-icons-28
+fenix5x.resourcePath = $(fenix5x.resourcePath);resources-launcher-40-40;resources-icons-28
 fenix5xplus.resourcePath = $(fenix5xplus.resourcePath);resources-launcher-40-40;resources-icons-28
 # Screen Size 260x260 launcher icon size 40x40
 fenix6.resourcePath = $(fenix6.resourcePath);resources-launcher-40-40;resources-icons-30
@@ -82,7 +114,6 @@ fenix6spro.resourcePath = $(fenix6spro.resourcePath);resources-launcher-40-40;re
 fenix6xpro.resourcePath = $(fenix6xpro.resourcePath);resources-launcher-40-40;resources-icons-32
 # Screen Size 260x260 launcher icon size 40x40
 fenix7.resourcePath = $(fenix7.resourcePath);resources-launcher-40-40;resources-icons-30
-# Screen Size 260x260 launcher icon size 40x40
 fenix7pro.resourcePath = $(fenix7pro.resourcePath);resources-launcher-40-40;resources-icons-30
 fenix7pronowifi.resourcePath = $(fenix7pronowifi.resourcePath);resources-launcher-40-40;resources-icons-30
 # Screen Size 240x240 launcher icon size 40x40
@@ -91,9 +122,23 @@ fenix7s.resourcePath = $(fenix7s.resourcePath);resources-launcher-40-40;resource
 fenix7spro.resourcePath = $(fenix7spro.resourcePath);resources-launcher-40-40;resources-icons-28
 # Screen Size 280x280 launcher icon size 40x40
 fenix7x.resourcePath = $(fenix7x.resourcePath);resources-launcher-40-40;resources-icons-32
-# Screen Size 280x280 launcher icon size 40x40
 fenix7xpro.resourcePath = $(fenix7xpro.resourcePath);resources-launcher-40-40;resources-icons-32
 fenix7xpronowifi.resourcePath = $(fenix7xpronowifi.resourcePath);resources-launcher-40-40;resources-icons-32
+# Screen Size 416x416 launcher icon size 60x60
+fenix843mm.resourcePath = $(fenix843mm.resourcePath);resources-launcher-60-60;resources-icons-48
+# Screen Size 454x454 launcher icon size 65x65
+fenix847mm.resourcePath = $(fenix847mm.resourcePath);resources-launcher-65-65;resources-icons-53
+# Screen Size 260x260 launcher icon size 40x40
+fenix8solar47mm.resourcePath = $(fenix8solar47mm.resourcePath);resources-launcher-40-40;resources-icons-30
+# Screen Size 280x280 launcher icon size 40x40
+fenix8solar51mm.resourcePath = $(fenix8solar51mm.resourcePath);resources-launcher-40-40;resources-icons-32
+# Screen Size 218x218 launcher icon size 36x36
+fenixchronos.resourcePath = $(fenixchronos.resourcePath);resources-launcher-36-36;resources-icons-26
+# Screen Size 416x416 launcher icon size 60x60
+fenixe.resourcePath = $(fenixe.resourcePath);resources-launcher-60-60;resources-icons-48
+# Screen Size 390 x 390 launcher icon size 54x54
+fr165.resourcePath = $(descentmk2s.resourcePath);resources-launcher-54-54;resources-icons-46
+fr165m.resourcePath = $(descentmk2s.resourcePath);resources-launcher-54-54;resources-icons-46
 # Screen Size 240x240 launcher icon size 40x40
 fr245.resourcePath = $(fr245.resourcePath);resources-launcher-40-40;resources-icons-28
 fr245m.resourcePath = $(fr245m.resourcePath);resources-launcher-40-40;resources-icons-28
@@ -108,22 +153,44 @@ fr265.resourcePath = $(fr265.resourcePath);resources-launcher-60-60;resources-ic
 fr265s.resourcePath = $(fr265s.resourcePath);resources-launcher-60-60;resources-icons-48
 # Screen Size 208x208 launcher icon size 35x35
 fr55.resourcePath = $(fr55.resourcePath);resources-launcher-35-35;resources-icons-24
+# Screen Size 390x390 launcher icon size 54x54
+fr57042mm.resourcePath = $(fr57042mm.resourcePath);resources-launcher-54-54;resources-icons-46
+# Screen Size 454x454 launcher icon size 65x65
+fr57047mm.resourcePath = $(fr57047mm.resourcePath);resources-launcher-65-65;resources-icons-53
+# Screen Size 240x240 launcher icon size 40x40
+fr645.resourcePath = $(fr645.resourcePath);resources-launcher-40-40;resources-icons-28
+fr645m.resourcePath = $(fr645m.resourcePath);resources-launcher-40-40;resources-icons-28
 # Screen Size 240x240 launcher icon size 40x40
 fr745.resourcePath = $(fr745.resourcePath);resources-launcher-40-40;resources-icons-28
+fr935.resourcePath = $(fr935.resourcePath);resources-launcher-40-40;resources-icons-28
 fr945.resourcePath = $(fr945.resourcePath);resources-launcher-40-40;resources-icons-28
 fr945lte.resourcePath = $(fr945lte.resourcePath);resources-launcher-40-40;resources-icons-28
 # Screen Size 260x260 launcher icon size 40x40
 fr955.resourcePath = $(fr955.resourcePath);resources-launcher-40-40;resources-icons-30
 # Screen Size 454x454 launcher icon size 65x65
 fr965.resourcePath = $(fr965.resourcePath);resources-launcher-65-65;resources-icons-53
+fr970.resourcePath = $(fr970.resourcePath);resources-launcher-65-65;resources-icons-53
+# Screen Size 240x400 launcher icon size 38x33
+gpsmap66.resourcePath = $(gpsmap66.resourcePath);resources-launcher-33-33;resources-icons-28
+gpsmap67.resourcePath = $(gpsmap67.resourcePath);resources-launcher-33-33;resources-icons-28
 # Screen Size 176x176 launcher icon size 62x62
-instinct2.resourcePath = $(instinct2.resourcePath);resources-launcher-62-62;resources-icons-21
+instinct2.resourcePath = $(instinct2.resourcePath);resources-launcher-62-62;resources-icons-21-w
 # Screen Size 163x156 launcher icon size 54x54
-instinct2s.resourcePath = $(instinct2s.resourcePath);resources-launcher-54-54;resources-icons-18
+instinct2s.resourcePath = $(instinct2s.resourcePath);resources-launcher-54-54;resources-icons-18-w
 # Screen Size 176x176 launcher icon size 62x62
-instinct2x.resourcePath = $(instinct2x.resourcePath);resources-launcher-62-62;resources-icons-21
+instinct2x.resourcePath = $(instinct2x.resourcePath);resources-launcher-62-62;resources-icons-21-w
+# Screen Size 390x390 launcher icon size 60x60, but the icon size used here is reduced as the menu items were clipped.
+instinct3amoled45mm.resourcePath = $(instinct3amoled45mm.resourcePath);resources-launcher-60-60;resources-icons-32
+# Screen Size 416x416 launcher icon size 60x60, but the icon size used here is reduced as the menu items were clipped.
+instinct3amoled50mm.resourcePath = $(instinct3amoled50mm.resourcePath);resources-launcher-60-60;resources-icons-34
+# Screen Size 176x176 launcher icon size 62x62
+instinct3solar45mm.resourcePath = $(instinct3solar45mm.resourcePath);resources-launcher-62-62;resources-icons-18-w
 # Screen Size 176x176 launcher icon size 26x26
-instinctcrossover.resourcePath = $(instinctcrossover.resourcePath);resources-launcher-26-26;resources-icons-21
+instinctcrossover.resourcePath = $(instinctcrossover.resourcePath);resources-launcher-26-26;resources-icons-21-w
+# Screen Size 166x166 launcher icon size 52x52, but the icon size used here is reduced as the menu items were clipped.
+instincte40mm.resourcePath = $(instincte40mm.resourcePath);resources-launcher-52-52;resources-icons-18-w
+# Screen Size	176x176 launcher icon size 62x62, but the icon size used here is reduced as the menu items were clipped.
+instincte45mm.resourcePath = $(instincte45mm.resourcePath);resources-launcher-62-62;resources-icons-18-w
 # Screen Size 218x218 launcher icon size 30x30
 legacyherocaptainmarvel.resourcePath = $(legacyherocaptainmarvel.resourcePath);resources-launcher-30-30;resources-icons-26
 # Screen Size 260x260 launcher icon size 35x35
@@ -131,6 +198,9 @@ legacyherofirstavenger.resourcePath = $(legacyherofirstavenger.resourcePath);res
 legacysagadarthvader.resourcePath = $(legacysagadarthvader.resourcePath);resources-launcher-35-35;resources-icons-30
 # Screen Size 218x218 launcher icon size 30x30
 legacysagarey.resourcePath = $(legacysagarey.resourcePath);resources-launcher-30-30;resources-icons-26
+# Screen Size 390x390 launcher icon size 60x60
+marq2.resourcePath = $(marq2.resourcePath);resources-launcher-60-60;resources-icons-46
+marq2aviator.resourcePath = $(marq2aviator.resourcePath);resources-launcher-60-60;resources-icons-46
 # Screen Size 240x240 launcher icon size 40x40
 marqadventurer.resourcePath = $(marqadventurer.resourcePath);resources-launcher-40-40;resources-icons-28
 marqathlete.resourcePath = $(marqathlete.resourcePath);resources-launcher-40-40;resources-icons-28
@@ -140,9 +210,8 @@ marqcommander.resourcePath = $(marqcommander.resourcePath);resources-launcher-40
 marqdriver.resourcePath = $(marqdriver.resourcePath);resources-launcher-40-40;resources-icons-28
 marqexpedition.resourcePath = $(marqexpedition.resourcePath);resources-launcher-40-40;resources-icons-28
 marqgolfer.resourcePath = $(marqgolfer.resourcePath);resources-launcher-40-40;resources-icons-28
-# Screen Size 390x390 launcher icon size 60x60
-marq2.resourcePath = $(marq2.resourcePath);resources-launcher-60-60;resources-icons-46
-marq2aviator.resourcePath = $(marq2aviator.resourcePath);resources-launcher-60-60;resources-icons-46
+# Screen Size 480x800 launcher icon size 60x60
+montana7xx.resourcePath = $(montana7xx.resourcePath);resources-launcher-60-60;resources-icons-53
 # Screen Size 390x390 launcher icon size 60x60
 venu.resourcePath = $(venu.resourcePath);resources-launcher-60-60;resources-icons-46
 # Screen Size 416x416 launcher icon size 70x70
@@ -150,19 +219,28 @@ venu2.resourcePath = $(venu2.resourcePath);resources-launcher-70-70;resources-ic
 venu2plus.resourcePath = $(venu2plus.resourcePath);resources-launcher-70-70;resources-icons-48
 # Screen Size 360x360 launcher icon size 61x61
 venu2s.resourcePath = $(venu2s.resourcePath);resources-launcher-61-61;resources-icons-42
-# Screen Size 240x240 launcher icon size 36x36
-venusq.resourcePath = $(venusq.resourcePath);resources-launcher-36-36;resources-icons-28
-venusqm.resourcePath = $(venusqm.resourcePath);resources-launcher-36-36;resources-icons-28
-# Screen Size 320x360 launcher icon size 40x40
-venusq2.resourcePath = $(venusq2.resourcePath);resources-launcher-40-40;resources-icons-38
-venusq2m.resourcePath = $(venusq2m.resourcePath);resources-launcher-40-40;resources-icons-38
 # Screen Size 454x454 launcher icon size 70x70
 venu3.resourcePath = $(venu3.resourcePath);resources-launcher-70-70;resources-icons-53
 # Screen Size 390x390 launcher icon size 70x70
 venu3s.resourcePath = $(venu3s.resourcePath);resources-launcher-70-70;resources-icons-46
+# Screen Size 390x390 launcher icon size 60x60
+venud.resourcePath = $(venud.resourcePath);resources-launcher-60-60;resources-icons-46
+# Screen Size 240x240 launcher icon size 36x36
+venusq.resourcePath = $(venusq.resourcePath);resources-launcher-36-36;resources-icons-28
+# Screen Size 320x360 launcher icon size 40x40
+venusq2.resourcePath = $(venusq2.resourcePath);resources-launcher-40-40;resources-icons-38
+venusq2m.resourcePath = $(venusq2m.resourcePath);resources-launcher-40-40;resources-icons-38
+# Screen Size 240x240 launcher icon size 36x36
+venusqm.resourcePath = $(venusqm.resourcePath);resources-launcher-36-36;resources-icons-28
+# Screen Size 240x240 launcher icon size 40x33
+vivoactive3.resourcePath = $(vivoactive3.resourcePath);resources-launcher-33-33;resources-icons-28
+vivoactive3m.resourcePath = $(vivoactive3m.resourcePath);resources-launcher-33-33;resources-icons-28
+vivoactive3mlte.resourcePath = $(vivoactive3mlte.resourcePath);resources-launcher-33-33;resources-icons-28
 # Screen Size 260x260 launcher icon size 35x35
 vivoactive4.resourcePath = $(vivoactive4.resourcePath);resources-launcher-35-35;resources-icons-30
 # Screen Size 218x218 launcher icon size 30x30
 vivoactive4s.resourcePath = $(vivoactive4s.resourcePath);resources-launcher-30-30;resources-icons-26
-# Screen Size 390x390 launcher icon size 70x70
-vivoactive5.resourcePath = $(vivoactive5.resourcePath);resources-launcher-70-70;resources-icons-46
+# Screen Size 390x390 launcher icon size 56x56
+vivoactive5.resourcePath = $(vivoactive5.resourcePath);resources-launcher-56-56;resources-icons-46
+# Screen Size 390x390 launcher icon size 54x54
+vivoactive6.resourcePath = $(vivoactive6.resourcePath);resources-launcher-54-54;resources-icons-46

removeTranslations.py

@@ -0,0 +1,94 @@
+####################################################################################
+#
+# Distributed under MIT Licence
+#   See https://github.com/house-of-abbey/GarminHomeAssistant/blob/main/LICENSE.
+#
+####################################################################################
+#
+# GarminHomeAssistant is a Garmin IQ application written in Monkey C and routinely
+# tested on a Venu 2 device. The source code is provided at:
+#            https://github.com/house-of-abbey/GarminHomeAssistant.
+#
+# J D Abbey & P A Abbey, 24 July 2025
+#
+#
+# Description:
+#
+# Python script to remove all the translations of a specific id from the XML files.
+#
+# Usage:
+#   python removeTranslations.py <id>
+#
+# Python installation:
+#   pip install beautifulsoup4
+# NB. For XML formatting:
+#   pip install lxml
+#
+# References:
+#  * https://www.crummy.com/software/BeautifulSoup/bs4/doc/
+#  * https://realpython.com/beautiful-soup-web-scraper-python/
+#  * https://www.crummy.com/software/BeautifulSoup/bs4/doc/#parsing-xml
+#  * https://www.crummy.com/software/BeautifulSoup/bs4/doc/#xml
+#
+####################################################################################
+import sys
+# from bs4 import BeautifulSoup
+import os
+
+def remove_translations(file_path: str, translation_id: str) -> None:
+    """
+    Remove all translations of a specific id from the XML file.
+    
+    :param file_path: Path to the XML file.
+    :param translation_id: The id of the translation to remove.
+    """
+    # Breaks the formatting
+    # with open(file_path, "r", encoding="utf-8") as file:
+    #     soup = BeautifulSoup(file, features="xml")
+
+    # # Find all string elements with the specified id
+    # strings_to_remove = soup.find_all("string", {"id": translation_id})
+
+    # for string in strings_to_remove:
+    #     string.decompose()  # Remove the string element
+
+    # # Write the modified XML back to the file
+    # with open(file_path, "wb") as file:
+    #     file.write(soup.encode("utf-8") + b"\n")
+
+    # Use standard string replace instead
+    with open(file_path, "r", encoding="utf-8") as file:
+        content = file.read()
+    
+    new = ""
+    for line in content.splitlines():
+        if not f'id="{translation_id}"' in line:
+            new += line + "\n"
+
+    with open(file_path, "w", encoding="utf-8") as file:
+        file.write(new)
+
+def main(translation_id: str) -> None:
+    """
+    Main function to process all XML files.
+    
+    :param translation_id: The id of the translation to remove.
+    """
+    xml_files = []
+    for directory in os.listdir("."):
+        if os.path.isdir(directory) and "resources-" in directory:
+            xml_file_path = os.path.join(directory, "strings", "strings.xml")
+            if os.path.exists(xml_file_path):
+                xml_files.append(xml_file_path)
+
+    for xml_file in xml_files:
+        print(f"Processing file: {xml_file}")
+        remove_translations(xml_file, translation_id)
+
+if __name__ == "__main__":
+    if len(sys.argv) != 2:
+        print("Usage: python removeTranslations.py <id>")
+        sys.exit(1)
+
+    translation_id = sys.argv[1]
+    main(translation_id)

resources-ara/strings/strings.xml

@@ -9,31 +9,93 @@
    tested on a Venu 2 device. The source code is provided at:
               https://github.com/house-of-abbey/GarminHomeAssistant.
 
-   P A Abbey & J D Abbey, 31 October 2023
+   P A Abbey & J D Abbey & Someone0nEarth & vincentezw, 31 October 2023
 
 -->
 
 <!--
-  Generated by Google Translate: English to Arabic
-  تم إنشاؤها بواسطة ترجمة جوجل من الإنجليزية
+  Generated by Google Translate and gemini-2.5-flash from English to Arabic
+  تم الإنشاء بواسطة ترجمة جوجل و gemini-2.5-flash من الإنجليزية إلى العربية
 -->
 
 <strings>
-  <string id="AppName">HomeAssistant</string>
-  <string id="MenuItemOn">على</string>
-  <string id="MenuItemOff">عن</string>
-  <string id="MenuItemTap">مقبض</string>
-  <string id="MenuItemMenu">قائمة طعام</string>
-  <string id="NoPhone">لا يوجد اتصال الهاتف</string>
-  <string id="NoInternet">لا يوجد اتصال بالإنترنت</string>
-  <string id="NoResponse">لا توجد استجابة، تحقق من الاتصال بالإنترنت</string>
-  <string id="NoMenu">خطأ في إحضار القائمة</string>
-  <string id="NoAPIKey">لا يوجد مفتاح API في إعدادات التطبيق</string>
-  <string id="NoApiUrl">لا يوجد عنوان URL لواجهة برمجة التطبيقات في إعدادات التطبيق</string>
-  <string id="NoConfigUrl">لا يوجد عنوان URL للتكوين في إعدادات التطبيق</string>
-  <string id="ApiFlood">مكالمات API سريعة جدًا. يرجى إبطاء طلباتك.</string>
-  <string id="ApiUrlNotFound">لم يتم العثور على عنوان URL. خطأ محتمل في عنوان URL لواجهة برمجة التطبيقات في الإعدادات.</string>
-  <string id="ConfigUrlNotFound">لم يتم العثور على عنوان URL. خطأ محتمل في عنوان URL للتكوين في الإعدادات.</string>
-  <string id="UnhandledHttpErr">قام طلب HTTP بإرجاع رمز الخطأ =</string>
-  <string id="TrailingSlashErr">يجب ألا يحتوي عنوان URL لواجهة برمجة التطبيقات على شرطة مائلة لاحقة '/'</string>
+  <string id="ApiFlood">مكالمات API سريعة للغاية. يرجى إبطاء طلباتك.</string>
+  <string id="ApiUrlNotFound">لم يتم العثور على عنوان URL. قد يكون هناك خطأ في عنوان URL الخاص بـ
+    API في الإعدادات.</string>
+  <string id="AppName" scope="glance">HomeAssistant</string>
+  <string id="Available" scope="glance">متاح</string>
+  <string id="Cached" scope="glance">مخزّن مؤقتًا</string>
+  <string id="Checking" scope="glance">التحقق ...</string>
+  <string id="ConfigUrlNotFound">لم يتم العثور على عنوان URL. قد يكون هناك خطأ في عنوان URL الخاص
+    بالتكوين في الإعدادات.</string>
+  <string id="Confirm">بالتأكيد؟</string>
+  <string id="Empty">فارغ</string>
+  <string id="Executed" scope="glance">مؤكد</string>
+  <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>
+  <string id="NoInternet">لا يوجد اتصال بالإنترنت.</string>
+  <string id="NoJson">لم يتم إرجاع أي JSON من طلب HTTP.</string>
+  <string id="NoPhone" scope="glance">لا يوجد اتصال هاتفي.</string>
+  <string id="NoPhoneNoCache" scope="glance">لا يوجد اتصال بالهاتف، لا توجد قائمة مخزنة مؤقتًا.</string>
+  <string id="NoResponse">لا توجد استجابة، تحقق من اتصال الإنترنت.</string>
+  <string id="TimedOut">انتهت مهلة الطلب</string>
+  <string id="PinInputLocked">إدخال رمز PIN مغلق لمدة</string>
+  <string id="PotentialError">خطأ محتمل</string>
+  <string id="Seconds">ثوان</string>
+  <string id="TemplateError">خطأ قالب</string>
+  <string id="TrailingSlashErr">يجب ألا يحتوي عنوان URL الخاص بـ API على شرطة مائلة في النهاية '/'.</string>
+  <string id="Unavailable" scope="glance">غير متاح</string>
+  <string id="Unconfigured" scope="glance">غير مهيأ</string>
+  <string id="UnhandledHttpErr">أرجع طلب HTTP رمز الخطأ =</string>
+  <string id="WebhookFailed">فشل في تسجيل Webhook</string>
+  <string id="WrongPin">رمز PIN خاطئ</string>
+  <string id="WifiLteNotAvailable">لا يتوفر Wi-Fi أو LTE</string>
+  <string id="WifiLtePrompt">التنفيذ عبر Wi-Fi/LTE؟</string>
+  <string id="WifiLteExecutionTitle">إرسال إلى Home Assistant.</string>
+  <string id="WifiLteExecutionDataError">لم يتم استلام البيانات.</string>
+  <!-- بالنسبة للإعدادات واجهة المستخدم الرسومية ، يجب أن تكون السلاسل بالترتيب المستخدمة. -->
+  <string id="SettingsSelect">تحديد...</string>
+  <string id="SettingsApiKey">مفتاح API لـ HomeAssistant.</string>
+  <string id="SettingsApiKeyPrompt">رمز وصول طويل الأمد.</string>
+  <string id="SettingsApiUrl">عنوان URL لـ HomeAssistant API.</string>
+  <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>
+  <string id="SettingsPollDelay">تأخير استطلاع إضافي (بالثواني). يضيف تأخيرًا بين تحديث الحالة لجميع
+    عناصر القائمة.</string>
+  <string id="SettingsConfirmTimeout">بعد هذا الوقت (بالثواني)، يتم إغلاق مربع حوار تأكيد لإجراء ما
+    تلقائيًا ويتم إلغاء الإجراء. اضبط على 0 لتعطيل المهلة.</string>
+  <string id="SettingsPin">رمز PIN مكون من 4 أرقام لاستخدامه في جميع الإجراءات التي تتطلب ذلك
+    (0000-9999).</string>
+  <string id="SettingsPinError">يرجى تكوين رمز PIN رقمي مكون من 4 أرقام بين 0000 و 9999 في إعدادات
+    التطبيق.</string>
+  <string id="SettingsTextAlign">محاذاة القائمة: لليسار (إيقاف) أو لليمين (تشغيل).</string>
+  <string id="SettingsLeftToRight">من اليسار إلى اليمين</string>
+  <string id="SettingsRightToLeft">من اليمين إلى اليسار</string>
+  <string id="SettingsWidgetStart">(عنصر واجهة المستخدم فقط) ابدأ التطبيق تلقائيًا من عنصر واجهة
+    المستخدم دون انتظار النقر.</string>
+  <string id="SettingsEnableBatteryLevel">تمكين خدمة الخلفية لإرسال مستوى بطارية الجهاز والموقع
+    وبيانات النشاط (إذا كانت مدعومة) إلى Home Assistant.</string>
+  <string id="SettingsBatteryLevelRefreshRate">معدل التحديث (بالدقائق) الذي يجب أن تكرر فيه خدمة
+    الخلفية إرسال البيانات.</string>
+  <string id="SettingsUserHttpHeader">رأس HTTP مقدم من المستخدم</string>
+  <string id="SettingsUserHttpHeaderDescription">تتطلب بعض عمليات تثبيت Home Assistant تحديد رأس
+    HTTP مخصص لكي تعمل.</string>
+  <string id="SettingsUserHttpHeaderName">رأس HTTP مقدم من المستخدم: الاسم</string>
+  <string id="SettingsUserHttpHeaderValue">رأس HTTP مقدم من المستخدم: القيمة</string>
+  <string id="SettingsClearWebhookId">أعد الاتصال بـ Home Assistant (مسح معرف Webhook، انظر دليل
+    استكشاف الأخطاء وإصلاحها).</string>
+  <string id="SettingsWebhookId">(للقراءة فقط) معرف Webhook الذي تم إنشاؤه بواسطة الجهاز لتحديثات
+    خدمة الخلفية. قد تحتاج هذا لتصحيح الأخطاء.</string>
 </strings>

resources-bul/strings/strings.xml

@@ -9,31 +9,79 @@
    tested on a Venu 2 device. The source code is provided at:
               https://github.com/house-of-abbey/GarminHomeAssistant.
 
-   P A Abbey & J D Abbey, 31 October 2023
+   P A Abbey & J D Abbey & Someone0nEarth & vincentezw, 31 October 2023
 
 -->
 
 <!--
-  Generated by Google Translate: English to Bulgarian
-  Генерирано от Google Translate от английски
+  Generated by Google Translate and gemini-2.5-flash from English to Bulgarian
+  Генерирано от Google Translate и gemini-2.5-flash от английски на български
 -->
 
 <strings>
-  <string id="AppName">HomeAssistant</string>
-  <string id="MenuItemOn">На</string>
-  <string id="MenuItemOff">Изкл</string>
-  <string id="MenuItemTap">Докоснете</string>
-  <string id="MenuItemMenu">Меню</string>
-  <string id="NoPhone">Няма телефонна връзка</string>
-  <string id="NoInternet">Няма интернет връзка</string>
-  <string id="NoResponse">Няма отговор, проверете интернет връзката</string>
-  <string id="NoMenu">Грешка при извличане на менюто</string>
-  <string id="NoAPIKey">Няма API ключ в настройките на приложението</string>
-  <string id="NoApiUrl">Няма URL адрес на API в настройките на приложението</string>
-  <string id="NoConfigUrl">Няма конфигурационен URL адрес в настройките на приложението</string>
-  <string id="ApiFlood">Извикванията на API са твърде бързи. Моля, забавете вашите заявки.</string>
-  <string id="ApiUrlNotFound">URL не е намерен. Потенциална грешка в URL адреса на API в настройките.</string>
-  <string id="ConfigUrlNotFound">URL не е намерен. Потенциална грешка в URL адреса на конфигурацията в настройките.</string>
-  <string id="UnhandledHttpErr">HTTP заявката върна код на грешка =</string>
-  <string id="TrailingSlashErr">URL адресът на API не трябва да има наклонена черта '/' в края</string>
+  <string id="ApiFlood">API повикванията са твърде чести. Моля, забавете заявките си.</string>
+  <string id="ApiUrlNotFound">URL адрес не е намерен. Потенциална грешка в URL адреса на API в настройките.</string>
+  <string id="AppName" scope="glance">HomeAssistant</string>
+  <string id="Available" scope="glance">На разположение</string>
+  <string id="Cached" scope="glance">Кеширан</string>
+  <string id="Checking" scope="glance">Проверка ...</string>
+  <string id="ConfigUrlNotFound">URL адрес не е намерен. Възможна грешка в URL адреса за конфигурация в настройките.</string>
+  <string id="Confirm">Сигурно?</string>
+  <string id="Empty">Празен</string>
+  <string id="Executed" scope="glance">Потвърдено</string>
+  <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>
+  <string id="NoInternet">Няма интернет връзка.</string>
+  <string id="NoJson">Не е върнат JSON от HTTP заявка.</string>
+  <string id="NoPhone" scope="glance">Няма телефонна връзка.</string>
+  <string id="NoPhoneNoCache" scope="glance">Няма телефонна връзка, няма кеширано меню.</string>
+  <string id="NoResponse">Няма отговор, проверете интернет връзката.</string>
+  <string id="TimedOut">Заявка изтече</string>
+  <string id="PinInputLocked">Въвеждането на ПИН е заключено за</string>
+  <string id="PotentialError">Потенциална грешка</string>
+  <string id="Seconds">секунди</string>
+  <string id="TemplateError">Грешка в шаблона</string>
+  <string id="TrailingSlashErr">URL адресът на API не трябва да завършва с наклонена черта '/'.</string>
+  <string id="Unavailable" scope="glance">Недостъпни</string>
+  <string id="Unconfigured" scope="glance">Неконфигуриран</string>
+  <string id="UnhandledHttpErr">HTTP заявката върна код за грешка = </string>
+  <string id="WebhookFailed">Неуспешна регистрация на Webhook</string>
+  <string id="WrongPin">Грешен ПИН</string>
+  <string id="WifiLteNotAvailable">Няма налични Wi-Fi или LTE</string>
+  <string id="WifiLtePrompt">Изпълнете над Wi-Fi/LTE?</string>
+  <string id="WifiLteExecutionTitle">Изпращане до Home Assistant.</string>
+  <string id="WifiLteExecutionDataError">Няма получени данни.</string>
+  <!-- За GUI на настройките, низовете трябва да са в реда, в който се използват. -->
+  <string id="SettingsSelect">Изберете ...</string>
+  <string id="SettingsApiKey">API ключ за Home Assistant.</string>
+  <string id="SettingsApiKeyPrompt">Дълготраен маркер за достъп.</string>
+  <string id="SettingsApiUrl">URL за Home Assistant API.</string>
+  <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>
+  <string id="SettingsPollDelay">Допълнително забавяне на опресняването (в секунди). Добавя забавяне между актуализацията на състоянието на всички елементи от менюто.</string>
+  <string id="SettingsConfirmTimeout">След това време (в секунди) диалоговият прозорец за потвърждение за действие автоматично се затваря и действието се отменя. Задайте на 0, за да деактивирате изчакването.</string>
+  <string id="SettingsPin">4-цифрен ПИН, който ще се използва за всички действия, които го изискват (0000-9999).</string>
+  <string id="SettingsPinError">Моля, конфигурирайте валиден 4-цифрен цифров ПИН между 0000 и 9999 в настройките на приложението.</string>
+  <string id="SettingsTextAlign">Наляво (изключено) или вдясно (включено) изравняване на менюто.</string>
+  <string id="SettingsLeftToRight">Отляво надясно</string>
+  <string id="SettingsRightToLeft">Отдясно наляво</string>
+  <string id="SettingsWidgetStart">(Само при джаджа) Приложението се стартира автоматично от джаджата, без да се чака докосване.</string>
+  <string id="SettingsEnableBatteryLevel">Активиране на фоновата услуга за изпращане на нивото на батерията на устройството, местоположението и (ако се поддържа) данни за активност към Home Assistant.</string>
+  <string id="SettingsBatteryLevelRefreshRate">Скоростта на опресняване (в минути), при която фоновата услуга трябва да повтаря изпращането на данни.</string>
+  <string id="SettingsUserHttpHeader">Потребителска HTTP заглавка</string>
+  <string id="SettingsUserHttpHeaderDescription">Някои инсталации на Home Assistant изискват специфицирането на персонализирана HTTP заглавка, за да функционират.</string>
+  <string id="SettingsUserHttpHeaderName">Потребителска HTTP заглавка: Име</string>
+  <string id="SettingsUserHttpHeaderValue">Потребителска HTTP заглавка: Стойност</string>
+  <string id="SettingsClearWebhookId">Свържете се отново с Home Assistant (изчистване на Webhook ID, вижте ръководството за отстраняване на неизправности).</string>
+  <string id="SettingsWebhookId">(Само за четене) Webhook ID, създаден от устройството за актуализации на фоновите услуги. Може да ви е необходим за отстраняване на грешки.</string>
 </strings>

resources-ces/strings/corrections.xml

@@ -0,0 +1,24 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!--
+
+   Distributed under MIT Licence
+     See https://github.com/house-of-abbey/GarminHomeAssistantWidget/blob/main/LICENSE.
+
+
+   GarminHomeAssistantWidget is a Garmin IQ widget written in Monkey C. The source code is provided at:
+              https://github.com/house-of-abbey/GarminHomeAssistantWidget.
+
+   P A Abbey & J D Abbey & Someone0nEarth, 15 April 2024
+
+-->
+
+<!--
+  Corrections for the Czech language
+  Opravy pro český jazyk
+-->
+
+<strings>
+  <string id="Confirm">Určitě?</string>
+  <string id="Available">Dostupné</string>
+  <string id="GlanceMenu">Menu</string>
+</strings>

resources-ces/strings/strings.xml

@@ -9,31 +9,79 @@
    tested on a Venu 2 device. The source code is provided at:
               https://github.com/house-of-abbey/GarminHomeAssistant.
 
-   P A Abbey & J D Abbey, 31 October 2023
+   P A Abbey & J D Abbey & Someone0nEarth & vincentezw, 31 October 2023
 
 -->
 
 <!--
-  Generated by Google Translate: English to Czech
-  Generováno překladačem Google z angličtiny
+  Generated by Google Translate and gemini-2.5-flash from English to Czech
+  Vygenerováno pomocí Google Translate a gemini-2.5-flash z angličtiny do češtiny
 -->
 
 <strings>
-  <string id="AppName">HomeAssistant</string>
-  <string id="MenuItemOn">Na</string>
-  <string id="MenuItemOff">Vypnuto</string>
-  <string id="MenuItemTap">Klepněte</string>
-  <string id="MenuItemMenu">Jídelní lístek</string>
-  <string id="NoPhone">Žádné telefonní spojení</string>
-  <string id="NoInternet">Žádné internetové připojení</string>
-  <string id="NoResponse">Žádná odpověď, zkontrolujte připojení k internetu</string>
-  <string id="NoMenu">Chyba načítání nabídky</string>
-  <string id="NoAPIKey">V nastavení aplikace není žádný klíč API</string>
-  <string id="NoApiUrl">V nastavení aplikace není žádná adresa URL API</string>
-  <string id="NoConfigUrl">V nastavení aplikace není žádná konfigurační URL</string>
-  <string id="ApiFlood">Příliš rychlá volání API. Zpomalte prosím své požadavky.</string>
-  <string id="ApiUrlNotFound">Adresa URL nenalezena. Potenciální chyba adresy URL rozhraní API v nastavení.</string>
-  <string id="ConfigUrlNotFound">Adresa URL nenalezena. Potenciální chyba konfigurační adresy URL v nastavení.</string>
-  <string id="UnhandledHttpErr">Požadavek HTTP vrátil kód chyby =</string>
-  <string id="TrailingSlashErr">Adresa URL rozhraní API nesmí mít koncové lomítko „/“</string>
+  <string id="ApiFlood">Volání API jsou příliš rychlá. Prosím, zpomalte své požadavky.</string>
+  <string id="ApiUrlNotFound">URL nebyla nalezena. Potenciální chyba URL API v nastavení.</string>
+  <string id="AppName" scope="glance">HomeAssistant</string>
+  <string id="Available" scope="glance">Dostupné</string>
+  <string id="Cached" scope="glance">V mezipaměti</string>
+  <string id="Checking" scope="glance">Kontrola ...</string>
+  <string id="ConfigUrlNotFound">URL nebyla nalezena. Potenciální chyba URL konfigurace v nastavení.</string>
+  <string id="Confirm">Určitě?</string>
+  <string id="Empty">Prázdný</string>
+  <string id="Executed" scope="glance">Potvrzeno</string>
+  <string id="GlanceMenu" scope="glance">Menu</string>
+  <string id="Memory" scope="glance">Paměť</string>
+  <string id="MenuUpdated">Menu aktualizováno, restartujte.</string>
+  <string id="MenuCheckDisabled">Aktualizace menu zakázány.</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">Žádná konfigurační URL v nastavení aplikace.</string>
+  <string id="NoInternet">Žádné připojení k internetu.</string>
+  <string id="NoJson">Žádný JSON se nevrátil z požadavku HTTP.</string>
+  <string id="NoPhone" scope="glance">Žádné telefonní připojení.</string>
+  <string id="NoPhoneNoCache" scope="glance">Žádné připojení telefonu, žádné menu v mezipaměti.</string>
+  <string id="NoResponse">Žádná odpověď, zkontrolujte připojení k internetu.</string>
+  <string id="TimedOut">Vypršel časový limit požadavku.</string>
+  <string id="PinInputLocked">Vstup PIN uzamčen na</string>
+  <string id="PotentialError">Potenciální chyba</string>
+  <string id="Seconds">sekundy</string>
+  <string id="TemplateError">Chyba šablony</string>
+  <string id="TrailingSlashErr">URL API nesmí mít koncové lomítko '/'.</string>
+  <string id="Unavailable" scope="glance">Nedostupné</string>
+  <string id="Unconfigured" scope="glance">Nekonfigurované</string>
+  <string id="UnhandledHttpErr">HTTP požadavek vrátil chybový kód =</string>
+  <string id="WebhookFailed">Nepodařilo se zaregistrovat Webhook</string>
+  <string id="WrongPin">Špatný PIN</string>
+  <string id="WifiLteNotAvailable">Není k dispozici žádné Wi-Fi nebo LTE</string>
+  <string id="WifiLtePrompt">Provést přes Wi-Fi/LTE?</string>
+  <string id="WifiLteExecutionTitle">Odesílám do Home Assistant.</string>
+  <string id="WifiLteExecutionDataError">Nebyla přijata žádná data.</string>
+  <!-- Pro GUI nastavení by měly být řetězce v pořadí, které jsou použity. -->
+  <string id="SettingsSelect">Vybrat...</string>
+  <string id="SettingsApiKey">Klíč API pro HomeAssistant.</string>
+  <string id="SettingsApiKeyPrompt">Dlouhodobý přístupový token.</string>
+  <string id="SettingsApiUrl">URL pro HomeAssistant API.</string>
+  <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ři příštím spuštění?</string>
+  <string id="SettingsEnableMenuUpdateCheck">Kontrolovat aktualizace menu při spuštění aplikace? Poznámka: Ukládání menu do mezipaměti musí být povoleno. Toto nastavení může způsobit pád starších zařízení s menší pamětí.</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">Časový limit v sekundách. Ukončete aplikaci po této době nečinnosti, abyste šetřili baterii zařízení.</string>
+  <string id="SettingsPollDelay">Další zpoždění dotazování (v sekundách). Přidá zpoždění mezi aktualizací stavu všech položek nabídky.</string>
+  <string id="SettingsConfirmTimeout">Po této době (v sekundách) je potvrzovací dialog pro akci automaticky uzavřen a akce je zrušena. Nastavte na 0 pro deaktivaci časového limitu.</string>
+  <string id="SettingsPin">4místný PIN, který se má použít pro všechny akce, které jej vyžadují (0000-9999).</string>
+  <string id="SettingsPinError">Nakonfigurujte prosím platný čtyřmístný číselný PIN mezi 0000 a 9999 v nastavení aplikace.</string>
+  <string id="SettingsTextAlign">Vlevo (vypnuto) nebo vpravo (zapnuto) zarovnání nabídky.</string>
+  <string id="SettingsLeftToRight">Zleva doprava</string>
+  <string id="SettingsRightToLeft">Vpravo doleva</string>
+  <string id="SettingsWidgetStart">(Pouze widget) Automatické spuštění aplikace z widgetu bez čekání na klepnutí.</string>
+  <string id="SettingsEnableBatteryLevel">Povolit službě na pozadí odesílat úroveň baterie zařízení, jeho polohu a (pokud je podporováno) údaje o aktivitě do Home Assistant.</string>
+  <string id="SettingsBatteryLevelRefreshRate">Frekvence aktualizace (v minutách), s jakou má služba na pozadí opakovaně odesílat data.</string>
+  <string id="SettingsUserHttpHeader">Uživatelská hlavička HTTP</string>
+  <string id="SettingsUserHttpHeaderDescription">Některé instalace Home Assistant vyžadují specifikaci vlastní hlavičky HTTP pro správnou funkci.</string>
+  <string id="SettingsUserHttpHeaderName">Uživatelská hlavička HTTP: Název</string>
+  <string id="SettingsUserHttpHeaderValue">Uživatelská hlavička HTTP: Hodnota</string>
+  <string id="SettingsClearWebhookId">Znovu se připojte k Home Assistant (vymazat ID Webhooku, viz příručka pro odstraňování problémů).</string>
+  <string id="SettingsWebhookId">(Pouze pro čtení) ID Webhooku vytvořené zařízením pro aktualizace služby na pozadí. Možná to budete potřebovat pro ladění.</string>
 </strings>

resources-dan/strings/strings.xml

@@ -9,31 +9,79 @@
    tested on a Venu 2 device. The source code is provided at:
               https://github.com/house-of-abbey/GarminHomeAssistant.
 
-   P A Abbey & J D Abbey, 31 October 2023
+   P A Abbey & J D Abbey & Someone0nEarth & vincentezw, 31 October 2023
 
 -->
 
 <!--
-  Generated by Google Translate: English to Danish
-  Genereret af Google Translate fra engelsk
+  Generated by Google Translate and gemini-2.5-flash from English to Danish
+  Genereret af Google Translate og gemini-2.5-flash fra engelsk til dansk
 -->
 
 <strings>
-  <string id="AppName">HomeAssistant</string>
-  <string id="MenuItemOn">På</string>
-  <string id="MenuItemOff">Af</string>
-  <string id="MenuItemTap">Tryk på</string>
-  <string id="MenuItemMenu">Menu</string>
-  <string id="NoPhone">Ingen telefonforbindelse</string>
-  <string id="NoInternet">Ingen internetforbindelse</string>
-  <string id="NoResponse">Intet svar, tjek internetforbindelse</string>
-  <string id="NoMenu">Fejl ved menuhentning</string>
-  <string id="NoAPIKey">Ingen API-nøgle i applikationsindstillingerne</string>
-  <string id="NoApiUrl">Ingen API-URL i applikationsindstillingerne</string>
-  <string id="NoConfigUrl">Ingen konfigurations-URL i applikationsindstillingerne</string>
-  <string id="ApiFlood">API-kald for hurtigt. Sænk venligst dine anmodninger.</string>
-  <string id="ApiUrlNotFound">URL ikke fundet. Potentiel API URL-fejl i indstillinger.</string>
+  <string id="ApiFlood">API-kald er for hyppige. Sænk venligst dine anmodninger.</string>
+  <string id="ApiUrlNotFound">URL ikke fundet. Potentiel API-URL-fejl i indstillinger.</string>
+  <string id="AppName" scope="glance">HomeAssistant</string>
+  <string id="Available" scope="glance">Tilgængelig</string>
+  <string id="Cached" scope="glance">Cachelagret</string>
+  <string id="Checking" scope="glance">Kontrollerer...</string>
   <string id="ConfigUrlNotFound">URL ikke fundet. Potentiel konfigurations-URL-fejl i indstillinger.</string>
-  <string id="UnhandledHttpErr">HTTP-anmodning returnerede fejlkode =</string>
-  <string id="TrailingSlashErr">API URL må ikke have en efterfølgende skråstreg '/'</string>
+  <string id="Confirm">Sikker?</string>
+  <string id="Empty">Tom</string>
+  <string id="Executed" scope="glance">Bekræftet</string>
+  <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>
+  <string id="NoInternet">Ingen internetforbindelse.</string>
+  <string id="NoJson">Ingen JSON modtaget fra HTTP-anmodning.</string>
+  <string id="NoPhone" scope="glance">Ingen telefonforbindelse.</string>
+  <string id="NoPhoneNoCache" scope="glance">Ingen telefonforbindelse, ingen cachelagret menu.</string>
+  <string id="NoResponse">Intet svar, tjek internetforbindelsen.</string>
+  <string id="TimedOut">Anmodning udløb</string>
+  <string id="PinInputLocked">PIN-indtastning låst i</string>
+  <string id="PotentialError">Potentiel fejl</string>
+  <string id="Seconds">sekunder</string>
+  <string id="TemplateError">Skabelonfejl</string>
+  <string id="TrailingSlashErr">API-URL må ikke have en afsluttende skråstreg '/'.</string>
+  <string id="Unavailable" scope="glance">Utilgængelig</string>
+  <string id="Unconfigured" scope="glance">Ukonfigureret</string>
+  <string id="UnhandledHttpErr">HTTP-anmodning returnerede fejlkode = </string>
+  <string id="WebhookFailed">Kunne ikke registrere webhook</string>
+  <string id="WrongPin">Forkert PIN</string>
+  <string id="WifiLteNotAvailable">Ingen Wi-Fi eller LTE tilgængelig</string>
+  <string id="WifiLtePrompt">Udfør via Wi-Fi/LTE?</string>
+  <string id="WifiLteExecutionTitle">Sender til Home Assistant.</string>
+  <string id="WifiLteExecutionDataError">Ingen data modtaget.</string>
+  <!-- For indstillingerne GUI skal strenge være i den rækkefølge, de bruges. -->
+  <string id="SettingsSelect">Vælg...</string>
+  <string id="SettingsApiKey">API-nøgle til Home Assistant.</string>
+  <string id="SettingsApiKeyPrompt">Langvarig adgangstoken.</string>
+  <string id="SettingsApiUrl">URL til Home Assistant API.</string>
+  <string id="SettingsConfigUrl">URL til menukonfiguration (JSON).</string>
+  <string id="SettingsCacheConfig">Skal applikationen cachelagre menukonfigurationen?</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 i sekunder. Afslut applikationen efter denne periode med inaktivitet for at spare på enhedens batteri.</string>
+  <string id="SettingsPollDelay">Yderligere afstemningsforsinkelse (i sekunder). Tilføjer en forsinkelse mellem statusopdateringen af alle menupunkter.</string>
+  <string id="SettingsConfirmTimeout">Efter denne tid (i sekunder) lukkes en bekræftelsesdialog for en handling automatisk, og handlingen annulleres. Indstil til 0 for at deaktivere timeout.</string>
+  <string id="SettingsPin">4-cifret PIN, der skal bruges til alle handlinger, der kræver det (0000-9999).</string>
+  <string id="SettingsPinError">Konfigurer venligst en gyldig 4-cifret numerisk PIN mellem 0000 og 9999 i applikationsindstillingerne.</string>
+  <string id="SettingsTextAlign">Venstre (fra) eller højre (til) menujustering.</string>
+  <string id="SettingsLeftToRight">Venstre til højre</string>
+  <string id="SettingsRightToLeft">Højre til venstre</string>
+  <string id="SettingsWidgetStart">(Kun widget) Start automatisk applikationen fra widgetten uden at vente på et tryk.</string>
+  <string id="SettingsEnableBatteryLevel">Aktivér baggrundstjenesten til at sende enhedens batteriniveau, lokation og (hvis understøttet) aktivitetsdata til Home Assistant.</string>
+  <string id="SettingsBatteryLevelRefreshRate">Opdateringshastigheden (i minutter), hvormed baggrundstjenesten skal gentage afsendelse af data.</string>
+  <string id="SettingsUserHttpHeader">Brugerdefineret HTTP-header</string>
+  <string id="SettingsUserHttpHeaderDescription">Nogle Home Assistant-installationer kræver angivelse af en brugerdefineret HTTP-header for at fungere.</string>
+  <string id="SettingsUserHttpHeaderName">Brugerdefineret HTTP-header: Navn</string>
+  <string id="SettingsUserHttpHeaderValue">Brugerdefineret HTTP-header: Værdi</string>
+  <string id="SettingsClearWebhookId">Opret forbindelse igen til Home Assistant (ryd Webhook-ID, se fejlfindingsguide).</string>
+  <string id="SettingsWebhookId">(Kun læsning) Webhook-ID'et oprettet af enheden til opdateringer fra baggrundstjenesten. Du kan få brug for dette til fejlfinding.</string>
 </strings>

resources-deu/strings/corrections.xml

@@ -9,17 +9,72 @@
    tested on a Venu 2 device. The source code is provided at:
               https://github.com/house-of-abbey/GarminHomeAssistant.
 
-   P A Abbey & J D Abbey, 14 November 2023
+   P A Abbey & J D Abbey & Someone0nEarth, 14 November 2023
 
 -->
 
 <!--
   Corrections for the German language
   Korrekturen für die deutsche Sprache
+  Contributors: 
+  Someone0nEarth
+  tarekbecker
+  moesterheld
+  tispokes
 -->
 
 <strings>
-  <string id="MenuItemTap">Antippen</string>
-  <string id="MenuItemMenu">Menü</string>
+  <string id="ApiFlood">Zu viele API-Aufrufe in kurzer Zeit. Bitte verlangsame deine Anfragen.</string>
+  <string id="ApiUrlNotFound">URL nicht gefunden. Möglicher Fehler in der API-URL in den Einstellungen.</string>
+  <string id="Available" scope="glance">OK</string>
+  <string id="Cached" scope="glance">gecacht</string>
+  <string id="Checking" scope="glance">Prüfe...</string>
+  <string id="ConfigUrlNotFound">URL nicht gefunden. Möglicherweise falsche Konfigurations-URL in den Einstellungen.</string>
+  <string id="GlanceMenu" scope="glance">Menü</string>
+  <string id="Memory" scope="glance">Speicher</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>
+  <string id="NoJson">Keine JSON-Datei aus der HTTP-Anfrage zurückbekommen.</string>
+  <string id="NoPhoneNoCache" scope="glance">Keine Telefonverbindung und kein gecachtes Menü.</string>
+  <string id="NoResponse">Keine Antwort, bitte Internetverbindung prüfen.</string>
+  <string id="TimedOut">Anfragezeit überschritten.</string>
+  <string id="PinInputLocked">PIN-Eingabe gesperrt für</string>
+  <string id="PotentialError">Möglicher Fehler</string>
+  <string id="TemplateError">Template konnte nicht gerendert werden</string>
+  <string id="TrailingSlashErr">API-URL darf nicht mit einem Schrägstrich '/' enden.</string>
   <string id="UnhandledHttpErr">Die HTTP-Anfrage gab folgenden Fehlercode zurück = </string>
+  <string id="WebhookFailed">Webhook-Registrierung fehlgeschlagen.</string>
+  <string id="WrongPin">Falsche PIN.</string>
+  <string id="WifiLteNotAvailable">Kein WLAN oder LTE verfügbar.</string>
+  <string id="WifiLtePrompt">Über WLAN/LTE ausführen?</string>
+  <string id="WifiLteExecutionTitle">Sende an Home Assistant.</string>
+  <string id="WifiLteExecutionDataError">Keine Daten empfangen.</string>
+
+  <!-- Für die Einstellungs-GUI: Reihenfolge entspricht der Nutzung -->
+  <string id="SettingsSelect">Auswählen...</string>
+  <string id="SettingsApiKey">API-Schlüssel für HomeAssistant.</string>
+  <string id="SettingsApiKeyPrompt">Langzeit-Zugangstoken.</string>
+  <string id="SettingsApiUrl">URL der HomeAssistant-API.</string>
+  <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="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>
+  <string id="SettingsPollDelay">Zusätzliche Abfrageverzögerung (in Sekunden). Fügt zwischen den Status-Updates der Menüeinträge eine Pause ein.</string>
+  <string id="SettingsConfirmTimeout">Nach dieser Zeit (in Sekunden) wird ein Bestätigungsdialog automatisch geschlossen und die Aktion abgebrochen. Mit 0 deaktivieren.</string>
+  <string id="SettingsPin">4-stellige PIN für alle Aktionen, die diese erfordern (0000-9999).</string>
+  <string id="SettingsPinError">Bitte eine gültige 4-stellige numerische PIN in den App Einstellungen eingeben (0000-9999).</string>
+  <string id="SettingsTextAlign">Menüausrichtung: Links (aus) oder Rechts (ein).</string>
+  
+  <string id="SettingsRightToLeft">Von rechts nach links</string>
+  <string id="SettingsWidgetStart">(Nur Widget) App automatisch aus dem Widget starten, ohne auf Tippen zu warten.</string>
+  <string id="SettingsEnableBatteryLevel">Hintergrunddienst aktivieren, um Akkustand, Standort und (falls unterstützt) Aktivitätsdaten an Home Assistant zu senden.</string>
+  <string id="SettingsBatteryLevelRefreshRate">Intervall (in Minuten), in dem der Hintergrunddienst die Daten erneut senden soll.</string>
+  <string id="SettingsUserHttpHeader">Zusätzlicher HTTP-Header</string>
+  <string id="SettingsUserHttpHeaderDescription">Einige Home Assistant-Installationen erfordern die Angabe eines benutzerdefinierten HTTP-Headers, um zu funktionieren.</string>
+  <string id="SettingsUserHttpHeaderName">Zusätzlicher HTTP-Header: Name</string>
+  <string id="SettingsUserHttpHeaderValue">Zusätzlicher HTTP-Header: Value</string>
+  <string id="SettingsWebhookId">(Nur lesen) Die vom Gerät erstellte Webhook-ID für Hintergrund-Updates. Kann zum Debuggen benötigt werden.</string>
 </strings>

resources-deu/strings/strings.xml

@@ -9,31 +9,79 @@
    tested on a Venu 2 device. The source code is provided at:
               https://github.com/house-of-abbey/GarminHomeAssistant.
 
-   P A Abbey & J D Abbey, 31 October 2023
+   P A Abbey & J D Abbey & Someone0nEarth & vincentezw, 31 October 2023
 
 -->
 
 <!--
-  Generated by Google Translate: English to German
-  Erstellt durch Google Translate aus dem Englischen
+  Generated by Google Translate and gemini-2.5-flash from English to German
+  Generiert von Google Translate und gemini-2.5-flash aus dem Englischen ins Deutsche
 -->
 
 <strings>
-  <string id="AppName">HomeAssistant</string>
-  <string id="MenuItemOn">An</string>
-  <string id="MenuItemOff">Aus</string>
-  <string id="MenuItemTap">Antippen</string>
-  <string id="MenuItemMenu">Menü</string>
-  <string id="NoPhone">Keine Telefonverbindung</string>
-  <string id="NoInternet">Keine Internetverbindung</string>
-  <string id="NoResponse">Keine Antwort, überprüfen Sie die Internetverbindung</string>
-  <string id="NoMenu">Fehler beim Abrufen des Menüs</string>
-  <string id="NoAPIKey">Kein API-Schlüssel in den Anwendungseinstellungen</string>
-  <string id="NoApiUrl">Keine API-URL in den Anwendungseinstellungen</string>
-  <string id="NoConfigUrl">Keine Konfigurations-URL in den Anwendungseinstellungen</string>
-  <string id="ApiFlood">API-Aufrufe zu schnell. Bitte verlangsamen Sie Ihre Anfragen.</string>
-  <string id="ApiUrlNotFound">URL nicht gefunden. Möglicher API-URL-Fehler in den Einstellungen.</string>
-  <string id="ConfigUrlNotFound">URL nicht gefunden. Möglicher Konfigurations-URL-Fehler in den Einstellungen.</string>
+  <string id="ApiFlood">Zu viele API-Aufrufe in kurzer Zeit. Bitte verlangsame deine Anfragen.</string>
+  <string id="ApiUrlNotFound">URL nicht gefunden. Möglicher Fehler in der API-URL in den Einstellungen.</string>
+  <string id="AppName" scope="glance">HomeAssistant</string>
+  <string id="Available" scope="glance">OK</string>
+  <string id="Cached" scope="glance">gecacht</string>
+  <string id="Checking" scope="glance">Prüfe...</string>
+  <string id="ConfigUrlNotFound">URL nicht gefunden. Möglicherweise falsche Konfigurations-URL in den Einstellungen.</string>
+  <string id="Confirm">Sicher?</string>
+  <string id="Empty">Leer</string>
+  <string id="Executed" scope="glance">Bestätigt</string>
+  <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>
+  <string id="NoInternet">Keine Internetverbindung.</string>
+  <string id="NoJson">Keine JSON-Datei aus der HTTP-Anfrage zurückbekommen.</string>
+  <string id="NoPhone" scope="glance">Keine Telefonverbindung.</string>
+  <string id="NoPhoneNoCache" scope="glance">Keine Telefonverbindung und kein gecachtes Menü.</string>
+  <string id="NoResponse">Keine Antwort, bitte Internetverbindung prüfen.</string>
+  <string id="TimedOut">Anfragezeit überschritten.</string>
+  <string id="PinInputLocked">PIN-Eingabe gesperrt für</string>
+  <string id="PotentialError">Möglicher Fehler</string>
+  <string id="Seconds">Sekunden</string>
+  <string id="TemplateError">Template konnte nicht gerendert werden</string>
+  <string id="TrailingSlashErr">API-URL darf nicht mit einem Schrägstrich '/' enden.</string>
+  <string id="Unavailable" scope="glance">Nicht verfügbar</string>
+  <string id="Unconfigured" scope="glance">Nicht konfiguriert</string>
   <string id="UnhandledHttpErr">Die HTTP-Anfrage gab folgenden Fehlercode zurück = </string>
-  <string id="TrailingSlashErr">Die API-URL darf keinen abschließenden Schrägstrich „/“ enthalten.</string>
+  <string id="WebhookFailed">Webhook-Registrierung fehlgeschlagen.</string>
+  <string id="WrongPin">Falsche PIN.</string>
+  <string id="WifiLteNotAvailable">Kein WLAN oder LTE verfügbar.</string>
+  <string id="WifiLtePrompt">Über WLAN/LTE ausführen?</string>
+  <string id="WifiLteExecutionTitle">Sende an Home Assistant.</string>
+  <string id="WifiLteExecutionDataError">Keine Daten empfangen.</string>
+  <!-- Für die Einstellungs-Benutzeroberfläche sollten die Texte in der Reihenfolge ihrer Verwendung angeordnet sein. -->
+  <string id="SettingsSelect">Auswählen...</string>
+  <string id="SettingsApiKey">API-Schlüssel für HomeAssistant.</string>
+  <string id="SettingsApiKeyPrompt">Langzeit-Zugangstoken.</string>
+  <string id="SettingsApiUrl">URL der HomeAssistant-API.</string>
+  <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>
+  <string id="SettingsPollDelay">Zusätzliche Abfrageverzögerung (in Sekunden). Fügt zwischen den Status-Updates der Menüeinträge eine Pause ein.</string>
+  <string id="SettingsConfirmTimeout">Nach dieser Zeit (in Sekunden) wird ein Bestätigungsdialog automatisch geschlossen und die Aktion abgebrochen. Mit 0 deaktivieren.</string>
+  <string id="SettingsPin">4-stellige PIN für alle Aktionen, die diese erfordern (0000-9999).</string>
+  <string id="SettingsPinError">Bitte eine gültige 4-stellige numerische PIN in den App Einstellungen eingeben (0000-9999).</string>
+  <string id="SettingsTextAlign">Menüausrichtung: Links (aus) oder Rechts (ein).</string>
+  <string id="SettingsLeftToRight">Von links nach rechts</string>
+  <string id="SettingsRightToLeft">Von rechts nach links</string>
+  <string id="SettingsWidgetStart">(Nur Widget) App automatisch aus dem Widget starten, ohne auf Tippen zu warten.</string>
+  <string id="SettingsEnableBatteryLevel">Hintergrunddienst aktivieren, um Akkustand, Standort und (falls unterstützt) Aktivitätsdaten an Home Assistant zu senden.</string>
+  <string id="SettingsBatteryLevelRefreshRate">Intervall (in Minuten), in dem der Hintergrunddienst die Daten erneut senden soll.</string>
+  <string id="SettingsUserHttpHeader">Zusätzlicher HTTP-Header</string>
+  <string id="SettingsUserHttpHeaderDescription">Einige Home Assistant-Installationen erfordern die Angabe eines benutzerdefinierten HTTP-Headers, um zu funktionieren.</string>
+  <string id="SettingsUserHttpHeaderName">Zusätzlicher HTTP-Header: Name</string>
+  <string id="SettingsUserHttpHeaderValue">Zusätzlicher HTTP-Header: Value</string>
+  <string id="SettingsClearWebhookId">Neu mit Home Assistant verbinden (Webhook-ID löschen, siehe Fehlerbehebungshandbuch).</string>
+  <string id="SettingsWebhookId">(Nur lesen) Die vom Gerät erstellte Webhook-ID für Hintergrund-Updates. Kann zum Debuggen benötigt werden.</string>
 </strings>

resources-dut/strings/strings.xml

@@ -9,31 +9,94 @@
    tested on a Venu 2 device. The source code is provided at:
               https://github.com/house-of-abbey/GarminHomeAssistant.
 
-   P A Abbey & J D Abbey, 31 October 2023
+   P A Abbey & J D Abbey & Someone0nEarth & vincentezw, 31 October 2023
 
 -->
 
 <!--
-  Generated by Google Translate: English to Dutch
-  Gegenereerd door Google Translate uit het Engels
+  Generated by Google Translate and gemini-2.5-flash from English to Dutch
+  Gegenereerd door Google Translate en gemini-2.5-flash van Engels naar Nederlands
 -->
 
 <strings>
-  <string id="AppName">HomeAssistant</string>
-  <string id="MenuItemOn">Op</string>
-  <string id="MenuItemOff">Uit</string>
-  <string id="MenuItemTap">Kraan</string>
-  <string id="MenuItemMenu">Menu</string>
-  <string id="NoPhone">Geen telefoonverbinding</string>
-  <string id="NoInternet">Geen internet verbinding</string>
-  <string id="NoResponse">Geen reactie, controleer de internetverbinding</string>
-  <string id="NoMenu">Fout bij ophalen van menu</string>
-  <string id="NoAPIKey">Geen API-sleutel in de applicatie-instellingen</string>
-  <string id="NoApiUrl">Geen API-URL in de applicatie-instellingen</string>
-  <string id="NoConfigUrl">Geen configuratie-URL in de applicatie-instellingen</string>
   <string id="ApiFlood">API-aanroepen te snel. Vertraag uw verzoeken.</string>
-  <string id="ApiUrlNotFound">URL niet gevonden. Mogelijke API-URL-fout in instellingen.</string>
-  <string id="ConfigUrlNotFound">URL niet gevonden. Mogelijke configuratie-URL-fout in de instellingen.</string>
+  <string id="ApiUrlNotFound">URL niet gevonden. Potentiële API-URL-fout in instellingen.</string>
+  <string id="AppName" scope="glance">HomeAssistant</string>
+  <string id="Available" scope="glance">Beschikbaar</string>
+  <string id="Cached" scope="glance">In cache</string>
+  <string id="Checking" scope="glance">Controleren ...</string>
+  <string id="ConfigUrlNotFound">URL niet gevonden. Potentiële configuratie-URL-fout in
+    instellingen.</string>
+  <string id="Confirm">Zeker?</string>
+  <string id="Empty">Leeg</string>
+  <string id="Executed" scope="glance">Bevestigd</string>
+  <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-sleutel 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>
+  <string id="NoInternet">Geen internetverbinding.</string>
+  <string id="NoJson">Geen JSON ontvangen van het HTTP-verzoek.</string>
+  <string id="NoPhone" scope="glance">Geen telefoonverbinding.</string>
+  <string id="NoPhoneNoCache" scope="glance">Geen telefoonverbinding, geen menu in de cache.</string>
+  <string id="NoResponse">Geen antwoord, controleer internetverbinding</string>
+  <string id="TimedOut">Verzoek is verlopen</string>
+  <string id="PinInputLocked">PIN-invoer vergrendeld voor</string>
+  <string id="PotentialError">Potentiële fout</string>
+  <string id="Seconds">seconden</string>
+  <string id="TemplateError">Sjabloonfout</string>
+  <string id="TrailingSlashErr">API-URL mag geen afsluitende schuine streep '/' hebben.</string>
+  <string id="Unavailable" scope="glance">Niet beschikbaar</string>
+  <string id="Unconfigured" scope="glance">Niet geconfigureerd</string>
   <string id="UnhandledHttpErr">HTTP-verzoek retourneerde foutcode =</string>
-  <string id="TrailingSlashErr">API-URL mag geen afsluitende slash '/' bevatten</string>
+  <string id="WebhookFailed">Kon Webhook niet registreren</string>
+  <string id="WrongPin">Verkeerde PIN</string>
+  <string id="WifiLteNotAvailable">Geen Wi-Fi of LTE beschikbaar</string>
+  <string id="WifiLtePrompt">Uitvoeren via Wi-Fi/LTE?</string>
+  <string id="WifiLteExecutionTitle">Verzenden naar homeassistent.</string>
+  <string id="WifiLteExecutionDataError">Geen gegevens ontvangen.</string>
+  <!-- Voor de instellingen-GUI moeten strings in de volgorde staan waarin ze worden gebruikt. -->
+  <string id="SettingsSelect">Selecteer ...</string>
+  <string id="SettingsApiKey">API-sleutel voor Home Assistant.</string>
+  <string id="SettingsApiKeyPrompt">Langdurige Access Token.</string>
+  <string id="SettingsApiUrl">URL voor Home Assistant API.</string>
+  <string id="SettingsConfigUrl">URL voor menuconfiguratie (JSON).</string>
+  <string id="SettingsCacheConfig">Moet de applicatie de menuconfiguratie cachen?</string>
+  <string id="SettingsClearCache">Moet de applicatie de bestaande cache wissen bij de volgende
+    start?</string>
+  <string id="SettingsEnableMenuUpdateCheck">Controleren op menu-updates bij het starten van de applicatie? Let op: Menu-caching moet zijn ingeschakeld. Deze instelling kan ervoor zorgen dat oudere apparaten met minder geheugen crashen.</string>
+  <string id="SettingsWifiLteExecutionEnable">Schakel het uitvoeren van opdrachten via Wi-Fi/LTE in.</string>
+  <string id="SettingsVibration">Moet de applicatie feedback geven via trillingen?</string>
+  <string id="SettingsAppTimeout">Time-out in seconden. Sluit de applicatie af na deze periode van
+    inactiviteit om de batterij van het apparaat te sparen.</string>
+  <string id="SettingsPollDelay">Extra pollingvertraging (in seconden). Voegt een vertraging toe
+    tussen de statusupdate van alle menu-items.</string>
+  <string id="SettingsConfirmTimeout">Na deze tijd (in seconden) wordt een
+    bevestigingsdialoogvenster voor een actie automatisch gesloten en wordt de actie geannuleerd.
+    Stel in op 0 om de time-out uit te schakelen.</string>
+  <string id="SettingsPin">4-cijferige PIN die moet worden gebruikt voor alle acties die dit
+    vereisen (0000-9999).</string>
+  <string id="SettingsPinError">Configureer een geldige 4-cijferige numerieke PIN tussen 0000 en
+    9999 in de toepassingsinstellingen.</string>
+  <string id="SettingsTextAlign">Links (uit) of rechts (aan) menu-uitlijning.</string>
+  <string id="SettingsLeftToRight">Van links naar rechts</string>
+  <string id="SettingsRightToLeft">Van rechts naar links</string>
+  <string id="SettingsWidgetStart">(Alleen widget) Start de toepassing automatisch vanuit de widget
+    zonder te wachten op een tik.</string>
+  <string id="SettingsEnableBatteryLevel">Schakel de achtergrondservice in om het batterijniveau van
+    het apparaat, de locatie en (indien ondersteund) activiteitsgegevens naar Home Assistant te
+    verzenden.</string>
+  <string id="SettingsBatteryLevelRefreshRate">De verversingssnelheid (in minuten) waarbij de
+    achtergrondservice het verzenden van gegevens moet herhalen.</string>
+  <string id="SettingsUserHttpHeader">Door gebruiker opgegeven HTTP-header</string>
+  <string id="SettingsUserHttpHeaderDescription">Sommige Home Assistant-installaties vereisen de
+    specificatie van een aangepaste HTTP-header om te functioneren.</string>
+  <string id="SettingsUserHttpHeaderName">Door gebruiker opgegeven HTTP-header: Naam</string>
+  <string id="SettingsUserHttpHeaderValue">Door gebruiker opgegeven HTTP-header: Waarde</string>
+  <string id="SettingsClearWebhookId">Opnieuw verbinden met Home Assistant (Webhook-ID wissen, zie
+    Gids voor probleemoplossing).</string>
+  <string id="SettingsWebhookId">(Alleen lezen) De Webhook-ID die door het apparaat is gemaakt voor
+    updates van de achtergrondservice. Mogelijk heeft u dit nodig voor foutopsporing.</string>
 </strings>

resources-est/strings/strings.xml

@@ -9,31 +9,91 @@
    tested on a Venu 2 device. The source code is provided at:
               https://github.com/house-of-abbey/GarminHomeAssistant.
 
-   P A Abbey & J D Abbey, 31 October 2023
+   P A Abbey & J D Abbey & Someone0nEarth & vincentezw, 31 October 2023
 
 -->
 
 <!--
-  Generated by Google Translate: English to Estonian
-  Loodud Google'i tõlke abil inglise keelest
+  Generated by Google Translate and gemini-2.5-flash from English to Estonian
+  Genereeritud Google Translate'i ja gemini-2.5-flashi poolt inglise keelest eesti keelde
 -->
 
 <strings>
-  <string id="AppName">HomeAssistant</string>
-  <string id="MenuItemOn">Peal</string>
-  <string id="MenuItemOff">Väljas</string>
-  <string id="MenuItemTap">Puudutage</string>
-  <string id="MenuItemMenu">Menüü</string>
-  <string id="NoPhone">Telefoniühendus puudub</string>
-  <string id="NoInternet">Interneti-ühendus puudub</string>
-  <string id="NoResponse">Ei reageeri, kontrollige Interneti-ühendust</string>
-  <string id="NoMenu">Menüü toomise viga</string>
-  <string id="NoAPIKey">Rakenduse seadetes pole API-võtit</string>
-  <string id="NoApiUrl">Rakenduse seadetes pole API URL-i</string>
-  <string id="NoConfigUrl">Rakenduse seadetes pole konfiguratsiooni URL-i</string>
-  <string id="ApiFlood">API-kõned liiga kiired. Palun aeglustage oma taotlusi.</string>
+  <string id="ApiFlood">API kõned on liiga kiired. Palun aeglustage oma päringuid.</string>
   <string id="ApiUrlNotFound">URL-i ei leitud. Võimalik API URL-i viga seadetes.</string>
+  <string id="AppName" scope="glance">HomeAssistant</string>
+  <string id="Available" scope="glance">Saadav</string>
+  <string id="Cached" scope="glance">Vahemällu salvestatud</string>
+  <string id="Checking" scope="glance">Kontrollin...</string>
   <string id="ConfigUrlNotFound">URL-i ei leitud. Võimalik konfiguratsiooni URL-i viga seadetes.</string>
-  <string id="UnhandledHttpErr">HTTP päring tagastas veakoodi =</string>
-  <string id="TrailingSlashErr">API URL-i lõpus ei tohi olla kaldkriipsu „/”</string>
+  <string id="Confirm">Kindel?</string>
+  <string id="Empty">Tühi</string>
+  <string id="Executed" scope="glance">Kinnitatud</string>
+  <string id="GlanceMenu" scope="glance">Menüü</string>
+  <string id="Memory" scope="glance">Mälu</string>
+  <string id="MenuUpdated">Menüü värskendatud, taaskäivita.</string>
+  <string id="MenuCheckDisabled">Menüü värskendused keelatud.</string>
+  <string id="NoAPIKey" scope="glance">Rakenduse seadetes pole API võtit.</string>
+  <string id="NoApiUrl" scope="glance">Rakenduse seadetes pole API URL-i.</string>
+  <string id="NoConfigUrl" scope="glance">Rakenduse seadetes pole konfiguratsiooni URL-i.</string>
+  <string id="NoInternet">Interneti-ühendust pole.</string>
+  <string id="NoJson">HTTP päring ei tagastanud JSON-i.</string>
+  <string id="NoPhone" scope="glance">Telefoniühendust pole.</string>
+  <string id="NoPhoneNoCache" scope="glance">Pole telefoniühendust ega vahemällu salvestatud menüüd.</string>
+  <string id="NoResponse">Vastust pole, kontrollige Interneti-ühendust</string>
+  <string id="TimedOut">Päring aegus</string>
+  <string id="PinInputLocked">PIN-koodi sisestus lukustatud</string>
+  <string id="PotentialError">Potentsiaalne viga</string>
+  <string id="Seconds">sekundid</string>
+  <string id="TemplateError">Malli viga</string>
+  <string id="TrailingSlashErr">API URL-il ei tohi olla lõpus kaldkriipsu '/'.</string>
+  <string id="Unavailable" scope="glance">Kättesaamatu</string>
+  <string id="Unconfigured" scope="glance">Konfigureerimata</string>
+  <string id="UnhandledHttpErr">HTTP päring tagastas veakoodi = </string>
+  <string id="WebhookFailed">Webhooki registreerimine ebaõnnestus</string>
+  <string id="WrongPin">Vale PIN-kood</string>
+  <string id="WifiLteNotAvailable">Wi-Fi ega LTE pole saadaval</string>
+  <string id="WifiLtePrompt">Täita üle Wi-Fi/LTE?</string>
+  <string id="WifiLteExecutionTitle">Saadan Home Assistantile.</string>
+  <string id="WifiLteExecutionDataError">Andmeid pole laekunud.</string>
+  <!-- Seadete GUI jaoks peaksid stringid olema kasutamise järjekorras. -->
+  <string id="SettingsSelect">Valige...</string>
+  <string id="SettingsApiKey">API võti Home Assistantile.</string>
+  <string id="SettingsApiKeyPrompt">Pikaajaline juurdepääsuluba.</string>
+  <string id="SettingsApiUrl">URL Home Assistanti API jaoks.</string>
+  <string id="SettingsConfigUrl">URL menüü konfiguratsiooni jaoks (JSON).</string>
+  <string id="SettingsCacheConfig">Kas rakendus peaks menüü konfiguratsiooni vahemällu salvestama?</string>
+  <string id="SettingsClearCache">Kas rakendus peaks järgmisel käivitamisel olemasoleva vahemälu
+    tühjendama?</string>
+  <string id="SettingsEnableMenuUpdateCheck">Kontrolli menüü värskendusi rakenduse käivitamisel? Märkus: Menüü vahemällu salvestamine peab olema lubatud. See säte võib põhjustada vanemate, vähem mälu omavate seadmete kokkujooksmise.</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 sekundites. Väljuge rakendusest pärast seda tegevusetuse
+    perioodi, et säästa seadme akut.</string>
+  <string id="SettingsPollDelay">Täiendav päringuviivitus (sekundites). Lisab viivituse kõigi
+    menüüelementide olekuvärskenduste vahele.</string>
+  <string id="SettingsConfirmTimeout">Pärast seda aega (sekundites) suletakse toimingu
+    kinnitusdialoog automaatselt ja toiming tühistatakse. Määra 0, et aegumine keelata.</string>
+  <string id="SettingsPin">4-kohaline PIN-kood, mida kasutatakse kõigi seda nõudvate toimingute
+    jaoks (0000-9999).</string>
+  <string id="SettingsPinError">Palun konfigureerige rakenduse seadetes kehtiv 4-kohaline numbriline
+    PIN-kood vahemikus 0000 kuni 9999.</string>
+  <string id="SettingsTextAlign">Vasak (väljas) või parem (sees) menüü joondus.</string>
+  <string id="SettingsLeftToRight">Vasakult paremale</string>
+  <string id="SettingsRightToLeft">Paremale vasakule</string>
+  <string id="SettingsWidgetStart">(Ainult vidin) Käivitage rakendus vidinast automaatselt, ilma
+    puudutust ootamata.</string>
+  <string id="SettingsEnableBatteryLevel">Luba taustateenusel saata seadme aku tase, asukoht ja (kui
+    toetatud) tegevusandmed Home Assistantile.</string>
+  <string id="SettingsBatteryLevelRefreshRate">Värskendussagedus (minutites), millega taustateenus
+    peaks andmete saatmist kordama.</string>
+  <string id="SettingsUserHttpHeader">Kasutaja määratud HTTP päis</string>
+  <string id="SettingsUserHttpHeaderDescription">Mõned Home Assistanti installatsioonid vajavad
+    toimimiseks kohandatud HTTP päise määramist.</string>
+  <string id="SettingsUserHttpHeaderName">Kasutaja määratud HTTP päis: Nimi</string>
+  <string id="SettingsUserHttpHeaderValue">Kasutaja määratud HTTP päis: Väärtus</string>
+  <string id="SettingsClearWebhookId">Ühenda uuesti Home Assistantiga (tühjenda Webhooki ID, vt
+    tõrkeotsingu juhendit).</string>
+  <string id="SettingsWebhookId">(Ainult lugemiseks) Seadme loodud Webhooki ID taustateenuse
+    värskenduste jaoks. Võite seda silumiseks vajada.</string>
 </strings>

resources-fin/strings/strings.xml

@@ -9,31 +9,94 @@
    tested on a Venu 2 device. The source code is provided at:
               https://github.com/house-of-abbey/GarminHomeAssistant.
 
-   P A Abbey & J D Abbey, 31 October 2023
+   P A Abbey & J D Abbey & Someone0nEarth & vincentezw, 31 October 2023
 
 -->
 
 <!--
-  Generated by Google Translate: English to Finnish
-  Luonut Google Translate englannista
+  Generated by Google Translate and gemini-2.5-flash from English to Finnish
+  Generoinut Google Translate ja gemini-2.5-flash englannista suomeksi
 -->
 
 <strings>
-  <string id="AppName">HomeAssistant</string>
-  <string id="MenuItemOn">Päällä</string>
-  <string id="MenuItemOff">Vinossa</string>
-  <string id="MenuItemTap">Napauta</string>
-  <string id="MenuItemMenu">Valikko</string>
-  <string id="NoPhone">Ei puhelinyhteyttä</string>
-  <string id="NoInternet">Ei Internet-yhteyttä</string>
+  <string id="ApiFlood">API-kutsut liian tiheitä. Hidasta pyyntöjäsi.</string>
+  <string id="ApiUrlNotFound">URL-osoitetta ei löydy. Mahdollinen API-URL-virhe asetuksissa.</string>
+  <string id="AppName" scope="glance">HomeAssistant</string>
+  <string id="Available" scope="glance">Käytettävissä</string>
+  <string id="Cached" scope="glance">Välimuistissa</string>
+  <string id="Checking" scope="glance">Tarkistetaan...</string>
+  <string id="ConfigUrlNotFound">URL-osoitetta ei löydy. Mahdollinen määritys-URL-virhe asetuksissa.</string>
+  <string id="Confirm">Varma?</string>
+  <string id="Empty">Tyhjä</string>
+  <string id="Executed" scope="glance">Vahvistettu</string>
+  <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 API-avainta sovellusasetuksissa.</string>
+  <string id="NoApiUrl" scope="glance">Ei API-URL-osoitetta sovellusasetuksissa.</string>
+  <string id="NoConfigUrl" scope="glance">Ei määritys-URL-osoitetta sovellusasetuksissa.</string>
+  <string id="NoInternet">Ei Internet-yhteyttä.</string>
+  <string id="NoJson">HTTP-pyynnöstä ei palautettu JSONia.</string>
+  <string id="NoPhone" scope="glance">Ei puhelinyhteyttä.</string>
+  <string id="NoPhoneNoCache" scope="glance">Ei puhelinyhteyttä, ei välimuistissa olevaa valikkoa.</string>
   <string id="NoResponse">Ei vastausta, tarkista Internet-yhteys</string>
-  <string id="NoMenu">Valikkohakuvirhe</string>
-  <string id="NoAPIKey">Sovellusasetuksissa ei ole API-avainta</string>
-  <string id="NoApiUrl">Sovellusasetuksissa ei ole API URL-osoitetta</string>
-  <string id="NoConfigUrl">Sovelluksen asetuksissa ei ole konfigurointi-URL-osoitetta</string>
-  <string id="ApiFlood">API-kutsut liian nopeita. Hidasta pyyntöjäsi.</string>
-  <string id="ApiUrlNotFound">URL-osoitetta ei löydy. Mahdollinen API URL -virhe asetuksissa.</string>
-  <string id="ConfigUrlNotFound">URL-osoitetta ei löydy. Mahdollinen konfigurointi-URL-virhe asetuksissa.</string>
+  <string id="TimedOut">Pyyntö aikakatkaistu</string>
+  <string id="PinInputLocked">PIN-syöttö lukittu ajaksi</string>
+  <string id="PotentialError">Mahdollinen virhe</string>
+  <string id="Seconds">sekuntia</string>
+  <string id="TemplateError">Mallivirhe</string>
+  <string id="TrailingSlashErr">API-URL-osoitteessa ei saa olla loppukauttaviivaa '/'.</string>
+  <string id="Unavailable" scope="glance">Ei käytettävissä</string>
+  <string id="Unconfigured" scope="glance">Määrittelemätön</string>
   <string id="UnhandledHttpErr">HTTP-pyyntö palautti virhekoodin =</string>
-  <string id="TrailingSlashErr">API-URL-osoitteessa ei saa olla perässä olevaa kauttaviivaa '/'</string>
+  <string id="WebhookFailed">Webhookin rekisteröinti epäonnistui</string>
+  <string id="WrongPin">Väärä PIN-koodi</string>
+  <string id="WifiLteNotAvailable">Ei Wi-Fiä tai LTE:tä käytettävissä.</string>
+  <string id="WifiLtePrompt">Suoritetaanko Wi-Fi/LTE-yhteyden kautta?</string>
+  <string id="WifiLteExecutionTitle">Lähetetään Home Assistantille.</string>
+  <string id="WifiLteExecutionDataError">Tietoja ei vastaanotettu.</string>
+  <!-- Asetusten käyttöliittymän osalta merkkijonojen tulisi olla siinä järjestyksessä, jossa niitä
+  käytetään. -->
+  <string id="SettingsSelect">Valitse...</string>
+  <string id="SettingsApiKey">API-avain HomeAssistantille.</string>
+  <string id="SettingsApiKeyPrompt">Pitkäikäinen käyttöoikeustunnus.</string>
+  <string id="SettingsApiUrl">URL-osoite HomeAssistantin API:lle.</string>
+  <string id="SettingsConfigUrl">Valikon määrityksen URL-osoite (JSON).</string>
+  <string id="SettingsCacheConfig">Pitäisikö sovelluksen tallentaa valikon kokoonpano välimuistiin?</string>
+  <string id="SettingsClearCache">Pitäisikö sovelluksen tyhjentää olemassa oleva välimuisti
+    seuraavalla käynnistyksellä?</string>
+  <string id="SettingsEnableMenuUpdateCheck">Tarkistetaanko valikkopäivitykset sovelluksen käynnistyksen yhteydessä? Huomaa: Valikon välimuistiin tallennus on oltava käytössä. Tämä asetus voi aiheuttaa vanhempien, vähemmän muistia omaavien laitteiden kaatumisen.</string>
+  <string id="SettingsWifiLteExecutionEnable">Ota komentojen suorittaminen käyttöön
+    Wi-Fi/LTE-yhteyden 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 säästääksesi laitteen akkua.</string>
+  <string id="SettingsPollDelay">Lisäkyselyviive (sekunneissa). Lisää viive kaikkien
+    valikkokohteiden tilapäivityksen välillä.</string>
+  <string id="SettingsConfirmTimeout">Tämän ajan jälkeen (sekunneissa) toiminnan
+    vahvistusvalintaikkuna suljetaan automaattisesti ja toiminto peruutetaan. Aseta arvoon 0
+    poistamaan aikakatkaisu käytöstä.</string>
+  <string id="SettingsPin">4-numeroinen PIN-koodi, jota käytetään kaikkiin sitä vaativiin toimiin
+    (0000-9999).</string>
+  <string id="SettingsPinError">Määritä kelvollinen 4-numeroinen numeerinen PIN-koodi välillä
+    0000-9999 sovellusasetuksissa.</string>
+  <string id="SettingsTextAlign">Vasen (pois päältä) tai oikea (on) valikon kohdistus.</string>
+  <string id="SettingsLeftToRight">Vasemmalta oikealle</string>
+  <string id="SettingsRightToLeft">Oikealta vasemmalle</string>
+  <string id="SettingsWidgetStart">(Vain widget) Käynnistä sovellus automaattisesti widgetistä
+    odottamatta napautusta.</string>
+  <string id="SettingsEnableBatteryLevel">Ota taustapalvelu käyttöön laitteen akkutason, sijainnin
+    ja (jos tuettu) aktiivisuustietojen lähettämiseksi Home Assistantille.</string>
+  <string id="SettingsBatteryLevelRefreshRate">Päivitysnopeus (minuuteissa), jolla taustapalvelun
+    tulisi toistaa tietojen lähettäminen.</string>
+  <string id="SettingsUserHttpHeader">Käyttäjän määrittämä HTTP-otsake</string>
+  <string id="SettingsUserHttpHeaderDescription">Jotkut Home Assistant -asennukset vaativat
+    mukautetun HTTP-otsakkeen määrittelyn toimiakseen.</string>
+  <string id="SettingsUserHttpHeaderName">Käyttäjän määrittämä HTTP-otsake: Nimi</string>
+  <string id="SettingsUserHttpHeaderValue">Käyttäjän määrittämä HTTP-otsake: Arvo</string>
+  <string id="SettingsClearWebhookId">Yhdistä uudelleen Home Assistantiin (tyhjennä Webhook ID,
+    katso vianetsintäopas).</string>
+  <string id="SettingsWebhookId">(Vain luku) Laitteen luoma Webhook ID taustapalvelun päivityksiä
+    varten. Saatat tarvita tätä virheenkorjaukseen.</string>
 </strings>

resources-fre/strings/corrections.xml

@@ -9,7 +9,7 @@
    tested on a Venu 2 device. The source code is provided at:
               https://github.com/house-of-abbey/GarminHomeAssistant.
 
-   P A Abbey & J D Abbey, 14 November 2023
+   P A Abbey & J D Abbey & Someone0nEarth, 14 November 2023
 
 -->
 
@@ -19,7 +19,5 @@
 -->
 
 <strings>
-  <string id="MenuItemOn">Activé</string>
-  <string id="MenuItemTap">Clic</string>
   <string id="ApiFlood">Appels API trop rapide. Veuillez signaler cette erreur avec les détails de l'appareil.</string>
 </strings>

resources-fre/strings/strings.xml

@@ -9,31 +9,98 @@
    tested on a Venu 2 device. The source code is provided at:
               https://github.com/house-of-abbey/GarminHomeAssistant.
 
-   P A Abbey & J D Abbey, 31 October 2023
+   P A Abbey & J D Abbey & Someone0nEarth & vincentezw, 31 October 2023
 
 -->
 
 <!--
-  Generated by Google Translate: English to French
-  Généré par Google Translate de l'anglais
+  Generated by Google Translate and gemini-2.5-flash from English to French
+  Généré par Google Translate et gemini-2.5-flash de l'anglais au français
 -->
 
 <strings>
-  <string id="AppName">HomeAssistant</string>
-  <string id="MenuItemOn">Activé</string>
-  <string id="MenuItemOff">Désactivé</string>
-  <string id="MenuItemTap">Clic</string>
-  <string id="MenuItemMenu">Menu</string>
-  <string id="NoPhone">Pas de connexion téléphonique</string>
-  <string id="NoInternet">Pas de connexion Internet</string>
-  <string id="NoResponse">Pas de réponse, vérifiez la connexion Internet</string>
-  <string id="NoMenu">Erreur de récupération du menu</string>
-  <string id="NoAPIKey">Pas de clé API dans les paramètres de l'application</string>
-  <string id="NoApiUrl">Aucune URL API dans les paramètres de l'application</string>
-  <string id="NoConfigUrl">Aucune URL de configuration dans les paramètres de l'application</string>
   <string id="ApiFlood">Appels API trop rapide. Veuillez signaler cette erreur avec les détails de l'appareil.</string>
-  <string id="ApiUrlNotFound">URL introuvable. Erreur potentielle d'URL d'API dans les paramètres.</string>
-  <string id="ConfigUrlNotFound">URL introuvable. Erreur potentielle d'URL de configuration dans les paramètres.</string>
-  <string id="UnhandledHttpErr">La requête HTTP a renvoyé un code d'erreur =</string>
-  <string id="TrailingSlashErr">L'URL de l'API ne doit pas comporter de barre oblique finale '/'</string>
+  <string id="ApiUrlNotFound">URL introuvable. L'URL de l'API est potentiellement erronée dans les
+    paramètres.</string>
+  <string id="AppName" scope="glance">HomeAssistant</string>
+  <string id="Available" scope="glance">Disponible</string>
+  <string id="Cached" scope="glance">Mis en cache</string>
+  <string id="Checking" scope="glance">Vérification...</string>
+  <string id="ConfigUrlNotFound">URL introuvable. L'URL de configuration est potentiellement erronée
+    dans les paramètres.</string>
+  <string id="Confirm">Confirmer ?</string>
+  <string id="Empty">Vide</string>
+  <string id="Executed" scope="glance">Exécuté</string>
+  <string id="GlanceMenu" scope="glance">Menu</string>
+  <string id="Memory" scope="glance">Mémoire</string>
+  <string id="MenuUpdated">Menu mis à jour, redémarrez.</string>
+  <string id="MenuCheckDisabled">Mises à jour du menu désactivées.</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>
+  <string id="NoInternet">Pas de connexion Internet.</string>
+  <string id="NoJson">Aucun JSON n'est retourné par la requête HTTP.</string>
+  <string id="NoPhone" scope="glance">Aucune connexion téléphonique.</string>
+  <string id="NoPhoneNoCache" scope="glance">Pas de connexion téléphonique, pas de menu en cache.</string>
+  <string id="NoResponse">Aucune réponse, vérifiez la connexion Internet</string>
+  <string id="TimedOut">Délai d'attente dépassé</string>
+  <string id="PinInputLocked">Saisie du code PIN verrouillée pour</string>
+  <string id="PotentialError">Erreur potentielle</string>
+  <string id="Seconds">secondes</string>
+  <string id="TemplateError">Erreur de modèle</string>
+  <string id="TrailingSlashErr">L'URL de l'API ne doit pas se terminer par une barre oblique '/'.</string>
+  <string id="Unavailable" scope="glance">Indisponible</string>
+  <string id="Unconfigured" scope="glance">Non configuré</string>
+  <string id="UnhandledHttpErr">La requête HTTP a renvoyé le code d'erreur =</string>
+  <string id="WebhookFailed">Échec de l'enregistrement du Webhook</string>
+  <string id="WrongPin">Code PIN incorrect</string>
+  <string id="WifiLteNotAvailable">Pas de Wi-Fi ou de LTE disponible</string>
+  <string id="WifiLtePrompt">Exécuter sur Wi-Fi / LTE ?</string>
+  <string id="WifiLteExecutionTitle">Envoi à Home Assistant.</string>
+  <string id="WifiLteExecutionDataError">Aucune donnée reçue.</string>
+  <!-- Pour l'interface graphique des paramètres, les chaînes doivent être dans l'ordre où elles
+  sont utilisées. -->
+  <string id="SettingsSelect">Sélectionner...</string>
+  <string id="SettingsApiKey">Clé API pour HomeAssistant.</string>
+  <string id="SettingsApiKeyPrompt">Jeton d'accès de longue durée.</string>
+  <string id="SettingsApiUrl">URL pour l'API HomeAssistant.</string>
+  <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'elle sera démarrée ?</string>
+  <string id="SettingsEnableMenuUpdateCheck">Vérifier les mises à jour du menu au démarrage de l'application ? Remarque : la mise en cache du menu doit être activée. Ce paramètre peut entraîner le plantage 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 un retour par vibrations ?</string>
+  <string id="SettingsAppTimeout">Délai d'expiration en secondes. L'application se fermera après
+    cette période d'inactivité pour économiser la batterie de l'appareil.</string>
+  <string id="SettingsPollDelay">Délai d'interrogation supplémentaire (en secondes). Ajoute un délai
+    entre la mise à jour de l'état de tous les éléments de menu.</string>
+  <string id="SettingsConfirmTimeout">Après ce délai (en secondes), une boîte de dialogue de
+    confirmation pour une action est automatiquement fermée et l'action est annulée. Définir à 0
+    pour désactiver le délai d'attente.</string>
+  <string id="SettingsPin">Code PIN à 4 chiffres à utiliser pour toutes les actions qui l'exigent
+    (0000-9999).</string>
+  <string id="SettingsPinError">Veuillez configurer un code PIN numérique à 4 chiffres valide entre
+    0000 et 9999 dans les paramètres de l'application.</string>
+  <string id="SettingsTextAlign">Alignement du menu : Gauche (désactivé) ou Droit (activé).</string>
+  <string id="SettingsLeftToRight">De gauche à droite</string>
+  <string id="SettingsRightToLeft">De droite à gauche</string>
+  <string id="SettingsWidgetStart">(Widget uniquement) Démarre automatiquement l'application depuis
+    le widget sans attendre une pression.</string>
+  <string id="SettingsEnableBatteryLevel">Activer le service d'arrière-plan pour envoyer le niveau
+    de la batterie de l'appareil, l'emplacement et (le cas échéant) les données d'activité à Home
+    Assistant.</string>
+  <string id="SettingsBatteryLevelRefreshRate">Le taux de rafraîchissement (en minutes) auquel le
+    service d'arrière-plan doit répéter l'envoi de données.</string>
+  <string id="SettingsUserHttpHeader">En-tête HTTP fourni par l'utilisateur</string>
+  <string id="SettingsUserHttpHeaderDescription">Certaines installations Home Assistant nécessitent
+    la spécification d'un en-tête HTTP personnalisé pour fonctionner.</string>
+  <string id="SettingsUserHttpHeaderName">En-tête HTTP fourni par l'utilisateur : Nom</string>
+  <string id="SettingsUserHttpHeaderValue">En-tête HTTP fourni par l'utilisateur : Valeur</string>
+  <string id="SettingsClearWebhookId">Se reconnecter à Home Assistant (effacer l'ID du Webhook, voir
+    le guide de dépannage).</string>
+  <string id="SettingsWebhookId">(Lecture seule) L'ID Webhook créé par l'appareil pour les mises à
+    jour du service d'arrière-plan. Vous pourriez en avoir besoin pour le débogage.</string>
 </strings>

resources-gre/strings/strings.xml

@@ -9,31 +9,96 @@
    tested on a Venu 2 device. The source code is provided at:
               https://github.com/house-of-abbey/GarminHomeAssistant.
 
-   P A Abbey & J D Abbey, 31 October 2023
+   P A Abbey & J D Abbey & Someone0nEarth & vincentezw, 31 October 2023
 
 -->
 
 <!--
-  Generated by Google Translate: English to Greek
-  Δημιουργήθηκε από τη Μετάφραση Google από τα Αγγλικά
+  Generated by Google Translate and gemini-2.5-flash from English to Greek
+  Δημιουργήθηκε από το Google Translate και το gemini-2.5-flash από Αγγλικά σε Ελληνικά
 -->
 
 <strings>
-  <string id="AppName">HomeAssistant</string>
-  <string id="MenuItemOn">Επί</string>
-  <string id="MenuItemOff">Μακριά από</string>
-  <string id="MenuItemTap">Παρακέντηση</string>
-  <string id="MenuItemMenu">Μενού</string>
-  <string id="NoPhone">Δεν υπάρχει σύνδεση τηλεφώνου</string>
-  <string id="NoInternet">Δεν υπάρχει σύνδεση στο διαδίκτυο</string>
-  <string id="NoResponse">Καμία απάντηση, ελέγξτε τη σύνδεση στο Διαδίκτυο</string>
-  <string id="NoMenu">Σφάλμα ανάκτησης μενού</string>
-  <string id="NoAPIKey">Δεν υπάρχει κλειδί API στις ρυθμίσεις της εφαρμογής</string>
-  <string id="NoApiUrl">Δεν υπάρχει διεύθυνση URL API στις ρυθμίσεις της εφαρμογής</string>
-  <string id="NoConfigUrl">Δεν υπάρχει διεύθυνση URL διαμόρφωσης στις ρυθμίσεις της εφαρμογής</string>
-  <string id="ApiFlood">Κλήσεις API πολύ γρήγορες. Παρακαλώ επιβραδύνετε τα αιτήματά σας.</string>
-  <string id="ApiUrlNotFound">Η διεύθυνση URL δεν βρέθηκε. Πιθανό σφάλμα διεύθυνσης URL API στις ρυθμίσεις.</string>
-  <string id="ConfigUrlNotFound">Η διεύθυνση URL δεν βρέθηκε. Πιθανό σφάλμα διεύθυνσης URL διαμόρφωσης στις ρυθμίσεις.</string>
-  <string id="UnhandledHttpErr">Το αίτημα HTTP επέστρεψε κωδικό σφάλματος =</string>
-  <string id="TrailingSlashErr">Η διεύθυνση URL του API δεν πρέπει να έχει τελική κάθετο "/"</string>
+  <string id="ApiFlood">Οι κλήσεις API είναι πολύ συχνές. Παρακαλούμε επιβραδύνετε τα αιτήματά σας.</string>
+  <string id="ApiUrlNotFound">Η διεύθυνση URL δεν βρέθηκε. Πιθανό σφάλμα URL API στις ρυθμίσεις.</string>
+  <string id="AppName" scope="glance">HomeAssistant</string>
+  <string id="Available" scope="glance">Διαθέσιμο</string>
+  <string id="Cached" scope="glance">Αποθηκευμένο</string>
+  <string id="Checking" scope="glance">Έλεγχος...</string>
+  <string id="ConfigUrlNotFound">Η διεύθυνση URL δεν βρέθηκε. Πιθανό σφάλμα URL διαμόρφωσης στις
+    ρυθμίσεις.</string>
+  <string id="Confirm">Σίγουρα;</string>
+  <string id="Empty">Κενό</string>
+  <string id="Executed" scope="glance">Επιβεβαιωμένο</string>
+  <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>
+  <string id="NoInternet">Χωρίς σύνδεση στο Διαδίκτυο.</string>
+  <string id="NoJson">Κανένα JSON δεν επεστράφη από το αίτημα HTTP.</string>
+  <string id="NoPhone" scope="glance">Χωρίς σύνδεση τηλεφώνου.</string>
+  <string id="NoPhoneNoCache" scope="glance">Δεν υπάρχει σύνδεση τηλεφώνου, δεν υπάρχει αποθηκευμένο
+    μενού.</string>
+  <string id="NoResponse">Χωρίς απάντηση, ελέγξτε τη σύνδεση στο Διαδίκτυο</string>
+  <string id="TimedOut">Το αίτημα έληξε</string>
+  <string id="PinInputLocked">Είσοδος PIN κλειδωμένη για</string>
+  <string id="PotentialError">Πιθανό σφάλμα</string>
+  <string id="Seconds">δευτερόλεπτα</string>
+  <string id="TemplateError">Σφάλμα προτύπου</string>
+  <string id="TrailingSlashErr">Η διεύθυνση URL του API δεν πρέπει να έχει τελική κάθετο '/'.</string>
+  <string id="Unavailable" scope="glance">Μη διαθέσιμο</string>
+  <string id="Unconfigured" scope="glance">Μη διαμορφωμένο</string>
+  <string id="UnhandledHttpErr">Η αίτηση HTTP επέστρεψε κωδικό σφάλματος =</string>
+  <string id="WebhookFailed">Αποτυχία εγγραφής webhook</string>
+  <string id="WrongPin">Λάθος PIN</string>
+  <string id="WifiLteNotAvailable">Χωρίς Wi-Fi ή LTE διαθέσιμο</string>
+  <string id="WifiLtePrompt">Εκτέλεση μέσω Wi-Fi/LTE;</string>
+  <string id="WifiLteExecutionTitle">Αποστολή στο Home Assistant.</string>
+  <string id="WifiLteExecutionDataError">Δεν λαμβάνονται δεδομένα.</string>
+  <!-- Για το GUI ρυθμίσεων, οι συμβολοσειρές πρέπει να είναι με τη σειρά που χρησιμοποιούνται. -->
+  <string id="SettingsSelect">Επιλογή...</string>
+  <string id="SettingsApiKey">Κλειδί API για το Home Assistant.</string>
+  <string id="SettingsApiKeyPrompt">Διακριτικό πρόσβασης μακράς διάρκειας.</string>
+  <string id="SettingsApiUrl">URL για το API του Home Assistant.</string>
+  <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>
+  <string id="SettingsPollDelay">Πρόσθετη καθυστέρηση ανανέωσης (σε δευτερόλεπτα). Προσθέτει μια
+    καθυστέρηση μεταξύ της ενημέρωσης κατάστασης όλων των στοιχείων μενού.</string>
+  <string id="SettingsConfirmTimeout">Μετά από αυτό το χρονικό διάστημα (σε δευτερόλεπτα), ένα
+    παράθυρο διαλόγου επιβεβαίωσης για μια ενέργεια κλείνει αυτόματα και η ενέργεια ακυρώνεται.
+    Ρυθμίστε στο 0 για να απενεργοποιήσετε το χρονικό όριο.</string>
+  <string id="SettingsPin">4-ψήφιο PIN που χρησιμοποιείται για όλες τις ενέργειες που το απαιτούν
+    (0000-9999).</string>
+  <string id="SettingsPinError">Παρακαλούμε διαμορφώστε ένα έγκυρο 4-ψήφιο αριθμητικό PIN μεταξύ
+    0000 και 9999 στις ρυθμίσεις της εφαρμογής.</string>
+  <string id="SettingsTextAlign">Ευθυγράμμιση μενού: Αριστερά (απενεργοποιημένο) ή Δεξιά (ενεργό).</string>
+  <string id="SettingsLeftToRight">Από αριστερά προς τα δεξιά</string>
+  <string id="SettingsRightToLeft">Δεξιά προς τα αριστερά</string>
+  <string id="SettingsWidgetStart">(Μόνο widget) Αυτόματη εκκίνηση της εφαρμογής από το widget χωρίς
+    να περιμένετε άγγιγμα.</string>
+  <string id="SettingsEnableBatteryLevel">Ενεργοποιήστε την υπηρεσία παρασκηνίου για την αποστολή
+    της στάθμης μπαταρίας της συσκευής, της τοποθεσίας και (αν υποστηρίζονται) δεδομένων
+    δραστηριότητας στο Home Assistant.</string>
+  <string id="SettingsBatteryLevelRefreshRate">Ο ρυθμός ανανέωσης (σε λεπτά) με τον οποίο η υπηρεσία
+    παρασκηνίου θα πρέπει να επαναλαμβάνει την αποστολή δεδομένων.</string>
+  <string id="SettingsUserHttpHeader">Κεφαλίδα HTTP που παρέχεται από τον χρήστη</string>
+  <string id="SettingsUserHttpHeaderDescription">Ορισμένες εγκαταστάσεις Home Assistant απαιτούν την
+    προδιαγραφή μιας προσαρμοσμένης κεφαλίδας HTTP για να λειτουργήσουν.</string>
+  <string id="SettingsUserHttpHeaderName">Κεφαλίδα HTTP που παρέχεται από τον χρήστη: Όνομα</string>
+  <string id="SettingsUserHttpHeaderValue">Κεφαλίδα HTTP που παρέχεται από τον χρήστη: Τιμή</string>
+  <string id="SettingsClearWebhookId">Επανασύνδεση στο Home Assistant (εκκαθάριση Webhook ID, δείτε
+    τον οδηγό αντιμετώπισης προβλημάτων).</string>
+  <string id="SettingsWebhookId">(Μόνο για ανάγνωση) Το Webhook ID που δημιουργήθηκε από τη συσκευή
+    για ενημερώσεις υπηρεσιών παρασκηνίου. Μπορεί να το χρειαστείτε για εντοπισμό σφαλμάτων.</string>
 </strings>

resources-heb/strings/strings.xml

@@ -9,31 +9,88 @@
    tested on a Venu 2 device. The source code is provided at:
               https://github.com/house-of-abbey/GarminHomeAssistant.
 
-   P A Abbey & J D Abbey, 31 October 2023
+   P A Abbey & J D Abbey & Someone0nEarth & vincentezw, 31 October 2023
 
 -->
 
 <!--
-  Generated by Google Translate: English to Hebrew
-  נוצר על ידי Google Translate מאנגלית
+  Generated by Google Translate and gemini-2.5-flash from English to Hebrew
+  נוצר על ידי Google Translate ו-gemini-2.5-flash מאנגלית לעברית
 -->
 
 <strings>
-  <string id="AppName">HomeAssistant</string>
-  <string id="MenuItemOn">עַל</string>
-  <string id="MenuItemOff">כבוי</string>
-  <string id="MenuItemTap">בֶּרֶז</string>
-  <string id="MenuItemMenu">תַפרִיט</string>
-  <string id="NoPhone">אין חיבור לטלפון</string>
-  <string id="NoInternet">אין חיבור אינטרנט</string>
-  <string id="NoResponse">אין תגובה, בדוק חיבור לאינטרנט</string>
-  <string id="NoMenu">שגיאת אחזור תפריט</string>
-  <string id="NoAPIKey">אין מפתח API בהגדרות האפליקציה</string>
-  <string id="NoApiUrl">אין כתובת API בהגדרות האפליקציה</string>
-  <string id="NoConfigUrl">אין כתובת אתר תצורה בהגדרות האפליקציה</string>
-  <string id="ApiFlood">קריאות API מהירות מדי. נא להאט את הבקשות שלך.</string>
-  <string id="ApiUrlNotFound">כתובת האתר לא נמצאה. שגיאה פוטנציאלית של כתובת ה-API בהגדרות.</string>
-  <string id="ConfigUrlNotFound">כתובת האתר לא נמצאה. שגיאת כתובת אתר פוטנציאלית של תצורה בהגדרות.</string>
-  <string id="UnhandledHttpErr">בקשת HTTP החזירה קוד שגיאה =</string>
-  <string id="TrailingSlashErr">כתובת ה-API לא חייבת לכלול לוכסן אחורי '/'</string>
+  <string id="ApiFlood">קריאות API מהירות מדי. אנא האט את בקשותיך.</string>
+  <string id="ApiUrlNotFound">כתובת URL לא נמצאה. שגיאת כתובת URL פוטנציאלית בהגדרות.</string>
+  <string id="AppName" scope="glance">HomeAssistant</string>
+  <string id="Available" scope="glance">זמין</string>
+  <string id="Cached" scope="glance">במטמון</string>
+  <string id="Checking" scope="glance">בודק...</string>
+  <string id="ConfigUrlNotFound">כתובת URL לא נמצאה. שגיאת כתובת URL פוטנציאלית של התצורה בהגדרות.</string>
+  <string id="Confirm">בטוח?</string>
+  <string id="Empty">ריק</string>
+  <string id="Executed" scope="glance">בוצע</string>
+  <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>
+  <string id="NoInternet">אין חיבור לאינטרנט.</string>
+  <string id="NoJson">לא התקבל JSON מבקשת HTTP.</string>
+  <string id="NoPhone" scope="glance">אין חיבור לטלפון.</string>
+  <string id="NoPhoneNoCache" scope="glance">אין חיבור לטלפון, אין תפריט במטמון.</string>
+  <string id="NoResponse">אין תגובה, בדוק את חיבור האינטרנט.</string>
+  <string id="TimedOut">פסק זמן לבקשה</string>
+  <string id="PinInputLocked">קלט PIN נעול עבור</string>
+  <string id="PotentialError">שגיאה פוטנציאלית</string>
+  <string id="Seconds">שניות</string>
+  <string id="TemplateError">שגיאת תבנית</string>
+  <string id="TrailingSlashErr">כתובת ה-URL של ה-API אסור שתכלול קו נטוי בסוף '/'.</string>
+  <string id="Unavailable" scope="glance">לא זמין</string>
+  <string id="Unconfigured" scope="glance">לא מוגדר</string>
+  <string id="UnhandledHttpErr">בקשת HTTP החזירה קוד שגיאה = </string>
+  <string id="WebhookFailed">נכשל רישום Webhook</string>
+  <string id="WrongPin">PIN שגוי</string>
+  <string id="WifiLteNotAvailable">אין Wi-Fi או LTE זמינים</string>
+  <string id="WifiLtePrompt">לבצע דרך Wi-Fi/LTE?</string>
+  <string id="WifiLteExecutionTitle">שולח אל Home Assistant.</string>
+  <string id="WifiLteExecutionDataError">לא התקבלו נתונים.</string>
+  <!-- עבור ה- GUI של הגדרות, המיתרים צריכים להיות בסדר שהם משתמשים בהם. -->
+  <string id="SettingsSelect">בחר...</string>
+  <string id="SettingsApiKey">מפתח API עבור HomeAssistant.</string>
+  <string id="SettingsApiKeyPrompt">אסימון גישה ארוך טווח.</string>
+  <string id="SettingsApiUrl">כתובת URL עבור ה-API של HomeAssistant.</string>
+  <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>
+  <string id="SettingsPollDelay">עיכוב סקר נוסף (בשניות). מוסיף עיכוב בין עדכוני הסטטוס של כל פריטי
+    התפריט.</string>
+  <string id="SettingsConfirmTimeout">לאחר זמן זה (בשניות), תיבת דו-שיח לאישור פעולה נסגרת אוטומטית
+    והפעולה מבוטלת. הגדר ל-0 כדי להשבית את פסק הזמן.</string>
+  <string id="SettingsPin">PIN בן 4 ספרות שישמש לכל הפעולות הדורשות אותו (0000-9999).</string>
+  <string id="SettingsPinError">אנא הגדר PIN מספרי תקין בן 4 ספרות בין 0000 ל-9999 בהגדרות היישום.</string>
+  <string id="SettingsTextAlign">יישור תפריט: שמאל (כבוי) או ימין (מופעל).</string>
+  <string id="SettingsLeftToRight">משמאל לימין</string>
+  <string id="SettingsRightToLeft">מימין לשמאל</string>
+  <string id="SettingsWidgetStart">(ווידג'ט בלבד) הפעל אוטומטית את היישום מהווידג'ט מבלי לחכות
+    להקשה.</string>
+  <string id="SettingsEnableBatteryLevel">אפשר לשירות הרקע לשלוח את רמת סוללת המכשיר, מיקום ו(אם
+    נתמך) נתוני פעילות אל Home Assistant.</string>
+  <string id="SettingsBatteryLevelRefreshRate">קצב הרענון (בדקות) שבו שירות הרקע ישלח נתונים באופן
+    חוזר.</string>
+  <string id="SettingsUserHttpHeader">כותרת HTTP שסופקה על ידי המשתמש</string>
+  <string id="SettingsUserHttpHeaderDescription">חלק מהתקנות Home Assistant דורשות הגדרה של כותרת
+    HTTP מותאמת אישית כדי לתפקד.</string>
+  <string id="SettingsUserHttpHeaderName">כותרת HTTP שסופקה על ידי המשתמש: שם</string>
+  <string id="SettingsUserHttpHeaderValue">כותרת HTTP שסופקה על ידי המשתמש: ערך</string>
+  <string id="SettingsClearWebhookId">התחבר מחדש אל Home Assistant (נקה מזהה Webhook, ראה מדריך
+    לפתרון בעיות).</string>
+  <string id="SettingsWebhookId">(קריאה בלבד) מזהה Webhook שנוצר על ידי המכשיר לעדכוני שירות רקע.
+    ייתכן שתזדקק לכך לצורך ניפוי באגים.</string>
 </strings>

resources-hrv/strings/strings.xml

@@ -9,31 +9,93 @@
    tested on a Venu 2 device. The source code is provided at:
               https://github.com/house-of-abbey/GarminHomeAssistant.
 
-   P A Abbey & J D Abbey, 31 October 2023
+   P A Abbey & J D Abbey & Someone0nEarth & vincentezw, 31 October 2023
 
 -->
 
 <!--
-  Generated by Google Translate: English to Croatian
-  Generirano Google prevoditeljem s engleskog
+  Generated by Google Translate and gemini-2.5-flash from English to Croatian
+  Generirano putem Google Prevoditelja i gemini-2.5-flash s engleskog na hrvatski
 -->
 
 <strings>
-  <string id="AppName">HomeAssistant</string>
-  <string id="MenuItemOn">Na</string>
-  <string id="MenuItemOff">Isključeno</string>
-  <string id="MenuItemTap">Dodirnite</string>
-  <string id="MenuItemMenu">Jelovnik</string>
-  <string id="NoPhone">Nema telefonske veze</string>
-  <string id="NoInternet">Nema internetske veze</string>
-  <string id="NoResponse">Nema odgovora, provjerite internetsku vezu</string>
-  <string id="NoMenu">Pogreška dohvaćanja izbornika</string>
-  <string id="NoAPIKey">Nema API ključa u postavkama aplikacije</string>
-  <string id="NoApiUrl">Nema API URL-a u postavkama aplikacije</string>
-  <string id="NoConfigUrl">Nema konfiguracijskog URL-a u postavkama aplikacije</string>
-  <string id="ApiFlood">API pozivi su prebrzi. Molimo usporite svoje zahtjeve.</string>
+  <string id="ApiFlood">API pozivi prebrzi. Usporite svoje zahtjeve.</string>
   <string id="ApiUrlNotFound">URL nije pronađen. Potencijalna pogreška API URL-a u postavkama.</string>
-  <string id="ConfigUrlNotFound">URL nije pronađen. Potencijalna pogreška URL-a konfiguracije u postavkama.</string>
-  <string id="UnhandledHttpErr">HTTP zahtjev vratio je kod greške =</string>
-  <string id="TrailingSlashErr">API URL ne smije imati kosu crtu na kraju '/'</string>
+  <string id="AppName" scope="glance">HomeAssistant</string>
+  <string id="Available" scope="glance">Dostupan</string>
+  <string id="Cached" scope="glance">Predmemorirano</string>
+  <string id="Checking" scope="glance">Provjera...</string>
+  <string id="ConfigUrlNotFound">URL nije pronađen. Potencijalna pogreška URL-a konfiguracije u
+    postavkama.</string>
+  <string id="Confirm">Potvrdi?</string>
+  <string id="Empty">Prazan</string>
+  <string id="Executed" scope="glance">Potvrđen</string>
+  <string id="GlanceMenu" scope="glance">Izbornik</string>
+  <string id="Memory" scope="glance">Memorija</string>
+  <string id="MenuUpdated">Izbornik ažuriran, 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 API URL-a u postavkama aplikacije.</string>
+  <string id="NoConfigUrl" scope="glance">Nema URL-a konfiguracije u postavkama aplikacije.</string>
+  <string id="NoInternet">Nema internetske veze.</string>
+  <string id="NoJson">Nije primljen JSON odgovor na HTTP zahtjev.</string>
+  <string id="NoPhone" scope="glance">Nema telefonske veze.</string>
+  <string id="NoPhoneNoCache" scope="glance">Nema telefonske veze, nema predmemoriranog izbornika.</string>
+  <string id="NoResponse">Nema odgovora, provjerite internetsku vezu</string>
+  <string id="TimedOut">Zahtjev je istekao</string>
+  <string id="PinInputLocked">Unos PIN-a zaključan na</string>
+  <string id="PotentialError">Potencijalna pogreška</string>
+  <string id="Seconds">sekundi</string>
+  <string id="TemplateError">Pogreška predloška</string>
+  <string id="TrailingSlashErr">API URL ne smije sadržavati kosu crtu '/' na kraju.</string>
+  <string id="Unavailable" scope="glance">Nedostupan</string>
+  <string id="Unconfigured" scope="glance">Nekonfiguriran</string>
+  <string id="UnhandledHttpErr">HTTP zahtjev vratio je kod pogreške = </string>
+  <string id="WebhookFailed">Registracija Webhooka nije uspjela</string>
+  <string id="WrongPin">Pogrešan PIN</string>
+  <string id="WifiLteNotAvailable">Wi-Fi ili LTE nije dostupno</string>
+  <string id="WifiLtePrompt">Izvršiti putem Wi-Fi/LTE?</string>
+  <string id="WifiLteExecutionTitle">Slanje u Home Assistant.</string>
+  <string id="WifiLteExecutionDataError">Nema primljenih podataka.</string>
+  <!-- Za GUI postavki, nizovi znakova trebaju biti poredani redoslijedom kojim se koriste. -->
+  <string id="SettingsSelect">Odaberite...</string>
+  <string id="SettingsApiKey">API ključ za HomeAssistant.</string>
+  <string id="SettingsApiKeyPrompt">Dugotrajni pristupni token.</string>
+  <string id="SettingsApiUrl">URL za HomeAssistant API.</string>
+  <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">Provjeriti ažuriranja izbornika pri pokretanju aplikacije? Napomena: Predmemoriranje izbornika mora biti omogućeno. Ova postavka može uzrokovati rušenje starijih uređaja s manje memorije.</string>
+  <string id="SettingsWifiLteExecutionEnable">Omogući izvršavanje naredbi putem Wi-Fi/LTE.</string>
+  <string id="SettingsVibration">Treba li aplikacija davati povratne informacije putem vibracija?</string>
+  <string id="SettingsAppTimeout">Istek vremena u sekundama. Izađite iz aplikacije nakon ovog
+    razdoblja neaktivnosti radi uštede baterije uređaja.</string>
+  <string id="SettingsPollDelay">Dodatno kašnjenje provjere (u sekundama). Dodaje kašnjenje između
+    ažuriranja statusa svih stavki izbornika.</string>
+  <string id="SettingsConfirmTimeout">Nakon tog vremena (u sekundama), dijaloški okvir za potvrdu
+    radnje automatski se zatvara i radnja se otkazuje. Postavite na 0 za onemogućavanje isteka
+    vremena.</string>
+  <string id="SettingsPin">Četveroznamenkasti PIN koji se koristi za sve radnje koje ga zahtijevaju
+    (0000-9999).</string>
+  <string id="SettingsPinError">Molimo konfigurirajte valjani četveroznamenkasti numerički PIN
+    između 0000 i 9999 u postavkama aplikacije.</string>
+  <string id="SettingsTextAlign">Poravnanje izbornika: lijevo (isključeno) ili desno (uključeno).</string>
+  <string id="SettingsLeftToRight">Slijeva na desno</string>
+  <string id="SettingsRightToLeft">Zdesna nalijevo</string>
+  <string id="SettingsWidgetStart">(Samo widget) Automatski pokrenite aplikaciju iz widgeta bez
+    čekanja na dodir.</string>
+  <string id="SettingsEnableBatteryLevel">Omogućite pozadinsku uslugu za slanje razine baterije
+    uređaja, lokacije i (ako je podržano) podataka o aktivnosti u Home Assistant.</string>
+  <string id="SettingsBatteryLevelRefreshRate">Brzina osvježavanja (u minutama) u kojoj bi
+    pozadinska usluga trebala ponoviti slanje podataka.</string>
+  <string id="SettingsUserHttpHeader">Korisnički HTTP zaglavlje</string>
+  <string id="SettingsUserHttpHeaderDescription">Neke instalacije Home Assistanta zahtijevaju
+    specifikaciju prilagođenog HTTP zaglavlja za funkcioniranje.</string>
+  <string id="SettingsUserHttpHeaderName">Korisnički HTTP zaglavlje: Naziv</string>
+  <string id="SettingsUserHttpHeaderValue">Korisnički HTTP zaglavlje: Vrijednost</string>
+  <string id="SettingsClearWebhookId">Ponovno se povežite s Home Assistantom (očisti ID Webhooka,
+    pogledajte vodič za rješavanje problema).</string>
+  <string id="SettingsWebhookId">(Samo za čitanje) ID Webhooka koji je uređaj stvorio za ažuriranja
+    pozadinske usluge. Možda će vam ovo trebati za otklanjanje pogrešaka.</string>
 </strings>

resources-hun/strings/strings.xml

@@ -9,31 +9,95 @@
    tested on a Venu 2 device. The source code is provided at:
               https://github.com/house-of-abbey/GarminHomeAssistant.
 
-   P A Abbey & J D Abbey, 31 October 2023
+   P A Abbey & J D Abbey & Someone0nEarth & vincentezw, 31 October 2023
 
 -->
 
 <!--
-  Generated by Google Translate: English to Hungarian
-  A Google Fordító generálta angolból
+  Generated by Google Translate and gemini-2.5-flash from English to Hungarian
+  Fordította: Google Translate és gemini-2.5-flash angolról magyarra
 -->
 
 <strings>
-  <string id="AppName">HomeAssistant</string>
-  <string id="MenuItemOn">Tovább</string>
-  <string id="MenuItemOff">Ki</string>
-  <string id="MenuItemTap">Koppintson a</string>
-  <string id="MenuItemMenu">Menü</string>
-  <string id="NoPhone">Nincs telefonkapcsolat</string>
-  <string id="NoInternet">Nincs internetkapcsolat</string>
+  <string id="ApiFlood">Az API hívások túl gyorsak. Kérjük, lassítsa a kéréseit.</string>
+  <string id="ApiUrlNotFound">URL nem található. Lehetséges API URL hiba a beállításokban.</string>
+  <string id="AppName" scope="glance">HomeAssistant</string>
+  <string id="Available" scope="glance">Elérhető</string>
+  <string id="Cached" scope="glance">Gyorsítótárazott</string>
+  <string id="Checking" scope="glance">Ellenőrzés ...</string>
+  <string id="ConfigUrlNotFound">URL nem található. Lehetséges konfigurációs URL hiba a
+    beállításokban.</string>
+  <string id="Confirm">Biztos?</string>
+  <string id="Empty">Üres</string>
+  <string id="Executed" scope="glance">Megerősített</string>
+  <string id="GlanceMenu" scope="glance">Menü</string>
+  <string id="Memory" scope="glance">Memória</string>
+  <string id="MenuUpdated">Menü frissítve, indítsa újra.</string>
+  <string id="MenuCheckDisabled">Menüfrissítések letiltva.</string>
+  <string id="NoAPIKey" scope="glance">Nincs API kulcs az alkalmazás beállításaiban.</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ás beállításaiban.</string>
+  <string id="NoInternet">Nincs internetkapcsolat.</string>
+  <string id="NoJson">A HTTP kérés nem adott vissza JSON-t.</string>
+  <string id="NoPhone" scope="glance">Nincs telefonkapcsolat.</string>
+  <string id="NoPhoneNoCache" scope="glance">Nincs telefonkapcsolat, nincs gyorsítótárazott menü.</string>
   <string id="NoResponse">Nincs válasz, ellenőrizze az internetkapcsolatot</string>
-  <string id="NoMenu">Menü Lekérési hiba</string>
-  <string id="NoAPIKey">Nincs API kulcs az alkalmazás beállításaiban</string>
-  <string id="NoApiUrl">Nincs API URL az alkalmazás beállításai között</string>
-  <string id="NoConfigUrl">Nincs konfigurációs URL az alkalmazás beállításai között</string>
-  <string id="ApiFlood">Az API-hívások túl gyorsak. Kérjük, lassítsa a kérések teljesítését.</string>
-  <string id="ApiUrlNotFound">Az URL nem található. Lehetséges API URL hiba a beállításokban.</string>
-  <string id="ConfigUrlNotFound">Az URL nem található. Lehetséges konfigurációs URL hiba a beállításokban.</string>
-  <string id="UnhandledHttpErr">A HTTP-kérés = hibakódot adott vissza</string>
-  <string id="TrailingSlashErr">Az API URL-ben nem lehet perjel a „/”</string>
+  <string id="TimedOut">A kérés időtúllépés</string>
+  <string id="PinInputLocked">PIN bevitel zárolva</string>
+  <string id="PotentialError">Lehetséges hiba</string>
+  <string id="Seconds">másodperc</string>
+  <string id="TemplateError">Sablonhiba</string>
+  <string id="TrailingSlashErr">Az API URL nem tartalmazhat záró perjelet '/'.</string>
+  <string id="Unavailable" scope="glance">Nem érhető el</string>
+  <string id="Unconfigured" scope="glance">Konfigurálatlan</string>
+  <string id="UnhandledHttpErr">HTTP kérés hibakóddal tért vissza: </string>
+  <string id="WebhookFailed">Nem sikerült regisztrálni a webhookot</string>
+  <string id="WrongPin">Hibás PIN</string>
+  <string id="WifiLteNotAvailable">Nincs elérhető Wi-Fi vagy LTE</string>
+  <string id="WifiLtePrompt">Végrehajtás a Wi-Fi/LTE-n keresztül?</string>
+  <string id="WifiLteExecutionTitle">Küldés a Home Assistantnek.</string>
+  <string id="WifiLteExecutionDataError">Nem érkezett adat.</string>
+  <!-- A beállítások GUI -jához a karakterláncoknak a használt sorrendben kell lenniük. -->
+  <string id="SettingsSelect">Válasszon...</string>
+  <string id="SettingsApiKey">API kulcs a Home Assistanthez.</string>
+  <string id="SettingsApiKeyPrompt">Hosszú élettartamú hozzáférési token.</string>
+  <string id="SettingsApiUrl">URL a Home Assistant API-hoz.</string>
+  <string id="SettingsConfigUrl">URL a menükonfigurációhoz (JSON).</string>
+  <string id="SettingsCacheConfig">Gyorsítótárazza az alkalmazás a menükonfigurációt?</string>
+  <string id="SettingsClearCache">Törölje az alkalmazás a meglévő gyorsítótárat a következő
+    indításkor?</string>
+  <string id="SettingsEnableMenuUpdateCheck">Menüfrissítések ellenőrzése az alkalmazás indításakor? Megjegyzés: A menü gyorsítótárazásának engedélyezve kell lennie. Ez a beállítás régebbi, kevesebb memóriával rendelkező eszközök összeomlását okozhatja.</string>
+  <string id="SettingsWifiLteExecutionEnable">Parancsok végrehajtásának engedélyezése Wi-Fi/LTE-n
+    keresztül.</string>
+  <string id="SettingsVibration">Adjon visszajelzést az alkalmazás rezgésekkel?</string>
+  <string id="SettingsAppTimeout">Időtúllépés másodpercben. Az eszköz akkumulátorának kímélése
+    érdekében az alkalmazás kilép ennyi inaktivitás után.</string>
+  <string id="SettingsPollDelay">További lekérdezési késleltetés (másodpercben). Késleltetést ad az
+    összes menüelem állapotfrissítése közé.</string>
+  <string id="SettingsConfirmTimeout">Ezen idő (másodpercben) elteltével egy művelet megerősítő
+    párbeszédablaka automatikusan bezáródik, és a művelet megszakad. Állítsa 0-ra az időtúllépés
+    kikapcsolásához.</string>
+  <string id="SettingsPin">4 számjegyű PIN-kód, amelyet minden szükséges művelethez használni kell
+    (0000-9999).</string>
+  <string id="SettingsPinError">Kérjük, konfiguráljon egy érvényes 4 számjegyű numerikus PIN-kódot
+    0000 és 9999 között az alkalmazás beállításaiban.</string>
+  <string id="SettingsTextAlign">Menü igazítása: Balra (ki) vagy Jobbra (be).</string>
+  <string id="SettingsLeftToRight">Balról jobbra</string>
+  <string id="SettingsRightToLeft">Jobbról balra</string>
+  <string id="SettingsWidgetStart">(Csak widget) Az alkalmazás automatikus indítása a widgetről,
+    érintés nélkül.</string>
+  <string id="SettingsEnableBatteryLevel">Engedélyezze a háttérszolgáltatásnak, hogy elküldje az
+    eszköz akkumulátorának töltöttségi szintjét, helyét és (ha támogatott) tevékenységi adatait a
+    Home Assistantnek.</string>
+  <string id="SettingsBatteryLevelRefreshRate">Az adatküldés ismétlési gyakorisága (percekben),
+    amellyel a háttérszolgáltatásnak adatokat kell küldenie.</string>
+  <string id="SettingsUserHttpHeader">Felhasználó által megadott HTTP fejléc</string>
+  <string id="SettingsUserHttpHeaderDescription">Néhány Home Assistant telepítéshez egyéni HTTP
+    fejléc megadása szükséges a működéshez.</string>
+  <string id="SettingsUserHttpHeaderName">Felhasználó által megadott HTTP-fejléc: Név</string>
+  <string id="SettingsUserHttpHeaderValue">Felhasználó által megadott HTTP-fejléc: Érték</string>
+  <string id="SettingsClearWebhookId">Csatlakozás újra a Home Assistanthez (webhook azonosító
+    törlése, lásd a hibaelhárítási útmutatót).</string>
+  <string id="SettingsWebhookId">(Csak olvasható) Az eszköz által létrehozott webhook azonosító a
+    háttérszolgáltatás frissítéseihez. Szüksége lehet rá a hibakereséshez.</string>
 </strings>

resources-icons-18-w/drawables.xml

@@ -0,0 +1,23 @@
+<!--
+
+   Distributed under MIT Licence
+     See https://github.com/house-of-abbey/GarminHomeAssistant/blob/main/LICENSE.
+
+
+   GarminHomeAssistant is a Garmin IQ application written in Monkey C and routinely
+   tested on a Venu 2 device. The source code is provided at:
+              https://github.com/house-of-abbey/GarminHomeAssistant.
+
+   J D Abbey & P A Abbey, 28 December 2022
+
+  References:
+   * https://fonts.google.com/icons
+
+-->
+
+<drawables>
+    <bitmap id="ErrorIcon" filename="error.svg"/>
+    <bitmap id="GroupTypeIcon" filename="group_type.svg"/>
+    <bitmap id="TapTypeIcon" filename="tap_type.svg"/>
+    <bitmap id="InfoTypeIcon" filename="info_type.svg"/>
+</drawables>

resources-icons-18-w/error.svg

@@ -0,0 +1 @@
+<svg height="18" viewBox="0 0 48 48" width="18" xmlns="http://www.w3.org/2000/svg"><path d="M24 34q.7 0 1.175-.475.475-.475.475-1.175 0-.7-.475-1.175Q24.7 30.7 24 30.7q-.7 0-1.175.475-.475.475-.475 1.175 0 .7.475 1.175Q23.3 34 24 34Zm-1.35-7.65h3V13.7h-3ZM24 44q-4.1 0-7.75-1.575-3.65-1.575-6.375-4.3-2.725-2.725-4.3-6.375Q4 28.1 4 23.95q0-4.1 1.575-7.75 1.575-3.65 4.3-6.35 2.725-2.7 6.375-4.275Q19.9 4 24.05 4q4.1 0 7.75 1.575 3.65 1.575 6.35 4.275 2.7 2.7 4.275 6.35Q44 19.85 44 24q0 4.1-1.575 7.75-1.575 3.65-4.275 6.375t-6.35 4.3Q28.15 44 24 44Zm.05-3q7.05 0 12-4.975T41 23.95q0-7.05-4.95-12T24 7q-7.05 0-12.025 4.95Q7 16.9 7 24q0 7.05 4.975 12.025Q16.95 41 24.05 41ZM24 24Z" fill="white" stroke="white"/></svg>

resources-icons-18-w/group_type.svg

@@ -0,0 +1,7 @@
+<svg height="18" viewBox="0 0 200 500" width="18" xmlns="http://www.w3.org/2000/svg">
+<g transform="matrix(1, 0, 0, 1, 0, 0)">
+<rect fill="white" height="100" rx="40" ry="40" width="200" x="0" y="0"/>
+<rect fill="white" height="100" rx="40" ry="40" width="200" x="0" y="200"/>
+<rect fill="white" height="100" rx="40" ry="40" width="200" x="0" y="400"/>
+</g>
+</svg>