[Board]: Change the "Client" role to "Client Mute" by default

[Nicolayka]

SOC

Other

Lora IC

All

Product Link

all stores

Description

I appeal to the developers! Due to the fact that the meshtastic network is expanding at a very high pace, and users who buy these devices do not particularly bother with their configuration, a huge number of devices with the Client role appear on the network. Due to the fact that the device has not been configured, the network is littered and messages are not getting through (there may be 5 or 10 devices with this role in one place). I kindly ask you to review the default role parameter in the firmware and change it to Client Mute! Those who read the manuals and understand the setup will change the role for themselves, and will not interfere with others. In St. Petersburg, as well as in other major cities, this parameter has caused a lot of problems! And the situation is getting worse every day.... Every fifth device was simply turned on, without any settings. People think they're helping to expand the network, but they're hurting, maybe I don't even know about it... Please kindly change this parameter.

---

Обращаюсь к разработчикам! В связи с тем, что сеть meshtastic расширяется очень большими темпами, и пользователи, которые покупают эти устройства, особо не заморачиваются с их настройкой, в сети появляется огромное количество устройств с ролью Client. Из-за того, что устройство не было настроено, сеть замусорена, и сообщения не доходят (в одном месте может быть 5 и 10 устройств с такой ролью). Очень прошу вас пересмотреть параметр роли в прошивке по умолчанию, и изменить её на Client Mute! Те, кто читают мануалы и понимают в настройке, изменят роль под себя, и не будут мешать другим. У нас в Санкт-Петербурге, да и в других крупных городах этот параметр вызвал огромное количество проблем! И с каждым днём положение усугубляется.... каждое пятое устройство было просто включено, без настройки. Люди думают, что помогают в расширении сети, но они вредят, может даже не знаю об этом... Огромная просьба изменить этот параметр.

[github-actions]

@Nicolayka, Welcome to Meshtastic! 👋

Thanks for opening your first issue. If it's helpful, an easy way
to get logs is the "Open Serial Monitor" button on the Web Flasher.

If you have ideas for features, note that we often debate big ideas
in the discussions tab
first. This tracker tends to be for ideas that have community
consensus and a clear implementation.

We're very active on discord,
especially the #firmware and #alphanauts-testing channels. If you'll
be around for a while, we'd love to see you there!

Welcome to the community! ❤️

[b8b8]

This would make Meshtastic not a mesh by default.

Bad idea, youre just recreating a cell network if you do this.

[Nicolayka]

This would make Meshtastic not a mesh by default.

Bad idea, youre just recreating a cell network if you do this.

And now the messages are lost and not getting through, because of such "clients".

[b8b8]

The problem in most European cities is a single channel is used for EVERYTHING. Traffic lights, power meters, meshtastic, meshcore, everything (unlike North America which has over 100 channels spread over 902-928 MHz). There is constant interference. What is working well in UK and Finland is the new narrow band channels that get around this. If it works well in London, it will work in St. Petersburg.

[Deuteranomalous1]

The mesh algorithm already takes care of this. Clients only rebroadcast if they do not hear a rebroadcast within the window with timing relative to received SNR of the message/traffic.

The issue of messages being black holed is often caused by poorly placed router nodes.

[b8b8]

Ill try and find a link for the new narrow channels and post back here.

[b8b8]

#9038

#8855