emby api not working

[SurvivaLlama]

Description

Good evening. I followed the instructions but I cant get the emby api key to work. Did emby change their apis?

homepage version

.8.13

Installation method

Docker

Configuration

- Emby:
        icon: emby.png
        href: http://192.168.1.141:8096
        ping: http://192.168.1.141:8096
        description: Media player
        widget:
          type: emby
          url: http://192.168.1.141:8096
          key: ****

Container Logs

No response

Browser Logs

No response

Troubleshooting

I know im doing something right, because all my other widgets at working. Ideas?

[glime-ai[bot]]

Thanks for posting a discussion about homepage here on GitHub. Homepage now uses a fancy new AI tool thanks to our friends at Glime, so the answer below is the AI bot's attempt to answer your question. If you feel it's sufficient you can mark the answer and close this post, otherwise feel free to leave it open of course!

Thanks for using Homepage! ❤️

---

To assist you with the Emby API key issue, I would need to clarify a few points:

1. Have you generated the API key from within Emby's settings as described in the documentation? You can create an API key by navigating to Settings > Advanced > Api Keys in your Emby server dashboard.
2. Can you confirm that the API key you are using in your configuration is the exact key generated from Emby without any modifications or redactions?
3. Have you tried using the API key directly in a browser or via a curl command to see if it's working outside of the Homepage widget context?

If you have confirmed the above and the API key still doesn't work, it's possible that there might be an issue with the Homepage widget configuration or a compatibility issue with the version of Emby you are using. Please ensure that your Homepage and Emby versions are compatible.

If you continue to experience issues, please provide any error messages you see in the browser console or Homepage container logs, as these can offer clues to the underlying problem.

Lastly, ensure that the API key is correctly placed in the key field of your configuration without any placeholder characters like ****. It should be the actual API key string provided by Emby.

If you need further assistance, please provide the additional information requested, and I'll be happy to help you troubleshoot the issue further.

This comment was generated by Glime.

[SurvivaLlama]

How do I do #3?

[shamoon]

Unfortunately you cant back-and-forth with the bot here (you can on the website or discord btw, which can be very helpful). But the troubleshooting guide is where you should start. It is extremely unlikely that emby broke their api.

As for a curl, emby API is of the format {url}/emby/{endpoint}?api_key={key} so e.g. curl -L 'http://localhost:8096/emby/Sessions/?api_key=740e46e44f224b41b24b21da225bf1e5'

[SurvivaLlama]

Thanks. What should I expect as the respond when I put that command in?

[shamoon]

You should see data, not an error. But also important to test from inside the homepage container to make sure it’s not a networking issue. See the troubleshooting guide in the docs

[github-actions[bot]]

This discussion has been automatically closed due to inactivity. See our contributing guidelines for more details.

[github-actions[bot]]

This discussion has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns. See our contributing guidelines for more details.