Update manifest.xml

Reverted the application ID to one of the project's.
Documentation & source tidy for Lang.Dictionary items.
2025-11-22 00:28:14 +00:00 · 2025-10-30 11:50:56 +00:00 · 2025-10-30 11:39:19 +00:00 · 2025-10-30 09:03:58 +00:00 · 2025-10-30 09:02:40 +00:00 · 2025-10-30 08:57:04 +00:00
24 changed files with 293 additions and 78 deletions
--- a/BackgroundService.md
+++ b/BackgroundService.md
@@ -1,4 +1,4 @@
-[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)
+[Home](README.md) | [Switches](examples/Switches.md) | [Actions](examples/Actions.md) | [Templates](examples/Templates.md) | [Numeric](examples/Numeric.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

--- a/HISTORY.md
+++ b/HISTORY.md
@@ -1,4 +1,4 @@
-[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)
+[Home](README.md) | [Switches](examples/Switches.md) | [Actions](examples/Actions.md) | [Templates](examples/Templates.md) | [Numeric](examples/Numeric.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

@@ -51,3 +51,4 @@
 |   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. |
 |   3.5   | Added support for Edge 550, 850 & MTB, Fenix 8 Pro 47mm, GPSMAP H1, Instinct Crossover AMOLED, Venu 4 41mm & 45mm, & Venu X1 devices which also required an SDK update to 8.3.0. The simulation of the Edge 850 device was off, as it failed to update the display and text was the wrong colour, but the buttons menu items operated HA correctly. The assumption is the simulation model is buggy until someone [reports](https://github.com/house-of-abbey/GarminHomeAssistant/issues) otherwise. |
+|   3.6   | Added numeric menu item type thanks to @thmichel. This allows you to select a numeric value for a tap action. |
--- a/HTTP_Headers.md
+++ b/HTTP_Headers.md
@@ -1,4 +1,4 @@
-[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)
+[Home](README.md) | [Switches](examples/Switches.md) | [Actions](examples/Actions.md) | [Templates](examples/Templates.md) | [Numeric](examples/Numeric.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

--- a/README.md
+++ b/README.md
@@ -1,4 +1,4 @@
-[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)
+[Home](README.md) | [Switches](examples/Switches.md) | [Actions](examples/Actions.md) | [Templates](examples/Templates.md) | [Numeric](examples/Numeric.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

@@ -146,21 +146,20 @@ Example schema:
    },
    {
      "name": "Heating",
-    "content": "{{ ' %.1f' | format(state_attr('climate.myheating','temperature'))  }}",
+      "content": "{{ ' %.1f' | format(state_attr('climate.room','temperature')) }}",
      "type": "numeric",
-        "entity": "climate.myheating",
+      "entity": "climate.room",
      "tap_action": {
        "service": "climate.set_temperature",
-          "data": {
-              "step": "0.5",
-              "start": "10",
-              "stop": "30",
-              "valueLabel": "temperature",
-              "formatString": "%.1f"
+        "picker": {
+            "step": 0.5,
+            "start": 10,
+            "stop": 30,
+            "attribute": "temperature",
+            "data_attribute": "temperature"
+        }
+      }
    }
-        },
-    "pin": false
-    } ,
  ]
 }
 ```
@@ -174,25 +173,28 @@ The example above illustrates how to configure:
 * Script invocation (`tap`)
 * Service invocation, e.g. Scene setting, (`tap`)
 * A sub-menu to open (`group`)
-* A numeric item (`numeric`), which allows you to set a numeric value e.g. for heating or a dimmer. ValueLabel defines the variable to return. You can optionally set the minimum (start) and maximum (stop) value as well as the step to increase/decrease and a tepmlate how to format the value.
+* A numeric item (`numeric`), which allows you to set a numeric value e.g. for heating or a dimmer. This is [explained more fully](examples/Numeric.md) in its own examples page.
 * 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      | ✅ |   ❌  |      ❌      |
+| HA Entity Type   | Tap | Toggle | Info (status)| Numeric |
+|------------------|:---:|:------:|:------------:|:-------:|
+| Switch           | ❌ |   ✅  |      ✅      |   ❌   |
+| Switched Light   | ❌ |   ✅  |      ✅      |   ❌   |
+| Dimmer Light     | ❌ |   ❌  |      ✅      |   ✅   |
+| Automation       | ✅ |   ✅  |      ❌      |   ❌   |
+| Script           | ✅ |   ❌  |      ❌      |   ❌   |
+| Scene            | ✅ |   ❌  |      ❌      |   ❌   |
+| Sensor           | ❌ |   ❌  |      ✅      |   ❌   |
+| Binary Sensor    | ❌ |   ❌  |      ✅      |   ❌   |
+| Thermostat       | ❌ |   ❌  |      ✅      |   ✅   |
+| Amplifier        | ❌ |   ❌  |      ✅      |   ✅   |
+| 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).
+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` and `numeric` 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 ;-) ?

--- a/TroubleShooting.md
+++ b/TroubleShooting.md
@@ -1,4 +1,4 @@
-[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)
+[Home](README.md) | [Switches](examples/Switches.md) | [Actions](examples/Actions.md) | [Templates](examples/Templates.md) | [Numeric](examples/Numeric.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

--- a/Wi-Fi.md
+++ b/Wi-Fi.md
@@ -1,4 +1,4 @@
-[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)
+[Home](README.md) | [Switches](examples/Switches.md) | [Actions](examples/Actions.md) | [Templates](examples/Templates.md) | [Numeric](examples/Numeric.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

--- a/examples/Actions.md
+++ b/examples/Actions.md
@@ -1,4 +1,4 @@
-[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)
+[Home](../README.md) | [Switches](Switches.md) | [Actions](Actions.md) | [Templates](Templates.md) | [Numeric](Numeric.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
@@ -108,3 +108,64 @@ If you would like to temporarily disable an item in your menu, e.g. for seasonal
  "enabled": false
 }
 ```
+
+# Selects
+
+Here is an example of how to make a light effect selector:
+
+```json
+{
+  "type": "group",
+  "name": "Example",
+  "title": "Light Effect",
+  "content": "{{ state_attr('light.moon', 'effect') }}",
+  "items": [
+    {
+      "type": "tap",
+      "name": "None",
+      "entity": "light.example",
+      "tap_action": {
+        "service": "light.turn_on",
+        "data": {
+          "effect": "None"
+        }
+      }
+    },
+    {
+      "type": "tap",
+      "name": "Rainbow",
+      "entity": "light.example",
+      "tap_action": {
+        "service": "light.turn_on",
+        "data": {
+          "effect": "Rainbow"
+        }
+      }
+    },
+    {
+      "type": "tap",
+      "name": "Glimmer",
+      "entity": "light.example",
+      "tap_action": {
+        "service": "light.turn_on",
+        "data": {
+          "effect": "Glimmer"
+        }
+      }
+    },
+    {
+      "type": "tap",
+      "name": "Twinkle",
+      "entity": "light.example",
+      "tap_action": {
+        "service": "light.turn_on",
+        "data": {
+          "effect": "Twinkle"
+        }
+      }
+    }
+  ]
+}
+```
+
+The same pattern works for any selector (`input_select.*`, `select.*`, `climate.*` mode).
--- a/examples/Glance.md
+++ b/examples/Glance.md
@@ -1,4 +1,4 @@
-[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)
+[Home](../README.md) | [Switches](Switches.md) | [Actions](Actions.md) | [Templates](Templates.md) | [Numeric](Numeric.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

--- a/examples/Numeric.md
+++ b/examples/Numeric.md
@@ -0,0 +1,139 @@
+[Home](../README.md) | [Switches](Switches.md) | [Actions](Actions.md) | [Templates](Templates.md) | [Numeric](Numeric.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)
+
+# Numeric
+
+Provides a number picker in order to adjust a numeric value of an entity.
+
+## Thermostat
+
+An example using a thermostat as a `numeric` menu item.
+
+```json
+{
+  "name": "Heating",
+  "content": "{{ ' %.1f' | format(state_attr('climate.room','temperature')) }}",
+  "type": "numeric",
+  "entity": "climate.room",
+  "tap_action": {
+    "service": "climate.set_temperature",
+    "picker": {
+        "step": 0.5,
+        "min": 10,
+        "max": 30,
+        "attribute": "temperature",
+        "data_attribute": "temperature"
+    }
+  }
+}
+```
+
+This needs some explanation. The `tap_action` object needs a `picker` object to specify the numeric menu item's behaviour. The `picker` object is described in the table below.
+
+Field            | Purpose                                                        | Mandatory |
+-----------------|----------------------------------------------------------------|-----------|
+`step`           | The increment or decrement step size.                          | Yes       |
+`min`            | The minimum value the numeric entity can take.                 | Yes       |
+`max`            | The maximum value the numeric entity can take.                 | Yes       |
+`attribute`      | The attribute on the `entity` that holds the state to be read. | No        |
+`data_attribute` | The attribute on the `service` call that sets the state.       | Yes       |
+
+It may well be the case that often `attribute` and `data_attribute` are the same attribute, as with this example.
+
+## Helper
+
+You might define a "helper" entity as follows in Home Assistant:
+
+<img src="../images/my_float.png" width="400" title="Home Assistant Helper definition for an 'input_number'." style="margin:5px"/>
+
+In this case, the state is the actual value, so the template uses `states(..)` instead of `state_attr(..)`, you must not set the optional `attribute` value in the JSON definition so that the application uses the correct template internally for querying the HA server for its present value. Your own template definition in the `content` field will need to follow suit too. The `data_attribute` must be set to `value` for the service call that sets the chosen value from the number carousel.
+
+```json
+{
+  "name": "My Float",
+  "content": "Currently {{ states('input_number.my_float') }}",
+  "type": "numeric",
+  "entity": "input_number.my_float",
+  "tap_action": {
+    "service": "input_number.set_value",
+    "picker": {
+      "step": 0.5,
+      "min": -10.0,
+      "max": 10.0,
+      "data_attribute": "value"
+    }
+  }
+}
+```
+
+## Amplifier
+
+The complication here is this amplifier uses one scale for changing the value, a range 0.0 to 1.0, and another to render the volume on the display, dB. So the template does some scale conversion, but the number picker has to use the 0.0 to 1.0 range which is annoying.
+
+```json
+{
+  "name": "Amplifer Volume",
+  "content": "{{ '%.1f' | format(state_attr('media_player.amplifier','volume_level') * 100 -80) }} dB ({{ state_attr('media_player.amplifier','volume_level') }})",
+  "type": "numeric",
+  "entity": "media_player.amplifier",
+  "tap_action": {
+    "service": "media_player.volume_set",
+    "picker": {
+        "step": 0.005,
+        "min": 0.2,
+        "max": 0.6,
+        "attribute": "volume_level",
+        "data_attribute": "volume_level"
+    }
+  }
+}
+```
+
+The above is a little awkward to change the volume as the picker's scale is unfamiliar. To make life easier you might choose to implement a "Template number" in Home Assistant as defined in the following dialogue box.
+
+<img src="../images/template_number.png" width="500" title="Home Assistant Helper definition for an 'input_number'." style="margin:5px"/>
+
+For copy and paste, the Jinja2 fields are as follows:
+
+1. Template rendering with conversion to dB:
+
+```
+{{ state_attr('media_player.amplifier','volume_level') * 100 -80 }}
+```
+
+2. Conversion from dB to range 0.0 to 1.0:
+
+```
+{{ (value+80)/100 }}
+```
+
+3. Availability template:
+
+```
+{{ not is_state('media_player.amplifier','unavailable') }}
+```
+
+The JSON menu definition can now use dB with the new template number as follows.
+
+```json
+{
+  "name": "Amplifier Volume",
+  "content": "{% if is_state('media_player.amplifier','unavailable') %}Off{% else %}{{ '%.1f' | format(states('number.amplifier_db') | float) }} dB{% endif %}",
+  "type": "numeric",
+  "entity": "number.amplifier_db",
+  "tap_action": {
+    "service": "number.set_value",
+    "picker": {
+        "step": 0.5,
+        "min": -60.0,
+        "max": -15.0,
+        "data_attribute": "value"
+    }
+  }
+},
+```
+
+## Trouble Shooting
+
+Specific to this menu item:
+
+1. If the number picker does not initialise with the correct value, amend the `attribute` field. Just because your template renders does not mean the application has extracted the numeric valueas the `content` template is rendered on the Home Assistant server.
--- a/examples/Switches.md
+++ b/examples/Switches.md
@@ -1,4 +1,4 @@
-[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)
+[Home](../README.md) | [Switches](Switches.md) | [Actions](Actions.md) | [Templates](Templates.md) | [Numeric](Numeric.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

--- a/examples/Templates.md
+++ b/examples/Templates.md
@@ -1,4 +1,4 @@
-[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)
+[Home](../README.md) | [Switches](Switches.md) | [Actions](Actions.md) | [Templates](Templates.md) | [Numeric](Numeric.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

--- a/images/my_float.png
+++ b/images/my_float.png
--- a/images/template_number.png
+++ b/images/template_number.png
--- a/manifest.xml
+++ b/manifest.xml
@@ -24,7 +24,7 @@
    Use "Monkey C: Edit Application" from the Visual Studio Code command palette
    to update the application attributes.
  -->
-    <iq:application id="971834c4-e4fc-4825-801f-7ac9db0e3044" 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 command palette to edit
      the build targets:
--- a/source/BackgroundServiceDelegate.mc
+++ b/source/BackgroundServiceDelegate.mc
@@ -133,20 +133,20 @@ class BackgroundServiceDelegate extends System.ServiceDelegate {
            var data = { "gps_accuracy" => accuracy };
            // Only add the non-null fields as all the values are optional in Home Assistant, and it avoid submitting fake values.
            if (position.position != null) {
-                data.put("gps", position.position.toDegrees());
+                data["gps"] = position.position.toDegrees();
            }
            if (position.speed != null) {
-                data.put("speed", Math.round(position.speed));
+                data["speed"] = Math.round(position.speed);
            }
            if (position.heading != null) {
                var heading = Math.round(position.heading * 180 / Math.PI);
                while (heading < 0) {
                    heading += 360;
                }
-                data.put("course", heading);
+                data["course"] = heading;
            }
            if (position.altitude != null) {
-                data.put("altitude", Math.round(position.altitude));
+                data["altitude"] = Math.round(position.altitude);
            }
            // System.println("BackgroundServiceDelegate onTemporalEvent(): data = " + data.toString());

--- a/source/HomeAssistantApp.mc
+++ b/source/HomeAssistantApp.mc
@@ -720,19 +720,13 @@ class HomeAssistantApp extends Application.AppBase {
                        var item     = mItemsToUpdate[i];
                        var template = item.getTemplate();
                        if (template != null) {
-                            mTemplates.put(i.toString(), {
-                                "template" => template
-                            });
+                            mTemplates[i.toString()] = { "template" => template };
                        }
                        if (item instanceof HomeAssistantToggleMenuItem) {
-                            mTemplates.put(i.toString() + "t", {
-                                "template" => (item as HomeAssistantToggleMenuItem).getToggleTemplate()
-                            });
+                            mTemplates[i.toString() + "t"] = { "template" => (item as HomeAssistantToggleMenuItem).getToggleTemplate() };
                        }
                        if (item instanceof HomeAssistantNumericMenuItem) {
-                            mTemplates.put(i.toString() + "n", {
-                                "template" => (item as HomeAssistantNumericMenuItem).getNumericTemplate()
-                            });
+                            mTemplates[i.toString() + "n"] = { "template" => (item as HomeAssistantNumericMenuItem).getNumericTemplate() };
                        }
                    }
                }
--- a/source/HomeAssistantGroupMenuItem.mc
+++ b/source/HomeAssistantGroupMenuItem.mc
@@ -33,7 +33,7 @@ class HomeAssistantGroupMenuItem extends HomeAssistantMenuItem {
        }?
    ) {
        if (options != null) {
-            options.put(:icon, icon);
+            options[:icon] = icon;
        } else {
            options = { :icon => icon };
        }
--- a/source/HomeAssistantMenuItemFactory.mc
+++ b/source/HomeAssistantMenuItemFactory.mc
@@ -31,9 +31,7 @@ class HomeAssistantMenuItemFactory {
    //! Class Constructor
    //
    private function initialize() {
-        mMenuItemOptions = {
-            :alignment => Settings.getMenuAlignment()
-        };
+        mMenuItemOptions = { :alignment => Settings.getMenuAlignment() };

        mTapTypeIcon = new WatchUi.Bitmap({
            :rezId => $.Rez.Drawables.TapTypeIcon,
@@ -84,7 +82,7 @@ class HomeAssistantMenuItemFactory {
    ) as WatchUi.MenuItem {
        var keys = mMenuItemOptions.keys();
        for (var i = 0; i < keys.size(); i++) {
-            options.put(keys[i], mMenuItemOptions.get(keys[i]));
+            options[keys[i]] = mMenuItemOptions.get(keys[i]);
        }
        return new HomeAssistantToggleMenuItem(
            label,
@@ -119,15 +117,15 @@ class HomeAssistantMenuItemFactory {
            if (data == null) {
                data = { "entity_id" => entity_id };
            } else {
-                data.put("entity_id", entity_id);
+                data["entity_id"] = entity_id;
            }
        }
        var keys = mMenuItemOptions.keys();
        for (var i = 0; i < keys.size(); i++) {
-            options.put(keys[i], mMenuItemOptions.get(keys[i]));
+            options[keys[i]] = mMenuItemOptions.get(keys[i]);
        }
        if (service != null) {
-            options.put(:icon, mTapTypeIcon);
+            options[:icon] = mTapTypeIcon;
            return new HomeAssistantTapMenuItem(
                label,
                template,
@@ -137,7 +135,7 @@ class HomeAssistantMenuItemFactory {
                mHomeAssistantService
            );
        } else {
-            options.put(:icon, mInfoTypeIcon);
+            options[:icon] = mInfoTypeIcon;
            return new HomeAssistantTapMenuItem(
                label,
                template,
@@ -172,9 +170,9 @@ class HomeAssistantMenuItemFactory {
        }
        var keys = mMenuItemOptions.keys();
        for (var i = 0; i < keys.size(); i++) {
-            options.put(keys[i], mMenuItemOptions.get(keys[i]));
+            options[keys[i]] = mMenuItemOptions.get(keys[i]);
        }
-        options.put(:icon, mTapTypeIcon);
+        options[:icon] = mTapTypeIcon;
        return new HomeAssistantNumericMenuItem(
            label,
            template,
--- a/source/HomeAssistantNumericMenuItem.mc
+++ b/source/HomeAssistantNumericMenuItem.mc
@@ -177,13 +177,11 @@ class HomeAssistantNumericMenuItem extends HomeAssistantMenuItem {
    //
    function getNumericTemplate() as Lang.String? {
        var entity_id = mData["entity_id"];
-        var attribute = mPicker["attribute"] as Lang.String;
+        var attribute = mPicker["attribute"] as Lang.String?;
        if (entity_id == null) {
            return null;
        } else {
            if (attribute == null) {
-                // Compiler says: "Statement is not reachable."
-                // This is wrong because a break point on the following line proves it is executed!
                return "{{states('" + entity_id.toString() + "')}}";
            } else {
                return "{{state_attr('" + entity_id.toString() + "','" + attribute + "')}}";
--- a/source/HomeAssistantView.mc
+++ b/source/HomeAssistantView.mc
@@ -35,7 +35,7 @@ class HomeAssistantView extends WatchUi.Menu2 {
        if (options == null) {
            options = { :title => definition.get("title") as Lang.String };
        } else {
-            options.put(:title, definition.get("title") as Lang.String);
+            options[:title] = definition.get("title") as Lang.String;
        }
        WatchUi.Menu2.initialize(options);

--- a/web/index.html
+++ b/web/index.html
@@ -7,7 +7,7 @@
    <link
      rel="stylesheet"
      data-name="vs/editor/editor.main"
-      href="https://www.unpkg.com/monaco-editor@0.45.0/min/vs/editor/editor.main.css" />
+      href="https://www.unpkg.com/monaco-editor@0.52.2/min/vs/editor/editor.main.css" />
    <link
      rel="stylesheet"
      type="text/css"
--- a/web/main.js
+++ b/web/main.js
@@ -141,10 +141,32 @@ async function get_services() {
 * @returns {Promise<{}>}
 */
 async function get_schema() {
-  const res = await fetch(
-    'https://raw.githubusercontent.com/house-of-abbey/GarminHomeAssistant/main/config.schema.json'
-  );
-  return res.json();
+  const searchParams = new URL(window.location).searchParams;
+
+  const url = searchParams.get('schema');
+  if (url) return (await fetch(url)).json();
+
+  const branch = searchParams.get('branch');
+  if (branch)
+    return (
+      await fetch(
+        `https://raw.githubusercontent.com/house-of-abbey/GarminHomeAssistant/refs/heads/${branch}/config.schema.json`
+      )
+    ).json();
+
+  const version = searchParams.get('version');
+  if (version)
+    return (
+      await fetch(
+        `https://raw.githubusercontent.com/house-of-abbey/GarminHomeAssistant/refs/tags/${version}/config.schema.json`
+      )
+    ).json();
+
+  return (
+    await fetch(
+      `https://raw.githubusercontent.com/house-of-abbey/GarminHomeAssistant/main/config.schema.json`
+    )
+  ).json();
 }

 /**
--- a/web/package.json
+++ b/web/package.json
@@ -10,7 +10,7 @@
  "author": "",
  "license": "ISC",
  "devDependencies": {
-    "@types/toastify-js": "^1.12.4",
+    "@types/toastify-js": "1.12.0",
    "@vscode/webview-ui-toolkit": "1.4.0",
    "json-ast-comments": "1.1.1",
    "monaco-editor": "0.52.2",
--- a/web/pnpm-lock.yaml
+++ b/web/pnpm-lock.yaml
@@ -6,8 +6,8 @@ settings:

 devDependencies:
  '@types/toastify-js':
-    specifier: ^1.12.4
-    version: 1.12.4
+    specifier: 1.12.0
+    version: 1.12.0
  '@vscode/webview-ui-toolkit':
    specifier: 1.4.0
    version: 1.4.0(react@18.2.0)
@@ -55,8 +55,8 @@ packages:
      exenv-es6: 1.1.1
    dev: true

-  /@types/toastify-js@1.12.4:
-    resolution: {integrity: sha512-zfZHU4tKffPCnZRe7pjv/eFKzTVHozKewFCKaCjZ4gFinKgJRz/t0bkZiMCXJxPhv/ZoeDGNOeRD09R0kQZ/nw==}
+  /@types/toastify-js@1.12.0:
+    resolution: {integrity: sha512-fqpDHaKhFukN9KRm24bbH0wozvHmSwjvkaLjBUrWcSfSS4zysIwTYqNLG3XbSNhRlsTNRNLGS23tp/VhPwsfHQ==}
    dev: true

  /@vscode/webview-ui-toolkit@1.4.0(react@18.2.0):
Author	SHA1	Message	Date
Philip Abbey	6e3cf73ab3	Update manifest.xml Reverted the application ID to one of the project's.	2025-10-30 11:50:56 +00:00
Philip Abbey	14186b7992	Documentation & source tidy for Lang.Dictionary items.	2025-10-30 11:39:19 +00:00
Philip Abbey	f64bed5058	Add light effect selector example to Select.md (#301 ) Added an example of a light effect selector in JSON format.	2025-10-30 09:03:58 +00:00
Philip Abbey	619671de5d	Moved the contents of Select.md to Actions.md Feels like we already have a home for the example without creating a separate new file.	2025-10-30 09:02:40 +00:00
Philip Abbey	6d18406880	Select schema version in web (#300 ) To test the schema on a specific version: ```url https://house-of-abbey.github.io/web/?version=v1.4 ``` To test the schema on a specific branch: ```url https://house-of-abbey.github.io/web/?branch=numeric-item-json-schema ``` To test the schema on an arbitrary URL (may be affected by cors): ```url https://house-of-abbey.github.io/web/?schema={url} ```	2025-10-30 08:57:04 +00:00
Philip Abbey	3a7676f4bf	Add Numeric Menu Item (#298 ) Added a new numeric menu item to set numeric values e.g. for heating, volume, dimmer etc.	2025-10-29 20:11:31 +00:00
thmichel	f19eb7c276	Fixed compiler warning for unreachable code	2025-10-29 19:18:06 +01:00
thmichel	c617d2cad6	Merge pull request #4 from house-of-abbey/Picker-formatter Suggested code changes from philipabbey	2025-10-29 18:33:54 +01:00
Joseph Abbey	81fa876449	Add light effect selector example to Select.md Added an example of a light effect selector in JSON format. Signed-off-by: Joseph Abbey <me@josephabbey.dev>	2025-10-22 14:37:41 +01:00
Joseph Abbey	b563ab7923	Arbitrary schema URL	2025-10-22 09:08:24 +01:00
Joseph Abbey	2ebf36a445	Select schema version in web	2025-10-22 09:05:09 +01:00