You’re solution worked perfectly for me with the configurator. Do you know how to get the corresponding url for the node red add-on, which is also using ingress. I have exactly the same problem with a double panel as above for the configurator.
Same experience with Node-RED here.
If you open the addon settings it will show you in the address bar the URL you need to use for that addon for the ingress: setting. It might have letters and numbers in it. It might look like xxxxxx_node-red or something like that. The URL_path is where the side panel tries to open when you tap on it. It might be node-red or something like that. The other settings seem to be common to all addons. I am using ingress with configurator, ssh & Web terminal and vscode addons.
I found the Node-red url that works with panel iframe using the following method.
- Open Node-red from the add on page under web ui.
- In your browser (in my case Safari) find the corresponding to the following:
a. Open develop menu
b. Select web inspector
c. In the inspector select the document tab
d. Under name there are is a list some having a long complex string. Right click the string and select copy url. - Go back to configuration.yaml
- Paste the url you copied as the url in your panel iframe configuration for Node-red.
2 Likes
Just an update from the official blog:
For the upcoming Home Assistant 0.92 release, we will be adding support to add links to your add-ons to the Home Assistant sidebar via a toggle on the add-on details page. The link will open the add-on Ingress interface, embedding the add-on in the Home Assistant UI. This will make it look and feel like a single system.
After upgrading the add-on, my
panel_iframedoesn’t work anymore.
This is related to the question above. Once you enable direct access again, your iFrame panel will start working again. Until the automated panel integration lands in 0.92, you can also manually add a panel that points at Ingress.
Check my previous post for the manual configuration.
I cannot access the add-on via Ingress using the Tor Browser or Firefox.
We found a last minute issue impacting Firefox based browsers (including the Tor Browser). There are some issues accessing add-ons that use WebSockets. We have identified the issue and expect it to be solved with the release of Home Assistant 0.91.4.
2 Likes
I still can not get it to work. I have this in my config:
configurator:
title: Configurator
icon: mdi:wrench
url: 'http://192.168.0.110:8123/api/hassio_ingress/xxx/'xxx replace my key for now. I still get a 401 when I rebooted my system. How can I get it to work?
Are you an admin?
Any user assigned the role of “user” does not have access to configuration or the hassio panel at all. You have to be administrator. It is using SSO and when you open this new ingress version of configurator you are signing in with whatever admin you are currently signed in with.
Yes, my account is an admin account.
I need to access the configurator first through the hassio addon webui. When I have done that, the menu option in the panel works. Before that I Still get the 401 error.
I run hass.io on a pi. Version is 0.91.3
Iam having the same issue. If I open webui once the iframe works …
I use
panel_custom:
- name: hassio-main
sidebar_title: Configurator
sidebar_icon: hass:settings
js_url: /api/hassio/app/entrypoint.js
url_path: configurator
embed_iframe: true
require_admin: true
config:
ingress: core_configurator
that works without problems
Got it working too. Found the solution in an other topic.
Share a link please, thanks
panel_custom:
- name: hassio-main
sidebar_title: Configurator
sidebar_icon: hass:settings
js_url: /api/hassio/app/entrypoint.js
url_path: configurator
embed_iframe: true
require_admin: true
config:
ingress: core_configurator
Yeah I saw that but @lifelogger said he found a solution in another channel…
I need a solution for all other iframes… VS code, ESP Home, Portainer, Node red etc. Guess I just have to wait for the next release 
You could wait, or just reuse the same code… This is for VSCode:
- name: hassio-main
sidebar_title: Visual Studio Code
sidebar_icon: mdi:visual-studio-code
js_url: /api/hassio/app/entrypoint.js
url_path: vscode
embed_iframe: true
require_admin: true
config:
ingress: a0d7b954_vscode
The other ones you can figure out too, just go to the hassio page, click on the addon’s “Open Web UI” page, and see what’s at the end of the url. That goes in the “ingress: XXXXX” part of the custom panel code.
As per what @Silicon_Avatar said… there is no ‘fix’ you just need to see what to add and it’s pretty simple - use the configurator one as a guide.
This worked for me for the configurator:
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"
1 Like
WIth the 0.92 is not necessary to add the panel_custom in the configuration file.
Just go the add-on details page and use the toggle Show in Sidebar.
The Configurator will be added to the menu.
6 Likes
Handy.
Hopefully a check config button gets added to the configurator header. It would be so much easier than switching tabs from configurator — configuration → check config button.
Can anyone tell me how to to link to an internal page of Home Assistant using iFrame without the sidebar and header being duplicated? I want place a link in the sidebar to take me to the ZHA configuration page, but I end up with the whole page including header and sidebar embedded within.
# iFrame Panel integration
panel_iframe:
zha:
title: Zigbee
url: http://192.168.0.40:8123/config/zha/dashboard
icon: mdi:zigbee
require_admin: true
Is there a URL I can use to just point it at the internal part of the page?
1 Like
Panel Redirect can be used to accomplish this. Hopefully this will help someone and it will be added to the core of Home Assistant at some point in the future with no need to seek this out.
1 Like