Pwa note playing can embed home assistant dashboard for additional controls

[andrew-codes]

No description provided.

[cvele]

Over the last few days I've been working on a way to implement Playnite control in HASS dashboard. I'm heavily leaning onto your work - so first of all: thanks!

The implementation is described in detail over here: https://blog.cvetic.in.rs/home-automation/control-playnite-home-assistant-dashboard/

The concept can be drastically simplified, and the route I see is packaging playnite-web in hass addons as separate components, providing rudimentary rest api as backend for front-end and then packaging custom lovelace card for dashboards.

Is that the route you see playnite-web taking or do you see it as a separate initiative?

[andrew-codes]

Hi @cvele, I came across your post on Reddit and thought it was awesome! Thanks for the exposure.

In terms of your question, I've been torn trying to bridge two different directions/use cases. For me, personally, my end goal is to control my gaming setup with Playnite Web. I have something like what you posted, however Playnite Web's front-end is what activates a game to be played. I added this feature behind a login in Playnite Web and then embed Playnite Web into my HA dashboard (see image below). I use this on an iPad as my over-powered game room remote. I have tabs at the top of the single dashboard view to control things like volume, etc. though I typically handle that through volume presets that are also automated depending on what platform is playing, PC vs PlayStation, etc. I use a separate service to turn on/off the PlayStation over MQTT which I have in a separate repo now.

The other direction is for more broad appeal outside my own use case, sharing your library with friends. The two use cases aren't in direct conflict with each other, but adding in my own use case to a generalized sharing of your game library has felt a little weird to be honest.

With that said, I had not considered separating the API portion of Playnite Web to power other non-Playnite Web experiences, but I do not see why this couldn't be incorporated into Playnite Web. It would add one additional service to run (docker container), but that seems par for the course already given the parts are already separated.

As for packaging as HASS addons, this seems like an easy win, too. My understanding is this is simply a slight variation of how the application is packaged and a workflow to automate it. I'm not as familiar with how HASS addons are actually packaged.

To summarize: I'm amendable to the idea of creating an API service and adding a new release mechanism to release as a HASS add-ons. I'm not familiar with the process to package as a HASS add-ons, so I would welcome any aid in this endeavor, such as pull requests or guidance.

• I've added an issue to track the work to create an API separate from playnite-web here feat: enable powering non-playnite-web-app experiences by providing API to retrieve data #318.
• Tracking HASS add-on via Package playnite-web as HASS add-ons #319

[andrew-codes]

@cvele , additionally, once #319 is setup, I'd if you contributed any HA custom cards that you may have already made to be packaged as part of playnite-web's HASS add-ons!

[cvele]

@andrew-codes Thanks for the kind words.

API Service Separation: Creating a separate API service for Playnite Web is a practical and flexible move, aligning perfectly with a broader appeal. Your suggestion for a GraphQL interface is excellent, and adding subscriptions would enhance its capabilities significantly.

Packaging as HASS Add-ons: Packaging Playnite Web as HASS add-ons is a logical step, and I’m excited to help with the process. I’ve experimented a bit over the last few days, as seen in my GitHub repo. The main challenge right now is the lack of arm64 builds. My plan is to submit a couple of PRs, starting with multi-architecture support, followed by the HASS add-on package. I appreciate your patience as I’m still getting up to speed with HASS development.

Custom Lovelace Cards: I’m happy to contribute the custom Lovelace cards I’ve developed. It makes perfect sense to consolidate everything in one place. While this might need a different route via HACS, your point stands that it should all be part of the same repository.

Thanks again for your support and feedback. Looking forward to enhancing Playnite Web together!