Ok I now have my Dashboards generating again after re-creating the structure of the compiled folder.
But I am back to my original errors of the Java Console displaying.
[Error] Failed to load resource: the server responded with a status of 404 (Not Found) (state, line 0)
[Error] Failed to load resource: the server responded with a status of 404 (Not Found) (materialdesignicons.min.css.map, line 0)
[Error] Failed to load resource: the server responded with a status of 404 (Not Found) (jquery.gridster.css.map, line 0)
i guess you have changed some parts or reinstalled? (or else your dir structure couldnt be gone)
whats your version from AD?
how does your appdaemon.yaml look?
how does your apps.yaml look?
did you restart appdaemon completely?
what was in the logs after restart?
I have really only dipped my toe in app functionality and currently have nothing enabled. Using only for HADashboard I have restarted the container and this just regenerates the same log.
2017-10-04 20:44:49.487082 WARNING ------------------------------------------------------------
stdout
19:44:49
2017-10-04 20:44:49.487154 WARNING Unexpected error in dashboard thread
stdout
19:44:49
2017-10-04 20:44:49.487204 WARNING ------------------------------------------------------------
stdout
19:44:49
2017-10-04 20:44:49.487733 WARNING Traceback (most recent call last):
stdout
19:44:49
File "/usr/local/lib/python3.6/site-packages/aiohttp/web_urldispatcher.py", line 401, in __init__
stdout
19:44:49
raise ValueError('Not a directory')
stdout
19:44:49
ValueError: Not a directory
stdout
19:44:49
stdout
19:44:49
The above exception was the direct cause of the following exception:
stdout
19:44:49
stdout
19:44:49
Traceback (most recent call last):
stdout
19:44:49
File "/usr/local/lib/python3.6/site-packages/appdaemon/rundash.py", line 318, in run_dash
stdout
19:44:49
setup_routes(conf.dashboard_obj)
stdout
19:44:49
File "/usr/local/lib/python3.6/site-packages/appdaemon/rundash.py", line 288, in setup_routes
stdout
19:44:49
app.router.add_static('/compiled_javascript', dashboard.compiled_javascript_dir)
stdout
19:44:49
File "/usr/local/lib/python3.6/site-packages/aiohttp/web_urldispatcher.py", line 845, in add_static
stdout
19:44:49
follow_symlinks=follow_symlinks)
stdout
19:44:49
File "/usr/local/lib/python3.6/site-packages/aiohttp/web_urldispatcher.py", line 404, in __init__
stdout
19:44:49
"No directory exists at '{}'".format(directory)) from error
stdout
19:44:49
ValueError: No directory exists at '/conf/compiled/javascript'
stdout
19:44:49
stdout
19:44:49
2017-10-04 20:44:49.487802 WARNING ------------------------------------------------------------
stdout
19:44:49
2017-10-04 20:44:49.487854 INFO API is disabled
stdout
19:44:49
2017-10-04 20:44:49.530295 INFO Connected to Home Assistant 0.54.0
Thanks again for the reply @ReneTode I have followed your steps…
A couple of things I should maybe point out when launching the container initially I have no permission to edit the appdaemon.yaml I must fist adjust permissions for my user account. All files in the dir are owned by Root…
I have added the extra logging options and re-created the compiled structure as I did before. I’m now back to the the Java Console throwing the below errors.
[Error] Failed to load resource: the server responded with a status of 404 (Not Found) (state, line 0)
[Error] Failed to load resource: the server responded with a status of 404 (Not Found) (materialdesignicons.min.css.map, line 0)
[Error] Failed to load resource: the server responded with a status of 404 (Not Found) (jquery.gridster.css.map, line 0)
Log now looks like this…
2017-10-05 08:37:06.714768 INFO AppDaemon Version 2.1.9 starting
2017-10-05 08:37:06.714955 INFO Configuration read from: /conf/appdaemon.yaml
2017-10-05 08:37:06.789400 INFO Starting Apps
2017-10-05 08:37:06.908667 INFO Got initial state
2017-10-05 08:37:06.909120 INFO Loading Module: /conf/apps/hello.py
2017-10-05 08:37:06.909553 INFO Loading Object hello_world using class HelloWorld from module hello
2017-10-05 08:37:06.944248 INFO hello_world: Hello from AppDaemon
2017-10-05 08:37:06.944843 INFO hello_world: You are now ready to run Apps!
2017-10-05 08:37:06.944929 INFO App initialization complete
2017-10-05 08:37:06.945089 INFO Starting dashboard
2017-10-05 08:37:06.947615 INFO API is disabled
2017-10-05 08:37:06.984414 INFO Connected to Home Assistant 0.54.0
2017-10-05 08:37:24.284757 INFO AppDaemon Version 2.1.9 starting
2017-10-05 08:37:24.284938 INFO Configuration read from: /conf/appdaemon.yaml
2017-10-05 08:37:24.355238 INFO Starting Apps
2017-10-05 08:37:24.453383 INFO Got initial state
2017-10-05 08:37:24.453835 INFO Loading Module: /conf/apps/hello.py
2017-10-05 08:37:24.454251 INFO Loading Object hello_world using class HelloWorld from module hello
2017-10-05 08:37:24.487869 INFO hello_world: Hello from AppDaemon
2017-10-05 08:37:24.488494 INFO hello_world: You are now ready to run Apps!
2017-10-05 08:37:24.488575 INFO App initialization complete
2017-10-05 08:37:24.488743 INFO Starting dashboard
2017-10-05 08:37:24.491261 INFO API is disabled
2017-10-05 08:37:24.541878 INFO Connected to Home Assistant 0.54.0
2017-10-05 08:37:36.094094 INFO New dashboard connected: Family Room
2017-10-05 08:37:36.561697 INFO New dashboard connected: Family Room
2017-10-05 08:37:46.861448 INFO New dashboard connected: Master Bedroom
2017-10-05 08:38:08.202987 INFO New dashboard connected: Family Room
2017-10-05 08:38:20.134013 INFO function [get_dashboard] finished in 95 ms
2017-10-05 08:38:20.143362 INFO Dashboard disconnected
2017-10-05 08:38:22.454473 INFO New dashboard connected: Master Bedroom
2017-10-05 08:38:22.584680 INFO function [get_dashboard] finished in 13 ms
2017-10-05 08:38:22.597285 INFO Dashboard disconnected
2017-10-05 08:38:24.671297 INFO New dashboard connected: Master Bedroom
seems like that the dashboard is running correctly.
how does the screen you get look in the browser?
how do you call the dashboard in the browser?
do you have passwords set?
seems like you still have fileright problems. but i have no experience in docker at all
Error getting state, check Java Console for details
I call either direct or select from the main HADashboard menu. No passwords I have stripped this install right back to nothing.
Once I click OK on the pop up 5+ times it will go away but ill have icons missing and lack of functionality state updates etc presumably due to the CSS maps not loading.
what is in the compiled dirs after you tried loading the dashboard?
are the rights for those dirs set correctly?
try creating a dashboard with just one switch and look what error that gives.
Everything in them is owned by root. Which seems to be the norm no matter what I do…
Just loaded up a one switch board as you suggested. The JavaConsole reports the below errors…
[Error] Failed to load resource: the server responded with a status of 404 (Not Found) (materialdesignicons.min.css.map, line 0)
[Error] Failed to load resource: the server responded with a status of 404 (Not Found) (jquery.gridster.css.map, line 0)
[Error] WebSocket connection to 'ws://IP:5050/stream' failed: Unexpected response code: 400 (x6)
that can only be right if you run appdaemon as root (which seems unlikely to me)
you need to set the filerights from the directory compiled so that Appdaemon has reading/writing access for all files, subdirs and everything that gets created in there.
My Synology box forces running as sudo through ssh. With that in mind I just cleared the config folder started the container manually through the docker gui and everything built is once again owned by root.
As a test I just gave the whole config dir full r/w permissions to everyone. Restarted and loaded up a dashboard and still the same errors.
[Error] Failed to load resource: the server responded with a status of 404 (Not Found) (jquery.gridster.css.map, line 0)
[Error] Failed to load resource: the server responded with a status of 404 (Not Found) (materialdesignicons.min.css.map, line 0)
[Error] Failed to load resource: the server responded with a status of 404 (Not Found) (state, line 0)
[Error] WebSocket connection to 'ws://IP:5050/stream' failed: Unexpected response code: 400 (x5)
Error log still empty. Just re-built the config structure by hand and tried launching the container without -e credentials in the docker run command. Still the same outcome.