Question 1

What are the biggest Home Assistant 0.116 frontend changes?

Accepted Answer

The biggest change is the Entities card editor not breaking when you use special rows like dividers, section rows, buttons rows, and call-service rows. You can add those rows via YAML and then still edit them inside the UI editor without it throwing errors. On top of that, normal entity rows now have a dedicated UI editor for things like name, icon, and secondary info.

Question 2

Can you edit divider rows and section rows in the Entities card UI now?

Accepted Answer

Yes—once the row exists in the card, I can click into it and edit that row in YAML without the whole card editor breaking. We don’t have full visual editors for each special row yet, but the workflow is way smoother than before. You still have to add the special rows using the code editor for now.

Question 3

How do you show light brightness as secondary info in an Entities card?

Accepted Answer

In 0.116, I can edit a normal entity row and pick secondary information right in the UI. For a light entity, brightness shows up as an option, and it displays directly under the entity row. The available secondary info options depend on the entity domain, so you’ll see different choices for lights vs covers vs automations.

Question 4

Does the Entities card UI editor still work if I add a footer or other YAML options?

Accepted Answer

Yep, that’s one of the coolest parts: I can add things like a footer in the YAML code editor and the UI editor doesn’t break anymore. I can still edit the main parts of the card in the UI and only drop into YAML for the pieces that don’t have a visual editor yet. The goal is to keep expanding UI editing for headers/footers and more row types.

Question 5

How do you set the initial view on the Home Assistant Calendar card?

Accepted Answer

You can now set the Calendar card’s initial view in the card editor, like day view or list/agenda view. After I save it, the card will always open to that view when the dashboard loads. It’s a simple change, but it saves a ton of clicks if you never use month view.

Question 6

What changed in the Home Assistant Logbook in 0.116?

Accepted Answer

The Logbook UI now shows more information, and a lot of the message text is translatable, so it’ll display properly for non-English languages. The icon shown for an entry reflects the state at the time of the log entry, which is a really nice detail. And you get relative time (like “8 minutes ago”) so you don’t have to do mental math.

Question 7

What are custom view layouts in Home Assistant and why do they matter?

Accepted Answer

Custom view layouts let developers register new view types (currently via YAML) and control how cards are rendered and laid out—sizes, positioning, and even how edit mode is presented. Home Assistant will supply the cards and badges, and the view decides how to place them. This is a big foundation for things like drag & drop layouts and more advanced dashboard experiences.

Home Assistant 0.116 Frontend Changes

🛍️ Products Mentioned (1)

Like what I do? Sponsor me

About This Video

Frequently Asked Questions

🎬 More from Zack Barett