0.107: Multiple Lovelace Dashboards, adds helpers, new media player card

[BennyB44]

Nevermind, after playing with 107 and the new dashboards i have found that you can add a new one and leave it as auto generated while editing the original.

[nickrout]

I know you are new here, so I will politely point to this:

How to help us help you - or How to ask a good question

Before we begin… This forum is not a helpdesk The people here don’t work for Home Assistant, that’s an open source project. We are volunteering our free time to help others. Not all topics may get an answer, never mind one that helps you solve your problem. [image] This also isn’t a general home automation forum, this is a forum for Home Assistant and things related to it. Any question about Home Assistant, and about using things with Home Assistant, is welcome here. We can’t help you with e…

[jasebob]

With the changes to resources and lovelace dashboard the only way I can get things working is to add a lovelace section to configuration.yaml and also use the dashboard.
For example, I have this in my configuration.yaml

lovelace:
  resources:
    - url: /local/mini-media-player-bundle.js
      type: module

And then a matching resource in the dashboard

Without either one and you have no card and the red box.

[doktordoc (Sasa)]

help help
how to get out of kiosk mode

[miljume]

Did you find the solution for “Custom element doesn’t exist: hui-entity-filter-card.”?
I have the exact same issue after upgrading to 107.7

[Piggyback (René)]

See here :

Lovelace Card Preloader

In preparation for Home Assistant 0.107, I have created the Lovelace Card Preloader: Add it to your Lovelace resources: resources: - type: js url: /local/path/lovelace-card-preloader.js and then add something like this to your Lovelace config: preload: - markdown - gauge This will preload those cards on reload of the page. This is useful in the following cases: Custom cards which have not been updated for 0.107 Using the standard cards as rows within an entities card by using…

[bartwarot (Bart)]

uh oh, take it easy happy easter!

[macfox]

Not to distract from the improvement to add input entities via the GUI, but who comes up with the naming for new features?

Helpers is not very intuitive name for the already established Input entities. Maybe it’s a translation thing, but Helpers is vague and generic. Just call them what they are Input (controls).

[DavidFW1960 (David)]

@macfox

Helpers is not very intuitive name for the already established Input entities. Maybe it’s a translation thing, but Helpers is vague and generic. Just call them what they are Input (controls).

I agree. There must be a reason but helpers is a meaningless term to me at least…

[petro]

Manual tools? Helpers isn’t a great term

[tom_l]

Input entities - it’s what they are.

[selfisch (Timo)]

Hey, is there any thread or issue where you mentioned this?
I have the exact same issue and I am going mad because of this.

The only difference at my environment, I am only using Ubiquity stuff and it is only inconsistent with device tracking my mobile phone(OnePlus5T). My wifes phone(OnePlus3) and an old Nexus5 are device tracked fine. But if they leave the house after sundown, my house is shutting down… very onnoying!

And, at the unifi controller, my phone is up and running. Looks only like home-assistant is not getting the right state… why ever.

[finity]

there are way too many to list here but if you do a search with “@finity unifi” the top 10 or so pretty much all deal with me talking about the issues I’ve had with unifi.

But the good news (I think…) is the issue I submitted for the problem has been closed and the fix is merged so it should come out in the next release.

[Viking]

I was enthusiastically planning to get som “help”, but when I clicked the big red + , the “Add Helper” menu only offered “Text” (!) All the other options were greyed out (?) Why?

[SeanM]

@macfox

Not to distract from the improvement to add input entities via the GUI, but who comes up with the naming for new features?

Helpers is not very intuitive name for the already established Input entities. Maybe it’s a translation thing, but Helpers is vague and generic. Just call them what they are Input (controls).

“Input UI” was one of the original names discussed. But the plan is to add more things to that section over time. Ability to add template sensors via the UI is something being looked into for example.

So “Helpers” was decided as a better catch-all (or generic as you put it) name that is also simpler to understand for most. It will cover anything that helps you build automations, not just input controls.

@Viking

I was enthusiastically planning to get som “help”, but when I clicked the big red + , the “Add Helper” menu only offered “Text” (!) All the other options were greyed out (?) Why?

Make sure that you have either default_config: or the other input domains in your configuration.yaml file.

input_boolean:
input_datetime:
input_number:
input_select:
input_text:

If you already have those and it’s still not working, please open an issue on the frontend repo: Sign in to GitHub · GitHub

[Viking]

Thank you. Adding default_config: to configuration.yaml solved it.
But I wonder why this wasn’t in there already? (I cannot recall ever having removed it)

[SeanM]

Glad that worked for you. default_config: is a relatively new thing, it was added about a year ago. If you installed Home Assistant before then you wouldn’t have it in your configuration.yaml file.

[namadori]

@SeanM

Make sure that you have either default_config: or the other input domains in your configuration.yaml file.

input_boolean: input_datetime: input_number: input_select: input_text:

the need for the input domains should be in an error message in the helpers page, I was struggling for 30 minutes before finding this message.

[radinsky]

have you fixed the divider?

[samnewman86]

How do you set initial values for input selects using the helpers gui?