Hi everyone,
from 107.x version minut point integrations doesn’t work anymore.
All sensors are in unavailable mode.
Please consider a fix for that.
Thank you so much.
Regards,
Alessandro
Haven’t gone through the 225 messages above, apologies if it’s already been posted.
I have an issue/gripe with the new lovelace. Having to move resources to configuration.yaml is annoying, but I can live with it.
The major issue though is when trying to create/manage dashboards. Having that data in configuration.yaml means I have to restart HA to see the changes.
(Yeah I know I could do it from the UI, but I’m trying to use yaml mode)
I’m also forced to place my main lovelace dashboard file in the (already crowded) root directory else it’s not recognised (the / are just deleted and I end up with a file that obviously does not exist)
I also have questions about the new dashboard functionality. I haven’t updated yet.
I use yaml mode and have my lovelace config in the ui-lovelace.yaml in the config directory.
I understand that I will need to move the resources from ui-lovelace.yaml into the configuration.yaml under the “lovelace:” section.
But just to clarify, after that I shouldn’t need to do anything else to keep my lovelace config exactly the same as it is now? It will still continue to use the ui-lovelace.yaml file without needing to reference that default file anywhere, correct?
And then if I want to add another dashboard I can then add an entry to the configuration.yaml in the “lovelace:” section pointing to the newly added dashboard configuration filename? So I would then end up with two dashboards but only one of them needs to be referenced in the config? The default ui-lovelace.yaml will still work even then without it being referenced anywhere else?
Inspired by the new dashboard examples, i was actually wondering what would be a good setup for the examples as shown, mote specifically the
“generated.yaml” - an auto generated dashboard
"Tools"what would one display there?
Just looking fro some general inspiration
I think if you read above it is clear what is needed.
My configuration.yaml
lovelace:
mode: yaml
resources: !include lovelace/resources.yaml
I had my resources in a yaml file prior to the update so moving for me was very easy. You can also just leave them in the configuration.yaml file.
The dashboard is easily added from configuration, lovelace dashboards. You can have yaml or ui type. Since I have yaml already setup I setup two UI type. One that I don’t touch and it keeps adding devices to and the second where I take control so I can understand and learn the new HA.
1 Like
Maybe you should read above. All you need to most of the time is refresh the browser. I make changes all the time to my different lovelace views. I save the file and then refresh and the changes show up.
Read the 2nd post (way back up there) and the reply from Frenk. There’s a service to reload it.
1 Like
The dht sensor is not new.
There was a small change to the code 22 days ago, but nothing that should cause what you see.
Has the dependency Adafruit-DHT been successfully loaded? Check your log
grep -i adafruit home-assistant.log
I read the whole thread before I posted above and yet here I am…
The biggest question I had that I don’t think has been answered is if I need to specify my current ui-lovelace.yaml configuration file in the lovelace: section of configuration.yaml or if it will be picked up automatically as the default? And will it still be that way if I subsequently add other dashboards?
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.
No it doesn’t. I read it before I came here to ask my question two posts ago.
It doesn’t answer the question I am asking.
You aren’t answering the question I am asking.
Can anybody answer the question I’m asking?
If you are not getting the answer, back up and try it.
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.
Hello all,
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.
1 Like
Great job on the new features!
1 Like
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. 
For all those not able to show custom dashboard views in homeassistant cast yet, it is because the following 2 PRs are not released yet:
Everytime I restart, it looses deConz integration, have to delete and re-add.
My deconz key is on a separate pi3
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.