Media information playing in a browser is not directly available to a small external hardware display.
Back to selected work
In ProgressAutomation · IoT / Experiments
YouTube Music × ESP32
Browser media metadata sent to a local ESP32 display.
- Role
- Developer · Experiment
- Period
- In progress
- Stack
- JavaScript · Chrome Extension APIs · ESP32 · HTTP · JSON
Project media
No verified project screenshot is published here. The public repository is linked for implementation evidence.
Overview
What the project needed to solve.
A Manifest V3 extension reads the active YouTube Music player state and relays a compact now-playing payload to an ESP32 HTTP endpoint on the same network.
Contribution
Responsibilities and shipped work.
The wording reflects contribution and maintenance work without claiming sole ownership.
- Created the Manifest V3 Chrome extension structure.
- Read title, artist, duration, playback position, and paused state from YouTube Music.
- Relayed browser data through a background service worker to a local HTTP endpoint.
- Kept the experiment clearly separated from finished production work.
Technology
Trace the stack back to the work.
Select a technology to see the projects where it is evidenced.
Where I used JavaScript
Engineering areas
Challenges handled in context.
Browser integration
YouTube Music exposes player data through changing page structures, so the content script checks several selectors and media elements.
Local device delivery
The background worker bridges a secure browser page to an HTTP device endpoint on the local network.
Work still in progress
The public repository currently demonstrates the browser-side prototype; hardware firmware and a complete packaged workflow are not presented as finished.
Highlights
What is evidenced by the work.
- Browser-to-device now-playing data flow.
- Compact HTTP/JSON payload designed for a local embedded target.
- Frequent playback state updates for a near-real-time display.