referencing to the entity is not (yet) possible
you could try to use your HA pasword in stead of token.
No change commenting out base_url:.
Damn, thought I was on to something.
1 Like
I’ts not working.
I could write a script to download the image in memory (tmpfs to preserve the read write on my sdcard) and load it as local image…
I guess I’ll just let sleeping dogs lie. I’m more likely to experience a power outage than an internet outage here anyway - underground fiber. Since I moved here 5 years ago, I’ve had two outages; one of those was recent and turned out to be a bad switch at the fiber aggregator (I noticed it first but it affected a lot of others) for a total down time of about 8-10 hours.
The other was during Super Storm Sandy, but to be fair that was the largest hurricane in 200 years. And the power was out too. LOL
I’d try NGINX, but I can’t seem to find a resource that is noobish enough to make me comfortable attempting the installation and set up. I’m not a network engineer, so it’s a weak point.
thats another option.
using the iframe widget.
@rpitera the basic setup from nginx wasnt that difficult. i didnt trust myselve at first also, but it is worth the efford.
I thought that was how you were supposed to do it, at least when I was beta testing it was. All of my camera widgets use the HA proxy. (HA ones anyways. Some of my radars are direct URL.)
EDIT: I’m using this with the camera widget and have no problems. If you want to use the direct URL, then iframe should work.
You should do a write up for me and Chip! (He PM’d me thinking I was running it and I told him he must have confused me with you! LOL)
to do a write up i have to delete it and install all over again.
and i am glad i have it up and running 
but after installing nginx you could get my configuration from nginx
and thats the difficult part installing isnt more difficult then installing AD
Yep, Iframe is the way to go, Camera with local file also get an changing token
1 Like
Guess if it works it works!
Just to come full circle, in my dns server i have a primary zone that is the same domain as my external dyndns given domain. Then within that I have a NS Record that points back to my server’s ip address.
This means that I can use the full url externally and internally and they both point back to my server. Saves the headache of having to have a wan and lan setting for all my apps that I use; VNC/HASS etc…
2 Likes
i will try that also in the future.
havent used a local dns server because i have had terrible headaches from dns servers in the past
Some help to create skins
I’ve followed the indication present in the “variable.yaml”
Created a copy of one of the skins in the /home/pi/appdaemon_dashboard/appdaemon/appdaemon/assets/css/perso and edited the content, but I’ve got this error, when I try to load it at http://192.168.0.26:3040/Main?skin=perso
What is wrong in my steps ?
Off course, I’ve reloaded appdeamon and also tried to add “dash_force_compile: 1” in the appdaemon.yaml
I’ve also tried to change the background from an existing skin, but it don’t affect the result on the dashboard 
could be a rights problem.
but the best place to create a custom skin is here:
/home/pi/appdaemon_dashboard/appdaemon/appdaemon/conf/custom_css/yourskin
(thats also mentioned in the DASHBOARD.md if i am not mistaken)
the dir should contain 2 files:
dashboard.css
variables.yaml
you can copy them from 1 of the other skins and edit them.
changing the background is possible, but i cant tell you what has gone wrong in your case if you dont tell me how you tried it.
remember that your browser could also give you cashing problems. lots of times people try to edit skins and it only takes effect when they clear the cache from the browser.
another common problem it when the compliling has gone wrong after a user mistake and some compiled files dont get refrehed.
the dir
/home/pi/appdaemon_dashboard/appdaemon/appdaemon/conf/compiled
can be emptied at any time to make sure that the files really get recompiled.
Getting the same issue here with SSL with the latest version of the BETA. Wasn’t present in beta2 at least…
urllib3.exceptions.SSLError: hostname '192.168.0.43' doesn't match 'my.fqdn'
^ When using https://192.168.0.43:8123
2017-06-22 18:35:49.520454 WARNING Unable to connect to Home Assistant, retrying in 5 seconds
2017-06-22 18:35:49.521037 WARNING ------------------------------------------------------------
2017-06-22 18:35:49.521427 WARNING Unexpected error:
2017-06-22 18:35:49.521735 WARNING ------------------------------------------------------------
2017-06-22 18:35:49.530679 WARNING Traceback (most recent call last):
File "/usr/local/lib/python3.4/dist-packages/urllib3/connection.py", line 141, in _new_conn
(self.host, self.port), self.timeout, **extra_kw)
File "/usr/local/lib/python3.4/dist-packages/urllib3/util/connection.py", line 83, in create_connection
raise err
File "/usr/local/lib/python3.4/dist-packages/urllib3/util/connection.py", line 73, in create_connection
sock.connect(sa)
ConnectionRefusedError: [Errno 111] Connection refused
^ When using my external url which is portforwarded from 443 to 8123.
This show as the following without debug log level enabled:
2017-06-23 00:57:14.457418 WARNING Disconnected from Home Assistant, retrying in 5 seconds
Did anyone get to the bottom of it? I’d prefer keeping my url as it is but i’ve had to change the commtype to SSE to get it to work temporarily.
does this beta work behind a reverse proxy?
with ha_url: https://xxx.duckdns.org
pi@hassbian:~/appdaemon_dashboard/appdaemon $ python3 -m appdaemon.appdaemon -c /home/pi/appdaemon_dashboard/appdaemon/conf --commtype SSE -D DEBUG
2017-06-23 07:36:19.611798 INFO AppDaemon Version 2.0.0beta4 starting
2017-06-23 07:36:19.612328 INFO Configuration read from: /home/pi/appdaemon_dash board/appdaemon/conf/appdaemon.yaml
2017-06-23 07:36:19.612665 DEBUG get_ha_config()
2017-06-23 07:36:19.628677 WARNING Unable to connect to Home Assistant, retrying in 5 seconds
2017-06-23 07:36:19.629142 WARNING --------------------------------------------- ---------------
2017-06-23 07:36:19.629464 WARNING Unexpected error:
2017-06-23 07:36:19.629760 WARNING --------------------------------------------- ---------------
2017-06-23 07:36:19.638757 WARNING Traceback (most recent call last):
File "/usr/local/lib/python3.4/dist-packages/urllib3/connection.py", line 141, in _new_conn
(self.host, self.port), self.timeout, **extra_kw)
File "/usr/local/lib/python3.4/dist-packages/urllib3/util/connection.py", line 83, in create_connection
raise err
File "/usr/local/lib/python3.4/dist-packages/urllib3/util/connection.py", line 73, in create_connection
sock.connect(sa)
ConnectionRefusedError: [Errno 111] Connection refused
Duringwith ha_url: https://192.168.1.238:8123
That’s enough for me. I quit this project
pi@hassbian:~/appdaemon_dashboard/appdaemon $ python3 -m appdaemon.appdaemon -c /home/pi/appdaemon_dashboard/appdaemon/conf --commtype SSE -D DEBUG
2017-06-23 07:38:50.545111 INFO AppDaemon Version 2.0.0beta4 starting
2017-06-23 07:38:50.546009 INFO Configuration read from: /home/pi/appdaemon_dashboard/appdaemon/conf/appdaemon.yaml
2017-06-23 07:38:50.546583 DEBUG get_ha_config()
2017-06-23 07:38:50.660202 WARNING Unable to connect to Home Assistant, retrying in 5 seconds
2017-06-23 07:38:50.661041 WARNING ------------------------------------------------------------
2017-06-23 07:38:50.661609 WARNING Unexpected error:
2017-06-23 07:38:50.662154 WARNING ------------------------------------------------------------
2017-06-23 07:38:50.670986 WARNING Traceback (most recent call last):
File "/usr/local/lib/python3.4/dist-packages/urllib3/connectionpool.py", line 600, in urlopen
chunked=chunked)
File "/usr/local/lib/python3.4/dist-packages/urllib3/connectionpool.py", line 345, in _make_request
self._validate_conn(conn)
File "/usr/local/lib/python3.4/dist-packages/urllib3/connectionpool.py", line 844, in _validate_conn
conn.connect()
File "/usr/local/lib/python3.4/dist-packages/urllib3/connection.py", line 346, in connect
_match_hostname(cert, self.assert_hostname or hostname)
File "/usr/local/lib/python3.4/dist-packages/urllib3/connection.py", line 356, in _match_hostname
match_hostname(cert, asserted_hostname)
File "/usr/local/lib/python3.4/dist-packages/urllib3/packages/ssl_match_hostname/_implementation.py", line 154, in match_hostname
% (hostname, dnsnames[0]))
urllib3.packages.ssl_match_hostname._implementation.CertificateError: hostname '192.168.1.238' doesn't match xxx.duckdns.org'
During handlinSeems not …