-
-
Notifications
You must be signed in to change notification settings - Fork 322
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 Network Application API #626
Comments
output of
ouput of
|
There is also:
I think average_satisfaction would be a good one to report on. |
I try to change API endpoints locally, now it connect it, but not get any data. with browser, i able to read the data that Heimdall want to show it. |
Trying this also, changing the endpoint reports a successful login but I get no data changing the health endpoint. Looking at the code and the health endpoint data I would say everything expect for the uptime should work, the name of the properties (num_user, etc) look the same. |
@igorkulman thanks! |
Works perfectly. Thanks. Will this get pulled into the source? |
Thanks for testing, I have opened a PR with this #645 |
Have you guys tested this with a UDM or other unifi HW? Because per my PR, the only problem there was the decimals. (I am running the lastest firmware). I will test your code against my UDM, to see if there is really a difference between the appliance and the real HW. |
I only tested in my home setup which is Unifi Controller 7.4.162 running in a docker container on Linux. |
Can you quote exactly what goes in the enhanced api url field? I have this right now: "https://192.168.40.2/api/login" Says API successful but no stats |
|
I've try that, still can't get it to connect? |
Hello, I tried editing the ./config/www/SupportedApps/UniFi/UniFi.php |
I got this to work. here are the steps I took.
|
@igorkulman fix also worked for me. Pity it isn't being rolled into the official Heimdall release. I guess when updating to a newer version of Heimdal in the future, it will break again? |
@ZoltrixGFC The reason its not being rolled into the official release is likely because the fix appears incomplete. It would break things for people with UDM. (based on comment from @gavinmcfall ) In other words: it needs work. |
@mvdkleijn all good, I think maybe it has already been rolled in. The last update to Heimdall didn't remove the changes. |
Then I'll close this issue if no-one objects. Feel free to comment if that's a problem, I'll reopen. |
For what It's worth, I am running Heimdall 2.6.1 and I had to perform the fix listed above in order for the API to connect. Unifi Controller Network 8.0.26 and 8.1.113 |
Maybe this could just be split out so that UniFi Network is one type (with this fix) and UniFi remains the old Controller type (ie. without this fix) ? |
or a checkbox to select which type you're running I am having to revert these changes to connect to my self hosted Unifi controller but would prefer to stay vanilla. |
I created a PR #798 for the above (added a config switch for Self Hosted controllers). |
Hello, the current UniFi code doesn't work well with UniFi Network Application due to specific differences in it's API:
the login route must use:
/api/login
(not /api/auth/login). The health route must use:/api/s/default/stat/health
(not /proxy/network). There is no data for wan availability or lan availability on the health route (at least for my use case, I'm running the Network Application within an LXC container under proxmox). I found "uptime" available from route:/api/s/default/stat/sysinfo
. I'm running UniFi Network Application ver 7.3.83 under linux (LXC).The text was updated successfully, but these errors were encountered: