Skip to main content

LCN panel for Home Assistant

Project description

LCN Frontend

Buy Me A Coffee

This repository contains the frontend files for the Home Assistant LCN configuration panel.

A detailed guide can be found in the documentation.

Feel free to use the issue tracker to report bugs, give feetback or share ideas for improvements.

If you want to participate in development (great!) head down to the development section.

Features

  • Device Configuration Device Configuration

    • Set up modules and groups for all your LCN integrations.
    • Search for modules and groups and have them added automatically.
    • Select a module or group to access the respective Entity Configuration panel.
  • Entity Configuration Entity Configuration

    • Set up Home Assistant entities for each module or group.
    • Create new entities that map the functions of your LCN modules and configure their parameters.
    • New entities are automatically added to your Home Assistant configuration and you can add them to your dashboards just like for any other integration.

Development

Setting up the development environment

  • To display and test the frontend during development, you need to prepare a Home Assistant development environment. For this it is recommended to follow the instructions here.

  • You need to have node.js installed to build the frontend. Using nvm is the preferred method of installing node.js. Install nvm using the instructions provided here. Install the correct node.js version by running the following command in the root directory of your checkout working tree.

$ nvm install
$ make bootstrap
$ yarn install

Building the frontend

During development use the following command to build the frontend automatically whenever you make code changes:

$ make develop

A production build can be created by issuing:

$ make build

Preparing the frontend

Next is to symlink the build directory lcn_frontend into the Home Assistant configuration directory:

$ ln -s <lcn-frontend-dir>/lcn_frontend <hass-dir>/config/deps/lib/python3.xx/site-packages/
  • <lcn-frontend-dir> is the root working directory of the repository's checkout directory
  • <hass-dir> is the root working directory of the home-assistant-core repository's checkout directory

The <hass-dir>/config directory is created when first starting Home Assistant. Usually you have to create the mentioned sub-paths by your own. Use the appropriate Home Assistant's Python version in the path.

Alternatively, if you are working with a venv install:

export PYTHONPATH=<lcn-frontend-dir>

Starting Home Assistant

Start Home Assistant using:

$ hass -c config

Code quality

You may use the following commands to ensure code quality:

  • Code formatting: yarn run format
  • Code linting: yarn run lint
  • Type linting: yarn run lint:types

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

lcn_frontend-0.2.0.tar.gz (1.6 MB view details)

Uploaded Source

Built Distribution

lcn_frontend-0.2.0-py3-none-any.whl (1.6 MB view details)

Uploaded Python 3

File details

Details for the file lcn_frontend-0.2.0.tar.gz.

File metadata

  • Download URL: lcn_frontend-0.2.0.tar.gz
  • Upload date:
  • Size: 1.6 MB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/5.1.1 CPython/3.12.7

File hashes

Hashes for lcn_frontend-0.2.0.tar.gz
Algorithm Hash digest
SHA256 5443b99409632a814082aa0e29dc88f263b3f5deb02a695753aa0af1ea077354
MD5 0286c24585d1df6a015cdc33f1ab5827
BLAKE2b-256 747e91006cb4dcdbac7304fddfb6a4311eec4050713f9ef2520c8f95c25d9869

See more details on using hashes here.

File details

Details for the file lcn_frontend-0.2.0-py3-none-any.whl.

File metadata

File hashes

Hashes for lcn_frontend-0.2.0-py3-none-any.whl
Algorithm Hash digest
SHA256 0e1c6e853dc334657f589d617f4be987ebe4db770e7124c564419c33dd8b72b3
MD5 9049e865bb85a11670eb11085f68e00c
BLAKE2b-256 084ee15418fc46c21dc04d97e305528f998c1070ec83414f5ee385b2ff1ffc81

See more details on using hashes here.

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page