Open bcutter opened 4 months ago
I've got same problem ...
Similar issue, I get this problem when starting Phoscon from Campanion app but not from Chrome on windows
Test 1: Tried with Google Chrome on Android - same issue.
It really doesn't matter which browser/app is used.
Really starts to annoy me as hell as it makes it impossible to use Phoscon ~at all~ in Home Assistant!
Test 2: Tried to directly access Phoscon by using http://servername.domain:40850 in the browser. This is working - as it bypasses Home Assistant's UI. So it seems to be an Ingress related issue.
Yes it works only with local IP, but not with my domain name.
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.
Still broken. And no one cares. Great perspective for deCONZ users in Home Assistant.
Yes still broken. It's really strange that there aren't more complaints. I know for myself that the next coordinator will not be a conbee.
Same problem here, successfully locked me out with all my devices somehow :)
This is the request that fails:
Seems like it is also an old problem: https://github.com/home-assistant/addons/issues/929
The lack of interest from HA side (because of ZHA) and the lack of man power (and understanding how important the HA addon is in their chain and for their user base) from Dresden will very likely be the reason for this issue to never get solved. Same drama like with releases (we're now half a year behind the latest release...).
For this case both is needed: knowledge of Phoscon and of Ingress (HA side).
Feel free to prove me wrong.
Upgrade deConz to v2.27.6 :) https://github.com/home-assistant/addons/pull/3708
Upgrade deConz to v2.27.6 :)
Interesting. Where's the proof it fixes the issue? Any specific change or what are you referring to?
And recent PRs for the 2.27.6 release have been rejected so far, so I don't see a quick solution yet.
Still exists for me with deCONZ v2.28.1 (updated following https://github.com/home-assistant/addons/pull/3708) 😞
As this issue sits right between the two competence fields of both involved parties (HA team on the Ingress side and Dresden Elektronik team on the deCONZ side), I doubt this will be fixed or even looked into until they found an agreement on the deCONZ addon support topic.
Yes, I ordered sonoff zigbee dongle E and I am moving my zigbee network to it right now.
Describe the issue you are experiencing
Only surfing
/core_deconz/ingress
and selecting "Phoscon" ("deCONZ" works just fine) creates failed logins for the client. When using HTTP security (ban module on frequent failed logins) this immediately leads to a blocked client inip_bans.yaml
which hurts quite a bit (need to clean the file and restart HA Core):I can reproduce this issue with different clients (Win 11 in Firefox, iOS with HA Companion app, doesn't really matter).
It is sufficient to only load the Phoscon part, no need to enter any password at all. Some automatic API request seem to fail.
Assumption: As probably most users don't use HTTP security this issue has not been discovered so far.
What type of installation are you running?
Home Assistant OS
Which operating system are you running on?
Home Assistant Operating System
Which add-on are you reporting an issue with?
deCONZ
What is the version of the add-on?
6.23.0
Steps to reproduce the issue
/core_deconz/ingress
)System Health information
System Information
Home Assistant Community Store
GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok GitHub API Calls Remaining | 5000 Installed Version | 1.32.1 Stage | running Available Repositories | 1478 Downloaded Repositories | 85 HACS Data | okHome Assistant Cloud
logged_in | false -- | -- can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | okHome Assistant Supervisor
host_os | Home Assistant OS 12.2 -- | -- update_channel | stable supervisor_version | supervisor-2024.05.1 agent_version | 1.6.0 docker_version | 25.0.5 healthy | true supported | true board | rpi4-64 supervisor_api | ok version_api | okAnything in the Supervisor logs that might be useful for us?
Anything in the add-on logs that might be useful for us?
Additional information
Possibly related to the Phoscon bug introduced with addon version 6.21.0 (https://github.com/home-assistant/addons/pull/3226#issuecomment-1737293462), being reverted in 6.22.0 and "somehow" fixed (worked around?) in 6.23.0.
During that adventure the Phoscon page was in the spotlight of issues already. Maybe this issue is a leftover or a side effect of the fix.