-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
deCONZ in Ingress: failed login attempts when only surfing/loading Phoscon app #3595
Comments
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: 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 Test 2: |
Yes it works only with local IP, but not with my domain name. |
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
Home Assistant Cloud
Home Assistant Supervisor
Anything 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 (#3226 (comment)), 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.
The text was updated successfully, but these errors were encountered: