EUR full-term totals: 1 month €8.99 · 3 months €21.99 · 6 months €35.99 · 12 months €49.99 Compare plans →
Menu

Player apps

JellyCon home shortcut: use the actual skin’s library node

Create navigation to the intended server library without expecting every Kodi skin to expose identical widget controls.

Identify the player before signing in

Define the destination, not only the menu label

A Kodi home-screen label can point to many different destinations. Begin by deciding whether the shortcut should open one Jellyfin library, a global list or another supported JellyCon node. A menu called Movies does not prove which server or user supplies its content.

Confirm the desired library opens correctly through the ordinary JellyCon add-on view first. Keep the server, viewer and library name in private notes. A home customization should be built on a working destination rather than used to conceal an unresolved connection or access problem.

Use the skin’s actual customization capability

The guide’s skin-dependent examples select JellyCon nodes as links or widgets. Inspect the controls offered by the installed skin and version. For an original navigation example, a label chosen for a household should lead to the library that household actually uses, not a similarly named global list from another account.

Preserve the existing home arrangement before changing it. Add one harmless shortcut with an understandable label and select the intended node through the skin’s supported route. Keep the label separate from the destination so a later renamed library can be checked precisely.

Test the shortcut and any widget independently

Activate the new shortcut and confirm the actual library contents. Then inspect any widget configured to show recent or next-up items. A working library link and a correctly filtered widget are separate results. The viewer’s history can affect a next-up list independently of the skin.

Open one known authorized item and return through the intended navigation. If the home link opens a different server or profile, preserve that actual destination before editing more labels. Repeated cosmetic changes do not resolve an underlying user selection.

Retain the working route with its version context

Restart Kodi normally and verify the intended home entry still leads to the same node. Keep the skin and JellyCon versions with the final route. A later skin update can change the editing interface without changing the actual server library.

The expected outcome is understandable navigation to a known JellyCon destination. It does not synchronize the server into Kodi’s local database, grant extra content access or guarantee identical widget behavior in every skin. Preserve the ordinary add-on route as a fallback while the custom home layout is assessed.

Questions answered

Does a home label named Movies prove it uses Kodi’s local database?

No. Inspect its actual destination. A skin entry can point to a JellyCon server node.

Why test the widget separately from the shortcut?

They can request different lists or filters. A working library link does not prove the widget’s source and viewer state are correct.

Sources & further reading

Official references for the subjects discussed. Service terms and device software can change.

Your next step

A better setup starts with the right details.

Tell us your device model, viewing country and the programmes you want to discuss.

Talk on WhatsApp

+44 7532 814802

WhatsApp ↗↑ Top