It might have to be part of the official distro, which is also why I want to get it approved. I’m not even sure how to go about doing that.
Right now the major limiting factor is that the MythTVServiceAPI code is still in a state of flux and not in PyPI, so if I hard-code a version to pull in, it could break, and therefore won’t work. I could copy the relevant parts of the code into the frontend component itself, but that goes against the “modular” design philosophy that hass wants to use. That, and I like the idea of having the API being able to be updated separately for new versions of MythTV in the future.
I’m still running 0.27 or 0.28 (can’t even remember now) so having a 29.0 tester is a good thing. I’m also not running anything (even hass) on a Pi, so it’s probably good to have a tester working on the hardware that’s more common.
@lindsayward has done all of the fun stuff like the video images. Sadly, I don’t even use the component yet. I have a whole house MythTV system, but just use the frontends on the TV to control everything. I’ve been too busy playing with servers and getting Z-Wave and automations set up to really get into the media_player components. That and my Samsung TVs don’t seem to play nicely with HA anyway, so I can’t just say “watch TV” and have the TV turn on, which takes a lot out of the magic - I still need the remote… at least until I build some IR blasters. Once I do get into HADashboard again, I’ll probably get back to using the component.