Thank you for the feedback messages. There was still room for improvement:

The widget now detects display blanking/unblanking - as it should be of course - and stops/resumes tracking (i.e. cpu load ~0% when blanked). If "stop server when not connected" is enabled status is tracked once per minute.

I added an option "enable tracking" which is selected by default. But if one has the display on and the server running most of the time it might be better to disable tracking. In this mode the button displays just on/off. The number of connections can then be called up by long pressing the button and again from the confirmation dialog (see screenshot in post #1).

"Keep wifi power management off when connected" (to avoid input lags) is now implemented into the server configuration. This way it still works when tracking is disabled. Changes to this option take now effect immediately (the script is being restarted), so power management can be turned on/off on demand. This might be useful because of the increased battery drain when power managment is kept off.


Changes in v1.6-0:
* added power saving features:
+ widget detects display blanking and almost falls asleep
+ tracking made optional, just switch on/off and call up number of connections manually
* wifi power mangement is now implemented into the server configuration
* added option to choose wifi-pm refresh time
* confirmation dialog changed