Hi,
some guides (like Fritzbox call list) point to a “text-helper” but there is no text helper available. Just a text input helper, which is different. Is this gone in the current version ?
thx
Hi,
some guides (like Fritzbox call list) point to a “text-helper” but there is no text helper available. Just a text input helper, which is different. Is this gone in the current version ?
thx
There are two entity domains that create similar entities input_text
and text
. Generally speaking, input_text
entities are user-created, and text
entities are create by other integrations. The naming is a bit confusing, but an input_text
entity is what is created when you select “Text” as the Helper type.
The picture you have posted is the Text Helper creator, which will create an input_text
entity.
“Eingabe für Text”
is different:
That’s strange…
Is your HA instance up-to-date?
Have you restarted HA and refreshed your browser cache?
If you can’t get the helper editor to appear normally, you can always just configure the entity in YAML.
no matter if edge or firefox, the text helper doesn’t get any different than this
Have you tried setting up a Helper with just a name then editing it once it’s created?
How? There is no option for editing yaml in the helpers section?
No idea how you get there.
Devices Services->Entities?
There isn’t even a delete option to remove useless entities/helpers.
*sigh
when clicking the gear:
Try refreshing the list first. I have previous experiences with the helper UI trying to read the helper before creation is complete, and not trying again.
If that does not work, try clearing the (frontend) cache. Your dialog indeed seems to miss some fields that should be there, such as a min max length and whether it is a password or pain text field.
Wouldn’t be the same problem on a browser I didn’t use before, wouldn’t it? Or does HA have an internal cache? Actually it looks the same on edge and chrome.
Have you tried creating a new one on the new browser? Maybe the entity is indeed broken because it was made by an old cached UI on a new instance?
Woah that indeed worked, thanks. Looks like HA isn’t a Firefox friend. Gotta switch over to Chrome for it.
However, still this problem:
What I want with a text helper:
What I get with the text helper:
If Firefox was your goto browser before, flushing the cache there might have helped there too. Any browser can get caught in old caches.
I am fine with both, doesn’t matter. But I still have the problem that I get totally different options with the text helper
Where did you get that screenshot from? Because I don’t have it either. And this would typically be an option only available in the yaml version, not the UI. If you create an innput_text in yaml you can set it, but not in the UI that I have.