Simplistic configuration UI

woody4165 · April 9, 2019, 10:14am

just found this thread, thanks to @DavidFW1960, since I was looking for “Configurator Addon”.

I’ve opened an issue on the Github project page since it was not so easy to understand how it has changed from 2.1 to 3.0

Thanks to other user messages, most have been clarified.

Last think I haven’t got is if there is still a need for username and password or this is obsolete since everyone has the last part of the url that is different from each other.

Thanks for your work!

DavidFW1960 · April 9, 2019, 10:16am

It uses a home assistant user for authentication so you don’t configure it anymore. It says that in the post I linked you to.

duncank · April 9, 2019, 1:21pm

I’d like to add that this doesn’t work when HassOS isn’t updated to version 2.11. (Hassio -> System tab). I was on v1.13 and I didn’t know this could be and needed to be updated manually.
I had to click update manually and after that the ingress-badge was visible in the configurator plugin details, and the “open web ui”-button actually works. Before that, it direct me to about:blank#blocked.

woody4165 · April 9, 2019, 1:24pm

Correct, i was on 0.91.0 and wasn’t working, it was not possible to install if first time.

Then I updated on 0.91.2 and it’s working.

Don’t know if it is ok on 0.91.1

Maikl_Sh · April 9, 2019, 3:00pm

Thanks for the update!
Configurator works.
But only I did not manage to add the link to panel_iframe:
Has anyone got it?

apop · April 9, 2019, 3:05pm

Is it possible to have the Hassio add-on changelog updated with some of this so there’s a little more clarifying information? Not sure who manages that but it would probably help cut down some of these questions.

The HASS documentation is now out of date as well, but anyone can submit a PR to have that updated. I don’t mind trying to do that later today if nobody else gets to it first.

github.com

home-assistant/hassio-addons/blob/master/configurator/README.md

# Home Assistant Add-on: File editor

Browser-based configuration file editor for Home Assistant.

![Supports aarch64 Architecture][aarch64-shield] ![Supports amd64 Architecture][amd64-shield] ![Supports armhf Architecture][armhf-shield] ![Supports armv7 Architecture][armv7-shield] ![Supports i386 Architecture][i386-shield]

![Configurator in the Home Assistant Frontend][screenshot]

## About

The File editor, formerly known as Configurator, is a small web-app (you access it via web browser) that provides a
filesystem-browser and text-editor to modify files on the machine the File editor is
running on.

It is powered by Ace editor, which supports syntax highlighting for various
code/markup languages. YAML files (the default language for Home Assistant
configuration files) will be automatically checked for syntax errors while editing.

## Features

This file has been truncated. show original

krovachek · April 9, 2019, 3:07pm

For panel_frame on Hassio:

Install the add-on.
Start with "OPEN WEB UI’ in its window.
See the log.
You can find like this:

"GET /api/listdir?path=. HTTP/1.1" 200 8386 "http://192.168.31.143:8123/api/hassio_ingress/lotofnumbersandletterstoken/"

Copy the
http://192.168.31.143:8123/api/hassio_ingress/lotofnumbersandletterstoken
This is the url.

If it is working then could be added to the Configurator documentation

tboyce1 · April 9, 2019, 4:35pm

I must have missed something. Where was this ingress feature announced and/or where is it documented? All my searches just lead back to this one past saying that the add-on now supports it. I’d really like to learn more about how it works and how to integrate it into an add-on.

apop · April 9, 2019, 4:40pm

pocket · April 9, 2019, 6:05pm

This might be perceived as ‘anal retentive’ (which is hyphenated when modifying a noun), but I placed the link in secrets.yaml.

TomBrien · April 9, 2019, 6:09pm

Just to add that I found that after changing the iframe URL it is necessary to open use the Open Web UI link from the addon page on each device you use otherwise you will get a 401: Unauthorized error. After accessing the configurator it should work from the sidebar.

krovachek · April 9, 2019, 6:17pm

I can’t say anything…

pocket · April 9, 2019, 6:21pm

FYI

noun: anal-retentive

a person who is excessively orderly and fussy.

Maikl_Sh · April 9, 2019, 6:22pm

I did exactly as you wrote. But after copying this long address, a configuration error occurs.

panel_iframe:
  configurator:
    title: Configurator
    icon: mdi:wrench  
    http://192.168.1.36:8123/api/hassio_ingress/y00VItM88gYYpL88GMvlS-_MXQu0pcARb3KrYHkv7cM/

can not read an implicit mapping pair; a colon is missed at line 87, column 93:
… pL88GMvlS-_MXQu0pcARb3KrYHkv7cM

If you ignore this and save the changes, then errors occur when checking the configuration.
Before the configurator’s address was updated, everything was in order.
If you comment out the link, there are no errors either.

screenshot20190409211726

pocket · April 9, 2019, 6:23pm

You need the ‘url:’ tag ahead of the link.

Maikl_Sh · April 9, 2019, 6:28pm

For sure! My God, how could I forget about it.
Thank!

EpicLPer · April 9, 2019, 6:29pm

So far the way with simply copying the long string and using that on the side panel seems to work even after reboots, didn’t do a long-time test yet tho.

krovachek · April 9, 2019, 7:10pm

Oh, thanx for explanation, I’m a Hungarian guy so I have to learn more and more
In this case really anal-retentive that nobody say what we can do with this new version just it is here and eat if you can.
Anal-retentive like “zabszem van a seggében” but we use it for a person who very afraid.

pocket · April 9, 2019, 7:44pm

Yes, I spent hours yesterday trying to fix the Configurator add-on in a Hass.io installation. I thought I broke something in the process when I saw the default configuration appeared empty. Thankfully, I found this thread.

It sounds like the term “pucker factor” used by airplane pilots.

pocket · April 9, 2019, 9:21pm

Well, I was just presented with “401: Unauthorized” when trying to use a static URL in the configuration.yaml file. I guess Ingress is doing it’s job; I had another active instance. Is this expected behavior?