Thanks for the reply - and I personally also only use this driver for a couple of simple voice actions "turn TV on/off" or a simple dashboard tile that does the same thing.
But, while working on my dashboard app I realized there's a lot of people using dashboards for a lot of things I wouldn't have previously thought of. So, I just try to make the app as flexible as possible.
Anyway, yeah, trying to add every command would probably be overkill for any dashboard. I was originally just thinking of supporting many of the commands that are part of the parent device driver - which includes the navigation arrows. Then I realized these commands all require a device ID which isn't listed anywhere (at least exposed via Maker API). So I was really just looking for the possible device ID's to start (and the device name).
Of course, that leads to thinking about other possible things that could be done and that's where the deviceCommand options came from. I had also thought it could be nice to allow the user to switch activities and I realized there wasn't a way to do this via the parent driver (I know I could use each child driver for this but for me personally having it all on a single dashboard tile would be easier)..
I was hoping some of these request would just be easy on your end but no biggie if not either
