I do not. My lovelace.yaml file is located in my config directory. It is called ui-lovelace.yaml.
https://www.home-assistant.io/lovelace/yaml-mode/
This give directions on it.
My lovelace file which I used Frenck’s github public post just loads other stuff.
---
# This is actually just a bootstrap for my Lovelace configuration.
# It loads all resources for Lovelace dynamically from subfolders- since changed in .107
# inside the `lovelace/resources` directory.
#
# Views are actually include one by one, this to guarantee the order of
# the tabs of the view in the UI.
#
title: Home Control Panel
# from .107 move to configuration.yaml
#resources: !include lovelace/resources.yaml
custom_header: !include lovelace/cards/custom_header.yaml
views:
- !include lovelace/views/main.yaml
- !include lovelace/views/system_info.yaml
- !include lovelace/views/test.yaml
- !include lovelace/views/auto.yaml
- !include lovelace/views/media.yaml
This doesn’t seem to work if you have your main Lovelace config in storage mode but add YAML mode dashboards in configuration.yaml like this:
lovelace:
mode: storage
dashboards:
...
New YAML mode dashboards don’t appear until HA is restarted and the reload service isn’t present, presumably because this is only created if the main Lovelace config is in YAML mode.
Maybe I am not understanding your question. I thought you wanted to know if you need to specify my current ui.lovelace.yaml in the configuration.yaml file? If this is the question, you do not per the document
Restart Home Assistant for the mode to be changed. Create a new file <config>/ui-lovelace.yaml and add your Lovelace configuration. A good way to start this file is to copy and paste the “Raw configuration” from the UI so your manual configuration starts the same as your existing UI.
There is no mention of the configuration.yaml file. The change and the confusion for most had to due with the resources. This was moved to the configuration.yaml file from the ui.lovelace.yaml file.
Adding new dashboards did not change my default ui.lovelace.yaml file. The two files were created in the .storage directory This still loads as before and the two new ones I added load also.
If this is not your question ask again.
After updating to 107.4 my shopping list seem broken. The error:
2020-03-21 18:26:24 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection.140231263132304] Received invalid command: shopping_list/items
2020-03-21 18:35:23 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection.140231263132304] Received invalid command: shopping_list/items
2020-03-21 18:36:00 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection.140231263132304] Received invalid command: shopping_list/items/add
2020-03-21 18:36:00 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection.140231263132304] Received invalid command: shopping_list/items
2020-03-21 18:36:09 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection.140231263132304] Received invalid command: shopping_list/items/add
2020-03-21 18:36:09 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection.140231263132304] Received invalid command: shopping_list/items
I see the data file (.shopping_list.json) in HA’s config directory, It still has all my data in it. It’s just not showing the data and I can not add/recreate a list.
Anybody else seeing this with the shopping list after the update? Or anybody know whats the fix is?
Edit: Had to reconfigure it via the integrator page for some reason.
Yes, I think that is finally the answer I was looking for.
But TBH, it didn’t say anything in the document about it and the line you quoted didn’t have to do with that question but instead creating the ui-lovelace.yaml file out of an existing UI raw file.
But thanks for the info anyway.
I’ll try it and if it doesn’t work as expected then I’ll be back again.
I was never able to get the built in cast to work properly so I’ve been using a script to trigger a CATT shell command automatically after each reboot to cast my cameras to a Google Hub. Still works great with the latest update.
Hi,
I’m not good at It. I’ve installed terminal on HA and when I use this commant I have
grep -i adafruit home-assistant.log
Where the file should be located?
EDIT:
Ok found it. It has only this:
humidity, temperature = self.adafruit_dht.read_retry(self.sensor, self.pin)
File "/usr/local/lib/python3.7/site-packages/Adafruit_DHT/common.py", line 94, in read_retry
File "/usr/local/lib/python3.7/site-packages/Adafruit_DHT/common.py", line 80, in read
File "/usr/local/lib/python3.7/site-packages/Adafruit_DHT/common.py", line 55, in get_platform
File "/usr/local/lib/python3.7/site-packages/Adafruit_DHT/Raspberry_Pi_2.py", line 22, in <module>
ImportError: cannot import name 'Raspberry_Pi_2_Driver' from 'Adafruit_DHT'
Can anything be done by this? Will it work on Pi Zero W?
HI,
Can anyone tell me what url should be in here:
Tried to type in the url of the new dashboard (yaml file) but there is “The url should contain a - and cannot contain spaces or special characters, except for _ and -” error.
I´m seeing an issue after the update från 0.106.6 to 0.107.4 which logs an error when I try to restart Home Assistant Core.
Invalid config for [automation]: must contain at least one of service, service_template. @ data[‘action’][0]. Got None. (See /config/configuration.yaml, line 336).
The line it refers to in configuration.yaml is just the line where I include my automations.yaml file, and that hasn´t changed since the earlier version.
Any ideas on what the issue might be? There are no changes in my automation file either.
still, just to be sure before I update, (making changes a Lovelace view isn’t the same as adding or removing a custom card from the resources):
moving the resources: !include lovelace/resources.yaml line to configuration.yaml doesnt mean we have to restart HA for a custom-card change? I ask because I can’t find any Lovelace reload service in the services on my test instance, which is now on 107.5…
update
bit the bullet, and all seems to have gone well…
this isn’t correct though:
my resources are loaded via the !include above. Anyone else see this in the Info?