Deconz through ingress has an unselectable system

[PaulAntonDeen]

I have updated to Deconz 5.0 and HA 103.4 HassOS 3.7 and when I use the Deconz addin through ingress I get a page where I can see my Conbee stick but not select it (it is grayed out):

Everything else that was configured before upgrading to version 4 of Deconz still works, I just cannot use the deconz web interface to add new things or change config.

[frenck]

Hi there!

Thanks for opening an issue. It might be caused by previous data stored in your browser cache (cookies to be more exact). Be sure to clean your browser cache including cookie/application data.

For testing, you could try using a browser in incognito mode.

[PaulAntonDeen]

When opening HA in an incognito window I do not see anything except the P on top of the page. When clicking on that, the search for gateways starts and that seems to go on forever. (I can still control all the lights connected to the stick).

Clearing all cookies and loading through a normal chrome window yields the same behavior. (chrome on Mac, I will try another browser and OS to see if that makes a difference).

[PaulAntonDeen]

Found something: I normally approach my home assistant with its external domain https://my.domain.com:8123/core_deconz and ssl (even when I'm home). When I change the domain to its local IP adres https://192.168.2.103:8123/core_deconz suddenly things work great and I control my deconz stick.

[frenck]

That is interesting. I use a similar setup (where I use my external domain name internally as well), including SSL and I'm not experiencing that issue on any of my systems.

Nevertheless, thank you for sharing details, will look into this a bit more and see if I can find a way to reproduce your issue.

[PaulAntonDeen]

For your diagnostics:
I'm using the let's encrypt addon for the certificate
in configuration.yaml I have:

http:
  base_url: https://my.domain.com:8123
  ssl_certificate: /ssl/fullchain.pem
  ssl_key: /ssl/privkey.pem

In my router port forwarding is configured for 80 and 8123
The setup runs on hassio on a RPI3+

[asbl]

Thx. I'm using deconz in hassio without https. After updateing hassio and deconz addon, I had the same problem with chrome and firefox, so deconz was not usable. With your workaround I was able to use the interface again

Btw: I'm not using https

[Mimiix]

@frenck #941 is not fixed by any means. I am unable to use that. Further more i am now experiencing the same behaviour as @PaulAntonDeen.

What i did notice, is that it uses 8081. Is this port needed ? I believe that that port is used by Motioneye aswell.

[saruter]

Hi, I have the same issue when using Deconz Addon 5.0 via Ingress behind a Apache reverse proxy with SSL. I am seeing only the Phoscon "P"-Logo. Access via local http://hassio.local:8123 in browser works fine.
My setup:

• HassOS: 3.7
• Home Assistant: 103.5
• Deconz Addon: 5.0
• using Home Assistant via apache webserver as reverse-proxy and SSL
• use it from inside and outside my home network under domain https://smarthome.xyz.tld

I tried restarting Home-Assistant/Deconz Addon several times and cleared browser cache and tried incognito mode in Firefox and Chrome.
I tried setting the "base_url" parameter in configuration.yml to "https://smarthome.xyz.tld" as mentioned before, but that didn't changed anything.

What I see in the network tab in the firefox developer tools is the following:
Normal requests go to "https://smarthome.xyz.tld" whereas shortly after the Deconz Phoscon App is selected and only the Phoscon logo is visible, I see requests to "https://192.168.179.175/api/hassio_ingress/Ud2cwvHajsRCsIXVWEQ0ZueliqRvRxupzvsrwsfGPNA/api/config?_=1577739126418" which is strange because this address is the laptop I'm accessing Home Assistant and not the server which is serving Home Assistant...

Probably this helps solving the problem or getting nearer to a solution...

[mira2002]

This is a CORS Problem. The Ajax requests over Javascript use the wrong Domain / IP verwendet. Here the message form the browser console:

Quellübergreifende (Cross-Origin) Anfrage blockiert: Die Gleiche-Quelle-Regel verbietet das Lesen der externen Ressource auf https://192.168.178.25/api/hassio_ingress/m6-hgvHOoz-Wz8P2LeQK34cnP1T1fDzKVca3jHgajTk/api/config?_=1578157483133. (Grund: CORS-Anschlag schlug fehl).

[schneekluth]

Found something: I normally approach my home assistant with its external domain https://my.domain.com:8123/core_deconz and ssl (even when I'm home). When I change the domain to its local IP adres https://192.168.2.103:8123/core_deconz suddenly things work great and I control my deconz stick.

Same here on 0.104.3 running behind nginx-proxy-manager. I have set base_url, use_x_forwarded_forand trusted_proxies in configuration.yaml and access my hass.io via same url externally and in my home network. Deconz Web UI only works with internal IP. External url just shows the "P" logo without any gateway discovered.

[PaulAntonDeen]

The problem still persists on Deconz 5.1 with HA 0.104.3

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[SukramJ]

The problem still persists on Deconz 5.3.1 with HA 0.106.5.

It works without TLS, but still an issue with TLS an NGINX Reverse Proxy.

[PaulAntonDeen]

Confirmed here as well

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[PaulAntonDeen]

Still broken

[Sirezul]

Same for me, still broken with SSL.
Local IP works.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[saruter]

Still broken...

[PaulAntonDeen]

Still broken on HA 110.6 with deconz 5.3.5

[Mimiix]

I'm wondering, i've had this issue only when i used my external_ip in HA.

However, what browser are you using @PaulAntonDeen ?

[Syrox94]

Still not working with reverse proxy :/

[zybster]

I'm experiencing the same issue - Only the P show's up in Phoscon app when calling it via external domain.
Only works when accessing Homeassistant via LAN IP:8123
A fix would be greatly appreciated.

[TekkertheChaot]

Same issue here! Local IP access works, but as soon as I try to connect from external SSL domain, it doesn't

[cairon-ha]

Same issue here on core-2021.11.5 on supervisor-2021.10.8 and Home Assistant OS 6.6

It took me quite a while to find that issue and configure the Gateway.

Some said that switching from https to http can be a solution. Do you know how I can do that?

Thanks!

[Iscanniya]

Now I'm with you. Today, for no reason, I cannot access the gateway. It's only telling me, that it scans for gateways, but nothing happens. Using core-2021.12.3 and supervisor-2021.12.2 and Home Assistant OS 7.0

I thought it'd be the ConBee II Stick, so I resetted it with firmware flashing tool. Now, I can see in my logs corresponding to the gateway entry:
21-12-20 18:47:54 WARNING (MainThread) [supervisor.api.middleware.security] No API token provided for /api/8FE2467DF1

How to connect to that ConBee Stick again, if i cannot enter the Phoscon Page?

[wauswaus]

That is unrelated to this issue, see https://community.home-assistant.io/t/deconz-official-thread/100504/2800
Has something to do with the Deconz update to 6.11.0

[DanielTheCoder]

Upgraded already to 6.11.1, cleared local browser cache, solved access problem for me.
home-assistant/core#62388 (comment)

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[mueslo]

I am using the deCONZ 6.11.1 addon and the issue persists.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[TekkertheChaot]

Issue is not resolved yet.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[felixfischer]

Issue is not resolved yet.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[felixfischer]

And that's how you reduce the number of open issues simply by doing nothing. Genius!

[tannyl]

@felixfischer hopefully #2325 will get merged very soon and I hope that will finally fix this problem.

[mdegat01]

Damn, forgot to remove stale in time. Just for you @felixfischer I'll reopen it so it can close for real 😄

[felixfischer]

Awesome! I can confirm that the issue has been resolved! 🚀 👍