Insteon Panel Frontend
This repository holds the frontend files of Insteon configuration panel in home assistant.
Development Setup
-
Install vscode, git, and docker desktop
-
Install dev container extension in vscode
-
Fork/clone Insteon-panel
-
Open Insteon-panel repo in VS Code
- You should see a prompt asking you if you want to re-open the workspace in the container, say yes
- Once opened in the dev container, the bootstrap process should automatically run - this will take a few minutes to complete.
- Once bootstrapped, run
script/developto build the code. This will also watch for changes.- Built code is output to the
insteon_frontendfolder in the repo
- Built code is output to the
-
Follow these instructions to get a dev container of Home Assistant Core up and running
-
Now you will need to configure the Home Assistant Core container so that your locally-built
insteon-panelcode is available as a mounted directory:- Open .devcontainer/devcontainer.json
- Add a new “mounts” property to the root of the JSON object similar to this example:
"mounts": [ "source=/path/to/insteon-panel,target=/workspaces/insteon-panel,type=bind" ],
- Rebuild the dev container by pressing Shift+Command+P (Mac) / Ctrl+Shift+P (Windows/Linux) to open the Command Palette, then selecting the Dev Containers: Rebuild Container command.
- After the container is rebuilt and successfully re-opened, open the Command Pallate, choose Run Task, then Run Home Assistant Core
- Once home assistant core is running, navigate to http://localhost:8123 and setup your test home environment
- Install the Insteon integration (production version) and follow the normal setup steps
- Switch the Insteon integration to dev mode - in the
home-assistant/corecontainer, open the config/.storage/core.config_entries (in VS Code), find the Insteon the entry (can be found by text searching for “insteon”) and change the “options” object to this:"options":{"dev_path":"/workspaces/insteon-panel/insteon_frontend"} - Restart home assistant and go to the Insteon setup section (Settings -> Insteon). You’re now loading your locally built Insteon panel!
Metadata
Release files for insteon-frontend-home-assistant 0.7.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| insteon_frontend_home_assistant-0.7.0.tar.gz | 20.7 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| insteon_frontend_home_assistant-0.7.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 41.6 MB
Release files / insteon_frontend_home_assistant-0.7.0.tar.gz
| Download URL | insteon_frontend_home_assistant-0.7.0.tar.gz |
|---|---|
| Size | 20.7 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9b11b6b94a333f0cf9f06aedda91a4089e0b56d73eb195c9772f570716a878fa
|
|
BLAKE2b-256 checksum How to use checksums |
c161ff56b78a927685185e4fb4144e7f494b7708e6705feed59423acee6e4fdf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 27, 2026.
Transparency logRelease files / insteon_frontend_home_assistant-0.7.0-py3-none-any.whl
| Download URL | insteon_frontend_home_assistant-0.7.0-py3-none-any.whl |
|---|---|
| Size | 20.8 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
762635c31968661cb3e46af25fa6e0b9ac3d87e3d518084cc40ce70dd05675fb
|
|
BLAKE2b-256 checksum How to use checksums |
242e78375c472b0708e802631e2c274884d4c76a033787fa94c60ab65b585d00
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 27, 2026.
Transparency log