All Activity

Thanks for the feedback, Alexa has been updated, can you please try again?

Thanks, I will have a look

These two as well:

These plugins manage to overlay icons on posters. your plugin might not need to to do the overlay, just maintain the tags that another plugin can use to drive? Doing it via collections is a reasonable idea but maybe your "lane" is to off the management of tags, and another plugin do image overlay or collection building from tags, just a idea...

Hi, I did a restore to my new emby windows box yesterday and noticed the playlists were empty. I know why this is, because the libary and drive letters have changed. I found the M3u files and edited the paths, restarted Emby server. They are still empty. Is there anything else that can be done? Thanks

Whichever one you want. I believe QM said he uses kodinerds' version of Estuary for his testing, but I've used Arctic Fuse 3 and Arctic Zephyr Rounded without issue.

Thanks — good suggestion, and I've looked into what's actually possible rather than guessing. Splitting it into three parts, because they have different answers. What already works today, on every client Turn on "Prepend status to show description" in the plugin settings. It writes the status into the show's real description field, which every Emby client reads natively — Android TV, tvOS, iOS, web, all of them. You'll see things like "Returning Series 26 Jul 2026" or "Ended" at the start of the description on the show's page. No permissions to change, nothing platform-specific. It's the one route that works everywhere. What can't be done — and why An icon or badge drawn onto the poster, visible on all clients. The only plugin hook Emby provides for this is IImageEnhancer, and Emby's own team have confirmed that no client actually requests enhanced images. There's no server-side override to force it. It isn't a case of me not having built it — there's no working extension point to build it on. Status text under the posters in Continue Watching or library browse. Those grid views only render the item's title. A plugin can't add a second line, and the description field isn't shown there. The only way to get text under a poster would be to write it into the actual title — "Breaking Bad (Series Ended)" — which would wreck sorting and search.It would be too high of a price for a label, so unfortunately it can't be done. What I think would actually solve your problem better You said you don't start a show unless the season has finished. Rather than hunting for an icon on a poster, the plugin could maintain auto-updating collections — "Season Complete", "Series Ended", "Season Premiere This Week". Collections are a native Emby feature, so they show up properly on Android TV and every other client with no hacks at all, and you'd browse the finished shows as a list instead of scanning artwork. That's a bigger job than a badge and I'd want to prototype it before promising anything, but it's the one approach here that isn't fighting the platform.

thanks, maybe some caching issue here, will take a look

Thanks for creating the service! I have it setup and am having an issue. Some movies play just fine but others wont. These same movies play fine using Emby. I have tried from the library and both nodes in the video plugin. I have also tried reinstalling and on different systems. Any idea what may be the cause? Thanks

I have no issues displaying custom (16:9) genre images in either app. How to Report a Problem

Hello Is there any option for that or isn't this supported yet? I replaced genre images with 16:9 images, they show fine on IOS app, but I still see the auto generated genre images on Android mobile and Android TV version of Emby. BR

jinx

The new home screen settings (including spotlight, etc) were added to the AndroidTV app in v2.1.48

Nope, they both support the new home screen rows. Android TV app arguably does it better.

resuming still does not work on Emby Server v4.10.0.26. Any update about that? BR

@Blueskies278Thanks for plugin. Suggestion - I wonder wether the plugin could manage a tag(s) on media items. So that any overlay plugin (eg iconic or I think there is a free one now) could put an icon on movies, series, seasons, episodes that would be visible accross the entire emby ecosystem/all clients. I would love it if when i viewed continue watching and library on my android Tv i could see things like (Season Premier), Season Ended, Series Ended. So i knew when to start watching something (i dont start somethign unless its season is at least finnished).

Emby For Android is the only one that works with the new home screen features, right?

If there are no major bugs, I will request for the plugin to be added to the plugin catalog, if Emby agrees. If you are not that bothered about the icons and are happy with the plain text, it will be a simple install via the catalog and you will be good to go.

nevermind. Just needed to add some more images with that ratio. It was adjusted automatically then. BR

The genre images look very nice. Unfortunately Emby doesn't seem to be able to show them in the right format 16:9. I am getting black bars up and down on all clients. @ebrany chance adjusting that?

TV Show Status 2.5.21.0 Covering 2.5.18.0 → 2.5.21.0. The versions in between were tested but never released, so everything is gathered here. Two things in this release: The badge survives an Emby update — it comes back on its own, no restart The fix instructions are now correct on every platform — Windows, macOS, Linux and Docker Fixed — the badge repairs itself No more disappearing after an Emby update. Every update rebuilds Emby's web folder, deleting the badge script and the <script> tag that loads it. The badge used to stay gone until you restarted Emby. The plugin now re-checks and puts both back on its own. Recovery is fast. The check normally runs every 5 minutes, but drops to every 20 seconds the moment it finds the badge missing, and returns to 5 minutes once restored. It backs off after about 5 minutes of failed attempts, so a permission problem nobody has fixed doesn't become a permanent retry loop. Opening the settings page forces an immediate check, rather than showing the result of the last startup, which could be days old. Failed retries no longer fill the log with errors. The first failure is logged once, retries are silent, and recovery logs a single line saying how many attempts it took. Why a restart was the only thing that worked before Worth setting out, because the cause wasn't where it looked. The plugin deployed its script at exactly two moments: server startup, and when you pressed Save. On Docker, startup is the one moment after an update when the web folder is guaranteed unwritable — the update has just rebuilt it as root, and Emby runs as another user. So the deploy always ran at the worst possible moment, failed, and nothing ever looked again. That's why running the chown by hand only appeared to work when paired with a restart. The chown was doing its job. There was simply nothing left running that would try the deploy a second time. The fix isn't "retry faster" — it's "retry at all". Fixed — instructions that work on your platform The status box tells you how to fix a permission problem. On two platforms it was telling you something that couldn't work. macOS — it printed a path inside Server.app. The bundle is EmbyServer.app, so that folder never existed. Unreported because very few people run Emby Server on a Mac. Linux — there was no native Linux branch at all. Anyone not on Windows or macOS was assumed to be on Docker and handed a docker exec command, which is no use if you installed from a .deb or .rpm. Windows was correct, and still is. Changed Paths are no longer hardcoded. The plugin prints the path it actually resolved at runtime. That's exact on every platform and every install layout, and unlike a literal string it can't fall out of date when Emby changes something. Docker is detected, via /.dockerenv, rather than assumed for anything that isn't Windows or macOS. The permission message is a one-off setup step, not something to repeat after every update. The recommended cron interval is now every minute, not every five. Measured at about 75 ms per run — 0.125% of one core. Measured On a real update to 4.10.0.27, from the server log: ┏━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓ ┃ Time ┃ Event ┃ ┣━━━━━━━━━━╋━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┫ ┃ 10:15:29 ┃ Emby starts after the update ┃ ┣━━━━━━━━━━╋━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┫ ┃ 10:15:30 ┃ First deploy attempt - permission denied ┃ ┣━━━━━━━━━━╋━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┫ ┃ 10:20:00 ┃ Cron repairs the folder ownership ┃ ┣━━━━━━━━━━╋━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┫ ┃ 10:20:40 ┃ Badge restored ┃ ┗━━━━━━━━━━┻━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛ 5 minutes 11 seconds unattended — and of that, the plugin accounted for 40 seconds. The other four and a half minutes was waiting for the next cron tick, because cron was on a 5-minute schedule at the time. That's why the recommended cron line is now every minute. With ownership repaired within 60 seconds, expect roughly two minutes rather than five. That figure is a projection from the measurements above rather than a second timed update — the 5m11s is the one that was actually observed. Setup by platform The plugin retries on its own, but it can't grant itself permission. If the status box reports a problem, this is the one-off fix. The exact path for your system is shown in the status box itself — the paths below are typical, not universal. Docker / NAS The only platform that needs a recurring repair, because every Emby image update resets ownership. Fix it now, on your Docker host: docker exec -u root <container> chown -R 1000:1000 /system/dashboard-ui Then add the same command to cron once, and you never see the message again: * * * * * docker exec -u root <container> chown -R 1000:1000 /system/dashboard-ui Linux (native install, .deb / .rpm) sudo chown -R emby:emby "<path from the status box>" If your service runs as a different account, substitute it. Check with: systemctl show -p User emby-server macOS sudo chown -R $(whoami) "<path from the status box>" Windows Grant the account Emby Server runs as full control of the folder shown in the status box, then restart the service. You may need to do this as an administrator. In every case The badge returns within a few minutes. No restart, no Save — the plugin re-checks on its own. If the status box is green but you still can't see badges, your browser is holding the old page. A hard refresh — Ctrl+Shift+R, or Cmd+Shift+R on a Mac — brings them straight back. Worth knowing This plugin runs on every platform — NAS/Docker, Linux, Windows and macOS. Every path it uses is resolved from Emby itself rather than written into the code, so there's nothing platform-specific to install. Docker is the only one needing the cron line, and only because Docker resets folder ownership on every image update. The check is silent when everything is fine. Two file reads, no network traffic, no log entries. It only acts when the badge is actually missing. It's separate from the 15-minute TMDB refresh loop. Checking the badge is cheap and can run often; calling TMDB is not and shouldn't. The first check runs 2 minutes after startup, by which time the container has settled and any ownership repair has usually happened — so the retry succeeds unattended. Installing Copy EmbyTVShowStatus.dll into your Emby plugins folder Restart Emby Open the plugin's settings page and check the status box If it reports a permission problem, run the command it gives you Docker only: add the cron line above, once Unlike previous releases, there's no step to repeat after future Emby updates. Known limits, unchanged Web browser client only. The badge can't be shown on the native apps — Emby's own team confirmed no client requests enhanced images and there's no server-side override. "Prepend status to show description" is the option that works on every client, including Android and tvOS. The <script> tag has to be written into Emby's web folder. There is no plugin API for injecting into the shipped web client — checked against the SDK on 20 August 2026. IHasWebPages and the related interfaces all serve a file at a URL; none of them modify index.html. EmbyTVShowStatus.dll TVShowStatus-2.5.21.0.pdf

@Luke I think the new server 4.10.0.27 and app 3.5.47 only made things worse. It used to show the splash screen and then a quick flash of the connection screen (which was unreadable because it was so fast) and then the home screen. It was a real quick. Now I see the splash screen a spinning circle shows up and the connection screen is visible for a short period of time before I get the home screen. The whole process is slower. It's looks like it's not even trying to connect before the connection screen pops up. What it looks like to me is that there was time added AFTER the connection screen pops up and then it connects. What I was hoping for is that it would try to connect and then ONLY IF it didn't connect in X seconds the pop up would be displayed.

Tienes razón, él no tiene conocimientos avanzados y por eso batallamos. ¿Cómo se puede comprobar si el servidor del celular está parado y qué pasos exactos debe hacer él desde su Android para volver a encenderlo o iniciarlo, considerando que al abrir la app ya no le detecta nada tras pedirnos volver a iniciar sesión? La vdd no tengo conocimiento de esta app pero es extraño lo que sucedió hay forma de que un administrador pueda configurar algo ¿?

"

En principio, es posible instalar un servidor en el celular, pero sin conocimientos lo dudo. ¿Como conectó los contenidos al servidor de celular? Si realmente es así, cosa que dudo, el servidor del celular está parado.