Jellyfin integration incorrect values for media count

[seankim2398]

Description

Currently on v1.10.1 for Homepage with Jellyfin integration, I don't get the correct values reported by Jellyfin.

Here are the actual numbers for my media:

Here are the values reported by homepage:

homepage version

v1.10.1

Installation method

Docker

Configuration

- Jellyfin:
        icon: jellyfin.png
        href: {placeholder}
        description: Media Server
        server: my-docker
        container: jellyfin
        showStats: true
        widget:
            type: jellyfin
            url: http://jellyfin:8096
            key: {placeholder}
            enableBlocks: true
            enableNowPlaying: true
            enableUser: true
            enableMediaControl: false
            showEpisodeNumber: true
            expandOneStreamToTwoRows: false

Container Logs

No response

Browser Logs

No response

Troubleshooting

Restarting the service, clearing browser cache, looking for similar issues to potentially resolve this issue.

[shamoon]

Hello. Those are not the actual troubleshooting steps form the support template, please do those and post the output. In particular the api output would likely be helpful here since of course homepage isn’t making the numbers up and the basic logic hasn’t changed in ages

[avenger49]

I'm seeing the same issue as the OP. If you can provide the steps to get the api output, I'd be happy to grab that. I'm 1.12.3.

[shamoon]

The template links to https://gethomepage.dev/troubleshooting/#service-widget-errors specifically step 4 is what we’re talking about. Those are generic instructions of course, an LLM is a good way to get more specifics

[shamoon]

jellyfin/jellyfin#13970

[bncanxby]

Adding to this thread since I ran into the same issue and did some deeper investigation that might be useful.

I'm aware the maintainer @shamoon already linked jellyfin/jellyfin#13970, and I agree the root cause is on the Jellyfin side. However, since that issue has been open for a while with no fix in sight, I'd like to propose a workaround that could be implemented on the Homepage side.

---

The issue

The Jellyfin widget displays incorrect statistics when using an admin API key — it shows aggregated counts across all users instead of the counts for a specific user/library. This is because the API sums up the counts across all accounts on the server, resulting in heavily inflated numbers.

	Widget (incorrect)	Jellyfin dashboard (actual)
🎬 Movies	1,501	505
📺 Series	682	221
📺 Episodes	24,215	8,476

---

Investigation steps

To confirm the root cause, I did the following:

1. Verified there were no duplicate libraries in Jellyfin — all libraries were unique and correct.

2. Called the API directly to check what Homepage was actually receiving:

GET http://nas-ip:8096/Items/Counts?api_key=YOUR_KEY

This returned the same inflated numbers shown in the widget, confirming the issue is in the API response itself.

3. Retrieved the list of users to get the correct userId:

GET http://nas-ip:8096/Users?api_key=YOUR_KEY

This returns all users — the Id field of the desired user is needed for the next step.

4. Called the API with a specific userId to verify per-user counts:

GET http://nas-ip:8096/Items/Counts?userId=USER_ID&api_key=YOUR_KEY

This returned the correct numbers, matching what Jellyfin shows in its own dashboard.

5. Checked the Homepage widget source code and found the endpoint is hardcoded without any user filter:

Count: {
  endpoint: "emby/Items/Counts?api_key={key}",
},

There is no way to pass a userId from the YAML config — it is simply not supported.

---

Proposed workaround (Homepage side)

Since the Jellyfin API does return correct numbers when a userId is passed, it would be great to support an optional userId parameter in the widget config:

emby/Items/Counts?api_key={key}&userId={userId}

Proposed widget config:

widget:
  type: jellyfin
  url: http://your-nas:8096
  key: YOUR_API_KEY
  userId: YOUR_USER_ID  # optional

The userId can be retrieved by calling:

GET http://nas-ip:8096/Users?api_key=YOUR_KEY

and looking at the Id field of the desired user.

Tested on Jellyfin 10.11.11 and Homepage latest.

---

⚠️ Disclaimer: I am not a developer and have limited coding knowledge. The troubleshooting process and this write-up were done with the help of Claude (AI assistant by Anthropic). I hope the information is still useful and accurate enough to be actionable!

[buffaloexpatbill]

I'm curious, typically API keys are associated with a user. Are you able to generate a key for the presumably non admin user and configure that key for the Jellyfin widget?