Panel_iframe for configurator

Configuration
1

I’m just trying to get a link in Hassio with an iFrame to configurator, but it’s not quite working!

I kind of get a double version of hassio. See the image:

Any ideas?

This is my code:

panel_iframe:
  nodered:
    title: 'Node-Red'
    icon: 'mdi:shuffle-variant'
    url: 'http://192.168.1.xx:1880/'
    
  configurator:
    title: Configurator
    icon: mdi:wrench
    url: 'http://hassio.local:8123/hassio/ingress/core_configurator'
  
  backup:
    title: 'Snapshots'
    icon: mdi:cloud-upload
    url: 'http://hassio.local:1627'

30
301527×903 69.3 KB

1 Like
2 
configurator:
    title: Configurator
    icon: mdi:wrench
    url: 'http://hassio.local:3218'
3

You need the url generated by opening the new tab (button in upper right). Paste this url into your configurator panel config.

3 Likes
4

I’m not sure which ingress URL to use in my case since I use a custom port and forward to 8123. If I use the hassio.local ingress URL I can access the Configurator from the iFrame panel fine from inside but not from outside. The opposite is true if I use my duckdns ingress URL. Any ideas? Thanks!

5

Is it just me, or has the new tab button disappeared in configurator 3.1?

6

It should still be there. I have changed the previous icon (3 vertical dots) with a gear icon though. I did this to make it stand out more visually. Apparently there were quite a few people unaware of all those extras hidden in that menu because it never occurred to them to click it.

7

Gotcha. Just remember it being a button shaped like a box? Got it though and been able to grab in ingress URL for the add-on :grin::grin:

8

Daniel… is there still a reason to keep using the one from your repo that was always more up-to-date anymore or should I switch to this official one now?

9

Problem is this gives 401 error after restarts until I go through the add-on page

10

Does not work for me. It looks like the url holds a session id or something. When I use the whole url including session id I get a 401 not authorized. When I leave the session id out, I get a 404.

Can someone post the correctly url or config?

11

I’m also getting the same behavior.
I get the 401 message until I click the Open web UI link on the add-on. After that it works again.

12

Same here.

13

Another here.

14

It depends… As you see, there are people struggeling with embedding the ingress-configurator. On the other hand, your existing setup with the SESAME etc. aren’t required anymore. So if you have some exotic setup where you access the configurator directly, this may break because you can’t do the port forwarding.

My suggestion: Create a feature request where ingress-add-ons should get “add to menu”-checkboxes. Those then could add a link in the menu on the left were currently users have their panel-iframe links. That way users don’t have to get to the “open web ui” button to reliably open the configurator.
I bet this solution would make future ingress-add-ons a lot more userfriendly.

3 Likes
15

Thanks Daniel… so you are going to maintain your repo one going forward as well and it will continue with user/pass/sesame? If so then I don’t see any point changing something that is working very well.

I guess as more addons move to ingress like Frenck’s ones, there will be a smoother transition and less confusion for everyone.

16

Yes. That way I stay in control of providing new releases when they are done. It took several months for the official add-on to be updated. So with my repo there’s an alternative (without ingress).

1 Like
17

Hi all,

My panel iframe was working fine until i updated to Home Assistant 0.91.3, now when i click it i get this. but still able to access via webui in addons.

CHA
CHA1238×655 38.1 KB

i had yaml file like this :

panel_iframe:
  configurator:
    title: Configurator
    icon: mdi:wrench
    url: http://192.168.1.90:3218

anyone got a solution ?

thanks in advance

18

Hass.io > Dashboard > Configurator (add-on)

scroll down to Network, add 3218 as port and hit save.

1 Like
19

same here. Whomever introduced ingress into the architecture for this ‘single’ add-on needs to go back to 1st principals and ensure release testing and documentation BEFORE production upgrade!

20

I did that … but no luck …

also i noticed that there was a place to add your password for your Configurator addon, but now it just says

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

but i till have access via addon webui

but panel_iframe not working