Issue getting icons to show

Third party integrations HADashboard
1

No success with either FA or MDI. Checked the log files and originally had a permissions error, but fixed that with chown.

morning:
    widget_type: script
    title: Wake Up
    entity: script.good_morning
    icon_on: fa-sun
    icon_off: fa-sun

goodnight:
    widget_type: script
    title: Good Night
    entity: script.good_night
    icon_on: fa-moon
    icon_off: fa-moon

sensor.elkm1_area_1_status:
    widget_type: sensor
    icon_on: mdi:alarm-check
    icon_off: mdi:alarm-off
    entity: sensor.elkm1_area_1_status

I’ve attached a screenshot of what it renders. Any help would be appreciated!

HA 0.72.1 , AppDaemon 3.0.1

hadashboard
hadashboard1518×502 32.6 KB

The one that just says “off” to the right of the Garage is supposed to be the elkm1_area_1_status.

2

I just took a quick look at my HADashbaords and any of them that I specify an icon, it’s mdi- not mdi:

3

Thanks, I had seen it both ways wasn’t sure which was correct. I just tried it with mdi- but same result. :frowning:

4

MDI and FA add new icons once in a while.
and only when appdaemon is also updating that, those new ones are available.

so there is a possibility that you are using an icon that isnt available.
the second thing that is causing trouble in a lot off cases is cashe.

if you got problems like that make sure that you:

  1. restart AD and in some cases even the device that is running it
  2. make sure you have the compile options set on (see docs)
  3. make sure that you use a browser that supports all
  4. make sure that the browser cashe is cleared.
5

Hmm… regarding compile, are you referring to dash_force_compile? I tried setting that but no change. I’ve tried clearing caches also no change. Rebooted HA, AppDaemon, and the entire box, consistent behavior. My font-awesome.css indicates I have v4.7.0, and most of the icons (fa-sun, fa-moon) were added in 3.2.

The one suspicious thing in the log file is this:

2018-07-08 12:37:14.642842 WARNING css: /home exists, but is not writeable, owner: root
2018-07-08 12:37:14.655355 WARNING javascript: /home exists, but is not writeable, owner: root
2018-07-08 12:44:21.532647 WARNING css: /home exists, but is not writeable, owner: root
2018-07-08 12:44:21.535211 WARNING javascript: /home exists, but is not writeable, owner: root

But should this matter? AppDaemon is running as user homeassistant, and while /home is owned by root, /home/homeassistant/ has the correct permissions and is where the conf folder is stored. I wouldn’t expect it to be writing directly to /home .

6

that are normal log entries.
AD checks the trees to make sure that we know if everything is right with permissions, when people ask questions.
did you set and check your accesfile in appdaemon.yaml?
did you set dash_force_compile to 1 (not true)?
did you try other icons?
what browser do you use? and how did you clear cashe?
do other changes take effect?

i also notice that you use icon_on and off for sensor widget. and sensor doesnt have icons.

do you have any other css in the dashboard or did you change anything in the skin?
wrong css on any place can lead to unwanted effects on other places, thats why i ask.

7

One interesting thing is that fa-female and fa-male are the only two that I’ve found to work. However, the icons that shows up don’t even match what is on Font Awesome’s website.

No clue where it is pulling them from.

EDIT: fa-fighter-jet also appears to work. So, it seems some icons can work, just not the ones I care about (i.e. fa-sun and fa-moon for Morning and Evening routines).

8

Aha, figured it out. I was getting the names of the icons from Font Awesome’s website. But upon checking the font-awesome.css file in my AppDaemon installation, fa-sun is actually fa-sun-o . Not sure what the -o means but I didn’t see that on the website.

9

fa did make extreme changes to its website recently.
i just looked up sun and i find 3 different icons for it.

before they had 1 class with icons, now it seems they have more classes.
things like -o were used for setting 2 icons with the same name apart.
without the -o it was filled up, with it was with more whitespace inside.

10

Makes sense, thanks!