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[bot]]

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[bot]]

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[bot]]

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 ?

[PaulAntonDeen]

I use Chrome on Mac and Windows and the problem occurs on both. My HA (formerly called Hassio) is running on an rPi which has port 8123 and 80 port forwarded to it from my router. For me the issue occur when I use my private domain to access HA and it does not matter if I am internally connected to the WiFi or externally connected to another network. When I'm connected to local wifi I can change just the domain part to the local IP of the Pi and everything works fine.

[PaulAntonDeen]

And just confirmed the problem using MS Edge 42.17134.1098.0 (the pre-chrome version) as well.

[Mimiix]

That's not the issue.

In HA, 40850 is the port that's used (afaik). What happens if you portforward that 40850 in the router aswell?

[PaulAntonDeen]

No difference when port forwarding that one as well. You see in the Deconz logs that it is contacting itself on port 8123.

GET /api/config HTTP/1.1" 200 263 "https://**.**.**:8123/api/hassio_ingress/uL8ItLFEWDEy5QFNhRMZH6YV6T-yWLILWdBlsKkeo/pwa/login.html?1591772140245" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.97 Safari/537.36"

[Mimiix]

It's not deCONZ doing that, it's the implementation of the ingress thing. Unfortunately, that's not something deCONZ should fix. Should wait on a addon dev.

What you can try is see what happens if you contact your IP on 40850 .

[PaulAntonDeen]

Thanks for your help thinking through the problem. My guess the problem is in Ingress configuration. Using my domain URL or my internal IP address, nothing happens at port 40850. It cannot reach a website there. I think when Deconz moved to exposing the web-end through ingress, it stopped being accessible any other way. That is also when these problems started. So if I access ingress through my internal IP but with the rest of the URL exactly the same, it all works fine (still on port 8123).

[Mimiix]

Wait, you forwarded to port 80 right?

What happens if you put that back to 40850?

[PaulAntonDeen]

Initially no, i forwarded to 40850, but now I tried forwarding to 80 and 8123. No difference.

[mira2002]

Hi,

I get the follwing error in the chrome console when I start the addon page over ingress:

[Mimiix]

@PaulAntonDeen For me it always worked when i put http://internalip:40850/pwa/

Make sure not to use HTTPS on this. Phoscon doesn't seem to speak HTTPS.

[stale[bot]]

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.

[stale[bot]]

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.

[Sirezul]

Still a thing.

[stale[bot]]

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]

Still an issue with Phoscon Web App. The deCONZ application works.

[schneekluth]

Still an issue with Phoscon Web App. The deCONZ application works.

Same here.

[oashour]

Still broken.

[wauswaus]

looks like nobody wants to fix this

[tazztone]

gateway is never to be found when clicking on the "phoscon app" button inside deCONZ (win10 latest deconz version). also the "webapp" will not allow to reset the pw or say "error! on sending login data"

still dealing with the usb reconnect loop issue and trying to update firmware which always fails in deconz within hass.io.

[stale[bot]]

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.

[pawlizio]

I have same problems, but I use a reverse proxy, so all the domain certification is done on a seperate server. When accessing via public domain, I just see the P of phoscon app, no gateway. If I open via local domain everything works great.

[ottelo9]

I have same problems, but I use a reverse proxy, so all the domain certification is done on a seperate server. When accessing via public domain, I just see the P of phoscon app, no gateway. If I open via local domain everything works great.

I use reverse proxy, too. Have the same problem!

[stale[bot]]

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.

[robertmx]

Still an issue :-/. Even without a reverse proxy (but an external DNS name) the phoscon app doesn't work. It seems the ingress routing is broken. I see a lot of XHR requests, that have the resource path duplicated and some others failing for no obvious reason.

[Sirezul]

Still an issue :-/. Even without a reverse proxy (but an external DNS name) the phoscon app doesn't work. It seems the ingress routing is broken. I see a lot of XHR requests, that have the resource path duplicated and some others failing for no obvious reason.

@frenck could you help us with this one? It's been so long and this issue is still open. Any help is very much appreciated. If more information is needed I can provide it.🙏

[stepman0]

Same problem here... Any hints?

[LeoLTM]

Still an existing problem... ran into it while configuring my ConBee II today...

[felixfischer]

Absolutely not stale!

[maikalms]

Still Broken..