Expanded TroubleShooting.md with a new section illustrating the features of the GarminHomeAssistant web-based editor, including schema checking, entity name completion, and template preview. Added supporting images to the images/editor directory to visually demonstrate these features.
Added a highlighted section explaining the challenges and rationale behind the dashboard menu configuration approach, emphasizing the limitations of small devices and the need for external configuration. Encourages users to manage expectations and read documentation before seeking support.
Expanded the Selects section with an example showing how to use a tap action to cycle through EV charger modes using the select service. Also credited the community member who contributed the example.
Corrected typos in README.md and clarified troubleshooting steps in TroubleShooting.md. Added browser compatibility note for the web-based editor, improved error message explanations, and provided more detailed guidance for resolving 'No JSON returned from HTTP request' issues.
Added important notes about using REQBIN for API testing, including URL formatting and request limits.
Signed-off-by: Philip Abbey <philipabbey@users.noreply.github.com>
Added credits section acknowledging Matthias Oesterheld for the PIN feature contribution.
Signed-off-by: Philip Abbey <philipabbey@users.noreply.github.com>
Removed the need to specify any menu titles. The code works with a
`Null` as-is. I'm not convinced the lack of a title saves screen space
as desired, but the code works without a title, there's no real reason
to specify one as its not essential, so perhaps we just relax the
schema?
There is one user requesting this. They can work with a schema warning
for now and this can be rolled into the next release, when there's more
changes.
Changed the way colours were managed in the SVG files to make them more amenable to scripting. Changed the scripts to automate icon resizing.
Co-Authored-By: Joseph Abbey <me@josephabbey.dev>
Turns out the sync service will not run unless the picker has not only
been popped but the display also updated.
v3.7 needs a swift turnaround as its a bug reported by a user.
