Open AIIX opened 2 years ago
A few comments in favor of the Web UI:
I think both approaches are useful; I think showing a default QML when you match a voice intent makes sense since that intent should specify an item or group. For something like a home page or control panel (or an intent to 'show {x} dashboard'), I think it makes more sense to use the Lovelace UI.
I made a PR for loading the Lovelace UI, if you want to give it a try: https://github.com/MycroftAI/skill-homeassistant/pull/91
Add a native QML UI interface instead of webviews as being used in https://github.com/MycroftAI/skill-homeassistant/pull/84 A native QML UI provides more controls over the UI integration than a web interface, For example, a basic QML UI can be implemented for a group of devices and each individual device within a group itself (just to be clear the below is just an example of what it can look like from my pov as a community dev)
Some of the cons of using a web interface instead of a native interface: