Open olivermaor opened 7 months ago
I don't know if the author will update the integration, if no, I've just created a fork with 2025.1 compatibility. https://github.com/Mis1ify/jellyfin_ha
@Mis1ify not sure if there is a way to change it, but for me it seems the entities only refresh when the integration is stopped/started, or the entity is messed with directly in home assistant. I'm on HA 2024.8.2
@Mis1ify not sure if there is a way to change it, but for me it seems the entities only refresh when the integration is stopped/started, or the entity is messed with directly in home assistant. I'm on HA 2024.8.2
For me it's working perfectly fine I'm also running HA 2024.8.2. I'll send my settings.
First, I needed to enable my entity manually, then it started updating everything.
I have a similar issue. But from what I can tell, it's because the user I am setting the integration up with is not an administrator. (I can use next/prev episode, pause, but not resume, also media playback state is frozen).
Media players seem to function if I set up with my admin account instead, however the admin account is not the account used for playback by the house so the optional card datas produced by this login are worthless ><
Edit: by admin I simply mean this checkbox
I'd be swell if I didn't have to let my house have management permission for stuff to work though!
Hello, I received the following warning message in my logs:
Entity None (<class 'custom_components.jellyfin.media_player.JellyfinMediaPlayer'>) is using deprecated supported features values which will be removed in HA Core 2025.1. Instead it should use <MediaPlayerEntityFeature.PAUSE|SEEK|PREVIOUS_TRACK|NEXT_TRACK|PLAY_MEDIA|STOP|PLAY|BROWSE_MEDIA: 152115>, please create a bug report at https://github.com/koying/jellyfin_ha/issues and reference https://developers.home-assistant.io/blog/2023/12/28/support-feature-magic-numbers-deprecation
Therefore, with reference to #https://developers.home-assistant.io/blog/2023/12/28/support-feature-magic-numbers-deprecation, I send this bug report and hope the problem resolves before January 2025, even though a custom component is affected.