While this works, it isn't nearly as fast as the previous built-in chronometer, unfortunately. :/

I guess it might be better than nothing for now and works.

While this works, it isn't nearly as fast as the previous built-in chronometer, unfortunately. :/

What do you mean exactly with 'not as fast'? Which step? Why do you need speed in an app the is meant to run contentiously and sleeps for 5 seconds on each round?

I mean the initial display takes a lot longer compared to the old built-in chronometer (pihole -c -e), but like I said, it's better than nothing and it works :)

I've been thinking about removing the startup countdown (which adds at least 3 seconds) for a long time. Maybe this should be done now, at least for --runonce?

I'm testing this on a slow device RPi 1 Model B:

real	0m15.731s
user	0m9.602s
sys	0m1.969s

I don't recall exactly how long it took with the old built-in chronometer, though :/

The slowness on RPi 1 is probably due to the jq handling of the API's JSON.
You know, you can run PADD now remotely on your super-beefy main machine which should be much faster ;-)

With the startup countdown removed

Can you push the patch so that I give it a go too?

Saved 2,5 sec

Yup, not bad.

This pull request has conflicts, please resolve those before we can evaluate the pull request.

Conflicts have been resolved.