-
-
Notifications
You must be signed in to change notification settings - Fork 28.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Jellyfin Duplicate Chromecast Media Players #108276
Comments
Hey there @j-stienstra, @ctalkington, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) jellyfin documentation |
@crazystick On your Jellyfin server do you have DLNA "Play To" enabled?
It's the top checkbox under "Settings". I have a misbehaving Toshiba TV which was showing up as 200 separate DLNA cast targets. Turning that off has stopped it from happening, with the downside I can't use the DLNA Cast feature. |
@tim-hitchins-ekkosense I tried your suggestion but it doesn't seem to have improved matters. I removed and readded the integration which got rid of most of the entities, but they are still going up. |
the common issue is that devices are created based on the reporting that the session device supports persistent identifier. The client applications report this to the server but they usually use some method on the client device as the identifier and its expected to be persistent. However, client devices can regenerate identifier to improve privacy that can cause the identifier to be less persistent than thought. Think of it like resetting Google advertising IDs on Android devices. |
for chromecast, it's deriving deviceId by base64 the name of receiver or first sender ID or time. This likely leads to the growing list of devices. so it's actually not creating persistent identifier and properly reports However, in your diagnostics, most your chromecast seem to report |
I'm wondering if we should just ignore sessions where the device_id starts with "chromecast_" as it seems like these are transient sessions and keeping them around as entities wouldn't have any benefit |
The problem
Jellyfin creates a new Chromecast device/entity every time you play something using the native Jellyfin app on Android.
This seems to be the same as issue #105000 but since I don't use AppleTV I don't know what Swiftfin is so not sure what the resolution might be.
What version of Home Assistant Core has the issue?
core-2023.11.1
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant Container
Integration causing the issue
Jellyfin
Link to integration documentation on our website
No response
Diagnostics information
config_entry-jellyfin-787b9eb6dd7dfe73d109348717be4c1b.json.txt
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: