Replies: 1 comment 3 replies
-
There is already a managed mode that does exactly what you want |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We are running a private mesh on a separate channel.
The purpose of our mesh is to provide tracking and communication for parents and their school children (mainly during the transition from primary school to high school when they start walking to school and start increasing their independence).
For this mesh to work it needs to be setup properly and all devices need to be in the correct mode. Our public mesh is an unusable mess because of incorrectly setup modules, wrong roles and old unmaintained devices sending out rubbish packets and taking hops that they can't possibly retransmit to anyone useful. It's a perfect example of how a mesh can turn to chaos without coordination.
Our mesh works, as intended, because it was setup correctly and I have personally configured every single device on it myself with the strict agreement that they not enter the configuration panel under any circumstances and not share any mesh configuration details with ANYONE.
It has gone pretty well so far, a few instances where the children have messed about with the configuration, but nothing serious until now. Someone has shared the configuration with an unknown person who has now joined the mesh with an improperly setup module role, so far the impact has been minor but if this spreads it will be a nightmare all over again.
Tl;dr: please add the option to pin code protect the configuration panel.
Beta Was this translation helpful? Give feedback.
All reactions