That is the logon page to my pfsense firewall
Maybe itās not allowing a mixed URL - calling an SSL page from within an iframe in a non-SSL caller? It may see it as a cross site attempt.
1 Like
Dashboard on Raspberry Pi3 7" display!
Got rid of sub pages and put everything on one page. I donāt have a lot of devices, not yet anyway! Not a lot of interactions but itās a work in progress.
Thanks for the awesome software!
6 Likes
Iāve noticed some odd behavior and Iām not sure if itās a bug or I have something setup incorrectly.
When I make a change the dash file and save the file then refresh the dashboard to view the changes I get an error that the dashboard canāt be found. I have to go to the original HELLO dashboard to view what dashboards are available click on the dashboard I want then it seems to work. The screen shot below is the error that I get when refresh.
Try doing a Shift + Refresh and see if it makes any difference.
1 Like
Iāve tried that and same issues. I have also tried across several devices that produce the same results.
Watch logs ā¦ tail -f /var/log/syslog
Does the iframe widget not support ssl webpages?
probably not, because the dashboard isnt ssl
1 Like
Been going nuts for not getting a simple notify call_service to work. After far too much headscratching and some swearing I finally found out that the message containing a % sign was the culprit. As far as I know this sort of thing is nowhere documented, so I am prone to call this a bug - albeit potentially/likely in Hass itself. Any of you know about a workaround, whilst this problem eventually gets solved by the respective devs ?
first i think you probably should try to find out where the problem lies.
what is the message you try to send and how?
can you send it the from out of HA?
to what are you sending it and can you send it to some other notify source?
Sorry for hijack this thread, but Iām having an issue with the latest beta.
Every time I restart HA, appdaemon/dashboard gets disconnected (obviously), but It doesnāt reconnects when HA is up and running again, so I have to restart appdaemon to get it connected.
In the logs I only see this
may 15 17:40:06 VM42 appdaemon[9297]: 2017-05-15 17:40:06.332379 WARNING Disconnected from Home Assistant, retrying in 5 seconds
may 15 17:40:11 VM42 appdaemon[9297]: 2017-05-15 17:40:11.501917 WARNING Disconnected from Home Assistant, retrying in 5 seconds
may 15 17:40:16 VM42 appdaemon[9297]: 2017-05-15 17:40:16.508238 WARNING Disconnected from Home Assistant, retrying in 5 seconds
may 15 17:40:21 VM42 appdaemon[9297]: 2017-05-15 17:40:21.513856 WARNING Disconnected from Home Assistant, retrying in 5 seconds
may 15 17:40:26 VM42 appdaemon[9297]: 2017-05-15 17:40:26.520698 WARNING Disconnected from Home Assistant, retrying in 5 seconds
may 15 17:40:31 VM42 appdaemon[9297]: 2017-05-15 17:40:31.543632 INFO Got initial state
may 15 17:40:33 VM42 appdaemon[9297]: 2017-05-15 17:40:33.546169 WARNING Disconnected from Home Assistant, retrying in 5 seconds
may 15 17:40:38 VM42 appdaemon[9297]: 2017-05-15 17:40:38.562820 INFO Got initial state
may 15 17:40:40 VM42 appdaemon[9297]: 2017-05-15 17:40:40.564248 WARNING Disconnected from Home Assistant, retrying in 5 seconds
may 15 17:40:45 VM42 appdaemon[9297]: 2017-05-15 17:40:45.580166 INFO Got initial state
may 15 17:40:47 VM42 appdaemon[9297]: 2017-05-15 17:40:47.580661 WARNING Disconnected from Home Assistant, retrying in 5 seconds
may 15 17:40:52 VM42 appdaemon[9297]: 2017-05-15 17:40:52.595292 INFO Got initial state
may 15 17:40:54 VM42 appdaemon[9297]: 2017-05-15 17:40:54.596431 WARNING Disconnected from Home Assistant, retrying in 5 seconds
may 15 17:40:59 VM42 appdaemon[9297]: 2017-05-15 17:40:59.608386 INFO Got initial state
may 15 17:41:01 VM42 appdaemon[9297]: 2017-05-15 17:41:01.610810 WARNING Disconnected from Home Assistant, retrying in 5 seconds
may 15 17:41:06 VM42 appdaemon[9297]: 2017-05-15 17:41:06.626843 INFO Got initial state
^C
dani@VM42:~/appdaemon$ sudo systemctl restart appdaemon
[sudo] password for dani:
dani@VM42:~/appdaemon$ journalctl -f -u appdaemon
-- Logs begin at lun 2017-05-15 15:34:30 CEST. --
may 15 17:40:54 VM42 appdaemon[9297]: 2017-05-15 17:40:54.596431 WARNING Disconnected from Home Assistant, retrying in 5 seconds
may 15 17:40:59 VM42 appdaemon[9297]: 2017-05-15 17:40:59.608386 INFO Got initial state
may 15 17:41:01 VM42 appdaemon[9297]: 2017-05-15 17:41:01.610810 WARNING Disconnected from Home Assistant, retrying in 5 seconds
may 15 17:41:06 VM42 appdaemon[9297]: 2017-05-15 17:41:06.626843 INFO Got initial state
may 15 17:41:08 VM42 appdaemon[9297]: 2017-05-15 17:41:08.627956 WARNING Disconnected from Home Assistant, retrying in 5 seconds
may 15 17:41:12 VM42 systemd[1]: Stopping AppDaemon service for Home Assistant...
may 15 17:41:12 VM42 systemd[1]: Stopped AppDaemon service for Home Assistant.
may 15 17:41:12 VM42 systemd[1]: Started AppDaemon service for Home Assistant.
may 15 17:41:13 VM42 appdaemon[10447]: 2017-05-15 17:41:13.888102 INFO AppDaemon Version 2.0.0beta3.5 starting
may 15 17:41:13 VM42 appdaemon[10447]: 2017-05-15 17:41:13.888887 INFO Apps are disabled
may 15 17:41:18 VM42 appdaemon[10447]: 2017-05-15 17:41:18.941304 INFO Got initial state
may 15 17:41:18 VM42 appdaemon[10447]: 2017-05-15 17:41:18.941522 INFO Starting dashboard
may 15 17:41:18 VM42 appdaemon[10447]: 2017-05-15 17:41:18.946219 INFO HADashboard Started
may 15 17:41:18 VM42 appdaemon[10447]: 2017-05-15 17:41:18.946413 INFO Listening on ('192.168.1.197', 5050)
may 15 17:41:18 VM42 appdaemon[10447]: 2017-05-15 17:41:18.949959 INFO Connected to Home Assistant 0.44.2
may 15 17:41:21 VM42 appdaemon[10447]: 2017-05-15 17:41:21.156731 INFO New dashboard connected: Casa
As you can see, It gets an initial state,but then it disconnects again.
My appdaemon conf is this. I have apps disabled for now, will use them when I get this issue back.
[AppDaemon]
ha_url = http://192.168.1.197:8123
ha_key = myhakey
logfile = STDOUT
errorfile = STDERR
threads = 10
dash_url = http://192.168.1.197:5050
#app_dir = /home/dani/appdaemon/conf/apps
disable_apps = 1
Any idea ? Thanks!!
It turned out to be plain simple: taking out the % sign was enough to get things going, so it is definitely the inclusion of this specific character (I suspect there may be others) that made it blow up. The bad news is that the same goes when trying through the dev panel in Hassā¦ Thatās why I said the bug is likely to be found there.
Not a question of life and death but still, if you can think of a workaroundā¦?
Could you try using an escape character? Iām assuming this is in the body of the message and not an included variable.
oke so you know it is in HA.
which notify component? have you tested more notify components?
Just for grins, try escaping the % sign with a leading \
% is one of those special characters that gets interpreted when itās in a string sometimes.
Everybody keeps repeating my suggestions lately! 
1 Like
Using Join notify. Tried single (eg gsm) or grouped (gsm + chrome) - makes no difference.
Tried the escape route already before posting - no joy. But in that case (in the dev section) Hass at least throws āError parsing JSON: SyntaxError: Unexpected token % in JSON at position 41ā at me, instead of silently failing. Not clear to me why the % should be offending Jsonā¦
i tried it with pushbullet like this:
{"message":"even testen of een % teken gestuurd kan worden"}
no error, the message gets send without any problem.
lannouncer has no problem with it also.
so i am curious what message you try to send and how, because json has no problem with it.