I get the following hass.io UI error:
while parsing a block collection in “/config/ui-lovelace.yaml”, line 28, column 7 expected <block end>, but found ‘<block sequence start>’ in “/config/ui-lovelace.yaml”, line 47, column 8
while parsing this Lovelace-ui.yaml file:
Sorry I’ve not put the yaml script in a code block, it seems my ssh client can’t copy from the nano editor. Also I can’t get my MacOS SSH to work on the command prompt (which I know I could copy from!).
I can’t read your code but entity on 47 seems to have an extra character?
You seem to have to entity filters. One for who’s home and one for what lights are on. The second one misses the type and should be an array entry.
- type: entity-filter
entities:
...
- type: entity-filter # This is missing
entities:
...Still getting same error after adding your suggestion.
Going on your suggestion, I also made sure:
-type: glance
and
entities:
were in each section that represents a glance card.
Post your yaml. Please don’t use images, copy and paste it into your post with proper formatting. Use the blue ribbon as a guide for that. There’s even a link that explains how to properly post code. Also, paste the full error, don’t regurgitate it with your own wording.
I understand the need to post proper code snippets, but did you even read my reason for posting images? Also, the error message is not regurgitated, I have quoted the compete error message!
I get you, but you made changes and didn’t post new yaml (and new error with potentially new line numbers). I did read your post, that still doesn’t change the fact that working with images is 1000x harder. People can’t copy and paste your code into a text editor to get line numbers, we have to guess. Some times these issues don’t stand out without having that information.
There are plenty of ways to access your PI’s configuration so that you can view the files to be able to copy/paste from them.
Well FYI I later managed to solve my SSH problems in my Mac’s console window, so it shouldn’t be an issue again 
Spelling error:
I did fix that.