Home Assistant service doesn't start when using weblink

Configuration
1

Hello everyone.

I noticed I could show web links in the frontend, so I decided to give it a try. Here is what I did after reading this:

configuration.yaml

weblink: !include includes/weblinks.yaml

weblinks.yaml

entities:
  - name: Vodafone Router
    url: link
    icon: mdi:router-wireless
  - name: HP Printer
    url: http://172.16.23.8
    icon: mdi:printer-settings
  - name: WD My Book Live
    url: http://172.16.23.10/UI
    icon: mdi:server-network
  - name: OpenMediaVault
    url: http://172.16.23.13
    icon: mdi:server-network
  - name: NAS Daily Backup Log
    url: http://172.16.23.13/web/logb.php
    icon: mdi:backup-restore             
  - name: FlashAir Backup Log
    url: http://172.16.23.13//web/log.php
    icon: mdi:backup-restore

Service log only shows (from command sudo systemctl status [email protected]):

[email protected] - Home Assistant for homeassistant
   Loaded: loaded (/etc/systemd/system/[email protected]; enabled)
   Active: active (running) since Sáb 2017-06-17 00:13:03 WEST; 22s ago
 Main PID: 10315 (hass)
   CGroup: /system.slice/system-home\x2dassistant.slice/[email protected]
           └─10315 /srv/homeassistant/bin/python3 /srv/homeassistant/bin/hass

Jun 17 00:13:03 hassbian systemd[1]: Started Home Assistant for homeassistant.
Jun 17 00:13:08 hassbian hass[10315]: Config directory: /home/homeassistant/.homeassistant

And of course frontend doesn’t run, as service doesn’t seem to behave as it should.

Running Hass 0.46.1, has anyone else a similar issue with weblink?

Thanks in advance.

2

Weblinks working fine here, and the snippet you posted from status just shows HA booting up correctly, with the service starting 22 seconds before you copy/pasted it.

If you add a new component it is entirely normal for startup to take longer than usual, and I don’t think mine starts in 22 seconds even without adding new components.

Maybe wait a bit longer, or if you have and there’s still no joy, what’s the error now?

3

After 6 minutes, it is exactly the same, nothing else is shown in status of the service and HASS doesn’t start.

If I go back and comment the weblink line in configuration.yaml, everything works properly again. 5 seconds after restarting the service, I can already see info messages from homeassistant.core, for instance.

Really strange, as no error message appears.

4

Hmm, love a good mystery :smile:

And just to confirm…

Your files are arranged like this:

.homeassistant/
          |
          |--configuration.yaml 
          |
          |--includes/
                     |
                     |--weblinks.yaml

And those are definitely the correct filenames, and you’re happy there’s no erroneous whitespace in weblinks.yaml?

5

Yep, structure is as you pictured and spacing also seems OK in weblinks.yaml.

6

… There’s an extra slash in the last url in the list (http://172.16.23.13//web/log.php) maybe that’s causing a parsing error?

7

Actually I found the error: file weblinks.yaml was owned/group pi instead of homeassistant.

After changing ownership and groups, Hass is back.

Thanks for your help anyway.

2 Likes