Files
hassio-addons/changedetection.io
copilot-swe-agent[bot] 8a0f15413c Add My Home Assistant repository button to all addon READMEs
Add the "Add repository to my Home Assistant" blue button to all
addon README files that were missing it. This makes it easier for
new HA users to add the repository with a single click.

Updated 59 addon READMEs:
- 51 with standard Installation section format
- 8 with non-standard or missing Installation sections

Co-authored-by: alexbelgium <44178713+alexbelgium@users.noreply.github.com>
2026-02-23 09:02:12 +00:00
..
2026-01-24 18:36:44 +01:00
2026-02-04 15:59:55 +01:00
2025-08-31 23:06:36 +00:00
2025-08-31 23:06:36 +00:00
2026-02-22 23:10:24 +00:00

Home assistant add-on: changedetection.io

I maintain this and other Home Assistant add-ons in my free time: keeping up with upstream changes, HA changes, and testing on real hardware takes a lot of time (and some money). I use around 5-10 of my >110 addons so regularly I install test machines (and purchase some test services such as vpn) that I don't use myself to troubleshoot and improve the addons

If this add-on saves you time or makes your setup easier, I would be very grateful for your support!

Buy me a coffee Donate via PayPal

Addon informations

Version Ingress Arch

Codacy Badge GitHub Super-Linter Builder

Thanks to everyone having starred my repo! To star it click on the image below, then it will be on top right. Thanks!

Stargazers repo roster for @alexbelgium/hassio-addons

downloads evolution

About

Changedetection.io provides free, open-source web page monitoring, notification and change detection.

This addon is based on the docker image from linuxserver.io.

Configuration

Use the add-on env_vars option to pass extra environment variables (uppercase or lowercase names). See https://github.com/alexbelgium/hassio-addons/wiki/Add-Environment-variables-to-your-Addon-2 for details.

Main app

Web UI can be found at <your-ip>:5000, also accessible from the add-on page or through the sidebar using Ingress.

Sidebar shortcut

You can add a shortcut pointing to your Changedetection.io instance with the following steps:

  1. Go to ⚙ Settings > Dashboards
  2. Click Add Dashboard at the bottom corner
  3. Select the Webpage option, and paste the Web UI URL you got from the add-on page.
  4. Fill in the title for the sidebar item, an icon (suggestion: mdi:vector-difference), and a relative URL for that panel (e.g. change-detection). Lastly, confirm it.

Options

Option Type Default Description
PGID int 0 Group ID for file permissions
PUID int 0 User ID for file permissions
TZ str Timezone (e.g., Europe/London)
BASE_URL str Full URL when running behind reverse proxy
PLAYWRIGHT_DRIVER_URL str Playwright driver WebSocket URL
TIMEOUT int 60000 Request timeout in milliseconds

Example Configuration

PGID: 0
PUID: 0
TZ: "Europe/London"
BASE_URL: "https://changedetection.mydomain.com"
PLAYWRIGHT_DRIVER_URL: "ws://db21ed7f-browserless-chrome:3000/chromium?headless=true&stealth=true&blockAds=true"
TIMEOUT: 60000

Connect to browserless Chrome (from @RhysMcW)

Install and start the Browserless Chrome add-on, then use the PLAYWRIGHT_DRIVER_URL option to connect to it. This option must be filled with the Browserless Chrome URL: "ws://db21ed7f-browserless-chrome:3000/chromium?headless=true&stealth=true&blockAds=true"

The db21ed7f-browserless-chrome hostname is displayed in the UI, on the Browserless Chromium addon page: image

Then restart the Changedetection.io add-on - after that you can use the browser options in Changedetection.io.

Installation

The installation of this add-on is pretty straightforward and not different in comparison to installing any other Hass.io add-on.

  1. Add my add-ons repository to your home assistant instance (in supervisor addons store at top right, or click button below if you have configured my HA) Open your Home Assistant instance and show the add add-on repository dialog with a specific repository URL pre-filled.
  2. Install this add-on.
  3. Click the Save button to store your configuration.
  4. Start the add-on.
  5. Check the logs of the add-on to see if everything went well.
  6. Carefully configure the add-on to your preferences, see the official documentation for for that.