So, I wrote a complete solution that exists of a client script written in Bash and a server application written in Python.
The monitor service has some tags for a deployment in træfik. docker.sh build fing fing-parser will be enough.
docker.sh -help to know how to use it, but probably a. Maybe the last two are not needed, but well, they are in the script just in case.
For helping to build everything, a bash script called docker.sh is provided that allows you to build, remove, push and pull the images. Could be a good start for a deployment in your home. The repository has a docker-compose.yaml file that I'm using right now to deploy the system in my home. It is a simple node.js app with an index.html that shows the dashboard. It is optimized enough to sniff around, but maybe not at all for lots of devices in screen. The simple page has a fully functional dashboard to observe all information stored in the databases.
A structure for initial influxdb database can be found in the folder /influxdb.
All information will be stored in the same measure in influxdb (retention policy must be week_rp and measure must be activity) and in the same redis database (with keys prefixed with fingo: and the MAC after). The python script listens for every change in the shared folder (shared between all fing instances and the script), but only acts when the change has something to do with. You can listen for different networks by creating different fing instancies. The -o thing tells fing to write to that. As an (typical) example, 192.168.1.0/24 would be a value for that. The NETWORK_IP/NETWORK_MASK must point to the network you want to watch. If you don't want that, you can disable with a false. The -d argument is to force obtain the domain names of every device. To make it work, fing should start with this arguments fing -d true -n NETWORK_IP/NETWORK_MASK -o table,csv,/fing/SOME_NAME.csv. This script listen for changes in a folder, and when a file is changed (and is a csv) stores all the information in the influxdb and redis databases. And now the little python script (called fing-parser) comes into the game. Using the right arguments, fing can write the scanning into a. Uses fing app to detect the devices available in the network and if they are connected or not. It is available a simple page that allows you to monitor quickly the uptime. Uses fing to observe the changes and a little parser that listens for changes in a file fing edits and stores the data in an influxdb measure and some extra data into a redis database. Everything in Docker containers, and ARM friendly.
Known when your network devices are connected to your home's network with a good precission in time.