Federico Capoano
Federico Capoano
Extend the [REST API of OpenWISP Controller](https://github.com/openwisp/openwisp-controller/pull/386#pullrequestreview-628538950) by adding two endpoints, one for the list of devices and one for the device detail. - `/api/v1/monitoring/device/`: list devices and include the...
We now get the values from the timeseries DB as GB, then convert them again in #397 so we should measure whether it's convenient to just show them in bytes...
Allow specify by custom date range: the user will be able to select a range of dates and reload the graphs for the dates specified. First the backend and API...
Now that #372 is merged, we should add a way to fetch / manipulate this data via REST API too. `/api/v1/monitoring/wifi-session/` filters (similar to admin): - device ID - organization...
The bar chart with timeframe higher than one month is not looking right:  The bars became too thin.
Depends on https://github.com/openwisp/openwisp-monitoring/issues/350. If not using HT/VHT, flag the HT/VHT field of WiFi clients as null and show it as with the unkonwn gray question mark icon instead of the...
In the device status, we're able to see different WiFi info like channel, frequency, noise, etc, but it's not evident whether that interface is working with in High Throughput mode...
I had to pin the inflxudb docker image used for testing to version 1.8.4 because the new version 2.0 breaks the tests: https://github.com/openwisp/openwisp-monitoring/pull/273 However, this is not great: we want...
This could help: https://github.com/msabramo/requests-unixsocket (I am not sure is required but if we need extra code to do this we can start looking from there).
The device status gets cleared after 24 hours, so if a device goes offline the connected wifi clients will still be shown in the device status tab. I am thinking...