Currently, identification of bot wifi connectivity issues are based on a customer submitting a ticket or someone from Locus checking Fleet Monitor. The Locus system does not proactively identify/notify of potential issues. We have encountered situations where there are several offline/disabled bots at a site due to AP issues or insufficient wifi coverage for high traffic areas, but don't know about it unitl the customer submits a ticket.
It would be helpful if bots could report loss of connectivity over a defined time period (e.g., last 1 min, 5 min, 10 min, etc) and thresholds could be defined that generated alerts to Support if excessive loss of connectivity occurred. This would enable Locus to proactively respond to wifi connectivity issues impacting a customer and also identify Locus network issues that need to be addressed.