Connection count scoring is skewing the overall score

[Cyb3r-Monk]

If my calculations are correct; when the sleep value of a beacon is higher than 10 seconds, the connection count score is greatly impacted which skews the overal score calculation. Below are examples:

Sleep: 10s
Duration: 43200s (12h)
Conn. count: 4320
Conn. score: 1.0

Sleep: 15s
Duration: 43200s (12h)
Conn. count: 2880
Conn. score: 0.66 (big decrease)

Sleep: 30s
Duration: 43200s (12h)
Conn. count: 1440
Conn. score: 0.33 ( huge decrease)

I think the connection count score calculation needs some improvement. Increasing the divisor could help.

tsConnDiv := (float64(a.tsMax) - float64(a.tsMin)) / 10.0 -> maybe 60.0? 
tsConnCountScore := float64(res.ConnectionCount) / tsConnDiv
if tsConnCountScore > 1.0 {
tsConnCountScore = 1.0
}