Open disbrand opened 1 year ago
Hey, just looked through the Emby API documentation, and looks like all the endpoints that I need are mirrored 1:1 from jellyfin.
Try to use the jellyfin integration to attach your emby server - /jellyfinsettings setup
for server url, put https://[YOUR SERVER URL]:[YOUR SERVER PORT]/emby
you'll need to also generate an API key from within emby settings.
I'll probably make an emby integration and update this issue appropriately when I do, but I want to redesign the separation of integrations first, to keep the spaghetti code to a minimum.
For some reason, not sure if it's a recent release, but the password isn't being added correctly. So it's not working anymore for Emby user creation.
For some reason, not sure if it's a recent release, but the password isn't being added correctly. So it's not working anymore for Emby user creation.
User created but password seems to not be, so logging in with blank password seems to be the workaround until its looked at
So does this work with emby using the jellyfin integration out of the box?
The APIs for jellyfin and emby are similar, but probably not identical since it's been a while since it was forked. On Nov. 20, 2023, 2:07 PM -0500, sudodrew @.***>, wrote:
For some reason, not sure if it's a recent release, but the password isn't being added correctly. So it's not working anymore for Emby user creation. User created but password seems to not be, so logging in with blank password seems to be the workaround until its looked at — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were assigned.Message ID: @.***>
It appears to work partially out of the box. I have it connected to my emby server. The username works but the generated password doesn't. The user is able to log in with their username and a blank password. So I assume it's only creating the user but not passing the password.
Just dropping an issue to request some research into potential Emby support, as asked on Reddit :)