Amended documentation about special characters in the glance view

And a couple of code tidy items too.

.github/ISSUE_TEMPLATE/bug_report.md

@@ -2,13 +2,19 @@
 name: Bug report
 about: Create a report to help us improve
 title: ''
-labels: bug
+labels: question
 assignees: ''
 
 ---
 
-**Describe the bug**
-A clear and concise description of what the bug is.
+The majority of bug reports submitted are solved without changes to the Garmin application's code. This means that reporters are too often keen to attribute their issue to a problem with the application instead of:
+1. Their own lack of reading documentation
+2. Their own infrastructure
+
+Therefore in the first place make your report as if it were a **question** in order to establish if the authors agree there is really a bug!
+
+**Describe your issue**
+A clear and concise description of what the issue is.
 
 **IMPORTANT!**
 I have:
@@ -17,8 +23,9 @@ I have:
 - [ ] Checked that my JSON Syntax is correct ([options 2, 3, or 4](https://github.com/house-of-abbey/GarminHomeAssistant#editing-the-json-file) or otherwise)
 - [ ] Checked that my JSON follows the schema ([options 2, 3, or 4](https://github.com/house-of-abbey/GarminHomeAssistant#editing-the-json-file))
 - [ ] Used the online editor to check my JSON against HomeAssistant ([option 1](https://github.com/house-of-abbey/GarminHomeAssistant#editing-the-json-file))
-- [ ] Checked the [Docs](https://github.com/house-of-abbey/GarminHomeAssistant)
-- [ ] Checked the [Troubleshooting Guide](https://github.com/house-of-abbey/GarminHomeAssistant/blob/main/TroubleShooting.md)
+- [ ] Read the [Documentation](https://github.com/house-of-abbey/GarminHomeAssistant)
+- [ ] Run through the [Troubleshooting Guide](https://github.com/house-of-abbey/GarminHomeAssistant/blob/main/TroubleShooting.md)
+- [ ] Checked the [Known Issues](https://github.com/house-of-abbey/GarminHomeAssistant?tab=readme-ov-file#known-issues), i.e. the problems beyond the control of this Garmin application and must therefore be tolerated!
 
 **To Reproduce**
 Steps to reproduce the behavior:

Etiquette.md

@@ -142,6 +142,8 @@ On Mon, 6 May 2024 at 09:01, <noreply@garmin.com> wrote:
 
 ![Please help me set this up](images/etiquette/2024-05-06_GHA_Bad_Review.png)
 
+<img src="images/etiquette/2026-04-02_GHA_Bad_Review.png" width="70%" title="Not working">
+
 Answer: Make sure you meet the [minimum requirements for being a user](#etiquette) please! Provide more information on what the problem actually is. Clearly the support reply pointing to the documentation was either not read or not considered helpful, hence the point about meeting the minimum user requirements.
 
 On Fri, 31 Oct 2025 at 11:45, <noreply@garmin.com> wrote:
@@ -390,10 +392,10 @@ Don't get an embarrassing retort, I call out those who "click & complain" withou
 
 Two words. Perhaps too lazy to consider why others gave rave reviews and ponder what he was doing wrong? Perhaps did not consider there might be some documentation to assist or support routes (subject to [getting a polite reply](getting-help-with-a-polite-reply))?
 
-<img src="images/etiquette/2026-01-21 GHA_Bad_Review.png" width="70%" title="Two words">
+<img src="images/etiquette/2026-01-21_GHA_Bad_Review.png" width="70%" title="Two words">
 
 ---
 
 Blaming the wrong application. Just rude. Please get your facts straight. And it was such a simple workaround for the Garmin Connect IQ app bug.
 
-<img src="images/etiquette/2025-11-19%20GHA_Bad_Review.png" width="85%" title="Misplaced blame">
+<img src="images/etiquette/2025-11-19_GHA_Bad_Review.png" width="85%" title="Misplaced blame">

examples/Glance.md

@@ -48,7 +48,7 @@ The 'status' view will persist showing until the API becomes available as withou
 You may make this as complicated as you like! But you have limited space and only ASCII text characters. **It is essential to turn on menu caching in order to display of the template**. This is a change in v3.11 where multiple users are now making larger JSON menus than was originally envisaged for this watch application. As a result the Glance view would fail with an untrapable (fatal) _"Error: Out Of Memory Error"_. A work around is to pull out the glance subsection of the menu and cache that separately during execution of the full application, but that means any changes to the customised Glance view do not show until after the full application has been run.
 
 > [!IMPORTANT]
-> Sadly what you cannot do is use special characters like: 🌞🔋⛅🪫. Whilst these do display in menu items, they do not seem to work on the Glance view. We really like them, so have tried but failed. Only ASCII text appears to be supported by the Garmin Connect IQ SDK's Glance View. This is not something we have any control over, please do not request this to be "fixed".
+> Sadly support for special characters like 🌞🔋⛅🪫 in the glance view is device dependent. For example they are not available on a Venu2 device but are available on a Venu X1 device. The application documentation shows them displaying in menu items. Only ASCII text appears to be universally supported by the Garmin Connect IQ (as you might hope). This is not something we have any control over, please do not request this to be "fixed".
 
 It is possible to revert to the default glance content without deleting the template by changing the `type` to `status`.
 

source/HomeAssistantService.mc

@@ -122,6 +122,7 @@ class HomeAssistantService {
     //!
     //! @param action The Home Assistant action to be run, e.g. from the JSON `action` field.
     //! @param data   Data to be supplied to the action call.
+    //! @param exit   Whether to exit the app after making the call.
     //
     function call(
         action as Lang.String,

source/HomeAssistantToggleMenuItem.mc

@@ -228,9 +228,7 @@ class HomeAssistantToggleMenuItem extends WatchUi.ToggleMenuItem {
         // If there's no response body, let's assume that what we did actually happened and flip the toggle.
         if (data.size() == 0) {
             setEnabled(!isEnabled());
-        }
-
-        else {
+        } else {
             for(var i = 0; i < data.size(); i++) {
                 if ((data[i].get("entity_id") as Lang.String).equals(mData.get("entity_id"))) {
                     var state = data[i].get("state") as Lang.String;