Home Panel - A web frontend for controlling the home

Home Panel

Build Status

GitHub Release Project Stage License

GitHub Activity Project Maintenance

Docker Version Docker Pulls

Supports armhf Architecture Supports aarch64 Architecture Supports amd64 Architecture Supports i386 Architecture

Buy me a coffee

A web frontend for controlling the home. Integrates with
Home Assistant as an additional frontend.



  • Supports Home Assistant entities, cameras, news feeds, iframes and
  • Made for touch screens and desktops with a sideways scrolling Material Design
  • Fully customizable interface.
  • Custom theme support.
  • Full in application configuration UI.

Documentation / Setup

Setup and configuration for the app is available here


Support / Discussion

Code of Conduct

Contribution Guidelines




Release 0.4.0

Full Changelog


  • :sparkles: add link support (#17)
  • :sparkles: radio support (#15)
  • :books: update docs
  • :arrow_up: update packages

This release adds the requirement of https://github.com/timmo001/home-panel-api

1 Like

HASS.io Addon

Now I am happy with security and the app has a decent amount of features, I am going to look into creating an addon for hass.io

See progress on this on the issue page:


Release 0.4.1

Full Changelog


  • :rocket: fix ci build
  • :books: change to mkdocs
  • :boat: shrink container by cleaning yarn cache
  • :fire: fix missing entity or missing config

Hi @timmo001 ,

SSL is mandatory? tried to install with flag REACT_APP_HASS_SSL=‘false’ and after 30 secs, the docker stops running

Hi @revin,

SSL isn’t mandatory, however is recommended when using Home Panel in a production environment

Can you post the logs?

If using docker-compose:

docker-compose logs -f

or docker:

docker logs -f NAME_OF_CONTAINER

Hi @timmo001,

The detail error is:

nginx: [emerg] BIO_new_file("/ssl/fullchain.pem") failed (SSL: error:02FFF002:system library:func(4095):No such file or directory:fopen('/ssl/fullchain.pem', 'r') error:20FFF080:BIO routines:CRYPTO_internal:no such file)

Here you have the fulllog:


It seems that I don’t write the correct syntax to avoid SSL. This is the full docker instruction:

docker run -d --name="panel" -e REACT_APP_HASS_HOST='' -e REACT_APP_HASS_PASSWORD='API_PASSWORD' -e REACT_APP_HASS_SSL='false' -p 8234:443 -v /docker/panel/ssl:/ssl -v /docker/panel/config.json:/usr/src/app/config.json timmo001/home-panel


1 Like

Ah glad you managed to fix it.

I will add some examples for those who don’t want to use ssl to the docs

Hi @timmo001

Sorry but english it’s not my native language and I didn’t explain well.

I wanted to explain that the sintax that I’m using it’s not the correct to avoid SSL. I’m still not able to start the docker.

I also tried with the -e REACT_APP_HASS_SSL='false' option but I get the same error.

1 Like

Looks like there is an issue with the nginx config file that is copied on build. I have found the issue in the dockerfile and and fixed it.

This will be available in the next release, coming in the next few hours. Thanks for the heads up @revin!

Good news!

Thanks @timmo001

Release 0.4.2

Full Changelog


  • :hammer: fix radio hidden position
  • :hammer: fix theme selection
  • :sparkles: added screenshots and more examples to docs
  • :rocket: temporary fix for #28
  • :boat: fix docker for non ssl setups
  • :books: update docs to include unsecure examples

Hi @timmo001

Just Installed 0.4.3. Specifying -p 8234:443 option, I can’t connect to the app. I’ve used the --net=host option and now is able to bind to port 80

now I can see the app but I’m stuck on “attemting to connect to Hass”.

Is it possible to see the apps logs? with docker logs only get the info until the nginx start process.


I’ve been working on it and now I’m able to start on 8234 port without --net option but I’m stuck on “attemting to connect hass”

I 've tried with -e REACT_APP_HASS_HOST='' and -e REACT_APP_HASS_HOST='' but i get the same error.

Hi @revin,

If you are using Chrome, you can press F12 to bring up the developer console, which will give you any errors that arise.

You might want to try setting REACT_APP_HASS_SSL='true' since the secure option is likely the default with HASS now

You pointed on th right direction

WebSocket connection to 'wss://' failed: Error in connection establishment: net::ERR_SSL_PROTOCOL_ERROR

Will try later to generate a certificate and build with SSL option. I’d prefer to stay out SSL configs as I manage them from another nginx and FW.

1 Like

Hope the hassio addon Is ready soon

Release v0.4.4

Full Changelog


  • :arrow_up: upgrade packages
  • :hammer: remove redundant code
  • :boat: remove useless build step
  • :boat: add api to compose file
  • :books: update docs
  • :framed_picture: optimised images

Keep an eye on the issue page for updates on the HASS.io addon:


1 Like

Release v0.4.5

Full Changelog


  • :hammer: allow for hassio ws proxy

This is a small change to allow for the use of hassio’s websocket proxy in the effort to create the hassio addon

1 Like

Any chance of making this work with a non-SSL HomeAssistant setup? I’m getting the same issue as above where it can’t get past “Attempting to connect to HASS…”

Checking in the JS Console I see it fails to connect to wss://…

Here’s the logfile from docker, as you can see, the build realizes I don’t want the SSL config, but in the actual page code, the check of process.env.REACT_APP_HASS_SSL still seems to return true.

Copy disabled SSL nginx config,
Copy config..,
Build app..,
yarn run v1.7.0,
$ react-scripts build --production,
Creating an optimized production build...,
Compiled successfully.,
File sizes after gzip:,
  213.59 KB  build/static/js/main.8047b977.js,
  20.91 KB   build/static/css/main.12aa7665.css,
The project was built assuming it is hosted at the server root.,
You can control this with the homepage field in your package.json.,
For example, add this to build it for GitHub Pages:,
  "homepage" : "http://myname.github.io/myapp",,
The build folder is ready to be deployed.,
You may serve it with a static server:,
  yarn global add serve,
  serve -s build,
Find out more about deployment here:,
Done in 37.69s.,
Move build files to html directory..,
Run nginx server..,