Simplistic configuration UI

Share your Projects!
203

Hi,
I’m using Hass Configurator with the official Add On on Hass.io with Version 0.2.0.

Everything works fine, except the information from the homeassistant_api are not loading into Hass Configurator Editor. The fields for Events, Entities and Services are empty.

I tried a lot configurations, with no success.

This is my config, please help

{
  "homeassistant_api": "http://192.168.2.25:8123/api",
  "homeassistant_password": "my_HA_password",
  "username": "admin",
  "password": "super long and safe password",
  "certfile": "/ssl/cert.pem",
  "keyfile": "/ssl/privkey.pem",
  "ssl": true,
  "allowed_networks": [],
  "banned_ips": [
    "8.8.8.8"
  ],
  "ignore_pattern": [
    "__pycache__"
  ]
}
204

Is your configuration for the API correct? It is when the dropdown-menus with the entities are populated. If they are, then I don’t know what could be causing the problems.

205

It should be possible to keep the default API (http://homeassistant:8123/api) since hassio has its own DNS. Besides that it is required that the password for the API is set in Home Assistant as well. So in your configuration.yaml you need to have something like:

http:
  api_password: super long and safe password
206

thx for reply,

Are you sure? I thought my “super long and safe password” is for the login for HASS Configurator? And the "homeassistant_password": "my_HA_password" is the api_password?
I’m confused :confused:

I tried with all passwords the same. But no success :frowning:

Thats the log:

INFO:2017-09-27 22:33:31,157:__main__:193.107.xx.xx - "GET / HTTP/1.1" 200 -
WARNING:2017-09-27 22:33:31,191:__main__:Exception getting bootstrap
WARNING:2017-09-27 22:33:31,192:__main__:Remote end closed connection without response
INFO:2017-09-27 22:33:33,168:__main__:193.107.xx.xx - "GET /api/listdir?path=. HTTP/1.1" 200 -
INFO:2017-09-27 22:33:34,534:__main__:193.107.xx.xx - "GET /favicon.ico HTTP/1.1" 200 -
INFO:2017-09-27 22:33:34,536:__main__:193.107.xx.xx - "GET /favicon.ico HTTP/1.1" 404 -
207

homeassistant_password is the one you set for HASS. username and password is what you use to login to the configurator itself.
The logoutput tells us, that the configurator is not able to fetch the required data from the API. It should get the data from 192.168.x.x, but in the log it shows some external IP. Do you have an explanation for that? Did you change the API setting to your external IP?

208

No I have no explanation for that.

My configuration.yaml looks like this

http:
  api_password: !secret api_password
  ssl_certificate: '/ssl/cert.pem'
  ssl_key: '/ssl/privkey.pem'
  trusted_networks:
    - 127.0.0.1
    - 192.168.2.0/24
  ip_ban_enabled: True
  login_attempts_threshold: 5

The log above is done remotely. But if I connect locally its the same…
Where do I find the API settings to change to external?

209

To be honest: I have no idea what the problem can be. The config is looking good to me. And sinc I don’t use hassio myself, I have nothing to compare. Maybe someone reading along with a working hassio setup is able to help.
The main error is that the configurator fails to use the HASS API. Maybe look at the HASS logs for more information. Maybe even set the log level to debug to get more output.

210

Hm, thats strange…

Just to be clear.
I tried to access HASS Configurator Locally. Now I see this in the Log. Its a Local IP, but thats the IP of the devices accessing HASS Configurator (192.168.2.27) not the IP of Home Assistant (192.168.2.25)

So it must be 192.168.2.25 to get it to work?

INFO:2017-09-28 00:40:54,082:__main__:192.168.2.27 - "GET / HTTP/1.1" 200 -
WARNING:2017-09-28 00:40:54,088:__main__:Exception getting bootstrap
WARNING:2017-09-28 00:40:54,089:__main__:Remote end closed connection without response
INFO:2017-09-28 00:40:56,171:__main__:192.168.2.27 - "GET /api/listdir?path=. HTTP/1.1" 200 -
INFO:2017-09-28 00:40:57,564:__main__:192.168.2.27 - "GET /favicon.ico HTTP/1.1" 200 -
INFO:2017-09-28 00:40:57,566:__main__:192.168.2.27 - "GET /favicon.ico HTTP/1.1" 404 -
INFO:2017-09-28 00:42:17,672:__main__:192.168.2.27 - "GET / HTTP/1.1" 200 -
WARNING:2017-09-28 00:42:17,706:__main__:Exception getting bootstrap
WARNING:2017-09-28 00:42:17,707:__main__:Remote end closed connection without response
INFO:2017-09-28 00:42:20,059:__main__:192.168.2.27 - "GET /api/listdir?path=. HTTP/1.1" 200 -
211

No, that’s ok like that. That was a mistake on my side. It is indeed the accessing IP, not the target for the API. I messed that up.

212

Ok,

So still no reason why its not working?! :frowning:
I try to find someone with completely working Configurator and hass.io

Thanks for helping

213

The API is working fine. I can see/edit the folders/files with no problems.

It’s just the hass restart button. Not an issue as I can do it from the configuration module.

214

You dont need the api to edit folder or files.
Its for things like Restarting or the List oft Entitie IDs or services.

215

for autorun, if you’re on a raspeberry PI i suggest you follow uption 2. works fine.
just bear in mind that the Hass-PoC-Configurator file should end with .service as oppossed to .systemd.
Once you creater follow the instruction on the enable command and it should work.

216

How kind of you, thanks! I have read that in an earlier post of yours so I figured that out already.

217

One thing just came to my mind: You have HASS configured to use SSL, correct? In that case you must also use SSL for the API. So instead of::
"homeassistant_api": "http://192.168.2.25:8123/api"
try
"homeassistant_api": "https://192.168.2.25:8123/api"

The regular http-backend doesn’t exist anymore when you enable SSL.

218

Hi,
yes SSL is enabled.
I tried this before, too. But also no access.

Maybe with ssl its because, the Local IP doesn’t match the DNS of the Cert (duckdns.org). The local IP Adress is also marked as “unsafe” in the Browser.
Is it possible to disable SSL Auth for local access?

WARNING:2017-09-28 16:34:39,194:__main__:hostname '192.168.2.25' doesn't match 'xxx.duckdns.org'
INFO:2017-09-28 16:34:40,256:__main__:192.168.2.4 - "GET /api/listdir?path=. HTTP/1.1" 200 -
219

Have you tried setting the hass-API option to you duckdns hostname? If hass is exposed to the internet, then that should be working if your port forwarding is working as well.

PS: No, it’s not possible to disable SSL verification. The urllib.request.Request method has no flag for this.

220

Hi,

sorry for late response.
Its also not working with the DNS Name :frowning:

Maybe it has something to do with the SSL connection.
If I have time, I will try to test without SSL.
I post my results here.
Thx a lot for all the help!

221

Hi,

all my errors are gone with ne new hass.io Addon Store Version auf Configurator (0.2.0-p3)
Now it works like a charm inclusiv the entity ID list.
Thx a lot for the hard work.

1 Like
222

I’ve set up DuckDNS on my Hass.io setup but can no longer access the configuration panel. Everything was working fine before I set up DuckDNS. Tried adding SSL to true and adding the DuckDNS ip address in options.

Any advice?

EDIT i unded up settign 0.0.0.0/0 for known devices and it started working. Is there any other way to implement without exposing all the ips?