Most of my input_booleans show up on the default view under the “Input Boolean” card.
I’ve got a few that don’t, no matter what order they are in configuration.yaml. They look the same to me, so I’m not sure why some show up and some don’t. Even if I specify these in a custom group, they don’t show up. Any ideas why?
For instance, all of these show up except test_button and lightning_safety_mode.
input_boolean:
basement_secure:
name: Basement Secure
initial: on
first_floor_secure:
name: First Floor Secure
initial: on
second_floor_secure:
name: Second Floor Secure
initial: on
dash_on_button:
name: Dash ON Button
initial: off
dash_glad_button:
name: Dash Glad Button
initial: off
dash_tide_button:
name: Dash Tide Button
initial: off
test_button:
name: Test Button
initial: off
lightning_safety_mode:
name: Lightning Safety Mode
initial: off
Is your Lovelace UI the default one or have you already started to modify it, either directly using the ‘Configure UI’ menu option or via the ui-lovelace.yaml file?
try going to the dev-tools states page and look at the attributes for the input_booleans that aren’t showing up and compare them to the ones that are to see if there’s any differences.
In that case they have not been added to lovelace so they are not displaying.
Check in the side panel, i icon…
See my lovelace mode is storage
What is your lovelace mode? I am going to take a wild stab and say it’e either storage or yaml. The only mode that will automatically show them all is auto generated.
Ok, this helped. I was in storage mode. I deleted .storage/lovelace and got back to auto mode. this didn’t populate the booleans on the default view, but at least on my custom views where I added them manually they are appearing now. Thanks!
I haven’t done anything intentionally to use lovelace at all - if I modified it I’m not sure how. I’ve always had custom groups via groups.yaml which predated lovelace. Not sure how it got out of auto mode into storage mode.