Closed oferlaor closed 6 months ago
Just run atvremote wizard
and follow the instructions, should be enough.
Right, I think there's a bug in companion when running the wizard. I'll fix that soon and make a release, will let you know when it's available.
Thanks.
BTW, any plans to create a "wizard" functionality into the web service?
Although the library is critical, I think the web service is undervalued, particularly if it's widely available in Docker. As many people do, I have a smart home with easy access to REST, but complex protocols are relegated to IR. It might be a good idea to have a full (simple) flow supported through the Web service and have an official docker image for it (I had to cobble one together, which I assume is not up to date with the latest atvremote).
On Wed, Sep 27, 2023 at 7:13 PM Pierre Ståhl @.***> wrote:
Right, I think there's a bug in companion when running the wizard. I'll fix that soon and make a release, will let you know when it's available.
— Reply to this email directly, view it on GitHub https://github.com/postlund/pyatv/issues/2215#issuecomment-1737700553, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAXNRHGAIRULOUMPRDPHBJDX4RGC7ANCNFSM6AAAAAA5JTSBWE . You are receiving this because you authored the thread.Message ID: @.***>
-- Best regards,
Thing is that pyatv is purely a library and does not expose any API except for a pure python API. That is my only intention to support as well. I have some example code for exposing parts of the API via HTTP, but it is merely that: an example. The way it should go is that someone needs to implement a proper application built with pyatv that exposes an API for external consumers. That would be great, but not something that I'm interested in developing not maintaining unfortunately.
What do you need help with?
I am trying to use pyatv with a docker instance using the aiohttp implementation.
From what I understand, the protocol I need to use is companion link.
I was able to launch a docker instance of pyatv and I can see my device when I access the /scan endpoint. I'm also able to connect, but only via MRP (companion is asking for credentials that I can't seem to figure out how to generate).
Using MRP, I can't see to use any /remote_control command (it replies not supported to everything I'm trying). Any suggestions?