Is there a Hello.dash file in your /appdaemon_dashboard/appdaemon/conf/dashboards/ directory? If so, what are the contents?
Yes sir. Here it is:
#
# Main arguments, all optional
#
title: Hello Panel
widget_dimensions: [120, 120]
widget_margins: [5, 5]
columns: 8
label:
widget_type: label
text: Hello World
layout:
- label(2x2)I ask because I ran into this same issue during the testing of the newest release with @aimc and my Hello.dash was kinda screwy, but yours is correct.
Iām going to assume at this point that you are trying to load Hello.dash with the default style, so it rules out any custom CSS being at fault.
Can you take a look in the /appdaemon_dashboard/appdaemon/conf/compiled/html/default directory and tell me if you see the files hello_body.html and hello_head.html? Can you load any of the other dashboards that come as example files?
Iām going to assume at this point that you are trying to load Hello.dash with the default style
Correct.
Can you take a look in the /appdaemon_dashboard/appdaemon/conf/compiled/html/default directory and tell me if you see the files hello_body.html and hello_head.html?
I donāt have a ācompiledā directory. This is whatās in my conf dir. Searching for those files turns up nothing, also ā I tried that even before my first post about this problem.
pi@hassbian:~/appdaemon_dashboard/appdaemon/conf $ ls -al
total 44
drwxr-xr-x 6 pi pi 4096 Jun 2 17:31 .
drwxr-xr-x 7 pi pi 4096 Jun 1 18:05 ..
-rwxr-xr-x 1 pi pi 339 Jun 3 08:57 appdaemon.cfg
-rwxr-xr-x 1 pi pi 188 Jun 1 18:05 appdaemon.cfg.example
drwxr-xr-x 2 pi pi 4096 Jun 1 18:05 apps
drwxr-xr-x 2 pi pi 4096 Jun 1 18:05 dashboards
drwxr-xr-x 3 pi pi 4096 Jun 1 18:05 example_apps
drwxr-xr-x 4 pi pi 4096 Jun 1 18:05 example_dashboards
-rwxr-xr-x 1 pi pi 6563 Jun 1 18:05 examples.cfg
-rw-r--r-- 1 pi pi 5 Jun 1 18:05 .gitignore
I followed all the steps to build that @quadportnick posted here. I see some people use ādocker run ā¦ā but I canāt because (I suppose) I did ādocker start ā¦ā ā if thatās even relevant.
I donāt know if this has anything to do with it, but when I first started with this a couple days ago it kept failing on this line in Dockerfile:
RUN mkdir -p /usr/src/app
I had to sudo mkdir the src and app dirs for it to continue, but even now that directory (/usr/src/app) seems to always be empty when I check.
Unfortunately, I have no experience with Docker but there are others who follow this thread that do. I am concerned that you donāt have a compiled directory though; I canāt imagine that Docker would be so different that it would put it in another place.
1 Like
I updated to the new HASS and updated the zwave fan component. How will this effect HADashboard?
Tried reinstalling hadashboard but still same error -
Traceback (most recent call last):
File "/usr/lib/python3.4/runpy.py", line 170, in _run_module_as_main
"__main__", mod_spec)
File "/usr/lib/python3.4/runpy.py", line 85, in _run_code
exec(code, run_globals)
File "/home/pi/appdaemon_dashboard/appdaemon/appdaemon/appdaemon.py", line 27, in <module>
import appdaemon.appdash as appdash
File "/home/pi/appdaemon_dashboard/appdaemon/appdaemon/appdash.py", line 2, in <module>
from aiohttp import web
File "/usr/local/lib/python3.4/dist-packages/aiohttp/__init__.py", line 6, in <module>
from .client import * # noqa
TypeError: source code string cannot contain null bytes
Any ideas
Should have no effect
Not sure - Iām currently on vacation, Iāll have a look when I get back. There may be a version mismatch with AIOHTTP or you may have some corrupted files.
First work, now vacation. We see where we rank in your priorities. LOL Have fun
3 Likes
First wife, then work, then vacation. We are at #4, as it should be. Happy dev, tight code.
4 Likes
When I replace the light prefix with the fan prefix in HASS I get the dashboard error.
I got it working . Uninstalled aiohttp and jinja and installed again. Everything working now 
1 Like
I can try and guess, but a look at the actual error might be quicker 
Also, Iād like to see how you are defining the dashboard.
Were is the default error log located?
Here is the layout that I have for my main dashboard.
layout:
- clock(2x1), weather(2x2), gameroom_temperature(1x1), gameroom_humidity(1x1), joel_presence(1x1), aimee_presence(1x1)
- scene.manual_morning_time, scene.manual_night_time, master_temperature(1x1), master_humidity(1x1), garage(2x1)
- light.livingroom,light.mantle2, light.mantle3, light.kitchen,light.gameroom, light.ge_12730_fan_control_switch_level_23_0,light.linear_wd500z1_wall_dimmer_switch_level_20_0, decorative_lights(1x1)
- climate.hallway_whats_up_fishes, light.ge_12730_fan_control_switch_level_11_0(1x1),garage_light(1x1)
- camera_dash, aimee_workout, joel_workout, reload
This is the error message I get when i change the light to fan.
look in your appdaemon.cfg file. That should specify it.
The only thing i am seeing is
logfile = STDOUT
errorfile = STDERR
Did you define a separate entity for the light you turned into a fan rather than just relying on the layout? Since there is no fan widget yet you will need to do so, probably using the switch widget.
then if you are running appdaemon in the backgorund, your files are not being captured. To capture the log you need to specify a full directory and fill name where you want the log files stored. I just put them in the appdaemon application directory in my install. It makes them easy to find.