Docu: shifthelper appears to not call when solving the problem "too quickly"

[dneise]

#The shifthelper checks the status every 5minutes.
people seem not to realize that.

When a problem occurs, like main.js died and one solves it quickly, say withing one minute, then chances are high the shifthelper didn't even realize there was a problem. So no call will be sent out.

Also it is possible ones phone has a bad reception, so even though a call went out (to twilio) it didn't cause ones phone to actually ring. Things like bad reception can cause this.
Also here: If one does not get a call, but still fixes the problem, of course no second call will be generated.

We should remind shifters that the task of the shifthelper is not and has never been to support their decision to solve a problem in case they were just about to solve it anyway, but to remind them of a problem in case they were not aware of it in the first place. (maybe because they fell asleep)

So in order to "test" that the shifthelper does its job, one must first "fail" as a shifter, i.e. one should not react immediately on a smartfact alert, but wait 5 or 10 minutes.

If this time is too long, we need to reduce the check interval from 300 seconds to maybe 60? or maybe 1?