All Activity

Thanks but it's correct. OK odd, very odd. Any idea how that gets change in Emby without manually being changed? I almost missed what you were saying till I just went into /mnt/ and checked /My Files/ and /My Files II/. That should read /My Files II/Movies/Movies/. Watching something on the TV now so I'll fix anything in Emby that needs to be fixed and then test in abit. Will let you know what I get. Thanks for the nice catch.

Thanks for the explanation, that makes total sense! Yes, removing or clarifying that 'skipped' display would definitely prevent confusion. I'll let the scan finish and then test manual OCR detection on the failed shows.

Okay thanks for letting me know! I'll try that as soon as it's available.

I've been waiting to jump into intro/end credits workflows for a while now. If I understood things correctly, the best approach is to start using TheIntroDB plugin to get the timestamps from the community and whatever is not detected, run yocker's awesome solution, generate timestamps and that will contribute back to the TheIntroDB community via EmbyCredits?

Just a guess but Movies/Movies/ looks like a wrong mount.

Reminded me to add that this happens in both Emby apps on the Fire TV.

Reserved

EMBi – Emby integration for Home Assistant Hi everyone, I'd like to share EMBi, a community integration that brings Emby players and library information into Home Assistant. I use it myself and wanted an easy way to see what is playing, control supported players and keep the integration tidy. What can it do? Show Emby players with titles, artwork and playback progress; play, pause, stop and seek where the client supports remote control. Keep known players visible or show them only while playing or paused. Provide seven selectable sensors: movies, TV series, episodes, albums, tracks, active players and users watching. Configure the connection and sensors through the Home Assistant UI. No YAML is required to create the sensors. The optional dashboard examples below use card YAML. Offer English and German setup, options and sensor translations. Optionally clean up old entries from the Emby device history, manually or automatically. Automatic cleanup is off on a new installation. Active players are not the same as users watching. One person can use more than one player. The active-player sensor counts different device/app combinations that are playing or paused. Users watching counts each user once and excludes paused sessions. Active players also includes clients you have hidden from Home Assistant's player list. Installation: Add the repository to HACS as a custom Integration repository, install EMBi and restart Home Assistant. Then open Settings → Devices & services → Add integration → EMBi and enter your Emby connection details and API key. Requires Home Assistant 2026.7.2 or newer. When upgrading, enable the new Active players sensor in EMBi's options if desired; existing selections are preserved. Please read before using cleanup: Removing old Emby device-history records is at your own risk. Only selected device/client entries are removed — never your libraries, movies, series, music or user accounts. A removed client may need to sign in again. The optional HA cleanup also removes the corresponding EMBi player entries. Active or uncertain sessions are protected, but Emby's separate check/delete requests leave a small unavoidable timing window. Keep suitable backups. EMBi uses the emby domain and replaces HA's built-in Emby integration, so the custom-integration warning in Home Assistant is expected. Repository and installation guide: https://github.com/Seger85/home-assistant-embi Dashboard examples The first and third examples use community cards: Mushroom, auto-entities and mini-media-player. Install them separately through HACS. EMBi itself does not require them. The library card is a built-in Home Assistant card. Enable the required sensors and replace example IDs with your own where necessary. The player list follows the server of sensor.emby_active_players; replace that ID in both relevant cards if yours differs. Hidden player entities are absent from the card even when the server-wide sensor counts them. These original screenshots show my German dashboard with a custom theme; the examples use English labels. Colours and rounded corners depend on your theme. Step-by-step dashboard guide Active players double_tap_action: action: none entity: sensor.emby_active_players hold_action: action: none icon: mdi:cast-connected multiline_secondary: true primary: |- {% set count = states('sensor.emby_active_players') %} {% if count in ['unknown', 'unavailable'] %}Active Emby players currently unavailable {% elif count | int == 1 %}1 Emby player is active {% else %}{{ count | int }} Emby players are active{% endif %} secondary: What is playing? Playing and paused devices at a glance. tap_action: action: more-info type: custom:mushroom-template-card Library counts entities: - entity: sensor.emby_movie_count icon: mdi:movie name: Movies - entity: sensor.emby_tv_series_count icon: mdi:television-classic name: TV series - entity: sensor.emby_tv_episode_count icon: mdi:television-play name: Episodes title: My Emby library type: entities Player cards card: show_header_toggle: false state_color: true type: entities filter: template: | {% set entry = config_entry_id('sensor.emby_active_players') %} {% set ns = namespace(rows=[]) %} {% for player in expand(integration_entities('emby')) | selectattr('domain', 'eq', 'media_player') | list %} {% if entry and config_entry_id(player.entity_id) == entry and player.state in ['playing', 'paused'] %} {% set duration = player.attributes.get('media_duration') %} {% set position = player.attributes.get('media_position') %} {% set updated = as_timestamp(player.attributes.get('media_position_updated_at'), none) %} {% set elapsed = ([as_timestamp(now()) - updated, 0] | max) if player.state == 'playing' and updated is not none else 0 %} {% set invalid_runtime = duration is not number or position is not number or position < 0 or position + elapsed > duration %} {% set ns.rows = ns.rows + [{ 'entity': player.entity_id, 'type': 'custom:mini-media-player', 'artwork': 'material', 'hide': {'controls': false, 'volume': true, 'next': true, 'prev': true, 'runtime': invalid_runtime, 'info': false}, 'tap_action': {'action': 'more-info'} }] %} {% endif %} {% endfor %} {{ ns.rows }} show_empty: false sort: method: friendly_name type: custom:auto-entities I'd be happy to hear how it works with your Emby clients. For a problem report, please include your EMBi, Home Assistant and Emby versions and the client app. Check logs and screenshots for personal information before sharing them. GitHub Issues is the best place for reproducible bugs. EMBi is a community project, not an official Emby or Home Assistant product. Thanks to the Home Assistant, Emby and frontend-card communities for their work! EMBi – Emby-Integration für Home Assistant Hallo zusammen, ich möchte euch EMBi vorstellen: eine Community-Integration, mit der ihr Emby-Player und Informationen zur Mediathek direkt in Home Assistant nutzen könnt. Ich nutze sie selbst und wollte einfach sehen, was gerade läuft, unterstützte Player steuern und die Integration übersichtlich halten. Was kann EMBi? Emby-Player mit Titel, Cover und Fortschritt anzeigen und steuern: Wiedergabe, Pause, Stopp und Spulen, soweit die jeweilige App Fernsteuerung unterstützt. Bekannte Player behalten oder nur während Wiedergabe und Pause anzeigen. Sieben einzeln wählbare Sensoren bereitstellen: Filme, Serien, Episoden, Alben, Musiktitel, aktive Player und schauende Benutzer. Verbindung und Sensoren über die Home-Assistant-Oberfläche einrichten. Für die Sensoren braucht ihr keinen YAML-Code. Nur die optionalen Dashboard-Beispiele unten verwenden Karten-YAML. Einrichtung, Optionen und Sensornamen auf Deutsch und Englisch anzeigen. Auf Wunsch alte Einträge aus der Emby-Gerätehistorie manuell oder automatisch aufräumen. Bei einer neuen Einrichtung ist die Automatik ausgeschaltet. Aktive Player sind nicht dasselbe wie schauende Benutzer. Eine Person kann mehrere Player nutzen. Der Player-Sensor zählt unterschiedliche Geräte-/App-Kombinationen mit Wiedergabe oder Pause. Der Benutzersensor zählt jeden Benutzer mit laufender Wiedergabe einmal; Pause zählt dort nicht mit. Auch in HA ausgeblendete Clients können im serverweiten Player-Sensor mitgezählt werden. Installation: Das Repository in HACS als benutzerdefiniertes Repository der Kategorie Integration hinzufügen, EMBi installieren und Home Assistant neu starten. Danach unter Einstellungen → Geräte & Dienste → Integration hinzufügen → EMBi die Emby-Verbindung und den API-Schlüssel eintragen. Voraussetzung ist Home Assistant 2026.7.2 oder neuer. Beim Update bleibt eure Sensorauswahl erhalten; den neuen Sensor Aktive Player könnt ihr in den EMBi-Optionen einschalten. Bitte vor dem Aufräumen lesen: Das Entfernen alter Einträge aus der Emby-Gerätehistorie geschieht auf eigene Gefahr. Gelöscht werden nur ausgewählte Geräte-/Client-Einträge — keine Bibliotheken, Filme, Serien, Musikdateien oder Benutzerkonten. Ein betroffener Client muss sich eventuell erneut anmelden. Optional entfernt EMBi auch die passenden eigenen HA-Player-Einträge. Aktive und nicht eindeutig beurteilbare Sitzungen werden geschützt. Zwischen letzter Prüfung und Löschung bleibt wegen der getrennten Emby-API-Aufrufe ein kleines technisches Zeitfenster. Denkt daher an passende Backups. EMBi verwendet die Domain emby und ersetzt die eingebaute Emby-Integration. Der entsprechende Hinweis auf eine benutzerdefinierte Integration in Home Assistant ist deshalb normal. Repository und deutsche Anleitung: https://github.com/Seger85/home-assistant-embi/blob/main/README.de.md Beispiele für euer Dashboard Für die erste und dritte Karte braucht ihr diese Community-Erweiterungen: Mushroom, auto-entities und mini-media-player. Ihr könnt sie separat über HACS installieren. EMBi selbst benötigt sie nicht. Die Mediathekskarte ist eine normale Home-Assistant-Karte. Schaltet die benötigten Sensoren ein und passt bei Bedarf die Beispiel-IDs an. Die Playerliste gehört zum Server von sensor.emby_active_players; ersetzt diese ID gegebenenfalls in beiden betreffenden Karten. Ausgeblendete Player erscheinen nicht in der Kartenliste, können aber im serverweiten Sensor mitzählen. Die Originalbilder zeigen mein Dashboard mit eigenem Theme. Farben und Rundungen können bei euch anders aussehen. Schritt-für-Schritt-Anleitung für die Karten Aktive Player double_tap_action: action: none entity: sensor.emby_active_players hold_action: action: none icon: mdi:cast-connected multiline_secondary: true primary: |- {% set count = states('sensor.emby_active_players') %} {% if count in ['unknown', 'unavailable'] %}Aktive Emby-Player derzeit nicht verfügbar {% elif count | int == 1 %}1 Emby-Player ist aktiv {% else %}{{ count | int }} Emby-Player sind aktiv{% endif %} secondary: Was läuft gerade? Wiedergabe und Pause im Überblick. tap_action: action: more-info type: custom:mushroom-template-card Mediathek entities: - entity: sensor.emby_movie_count icon: mdi:movie name: Filme - entity: sensor.emby_tv_series_count icon: mdi:television-classic name: Serien - entity: sensor.emby_tv_episode_count icon: mdi:television-play name: Episoden title: Meine Emby-Mediathek type: entities Wiedergabekarten card: show_header_toggle: false state_color: true type: entities filter: template: | {% set entry = config_entry_id('sensor.emby_active_players') %} {% set ns = namespace(rows=[]) %} {% for player in expand(integration_entities('emby')) | selectattr('domain', 'eq', 'media_player') | list %} {% if entry and config_entry_id(player.entity_id) == entry and player.state in ['playing', 'paused'] %} {% set duration = player.attributes.get('media_duration') %} {% set position = player.attributes.get('media_position') %} {% set updated = as_timestamp(player.attributes.get('media_position_updated_at'), none) %} {% set elapsed = ([as_timestamp(now()) - updated, 0] | max) if player.state == 'playing' and updated is not none else 0 %} {% set invalid_runtime = duration is not number or position is not number or position < 0 or position + elapsed > duration %} {% set ns.rows = ns.rows + [{ 'entity': player.entity_id, 'type': 'custom:mini-media-player', 'artwork': 'material', 'hide': {'controls': false, 'volume': true, 'next': true, 'prev': true, 'runtime': invalid_runtime, 'info': false}, 'tap_action': {'action': 'more-info'} }] %} {% endif %} {% endfor %} {{ ns.rows }} show_empty: false sort: method: friendly_name type: custom:auto-entities Ich freue mich über eure Erfahrungen mit unterschiedlichen Emby-Clients. Wenn etwas nicht klappt, nennt bitte EMBi-, Home-Assistant- und Emby-Version sowie die verwendete Client-App. Prüft Logs und Screenshots vor dem Teilen auf persönliche Angaben. Nachvollziehbare Fehler meldet ihr am besten über GitHub Issues. EMBi ist ein Community-Projekt und kein offizielles Produkt von Emby oder Home Assistant. Danke an die Home-Assistant-, Emby- und Karten-Community für ihre Arbeit!

Bonjour Le site ne fonctionne plus impossible d'effectuer une recherche .

I think versions and how it is working is not great. I have two source for my media. They are identical files. Primary is my preferred location as it has unlimited bandwidth. Secondary is more restricted, hence it is okay good as a backup in an event where the primary is down. Let's say for episode one I have I have 'series name - S01E01 - #1 Primary' and ''series name - S01E01 - #2 Secondary' it is randomly showing #1 for one episode and another episode it is showing #2 randomly, no pattern at all. If you don't allow us to select a default in setting, at least allow us to forcefully identity the default as needed or display the source in alphabetical order.

Please delete my account

I should remove that from being shown as they are not truly "skipped". Chroma needs other episodes to compare the sound to before it knows what is the credit transition and there for what to look for. The skipped you see are just episodes it used for the comparison and not episodes it actually ran the detection on hence the "Only needed for audio comparison". There are also other reasons episodes are skipped, like for example they already have been run though detection, they are configured to be skipped in the rules sections and/or they failed previously (if that setting has been enabled). They are simply skipped to save time and not having to re-run detection every time on them when not needed. Quick disclaimer. The plugin's detection is not perfect, it needs episodes to either have the same music or a black scene transition. If none of those are there it will fail. Using OCR can help with that as almost all TV shows use credit scenes with text. As long as the OCR is set to look for the correct keywords and the text is not some strange fuzzy or stylized text, like anime tend to have, it will find the credits. This requires a bigger computer though as it's basically a small AI that is used to read the text. While OCR works and is in general more precise than the other detections i don't use it my self, the small Dell machine i have for my Emby is too small for it. Only my test and main machine have the horse power to run it. TL:DR. If you feel like there are too many failed episodes you can try and run manual detection on them again one TV show at a time. If you think they shouldn't have failed then send me a log from the "dry run with debug" and i will look at it. (One TV show at a time please so i don't get a 50MB log ).

If you want, I can give you the css file and you can use it.

Salut tuturor, Caut sfaturi despre cum să optimizez timpul inițial de deschidere a aplicației Emby pe iOS și Android. În prezent, de fiecare dată când deschid aplicația prin intermediul datelor celulare (4G/5G), există o întârziere de 3 până la 5 secunde pe ecranul de conectare înainte de încărcarea ecranului principal. Latența ping-ului către rețeaua mea este extrem de mică (~3-5 ms), iar redarea funcționează perfect, fără buffering odată conectat, așa că lățimea de bandă/ISP-ul nu reprezintă o problemă. Am testat două metode diferite de acces, dar ambele produc aceeași întârziere inițială a conexiunii de 3-5 secunde: 1. Redirecționare directă a porturilor: Portul 8920 a fost redirecționat direct în router către Emby. Certificat SSL personalizat valid (.pfx) încărcat direct în setările serverului Emby folosind DNS dinamic al furnizorului de servicii Internet (ISP). Viteză maximă, fără limitare sau accelerare a ratei DNS. 1. Proxy invers Apache (Port 443 HTTPS): Rutare subdomeniu către http://localhost:8095 cu HTTP/2 activat și certificate SSL valide. Configurație Apache personalizată care gestionează WebSockets, cifruri SSL, HSTS și antete proxy. Întrucât ambele metode produc exact aceeași întârziere de 3-5 secunde la pornire, presupun că aplicația ar putea rula prin verificări interne de timeout ale rețelei (de exemplu, încercând o rezervă LAN înainte de a trece la WAN) sau prin întârzieri de handshaking TLS. Iată configurația mea Apache VirtualHost pentru referință: <VirtualHost *:443> Nume server emby.domain.com Protocoale h2 http/1.1 Motorul SSL este activat Fișierul Certificat SSLC „C:/Apache24/conf/ssl/Certificate-Apache/server.pem” Fișierul SSLCertificateKey „C:/Apache24/conf/ssl/Certificate-Apache/server.pem” Protocol SSL toate -SSLv2 -SSLv3 -TLSv1 -TLSv1.1 SSLCipherSuite ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305 SSLHonorCipherComandă pe Compresie SSL dezactivată ProxyTimeout 86400 Expirare 86400 Mențineți activ Cereri MaxKeepAlive 100 Timeout KeepAlive 10 Cereri proxy dezactivate ProxyPreserveHost activat <LocationMatch "^/web/startup/manuallogin.html$"> Antetul este întotdeauna setat la Cache-Control „no-cache, no-store, must-revalidate, max-age=0” Antetul este întotdeauna setat la Pragma „no-cache” Antetul este întotdeauna setat la Expiră la „0” </LocationMatch> <LocationMatch "^/web/videoosd/videoosd.html$"> Antetul este întotdeauna setat la Cache-Control „no-cache, no-store, must-revalidate, max-age=0” Antetul este întotdeauna setat la Pragma „no-cache” Antetul este întotdeauna setat la Expiră la „0” </LocationMatch> <LocationMatch "^/web/videoosd/.*.(html|js|css)$"> Antetul este întotdeauna setat la Cache-Control „no-cache, no-store, must-revalidate, max-age=0” Antetul este întotdeauna setat la Pragma „no-cache” Antetul este întotdeauna setat la Expiră la „0” </LocationMatch> <LocationMatch "^/web/modules/common/strings/.*.json$"> Antetul este întotdeauna setat la Cache-Control „no-cache, no-store, must-revalidate, max-age=0” Antetul este întotdeauna setat la Pragma „no-cache” Antetul este întotdeauna setat la Expiră la „0” </LocationMatch> <LocationMatch "^/web/strings/.*.json$"> Antetul este întotdeauna setat la Cache-Control „no-cache, no-store, must-revalidate, max-age=0” Antetul este întotdeauna setat la Pragma „no-cache” Antetul este întotdeauna setat la Expiră la „0” </LocationMatch> Motor de rescriere activat RewriteCond %{HTTP:Upgrade} =websocket [NC] Actualizare RewriteCond %{HTTP:Conexiune} [NC] RewriteRule ^/?(.*) "ws://localhost:8095/$1" [P,L] ProxyPass / http://localhost:8095/ flushpackets=on timeout=86400 ProxyPassReverse / http://localhost:8095/ Antetul este întotdeauna setat la X-Robots-Tag ca „all” Antetul este întotdeauna setat la X-Content-Type-Options ca „nosniff” Antetul este întotdeauna setat la opțiunile X-Frame „DENY” Antetul este întotdeauna setat la X-XSS-Protection „1; mode=block” Antetul este întotdeauna setat la politica de referire „no-referrer-when-downgrade” Antetul este întotdeauna setat la Strict-Transport-Security „max-age= 63072000 ; includeSubDomains; preload” DocumentRoot „C:/Apache24/htdocs_PRIVATE/pages-errors-emby” <Directorul "C:/Apache24/htdocs_PRIVATE/pages-errors-emby"> Opțiuni -Indici PermiteSuprascriere Niciuna Solicitați toate acordurile </Director> RewriteCond %{ENV:REDIRECT_STATUS} 503 RewriteRule ^(.*)$ /503.html [L] <Fișiere "503.html"> Antetul este întotdeauna setat ca stare „503 Serviciu indisponibil” </Fișiere> ErrorLog „logs/emby.domain.com-error.log” Log personalizat „logs/emby.domain.com-access.log” combinat </VirtualHost> Există ceva ce pot modifica pe partea de server/proxy sau în setările clientului pentru a ocoli aceste câteva secunde de întârziere și a obține o conexiune aproape instantanee la lansarea aplicațiilor mobile? Mulţumesc! ScreenRecording_09-26-2026 12-59-42_1.mp4

Thanks for clarifying! Just to be sure I understand correctly: are the ~17,000 'skipped' episodes actually considered successful because the timings were resolved through batch audio comparison (since it says 'Only needed for audio comparison'), meaning only the ~4,600 'failed' episodes need OCR fallback?

For movies I have in 4K with an audio commentary, I only have the commentary on the 1080p version so I definitely wouldn't want that hidden.

Chroma/Hash detection needs either the same music between episodes or a black scene transition. If none of those are in the episodes then the detection will fail. A propper set up OCR can help with that, yes.

Hallo zusammen, mich würde mal brennend interessieren, nach welchem System ihr eure Schallplatten/CD's im Regal organisiert. Sortiert ihr strikt alphabetisch nach Künstlern, nach Genre, chronologisch nach Erscheinungsjahr oder sogar nach Stimmungen? Bei wachsender Sammlung steht man ja immer wieder vor der Frage, wie man am schnellsten findet, worauf man gerade Lust hat. Da ich selbst vor dem Problem stand, meine eigene Sammlung ordentlich und übersichtlich zu visualisieren, habe ich eine kleine Webanwendung programmiert: Discify Mit dem Tool lässt sich die eigene Discogs-Sammlung visuell aufbereiten und entspannt durchstöbern. Das Ganze ist komplett kostenlos und ohne Schnickschnack. Ich würde mich freuen, wenn ihr es mal ausprobiert! Wie behaltet ihr bisher digital und analog den Überblick – und was haltet ihr von meinem Tool? Ich bin gespannt auf eure Systeme und Feedback!

Thanks @Luke Of course, no ned to separate, but it would be good to know if it's movie or show or self e.t.c. .

Can’t edit post above but it’s suppose to say: This way as well means that there’s only 1 library and 1 entry of the movie. In plex I had to have separate remux libraries, which got messy, so this way, the user doesn’t even know that there are versions unless they have the correct hardware but can choose an edition if they fancy it - makes it much simpler. having 1 complete movie library, controllable by folder, was a primary reason to move to emby, as it simplified the presentation for users. All they see is a movie section but for more technically savvy users and with the correct hardware, they get access to additional options.

@yockerDo you know why I have nearly 17,000 skipped episodes? I don't have the log file yet, should I enable OCR? @sydlexiusthank you

am already using it thanx man

I too split movies by version and edition and would ultimately like to choose the combination. My setup is: Possible versions: 4K full disc, 1080p, and some old legacy 720p for mobile If it’s a good movie with decent sound I will remux it in a separate 4K remux folder but mainly my discs get stripped to something more resembling web-dl/1080p with lossy sound. By putting the remux in a separate folder but linked to the same library I can limit who sees them as it needs an Nvidia shield and decent internet to play properly, so at my brothers house he has this and I enable it but my parents use tv app, so they just see the standard 1080p folder. Possible editions: director, theatrical etc. So, 2 dropdowns would be most elegant, which are contextually aware of each other, so it will only populate the files available. 1) Pick edition first and then 2) it displays available versions associated with that version. If there’s only one edition and multiple versions it just unlocks the dropdown for versions and if there’s multiple versions, it will keep locked or unlock versions dropdown accordingly - simples

Hi there, I provided the log output above. Isn't that a specific example?