-
-
Notifications
You must be signed in to change notification settings - Fork 29.2k
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
UniFi: Add UDM/P support #33766
UniFi: Add UDM/P support #33766
Conversation
scrolling through looks like maybe this is now fixed? however I still get the error. I tried to change it to use port 80 because the controller doesnt run on 8443 anymore for UDM/P. Didnt work. |
Try 443 |
I did, I used my local ip 192.168.1.1 port 443 and then my unifi username and password, I also tried UBNT and my ssh password. I’m on 0.108.0 for HA.
… On Apr 8, 2020, at 2:53 PM, Robert Svensson ***@***.***> wrote:
Try 443
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub <#33766 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABIV6MOPBC5A6NYUOAM5KUTRLTW7HANCNFSM4MCVNEFQ>.
|
What does the debug logs say? |
I get “bad credentials”
Logger: homeassistant.components.unifi
Source: components/unifi/controller.py:323
Integration: unifi (documentation <https://www.home-assistant.io/integrations/unifi>, issues <https://github.com/home-assistant/home-assistant/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+unifi%22>)
First occurred: 5:30:00 PM (1 occurrences)
Last logged: 5:30:00 PM
Unknown UniFi communication error occurred
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/unifi/controller.py", line 323, in get_controller
await controller.login()
File "/usr/local/lib/python3.7/site-packages/aiounifi/controller.py", line 68, in login
await self.request("post", url, json=auth)
File "/usr/local/lib/python3.7/site-packages/aiounifi/controller.py", line 151, in request
raise ResponseError(f"Invalid content type: {res.content_type}")
aiounifi.errors.ResponseError: Invalid content type: text/html
… On Apr 8, 2020, at 3:19 PM, Robert Svensson ***@***.***> wrote:
What does the debug logs say?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub <#33766 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABIV6MM2YYRPR4KCQ6KPVPLRLTZ5ZANCNFSM4MCVNEFQ>.
|
I just realized you said you're trying it out on 0.108. The support is only on dev so far |
Is this likely to land in 0.108.2, or 0.109.0? I'm not certain if this counts as a bugfix for a point release... Thanks for the fix :) |
This is not a bug fix. If you can please try it out on dev |
Breaking change
Proposed change
Identify if controller runs on UniFi OS or not.
Type of change
Example entry for
configuration.yaml
:# Example configuration.yaml
Additional information
Checklist
black --fast homeassistant tests
)If user exposed functionality or configuration variables are added/changed:
If the code communicates with devices, web services, or third-party tools:
Updated and included derived files by running:
python3 -m script.hassfest
.requirements_all.txt
.Updated by running
python3 -m script.gen_requirements_all
..coveragerc
.The integration reached or maintains the following Integration Quality Scale: