[Feature]: Add Plex Support to What's Streaming Dashboard (WSD) #26
Description
💡 Feature Description
Add full support for Plex Media Server in the What's Streaming Dashboard ecosystem.
This would allow Plex users and server admins to benefit from all existing and upcoming WSD modules—such as user analytics, stream diagnostics, notifications, geo insights, and multi-server tools—without needing to migrate away from Plex.
📈 Motivation and Context
While WSD is built with Emby/Jellyfin in mind, a large user base (fanboys) still relies on Plex due to its early ecosystem, apps, and familiarity.
Adding Plex support provides:
- Broader adoption of WSD across communities
- A unified interface for multi-server admins (Plex + Emby + Jellyfin)
- A feature-rich dashboard that Plex users currently lack (especially for in-depth device, geo, and stream analytics)
- An alternative to Tautulli (which many Plex users find limiting or stagnant)
🛠️ Suggested Implementation (if known)
🔗 Authentication + API Access
- Use Plex token-based authentication (
X-Plex-Token) - Server discovery using Plex account or manual config of IPs
📡 Plex API Endpoints of Interest
/status/sessions— current playbacks and user activity/library/sections— media libraries and stats/accounts— user info and auth metadata- Webhooks — for media added, playback started/stopped
🔍 Feature Modules to Support
- Watch Stats: history, users, top content
- Geo IP Lookups: map IPs for streams
- Session Viewer: real-time dashboard of all active users
- Device Insights: streaming methods, devices, network types
- Notifications: alerts via Signal, Android app, email
- Multi-server view: add Plex as a peer alongside Emby/Jellyfin
🖼️ Visuals or References (optional)
- UI toggle: [☑] Include Plex Streams in WSD
- Side-by-side charts for Plex vs. Emby usage
🔗 Related Issues or Discussions
- [Multi-Server Dashboard Mode FR]
- [Geo Playback History Map]
- [Signal Notifications]
🧩 Additional Notes
- This feature is WIP and may be released in staged support (sessions first, then stats, then control tools)
- May require a separate Plex service adapter in WSD to unify session + metadata models
- Must respect Plex's Terms of Use and token handling requirements