diff --git a/HISTORY.md b/HISTORY.md index 64f2226..8769814 100644 --- a/HISTORY.md +++ b/HISTORY.md @@ -9,14 +9,14 @@ | 1.2 | Do not crash on zero items to update. Report unreachable URLs. Verify API URL does not have a trailing slash '/'. Increased HTTP response diagnosis. Reduced minimum API Level required from 3.3.0 to 3.1.0 to allow more device "part numbers" to be satisfied. | | 1.3 | Tap for scripts was working in emulation but not on some phones. Decision is to make the 'service' field in the JSON compulsory for 'tap' menu items. This is a breaking change, but for many might be a fix for something not working correctly. Improve language support, we can now accept language corrections and prevent the automated translation of strings from clobbering manually refined entries. Thank you to two new contributors. | | 1.4 | New lean user Interface with thanks to [Someone0nEarth](https://github.com/Someone0nEarth) for their contribution which is now the default. If you prefer the old style you can still select it in the settings. The provision of a 'service' tag is now not just heavily suggested by the JSON schema, it is enforced in code. With apologies to anyone suffering a breakage as a result. | -| 1.5 |
Added an optional confirmation dialogue view to prevent accidental execution of actions on mistaken tap. This also brings a change in the JSON schema to allow an optional field to specify that the confirmation should be used for a menu item. As we are now maturing and adding features we have decided to mitigate breaking changes to the JSON schema by being more careful to adopt the Home Assistant schema (noting there is a 1:1 mapping between YAML and JSON). This change does deprecate the top level `service` tag in favour of `tag_action` containing multiple fields including `service` & `confirm`. Users should migrate to the new format for the new functionality, but the timescale for actual deprecation are long and undecided. | +| 1.5 |
Added an optional confirmation dialogue view to prevent accidental execution of actions on mistaken tap. This also brings a change in the JSON schema to allow an optional field to specify that the confirmation should be used for a menu item. As we are now maturing and adding features we have decided to mitigate breaking changes to the JSON schema by being more careful to adopt the HomeAssistant schema (noting there is a 1:1 mapping between YAML and JSON). This change does deprecate the top level `service` tag in favour of `tag_action` containing multiple fields including `service` & `confirm`. Users should migrate to the new format for the new functionality, but the timescale for actual deprecation are long and undecided. | | 1.6 | Added a user configurable 'timeout' in seconds so that when no action is taken the application automatically closes, stopping the continuous polling for changes of status and hence saving the drain on the battery. This can be disabled with timeout=0. | | 1.7 | Added timeout to confirmation views so that when used for security devices it does not linger when left unconfirmed. Thanks to [Jan Schneider](https://github.com/j-a-n) for the contribution. Known bug for devices not supporting [`WatchUi.getCurrentView()`](https://developer.garmin.com/connect-iq/api-docs/Toybox/WatchUi.html#getCurrentView-instance_function) API call which is only available on API Level 3.4.0, e.g. Vivoactive 4S. | | 2.0 | A significant code base change to enable both a 'widget' version for older devices, e.g. Venu (1), and an application with a glance, e.g. Venu2. These two versions must now be distributed under separate application IDs, but they have the same code base. A further 20 more devices are now supported, the settings have been internationalised, and there's a bug fix for older devices when trying to display a helpful error message but instead the application crashed. This version has come from a significant collaboration with [Someone0nEarth](https://github.com/Someone0nEarth). | -| 2.1 | Deployment of an idea to provide Home Assistant with access to the watch battery level. Using this requires [significant setup](BackgroundService.md) on the Home Assistant configuration and hence is detailed separately. Due to this, the default state for this battery option is _off_. Changed the application settings user interface to be more intuitive, and hence amended the way settings are managed in the background. | +| 2.1 | Deployment of an idea to provide HomeAssistant with access to the watch battery level. Using this requires [significant setup](BackgroundService.md) on the HomeAssistant configuration and hence is detailed separately. Due to this, the default state for this battery option is _off_. Changed the application settings user interface to be more intuitive, and hence amended the way settings are managed in the background. | | 2.2 | Adds a feature to cache the menu configuration and save the time taken for an HTTP request to fetch it. You as the user are responsible for managing the cache by clearing it when you update your configuration. Improvement to widget root display updates. Bug fix for battery level reporting when in the glance carousel. Fixed an uninternationalised string, "Execute". Unfixed issue with battery level updates when the user is not an administrator. | -| 2.3 | Fix for battery level updates where previously the function only worked for administrator accounts. The new solution is based on Webhooks and is simpler to implement on Home Assistant. Language support fix where an automatic translation produced an inappropriate word, possibly in more than one language. | -| 2.4 | Sensor status reporting via Home Assistant 'templates'. This provides a generalised way of viewing the status of any entity as long as the result can be rendered as text, e.g. 'uncovered', 'open', '76%', '21 °C'. Removal of the menu style option. The original style was kept after the introduction of the icon style solely to keep the code for a possible re-use for sensor statuses. This version delivers that new feature, hence the style option has been removed. The new JSON configuration file format allows for the old style to be replicated if you are desperate! Added a feature to provide parameters to actions (`tap` or `template`). Added a feature to confirm `toggle` menu items. | +| 2.3 | Fix for battery level updates where previously the function only worked for administrator accounts. The new solution is based on Webhooks and is simpler to implement on HomeAssistant. Language support fix where an automatic translation produced an inappropriate word, possibly in more than one language. | +| 2.4 | Sensor status reporting via HomeAssistant 'templates'. This provides a generalised way of viewing the status of any entity as long as the result can be rendered as text, e.g. 'uncovered', 'open', '76%', '21 °C'. Removal of the menu style option. The original style was kept after the introduction of the icon style solely to keep the code for a possible re-use for sensor statuses. This version delivers that new feature, hence the style option has been removed. The new JSON configuration file format allows for the old style to be replicated if you are desperate! Added a feature to provide parameters to actions (`tap` or `template`). Added a feature to confirm `toggle` menu items. | | 2.5 | A small memory efficiency of about 1kB by removing `RezStrings.mc`. This will aid widgets on old watches that only have 60kB available to an application and are using about 45kB before the menu is fetched, hence 1kB is more significant to those devices. | | 2.6 | Added more information reporting to the background service, in addition to the device battery level and charging status, we now include location, location accuracy, and (if supported by your device) the activity information. Note the updates are sent periodically and are not event driven. | | 2.7 | Bug fix release: 1. Handling a settings change, 2. Avoid caching a bad menu, 3. Managing bad JSON in menu definitions. | @@ -46,6 +46,7 @@ | 2.31 | Adding [two new options](./examples/Actions.md#exit-on-tap) to the menu items: 1) The ability to disable a menu item, e.g. temporarily for seasonal changes, 2) The option to exit after a menu item has been select. | | 2.32 | Bug fix for a breaking change extracting options caused by the need to rearrange function parameters for an [annoying compiler error](https://github.com/house-of-abbey/GarminHomeAssistant/issues/253). | | 3.0 | First version with the ability to use [Wi-Fi or LTE](Wi-Fi.md) instead of Bluetooth but with limited functionality, thanks to [@vincentezw](https://github.com/vincentezw). | -| 3.1 | Added the ability for users to provide [custom HTTP headers](HTTP_Headers.md) for their Home Assistant server. Improved German language translations. Thanks to [@tispokes](https://github.com/tispokes) for assisting with both of those. Removed all groups in settings as the SDK is buggy. Fixed a bug with templates in glances causing application crash on startup. | -| 3.2 | Only enable or disable sensors on Home Assistant when the background service options is changed, i.e. do not call the API to enable on start up every time. | +| 3.1 | Added the ability for users to provide [custom HTTP headers](HTTP_Headers.md) for their HomeAssistant server. Improved German language translations. Thanks to [@tispokes](https://github.com/tispokes) for assisting with both of those. Removed all groups in settings as the SDK is buggy. Fixed a bug with templates in glances causing application crash on startup. | +| 3.2 | Only enable or disable sensors on HomeAssistant when the background service options is changed, i.e. do not call the API to enable on start up every time. | | 3.3 | Providing automatic detection for menu definition updates, but still requires an application restart. | +| 3.4 | Fixed a bug where templates failed to display in toggle menu items (at least on some devices). Fixed a bug where a menu item requesting to exit on completion appeared to indicate failure when using Wi-Fi or LTE. The fix uses a delay in exiting the application modelled as sufficient for a Venu 2 device, so this might need tweaking for other devices. Attempt to fixed an "Out of Memory" bug caused by v3.3 by making automatic checking for menu updates both optional and automatically turned off when insufficient memory is available. This last bug is device dependent and may require another attempt. | diff --git a/README.md b/README.md index e033265..ecb13d2 100644 --- a/README.md +++ b/README.md @@ -4,24 +4,24 @@ -A Garmin application to provide a "dashboard" to control your devices via [Home Assistant](https://www.home-assistant.io/). The application will never be as fully fledged as a Home Assistant dashboard, so it is designed to be good enough for the simple and essential things. Those things that can be activated via an on/off toggle or a tap. That should cover lights, switches, and anything requiring a single press such as an automation. For anything more complicated, e.g. thermostat, it would always be quicker and simpler to reach for your phone or tablet... or the device's own remote control! +A Garmin application to provide a "dashboard" to control your devices via [HomeAssistant](https://www.home-assistant.io/). The application will never be as fully fledged as a HomeAssistant dashboard, so it is designed to be good enough for the simple and essential things. Those things that can be activated via an on/off toggle or a tap. That should cover lights, switches, and anything requiring a single press such as an automation. For anything more complicated, e.g. thermostat, it would always be quicker and simpler to reach for your phone or tablet... or the device's own remote control! -The application is designed around a simple scrollable menu where menu items have been extended to interface with the [Home Assistant API](https://developers.home-assistant.io/docs/api/rest/), e.g. to get the status of switches or lights for display on the `toggle` menu item, or a text status for an entity (`info` item). It is possible to nest menus, so there is a menu item to open a sub-menu. This can be arbitrarily deep and nested in the format of a tree of items, although you need to consider if reaching for your phone becomes quicker to select the device what you want to control. +The application is designed around a simple scrollable menu where menu items have been extended to interface with the [HomeAssistant API](https://developers.home-assistant.io/docs/api/rest/), e.g. to get the status of switches or lights for display on the `toggle` menu item, or a text status for an entity (`info` item). It is possible to nest menus, so there is a menu item to open a sub-menu. This can be arbitrarily deep and nested in the format of a tree of items, although you need to consider if reaching for your phone becomes quicker to select the device what you want to control. -**The intended audience for this application are those comfortable with configuring a Home Assistant** (e.g. editing the YAML configuration files) and debugging why URLs don't work. It does not require programming skills, but the menu is configured via JSON which feels like "coding" (more like "describing"). If you are not comfortable with this relatively low level of configuration, you may like to try other Garmin applications instead. +**The intended audience for this application are those comfortable with configuring a HomeAssistant** (e.g. editing the YAML configuration files) and debugging why URLs don't work. It does not require programming skills, but the menu is configured via JSON which feels like "coding" (more like "describing"). If you are not comfortable with this relatively low level of configuration, you may like to try other Garmin applications instead. **If you are struggling with getting the application to work, please consult the [troubleshooting guide](TroubleShooting.md#menu-configuration-url) first.** ## No HTTPS? > [!IMPORTANT] -> The Garmin SDK allows HTTP requests only to a limited number of domains specified in their app. Therefore, for your Garmin to communicate with your Home Assistant instance, your Home Assistant instance must be accessible via HTTPS (with a public certificate!) or through a local DNS server that overrides one of the whitelisted domains to communicate using HTTP. +> The Garmin SDK allows HTTP requests only to a limited number of domains specified in their app. Therefore, for your Garmin to communicate with your HomeAssistant instance, your HomeAssistant instance must be accessible via HTTPS (with a public certificate!) or through a local DNS server that overrides one of the whitelisted domains to communicate using HTTP. > >New with version 3.1, you can use [Cloudflared](https://github.com/brenner-tobias/addon-cloudflared) plug-in in combination with a [custom HTTP header](HTTP_Headers.md) and do not need a public certificate for HTTPS. > -> To make your Home Assistant instance accessible via HTTPS, you will need a public certificate. You can get one for free from [Let's Encrypt](https://letsencrypt.org/) or you can pay for [Home Assistant cloud](https://www.nabucasa.com/). (You can install a local [Nginx proxy server](https://my.home-assistant.io/redirect/supervisor_addon/?addon=a0d7b954_nginxproxymanager) to manage Let's Encrypt certificates.) +> To make your HomeAssistant instance accessible via HTTPS, you will need a public certificate. You can get one for free from [Let's Encrypt](https://letsencrypt.org/) or you can pay for [HomeAssistant cloud](https://www.nabucasa.com/). (You can install a local [Nginx proxy server](https://my.home-assistant.io/redirect/supervisor_addon/?addon=a0d7b954_nginxproxymanager) to manage Let's Encrypt certificates.) > -> If you use a local DNS server (like [Pi-Hole](https://pi-hole.net/)), you can create a local DNS record for the domain `garmincdn.com` (which is allowed for HTTP in the Garmin SDK) and map it to your Home Assistant instance's IP. "_[About Communication Between Garmin SDK and a Raspberry Pi](https://www.instructables.com/About-Communication-Between-Garmin-SDK-and-a-Raspb/)_" provides additional workarounds for HTTP request restrictions in the Garmin SDK. +> If you use a local DNS server (like [Pi-Hole](https://pi-hole.net/)), you can create a local DNS record for the domain `garmincdn.com` (which is allowed for HTTP in the Garmin SDK) and map it to your HomeAssistant instance's IP. "_[About Communication Between Garmin SDK and a Raspberry Pi](https://www.instructables.com/About-Communication-Between-Garmin-SDK-and-a-Raspb/)_" provides additional workarounds for HTTP request restrictions in the Garmin SDK. > > **No support is offered to those circumventing the HTTPS restriction of the Connect IQ SDK.** You are supporting yourself! @@ -56,13 +56,13 @@ The following table lists the differences in functionality between the two. The ## Dashboard Definition -Setup for this menu is more complicated than the Connect IQ settings menu really allows you to specify. In order to make the dashboard easily configurable and easy to change, we have provided an external mechanism for specifying the menu layout, a JSON file you write, retrieved from a URL you specify. JSON was chosen over YAML because Garmin can parse JSON HTTP GET responses into its own internal dictionary, it cannot parse YAML, hence a choice of one really. Note that JSON and YAML are essentially a 1:1 format mapping except JSON does not have comments. We recommend you take advantage of [Home Assistant's own web server](https://www.home-assistant.io/integrations/http/#hosting-files) to provide the JSON definition. The advantages of this are: +Setup for this menu is more complicated than the Connect IQ settings menu really allows you to specify. In order to make the dashboard easily configurable and easy to change, we have provided an external mechanism for specifying the menu layout, a JSON file you write, retrieved from a URL you specify. JSON was chosen over YAML because Garmin can parse JSON HTTP GET responses into its own internal dictionary, it cannot parse YAML, hence a choice of one really. Note that JSON and YAML are essentially a 1:1 format mapping except JSON does not have comments. We recommend you take advantage of [HomeAssistant's own web server](https://www.home-assistant.io/integrations/http/#hosting-files) to provide the JSON definition. The advantages of this are: -1. the file is as public as you make your Home Assistant, -2. the file is editable within Home Assistant via "[Studio Code Server](https://my.home-assistant.io/redirect/supervisor_addon/?addon=a0d7b954_vscode)", and +1. the file is as public as you make your HomeAssistant, +2. the file is editable within HomeAssistant via "[Studio Code Server](https://my.home-assistant.io/redirect/supervisor_addon/?addon=a0d7b954_vscode)", and 3. the schema is verifiable using [JSON Schema](https://json-schema.org/overview/what-is-jsonschema). -We have used `/config/www/garmin/.json` on our home brew Home Assistant's file system. That equates to a URL of `https://homeassistant.local/local/garmin/.json`. +We have used `/config/www/garmin/.json` on our home brew HomeAssistant's file system. That equates to a URL of `https://homeassistant.local/local/garmin/.json`. > [!IMPORTANT] > However [recent reports](https://community.home-assistant.io/t/www-folder-location-for-local-documents/24903/16) suggest this path may no longer work on [Nabu Casa](https://www.nabucasa.com/) and you should use `/homeassistant/www/` instead of `/config/www/`. We are unable to verify this since our free trial of Nabu Casa has expired. @@ -160,7 +160,7 @@ The example above illustrates how to configure: * You can also display the status of devices (`info`) which is essentially a `tap` with no action * All menu items can display the results of evaluating [templates](examples/Templates.md). -The following table indicates how Home Assistant entity types can map to the Garmin applications menu types. Presently, an automation is the only one that can be either a `tap` or a `toggle`. +The following table indicates how HomeAssistant entity types can map to the Garmin applications menu types. Presently, an automation is the only one that can be either a `tap` or a `toggle`. | HA Entity Type | Tap | Toggle | Info (status)| |------------------|:---:|:------:|:------------:| @@ -178,7 +178,7 @@ Multiple templates are evaluated in a single HTTP request to update their status You can now specify alternative texts to use instead of "On" and "Off", e.g. "Locked" and "Unlocked" or "Open" and "Closed" through the use of a [template menu item](examples/Templates.md). But wouldn't having locks operated from your watch be a security concern ;-) ? -The [schema](https://raw.githubusercontent.com/house-of-abbey/GarminHomeAssistant/main/config.schema.json) is checked by using a URL directly back to this GitHub source repository, so you do not need to install that file. You can just copy & paste your entity names from the YAML configuration files used to configure Home Assistant. With a submenu, there's a difference between `title` and `name`. The `name` goes on the menu item, and the `title` at the head of the submenu. If your dashboard definition fails to meet the schema, the application will simply drop items with the wrong field names without warning to protect itself. +The [schema](https://raw.githubusercontent.com/house-of-abbey/GarminHomeAssistant/main/config.schema.json) is checked by using a URL directly back to this GitHub source repository, so you do not need to install that file. You can just copy & paste your entity names from the YAML configuration files used to configure HomeAssistant. With a submenu, there's a difference between `title` and `name`. The `name` goes on the menu item, and the `title` at the head of the submenu. If your dashboard definition fails to meet the schema, the application will simply drop items with the wrong field names without warning to protect itself. ### Old deprecated format @@ -206,7 +206,7 @@ The above should be replaced by the following: } ``` -This allows the `confirm` and `pin` fields to be accommodated in the `tap_action` along side the `service` tag, and follows the Home Assistant YAML format more closely. +This allows the `confirm` and `pin` fields to be accommodated in the `tap_action` along side the `service` tag, and follows the HomeAssistant YAML format more closely. ### More Examples @@ -217,8 +217,8 @@ This allows the `confirm` and `pin` fields to be accommodated in the `tap_action ## Editing the JSON file You have options. The first is what we use. -1. **Best!** Use the GarminHomeAssistant [Web-based Editor](https://house-of-abbey.github.io/GarminHomeAssistant/web/) which includes `entity` and `service` name completion and validation by fetching data from your own Home Assistant instance. _Pretty nifty eh?_ The other method listed below do not add this convenience and checking. -2. Use the [Studio Code Server](https://community.home-assistant.io/t/home-assistant-community-add-on-visual-studio-code/107863) addon for Home Assistant. You can then edit your JSON file in place. +1. **Best!** Use the GarminHomeAssistant [Web-based Editor](https://house-of-abbey.github.io/GarminHomeAssistant/web/) which includes `entity` and `service` name completion and validation by fetching data from your own HomeAssistant instance. _Pretty nifty eh?_ The other method listed below do not add this convenience and checking. +2. Use the [Studio Code Server](https://community.home-assistant.io/t/home-assistant-community-add-on-visual-studio-code/107863) addon for HomeAssistant. You can then edit your JSON file in place. 3. Locally installed VSCode, or if not installed, try 4. The on-line version at https://vscode.dev/, which works really well. @@ -232,7 +232,7 @@ Make sure you can browse to the URL of your JSON file in a standard web browser ## API Key Creation -Having created your JSON definition for your dashboard, you need to create an API key for your personal account on Home Assistant. You will need a [Long-Lived Access Token](https://developers.home-assistant.io/docs/auth_api/#long-lived-access-token). This is not obvious to find and is bound to your own Home Assistant account. Follow the menu sequence: `HA -> User Profile -> "Security" tab -> Long-lived access tokens`. Make sure you save the generated token before dismissing it. +Having created your JSON definition for your dashboard, you need to create an API key for your personal account on HomeAssistant. You will need a [Long-Lived Access Token](https://developers.home-assistant.io/docs/auth_api/#long-lived-access-token). This is not obvious to find and is bound to your own HomeAssistant account. Follow the menu sequence: `HA -> User Profile -> "Security" tab -> Long-lived access tokens`. Make sure you save the generated token before dismissing it. ![Long-Lived Access Token](images/Long_Lived_Access_Tokens.png) @@ -240,7 +240,7 @@ Having created that token, before you dismiss the dialogue box with the value yo ## API URL -If you are using [Nabu Casa](https://www.nabucasa.com/) then your Cloud API URL can be found by looking up your URL via `HA -> Settings -> Home Assistant Cloud -> Remote Control -> Nabu Casa URL` and don't forget to add `/api` to the end of the copied string. +If you are using [Nabu Casa](https://www.nabucasa.com/) then your Cloud API URL can be found by looking up your URL via `HA -> Settings -> HomeAssistant Cloud -> Remote Control -> Nabu Casa URL` and don't forget to add `/api` to the end of the copied string. ![Nabu Casa Remote Control](images/Nabu_Casa_Remote_Control.png) @@ -255,19 +255,34 @@ Unfortunately the Settings dialogue box in the Garmin IQ application "times out" 1. Copy and paste your API key you've just created into the top field. -2. Add the URL for your Home Assistant API, e.g. `https:///api`. (No trailing slash `/`` character as one gets appended when creating the URL and you do not want two.) +2. Add the URL for your HomeAssistant API, e.g. `https:///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:///local/garmin/.json`. -You should now have a working application on your watch and be able to operate your Home Assistant devices for as long as your watch is within Bluetooth range of your phone. +You should now have a working application on your watch and be able to operate your HomeAssistant devices for as long as your watch is within Bluetooth range of your phone. -You may choose to cache your menu definition on your device in order to reduce the delay in showing the menu (as it saves waiting for an HTTP GET request). If you use this option you need to be aware of hwo updates to the menu are managed. You may either: +### Changes to the (JSON) Dashboard Definition & Caching + +Without caching enabled, when you change the JSON file defining your dashboard, you must exit the application and the reopen it. It only takes a matter of a few seconds to pick up the new definition. + +You may choose to cache your menu definition on your device in order to reduce the delay in showing the menu (as it saves waiting for an HTTP GET request). If you use this option you need to be aware of how updates to the menu are managed. You may either: 1. **Choose to have the cache cleared.** The toggle option below the cache option allows you to choose to refresh the cache the next time the application starts. Once the cache has been cleared, the application will reset this toggle for you, so you do not need to return to the settings to amend it. -2. **Let the application retrieve the menu after starting and setting up the switch states** (including evaluating [templates](examples/Templates.md)), and then verify you have the latest menu. If a newer menu is retrieved you will be notified via a 'toast' or blue screen for devices without a toast in their API. You will be prompted to restart the application in order to build the menu from this latest menu definition. There are no plans to make the menu definition update recreate the rendered menu items because it could change the selected item just as you action it, and because restarting is simple for the user and simpler for the code. +2. **Let the application retrieve the menu after starting and setting up the switch states** (including evaluating [templates](examples/Templates.md)), and then verify you have the latest menu. If a newer menu is retrieved you will be notified via a 'toast' or blue screen for devices without a toast in their API. You will be prompted to restart the application in order to build the menu from this latest menu definition. **This method has proven tricky in older devices with less memory.** Hence it can be turned off to avoid "Out of Memory" crashes. The application tries to protect against crashes by detecting insufficient memory and disabling the option (but note that this may require some tuning). Hence this option is off by default in case it causes a crash and new users are unaware of the potential cause. + +**Summary:** The two cache options are therefore distinct, the **first is a manual** forced refresh (the old way). The menu is refreshed on start up and no restart is required. The **second enables automatic checking** after starting and after presenting a usable menu with no extra delay but then any detected changes require a restart. + +Whilst it would be a smoother experience, there are no plans to make the menu definition update dynamically recreate the rendered menu items without a restart because: +1. Re-rendering the menu could change the selected item just as you action it. +2. V3.3 proved that older devices are now reaching their memory limits. If you have an old device with limited memory to spare you will probably find the App disables the automatic method for you. If your device crashes with this option turned on, best turn it off manually and let me know via a [Github issue](https://github.com/house-of-abbey/GarminHomeAssistant/issues). This will allow us to fine tune the conditions for insufficient memory. We will then ask you to perform a [small task to retrieve the debug information](https://developer.garmin.com/connect-iq/core-topics/debugging/) we need about memory usage. +3. Restarting is simple for the user and simpler for the code. + +### Vibration The application uses vibration to confirm the action has been requested, which is different to the 'toast' that appears to show the action has been successfully executed. This is enabled by default but may be turned off if you do not desire this behaviour. -The application timeout prevents the HomeAssistant App running on your watch when you have forgotten to close it. It prevents the refreshing of the menu statuses and therefore excessive wear on your battery level. For those users who prefer to keep the application open all the time for continuous use, they can reduce the battery wear by increasing the "poll delay". This inserts a user configurable number of seconds between each round of item update checks, hence reducing the API access activity. This also reduces the responsive of the statuses displayed when HA devices are switched externally, i.e. by another Home Assistant client, then the watch menu display will not update as quickly. Therefore if you only use the HomeAssistant App briefly now and then, keep this setting at the default 0 seconds. NB. To be clear, all items are updated then a configurable delay is inserted before the next round of all item updates. If your poll delay is greater than zero, then your application timeout should be set to zero, otherwise you will exit the application and negate the value of the poll delay function. +### Power Management + +The application timeout prevents the HomeAssistant App running on your watch when you have forgotten to close it. It prevents the refreshing of the menu statuses and therefore excessive wear on your battery level. For those users who prefer to keep the application open all the time for continuous use, they can reduce the battery wear by increasing the "poll delay". This inserts a user configurable number of seconds between each round of item update checks, hence reducing the API access activity. This also reduces the responsive of the statuses displayed when HA devices are switched externally, i.e. by another HomeAssistant client, then the watch menu display will not update as quickly. Therefore if you only use the HomeAssistant App briefly now and then, keep this setting at the default 0 seconds. NB. To be clear, all items are updated then a configurable delay is inserted before the next round of all item updates. If your poll delay is greater than zero, then your application timeout should be set to zero, otherwise you will exit the application and negate the value of the poll delay function. | Application Timeout | Poll Delay | Comment | |:-------------------:|:----------:|:--------| @@ -280,9 +295,13 @@ There is a second timeout value for confirmation views. This is intended for use The confirmation timeout is also used for the maximum time between clicks in the PIN confirmation dialog. The PIN confirmation provides a more secure alternative for toggling security-sensitive actions. +### Text Alignment + There is a toggle setting for "text alignment" that provides finer adjustment for right-to-left languages. Perhaps this could be made automatic based on device language? -The application and widget both include a background service to report your watch's battery level and charging status. You may enable a background service to report the battery level to your Home Assistant. This is not available over your Bluetooth connection like with other Bluetooth devices as Garmin did not implement it. This no longer requires any setup, and we offer this [trouble shooting](TroubleShooting.md#watch-battery-level-reporting) guide. The last field here is readonly and allows the user to copy & paste the Webhook ID setup by the application when required for this trouble shooting guide. +### Background Service + +The application and widget both include a background service to report your watch's battery level and charging status. You may enable a background service to report the battery level to your HomeAssistant. This is not available over your Bluetooth connection like with other Bluetooth devices as Garmin did not implement it. This no longer requires any setup, and we offer this [trouble shooting](TroubleShooting.md#watch-battery-level-reporting) guide. The last field here is readonly and allows the user to copy & paste the Webhook ID setup by the application when required for this trouble shooting guide. ## Tap Item Response @@ -290,11 +309,11 @@ Its obvious that a toggle menu item has been triggered as the visible switch cha -The application will display a 'toast' showing Home Assistant's friendly name of the triggered item. The toast will disappear after a short while if not dismissed by the user. N.B. There are reports that on the Forerunner 55 device, the toasts do not dissapear without manual intervention. On other devices like the Venu 2 the toast can take 15 seconds to dissappear if not dismissed. Unfortunately, there is no API call to change this behaviour. +The application will display a 'toast' showing HomeAssistant's friendly name of the triggered item. The toast will disappear after a short while if not dismissed by the user. N.B. There are reports that on the Forerunner 55 device, the toasts do not dissapear without manual intervention. On other devices like the Venu 2 the toast can take 15 seconds to dissappear if not dismissed. Unfortunately, there is no API call to change this behaviour. ## External Device Changes -Home Assistant will inevitably change the state of devices you are also controlling via your Garmin. The Garmin application does not maintain a web socket to listen for changes. Instead it must poll the Home Assistant API with your key. Therefore the application is not that responsive to changes. Instead there will be a delay of multiples of 100 ms per item whose status needs to be checked and amended. +HomeAssistant will inevitably change the state of devices you are also controlling via your Garmin. The Garmin application does not maintain a web socket to listen for changes. Instead it must poll the HomeAssistant API with your key. Therefore the application is not that responsive to changes. Instead there will be a delay of multiples of 100 ms per item whose status needs to be checked and amended. The per toggle item delay is caused by a queue of responses to web requests. The responses fill up a buffer and in early testing we observed [`Communications.BLE_QUEUE_FULL`](https://developer.garmin.com/connect-iq/api-docs/Toybox/Communications.html) response codes. For a Venu 2 Garmin watch an API call delay of 600 ms was found to be sustainable (500 ms was still too fast). The code now chains a sequence of updates, so as one finishes it invokes the next item's update. **The more items requiring a status update that you pack into your dashboard, the slower each individual item will be updated!** @@ -302,10 +321,6 @@ The thinking here is that the watch application will only ever be open briefly n To prevent excessive battery usage, set the application timeout in the settings. This will prevent you from leaving the application open and forgotten when not being used, and the polling mechanism will then cease, saving battery life. Again, the thinking here is that the watch application will only ever be open briefly not persistently, and hence not be a constant source of battery usage unless the [background service](BackgroundService.md) for sending any watch status is used aggressively fast. -## Changes to the (JSON) Dashboard Definition - -When you change the JSON file defining your dashboard, you must exit the application and the reopen it. It only takes a matter of a few seconds to pick up the new definition, but it is not automatic. *Don't forget* you may explicitly choose to clear your cached menu, or wait the application to discover your definition has changed and prompt you to restart. The application check only happens once after startup, rendering menu items and setting the menu item states. - ## Submitting Corrections for Translations Initially all text has been created in English, and a [Python script](https://github.com/house-of-abbey/GarminHomeAssistant/blob/main/translate.py) (Google Translate under the hood) has been used to create the first version of all translations. We have been pleased to accept better translations from native language speakers, *thank you*. If you would like to submit improved translations, our preference is you do so via a [Git pull request](https://github.com/house-of-abbey/GarminHomeAssistant/pulls). If you are not comfortable doing this, then just raise an issue and someone will eventually pick the request up. @@ -331,7 +346,7 @@ Check the latest unresolved [issues](https://github.com/house-of-abbey/GarminHom 1. There are some cases where the file format may be valid JSON, but invalid against the schema, and the failure to catch this error could cause the application to crash. Whilst we have taken care to manage many issues, there may still be cases that are uncaught. Please verify your JSON schema, see the [trouble shooting guide](TroubleShooting.md). -2. On some (old) devices (e.g. Vivoactive 3, Fenix 5s & Edge 520+), the menu does not update correctly to reflect changes in state effected by an external Home Assistant control. E.g. when the phone application changes the toggle status of a switch, the Garmin application does not reflect that change until the menu is touched or scrolled a little. This is a [known issue](https://forums.garmin.com/developer/connect-iq/i/bug-reports/menu2-doesn-t-allow-live-updates) already reported without a suggested software fix. +2. On some (old) devices (e.g. Vivoactive 3, Fenix 5s & Edge 520+), the menu does not update correctly to reflect changes in state effected by an external HomeAssistant control. E.g. when the phone application changes the toggle status of a switch, the Garmin application does not reflect that change until the menu is touched or scrolled a little. This is a [known issue](https://forums.garmin.com/developer/connect-iq/i/bug-reports/menu2-doesn-t-allow-live-updates) already reported without a suggested software fix. 3. The iPhone Connect IQ application has a bug in it we cannot be responsible for. Thanks to user [a_smart_hoome](https://community.home-assistant.io/u/a_smart_hoome) who worked the problem with the dropped Internet connection, see his explanation at https://community.home-assistant.io/t/home-assistant-app-for-garmin/637348/61 for details. Please complain to the Connect IQ application developers rather than us! @@ -343,10 +358,12 @@ Check the latest unresolved [issues](https://github.com/house-of-abbey/GarminHom 7. We are unable to support HTTP natively (without the workaround specified earlier). This is a limitation placed upon us by the Connect IQ API which for security reasons refuses to work with HTTP requests. There is nothing developers can do about this limitation. See the [Trouble Shooting](TroubleShooting.md#do-it-yourself-setup) guide for an example setup. We would appreciate it if users did not leave poor reviews for the lack of this feature which is beyond our control to fix. -8. There is a [bug in Garmin Express so that when you use that software to amend the application's settings](https://github.com/house-of-abbey/GarminHomeAssistant/issues/194), the page appears in a random language not of your choice. I would like to thank user [heviiguy](https://github.com/heviiguy) for his work researching the issue, leading to these references that indicate the authors of Garmin Home Assistant cannot resolve this issue as its a bug in Garmin Express that Garmin are refusing to believe exists! See these pages for details: +8. There is a [bug in Garmin Express so that when you use that software to amend the application's settings](https://github.com/house-of-abbey/GarminHomeAssistant/issues/194), the page appears in a random language not of your choice. I would like to thank user [heviiguy](https://github.com/heviiguy) for his work researching the issue, leading to these references that indicate the authors of Garmin HomeAssistant cannot resolve this issue as its a bug in Garmin Express that Garmin are refusing to believe exists! See these pages for details: - [Garmin Express - Wrong Language](https://forums.garmin.com/developer/connect-iq/i/bug-reports/garmin-express---wrong-language) - [Incorrect language displayed for custom data fields](https://forums.garmin.com/developer/connect-iq/f/discussion/388137/incorrect-language-displayed-for-custom-data-fields) +9. When using Wi-Fi or LTE to toggle a light, the `toggle` will fail when the default or current state of the application's menu does not match the state of the light. The same applies to a cover or other thing that can be toggled. This is because the application is unable to initialise the menu with the current state without Bluetooth. Hence the Wi-Fi/LTE functionality is best used with `tap` items only. + # Authors & Contributors For an up to date list of all authors and contributors, please check the [contributor's page](https://github.com/house-of-abbey/GarminHomeAssistant/graphs/contributors). Thank you all for improving this application. diff --git a/TroubleShooting.md b/TroubleShooting.md index fed5005..d01ee62 100644 --- a/TroubleShooting.md +++ b/TroubleShooting.md @@ -6,8 +6,8 @@ Before [raising an issue](https://github.com/house-of-abbey/GarminHomeAssistant/issues) about a possible bug, _please, please_ check your JSON is compliant with both the JSON format and our schema. To do this you have options. The first is what we use. -1. **Best!** Use the GarminHomeAssistant [Web-based Editor](https://house-of-abbey.github.io/GarminHomeAssistant/web/) which includes `entity` and `service` name completion and validation by fetching data from your own Home Assistant instance. _Pretty nifty eh?_ The other methods listed below do not add this convenience and checking. -2. Use the [Studio Code Server](https://community.home-assistant.io/t/home-assistant-community-add-on-visual-studio-code/107863) addon for Home Assistant. You can then edit your JSON file in place. +1. **Best!** Use the GarminHomeAssistant [Web-based Editor](https://house-of-abbey.github.io/GarminHomeAssistant/web/) which includes `entity` and `service` name completion and validation by fetching data from your own HomeAssistant instance. _Pretty nifty eh?_ The other methods listed below do not add this convenience and checking. +2. Use the [Studio Code Server](https://community.home-assistant.io/t/home-assistant-community-add-on-visual-studio-code/107863) addon for HomeAssistant. You can then edit your JSON file in place. 3. Locally installed VSCode, or if not installed, try 4. The on-line version at https://vscode.dev/, which works really well. Paste in your JSON (and change the file type to JSON if not saving), it will then verify your file format and schema for you, highlighting any errors for you to fix. @@ -23,7 +23,7 @@ With either of the following setups, there are inevitably some problems along th ### Nabu Casa Setup -You can purchase cloud-based access to your Home Assistant from [Nabu Casa](https://www.nabucasa.com/), and then your setup will look something like this. +You can purchase cloud-based access to your HomeAssistant from [Nabu Casa](https://www.nabucasa.com/), and then your setup will look something like this. ![Nabu Casa Setup](images/nabu_casa_setup.png) @@ -67,9 +67,9 @@ This URL is very simple, you should be able to read the contents returned in a s The browser page should then display the JSON string you saved to the file on the web server. The point is this is a simple HTTP GET request with no bells and whistles. -The menu configuration can be hosted anywhere, it does not have to be on the Home Assistant web server. Just as long as it is reachable from your phone from which you Bluetooth connect to your watch, or you watch if it has direct Internet access. +The menu configuration can be hosted anywhere, it does not have to be on the HomeAssistant web server. Just as long as it is reachable from your phone from which you Bluetooth connect to your watch, or you watch if it has direct Internet access. -### Home Assistant API URL +### HomeAssistant API URL This is slightly trickier owning to the need to supply the API key. Here are three ways you can test your API URL is correctly configured. If successful, each of these should produce a JSON string output looking like: @@ -124,8 +124,8 @@ There's an online way of testing the API URL too, thanks to [REQBIN](https://req With thanks to [@ziceva](https://github.com/ziceva) for solving this problem. The symptoms are: 1. Using an API URL with SSL (HTTPS), the [web-based editor](https://house-of-abbey.github.io/GarminHomeAssistant/web/) running in a browser on the same phone running Garmin Connect works well. -2. The exact same configuration is set in the Garmin Home Assistant application. -3. The Garmin Home Assistant application reports: +2. The exact same configuration is set in the Garmin HomeAssistant application. +3. The Garmin HomeAssistant application reports: ``` API: not available Menu: not available @@ -153,7 +153,7 @@ To verify if you have this issue you can use a tool like [SSL Shoppers's SSL Che ## Watch Battery Level Reporting -For this you will need to have already got the main application or widget working with a menu in order to prove that the API calls are successful. We have proven this works with both our home brew infrastructure as well as Nabu Casa. Now with a script similar to one of the following two, you should be able to fake the watch API call and verify receipt by Home Assistant. +For this you will need to have already got the main application or widget working with a menu in order to prove that the API calls are successful. We have proven this works with both our home brew infrastructure as well as Nabu Casa. Now with a script similar to one of the following two, you should be able to fake the watch API call and verify receipt by HomeAssistant. #### Battery: Linux, MacOS, UNIX, Cygwin etc @@ -315,7 +315,7 @@ JSON for copy & paste: ![No JSON](images/NoJson.png) -When the application persists in reporting "No JSON returned from HTTP request." this might be due to a mismatch between the Webhook ID and the device settings on the Home Assistant server. We have discovered that the Webhook ID is required for Home Assistant API calls with templates in order to work in a non-privileged account. The application options include the ability to clear the Webhook ID in the application forcing a new one to be set up. This should prevent the above error being shown on startup. +When the application persists in reporting "No JSON returned from HTTP request." this might be due to a mismatch between the Webhook ID and the device settings on the HomeAssistant server. We have discovered that the Webhook ID is required for HomeAssistant API calls with templates in order to work in a non-privileged account. The application options include the ability to clear the Webhook ID in the application forcing a new one to be set up. This should prevent the above error being shown on startup. Look for this option in the application settings: @@ -323,7 +323,7 @@ Look for this option in the application settings: # Debug Logs -As a desperate measure to assist with debugging the Home Assistant Application, you might be asked to send the authors a debug log. +As a desperate measure to assist with debugging the HomeAssistant Application, you might be asked to send the authors a debug log. ![How to find the debug log file](images/debug_log_location.png) diff --git a/Wi-Fi.md b/Wi-Fi.md index ef49760..dd4ca3a 100644 --- a/Wi-Fi.md +++ b/Wi-Fi.md @@ -2,7 +2,7 @@ # Wi-Fi & LTE -Many watches now include the ability to synchronise data over Wi-Fi or event LTE in addition to Bluetooth. This gives users of this application the expectation that they should be able to operate Home Assistant devices from their watch without Bluetooth and hence their phone (that they left out of contact distance). The whole point of Bluetooth after all is that it is [low power](https://en.wikipedia.org/wiki/Bluetooth#Uses). Using Wi-Fi and LTE are power hungry and therefore not something that can be left on continuously in a small device. The watch function that uses Wi-Fi & LTE is the ability to 'synchronise', e.g. activity data (FIT files) and application updates. This function then has a limited period of time for which radio is active. Neither Wi-Fi nor LTE are "always on" like Bluetooth. +Many watches now include the ability to synchronise data over Wi-Fi or event LTE in addition to Bluetooth. This gives users of this application the expectation that they should be able to operate HomeAssistant devices from their watch without Bluetooth and hence their phone (that they left out of contact distance). The whole point of Bluetooth after all is that it is [low power](https://en.wikipedia.org/wiki/Bluetooth#Uses). Using Wi-Fi and LTE are power hungry and therefore not something that can be left on continuously in a small device. The watch function that uses Wi-Fi & LTE is the ability to 'synchronise', e.g. activity data (FIT files) and application updates. This function then has a limited period of time for which radio is active. Neither Wi-Fi nor LTE are "always on" like Bluetooth. With version 3.0 onwards the application now includes the ability to temporarily turn on Wi-Fi or LTE in order to perform a task on the watch. To do this, the "synchronise" function of the Connect IQ SDK has been cleverly hijacked. This appears to be a highly sought after solution from several users as **it allows the watch to operate when out of range of the associated phone**. diff --git a/compile_sim.cmd b/compile_sim.cmd index 9c9cfc1..43c0a88 100644 --- a/compile_sim.cmd +++ b/compile_sim.cmd @@ -93,7 +93,7 @@ if not exist %DEST% ( ) echo. -echo Starting compilation for simulation on %DEVICE%. +echo Starting compilation for simulation on '%DEVICE%'. echo. rem call %SDK_PATH%\connectiq.bat @@ -109,8 +109,9 @@ rem Compile PRG for a single device for side loading --jungles %SRC%\%JUNGLE% ^ --private-key %SRC%\..\developer_key ^ --device %DEVICE%_sim ^ - --warn ^ - --release + --warn + +rem --release if %ERRORLEVEL% equ 0 ( %SDK_PATH%\monkeydo.bat %SRC%\bin\HomeAssistant.prg %DEVICE% diff --git a/examples/Actions.md b/examples/Actions.md index 1df7942..0a1f546 100644 --- a/examples/Actions.md +++ b/examples/Actions.md @@ -75,7 +75,7 @@ Note that for notify events, you _must_ not supply an `entity_id` or the API cal > [!IMPORTANT] > Be careful with the value of the `service` field. -Note that the `service` field will need to be a locally custom `script.` as soon as any `data` fields are populated and not something more generic like `script.turn_on`. If the `service` field is wrong, the application will fail with a [`Communications.INVALID_HTTP_BODY_IN_NETWORK_RESPONSE`](https://developer.garmin.com/connect-iq/api-docs/Toybox/Communications.html) error in the response from your Home Assistant and show the error message as _"No JSON returned from HTTP request"_ on your device. In the [web-based editor](https://house-of-abbey.github.io/GarminHomeAssistant/web/) you can use the standard developer tools to observe an `HTTP 400` error which the application does not see. Here we are limited by the [Garmin Connect IQ](https://developer.garmin.com/connect-iq/overview/) software development kit (SDK). We do not have enough information at the point of execution in the application to determine the cause of the error. Nor is there an immediately obvious way of identifying this issue using the JSON schema checks. +Note that the `service` field will need to be a locally custom `script.` 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 diff --git a/examples/Templates.md b/examples/Templates.md index b488125..92132e0 100644 --- a/examples/Templates.md +++ b/examples/Templates.md @@ -5,7 +5,7 @@ In order to provide the most functionality possible the content of the menu item comes from a user-defined template (i.e. you generate your own text). This allows you to do some pretty cool things. It also makes the configuration a bit more complicated. This page will help you understand how to use templates. - In this file anything between `<` and `>` is a placeholder. Replace it with the appropriate value. -- [Jinja2](https://palletsprojects.com/p/jinja/) syntax is used by Home Assistant [Templates](https://www.home-assistant.io/docs/configuration/templating/). Templates are used to dynamically insert values into the content. The syntax includes: +- [Jinja2](https://palletsprojects.com/p/jinja/) syntax is used by HomeAssistant [Templates](https://www.home-assistant.io/docs/configuration/templating/). Templates are used to dynamically insert values into the content. The syntax includes: - `{%` ... `%}` for Statements - `{{` ... `}}` for Expressions to print to the template output - `{#` ... `#}` for Comments not included in the template output diff --git a/images/GarminHomeAssistantSettings.png b/images/GarminHomeAssistantSettings.png index 9a70780..e9a1984 100644 Binary files a/images/GarminHomeAssistantSettings.png and b/images/GarminHomeAssistantSettings.png differ diff --git a/resources-ara/strings/strings.xml b/resources-ara/strings/strings.xml index a4263e5..8454fb2 100644 --- a/resources-ara/strings/strings.xml +++ b/resources-ara/strings/strings.xml @@ -32,6 +32,7 @@ قائمة طعام ذاكرة محدثة القائمة ، إعادة التشغيل. + تحديثات القائمة معطل. لا مفتاح API في إعدادات التطبيق. لا عنوان URL API في إعدادات التطبيق. لا يوجد عنوان URL للتكوين في إعدادات التطبيق. @@ -63,6 +64,7 @@ عنوان URL لتكوين القائمة (JSON). هل يجب أن يقوم تطبيق ذاكرة التخزين المؤقت لتكوين القائمة؟ هل يجب على التطبيق مسح ذاكرة التخزين المؤقت الموجودة في المرة القادمة التي يتم فيها بدء تشغيلها؟ + تحقق من تحديثات القائمة عند بدء التطبيق؟ ملاحظة: يجب تمكين تخزين المؤقت القائمة. قد يتسبب هذا الإعداد في تعطل الأجهزة القديمة ذات الذاكرة الأقل. تمكين تنفيذ الأوامر على Wi-Fi/LTE. هل يجب أن يقدم التطبيق ملاحظات عبر الاهتزازات؟ مهلة في ثوان. الخروج من التطبيق بعد هذه الفترة من عدم النشاط لحفظ بطارية الجهاز. diff --git a/resources-bul/strings/strings.xml b/resources-bul/strings/strings.xml index 730eb35..a0bab32 100644 --- a/resources-bul/strings/strings.xml +++ b/resources-bul/strings/strings.xml @@ -32,6 +32,7 @@ Меню Памет Менюто актуализирано, рестартиране. + Актуализации на менюто деактивирани. Няма ключ за API в настройките на приложението. Няма URL адрес на API в настройките на приложението. Няма URL адрес на конфигурация в настройките на приложението. @@ -63,6 +64,7 @@ URL за конфигуриране на менюто (JSON). Трябва ли приложението да кешира конфигурацията на менюто? Трябва ли приложението да изчисти съществуващия кеш следващия път, когато е стартиран? + Проверете за актуализации на менюто за стартиране на приложението? ЗАБЕЛЕЖКА: кеширането на менюто трябва да бъде активирано. Тази настройка може да доведе до сриване на по -старите устройства с по -малко памет. Активиране на изпълнение на команди над Wi-Fi/LTE. Трябва ли приложението да предоставя обратна връзка чрез вибрации? Време за изчакване за секунди. Излезте от приложението след този период на бездействие, за да запазите батерията на устройството. diff --git a/resources-ces/strings/strings.xml b/resources-ces/strings/strings.xml index e0a0817..fd7322f 100644 --- a/resources-ces/strings/strings.xml +++ b/resources-ces/strings/strings.xml @@ -32,6 +32,7 @@ Menu Paměť Aktualizováno nabídka, restartujte. + Aktualizace nabídky zakázáno. Žádný klíč API v nastavení aplikace. Žádná URL API v nastavení aplikace. V nastavení aplikace není žádná konfigurační adresa URL. @@ -63,6 +64,7 @@ URL pro konfiguraci nabídky (JSON). Měla by aplikace ukládat konfiguraci nabídky? Měla by aplikace vymazat stávající mezipaměť příště, až bude spuštěna? + Zkontrolujte aktualizace nabídky při zahájení aplikace? POZNÁMKA: Musí být povoleno ukládání do mezipaměti nabídky. Toto nastavení může způsobit, že starší zařízení s menší pamětí dojde. Povolit provádění příkazů přes Wi-Fi/LTE. Měla by aplikace poskytovat zpětnou vazbu prostřednictvím vibrací? Timeout během několika sekund. Po tomto období nečinnosti uložte aplikaci k uložení baterie zařízení. diff --git a/resources-dan/strings/strings.xml b/resources-dan/strings/strings.xml index d83002b..ee4c36d 100644 --- a/resources-dan/strings/strings.xml +++ b/resources-dan/strings/strings.xml @@ -32,6 +32,7 @@ Menu Hukommelse Menu opdateret, genstart. + Menuopdateringer deaktiveret. Ingen API -nøgle i applikationsindstillingerne. Ingen API -URL i applikationsindstillingerne. Ingen konfigurations -URL i applikationsindstillingerne. @@ -63,6 +64,7 @@ URL til menukonfiguration (JSON). Skal applikationscache menuen Konfiguration? Bør applikationen rydde den eksisterende cache næste gang den startes? + 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. Aktivér udførelse af kommandoer over Wi-Fi/LTE. Bør applikationen give feedback via vibrationer? Timeout på få sekunder. Afslut applikationen efter denne periode med inaktivitet for at gemme enhedsbatteriet. diff --git a/resources-deu/strings/strings.xml b/resources-deu/strings/strings.xml index 5099be9..c4e24d9 100644 --- a/resources-deu/strings/strings.xml +++ b/resources-deu/strings/strings.xml @@ -32,6 +32,7 @@ Menü Speicher Menü aktualisiert, neu starten. + Menü -Updates deaktiviert. Kein API-Schlüssel in den App-Einstellungen hinterlegt. Keine API-URL in den App-Einstellungen hinterlegt. Keine Menükonfigurations-URL (JSON) in den App-Einstellungen hinterlegt. @@ -63,6 +64,7 @@ URL für die Menükonfiguration (JSON). Soll die App die Menükonfiguration cachen? Soll die Anwendung beim nächsten Start den vorhandenen Cache löschen? + Ü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. Befehlsausführung über WLAN/LTE aktivieren. Soll die App Rückmeldung per Vibration geben? Timeout in Sekunden. Beendet die App nach dieser Inaktivitätszeit, um Akku zu sparen. diff --git a/resources-dut/strings/strings.xml b/resources-dut/strings/strings.xml index ab0ec73..5c5560a 100644 --- a/resources-dut/strings/strings.xml +++ b/resources-dut/strings/strings.xml @@ -32,6 +32,7 @@ Menu Geheugen Menu bijgewerkt, opnieuw opstarten. + Menu -updates uitgeschakeld. Geen API -toets in de toepassingsinstellingen. Geen API -URL in de toepassingsinstellingen. Geen configuratie -URL in de toepassingsinstellingen. @@ -63,6 +64,7 @@ URL voor menuconfiguratie (JSON). Moet de toepassingscache de menu -configuratie? Moet de toepassing de bestaande cache wissen de volgende keer dat deze wordt gestart? + Controleer op menu -updates over het starten van de applicatie? Opmerking: menu Caching moet worden ingeschakeld. Deze instelling kan ervoor zorgen dat oudere apparaten met minder geheugen crashen. Schakel opdrachten uit via Wi-Fi/LTE. Moet de applicatie feedback geven via trillingen? Time -out in seconden. Verlaat de toepassing na deze periode van inactiviteit om de apparaatbatterij op te slaan. diff --git a/resources-est/strings/strings.xml b/resources-est/strings/strings.xml index 67b794b..7d86b24 100644 --- a/resources-est/strings/strings.xml +++ b/resources-est/strings/strings.xml @@ -32,6 +32,7 @@ Menüü Mälu Menüü värskendatud, taaskäivitage. + Menüüvärskendused on keelatud. Rakenduse seadetes pole API -klahvi. Rakenduse seadetes pole API URL -i. Rakenduse sätetes pole konfiguratsiooni URL -i. @@ -63,6 +64,7 @@ URL menüü konfiguratsiooni jaoks (JSON). Kas rakenduse vahemälu peaks menüü konfiguratsiooni vahemälu vahemälu vahemälu vahemälu vahemälu vahemälu vahemälu vahemälu Kas rakendus peaks olemasoleva vahemälu järgmine kord alustama? + Kontrollige rakenduse käivitamise menüüuuendusi? MÄRKUS. Menüü vahemällu salvestamine peab olema lubatud. See säte võib põhjustada vanemate seadmete, mille mälu on vähem. Luba käskude täitmine Wi-Fi/LTE kaudu. Kas rakendus peaks vibratsiooni kaudu tagasisidet andma? Aegumine sekunditega. Pärast seda tegevusetuse perioodi seade aku salvestamiseks väljuge rakendusest. diff --git a/resources-fin/strings/strings.xml b/resources-fin/strings/strings.xml index 1d9eb42..dc159c2 100644 --- a/resources-fin/strings/strings.xml +++ b/resources-fin/strings/strings.xml @@ -32,6 +32,7 @@ Valikko Muisti Valikko päivitetty, käynnistä uudelleen. + Valikkopäivitykset poistettu käytöstä. Ei sovellusliittymää avainta sovellusasetuksissa. Ei sovellus -URL -osoitetta sovellusasetuksissa. Ei määritys -URL -osoitetta sovellusasetuksissa. @@ -63,6 +64,7 @@ Valikkokokoonpanon URL (JSON). Pitäisikö sovelluksen välimuistiin valikon kokoonpano? Pitäisikö sovelluksen tyhjentää olemassa oleva välimuisti seuraavalla kerralla? + Tarkista valikkopäivitykset sovelluksen käynnistyksestä? HUOMAUTUS: Valikon välimuisti on otettava käyttöön. Tämä asetus voi aiheuttaa vanhempia laitteita, joissa on vähemmän muistia kaatumiseen. Ota komentojen suorittaminen käyttöön Wi-Fi/LTE: n kautta. Pitäisikö sovelluksen antaa palautetta värähtelyjen kautta? Aikakatkaisu sekunneissa. Poistu sovelluksesta tämän toimettomuuden jälkeen laitteen akun tallentamiseksi. diff --git a/resources-fre/strings/strings.xml b/resources-fre/strings/strings.xml index 2d1b7fe..a1e4706 100644 --- a/resources-fre/strings/strings.xml +++ b/resources-fre/strings/strings.xml @@ -32,6 +32,7 @@ Menu Mémoire Menu mis à jour, redémarrer. + MENU MISE À JOUR Désactivé. Aucune clé API dans les paramètres de l'application. Aucune URL de l'API dans les paramètres de l'application. Aucune URL de configuration dans les paramètres de l'application. @@ -63,6 +64,7 @@ URL pour la configuration du menu (JSON). L'application devrait-elle mettre en cache la configuration du menu? L'application devrait-elle effacer le cache existant la prochaine fois qu'il sera démarré? + Vérifiez les mises à jour du menu au démarrage de l'application? Remarque: la mise en cache de menu doit être activée. Ce paramètre peut entraîner un écrasement des appareils plus anciens avec moins de mémoire. Activer l'exécution des commandes sur Wi-Fi / LTE. L'application devrait-elle fournir des commentaires via des vibrations? Timeout en quelques secondes. Quittez l'application après cette période d'inactivité pour enregistrer la batterie de l'appareil. diff --git a/resources-gre/strings/strings.xml b/resources-gre/strings/strings.xml index cedaac7..61d53ec 100644 --- a/resources-gre/strings/strings.xml +++ b/resources-gre/strings/strings.xml @@ -32,6 +32,7 @@ Μενού Μνήμη Ενημερώθηκε μενού, επανεκκίνηση. + Οι ενημερώσεις μενού απενεργοποιούνται. Δεν υπάρχει κλειδί API στις ρυθμίσεις εφαρμογής. Δεν υπάρχει διεύθυνση URL API στις ρυθμίσεις εφαρμογής. Χωρίς διευθύνσεις διαμόρφωσης στις ρυθμίσεις εφαρμογής. @@ -63,6 +64,7 @@ URL για διαμόρφωση μενού (JSON). Πρέπει η προσωρινή μνήμη εφαρμογής τη διαμόρφωση μενού; Πρέπει η εφαρμογή να διαγράψει την υπάρχουσα μνήμη cache την επόμενη φορά που θα ξεκινήσει; + Ελέγξτε για ενημερώσεις μενού κατά την έναρξη της εφαρμογής; ΣΗΜΕΙΩΣΗ: Η προσωρινή αποθήκευση μενού πρέπει να είναι ενεργοποιημένη. Αυτή η ρύθμιση μπορεί να προκαλέσει παλαιότερες συσκευές με λιγότερη μνήμη για συντριβή. Ενεργοποιήστε τις εντολές εκτέλεσης μέσω Wi-Fi/LTE. Πρέπει η εφαρμογή να παρέχει ανατροφοδότηση μέσω δονήσεων; Χρονικό όριο σε δευτερόλεπτα. Βγείτε από την εφαρμογή μετά από αυτήν την περίοδο αδράνειας για να αποθηκεύσετε τη μπαταρία της συσκευής. diff --git a/resources-heb/strings/strings.xml b/resources-heb/strings/strings.xml index 3eb50b2..582778a 100644 --- a/resources-heb/strings/strings.xml +++ b/resources-heb/strings/strings.xml @@ -32,6 +32,7 @@ תַפרִיט זֵכֶר מעודכן בתפריט, הפעל מחדש. + עדכוני תפריט מושבתים. אין מפתח API בהגדרות היישום. אין כתובת URL בהגדרות היישום. אין כתובת אתר תצורה בהגדרות היישום. @@ -63,6 +64,7 @@ כתובת אתר לתצורת תפריט (JSON). האם על היישום למנוע את תצורת התפריט? האם על היישום לנקות את המטמון הקיים בפעם הבאה שהוא מתחיל? + בדוק אם יש עדכוני תפריט על התחלת היישום? הערה: יש לאפשר מטמון בתפריט. הגדרה זו עלולה לגרום למכשירים ישנים עם פחות זיכרון להתרסק. אפשר לבצע פקודות דרך Wi-Fi/LTE. האם על היישום לספק משוב באמצעות תנודות? פסק זמן בשניות. צא מהיישום לאחר תקופת חוסר פעילות זו כדי לחסוך את סוללת ההתקן. diff --git a/resources-hrv/strings/strings.xml b/resources-hrv/strings/strings.xml index 53cb29a..5b48cb8 100644 --- a/resources-hrv/strings/strings.xml +++ b/resources-hrv/strings/strings.xml @@ -32,6 +32,7 @@ Jelovnik Memorija Izbornik Ažurirano, ponovno pokrenite. + Ažuriranja izbornika onemogućena. Nema API ključa u postavkama aplikacije. Nema URL -a API -ja u postavkama aplikacije. Nema URL -a konfiguracije u postavkama aplikacije. @@ -55,7 +56,7 @@ Izvršite preko Wi-Fi/LTE? Slanje kod kuće pomoćnika. Nema primljenih podataka. - + Odaberite ... Ključ API -ja za HomeAssistant. Dugotrajni pristupni token. @@ -63,6 +64,7 @@ URL za konfiguraciju izbornika (JSON). Treba li aplikacija predmemorirati konfiguraciju izbornika? Treba li aplikacija očistiti postojeću predmemoriju sljedeći put kad se pokrene? + Provjerite ažuriranja izbornika o pokretanju aplikacije? Napomena: Mora biti omogućeno predmemoriranje izbornika. Ova postavka može uzrokovati da se stariji uređaji s manje memorije sruše. Omogući izvršavanje naredbi preko Wi-Fi/LTE. Treba li aplikacija davati povratne informacije putem vibracija? Timeout u sekundi. Izađite iz aplikacije nakon ovog razdoblja neaktivnosti kako biste uštedjeli bateriju uređaja. diff --git a/resources-hun/strings/strings.xml b/resources-hun/strings/strings.xml index af27d13..ea4273c 100644 --- a/resources-hun/strings/strings.xml +++ b/resources-hun/strings/strings.xml @@ -32,6 +32,7 @@ Menü Emlékezet A menü frissítve, indítsa újra. + A menüfrissítések letiltva. Nincs API -kulcs az alkalmazásbeállításokban. Nincs API URL az alkalmazás beállításaiban. Nincs konfigurációs URL az alkalmazásbeállításokban. @@ -63,6 +64,7 @@ URL a menükonfigurációhoz (JSON). Az alkalmazásnak gyorsítótáraznia kell a menükonfigurációt? Az alkalmazásnak törölnie kell -e a meglévő gyorsítótárat a következő indításkor? + Ellenőrizze a menüfrissítéseket az alkalmazás indításakor? MEGJEGYZÉS: A menü gyorsítótárazását engedélyezni kell. Ez a beállítás a kevesebb memóriával rendelkező régebbi eszközök összeomlását okozhatja. Engedélyezze a parancsok végrehajtási végrehajtását a Wi-Fi/LTE-n keresztül. Az alkalmazásnak visszacsatolást kell adnia a rezgések révén? Időtúllépés másodpercek alatt. Az eszköz akkumulátorának mentése érdekében kilépjen az alkalmazásból az inaktivitás után. diff --git a/resources-ind/strings/strings.xml b/resources-ind/strings/strings.xml index 0c2b72a..faf3adf 100644 --- a/resources-ind/strings/strings.xml +++ b/resources-ind/strings/strings.xml @@ -32,6 +32,7 @@ Menu Ingatan Menu diperbarui, restart. + Pembaruan menu dinonaktifkan. Tidak ada kunci API di pengaturan aplikasi. Tidak ada URL API di pengaturan aplikasi. Tidak ada URL konfigurasi di pengaturan aplikasi. @@ -63,6 +64,7 @@ URL untuk Konfigurasi Menu (JSON). Haruskah Aplikasi Menyimpan Konfigurasi Menu? Haruskah aplikasi menghapus cache yang ada lain kali dimulai? + Periksa pembaruan menu pada aplikasi mulai? Catatan: Caching menu harus diaktifkan. Pengaturan ini dapat menyebabkan perangkat yang lebih tua dengan lebih sedikit memori untuk macet. Aktifkan Perintah yang Mengeksekusi melalui Wi-Fi/LTE. Haruskah aplikasi memberikan umpan balik melalui getaran? Batas waktu dalam hitungan detik. Keluar dari aplikasi setelah periode tidak aktif ini untuk menyimpan baterai perangkat. diff --git a/resources-ita/strings/strings.xml b/resources-ita/strings/strings.xml index a4d5b48..991d15f 100644 --- a/resources-ita/strings/strings.xml +++ b/resources-ita/strings/strings.xml @@ -32,6 +32,7 @@ Menu Memoria Menu aggiornato, riavvio. + Aggiornamenti di menu disabilitati. Nessuna chiave API nelle impostazioni dell'applicazione. Nessun URL API nelle impostazioni dell'applicazione. Nessun URL di configurazione nelle impostazioni dell'applicazione. @@ -63,6 +64,7 @@ URL per la configurazione del menu (JSON). L'applicazione dovrebbe memorizzare la cache della configurazione del menu? L'applicazione dovrebbe cancellare la cache esistente la prossima volta che viene avviata? + Controllare gli aggiornamenti del menu all'inizio dell'applicazione? NOTA: la memorizzazione della memorizzazione nella cache dei menu deve essere abilitata. Questa impostazione può causare crash di dispositivi più vecchi con meno memoria. Abilita l'esecuzione dei comandi su Wi-Fi/LTE. L'applicazione dovrebbe fornire feedback tramite vibrazioni? Timeout in secondi. Esci dall'applicazione dopo questo periodo di inattività per salvare la batteria del dispositivo. diff --git a/resources-jpn/strings/strings.xml b/resources-jpn/strings/strings.xml index a8e0f68..0b6a6f3 100644 --- a/resources-jpn/strings/strings.xml +++ b/resources-jpn/strings/strings.xml @@ -32,6 +32,7 @@ メニュー メモリ メニューの更新、再起動。 + メニューの更新は無効です。 アプリケーション設定にAPIキーはありません。 アプリケーション設定にAPI URLはありません。 アプリケーション設定に構成URLはありません。 @@ -63,6 +64,7 @@ メニュー構成用のURL（JSON）。 アプリケーションはメニュー構成をキャッシュする必要がありますか？ 次回開始時にアプリケーションが既存のキャッシュをクリアする必要がありますか？ + アプリケーションの開始に関するメニューの更新を確認しますか？注：メニューキャッシングを有効にする必要があります。この設定により、メモリが少ない古いデバイスがクラッシュする可能性があります。 Wi-Fi/LTEを介してコマンドを実行できるようにします。 アプリケーションは振動を介してフィードバックを提供する必要がありますか？ 数秒でタイムアウト。デバイスバッテリーを保存するために、この不活性期間の後にアプリケーションを終了します。 diff --git a/resources-kor/strings/strings.xml b/resources-kor/strings/strings.xml index 0a840d3..0c91175 100644 --- a/resources-kor/strings/strings.xml +++ b/resources-kor/strings/strings.xml @@ -32,6 +32,7 @@ 메뉴 메모리 메뉴가 업데이트되고 다시 시작됩니다. + 메뉴 업데이트가 비활성화됩니다. 응용 프로그램 설정에 API 키가 없습니다. 응용 프로그램 설정에 API URL이 없습니다. 응용 프로그램 설정에 구성 URL이 없습니다. @@ -63,6 +64,7 @@ 메뉴 구성 (JSON) 용 URL. 응용 프로그램이 메뉴 구성을 캐시해야합니까? 다음에 시작될 때 응용 프로그램이 기존 캐시를 지우려면? + 애플리케이션 시작에서 메뉴 업데이트를 확인 하시겠습니까? 참고 : 메뉴 캐싱이 활성화되어야합니다.이 설정으로 인해 메모리가 적은 기존 장치가 충돌 할 수 있습니다. Wi-Fi/LTE를 통해 명령을 실행할 수 있습니다. 응용 프로그램이 진동을 통해 피드백을 제공해야합니까? 시간 초과 시간 초과. 장치 배터리를 저장하기 위해이 비활성 기간 후에 응용 프로그램을 종료하십시오. diff --git a/resources-lav/strings/strings.xml b/resources-lav/strings/strings.xml index f1bea72..496a245 100644 --- a/resources-lav/strings/strings.xml +++ b/resources-lav/strings/strings.xml @@ -32,6 +32,7 @@ Ēdienkarte Atmiņa Atjaunināta izvēlne, restartējiet. + Izvēlnes atjauninājumi ir atspējoti. Lietojumprogrammas iestatījumos nav API atslēgas. Lietojumprogrammu iestatījumos nav API URL. Lietojumprogrammas iestatījumos nav konfigurācijas URL. @@ -63,6 +64,7 @@ URL izvēlnes konfigurācijai (JSON). Vai lietojumprogrammai vajadzētu kešatmiņā izvēlnes konfigurāciju? Vai lietojumprogrammai vajadzētu notīrīt esošo kešatmiņu nākamreiz, kad tā tiks sākta? + Pārbaudiet izvēlnes atjauninājumus lietojumprogrammas sākumā? PIEZĪME: jābūt iespējotai izvēlnei kešatmiņā. Šis iestatījums var izraisīt vecākām ierīcēm ar mazāku atmiņu avāriju. Iespējot izpildīt komandas, izmantojot Wi-Fi/LTE. Vai lietojumprogrammai vajadzētu sniegt atgriezenisko saiti, izmantojot vibrācijas? Noildze sekundēs. Izejiet no lietojumprogrammas pēc šī bezdarbības perioda, lai saglabātu ierīces akumulatoru. diff --git a/resources-lit/strings/strings.xml b/resources-lit/strings/strings.xml index 9a7a864..8233b8c 100644 --- a/resources-lit/strings/strings.xml +++ b/resources-lit/strings/strings.xml @@ -32,6 +32,7 @@ Meniu Atmintis Meniu Atnaujinta, paleiskite iš naujo. + Meniu atnaujinimai išjungti. Nėra API rakto programos nustatymuose. Nėra API URL programos nustatymuose. Nėra konfigūracijos URL programos nustatymuose. @@ -63,6 +64,7 @@ URL meniu konfigūracijai (JSON). Ar programos talpykla turėtų talpinti meniu konfigūraciją? Ar programa turėtų išvalyti esamą talpyklą kitą kartą, kai ji bus paleista? + Patikrinkite, ar nėra meniu atnaujinimų, pradedant programą? PASTABA: Turi būti įjungtas meniu talpyklos talpykla. Šis nustatymas gali sukelti senesnius įrenginius, turinčius mažiau atminties. Įgalinti komandas vykdant „Wi-Fi“/LTE. Ar programa turėtų pateikti grįžtamąjį ryšį per vibracijas? Laikas per kelias sekundes. Išeikite iš programos po šio neveiklumo laikotarpio, kad išsaugotumėte įrenginio akumuliatorių. diff --git a/resources-nob/strings/strings.xml b/resources-nob/strings/strings.xml index 7c0eef7..6799b92 100644 --- a/resources-nob/strings/strings.xml +++ b/resources-nob/strings/strings.xml @@ -32,6 +32,7 @@ Meny Hukommelse Meny oppdatert, omstart. + Menyoppdateringer deaktivert. Ingen API -nøkkel i applikasjonsinnstillingene. Ingen API -URL i applikasjonsinnstillingene. Ingen konfigurasjons -URL i applikasjonsinnstillingene. @@ -63,6 +64,7 @@ URL for menykonfigurasjon (JSON). Bør applikasjonsbufferen menykonfigurasjonen? Bør applikasjonen fjerne den eksisterende cachen neste gang den startes? + Se etter menyoppdateringer på applikasjonsstart? MERKNAD: MENU -hurtigbufring må være aktivert. Denne innstillingen kan føre til at eldre enheter med mindre minne krasjer. Aktiver utførende kommandoer over Wi-Fi/LTE. Bør applikasjonen gi tilbakemelding via vibrasjoner? Tidsavbrudd på sekunder. Gå ut av applikasjonen etter denne perioden med inaktivitet for å lagre enhetsbatteriet. diff --git a/resources-pol/strings/strings.xml b/resources-pol/strings/strings.xml index 9e5fc4e..3d09800 100644 --- a/resources-pol/strings/strings.xml +++ b/resources-pol/strings/strings.xml @@ -32,6 +32,7 @@ Menu Pamięć Zaktualizowano menu, uruchom ponownie. + Zakładania menu wyłączone. Brak klucza API w ustawieniach aplikacji. Brak adresu URL API w ustawieniach aplikacji. Brak adresu URL konfiguracji w ustawieniach aplikacji. @@ -63,6 +64,7 @@ URL dla konfiguracji menu (JSON). Czy aplikacja powinna buforować konfigurację menu? Czy aplikacja powinna wyczyścić istniejącą pamięć podręczną następnym razem, gdy zostanie uruchomiona? + Sprawdź aktualizacje menu na temat uruchomienia aplikacji? Uwaga: Buforowanie menu musi być włączone. To ustawienie może spowodować awarię starszych urządzeń o mniejszej pamięci. Włącz wykonywanie poleceń przez Wi-Fi/LTE. Czy aplikacja powinna przekazywać informacje zwrotne za pośrednictwem wibracji? Limit czasu w sekundach. Wyjdź z aplikacji po tym okresie bezczynności, aby zapisać akumulator urządzenia. diff --git a/resources-por/strings/strings.xml b/resources-por/strings/strings.xml index 2aa29a5..21b1224 100644 --- a/resources-por/strings/strings.xml +++ b/resources-por/strings/strings.xml @@ -32,6 +32,7 @@ Menu Memória Menu Atualizado, reinicie. + Atualizações de menu desativadas. Nenhuma chave da API nas configurações do aplicativo. Nenhum URL da API nas configurações do aplicativo. Nenhum URL de configuração nas configurações do aplicativo. @@ -63,6 +64,7 @@ URL para configuração de menu (JSON). O aplicativo deve cache a configuração do menu? O aplicativo deve limpar o cache existente na próxima vez que for iniciado? + Verifique se há atualizações de menu no aplicativo Start? NOTA: O cache do menu deve ser ativado. Essa configuração pode causar dispositivos mais antigos com menos memória falha. Habilite os comandos de execução sobre Wi-Fi/LTE. O aplicativo deve fornecer feedback por meio de vibrações? Tempo limite em segundos. Saia do aplicativo após esse período de inatividade para salvar a bateria do dispositivo. diff --git a/resources-ron/strings/strings.xml b/resources-ron/strings/strings.xml index cd1f9e4..a36fcdf 100644 --- a/resources-ron/strings/strings.xml +++ b/resources-ron/strings/strings.xml @@ -32,6 +32,7 @@ Meniu Memorie Meniu actualizat, reporniți. + Actualizări de meniu dezactivate. Nici o cheie API în setările aplicației. Fără URL API în setările aplicației. Fără URL de configurare în setările aplicației. @@ -63,6 +64,7 @@ URL pentru configurația meniului (JSON). Aplicația cache ar trebui să fie configurația meniului? Aplicația ar trebui să șterge cache -ul existent data viitoare când va fi pornită? + Verificați actualizările meniului la pornirea aplicației? NOTĂ: Cachingul de meniu trebuie activat. Această setare poate provoca prăbușirea dispozitivelor mai vechi cu mai puțină memorie. Activați executarea comenzilor prin Wi-Fi/LTE. Aplicația ar trebui să ofere feedback prin vibrații? Timeout în câteva secunde. Ieșiți din aplicație după această perioadă de inactivitate pentru a economisi bateria dispozitivului. diff --git a/resources-slo/strings/strings.xml b/resources-slo/strings/strings.xml index b308dc6..8faa7e5 100644 --- a/resources-slo/strings/strings.xml +++ b/resources-slo/strings/strings.xml @@ -32,6 +32,7 @@ Ponuka Pamiatka Aktualizované menu, reštart. + Aktualizácie ponuky zakázané. V nastaveniach aplikácie chýba kľúč API V nastaveniach aplikácie chýba adresa URL rozhrania API V nastaveniach aplikácie chýba konfiguračná adresa URL @@ -63,6 +64,7 @@ URL pre konfiguráciu ponuky (JSON). Mala by sa aplikácia vyrovnávať konfiguráciu ponuky? Mala by aplikácia vymazať existujúcu vyrovnávaciu pamäť nabudúce, keď sa začne? + Skontrolujte aktualizácie ponuky na spustení aplikácie? Poznámka: Musí sa povoliť ukladanie do vyrovnávacej pamäte ponuky. Toto nastavenie môže spôsobiť staršie zariadenia s menšou pamäťou. Povoliť vykonávanie príkazov cez Wi-Fi/LTE. Mala by aplikácia poskytovať spätnú väzbu prostredníctvom vibrácií? Časový limit v sekundách. Opustite aplikáciu po tomto období nečinnosti, aby ste uložili batériu zariadenia. diff --git a/resources-slv/strings/strings.xml b/resources-slv/strings/strings.xml index eb74110..b830719 100644 --- a/resources-slv/strings/strings.xml +++ b/resources-slv/strings/strings.xml @@ -32,6 +32,7 @@ Meni Spomin Meni posodobljen, znova zaženite. + Posodobitve menija onemogočene. V nastavitvah aplikacije ni ključa API -ja. V nastavitvah aplikacije ni URL API -ja. V nastavitvah aplikacije ni URL konfiguracije. @@ -63,6 +64,7 @@ URL za konfiguracijo menija (JSON). Ali naj aplikacija predpomni konfiguracija menija? Ali bi morala aplikacija očistiti obstoječi predpomnilnik naslednjič, ko se začne? + Preverite, ali posodobitve menijev pri zagonu aplikacije? OPOMBA: Omogoči mora biti predpomnjenje menija. Ta nastavitev lahko povzroči, da se starejše naprave z manj pomnilnika zrušijo. Omogoči izvajanje ukazov prek Wi-Fi/LTE. Ali bi morala aplikacija posredovati povratne informacije z vibracijami? Časovna omejitev v nekaj sekundah. Po tem obdobju neaktivnosti zapustite aplikacijo, da shranite baterijo naprave. diff --git a/resources-spa/strings/strings.xml b/resources-spa/strings/strings.xml index 0e3714d..95fc324 100644 --- a/resources-spa/strings/strings.xml +++ b/resources-spa/strings/strings.xml @@ -32,6 +32,7 @@ Menú Memoria Menú actualizado, reiniciar. + Actualizaciones de menú deshabilitadas. No hay clave API en la configuración de la aplicación. No hay URL de API en la configuración de la aplicación. No hay URL de configuración en la configuración de la aplicación. @@ -63,6 +64,7 @@ URL para la configuración del menú (JSON). ¿Debería la aplicación almacenar en caché la configuración del menú? ¿Debería la aplicación borrar el caché existente la próxima vez que se inicie? + ¿Verifica las actualizaciones de menú en la aplicación Inicio? Nota: El almacenamiento en caché del menú debe estar habilitado. Esta configuración puede hacer que los dispositivos más antiguos con menos memoria se bloqueen. Habilite la ejecución de comandos sobre Wi-Fi/LTE. ¿Debería la aplicación proporcionar comentarios a través de vibraciones? Tiempo de espera en segundos. Salga de la aplicación después de este período de inactividad para guardar la batería del dispositivo. diff --git a/resources-swe/strings/strings.xml b/resources-swe/strings/strings.xml index eae5fc3..3fb9b80 100644 --- a/resources-swe/strings/strings.xml +++ b/resources-swe/strings/strings.xml @@ -32,6 +32,7 @@ Meny Minne Meny Uppdaterad, omstart. + Menyuppdateringar inaktiverade. Ingen API -nyckel i applikationsinställningarna. Ingen API -URL i applikationsinställningarna. Ingen konfigurations -URL i applikationsinställningarna. @@ -63,6 +64,7 @@ URL för menykonfiguration (JSON). Bör applikationen cache menykonfigurationen? Bör applikationen rensa den befintliga cachen nästa gång den startas? + Kontrollera om menyuppdateringar vid applikationsstart? Obs: Meny Caching måste vara aktiverad. Denna inställning kan orsaka äldre enheter med mindre minne att krascha. Aktivera körkommandon över Wi-Fi/LTE. Bör applikationen ge feedback via vibrationer? Timeout på några sekunder. Exit the application after this period of inactivity to save the device battery. diff --git a/resources-tha/strings/strings.xml b/resources-tha/strings/strings.xml index a36312c..d766e14 100644 --- a/resources-tha/strings/strings.xml +++ b/resources-tha/strings/strings.xml @@ -32,6 +32,7 @@ เมนู หน่วยความจำ อัปเดตเมนูรีสตาร์ท + การอัปเดตเมนูปิดใช้งาน ไม่มีคีย์ API ในการตั้งค่าแอปพลิเคชัน ไม่มี URL API ในการตั้งค่าแอปพลิเคชัน ไม่มี URL การกำหนดค่าในการตั้งค่าแอปพลิเคชัน @@ -63,6 +64,7 @@ URL สำหรับการกำหนดค่าเมนู (JSON) แอปพลิเคชันควรแคชการกำหนดค่าเมนูหรือไม่? แอปพลิเคชันควรล้างแคชที่มีอยู่ครั้งต่อไปในครั้งต่อไปหรือไม่ + ตรวจสอบการอัปเดตเมนูบนแอปพลิเคชันเริ่มต้นหรือไม่ หมายเหตุ: การแคชเมนูจะต้องเปิดใช้งานการตั้งค่านี้อาจทำให้อุปกรณ์เก่าที่มีหน่วยความจำน้อยลง เปิดใช้งานการดำเนินการคำสั่งผ่าน Wi-Fi/LTE แอปพลิเคชันควรให้ข้อเสนอแนะผ่านการสั่นสะเทือนหรือไม่? หมดเวลาในไม่กี่วินาที ออกจากแอปพลิเคชันหลังจากช่วงเวลาที่ไม่มีการใช้งานเพื่อประหยัดแบตเตอรี่อุปกรณ์ diff --git a/resources-tur/strings/strings.xml b/resources-tur/strings/strings.xml index cfb91a8..248742f 100644 --- a/resources-tur/strings/strings.xml +++ b/resources-tur/strings/strings.xml @@ -32,6 +32,7 @@ Menü Hafıza Menü güncellendi, yeniden başlat. + Menü güncellemeleri devre dışı. Uygulama ayarlarında API anahtarı yok. Uygulama ayarlarında API URL'si yok. Uygulama ayarlarında yapılandırma URL'si yok. @@ -63,6 +64,7 @@ Menü yapılandırması için URL (JSON). Uygulama menü yapılandırmasını önbelleğe almalı mı? Uygulama bir dahaki sefere başladığında mevcut önbelleği temizlemeli mi? + Uygulama başlangıcında menü güncellemelerini kontrol edin? Not: Menü önbellekleme etkinleştirilmelidir. Bu ayar daha az belleğe sahip eski cihazların çökmesine neden olabilir. Wi-Fi/LTE üzerinden komutların yürütülmesini etkinleştirin. Uygulama titreşimlerle geri bildirim sağlamalı mı? Saniyeler içinde zaman aşımı. Cihaz bataryasını kaydetmek için bu hareketsizlik döneminden sonra uygulamadan çıkın. diff --git a/resources-ukr/strings/strings.xml b/resources-ukr/strings/strings.xml index fb50cac..ab12c77 100644 --- a/resources-ukr/strings/strings.xml +++ b/resources-ukr/strings/strings.xml @@ -32,6 +32,7 @@ Меню Пам'ять Меню оновлено, перезапустіть. + Оновлення меню вимкнено. Немає ключа API в налаштуваннях програми. Немає URL -адреси API в налаштуваннях програми. Немає URL -адреси конфігурації в налаштуваннях програми. @@ -63,6 +64,7 @@ URL -адреса для конфігурації меню (JSON). Чи повинен додатковий кеш конфігурації меню? Чи повинен програма очистити існуючий кеш наступного разу, коли він буде запущений? + Перевірте наявність оновлень меню щодо запуску програми? ПРИМІТКА: Меню кешування необхідно увімкнути. Це налаштування може спричинити аварію старіші пристрої з меншою пам'яттю. Увімкнути виконання команд над Wi-Fi/LTE. Чи повинен програма надавати зворотній зв'язок через вібрації? Тайм -аут за лічені секунди. Вийдіть із програми після цього періоду бездіяльності, щоб зберегти акумулятор пристрою. diff --git a/resources-vie/strings/strings.xml b/resources-vie/strings/strings.xml index b5e30e6..2b428b2 100644 --- a/resources-vie/strings/strings.xml +++ b/resources-vie/strings/strings.xml @@ -32,6 +32,7 @@ Menu Ký ức Menu được cập nhật, khởi động lại. + Cập nhật menu bị vô hiệu hóa. Không có khóa API trong cài đặt ứng dụng. Không có URL API trong cài đặt ứng dụng. Không có URL cấu hình trong cài đặt ứng dụng. @@ -63,6 +64,7 @@ URL cho cấu hình menu (JSON). Bộ đệm ứng dụng có nên cấu hình menu không? Ứng dụng có nên xóa bộ đệm hiện tại vào lần tới khi nó được bắt đầu không? + Kiểm tra cập nhật menu khi bắt đầu ứng dụng? Lưu ý: Bộ nhớ đệm menu phải được bật. Cài đặt này có thể khiến các thiết bị cũ hơn có ít bộ nhớ gặp sự cố. Bật các lệnh thực thi qua Wi-Fi/LTE. Ứng dụng có nên cung cấp phản hồi thông qua các rung động? Thời gian chờ trong giây. Thoát khỏi ứng dụng sau khoảng thời gian không hoạt động để lưu pin thiết bị. diff --git a/resources-zhs/strings/strings.xml b/resources-zhs/strings/strings.xml index cf151dc..21cab3f 100644 --- a/resources-zhs/strings/strings.xml +++ b/resources-zhs/strings/strings.xml @@ -32,6 +32,7 @@ 菜单 记忆 菜单更新，重新启动。 + 菜单更新禁用。 应用程序设置中没有API密钥。 应用程序设置中没有API URL。 应用程序设置中没有配置URL。 @@ -63,6 +64,7 @@ 菜单配置的URL（JSON）。 应用程序缓存菜单配置应该缓存吗？ 应用程序下次启动时是否应该清除现有的高速缓存？ + 检查应用程序启动时的菜单更新吗？注意：必须启用菜单缓存。此设置可能会导致较旧的设备，而内存较小。 在Wi-Fi/LTE上启用执行命令。 应用程序是否应该通过振动提供反馈？ 超时几秒钟。在此不活动期间退出应用程序以节省设备电池。 diff --git a/resources-zht/strings/strings.xml b/resources-zht/strings/strings.xml index 89133c9..3d0ef1a 100644 --- a/resources-zht/strings/strings.xml +++ b/resources-zht/strings/strings.xml @@ -32,6 +32,7 @@ 菜單 記憶 菜單更新，重新啟動。 + 菜單更新禁用。 應用程序設置中沒有API密鑰。 應用程序設置中沒有API URL。 應用程序設置中沒有配置URL。 @@ -63,6 +64,7 @@ 菜單配置的URL（JSON）。 應用程序緩存菜單配置應該緩存嗎？ 應用程序下次啟動時是否應該清除現有的高速緩存？ + 檢查應用程序啟動時的菜單更新嗎？注意：必須啟用菜單緩存。此設置可能會導致較舊的設備，而內存較小。 在Wi-Fi/LTE上啟用執行命令。 應用程序是否應該通過振動提供反饋？ 超時幾秒鐘。在此不活動期間退出應用程序以節省設備電池。 diff --git a/resources-zsm/strings/strings.xml b/resources-zsm/strings/strings.xml index 8fc11d8..06d5678 100644 --- a/resources-zsm/strings/strings.xml +++ b/resources-zsm/strings/strings.xml @@ -32,6 +32,7 @@ Menu Ingatan Menu dikemas kini, mulakan semula. + Kemas kini menu dilumpuhkan. Tiada kunci API dalam tetapan aplikasi. Tiada URL API dalam tetapan aplikasi. Tiada URL Konfigurasi dalam Tetapan Aplikasi. @@ -63,6 +64,7 @@ URL untuk Konfigurasi Menu (JSON). Sekiranya aplikasi cache konfigurasi menu? Sekiranya permohonan membersihkan cache yang sedia ada pada masa akan datang, ia bermula? + Semak kemas kini menu pada permulaan aplikasi? Nota: Caching menu mesti diaktifkan. Tetapan ini boleh menyebabkan peranti yang lebih lama dengan memori yang kurang untuk kemalangan. Dayakan perintah melaksanakan melalui Wi-Fi/LTE. Sekiranya permohonan memberikan maklum balas melalui getaran? Tamat masa dalam beberapa saat. Keluar dari permohonan selepas tempoh tidak aktif ini untuk menyimpan bateri peranti. diff --git a/resources/settings/properties.xml b/resources/settings/properties.xml index bc11cee..6f0d2ce 100644 --- a/resources/settings/properties.xml +++ b/resources/settings/properties.xml @@ -38,6 +38,22 @@ --> false + + false +