Configurator breaks after 0.92 upgrade

Configuration
1

With both 0.91 and 0.92 upgrades now - configurator breaks.
Error message “hassio.local refused to connect” and a little cloud graphic.
Previous support worked with the apprent changes related to the ingress capabilities.
Here is my config:

Enables configuration UI

config:
panel_custom:
- name: hassio-main
sidebar_title: Configurator
sidebar_icon: mdi:wrench
js_url: /api/hassio/app/entrypoint.js
url_path: configurator
embed_iframe: true
require_admin: true
config:
ingress: “core_configurator”

2

I’m also unable to access configurator since updating to 0.92.1. I have configurator 3.2 installed via Hassio. The documentation provided on the configurator page gives an error when trying to save. I’m not able to start the add-on, and trying to access it from the menu gives the cloud graphic and “hassio.local refused to connect” message.

3

Not sure which way I’m facing now…
Loaded the configurator addon v3.2 and it works but, I now have 2 x Configurators on my menu.

hassio-menu
hassio-menu208×587 13.1 KB

4

I see two configurators on the menu as well. However, one gives a 502 bad gateway for me, probably because the add-on won’t start. When I try to set up Configurator with the config recommended in the documentation

{
“dirsfirst”: false,
“enforce_basepath”: false
}

I get the following error:

not a valid value for dictionary value @ data[‘options’]. Got {‘dirsfirst’: False, ‘enforce_basepath’: False}

5

If you have an iframe setup for Configurator, remove it. I’ve been unable to start it with the link on the add-in configuration page, either. What DOES work, is configuring an HTTP port (like 3218) on the configuration page, restarting Home Assistant, then opening a new window in your browser at http://home-assistant-IP:3218/ It should ask you for your username and password, then display the good old Configurator screen you all know and love. Good luck!

1 Like
6

I installed a new home assistant 0.92.1 through docker.io. Added addon configurator 3.2 via Hassio. When you start Open Web UI on the configurator page, it gives error 502: Bad Gateway. I tried the recommendations indicated in the branch, but they do not help. Help please advice. Thank you in advance.
My logs see below
Log

[15:39:54] INFO: Add-on running PANIC: unprotected error in call to Lua API (bad light userdata pointer) INFO:2019-05-02 15:39:55,823:hass_configurator.configurator:Starting server INFO:2019-05-02 15:39:55,825:hass_configurator.configurator:listening on: http://127.0.0.1:80

System log
19-05-02 11:26:19 INFO (SyncWorker_11) [hassio.docker.interface] Restart homeassistant/raspberrypi3-64-homeassistant
19-05-02 11:26:53 INFO (MainThread) [hassio.homeassistant] Detect a running Home Assistant instance
19-05-02 11:34:30 INFO (SyncWorker_1) [hassio.docker.interface] Restart homeassistant/raspberrypi3-64-homeassistant
19-05-02 11:34:57 INFO (MainThread) [hassio.homeassistant] Detect a running Home Assistant instance
19-05-02 11:39:50 INFO (SyncWorker_8) [hassio.docker.interface] Stop addon_core_configurator application
19-05-02 11:39:51 INFO (SyncWorker_8) [hassio.docker.interface] Clean addon_core_configurator application
19-05-02 11:39:53 INFO (SyncWorker_1) [hassio.docker.addon] Start Docker add-on homeassistant/aarch64-addon-configurator with version 3.2
19-05-02 11:40:03 ERROR (MainThread) [hassio.api.ingress] Ingress error: Cannot connect to host 172.30.33.0:8099 ssl:None [Connection refused]
19-05-02 11:43:14 ERROR (MainThread) [hassio.api.ingress] Ingress error: Cannot connect to host 172.30.33.0:8099 ssl:None [Connection refused]
19-05-02 11:48:32 ERROR (MainThread) [hassio.api.ingress] Ingress error: Cannot connect to host 172.30.33.0:8099 ssl:None [Connection refused]

7

How do you do this?

8

This may be the same symptom coming from a different cause, but I found an answer to the same problem.
I started getting the 502: bad gateway error after an update. A little poking around revealed that Configurator needed to be turned on again as one of my add-ons. After I restarted Configurator, it started loading as normal.

1 Like