homehub
A private, lightweight, no-login, self-hosted family utility for your home and it comes with no config PWA.
Automatically checked · GitHub checked 2026-11-13

Overview
Maintainer Note
Thank you for your interest in this project! I originally started it as a personal utility and never expected it to grow so quickly—I’m genuinely thrilled and grateful that it’s become helpful to you and your family.Please note that I am currently the sole maintainer and manage this repository alongside a full-time job, which means the time I can give to this project is somewhat limited. Responses to issues, pull requests, or questions may be delayed, especially during busy periods at work or at home.
I typically work on the project after office hours or on weekends, depending on my availability and energy. Your patience, understanding, and support mean a lot—thank you for helping make this project better!
Featured in: XDA Developers · DB Tech (video) · selfh.st
🏡 HomeHub: Your All-In-One Family Dashboard
Ever wanted a simple, private spot on your home network for your family's daily stuff? That's HomeHub. It's a lightweight, self-hosted web app that turns any computer (even a Raspberry Pi!) into a central hub for shared notes, shopping lists, chores, a media downloader, and even a family expense tracker.
It’s designed to be easy to use for everyone in the family, with a clean interface that works great on any device.
What Can It Do?
HomeHub is packed with useful tools to make family life a little more organized:
- 📝 Shared Notes: A simple place to jot down quick notes for everyone to see.
- ☁️ Shared Cloud: Easily upload and share files across your home network.
- 🛒 Shopping List: A collaborative list so you never forget the milk again. Comes with suggestions based on your history!
- ✅ Chore Tracker: A simple to-do list for household tasks.
- 🗓️ Calendar & Reminders: A shared calendar to keep track of important dates.
- 👋 Who's Home?: See at a glance who is currently home.
- 💰 Expense Tracker: A powerful tool to track family spending, with support for recurring bills like newspapers, milk, or subscriptions. Set monthly budgets (overall and per category) and see charts of spending by category, by person and by day. Export a month or a date range as a CSV file for Excel or Google Sheets, and import expenses from a CSV file (HomeHub's own export or a bank or UPI statement) with a preview that flags likely duplicates. Anyone can record an expense paid by anyone, but only the person who added it (or the admin) can edit or delete it.
- 🎬 Media Downloader: Save videos or music from popular sites directly to your server.
- 🗑️ Trash: Deleted reminders, shopping items, chores, notes, recipes, expiry items and expenses wait in a shared Trash for 7 days, so anything removed by mistake (in HomeHub or through the API) can be restored.
- ...and more, including a Recipe Book, Expiry Tracker, URL Shortener, PDF Compressor, Weather Updates and QR Code Generator!
Salient Features
- Private & Self-Hosted: All your data stays on your network. No cloud, no tracking.
- Simple & Lightweight: Runs smoothly on minimal hardware.
- Family-Focused: Designed to be intuitive for users of all technical skill levels.
- Customizable: Toggle features on or off and even change the color theme right from the
config.ymlfile. - Forgiving: Deleted reminders, shopping items, chores, notes, recipes, expiry items and expenses go to a shared Trash for 7 days, so a slip of the finger can be undone.
Getting Started is Easy
The best way to run HomeHub is with Docker. It's quick and keeps everything tidy
- First, copy the
config-example.ymltoconfig.yml. This is where you'll name your hub, add family members and choose which features to show. The settings at the bottom (site password, upload limit, colours, reminders, calendar feed, weather, theme) are optional: delete any you don't need and HomeHub uses its defaults.
Click to see an example config.yml
# HomeHub settings
#
# Copy this file to config.yml and edit it. Changes are usually picked up on the next
# page load; if one is not, restart HomeHub (docker compose restart homehub).
# Quotes are optional, also around hex colours such as #2563eb.
# Everything below "OPTIONAL" can be deleted: HomeHub uses the default shown for it.
# ---------------------------------------------------------------------------
# BASICS
# ---------------------------------------------------------------------------
instance_name: "My Home Hub" # shown in the sidebar and the browser tab
# UI language for the whole household: a code from "Supported languages" in the README.
# Anything else falls back to English.
language: en
# The admin manages settings, budgets and backups. To protect it with a password, run:
# docker exec -it homehub flask set-admin-password
admin_name: "Administrator"
# Everyone in the household, as they appear in the user picker, splits and chores.
# To give someone their own chart colour, see "Colours" under OPTIONAL.
family_members:
- Mom
- Dad
- Dipanshu
- Vivek
- India
# ---------------------------------------------------------------------------
# FEATURES
# ---------------------------------------------------------------------------
# true shows a feature, false hides it. Keep every line: for most features a missing
# line counts as false (calendar, expense_tracker, who_is_home and personal_status are
# the exceptions and stay on).
feature_toggles:
notes: true
shared_cloud: true # shared file uploads
shopping_list: true
calendar: true
chores: true # to-do list and chores
recipes: true
expiry_tracker: true
url_shortener: false
media_downloader: true
pdf_compressor: true
qr_generator: true
expense_tracker: true
who_is_home: true # Welcome page: who is home right now
personal_status: true # Welcome page: a short status per person
# ---------------------------------------------------------------------------
# OPTIONAL: delete any block you do not need
# ---------------------------------------------------------------------------
# Site password, asked once per browser. Without it (or left empty) anyone on your
# network can open HomeHub.
password: ""
# Largest upload (Shared Cloud, PDFs) in MB. 0 removes the limit. Default: 1024.
max_upload_mb: 1024
# Colours for people in the expense charts: a colour name (teal, red) or hex.
# Without one, each person gets a colour from the default palette by their place in
# family_members, and the admin comes after the family. To pick one, write that person
# in family_members as a name with a colour:
# family_members:
# - Mom
# - name: Dad
# color: "#7c3aed"
# admin_color: "#0d9488"
# Reminders and calendar. Without this block: 12-hour times, weeks starting on Sunday,
# and reminders without categories.
reminders:
time_format: 12h # 12h or 24h
calendar_start_day: sunday # a weekday name (sunday to saturday) or 0-6, where 0 is Sunday
# Categories to pick from when adding a reminder. key: short id (lowercase, no spaces),
# label: the name shown, color: a colour name or hex.
categories:
- key: health
label: Health
color: "#dc2626"
- key: bills
label: Bills
color: "#0d9488"
- key: school
label: School
color: "#7c3aed"
- key: family
label: Family
color: "#2563eb"
# Calendar subscription feed: HomeHub reminders, with alerts, in the calendar app on your
# phone or computer. Read-only. Off while the token is empty. Make a token (16+ characters):
# python -c "import secrets; print(secrets.token_urlsafe(32))"
# and subscribe to http://<your-homehub>/calendar.ics?token=<token>. Anyone with the link
# can read your reminders; change the token to revoke it (no restart needed).
calendar_feed:
token: ""
alerts: true # false = events without phone alerts
# Weather widget on the Welcome page (Open-Meteo, no account needed). Off unless enabled.
weather:
enabled: false
label: "" # place name shown on the widget; empty hides it
latitude: "" # empty: use the browser's location
longitude: "" # empty: use the browser's location
timezone: "" # e.g. "Asia/Kolkata" or "America/New_York"; empty: detected automatically
units: metric # metric or imperial
view: compact # compact, or detailed (adds today's sunrise, sunset, UV, rain chance, high and low)
# Colours of the app. Without this block HomeHub uses its default blue look.
# The README "Theming" section lists every key.
theme:
primary_color: "#1d4ed8"
2. Run with Docker Compose
Use the provided compose.yml file to get started in seconds:
# compose.yml
services:
homehub:
container_name: homehub
image: ghcr.io/surajverma/homehub:latest
restart: unless-stopped
ports:
- "5000:5000" #app listens internally on port 5000
volumes:
- ./uploads:/app/uploads
- ./media:/app/media
- ./pdfs:/app/pdfs
- ./data:/app/data
- ./config.yml:/app/config.yml:ro
environment:
- SECRET_KEY=${SECRET_KEY:-} # optional, from .env; left empty, a key is generated once and kept in data/secret_key
# - TZ=Asia/Kolkata # optional; see "Timezone" below
docker compose up -d
That's it! Open your browser and head to http://localhost:5000
docker logs homehub shows errors and HomeHub's own messages. To also log every request, add - GUNICORN_CMD_ARGS=--access-logfile - under environment: in compose.yml and run docker compose up -d.
Admin password (optional)
By default anyone can pick the admin user from the user switcher. To protect it, the server owner can set an admin password from the host:
docker exec -it homehub flask set-admin-password
- You are asked to type the password twice. Only a salted hash is stored, in
data/app.db; nothing is written toconfig.yml. - Once set, switching to the admin user asks for the password. Family members keep switching freely.
- The Backups page is only available once an admin password is set.
- Run the same command again to change it. A forgotten password is fixed the same way.
docker exec -it homehub flask set-admin-password --clearremoves it and restores the default behaviour.- Not using Docker? Run
flask set-admin-passwordfrom the project folder.
The password in config.yml is separate: it protects the whole site and keeps working as before. You write it in config.yml as plain text; HomeHub only keeps a salted hash of it in memory, and after 5 wrong attempts the login form makes that device wait a minute, like the admin password prompt.
Logins and admin unlocks survive a restart: if SECRET_KEY is not set, HomeHub generates one on first start and keeps it in data/secret_key.
Trash
Deleting something in HomeHub moves it to the Trash (in the menu) instead of removing it at once: reminders and recurring reminders, shopping items, chores and recurring chores, notes, recipes, expiry items, expenses and recurring expenses. (Deleting a recurring reminder that has already started only ends it from today, keeping its earlier dates; that has a short Undo instead.) Right after a delete, the Undo button in the message brings it back; after that, the Trash page lists everything deleted in the last 7 days, newest first, with who deleted it and how many days are left. Each module page has a Trash link that shows only its own items (on the Calendar it's the Trash button). Reminders that were in the calendar's old trash when you upgrade are moved to the Trash page, keeping the day they were deleted.
Whoever added an item (or the admin) can Restore it or Delete forever. Things deleted through the API land here too, marked with the app that deleted them, for example Priya (via Hermes). After 7 days items are deleted for good automatically. On the server:
docker exec -it homehub flask trash list
docker exec -it homehub flask trash restore t-3f9c2a7d1e
The restore takes the reference in the first column of flask trash list (it starts with t-). It names one entry for good, so a restore typed from an older listing never brings back a different item.
Backup and restore
Backups are zip files kept on the server in data/backups/ (on the host through the ./data volume). The Backups page and the flask backup command save to the same folder and see the same list. A backup only protects you once it is copied to another device, so download it or copy it off the machine.
From the browser: set an admin password first; backups hold everyone's data and may contain the site password, so the Backups page stays off without one. Then, as the unlocked admin, open Manage backups on the Welcome page.
- Create a backup: tick what to include. Each part shows its size, with a running total. The database and settings are always included. Downloaded media is off by default because it can be very large, and the page warns above about 1 GB. The backup is built in the background, so you can leave the page.
- Download any backup in the list (an interrupted download can resume), then delete it to free up space on the server.
- Restore from a backup file: choose a backup zip and you go straight to the restore page. It asks for the admin password again; you see what the backup holds and can untick parts. The uploaded zip is deleted from the server once the restore is done or cancelled. Uploads are limited by
max_upload_mb(and by any reverse proxy in front of HomeHub); raise that for a bigger backup, or useflask restorebelow. - Safety backups: before a restore replaces anything, the current data is saved as a safety backup in the list. It is the undo for that restore, so it is the one kind of backup with a Restore button there. The newest 3 are kept; older ones are deleted automatically.
- Restart HomeHub after a restore (
docker compose restart homehub). config.ymlis never overwritten, because it is mounted read-only. After a restore, the page shows the backup's config (passwords hidden) and saves it asdata/config-from-backup.yml; copy the settings you want intoconfig.ymlyourself.
Backups that include config.yml may contain the site password in plain text. Keep them somewhere safe.
From the host (works with or without an admin password):
docker exec -it homehub flask backup # database, uploads, PDFs and config.yml
docker exec -it homehub flask backup --include-media # media too
docker exec -it homehub flask restore /app/data/backups/homehub-backup-YYYYMMDD-HHMMSS.zip
docker compose restart homehub
--no-configleavesconfig.ymlout, and--output PATHwrites the zip somewhere else inside the container.flask restorechecks the zip, asks you to confirm (--yesskips the question), saves a safety backup and prints its path, restores everything in the zip, and runs database upgrades. As in the browser, the backup'sconfig.ymlgoes todata/config-from-backup.yml.- Not using Docker? Run
flask backupandflask restore PATHfrom the project folder.
Timezone (optional)
HomeHub decides what "today" is (due dates, overdue chores, recurring expenses and chores) and which time to show next to "By … at …" from the container's clock, which is UTC by default. If you are far from UTC, "today" can roll over a few hours early or late. Set your timezone with TZ in compose.yml:
environment:
- TZ=Asia/Kolkata
Use a name from the tz database, then run docker compose up -d. Leaving it out keeps the old UTC behaviour.
Reminders in your phone's calendar (optional)
HomeHub reminders can show up in the calendar app on your phone or computer, with alerts, and stay up to date. It's one-way: you add and change reminders in HomeHub.
Turn it on. Make a token with python -c "import secrets; print(secrets.token_urlsafe(32))" and add it to config.yml (no restart needed):
calendar_feed:
token: "paste-the-token-here" # 16+ characters; empty turns the feed off
alerts: true # false = events without phone alerts
Then subscribe (not import) to http://<your-homehub-address>:<port>/calendar.ics?token=<token>.
| App | On your home network | Needs HomeHub reachable from the internet |
|---|---|---|
| iPhone / iPad (subscribed on the device) | ✓ | |
| Android with ICSx⁵ (shows in the Google Calendar app too) | ✓ | |
| Apple Calendar on Mac ("On My Mac") | ✓ | |
| Thunderbird | ✓ | |
| Google Calendar website, Outlook | ✓ |
Google Calendar and Outlook fetch the feed from Google's or Microsoft's servers, so they only work if your HomeHub is reachable from the internet over HTTPS (for example via a reverse proxy or a tunnel), which isn't recommended for a home app. The feed itself works; they just can't reach it. Google also refreshes slowly (often every 12-24 h).
Step-by-step setup for each app, turning on alerts on iPhone, and how times work: docs/calendar-feed.md.
Keep the link secret: anyone who has it can read your reminders.
If it leaks, change the token in config.yml; old links stop working straight away.
API, Home Assistant and AI agents (optional)
HomeHub has a token-protected JSON API at /api/v1/ and a built-in MCP endpoint at /api/v1/mcp, so Home Assistant, phone shortcuts, NFC tags, Node-RED, scripts and AI agents (such as Hermes or Claude) can read and update who is home, reminders, the shopping list, chores, notes, recipes, the expiry tracker and expenses, and read the notice board and the weather.
The API is off until you create a token. Switch to the admin user and open Admin tools > API access on the Welcome page (it needs an admin password), or use the command line:
docker exec -it homehub flask api-token create "Home Assistant" --tool presence=write --tool reminders=read --act-as-members
Each token gets only the tools you pick, read-only or read and write. Keep tokens secret, and don't expose HomeHub to the internet: for agents outside your home, use a VPN such as Tailscale. Set your timezone too, so "today" means the same day for the API as for you.
Endpoints, curl examples, Home Assistant YAML, phone shortcuts and setting up AI agents: docs/api.md.
Language
HomeHub can show its interface in another language. Set it for the whole household in config.yml:
language: hi # a code from the table below
The change applies on the next page load, no restart needed. A missing or unknown value falls back to English, and so does any text that has no translation yet. What you type into HomeHub (notes, chores, names) is never translated.
Supported languages
| Code | Language | Extra font |
|---|---|---|
en | English (default) | |
hi | Hindi (हिन्दी) | Noto Sans Devanagari |
zh | Chinese, Simplified (简体中文) | Noto Sans SC |
tr | Turkish (Türkçe) |
This table is the one place to list a new language. Translations are added by the community, so coverage can vary.
Translating HomeHub
Each language is one file, translations/<code>/LC_MESSAGES/messages.po, covering both the pages and the page scripts. To add a language (Marathi, mr, as the example):
- Create the file. This sets up the folder and the right plural rules for the language:
pybabel init -i translations/messages.pot -d translations -l mr --no-wrap - Fill in each
msgstrintranslations/mr/LC_MESSAGES/messages.po. Any text editor works; Poedit makes it easier. Keep placeholders such as%(name)sand{count}exactly as they are. - Set
language: mrinconfig.ymland rebuild withdocker compose up -d --build. - Add a row for the language to the Supported languages table.
- Only if the language is not written in Latin, Cyrillic or Greek script (which the Inter font already covers), add its Noto font from Google Fonts to
LANGUAGE_FONTSinapp/i18n.py, for example'mr': 'Noto Sans Devanagari', and name it in the table's Extra font column. French, German, Spanish or Russian need nothing here; Devanagari, Chinese, Japanese, Korean, Thai, Tamil or Bengali do. The font loads only when that language is selected.
Good to know:
- Anything left untranslated shows in English, so a partial translation is welcome.
- Month and weekday names come from the language automatically.
- Right-to-left languages are not supported yet: the text would translate, but the layout is not mirrored.
- Translations are built into the Docker image; the compiled
.mofiles are not kept in git.
Sending a translation: a pull request for a language should only change that language's file under translations/, add its row to the Supported languages table and, if step 5 applies, add the font line. There is no need to touch config-example.yml or the config sample above. The tests check that placeholders are intact and that nothing like links or HTML has been added. A review from a second native speaker is very welcome.
For developers: marking and updating text
In templates and Python, wrap text in _() (ngettext() for counts). Page scripts in static/js use t('text', {params}), th() when the result goes into an HTML string, tn(one, other, count) for counts and tc('context', 'text') when one English word needs different translations. A sentence with a name, number or link in it is always one string with a placeholder, so each language can put the value where its grammar needs it.
# After adding or changing text: collect the strings and bring every language file up to date
flask translations update
# Compile for a local (non-Docker) run
flask translations compile
Theming
HomeHub follows your system dark/light mode. You can customize colors via config.yml > theme.
Configurable keys (all optional):
theme:
# Accent colors
primary_color: "#1d4ed8"
secondary_color: "#a0aec0"
# Surfaces & text
background_color: "#f8fafc"
card_background_color: "#ffffff"
text_color: "#0f172a"
# Sidebar palette. Leave these out for the default light sidebar.
# Setting sidebar_background_color gives a coloured sidebar with light links.
sidebar_background_color: "#2563eb"
sidebar_text_color: "#ffffff" # text color used for the sidebar title and labels
sidebar_link_color: "rgba(255,255,255,0.95)" # link text color in sidebar items
sidebar_link_border_color: "rgba(255,255,255,0.18)" # subtle border around sidebar links
sidebar_active_color: "#3b82f6" # background of the current page's link
Tips:
- Hex colours work with or without quotes (
primary_color: #1d4ed8is fine). - The old default blue sidebar (
#2563eb) is treated as "not set", so configs copied from an olderconfig-example.ymlget the new light sidebar. Pick any other colour to keep a coloured sidebar. - Prefer lighter/darker accents? Tweak
primary_colorandsecondary_color. - Dark mode palette adapts automatically; the variables above apply to light mode, while dark mode uses tuned counterparts for good contrast.
Colours for people in the expense charts
Each person gets a chart colour from a fixed palette, by their position in family_members (the admin comes after the family). To pick a colour yourself, write that person as a name with a color; plain names keep working, and the admin's colour goes in admin_color:
admin_name: "Administrator"
admin_color: "#0d9488"
family_members:
- Mom
- name: Dad
color: "#7c3aed"
- name: Dipanshu
color: red
- Use a colour name (
red,teal,RoyalBlue: any CSS colour name) or a hex colour (#7c3aedor#73d), with or without quotes. Anything else is ignored with a warning in the log, and that person keeps the default. - People without a colour keep the one they had, so picking a colour for one person never changes anyone else's.
- HomeHub adjusts a colour only when it would be hard to see: a very pale one is darkened a little on the light cards, a very dark one is lightened a little on the dark cards. Everything else is used as written.
- Nothing stops two people from looking alike: if you pick a colour close to someone else's default (blue for Dad while Mom is blue by position), give Mom a colour too.
- Restart HomeHub (or save
config.yml; it is re-read when it changes) and reload the page.
Weather Widget
HomeHub includes an optional weather widget powered by Open-Meteo, a free weather API. The widget displays current weather conditions and optionally today's forecast on your dashboard.
By default, the weather widget is hidden. You can enable it through config.yml:
weather:
enabled: true # set to true to show the widget
label: "" # optional location label (e.g., "Kolkata"). Leave blank to hide.
latitude: "" # optional, leave empty to use browser geolocation
longitude: "" # optional, leave empty to use browser geolocation
timezone: "" # optional, e.g., "Asia/Kolkata" or "America/New_York"; if unset, API uses timezone=auto
units: metric # metric or imperial (default: metric)
view: compact # compact or detailed (detailed shows today's forecast: sunrise, sunset, UV, rain %, highs/lows)
Features:
- Two view modes:
compact: Shows current temperature, weather condition, feels like, wind (with direction and gusts), humidity, and recent precipitationdetailed: Adds today's forecast with sunrise/sunset times, UV index, precipitation probability, and daily high/low temperatures
- Smart caching: Weather data is cached for 15 minutes to respect API rate limits and improve performance. With coordinates in
config.yml, the server fetches it and shares that cache with the API - Flexible location: Use configured coordinates or browser geolocation
- Timezone support: Displays times in your configured timezone, or uses automatic detection
- Unit selection: Choose between metric (°C, km/h, mm) or imperial (°F, mph, mm) units
Privacy Note: When enabled, the widget makes API requests to Open-Meteo's servers. Please review Open-Meteo's privacy policy for details on their data handling practices.
Development Setup
To contribute or run & build HomeHub locally, follow these steps:
1. Clone the Repository
git clone https://github.com/surajverma/homehub.git
cd homehub
2. Python Environment Setup
python -m venv venv
venv\Scripts\activate # On Windows
pip install -r requirements-dev.txt # the app's packages plus pytest
3. Configuration
- Copy
config-example.ymltoconfig.ymland edit as needed for your family, features, and theme.
4. CSS Build (Tailwind + Custom Styles)
npm install
npm run build:css
- For live CSS rebuilds during development:
npm run watch:css
5. Running the App
- With Docker (recommended):
To run your own changes in Docker, create a
docker compose up -dcompose.override.ymlnext tocompose.yml(it is gitignored) withservices: homehub: build: .andpull_policy: build, then rundocker compose up -d --build. Leavecompose.ymlitself unchanged. - Locally (for development):
(Ensure you have built CSS and set up your config.) Set
python run.pyFLASK_DEBUG=1to get auto-reload and Flask's debugger; it is off by default.
6. Troubleshooting
- If you see missing dependency errors, ensure you have run both
pip install -r requirements-dev.txtandnpm install. - If port 5000 is in use, stop the conflicting service or change the port in
compose.ymlandconfig.yml. - For Docker issues, try
docker compose downthendocker compose up -d. - If the log says
config.yml is missingorconfig.yml is a folder, HomeHub is running on the defaults fromconfig-example.yml. Docker creates an emptyconfig.ymlfolder when the file is not there at first start: remove that folder, copyconfig-example.ymltoconfig.yml, and start the container again. docker psshows the container ashealthyonce the app answers on/healthz.- The database runs in SQLite's WAL mode. If
data/sits on a network share (NFS, SMB) and you seedatabase is lockedor disk I/O errors, add- SQLITE_JOURNAL_MODE=DELETEunderenvironment:to go back to the previous mode.
Supported platforms
The Docker image is built for linux/amd64 and linux/arm64, which includes a Raspberry Pi 4 or 5 running a 64-bit OS. 32-bit ARM (linux/arm/v7, e.g. 32-bit Raspberry Pi OS) is no longer built: stay on the last image you pulled, or move to a 64-bit OS to keep getting updates.
License
This project is licensed under the MIT License. See the LICENSE file for details.
Contributing
Contributions are always welcome! If you have any ideas, suggestions, or bug reports, please open an issue or submit a pull request.
Disclaimer & Security Notice
This software is being provided to the community "as is." This means it comes without any warranty or guarantee of any kind. While I've done my best to build it, I can't promise it will be perfect, fit your exact needs, or be 100% free of bugs.
Please be aware that you are using this software at your own risk. The authors and contributors are not responsible for any problems, damages, or data loss that might occur from using it.
🛡️ Important Security Notice
This project is built for use on a local or trusted network (like your home).
It is not designed or hardened to be safely exposed to the public internet. If you choose to host this software publicly, you are solely responsible for performing a full security review and adding the necessary protections before you do so.
🌤️ Weather Data & Third-Party Services
The optional weather widget uses Open-Meteo, a free weather API service. When the weather widget is enabled:
- With
latitudeandlongitudeinconfig.yml, the HomeHub server fetches the weather from Open-Meteo; without them, your browser uses its own location and the server passes that request on - Location coordinates (latitude/longitude) are sent to their API
- Open-Meteo has its own privacy policy and terms of service
By enabling the weather widget, you acknowledge that weather data is provided by a third-party service and is subject to their policies. HomeHub itself keeps weather data only in memory (on the server, for 15 minutes) and in the browser's cache. The API's weather answer never includes the coordinates or the place name.
Have Fun!
This project was built to be a practical tool for my own family, and I hope it's useful for yours too.
If you find HomeHub useful, you can buy me a coffee ☕.