BTW, I have looked at several implementations of Radio AI / WiFi AI.

Everything I can find indicates that the only thing happening here is the system is looking at wifi channel usage, quality, etc and selecting parameters based on which channels have the lowest noise and what APs are within reach.

The only AI piece I can think of (which is really a stretch calling it AI) is keeping a history of channel quality statistics ... so you aren't switching channels when a "bad" channel becomes "good" for a short time.

This should all be do-able with wifi channel quality from regular channel scans.

It looks like the recent controler update made changes to the API. There is now an extra parameter (omadacId) in the URL that you have to retrieve through /api/info.

Then you can get the token at %omadacId%/api/v2/login. However from there on I don't know how to proceed. 

Previously I could just take this 'token' value and set it as a parameter, token=. However, viewing in Chrome, this has now changed to _=, but with the token it no longer works. Any suggestions?

@Driekes I am experiencing the same. I've been trying to change the python script that worked to a PHP script. I am able to log in, but I can't process a get request for active clients or devices.

Is there any news on an updated API documentation

I was able to generate a PHP API v2 curl session. Which allows me to get the data required, with the implementation of a cron job I now get every 15 minutes actual connected devices from my site stored in a JSON file.

If anyone is interested i'd like to share the code.

@ml88nl I also got it working. I received a 'latest version' of the documentation but it is partial. Compared with the already linked V2 you should come a long way.

So I mentioned before that indeed you have to retrieve the new path, and then the token is no longer in the URL, but a Csrf-token in the headers. That should work.

@Fae 

This one is incomplete, e.g. it does not contain info related to login. Can you check if there is a more complete version?

@Fae If I look at the previous shared docs, it also had a portion about login, that is missing. So login, loginstatus, logout, what to put in the headers (token), path etc.

Because that is the part that was changed I had to test a bit more. I have only a limited use case, so now I figured the login part out I am good, so I don't know if other parts are missing too.

@Driekes 

maybe you could share how you managed to get the login request working?

I'm actually trying to build a curl on the shell:

curl -k --header "Content-Type: application/json" --request POST --data '{"username":"admin","password":"mypassword"}' 'https://10.10.10.8:8043/ed773722bbb0914cb064dd2772d68f4e/login'

But I get this error in my response:

{"timestamp":1644794750844,"status":405,"error":"Method Not Allowed","message":"","path":"/ed773722bbb0914cb064dd2772d68f4e/login"}

Otherwise it looks like I have to wait for a positive response from Fae