https://github.com/mrueg/addon-standalone-chromium
Chromium Standalone to use for Selenium Remote Webdriver
https://github.com/mrueg/addon-standalone-chromium
addon chromium home-assistant home-assistant-addon selenium selenium-webdriver
Last synced: 5 months ago
JSON representation
Chromium Standalone to use for Selenium Remote Webdriver
- Host: GitHub
- URL: https://github.com/mrueg/addon-standalone-chromium
- Owner: mrueg
- License: apache-2.0
- Created: 2025-05-06T13:41:40.000Z (about 1 year ago)
- Default Branch: main
- Last Pushed: 2025-11-24T15:59:08.000Z (7 months ago)
- Last Synced: 2025-11-28T02:54:22.096Z (7 months ago)
- Topics: addon, chromium, home-assistant, home-assistant-addon, selenium, selenium-webdriver
- Language: Jinja
- Homepage:
- Size: 89.8 KB
- Stars: 1
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Contributing: .github/CONTRIBUTING.md
- License: LICENSE
- Code of conduct: .github/CODE_OF_CONDUCT.md
Awesome Lists containing this project
README
# addon-standalone-chromium
> [!CAUTION]
> This is still work in progress and things might not work as expected.
> I won't provide support, if you find an issue PRs are welcome though!
## What it does
Provides a Chromium Standalone addon to run Selenium Webdriver remotely.
Exposes port 4444 internally, so integrations that use selenium can connect remotely to it and scrape the web.
The integration needs to connect to `http://CONTAINER_NAME:4444/wd/hub`, where CONTAINER_NAME is the name of the container started within Home-Assistant.
You can also expose port 7390 for a NoVNC access, which allows you to view the selenium actions.
An integration that uses this addon is: [home-assistant-voebb](https://github.com/mrueg/home-assistant-voebb).
Builds are available for arm64 and amd64, as they depend on what selenium upstream provides.
## Work in Progress:
- Selenium Grid UI doesn't load through ingress, if you need to access it you need to expose port 4444 externally.