You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Necessary to resolve issues where schedules and output were written
to /app/data inside the container instead of the user-mounted /data
volume. The app now auto-detects the data directory at startup and
supports both mount points:
- -v ./trmnl-data:/data (recommended, matches docs)
- -v ./trmnl-data:/app/data (legacy workaround, also works)
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: README.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -51,6 +51,8 @@ docker run -d --name trmnl-ha \
51
51
```
52
52
53
53
> **Note:** Replace `YOUR_HOST_IP` with your machine's IP (e.g., `192.168.1.100`). Container names like `homeassistant` won't work since HA uses host networking.
54
+
>
55
+
> **Volume mount:**`-v ./trmnl-data:/data` is recommended. `-v ./trmnl-data:/app/data` also works.
Create cron-based schedules via the Web UI for automatic captures.
306
317
307
-
**Storage:**`/data/schedules.json` (persists across restarts)
318
+
**Storage:**`schedules.json`in the data directory (persists across restarts when a volume is mounted — see [Data Persistence](#home-assistant-container-docker))
308
319
309
320
**Manual Trigger:** Click **Send Now** to execute immediately.
0 commit comments