updated to stable 3.0.0, deleted the content of the compiled dir and all the logs… but no change. Still no files in the compiled directory 
they cant be the same because you changed things 
so thats why i ask about them.
Sure, no problem.
Below are the logs I collected just after last night testing. As I mentioned, nothing in the logs whatsoever. This time not even when trying to access the FirePanel.
$ cat appdaemon/logs/error.log
[empty]
$ cat appdaemon/logs/access.log
[empty]
$ cat appdaemon/logs/appdaemon.log
2018-03-19 22:39:53.344333 INFO AppDaemon Version 3.0.0 starting
2018-03-19 22:39:53.345092 INFO Configuration read from: /home/homeassistant/.homeassistant/appdaemon/conf/appdaemon.yaml
2018-03-19 22:39:53.347276 INFO AppDaemon: Starting Apps
2018-03-19 22:39:53.353962 INFO AppDaemon: Loading Plugin HASS using class HassPlugin from module hassplugin
2018-03-19 22:39:53.573976 INFO AppDaemon: HASS: HASS Plugin Initializing
2018-03-19 22:39:53.575290 INFO AppDaemon: HASS: HASS Plugin initialization complete
2018-03-19 22:39:53.576204 INFO Starting Dashboards
2018-03-19 22:39:53.700734 INFO API is disabled
2018-03-19 22:39:53.704134 WARNING AppDaemon: HASS: Disconnected from Home Assistant, retrying in 5 seconds
2018-03-19 22:39:58.710281 WARNING AppDaemon: HASS: Disconnected from Home Assistant, retrying in 5 seconds
2018-03-19 22:40:03.714639 WARNING AppDaemon: HASS: Disconnected from Home Assistant, retrying in 5 seconds
2018-03-19 22:40:08.719079 WARNING AppDaemon: HASS: Disconnected from Home Assistant, retrying in 5 seconds
2018-03-19 22:40:21.192850 WARNING AppDaemon: HASS: Disconnected from Home Assistant, retrying in 5 seconds
2018-03-19 22:40:26.198367 WARNING AppDaemon: HASS: Disconnected from Home Assistant, retrying in 5 seconds
2018-03-19 22:40:31.203956 WARNING AppDaemon: HASS: Disconnected from Home Assistant, retrying in 5 seconds
2018-03-19 22:40:36.283287 INFO AppDaemon: HASS: Connected to Home Assistant 0.65.5
2018-03-19 22:40:36.498067 INFO AppDaemon: Adding /home/homeassistant/.homeassistant/appdaemon/apps to module import path
2018-03-19 22:40:36.498760 INFO AppDaemon: Processing restart for HASS
2018-03-19 22:40:38.476002 INFO AppDaemon: App initialization complete
and appdaemon was properly running…
● [email protected] - AppDaemon
Loaded: loaded (/etc/systemd/system/[email protected]; enabled; vendor preset: enabled)
Active: active (running) since Mon 2018-03-19 22:39:47 PDT; 7min ago
Main PID: 526 (appdaemon)
CGroup: /system.slice/system-appdaemon.slice/[email protected]
└─526 /srv/homeassistant/bin/python3 /srv/homeassistant/bin/appdaemon -c /home/homeassistant/.homeassistant/appdaemon/conf
Mar 19 22:39:47 hass49 systemd[1]: Started AppDaemon.
However I did check I could access the server on that port from my machine, see below:
$ telnet 10.1.190.49 5050
Trying 10.1.190.49...
Connected to 10.1.190.49.
Escape character is '^]'.
^[^]
telnet> quit
Connection closed.
One more thing, I can access my homeassistant install on port 8123 no problem, so nothing wrong with the web server or anything…
Let me know if I can provide more info to get to the bottom of this… this issue is driving me crazy! I’d love to start using my wall tablets once again…
i just realised:
you have AD and HASS in a venv.
do you have them installed in the same venv? or 2 seperate venvs?
since the last few weeks there is trouble when its just 1 venv.
it should generate errors though, so i dont expect that to be the cause, but i need to make sure.
appdaemon seems to run correctly, so in that case it only can be a cashing problem in the browser(s) you use.
Yes, I do have both AD and HASS in the same venv.
Also I did try with 3 different browsers, no luck.
in that case i advice you to create a second venv for AD.
or at least make sure you install/upgrade HA AFTER you have updated AD. (so if you have upgraded AD now without updateing HA, first update HA)
if you are up to date with HA, then downgrade 1 level and upgrade again.
I created a new user and a new venv for appdaemon, changed the permission but still same result. See logs below:
● [email protected] - AppDaemon
Loaded: loaded (/etc/systemd/system/[email protected]; disabled; vendor preset: enabled)
Active: active (running) since Sun 2018-03-25 20:26:39 PDT; 3min 20s ago
Main PID: 15008 (appdaemon)
CGroup: /system.slice/system-appdaemon.slice/[email protected]
└─15008 /srv/appdaemon/bin/python3 /srv/appdaemon/bin/appdaemon -c /home/homeassistant/.homeassistant/appdaemon/conf
Mar 25 20:26:39 hass49 systemd[1]: Started AppDaemon.
permissions:
$ ls -la appdaemon/
total 24
drwxr-xr-x 6 appdaemon casa 4096 Mar 16 14:20 .
drwxr-xr-x 13 homeassistant casa 4096 Mar 25 20:27 ..
drwxr-xr-x 2 appdaemon casa 4096 Mar 17 14:10 apps
drwxr-xr-x 3 appdaemon casa 4096 Mar 24 20:26 conf
drwxr-xr-x 2 appdaemon casa 4096 Mar 24 20:18 dashboards
drwxr-xr-x 2 appdaemon casa 4096 Mar 24 20:25 logs
systemd service:
[Unit]
Description=AppDaemon
[email protected]
[email protected]
[Service]
Type=simple
User=appdaemon
ExecStart=/srv/appdaemon/bin/appdaemon -c /home/homeassistant/.homeassistant/appdaemon/conf
[Install]
WantedBy=multi-user.target
logs:
$ cat appdaemon/logs/appdaemon.log
2018-03-25 20:26:42.469103 INFO AppDaemon Version 3.0.0 starting
2018-03-25 20:26:42.470571 INFO Configuration read from: /home/homeassistant/.homeassistant/appdaemon/conf/appdaemon.yaml
2018-03-25 20:26:42.472664 INFO AppDaemon: Starting Apps
2018-03-25 20:26:42.478221 INFO AppDaemon: Loading Plugin HASS using class HassPlugin from module hassplugin
2018-03-25 20:26:42.531045 INFO AppDaemon: HASS: HASS Plugin Initializing
2018-03-25 20:26:42.532035 INFO AppDaemon: HASS: HASS Plugin initialization complete
2018-03-25 20:26:42.532824 INFO Starting Dashboards
2018-03-25 20:26:42.548093 INFO API is disabled
2018-03-25 20:26:42.565532 INFO AppDaemon: HASS: Connected to Home Assistant 0.65.6
2018-03-25 20:26:42.670674 INFO AppDaemon: Got initial state from namespace default
2018-03-25 20:26:44.807038 INFO AppDaemon: Adding /home/homeassistant/.homeassistant/appdaemon/apps to module import path
2018-03-25 20:26:44.808461 INFO AppDaemon: App initialization complete
and my config:
secrets: /home/homeassistant/.homeassistant/appdaemon/conf/secrets.yaml
log:
#logfile: STDOUT
#errorfile: STDERR
accessfile: /home/homeassistant/.homeassistant/appdaemon/logs/access.log
errorfile: /home/homeassistant/.homeassistant/appdaemon/logs/error.log
logfile: /home/homeassistant/.homeassistant/appdaemon/logs/appdaemon.log
logsize: 100000
log_generations: 10
appdaemon:
threads: 10
disable_apps: 1
app_dir: /home/homeassistant/.homeassistant/appdaemon/apps
plugins:
HASS:
type: hass
ha_url: http://10.1.190.49:8123
ha_key: !secret dash_password
namespace: default
hadashboard:
dash_url: http://10.1.190.49:5050
#dash_password: !secret dash_password
dash_dir: /home/homeassistant/.homeassistant/appdaemon/dashboards
accessfile: /home/homeassistant/.homeassistant/appdaemon/logs/dash_access.log
dash_compile_on_start: 1
all other logs empty… and still nothing in the compiled dir
$ ls -la appdaemon/conf/compiled/
total 16
drwxr-xr-x 4 appdaemon casa 4096 Mar 24 20:25 .
drwxr-xr-x 3 appdaemon casa 4096 Mar 24 20:26 ..
drwxr-xr-x 2 appdaemon appdaemon 4096 Mar 24 20:25 css
drwxr-xr-x 2 appdaemon appdaemon 4096 Mar 24 20:25 javascrip
Not really sure what else to do… I think I’m going to just rebuild on a new system and try to get appdaemon running on that, if that works I’ll migrate my config over.
there is not nothing in the compiled dir.
there is a javascrip dir that doesnt belong there.
and in the compiled dir nothing will appaer unless a dashboard is loaded.
try creating a dashboard like this:
title: test
widget_dimensions: [120, 120]
widget_size: [1,1]
widget_margins: [10, 10]
columns: 4
myclock:
widget_type: clock
show_seconds: 1
layout:
- myclock
save it as hello.dash in your dashboards directory and open it in google chrome with
http://10.1.190.49:5050/hello
and i just noticed this:
ha_key: !secret dash_password
i think you give the wrong password there
the directories are created by appdaemon at start, as compiled dir was empty before to launch the service. when I said nothing I meant, no content beside those 2 empty directories.
the password is correct as you can see in the logs it connects fine to homeassistant.
I created a test.dash and I tried to load it, no change. See below:
$ cat logs/appdaemon.log
2018-03-24 20:25:07.413858 INFO AppDaemon Version 3.0.0 starting
2018-03-24 20:25:07.414583 INFO Configuration read from: /home/homeassistant/.homeassistant/appdaemon/conf/appdaemon.yaml
2018-03-24 20:25:07.416570 INFO AppDaemon: Starting Apps
2018-03-24 20:25:07.422251 INFO AppDaemon: Loading Plugin HASS using class HassPlugin from module hassplugin
2018-03-24 20:25:07.485781 INFO AppDaemon: HASS: HASS Plugin Initializing
2018-03-24 20:25:07.486799 INFO AppDaemon: HASS: HASS Plugin initialization complete
2018-03-24 20:25:07.487618 INFO Starting Dashboards
2018-03-24 20:25:07.510405 INFO API is disabled
2018-03-24 20:25:07.528507 INFO AppDaemon: HASS: Connected to Home Assistant 0.65.6
2018-03-24 20:25:07.631901 INFO AppDaemon: Got initial state from namespace default
2018-03-24 20:25:09.747217 INFO AppDaemon: Adding /home/homeassistant/.homeassistant/appdaemon/apps to module import path
2018-03-24 20:25:09.748701 INFO AppDaemon: App initialization complete
2018-03-25 20:26:42.469103 INFO AppDaemon Version 3.0.0 starting
2018-03-25 20:26:42.470571 INFO Configuration read from: /home/homeassistant/.homeassistant/appdaemon/conf/appdaemon.yaml
2018-03-25 20:26:42.472664 INFO AppDaemon: Starting Apps
2018-03-25 20:26:42.478221 INFO AppDaemon: Loading Plugin HASS using class HassPlugin from module hassplugin
2018-03-25 20:26:42.531045 INFO AppDaemon: HASS: HASS Plugin Initializing
2018-03-25 20:26:42.532035 INFO AppDaemon: HASS: HASS Plugin initialization complete
2018-03-25 20:26:42.532824 INFO Starting Dashboards
2018-03-25 20:26:42.548093 INFO API is disabled
2018-03-25 20:26:42.565532 INFO AppDaemon: HASS: Connected to Home Assistant 0.65.6
2018-03-25 20:26:42.670674 INFO AppDaemon: Got initial state from namespace default
2018-03-25 20:26:44.807038 INFO AppDaemon: Adding /home/homeassistant/.homeassistant/appdaemon/apps to module import path
2018-03-25 20:26:44.808461 INFO AppDaemon: App initialization complete
$ cat logs/error.log
$ cat logs/access.log
2018-03-26 19:51:05.684369 INFO Compiling dashboard 'test'
2018-03-26 19:51:06.201793 WARNING Dashboard 'test' not found
2018-03-26 19:51:06.202644 WARNING ------------------------------------------------------------
2018-03-26 19:51:06.203065 WARNING Unexpected error during DASH creation
2018-03-26 19:51:06.203399 WARNING ------------------------------------------------------------
2018-03-26 19:51:06.210888 WARNING Traceback (most recent call last):
File "/srv/appdaemon/lib/python3.5/site-packages/appdaemon/dashboard.py", line 822, in get_dashboard
with open(include_path, "r") as include_file:
FileNotFoundError: [Errno 2] No such file or directory: '/home/homeassistant/.homeassistant/appdaemon/conf/compiled/html/default/test_head.html'
2018-03-26 19:51:06.211467 WARNING ------------------------------------------------------------
2018-03-26 19:51:06.211857 INFO function [get_dashboard] finished in 567 ms
screenshow below:
same exact error I start receiving when I first upgraded appdaemon to 3.0.0b5
I have exactly the same problem, after upgraded to version 3. I have AppDaemon running in a different ENV of hass. I’m using HASSBIAN. My symptoms are exactly the same as the @angelo
thanks
i dont know much about users in linux and about venv in general.
but i know that
/home/homeassistant/.homeassistant
is the directory that is the home directory from the homeassistant user.
and now you have a user appdaemon that wants to use subdirs inside that.
and you have a programm (appdaemon) that is started as user B and wants to write inside the homedir from user A and it complains about that it cant.
for me it still sais that somehow the rights in the configuration directory from appdaemon are not how they need to be.
The reason is because I’d like to back them up under the same git repo. However appdaemon has its venv and only the configuration files, which are owned and readable/writeable by the appdaemon user, located in the homeassistant directory. I wouldn’t think that is a problem, but I see your point.
See below the logs of my test with the configuration files located in the appdaemon home directory.
service status:
● [email protected] - AppDaemon
Loaded: loaded (/etc/systemd/system/[email protected]; disabled; vendor preset: enabled)
Active: active (running) since Tue 2018-03-27 16:22:43 PDT; 4s ago
Main PID: 684 (appdaemon)
CGroup: /system.slice/system-appdaemon.slice/[email protected]
└─684 /srv/appdaemon/bin/python3 /srv/appdaemon/bin/appdaemon -c /home/appdaemon/appdaemon/conf
Mar 27 16:22:43 hass49 systemd[1]: Started AppDaemon.
logs:
$ cat logs/appdaemon.log
2018-03-27 16:22:47.072481 INFO AppDaemon Version 3.0.0 starting
2018-03-27 16:22:47.073202 INFO Configuration read from: /home/appdaemon/appdaemon/conf/appdaemon.yaml
2018-03-27 16:22:47.075160 INFO AppDaemon: Starting Apps
2018-03-27 16:22:47.080893 INFO AppDaemon: Loading Plugin HASS using class HassPlugin from module hassplugin
2018-03-27 16:22:47.144159 INFO AppDaemon: HASS: HASS Plugin Initializing
2018-03-27 16:22:47.145163 INFO AppDaemon: HASS: HASS Plugin initialization complete
2018-03-27 16:22:47.146218 INFO Starting Dashboards
2018-03-27 16:22:47.161448 INFO API is disabled
2018-03-27 16:22:47.180892 INFO AppDaemon: HASS: Connected to Home Assistant 0.65.6
2018-03-27 16:22:47.282974 INFO AppDaemon: Got initial state from namespace default
2018-03-27 16:22:49.442461 INFO AppDaemon: Adding /home/appdaemon/appdaemon/apps to module import path
2018-03-27 16:22:49.443937 INFO AppDaemon: App initialization complete
and
$ cat logs/access.log
2018-03-27 16:23:21.755966 INFO Compiling dashboard 'test'
2018-03-27 16:23:22.352716 WARNING Dashboard 'test' not found
2018-03-27 16:23:22.353564 WARNING ------------------------------------------------------------
2018-03-27 16:23:22.353973 WARNING Unexpected error during DASH creation
2018-03-27 16:23:22.354306 WARNING ------------------------------------------------------------
2018-03-27 16:23:22.361816 WARNING Traceback (most recent call last):
File "/srv/appdaemon/lib/python3.5/site-packages/appdaemon/dashboard.py", line 822, in get_dashboard
with open(include_path, "r") as include_file:
FileNotFoundError: [Errno 2] No such file or directory: '/home/appdaemon/appdaemon/conf/compiled/html/default/test_head.html'
2018-03-27 16:23:22.362413 WARNING ------------------------------------------------------------
2018-03-27 16:23:22.362798 INFO function [get_dashboard] finished in 645 ms
permissions and directory structure:
$ ls -la /home/appdaemon/appdaemon/
total 24
drwxr-xr-x 6 appdaemon appdaemon 4096 Mar 27 16:13 .
drwxr-xr-x 4 appdaemon appdaemon 4096 Mar 27 16:19 ..
drwxr-xr-x 2 appdaemon appdaemon 4096 Mar 27 16:13 apps
drwxr-xr-x 3 appdaemon appdaemon 4096 Mar 27 16:19 conf
drwxr-xr-x 2 appdaemon appdaemon 4096 Mar 27 16:13 dashboards
drwxr-xr-x 2 appdaemon appdaemon 4096 Mar 27 16:22 logs
$ ls -la /home/appdaemon/appdaemon/conf/compiled/
total 16
drwxr-xr-x 4 appdaemon appdaemon 4096 Mar 27 16:17 .
drwxr-xr-x 3 appdaemon appdaemon 4096 Mar 27 16:19 ..
drwxr-xr-x 2 appdaemon appdaemon 4096 Mar 27 16:17 css
drwxr-xr-x 2 appdaemon appdaemon 4096 Mar 27 16:17 javascript
As you can see same exact result.
we had a bug a while ago that needed to create the compiled structure yourselve.
so please create the directory:
/home/appdaemon/appdaemon/conf/compiled/html
with the same rights and try again.
I had a similar issue also and found that it was because of a particular widget in the .dash file. Try doing a process of elimination and see if you can pin point the exact widget by deleting them from your dash and layout and go from there.
@angelo try removing the clock widget in your test.dash and just add the standard clock.clock to your layout and see what happens.
I had this same issue in that i had to re create the directories manually. Once i created them all worked fine.
the clock he uses in his test dashboard is the standard clock
Lol i know i know but as i mentioned earlier, for some reason i had issues with listing a widget and then referring to it in the layout file but when i just referred directly to the entity in the layout it seemed to work. Something else entirely but just a suggestion.
Done. Same exact errors/behavior.
$ ls -la /home/appdaemon/appdaemon/conf/compiled/html/
total 8
drwxr-xr-x 2 appdaemon appdaemon 4096 Mar 27 16:56 .
drwxr-xr-x 5 appdaemon appdaemon 4096 Mar 27 16:56 ..I dont know much about venv but i can see you have an appdaemon folder within the appdaemon folder. Would this be causing an issue?
I had this issue on v3. I downgraded back to v2