A custom HTML5 dashboard that displays real-time temperature and humidity readings from sensors across the apartment. It consumes data from InfluxDB via the Flux query API and visualizes it with Chart.js, auto-refreshing every 30 seconds.
+ +The dashboard sits at the end of a sensor data pipeline that starts at physical devices scattered around the flat:
+sensoren bucket, organized by org Heimnetzwerk.The dashboard monitors 10 rooms across the apartment: server room, balcony, living room (desk and iMac areas), kitchen, bathroom, hallway, study, children's room, and bedroom. Each room shows current temperature and humidity, with optional pressure and light-level readings where sensors support it.
+ +The air quality dashboard is a standalone page, separate from the main home dashboard and the Tasmota energy monitoring setup. It shares the same InfluxDB instance and MQTT infrastructure but queries different measurement types (temperature/humidity vs. power/energy). The home dashboard shows a summary of room temperatures alongside energy data, while this dashboard provides the detailed view with historical charts for climate monitoring specifically.
+ +The plug collection has grown over time as different brands became available at different price points. Gosund P1 multi-socket strips handle areas with multiple devices, while the SP112 single sockets cover dedicated appliances. Eightree plugs are ESP32-based and flashable to Tasmota, while the Athom and IDS models round out the remaining circuits. A Tasmota RF Bridge extends the ecosystem to RF-only devices like the 3D printer plug in the study.
-The goal is subtle automation that improves daily life without being intrusive. Lights turn on when someone enters a room, music starts playing in the bathroom when the light switches on, and LED matrix displays show the time, weather, and laundry status. But nothing talks unless spoken to — no voice assistants, no always-on microphones, just simple sensor-driven automation that runs locally without cloud dependencies.
Beyond hardware automation, several self-hosted services run on the Synology NAS: TubeArchivist for YouTube archiving, OctoPrint for remote 3D printer control, iCloud Contacts Sync for keeping the address book up to date, and a Google Calendar sync for dashboard widgets. Each service is containerized and backed up as part of the NAS backup strategy.
+Beyond hardware automation, several self-hosted services run on the Synology NAS: TubeArchivist and TubeSync for YouTube archiving, OctoPrint for remote 3D printer control, iCloud Contacts Sync for keeping the address book up to date, and a Google Calendar sync for dashboard widgets. Each service is containerized and backed up as part of the NAS backup strategy.
diff --git a/smarthome/tasmota-energy/index.njk b/smarthome/tasmota-energy/index.njk index 552c8e3..6fca691 100644 --- a/smarthome/tasmota-energy/index.njk +++ b/smarthome/tasmota-energy/index.njk @@ -54,6 +54,9 @@ via Flux to display real-time and historical usage charts.The same InfluxDB instance also stores temperature and humidity readings from HomematicIP room sensors and ESP32 DHT22 devices. These feed the air quality dashboard, which visualizes 24-hour climate history across 10 rooms. The energy and climate data share the MQTT-to-InfluxDB pipeline but live in separate measurement categories, keeping power monitoring and environmental sensing cleanly separated.
+Tasmota was chosen over alternatives like ESPHome or Tuya firmware for several reasons. The local-only control means no cloud dependency — the diff --git a/smarthome/tubearchivist/index.njk b/smarthome/tubearchivist/index.njk index 5b180c6..8a4f8e7 100644 --- a/smarthome/tubearchivist/index.njk +++ b/smarthome/tubearchivist/index.njk @@ -1,55 +1,43 @@ --- -title: "TubeArchivist" +title: "YouTube Archiving: TubeArchivist & TubeSync" section: "smarthome" parent: "/" -description: "Self-hosted YouTube archiving and media management running on the Synology NAS." +description: "Self-hosted YouTube archiving and media management running on the Synology NAS, comparing TubeArchivist and TubeSync." layout: base.njk --- -
TubeArchivist runs on the Synology NAS via Docker Compose, self-hosting -a searchable archive of downloaded YouTube content (Elasticsearch + -Redis + the TubeArchivist app itself). It's used to archive channels -worth rewatching — tutorials, long-form content, and anything that might -disappear behind copyright strikes or channel deletions.
+Two self-hosted YouTube tools run on the Synology NAS via Docker Compose, each taking a different approach to the same goal: keeping offline copies of channels worth rewatching. TubeArchivist provides a full archive with search and metadata, while TubeSync focuses on automatic synchronization of playlists into a media server library.
-Running Elasticsearch on Synology's DSM kernel isn't fully -straightforward: newer Elasticsearch releases require a Linux kernel -feature (SECCOMP) that Synology's kernel doesn't compile in. The fix is -version-pinning Elasticsearch to the last release that still works -without it, rather than fighting the kernel.
+TubeArchivist self-hosts a searchable archive of downloaded YouTube content (Elasticsearch, Redis, and the TubeArchivist app itself). It's used to archive channels worth rewatching, including tutorials, long-form content, and anything that might disappear behind copyright strikes or channel deletions.
-Running Elasticsearch on Synology's DSM kernel isn't fully straightforward: newer Elasticsearch releases require a Linux kernel feature (SECCOMP) that Synology's kernel doesn't compile in. The fix is version-pinning Elasticsearch to the last release that still works without it, rather than fighting the kernel.
The main frustration with TubeArchivist is automatic playlist detection. New playlists added to subscribed channels are not always recognized by the app, meaning videos in those playlists get skipped during automatic downloads. The workaround is manually submitting individual videos or playlists through the TubeArchivist web interface using the built-in submission tool, which works but defeats the purpose of automated archiving. This issue remains unresolved.
+ +TubeSync takes a simpler approach: it syncs YouTube playlists directly into a media server library (like Jellyfin or Plex) without the full archive UI. Everything is manual: playlists must be added by URL, and there's no automatic discovery of new content from subscribed channels. It's a pure download-and-organize tool rather than a searchable archive.
+ +Both tools run in parallel on docker-host-nas, each with different strengths. TubeArchivist provides the better archive and search experience but has the playlist detection gap. TubeSync is more reliable for syncing specific playlists but requires manual curation. Neither has fully replaced the other yet, and the ideal solution of shutting one down hasn't been found.
+TubeArchivist data is split into two categories with different backup -priorities. The downloaded media files and Elasticsearch metadata are -backed up as part of the NAS backup volumes, since they take significant -time to re-download and re-index. The Redis cache is excluded — it only -holds session data and can be safely rebuilt on restart.
+Downloaded media files and Elasticsearch metadata are backed up as part of the NAS backup volumes, since they take significant time to re-download and re-index. The Redis cache is excluded, as it only holds session data and can be safely rebuilt on restart.
-| Data | Included in NAS backup? |
|---|---|
| Downloaded media files | Yes, via the NAS's own backup volumes |
| Elasticsearch metadata/index | Yes, via the NAS's own backup volumes |
| Redis cache | No — safe to delete/rebuild, only holds session data |
| Redis cache | No, safe to delete/rebuild, only holds session data |
Channels are added via the TubeArchivist web interface, which provides -a YouTube-like browsing experience for the archived content. New videos -from subscribed channels are automatically downloaded on a schedule. The -search function indexes titles, descriptions, and metadata, making it -easy to find specific videos in a large archive. The system runs headless -on the NAS with no dedicated display — all interaction happens through the -web interface or the companion mobile app.
-