Open Isilorn opened 8 months ago
Hi @Isilorn, probably on Unifi API U-LTE-PRO is categorised as UAP so is treated as that by the template. Unfortunately I don't have a U-LTE-PRO for tasting and Unifi API it lacks of documentations. The only way I can add this device is if you can give me the JSON response of the Unifi API for U-LTE-PRO.
Hello @MassimilianoPasquini97 with pleasure, I'll need some guidance to interrogate the Unifi API 😄
I'm using MacOS and Linux so shell script or command line will be fine
@Isilorn Follow this steps:
auth.json
containing Unifi credential. Replace {$UNIFI.USERNAME} and {$UNIFI.PASSWORD} with your credential. User must be a local user and is preferred to not use the same used by Zabbix.{
"username": "{$UNIFI.USERNAME}",
"password": "{$UNIFI.PASSWORD}"
}
curl -k -X POST -d @auth.json -c cookie --header 'Content-Type: application/json' https://{$UNIFI.IP}/api/auth/login
curl -k -X GET -b cookie --header 'Content-Type: application/json' https://{$UNIFI.IP}/proxy/network/api/s/default/stat/device/{$UNIFI.UAP.MAC}
The data is ready (and I've taken a look at the formatted version with jq), but I apologize for this potentially silly question... Where would you like me to send you a DM? I can't do it here on GitHub, and it seems disabled on Twitter 😊
I have enabled DM on X now, you can reach me there.
I recently added a U-LTE-PRO to my network setup, but it is being recognized as a WiFi access point. This is causing errors such as "wifi0 state is not RUN". I'm concerned that this misidentification might lead to missing some critical alerts (like switching to backup connection, loss of signal, etc.).
Here are the types of information being reported in Zabbix for the U-LTE-PRO:
And this is what's displayed on the UDM-SE interface for the device: