Announcement: HADashboard v2 Beta3!

sseclient==0.0.18

oke, its not really my area of expertise, so i asked for the wrong thing :wink:
there were quite a few connection problems in this thread (and in the beta2 thread)
i suggest you start reading this thread from the top and see if there is 1 thing that complies to you too.
untill now all connectionproblems were solved. so unless you have a problem that is new, the answer should be there.

but please feel free to ask again if you still cant find it. even i cant provide the solution, someone else will :wink:

1 Like

well so I read through the whole long thread. but the only real thing I could find was to downgrade aiohttp. Which I did but still the same problem. I’m also wondering why it takes so long to start up… couple of minutes on an RPI2.

And CPU utilisation remains low during those minutes so I suppose there is some kind of time-out happening.

However I’m making progress:

I enabled debug logging and get the following:

tail -f log.log

    os.makedirs(conf.compile_dir)
  File "/usr/lib/python3.4/os.py", line 227, in makedirs
    makedirs(head, mode, exist_ok)
  File "/usr/lib/python3.4/os.py", line 237, in makedirs
    mkdir(name, mode)
PermissionError: [Errno 13] Permission denied: 'conf'

2017-05-08 14:17:53.520603 WARNING ------------------------------------------------------------

Although the configuration directory is writable. So I appdaemon is actually trying to write somewhere else

No I included the full path to the configuration directory and what I get is:

2017-05-08 12:26:13.836786 INFO AppDaemon Version 2.0.0beta3.5 starting
2017-05-08 12:26:13.837935 INFO Apps are disabled
2017-05-08 14:30:34.767969 INFO Got initial state
2017-05-08 14:30:34.769955 INFO Starting dashboard
2017-05-08 14:30:34.799456 WARNING ------------------------------------------------------------
2017-05-08 14:30:34.801140 WARNING Unexpected error in dashboard thread
2017-05-08 14:30:34.802690 WARNING ------------------------------------------------------------
2017-05-08 14:30:34.812880 WARNING Traceback (most recent call last):
  File "/home/homeassistant/appdeamon_dashboard/appdaemon/appdaemon/appdash.py", line 254, in run_dash
    srv = loop.run_until_complete(f)
  File "/usr/lib/python3.4/asyncio/base_events.py", line 271, in run_until_complete
    self.run_forever()
  File "/usr/lib/python3.4/asyncio/base_events.py", line 244, in run_forever
    self._run_once()
  File "/usr/lib/python3.4/asyncio/base_events.py", line 1049, in _run_once
    event_list = self._selector.select(timeout)
  File "/usr/lib/python3.4/selectors.py", line 424, in select
    fd_event_list = self._epoll.poll(timeout, max_ev)
OSError: [Errno 9] Bad file descriptor

2017-05-08 14:30:34.814339 WARNING ------------------------------------------------------------

right, appdaemon tries to write the compiled files there.
so the downwards settings for the conf dir need to be writable for the appdaemon user.

yeah I figured. So now the mkdir problem is solved but and it seems appdaemon can write the compiled versions. But now it terminates with the above log.
appdaemon seems to be creating css and javascript in the compiled directory but those are empty. so I suppose the compilation might be failing?

at least you got a decent error now :wink:
to bad it is not an error i have seen before :wink:

i guess AD is trying to compile and that error makes it stop.
what did you change that it isnt retrying to connect?
or is this an reoccuring error?

It’s not reoccurring.

I called AD with the full config dir like so:

python3 -m appdaemon.appdaemon -d -c /home/homeassistant/appdaemon_dashboard/appdaemon/conf/

before I just used -c ./conf

now that you have set the right permissions try

python3 -m appdaemon.appdaemon -c conf
when you are in the dir
/home/homeassistant/appdaemon_dashboard/appdaemon

well the permissions were always right. I suppose however that the wrong directory was somehow tried writing to.

When I call AD like you suggested (python3 -m appdaemon.appdaemon -c conf I get the permission error again:

2017-05-08 14:56:16.839304 INFO Starting dashboard
2017-05-08 14:56:16.847888 WARNING ------------------------------------------------------------
2017-05-08 14:56:16.848819 WARNING Unexpected error in dashboard thread
2017-05-08 14:56:16.850448 WARNING ------------------------------------------------------------
2017-05-08 14:56:16.856071 WARNING Traceback (most recent call last):
  File "/home/homeassistant/appdeamon_dashboard/appdaemon/appdaemon/appdash.py", line 249, in run_dash
    set_paths()
  File "/home/homeassistant/appdeamon_dashboard/appdaemon/appdaemon/appdash.py", line 22, in set_paths
    os.makedirs(conf.compile_dir)
  File "/usr/lib/python3.4/os.py", line 227, in makedirs
    makedirs(head, mode, exist_ok)
  File "/usr/lib/python3.4/os.py", line 237, in makedirs
    mkdir(name, mode)
PermissionError: [Errno 13] Permission denied: 'conf'

2017-05-08 14:56:16.857187 WARNING ------------------------------------------------------------

permissions:

drwxr-xrwx 7 homeassistant homeassistant  4096 Apr 16 17:28 conf

and

homeassistant@automator:~/appdeamon_dashboard/appdaemon/conf $ ls -l
total 36
-rwxr-xr-x 1 homeassistant homeassistant  433 May  8 12:55 appdaemon.cfg
-rwxr-xr-x 1 homeassistant homeassistant  188 Apr 16 16:34 appdaemon.cfg.example
drwxr-xr-x 3 homeassistant homeassistant 4096 Apr 16 16:59 apps
drwxr-xr-x 4 homeassistant homeassistant 4096 May  8 12:11 compiled
drwxr-xr-x 2 homeassistant homeassistant 4096 May  8 09:38 dashboards
drwxr-xr-x 3 homeassistant homeassistant 4096 Apr 16 16:34 example_apps
drwxr-xr-x 4 homeassistant homeassistant 4096 Apr 16 16:34 example_dashboards
-rwxr-xr-x 1 homeassistant homeassistant 6563 Apr 16 16:34 examples.cfg

permissions seem oke.
you could try to run it with sudo, to see if it runs then.

i did some reading.
i use just -c conf but in the instructions andrew says pathtoconf
i looked back what you used and it could be the / at the end.

so you could also try:

python3 -m appdaemon.appdaemon -c /home/homeassistant/appdaemon_dashboard/appdaemon/conf

Thanks a lot for all the help. But That does not change things. I have to stop for today. Will try more tomorrow…

1 Like

All anyone has to do is give you a challenge and you find a way!

1 Like

can you verify which user is being used when you try to start AppDaemon? There were a couple of things up there that made me wonder.

I’ve been looking around and read the .md file but still couldn’t find any info about Climate control widget… Any idea how?

Thank you.

climate

A widget to monitor and contol a climate entity

Mandatory Arguments

  • entity - the entity_id of the climate entity

Optional Arguments:

  • title - the title displayed on the tile
  • title2 - a second line of title text
  • step - the size of step in temperature when fading the slider up or down
  • units - the unit symbol to be displayed

Cosmetic Arguments

  • widget_style
  • icon_up
  • icon_down
  • title_style
  • title2_style
  • text_style
  • level_style
  • level_up_style
  • level_down_style
1 Like

I was just about to paste that in!!

(BTW, you may want to edit the reference to ‘brightness’ in the docs.)

2 Likes

Nonsense! Everyone knows that brightness is a synonym for temperature!

4 Likes

Gosh it’s dim in here; I’m practically freezing!

2 Likes