The Sensor widget automatically detects text vs numbers and applies a different - they are both in the variables file, sensor_value_style and sensor_text_style
Yes, it’s a URL not a path to a file. At some point I’ll add a directory you can put pics in to be served up.
Hey Thunder,
What program is that you are using for editing?
That’s SublimeText. I started using it after I had a stray non UTF-8 character cause a crash in HA. This can happen when you use copy and paste from an HA Doc example; it’ll take the degree symbol or something and a normal text editor can just save it in a non UTF-8 format.
Ever since then, I’ve been using SublimeText, which among all of it’s other options, allows you to force saving in a specific format.
Took a little while to get used to and to figure out how to configure the interface to the way I wanted but it’s now my primary editor.
Thanks… just changes sensor_text_style and it works.
thanks for the directory pic for iframe in the future 
nice feature i think for homescreen
Just being courius …Is there also more planned for appdaemon like front-end configuration?
Do u already have a future feature list for dasbaord
? New release panned already …Sorry I’m so facinated of your work that i wanna know how it will continue 
like watching a series on TV …lol
I have a long list of stuff I want to get to, but no details!
I’m getting this up and running inside a docker image. Everything works but there seems to be an issue with the dash_url in the config:
If I set it to: dash_url = http://172.17.0.3:5050 where the IP is the address of the docker image then the system comes up fine but If I try to access the dashboard then the dashboard links are all using the internal address of the docker image which is not accessible on the LAN
if I set it to: dash_url = http://192.168.1.190:5050 where the IP is the address of the docker host that has port 5050 forwarded then the system throws an error at startup: error while attempting to bind on address 192.168.1.190 because that is not a local address
It feels like the deamon should be binding to 0.0.0.0:5050 (ie. all addresses) or a parameter with a bind address and an environment variable/parameter is needed to tell the container what URL it is listening on.
Am I missing something?
Are you running beta2? The behavior should be better.
In beta 2, the browser will connect back to the address it loaded from. When you say links, do you meant the front page that lists the available dashboards?
Yes those links.
I go to http://192.168.1.190 and get the generated page with in my case hello -> that takes me to http://172/17/0/3:5050/Hello. If I change the address I get the hello page.
I pulled the code yesterday - log says 2.0.0beta2.
OK, sounds like a bug, I’ll get a fix in place for the next beta. You should still be able to navigate to the Dashboard directly right?
Yes just hand cranks the URL…got a test panel working that apart from the time shows no data…off to read the forums to figure out why.
SO I think because I have the server running on the internal docker IP and am accessing via the docker host IP I am running foul of the cross site protections I have read about in the code. I am seeing similar behaviour where the icons are not rendering until I click and no data is being displayed from my entities.
Giving up for now - I may try running it on a macvlan connection with its own IP address a bit later and not using the default docker bridge
Did anyone try to proxy appdaemon through nginx.
I have homeassistant set up this way, but now I am trying to get appdaemon working through the proxy without any luck.
here is the nginx default site conf
server {
server_name my.doma.in;
listen 80;
return 301 https://$host$request_uri;
if ($allowed_country = no) {
return 444;
}
}
#
# HTTPS server
#
server {
listen 443;
server_name my.doma.in;
if ($allowed_country = no) {
return 444;
}
root html;
index index.html index.htm;
add_header Strict-Transport-Security "max-age=31536000; includeSubdomains";
ssl on;
ssl_certificate /etc/nginx/my.self.signed.web.crt;
ssl_certificate_key /etc/nginx/my.self.signed.web.key;
ssl_session_timeout 5m;
# ssl_session_cache builtin:1000 shared:SSL:10m;
ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
# ssl_ciphers HIGH:!aNULL:!eNULL:!EXPORT:!CAMELLIA:!DES:!MD5:!PSK:!RC4;
ssl_ciphers "EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH:!aNULL:!eNULL:!EXPORT:!DES:!MD5:!PSK:!RC4";
ssl_prefer_server_ciphers on;
ssl_session_cache shared:SSL:10m;
access_log /var/log/nginx/ujfalu_access.log;
proxy_buffering off;
location / {
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $connection_upgrade;
proxy_http_version 1.1;
proxy_pass http://my.doma.in:5050;
# proxy_read_timeout 90;
# proxy_redirect http://192.168.112.254:5050 https://my.doma.in;
proxy_redirect http:// https://;
auth_basic "Jelentkezz be";
auth_basic_user_file /etc/nginx/.htpasswd;
}
}
Appdaemon conf
[AppDaemon]
ha_url = http://my.doma.in:2012
logfile = /var/opt/homeassistant/appdaemon/appd_log.log
#logfile = STDOUT
#errorfile = STDERR
errorfile = /var/opt/homeassistant/appdaemon/appd_err.log
threads = 10
#app_dir = /var/opt/homeassistant/appdaemon/conf/apps
dash_url = http://my.doma.in:5050
dash_dir = /var/opt/homeassistant/appdaemon/conf/dashboards
disable_apps = 1
# Apps
#[hello_world]
#module = hello
#class = HelloWorld
If I change my.doma.in in the appdaemon.cfg to my internal IP then it works without any problems (from my internal network), but if I try it this way then this is what I get:
And this is what it looks like when its working:
afaik the external access is not supported yet. Wait to next version
oooh, ok, then. thx
I mode no promises! It will be after the beta because it wasn’t an original design goal. Even then I am of a mind to suggest NGINX, but by then I’ll have tried it myself to see what breaks
fair enough! we are more than thankful for your work. is there already something new ?
Beta 3 will be a little while longer - I have been rather busy at work and will be again next week, but we will have an alarm widget, a camera widget, an RSS widget and a meter widget and some other bits and pieces.
My goal is to make beta 3 fully able to replace the old dashboard and be the release candidate.
WOw! ambicious! great news… the camera widget is awesome… even if my workaround works awesome and fluent like never before in combination with hass
I’m not sure if it’s already something that I can do with a skin, or if it’s a new feature that may or may not have already been requested. Can we make it so that when we hover over a widget it changes it’s opacity to 1 from whatever it currently is? For example, my garage skin has the really sweet GT on it. My widgets are at a low opacity so they don’t obscure the car to much. It would be nice if when I hover over them, if they brightened up a bit so that you can see them a little better. Or maybe also if the widget is “on” the widget stays at full opacity. Does that make any sense?
