Therefore I advice not to update to Jellyfin Server 10.9 at the moment until the binding is adjusted.
@GiviMAD
Shall I create e.g. two issues? One for the id thingy and one for the migration to the current SDK. I can contribute - but progress will be slow … (a personal trait of mine; or the result of my involvement in too many things ).
with kind regards,
Patrik
Together with a sleep tracker and the HueSyncBox Binding (work in progress) it is possible to do nice automations - e.g. if you watch a movie, listen to music - or to switch of the music on you phone if the sleep tracker reports that you’re no longer awake
With the update to Jellyfin 10.10 the binding is no longer compatible:
2024-10-28 21:42:55.905 [ERROR] [.jellyfin.sdk.api.client.RawResponse] - Deserialization failed
kotlinx.serialization.SerializationException: org.jellyfin.sdk.model.api.GeneralCommandType does not contain element with name ',' at path $[0].Capabilities.SupportedCommands[1]
Even using the latest 1.4 SDK there are already issues with Jellyfin 10.9 (with based Android devices). For productive setups I recommend to use Jellyfin 10.8.
Update 2024-12-25
Fire TV and other Android TV based devices will update the Jellyfin client to the most recent version - which will not be compatible with the server version supported by openHAB. The latest supported client is 0.16.11. On some devices fortunately “side loading” of applications is possible. If you integrate the app into your setup, uninstall the official version and install the 0.16.11 .apk manually.
I started to evaluate possibilities to support recent and legacy server version with the official binding (Draft PR #17757) - but it will take months if/until some results can be expected (feel free to contribute ).
Finally I’m happy with the “prove of concept” to get rid of the dependency on the Android/Kotlin SDK. Unfortunately the generated code can not use the html client provided by core - but for a 1st implementation and a normal use case this should not be an issue. Especially as the current implementation creates separate connections as well.
As always, time is a scares commodity - and therefore I have the following question to the community: Do we still need support for legacy Jellyfin versions?
1st version should only support legacy servers (< 10.9)
legacy support for is not needed, support for current and supported server is enough
1st version should only support current version, but legacy support should be added later
0voters
I do not see a blocker for a server upgrade. Especially, as e.g. Fire-TV and other clients do not support pre 10.9 systems anymore. Supporting multiple API versions will require more resources, as there is more code to maintain. Therefore please add your arguments, if you need support for older versions. Else I’ll use the create infra. which is ready to support multiple API’s - but only implement support for the current stable and supported API.
I’m looking for testers for the new jellyfin binding. I can provide .jar file for 5.1.x version of openHAB. I will not publish this in the marketplace. Please send me a PM, if you can help to test the new binding.
Note: This a major re-write of the binding, so you will have to re-create the things (I have to look into how to automatically update an existing setup - not yet done). Help appreciated. If you miss a function, or channel now is the last call to have it added. I plan to plublish the PR for official review in the next 4-8 weeks.
Therefore I advice not to update to Jellyfin Server 10.9 at the moment until the binding is adjusted.
).
Update 2024-10-28 
).