Announcement: HADasboard beta4 - Release Candidate!

[Philippe_Demartin]

Some help to create skins
I’ve followed the indication present in the “variable.yaml”

#Custom styles instructions

1. Create a new directory under css
2. copy these files over
3. EDIT
4. Select the new dir as the “skin” argument of any
   dashboards you want to use it

Created a copy of one of the skins in the /home/pi/appdaemon_dashboard/appdaemon/appdaemon/assets/css/perso and edited the content, but I’ve got this error, when I try to load it at http://192.168.0.26:3040/Main?skin=perso

WARNING Skin ‘perso’ does not exist

What is wrong in my steps ?
Off course, I’ve reloaded appdeamon and also tried to add “dash_force_compile: 1” in the appdaemon.yaml
I’ve also tried to change the background from an existing skin, but it don’t affect the result on the dashboard

[ReneTode]

could be a rights problem.

but the best place to create a custom skin is here:

/home/pi/appdaemon_dashboard/appdaemon/appdaemon/conf/custom_css/yourskin

(thats also mentioned in the DASHBOARD.md if i am not mistaken)

the dir should contain 2 files:
dashboard.css
variables.yaml

you can copy them from 1 of the other skins and edit them.
changing the background is possible, but i cant tell you what has gone wrong in your case if you dont tell me how you tried it.
remember that your browser could also give you cashing problems. lots of times people try to edit skins and it only takes effect when they clear the cache from the browser.
another common problem it when the compliling has gone wrong after a user mistake and some compiled files dont get refrehed.

the dir
/home/pi/appdaemon_dashboard/appdaemon/appdaemon/conf/compiled
can be emptied at any time to make sure that the files really get recompiled.

[CBRHerms (Adam Shearman)]

Getting the same issue here with SSL with the latest version of the BETA. Wasn’t present in beta2 at least…

urllib3.exceptions.SSLError: hostname '192.168.0.43' doesn't match 'my.fqdn'

^ When using https://192.168.0.43:8123

2017-06-22 18:35:49.520454 WARNING Unable to connect to Home Assistant, retrying in 5 seconds
2017-06-22 18:35:49.521037 WARNING ------------------------------------------------------------
2017-06-22 18:35:49.521427 WARNING Unexpected error:
2017-06-22 18:35:49.521735 WARNING ------------------------------------------------------------
2017-06-22 18:35:49.530679 WARNING Traceback (most recent call last):
  File "/usr/local/lib/python3.4/dist-packages/urllib3/connection.py", line 141, in _new_conn
    (self.host, self.port), self.timeout, **extra_kw)
  File "/usr/local/lib/python3.4/dist-packages/urllib3/util/connection.py", line 83, in create_connection
    raise err
  File "/usr/local/lib/python3.4/dist-packages/urllib3/util/connection.py", line 73, in create_connection
    sock.connect(sa)
ConnectionRefusedError: [Errno 111] Connection refused

^ When using my external url which is portforwarded from 443 to 8123.
This show as the following without debug log level enabled:

2017-06-23 00:57:14.457418 WARNING Disconnected from Home Assistant, retrying in 5 seconds

Did anyone get to the bottom of it? I’d prefer keeping my url as it is but i’ve had to change the commtype to SSE to get it to work temporarily.

[noisufnoc (Mike)]

does this beta work behind a reverse proxy?

[anon35356645]

with ha_url: https://xxx.duckdns.org

pi@hassbian:~/appdaemon_dashboard/appdaemon $ python3 -m appdaemon.appdaemon -c                                         /home/pi/appdaemon_dashboard/appdaemon/conf --commtype SSE -D DEBUG
2017-06-23 07:36:19.611798 INFO AppDaemon Version 2.0.0beta4 starting
2017-06-23 07:36:19.612328 INFO Configuration read from: /home/pi/appdaemon_dash                                        board/appdaemon/conf/appdaemon.yaml
2017-06-23 07:36:19.612665 DEBUG get_ha_config()
2017-06-23 07:36:19.628677 WARNING Unable to connect to Home Assistant, retrying                                         in 5 seconds
2017-06-23 07:36:19.629142 WARNING ---------------------------------------------                                        ---------------
2017-06-23 07:36:19.629464 WARNING Unexpected error:
2017-06-23 07:36:19.629760 WARNING ---------------------------------------------                                        ---------------
2017-06-23 07:36:19.638757 WARNING Traceback (most recent call last):
  File "/usr/local/lib/python3.4/dist-packages/urllib3/connection.py", line 141,                                         in _new_conn
    (self.host, self.port), self.timeout, **extra_kw)
  File "/usr/local/lib/python3.4/dist-packages/urllib3/util/connection.py", line                                         83, in create_connection
    raise err
  File "/usr/local/lib/python3.4/dist-packages/urllib3/util/connection.py", line                                         73, in create_connection
    sock.connect(sa)
ConnectionRefusedError: [Errno 111] Connection refused

During

[anon35356645]

with ha_url: https://192.168.1.238:8123

That’s enough for me. I quit this project

pi@hassbian:~/appdaemon_dashboard/appdaemon $ python3 -m appdaemon.appdaemon -c /home/pi/appdaemon_dashboard/appdaemon/conf --commtype SSE -D DEBUG
2017-06-23 07:38:50.545111 INFO AppDaemon Version 2.0.0beta4 starting
2017-06-23 07:38:50.546009 INFO Configuration read from: /home/pi/appdaemon_dashboard/appdaemon/conf/appdaemon.yaml
2017-06-23 07:38:50.546583 DEBUG get_ha_config()
2017-06-23 07:38:50.660202 WARNING Unable to connect to Home Assistant, retrying in 5 seconds
2017-06-23 07:38:50.661041 WARNING ------------------------------------------------------------
2017-06-23 07:38:50.661609 WARNING Unexpected error:
2017-06-23 07:38:50.662154 WARNING ------------------------------------------------------------
2017-06-23 07:38:50.670986 WARNING Traceback (most recent call last):
  File "/usr/local/lib/python3.4/dist-packages/urllib3/connectionpool.py", line 600, in urlopen
    chunked=chunked)
  File "/usr/local/lib/python3.4/dist-packages/urllib3/connectionpool.py", line 345, in _make_request
    self._validate_conn(conn)
  File "/usr/local/lib/python3.4/dist-packages/urllib3/connectionpool.py", line 844, in _validate_conn
    conn.connect()
  File "/usr/local/lib/python3.4/dist-packages/urllib3/connection.py", line 346, in connect
    _match_hostname(cert, self.assert_hostname or hostname)
  File "/usr/local/lib/python3.4/dist-packages/urllib3/connection.py", line 356, in _match_hostname
    match_hostname(cert, asserted_hostname)
  File "/usr/local/lib/python3.4/dist-packages/urllib3/packages/ssl_match_hostname/_implementation.py", line 154, in match_hostname
    % (hostname, dnsnames[0]))
urllib3.packages.ssl_match_hostname._implementation.CertificateError: hostname '192.168.1.238' doesn't match xxx.duckdns.org'

During handlin

[anon35356645]

@CBRHerms

Did anyone get to the bottom of it? I’d prefer keeping my url as it is but i’ve had to change the commtype to SSE to get it to work temporarily.

Seems not …

[anon35356645]

@rpitera

I wonder if it has anything to do with the base_url: setting in the http: component.

I just commented it out and I’m restarting HA to see what effect it has.

and how did it go?

I have this in y configuration.yaml

base_url: https://xxx.duckdns.org

[ReneTode]

i think its time to call the big boss: @aimc heeeeeeelp

[rpitera (Robert Pitera)]

@ReneTode

to do a write up i have to delete it and install all over again.
and i am glad i have it up and running

That in itself speaks volumes. If NGINX was truly that easy to set up, you wouldn’t fear doing it.

[rpitera (Robert Pitera)]

Announcement: HADasboard beta4 - Release Candidate!

No change commenting out base_url:. Damn, thought I was on to something.

[azeroth12 (Ryan)]

Firstly thanks for all your hard work @aimc !

I’m trying to modify some widgets and it doesn’t seem like anything I do is getting picked up. To force the issue I completely deleted the entire widgets folder and everything kept working. Is there a bad reference somewhere? Is it possibly looking at a web based copy of the source? Or is there some super cache that I can’t get past?

I have the force compile flag on.

It’s weird, only changes that I make to the config.yaml get picked up. Everything else is ignored.

[lordsiris (Chris)]

Thanks for all the hard work on this. Just installed in docker (using image off dockerhub mezz64/appdaemon:dashdev). Took literally just a couple minutes to manually update to the .yaml config version. Finally turned off my old v1 and will just run this for both automations and dashboard!

Thanks!

[azeroth12 (Ryan)]

Figured it out. Not sure if this is my fault or by design, but apparently after moving to beta4 using the above instructions, appdaemon is now using /usr/local/lib/python3.6/site-packages/appdaemon/widgets instead of my local folder as it used to… I’d rather not have to dig so deep to tweak the widgets if possible. Haven’t found a way to point the app to a different directory yet…

[Philippe_Demartin]

Ok, Its working great
I made a skin for my tablet, pure css, no texture.
Clean and classy.
http://demartinenchile.com/media/blackglass.zip
It fit perfectly on a hd screen with a 6x4 grid and a widget_dimensions: [133, 123]
I load it with the WallPanel app at a zoom level off 150%

WallPanel for Android [Formerly HomeDash]

WallPanel is an browser app to display ‘dashboard’ type webpages such as HADashboard or HASS on a device, which may make good use of older tablets/devices you want to use for home automation dashboards. The difference between this and kiosk apps or pinning a web page is the app is providing remote control/home automation features (eg, you can remotely control the URL that’s being displayed, or get feedback on motion on the camera). P.S. An iOS version is in development with the same API This pr…

[Philippe_Demartin]

It’s fitting also great on my Plasma KDE5 desktop on a side screen, loaded in a webslice applet

[rpitera (Robert Pitera)]

@Philippe_Demartin

It’s fitting also great on my Plasma KDE5 desktop on a side screen, loaded in a webslice applet

Is it wrong to be aroused by a screen shot? Asking for a friend.

[ReneTode]

@rpitera

That in itself speaks volumes. If NGINX was truly that easy to set up, you wouldn’t fear doing it.

i dont say it was easy. (or difficult either) but anything that is working is very important.
i am not the only one to keep happy. lets say i start playing around for 2 hours and disturbing the lights or tv with that.
no problem if it brings an advantage afterwards, but if it is only to make others (to my wife unknown people) happy that breaks away a part of the WAL (wife acceptance level)

[aimc (Andrew Cockburn)]

I’m not supporting editing widgets yet for that very reason - when I add that in it will be via a local directory that overrides or adds to the built in widgets, the same way that custom skins do, I’m just not here yet.

[aimc (Andrew Cockburn)]

There are about 100 posts here - I have no idea what the original question was