It would be very useful if Repeaters could keep stats of #messages dropped per un-configured Region, and make those stats retrievable in Remote Management and/or via CLI.
My Repeater may be receiving thousands of messages for a Region for which it is not configured and dropping those messages - at the moment we are completely blind and have no way of seeing which Regions our Repeaters are dropping messages for.
If I could see that my Repeater is receiving & dropping thousands of messages for Region 'xyz' then I might consider adding Region 'xyz' to my Repeater - but at the moment we have no way of knowing.
Whilst the Repeater itself won't be able to resolve the clear-text for the un-known Regions it can still record the coded/encrypted (unknown) region code and keep track of the number of messages per encrypted (unknown) region ID. Those can then be retrieved by the app - and even if the app can't resolve those region names then you might be able to use some on-line tool to try to resolve the region name - for example MeshRank is able to do this as it now displays Region names on all messages with scope set - so it's certainly do'able.
It would be very useful if Repeaters could keep stats of #messages dropped per un-configured Region, and make those stats retrievable in Remote Management and/or via CLI.
My Repeater may be receiving thousands of messages for a Region for which it is not configured and dropping those messages - at the moment we are completely blind and have no way of seeing which Regions our Repeaters are dropping messages for.
If I could see that my Repeater is receiving & dropping thousands of messages for Region 'xyz' then I might consider adding Region 'xyz' to my Repeater - but at the moment we have no way of knowing.
Whilst the Repeater itself won't be able to resolve the clear-text for the un-known Regions it can still record the coded/encrypted (unknown) region code and keep track of the number of messages per encrypted (unknown) region ID. Those can then be retrieved by the app - and even if the app can't resolve those region names then you might be able to use some on-line tool to try to resolve the region name - for example MeshRank is able to do this as it now displays Region names on all messages with scope set - so it's certainly do'able.