how did you try to access the dashboard, and what is in it?
Accessed from Google Chrome.
The content of the file is:
#### Cameras
title: Cameras
widget_dimensions: [114, 114]
widget_size: [1, 1]
widget_margins: [5, 5]
columns: 8
global_parameters:
use_comma: 0
precision: 1
use_hass_icon: 1
layout:
- clock(2x1), jmra_presence, lslma_presence, bama_presence, panel_label (3x1)
- spacer, spacer, spacer, spacer, spacer, cam_rafa(3x2)
- cam02_entrada(2x2), cam01_hall(2x2)
-
- include: TemplateNavigation
clock:
widget_type: clock
widget_style: "border-radius: 6px;"
time_format: 24hr
show_seconds: 1
time_style: "color: #00aaff !important"
date_format_country: "pt"
date_format_options:
weekday: "long"
day: "2-digit"
month: "2-digit"
year: "numeric"
jmra_presence:
widget_type: device_tracker
widget_style: "border-radius: 6px;"
title: Jorge
device: jmra
lslma_presence:
widget_type: device_tracker
widget_style: "border-radius: 6px;"
title: Lara
device: lslma
bama_presence:
widget_type: device_tracker
widget_style: "border-radius: 6px;"
title: Bia
device: bama
panel_label:
widget_type: label
widget_style: "border-radius: 6px;"
text: CAMERAS
value_style: "margin-top: -10px;"
####
cam_rafa:
widget_type: camera
widget_style: "border-radius: 6px;"
entity_picture: https://192.168.1.200:8123/api/camera_proxy/camera.quarto_3?token=<token>&api_password=<password>
refresh: 10
cam01_hall:
widget_type: camera
widget_style: "border-radius: 6px;"
entity_picture: https://192.168.1.200:8123/api/camera_proxy/camera.hall_de_entrada?token=<token>&api_password=<password>
refresh: 10
cam02_entrada:
widget_type: camera
widget_style: "border-radius: 6px;"
entity_picture: https://192.168.1.200:8123/api/camera_proxy/camera.porta_da_rua?token=<token>&api_password=<password>
refresh: 10
<token>
and <password>
are “sanitizers”… cam02_entrada
doesn’t work on both dashboard and HA
Sorry to drift off topic.
@ReneTode would you point me at some config examples for Nginx please. I like that setup.
i can only give you my setup.
and i dont use a dashboard outside my home.
but it might give you some clues:
server {
listen 80;
server_name *.duckdns.org;
return 301 https://$server_name$request_uri;
}
server {
listen 443 ssl;
server_name anything.duckdns.org;
ssl on;
ssl_certificate /etc/letsencrypt/live/anything.duckdns.org/fullchain.pem; # /etc/nginx/cert.crt;
ssl_certificate_key /etc/letsencrypt/live/anything.duckdns.org/privkey.pem; # /etc/nginx/cert.key;
ssl_session_cache shared:SSL:10m;
ssl_protocols TLSv1.1 TLSv1.2;
ssl_ciphers 'EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH';
ssl_prefer_server_ciphers on;
proxy_buffering off;
location / {
proxy_pass http://your_ip:8123;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
}
location /api/appdaemon/ {
allow all;
proxy_pass http://your_ip:5051;
proxy_set_header Host $host;
proxy_redirect http:// http://;
}
location /custom_css/ {
allow all;
proxy_pass http://your_ip:5050;
proxy_set_header Host $host;
proxy_redirect http:// http://;
}
}
dont forget i dont use hassio.
and i did setup API in appdaemon to be able to call appdaemon apps by alexa.
i have read that for hassio users caddy is also a good and simple option.
Thanks for this. I’m not using hassio either. I build from bits so I know where things are and how they interact.
John
Still getting the robots.txt
error a couple of times a day but everything works fine apart from that.
How to use encryption with AppDaemon? Is the api_ssl_certificate
and api_ssl_key
the same as HA?
api is only if you want to reach appdaemon from another program, not for the dashboard.
what would you like the encryption for?
if you like to use dashboard and HA both from the outside, you will be better of using a proxyserver with encryption.
I’m already using let’s encrypt and duckdns to access HA from the outside but not using a proxy.
But now I need to access my dashboard from outside. Can you give me some hints? I’m using Hassio.
it seems caddy is easy for hassio users.
i use NGINX