I'm still struggling to justify adding things that would modify the device state (unlock, reboot). Technically, of course both requests are possible. Some thoughts:
Neither of these operations are available in HDHomeRun Config GUI, nor from the device webpage (at least not for any of my tuners). You can mess with the tuners a bit in HDHomeRun Config though, admittedly. For what I think are probably the lionshare of people out there these would be dangerous operations to allow, even if made optional to allow. I think most people are going to be using a front-end to the tuners, be it the HDHomeRun app, Kodi, Plex, etc. as well as a DVR/recording solution. Unlocking a tuner manually or rebooting it from an application that doesn't have any insight as to what the tuner stream(s) are being used for feels a bit on the reckless side. In the case of HDHomeRun DVR, the application *could* have insight into it since it somewhat knows what's going on, but HDHomeRun DVR doesn't expose what tuners it's actually using. It is true that one could compare the stream target IP with that of the HDHomeRun DVR and perhaps disallow, but again this is just one of a plethora of possible DVR systems that use HDHomeRun tuners. Once a tuner is unlocked, it's eligible for use by another application/purpose whether the current stream was needed or not. I think that's kind of a bad thing?
I did consider the UI implications and suggestions, however. What I was thinking would be a "lock" glyph adjacent to the target IP address that indicates it's locked, clicking that would unlock it and remove the glyph (NOTE: the glyph font I need to use on Windows 7 doesn't have an "unlock" glyph, just a "lock" one, so ... this). For reboot, have either a "power" glyph or the circular arrow type "refresh" glyph in the footer all the way to the right that would do it. An alternate option I thought of would be adding just a "wrench" glyph in the device footer all the way to the right that would bring up a context menu or something that would provide ways to unlock/reboot/channel scan/etc.
There is also the slippery slope factor to consider. If an application allows SOME device state modifying operations, will it eventually need to support ALL device state modifying operations, like the aforementioned channel scan? Now we're into HDHomeRun Setup turf, especially for legacy tuner devices, and I personally think that's a bridge too far.
I'm still not saying no, and I would like to know what everyone thinks about this. Such things are not hard to do, but still feel very out of place here to me. Maybe I just don't understand why anyone in 2022 is still manually unlocking and rebooting their HDHomeRun tuners? Are there issues with the modern tuners without LEDs that should be brought up to SiliconDust as opposed to having an application that can ease the pain? It's an honest question.
And hey, it's open source with a very
permissive "do what you want with it" license (that's how I roll
) Anyone is totally free to do whatever they want to this thing and make it their own!